

SRM/UX Support
______________

Introduction
____________


The 3.24 release of the Pascal Language System will provide support for
the Hp-ux SRM/UX system for the first time. SRM/UX is a server process
running on Hp-ux together with a collection of control files that emulate
the Shared Resource Manager (SRM) familiar to many Pascal System users.
Physically, an SRM/UX system will consist of a series 300, series 400, or
series 800 workstation running Hp-ux connected to one or more Pascal
Clients by way of a LAN cable or an SRM cable.

Performance with the SRM cable should be about the same as with SRM in
most reasonable situations. With the LAN cable speedups range from
modest to pretty good, in some cases up to 3x or 4x. 

SRM/UX allows the sharing of files between an Hp-ux system, BASIC WS
System, and Pascal Language System. A portion of the Hp-ux file system
is brought on line by running an appropriatly modified TABLE program
and appears to the Pascal Client roughly as an SRM volume would. SRM
systems may be replaced with SRM/UX systems by replacing the existing
SRM server with an Hp-ux SRM/UX server. An existing SRM server is not
upgradable to an SRM/UX server.

The advantages of SRM/UX are :

 * easy transfer and sharing of files among Hp-ux, BASIC WS, and Pascal
   Language systems

 * peripheral sharing through a central server computer 

 * software compatibility with most existing SRM applications


What SRM/UX is and is not
_________________________

SRM/UX is :

 * A mapping of SRM services onto an Hp-ux system.

 * A way of networking Pascal Workstation Systems to a standard centralized
   server.

SRM/UX is not :

 * A 100% emulation of SRM under Hp-ux. 

 * A way of running the Pascal Language System under Hp-ux, or the reverse.

 * A service that can be hosted on any arbitrary UNIX+ implementation.


+ UNIX is a trade mark of AT&T Blah Blah Blah ...

Getting Started
_______________

This section is not meant to be a replacement for the SRM/UX server
documentation ("SRM/UX: System Administrator's and User's Guide",
HP Part No. E2085-90000). Indeed, for a full explanation of SRM/UX
capabilities and limitations, the server document is required.
This section is meant to help one get started using a Pascal System
with an SRM/UX server, and to provide troubleshooting tips for
using the Pascal System with the SRM/UX server. The primary focus
will be one client with one server. This setup procedure can then
be cloned as many times as needed to create a fully configured
SRM/UX network.

Since SRM/UX runs on an Hp-ux server, a part of SRM/UX administration 
will involve maintaining the underlying Hp-ux system. This often
requires a full time system administrator. This person may be responsible
for maintaining the SRM/UX system as well, but this is not a
requirement. Proper use of the SRM/UX system requires a dedicated
SRM/UX system administrator with good knowledge of Hp-ux and who has
the authority to do system administration tasks, such as changing
or updating system files, re-building the system kernel, etc.

H/W requirements and limitations
________________________________

SRM/UX may operate over a LAN cable or an SRM cable, the actual
capabilities depend mostly on the bootrom present in the machine
to be used as the client. Series 200 bootrom revisions were numbered
1 thru 4. Series 300 bootrom revisions (so far) have been designated
A, A1, B, C, C1 and D.

SRM Cable
_________

All series 300 workstations can boot Pascal from the SRM/UX server over
the SRM cable. All series 200 workstations with Bootrom Revisions 3 and
4 can boot Pascal from the SRM/UX server. Early series 200 machines
with Bootrom versions 1 or 2 cannot boot Pascal over the SRM cable, but
they can be upgraded to Bootrom revision 3 or 4 and then become capable
of booting Pascal over the SRM cable.

LAN Cable
_________

All series 300 workstations with Bootrom revision B or later can boot
over the LAN cable. Series 200 models 226 and 236 may connect to the
SRM/UX server over the LAN cable after local boot, but they may not boot
from the server over the LAN cable. No other series 200 model may connect
with the server over the LAN cable in any way.

The Hp-ux File System, the Control File /etc/srmdconf, and Available
____________________________________________________________________

SRM/UX Volumes
______________


On the server machine, a control file (/etc/srmdconf) describes to
the server process (/etc/srmd) information about all the
Pascal Clients and the volumes they may access. Volumes are brought
on-line on the Pascal Client by executing a TABLE program which
contains appropriate calls to the routine tea_srm, just as volumes
are brought on line with the real SRM.

Srmdconf contains five tables. They are :

* VOLUME-TABLE
* LAN-CLIENTS
* SRM-CLIENTS
* SPOOL-ENVIRONMENT
* SPOOL-TABLE

For the present discussion, only the first 3 tables are relevant. Once 
your SRM/UX administrator has configured the system, ask him or her to
print a copy of srmdconf for you. This file will describe for you
all the volumes you may bring on line as a Pascal Client and provide
you with enough information to do it.

Following is a sample srmdconf file. We only show the entries for 4
volumes in the volume table, 1 LAN client, and 1 SRM client

VOLUME-TABLE

# Volume Descriptions
#
# Name      Address  Uid   Gid   Temp Directory   Root Directory
#----------------------------------------------------------------------------
 SRMUX_ROOT  :   8   : 17  :   9 :                : /srmserve
 HPUX_ROOT   :   9   :     :     : /tmp           : /
 JOHN        :  10   :     :     : /tmp 	  : /users/john
 SUSAN       :  10   :     :     : /tmp           : /users/susan

LAN-CLIENTS
# Clients
#
# Link Address   Internet     Node Snode Name     Uid   Gid  Umask Volume List
#-----------------------------------------------------------------------------
 0x80009123456 : 15.2.48.62  :  2 : 0 : Susan   : 213 :  20 : 022 : SRMUX_ROOT,
 HPUX_ROOT,SUSAN # Susan's Workstation

SRM-CLIENTS

# SRM Clients
#
# SRM Device SRMnode   Name       Uid  Gid  Umask  Volume List
#----------------------------------------------------------------------------
 /dev/srm  :   41   :  John     : 212 : 20 : 022 : SRMUX_ROOT,JOHN # John's
 Workstation


From the VOLUME-TABLE entries we can see where the possible volumes
actually sit in the underlying Hp-ux file system. This is illustrated
below :



        *************** FIGURE 1 HERE ********************


These are all the volumes users may bring on line (in this example).
Within the Volume List column for Susan's workstation we see that her
workstation may access the volumes SRMUX_ROOT and SUSAN. John's 
workstation may access the volumes SRMUX_ROOT and JOHN.
Looking at the the srmdconf file for your own system will show you
which volumes your workstation may access. We will come back to
this sample srmdconf file as needed.


Establishing a Boot Environment for Pascal Clients
__________________________________________________

Client Side Considerations
___________________________

This section describes, in general terms, the tasks required on the
workstation side to get SRM/UX up and running with an Hp-ux SRM/UX
server and a Pascal Workstation client. These steps assume all the
server side tasks have been completed.


The Software on the PaWS client side
____________________________________

The key modules on the Pascal Client side are DATA_COMM, IOMPX, LANDVR,
and SRM. The module DATA_COMM is contained in the file DATA_COMM (which
is located on the CONFIG: disc for single-sided media and the ACCESS:
disc for double-sided media), the IOMPX and LANDVR modules are contained
in the file LAN (which is located on the LIB: disc for single-sided media
and the ACCESS: disc for double-sided media), and the SRM module is
contained in the file SRM (which is located on the CONFIG: disc for
single sided media and the ACCESS: disc for double-sided media).

For SRM/UX connectivity over the SRM cable, the modules DATA_COMM and
SRM are required. For proper booting over the SRM cable, these modules
should be placed in the user's INITLIB file, in the order DATA_COMM
followed by SRM. 

For SRM/UX connectivity over the LAN cable, the modules IOMPX, LANDVR
and SRM are required. For proper booting over the LAN cable these
modules need to be placed in the user's INITLIB file in the order
IOMPX, LANDVR, and SRM.

Placing the modules DATA_COMM, IOMPX, LAN, and SRM in your INITLIB
file allows booting over LAN or SRM cable.

The modules normally are inserted into INITLIB using the techniques
described in Pascal 3.2 Workstations System, Vol. 2, in the chapter
Special Configurations. The file system driver SRM uses either of
the device drivers LAN or DATA_COMM, depending on whether the application
is communicating via a 98643A LAN card or via a 98629A SRM card.

Establishing Contact
____________________

Contact is established with the SRM/UX system with the tea_srm call
in the TABLE program just as it is with the real SRM. Since the Pascal
Language System is shipped on floppy discs, the system must be copied
from the Pascal Client to the server's file system after local boot
to establish a bootable system on the SRM/UX server.

To establish initial contact, set the select code of your client
workstation SRM or LAN card to 21, and carry out the following steps :

For SRM cable
_____________

1.) Execute DATA_COMM (which loads the DATA_COMM module)
2.) Execute SRM (which loads the SRM module)
3.) Re-run the TABLE program that executed when you first
    booted 

If the node address of the SRM card in the server is set at 0 then
the volume corresponding to volume address 8 as described in the
VOLUME-TABLE section of srmdconf should appear at unit #5 after
requesting a volumes listing with the FILER. Also, if your SYSTEM
directory has been set up, it will appear at unit #45.

If you carry out these steps and cannot bring volume 8 on line at
unit #5, check with your SRM/UX administrator and make sure the
server node address is set at 0. If it is not set at 0, you will
need to modify your TABLE program to override the default SRM
Device Address Vector values, recompile it, and re-execute it
to establish contact with the server. CTABLE.TEXT is the actual
file to modify.

The easiest solution is to have the server node address set at
0 and this is the recommended configuration. This may not always
be possible, however, because it is possible to have multiple 
SRM/UX servers or even a mixture of real SRM and SRM/UX servers
on the same local SRM subnet, and all these servers need to have
unique node addresses. 

Near the end of CTABLE.TEXT you can find the following code :

with SRM_dav do
   begin
   { tea_srm(46, sc, ba, du);  {free unless booting from HFS 
     hard disc}
     tea_srm(45, sc, ba, du);  {for possible use as the system unit}
   end; {with}

Modify this slightly to 

with SRM_dav do
   begin
     tea_srm(5, SC, M, 8);
   { tea_srm(46, sc, ba, du);  {free unless booting from HFS 
     hard disc}
     tea_srm(45, SC, M, du);  {for possible use as the system unit}
   end; {with}

Where M is the node setting on the SRM card in the server, and SC is
the select code setting of your client SRM card. Compile CTABLE.TEXT,
execute it, and request a volume listing with the FILER.
If volume 8 does not come on line at unit #5, ask your SRM/UX system
administrator for help.


For LAN cable
_____________

1.) Execute LAN (which loads the IOMPX and LANDVR modules)
2.) Execute SRM (which loads the SRM module)
3.) Re-run the TABLE program that executed when you first
    booted 

If the emulated node address of the the server is set at 0 (you can
read this value from the file srmdconf) then the volume corresponding
to volume address 8 as described in the VOLUME-TABLE section of srmdconf
should appear at unit #5 after requesting a volumes listing with the
FILER. Also, if your SYSTEM directory has been set up, it will appear
at unit #45. 

If volume 8 does not come on line at unit #5, get the emulated node
address of the server from the srmdconf file and carry out the steps
as described above in the section for the SRM cable, i.e. modify
CTABLE.TEXT, recompile it, and execute it. If this does not bring
volume 8 on line at unit #5, ask your SRM/UX system administrator for
help.


Setting Up a Bootable System
____________________________

Once contact with the server has been established, you may begin
copying all the system files from the floppy discs to your system
directory on the server. Your system directory should be at unit #45
but you can also reach it by prefixing down from the root at
unit #5 to WORKSTATIONS/SYSTEMnn or WORKSTATIONS/SYSTEMnnnnnn,
depending on whether you are running over SRM or LAN cable.

Establishing contact with the server is simple if the SRM/UX system
administrator has the SRM/UX system configured properly. If you carry
out the above steps and still cannot establish contact with the server,
ask your SRM/UX system administrator for help. Once contact has been
established between the server and client, the Pascal system files
can be copied to the server in preparation for setting up a bootable
system on the server.


Proper Location of System Files
_______________________________

Relative to the directory corresponding to volume 8 (this will appear
at unit #5 after running the TABLE program shipped with the system)
the file SYSTEM_P needs to be placed in the directory SYSTEMS. Also,
relative to this same directory (corresponding to volume 8), each client
needs to have the extension boot files (INITLIB, STARTUP and TABLE)
present in either the generic directory WORKSTATIONS/SYSTEM or in a
unique directory corresponding to each client named WORKSTATIONS/SYSTEMnn
(for SRM cable clients, nn corresponding to the node number switch
setting on their SRM card) or WORKSTATIONS/SYSTEMnnnnnn (for LAN clients,
nnnnnn being the last 6 digits of the Lan ID number for the LAN card).
Any alphabetic characters in the hex address must be capitalized in the 
name of the directory, i.e. /WORKSTATIONS/SYSTEM0034EF works but
/WORKSTATIONS/SYSTEM0034ef does not.





      *************** FIGURE 2 HERE ********************

                (showing files relative to volume 8)


If the system is being set up for a large number of Pascal Client
users, it is better to establish one system directory called something
like WORKSTATIONS/SYSTEM3.24. Then all the generic system files can
be dup-linked to each individual clients system directory to save
space in the servers host file system. Some files will be unique to
each clients system (e.g. TABLE and AUTOSTART) so not all the system
files can be shared, but most of them can be.

Now if power is cycled on the client workstation, the client bootrom
will display SYSTEM_P on the SRM/UX server as a bootable system. The
system may be selected in the usual way and booting will commence.
Assuming the proper TABLE program is used (the one used to establish
initial contact with the server) the root of the SRM/UX system should
come on line at unit #5 and if the client SRM or LAN card has select
code set at 21, unit #45 will come on line prefixed to the client's
system directory.


Default Configurations
______________________

TABLE is the configuration program for PaWS; it sets up the entries in
the PaWS unit table, usually at boot time. The code file TABLE is on
the boot microfloppy that HP ships with PaWS, and should be copied to
a boot directory on the SRM/UX server. The source for TABLE, called
CTABLE.TEXT, is supplied with PaWS on the ACCESS: or CONFIG: disks,
so that the user can easily modify the unit table configuration.
Users may modify their own TABLE program to access any SRM/UX volume
that /etc/srmdconf specifies they may.

TABLE configures the various drivers and devices into the unit table.
By default it will configure disk Volume 8 on any SRM or SRM/UX whose
host node number is 0 and which is connected to a 98643A or 98629A
at select code 21 in the PaWS machine, into the unit 
table at unit entry #5. In addition, if the subdirectory 
/WORKSTATIONS/SYSTEMnnnnnn (or /WORKSTATIONS/SYSTEMnn for a 98629A 
card) or /WORKSTATIONS/SYSTEM exists, unit entry #45 will be created and
associated with that subdirectory.

As well, if the PaWS client is booted from either a real SRM or from
SRM/UX, that server will be assigned units #5 and #45 as above,
regardless of whether the select code, host node number, or disk Volume
number match the defaults. Assignment of unit #45 is contingent on the
existence of its associated directory.

If either the driver for the card (LAN or DATA_COMM) or the SRM driver
is not in INITLIB, units #5 and #45 will not be connected at all.

Using SRM/UX on a 98643A card in PaWS does not preclude using the
card simultaneously for other applications, for example the NRC FUSION
software (ftp and telnet utilities). IOMPX provides multiplexed access
to the LAN card. The 98629A card can only be used for SRM. It is not
a general purpose I/O card.


Custom Configurations
_____________________

One can imagine wanting to make several modifications to the above
scheme: adding more unit entries with which to talk to one server,
being connected to several servers at once, etc. Some of these
possibilities are allowed for in the current implementation.



          ******** FIGURE 3 HERE ******************

          (show file system diagram with susan's directory
           PROJECT/DOCS)

In the above example, SUSAN may have a particular directory, say
PROJECT/DOCS (relative to the volume SUSAN) that she is currently
working in. She can modify her TABLE program to bring the volume
SUSAN: on line, at, say unit #46, and then prefix down to the
directory PROJECT/DOCS with a call to unit_prefix_successful in
the source for CTABLE.TEXT. This is illustrated below.

Adding Unit Entries
___________________

Near the end of the source, there is a call to tea_srm which passes
the number 46. Find this source line and clone it as many times as
you need extra unit entries. Then modify each clone to assign 
it an unused unit number. Below is an example:

with SRM_dav do
   begin
   { tea_srm(46, sc, ba, du);  {free unless booting from HFS 
     hard disc}
     tea_srm(45, sc, ba, du);  {for possible use as the system unit}
   end; {with}

You should modify the commented-out line to look like this:

tea_srm(46, sc, ba, 10);  {free unless booting from HFS hard disc}

This hooks up unit #46 to the volume SUSAN. This mapping (disk unit #10
with the volume SUSAN) is implied by the entry for Susan's workstation
in the LAN-CLIENTS portion of the file srmdconf on the server.

You will also need to modify some lines a little farther down in CTABLE.
The purpose is to prefix the unit down a desired path as the boot-up default.
Find the line

{ if not unit_prefix_successful('#46:?') then zap_assigned_unit(46);}

and remove the "{" and the "}" from the line and replace the "?" with the
desired default path. E.g. :

if not unit_prefix_successful('#46:/PROJECT/DOCS') then 
      zap_assigned_unit(46);

will set up unit 46 pointing to the directory PROJECT/DOCS, relative to
the volume SUSAN (/users/susan in the underlying Hp-ux file system)
unless that path can't be found, in which case unit 46 will be erased.

When the source is changed satisfactorily, compile CTABLE and execute it.
Use the FILER's Volumes command to check if things went well. Once the
Unit Table setup is being done correctly, you can copy CTABLE.CODE onto
your boot disk (or SRM/UX boot directory) naming it TABLE, TABLEP33, etc,
as needed for your specific boot setup.

The above scheme may be repeated as many times as you like, to the extent
that you do not run out of available unit table entries.

The above example brings on line a volume and directory on the same
server as the client was booting from. The TABLE program may be also
used to bring volumes and directories on line fromother servers provided
the client is set up on that server with all the proper entries in
srmdconf on that server.

Accessing Other SRM or SRM/UX Servers
_____________________________________

Add or modify lines that call tea_srm, setting the ba value to the
Server Node number (as seen in /etc/srmdconf on the other HP-UX
SRM/UX server machine) desired. If the other server (SRM or SRM/UX)
has node number 1 relative to this client, the call

tea_srm(48, sc, 1, 8);  { free unless booting from HFS hard disc }

sets up unit 48 to talk to volume 8 on an HP-UX machine whose srmd
server is pretending to be SRM host node 1 for this PaWS client.
The relevant part of the /etc/srmdconf file on this HP-UX machine might
look like this:

# ABC's Workstation
0x80009001234 : 33 : 1 : 160 : 27 : 022 : SRM, ABC

where the 98643A in the PaWS client has LAN address 0x80009001234.
Note the value 1 in the "server node" field.

Add a line to call unit_prefix_successful (as in the above example),
compile and execute.

Again, once the execution of CTABLE.CODE brings all your volumes
replace your TABLE program with CTABLE.CODE.

For further information, especially server setup and administration,
see the document "SRM/UX: System Administration and User's Guide".

PaWS FILER with SRM/UX
______________________

The FILER commands available to the PaWS user will be a mixture
of SRM and HFS commands. For SRM/UX volumes the filer will
display BOTH file locking and HFS permissions information when
the extended listing request is made.

For a normal listing,
the only difference visible to the user will be where the
filer displays 'Directory type ='. For SRM volumes, something
like Directory type = SRM 21,0,8 is displayed. This shows the
information select code = 21, bus address = 0, and disk unit =
8. For HFS volumes, Directory type = 777      17     9  will
be displayed, indicating file protections 777 and uid = 17,
gid = 9. For SRM/UX volumes, Directory type = SRM/UX 21,0,8
will be displayed, i.e. the SRM type of information is
simulated.

For an extended listing with an SRM/UX volume,
the field '..directory info...' will be
enhanced to show both the SRM 
like file locking status for the file, and also the HFS
permissions associated with the file. For example,
currently SRM volumes may display

           ..directory info...
           MRWSPC CLOSED

Also, the words SHARED, EXCLUSIVE and CORRUPT may replace CLOSED
in the directory info description. Of course, CLOSED, SHARED and 
EXCLUSIVE represent the file locking attributes held by the
file.

MWRSPC describes access rights to the file.

HFS volumes will display

           ..directory info...
           d777m    17u     9g

If the file is not a directory, 'd' will be blank. The '777'
entry describes the file protections, 17 and 9 the user and
group id's associated with the file.

For SRM/UX volumes, the directory info field will contain a
mixture of these two formats. The HFS info will remain in
place, and also two letters will indicate the current file
locking status with 'CL' for closed, etc. :

           ...directory info.....
           d777m    17u     9g CL

Here 'CL' could also be 'EX', 'SH' or 'CO'.

New Commands
____________

There will be some new commands available to the user for SRM/UX
volumes, in particular controlling HFS permissions for SRM/UX
from the workstation will be new. What will this look like ? 
Basically, the FILER's HFS command will be enhanced to work
with SRM/UX units as well as HFS units (note that for the
workstation, HFS usually means a local hard disk and not the file
system being shared with the HP-UX server). For files to which
the workstation has access, the UID and GID fields may be
modified, as well as the file mode which describes access
rights for owner, group and other. 

Hp-ux Special Files
___________________

As with an HFS disk, the Pascal Workstation System may see files on
the server intended for use only by the Hp-ux operating system that
the server process is running on. When doing an extended listing with
the FILER these files will be shown as having file type = 0 (which
prevents the Workstation from opening or manipulating the file) and
a letter will be printed before the mode for the file indicating the
file type, as follows

       letter         actual file type
      _______        _________________

         c            character device file
         b            block device file    
         n            network special file
         p            named pipe special file
         o            other special file
         s            socket special file
        
The Pascal Workstation user should not try to use or manipulate files
of these types.

Troubleshooting Tips
____________________

Following are some tips about what could be wrong if you are having
trouble with your system. If this doesn't help you solve your problem
see Appendix B, "Troublrshooting Your SRM/UX System", of the System
Administrator's Guide.

Server Side 
___________

If you cannot establish contact with the server, check with the
SRM/UX system administrator to make sure that the folowing steps have
been carried out :

 *  The SRM/UX server software (HP Part No. E2085A) must be present
    on the server

 *  The hardware (LAN or SRM cable, IO cards) must be properly
    installed

 *  A properly configured srmdconf file must be in place 

 *  All the drivers for the peripherals to be employed must
    be present in the kernel

 *  If using the SRM cable, the latest SRM driver needs to be included
    in the system kernel. This requires the kernel be rebuilt
    and the server system rebooted.

 *  The SRM/UX server process, /etc/srmd, must be running

 *  The file /etc/services must contain an entry for lansrm

 *  If booting over the LAN wire is desired, a proper version (66.35 or
    later) of the remote boot daemon /etc/rbootd, must be in place
    and running

 *  A properly configured /etc/boottab file must be in place

 *  The directory structure for each clients system directory and
    the generic SYSTEMS dirctory must be in place

Proper installation of the system hardware and software is described in
Chapters 3 and 4 of the System Administrator's manual.

Client Side
___________

Following are some symptoms of incorrect behavior and some hints about
where to look for the source of trouble.

Symptom : The Boot ROM doesn't display any bootable systems on the
          SRM/UX server.

Possible Problems :

          * Is the server process (srmd) running on the server ?

            From the server itself the Hp-ux command ps -ef will
            show all the running processes. /etc/srmd should be
            one of the processes displayed.

          * If running over the LAN cable, does the client have the
            correct Boot ROM for booting over the LAN cable ?

            Only series 300 machines with Boot ROM versions B and
            later may boot over the LAN cable

          * If running over the LAN cable, is /etc/rbootd, the remote
            boot daemon, running ?

            From the server itself the Hp-ux command ps -ef will
            show all the running processes. /etc/rbootd should be
            one of the processes displayed.

          * If running over the LAN cable, is /etc/boottab properly
            configured ?

            There should be an entry in the paws-srm line for the
            particular Pascal system you wish to boot. See the 
            server manual for a description of a correctly formatted
            /etc/boottab file.

          * Is this client configured correctly on the server (i.e.
            is there an entry in /etc/srmdconf for this client
            with correct information) ?

            Print out ( or have your SRM/UX administrator print out)
            a copy of the file /etc/srmdconf and check the information
            in the client line corresponding to your workstation
            for correctness.

          * Are there any SYSTEM files in the directory /SYSTEMS
            (relative to volume 8) ?

            Just list the files in this directory from the server
            or from another client and make sure the Pascal SYSTEM
            file (e.g. SYSTEM_P) is present in this directory.

          * Are there any hardware problems ?

            Chapter 3 of the SRM/UX System Administrator describes how
            to properly set the switches on LAN and SRM cards for use
            with the SRM/UX server and how to properly terminate LAN
            and SRM cables.



Symptom : The Boot ROM displays what appears to be a bootable system,
          but when trying to boot this system the workstation does
          not complete it's initialization and come up properly.

Possible Problems :

          * Is the server process (srmd) running on the server ?

            From the server itself the Hp-ux command ps -ef will
            show all the running processes. /etc/srmd should be
            one of the processes displayed. 

          * Is this client configured correctly on the server (i.e.
            is there an entry in /etc/srmdconf for this client
            with correct information) ?

            Print out (or have your SRM/UX administrator print out)
            a copy of the file /etc/srmdconf and check the information
            in the client line corresponding to your workstation
            for correctness.

          * Is some other computer using your workstations internet
            address ?

            Check the file /etc/hosts on the server workstation to
            make sure that your IP address is not being used by
            another workstation. Also check that your IP address is
            not being used by a different workstation on a different
            SRM/UX server on the same local subnet as your own
            workstation and server.
            

          * Are the boot extension files present in the proper
            directory ?

            Check to make sure that the files INITLIB, STARTUP, and
            TABLE are present in the clients system directory
            (/WORKSTATIONS/SYSTEMnn or /WORKSTATIONS/SYSTEMnnnnnn
            relative to the root of volume 8) or in the generic
            directory /WORKSTATIONS/SYSTEM (relative to the root of
            volume 8).

          * Is the last thing displayed on the CRT the copyright
            message ?

            You probably have the incorrect CRT drivers in your INITLIB
            for the display you are using. The INITLIB file for the
            series 300 workstations is from the BOOT2: disc while
            the correct INITLIB file for the series 200 workstations
            is from the BOOT: disc.

          * Are volumes #5 and #45 undefined after booting completes ?

            Make sure modifications to CTABLE.TEXT required to establish
            contact with the server initially are incorporated into
            the TABLE program used when booting. Also make sure that
            additional modifications to the TABLE program do not
            disable SRM/UX access to units #5 and #45.

            Also make sure that the necessary drivers for SRM/UX are
            present in INITLIB. Use the Librarian to verify that the
            DATA_COMM and SRM modules (if running over the SRM cable)
            or the IOMPX, LANDVR and SRM modules (if running over the
            LAN cable) are present in your INITLIB file.

                        

More Helpful hints for Pascal Workstation with SRM/UX
_____________________________________________________

1.) Error: IORESULT was 57.

    This message indicates that the Workstation asked the server to
    perform a link across physical mount points in the native Hp-ux
    file system of the server.
    
    If you get this error message when using the dup-link command
    of the FILER, it means you are attempting to perform an illegal
    link.
    
    If you get this error message when you using a Pascal Workstation
    subsystem (e.g. COMPILER, FILER, ASSEMBLER, etc.) it means that your
    SRM/UX file system has not been set up properly by the SRM/UX system
    administrator. The current working directory is not located on the
    same physical device as the TEMP directory for the volume which
    contains the current working directory as specified in the file
    /etc/srmdconf.
    
    This problem will not occur if volumes specified in /etc/srmdconf
    do not span more than one physical device (i.e. disk) and if the TEMP
    directory for that volume is located on that same disk.
       
