HP 3000 Manuals HP 3000 Manuals
Chapter 9 Remote Process Management Error Messages
RPM errors are (32-bit) integers that are returned in the result
parameter of the intrinsics RPMCREATE, RPMKILL, RPMCONTROL, and
RPMGETSTRING when the intrinsic execution fails. (A result of 0
indicates that the intrinsic succeeded.) There are two ranges of RPM
errors returned by the HP 3000 implementation of RPM. The first range
(0-99) includes generic RPM errors. The second range (100-199) includes
errors specific to the HP 3000 implementation.
0 MESSAGE NO ERROR.
CAUSE Successful execution.
ACTION None.
1 MESSAGE NETWORK DOWN.
CAUSE The transport is not available for use by RPM.
ACTION Wait until the transport is available.
2 MESSAGE ILLEGAL PROGRAM NAME LENGTH.
CAUSE The program namelen parameter in an RPMCREATE
call is greater than the allowed maximum of 256
(characters).
ACTION Shorten the program name.
3 MESSAGE ILLEGAL FLAG.
CAUSE An RPMCREATE call includes a flags parameter
with one or more undefined flag bits set.
ACTION Correct the flags parameter. The defined flags
are:
bit 0 No dsline (3000-specific)
bit 1 Wait until son dies
(3000-specific)
bit 31 Dependent
4 MESSAGE ILLEGAL OPTION.
CAUSE An RPMCREATE call includes an opt parameter with
one or more invalid options.
ACTION Correct the opt parameter. The valid options
are:
20000 RPM string
22001-22012, 22100 MPE options
5 MESSAGE ILLEGAL OPTION FORMAT.
CAUSE The opt parameter in an RPMCREATE call is not
formatted correctly.
ACTION Correct the opt format; use the INITOPT and
ADDOPT intrinsics to format the opt array.
6 MESSAGE INVALID LOGIN.
CAUSE This may be caused by several conditions
relating to the login (Env) and password
parameters of RPMCREATE:
* The login parameter is syntactically
incorrect for the remote machine. For
the HP 3000, the logon syntax is:
=
user[/userpass].acct[/acctpass],group[grouppass]
* The password parameter is syntactically
incorrect for the remote machine. For
the HP 3000, the password syntax is:
= [userpass][acctpass][,grouppass]
* The login and password are syntactically
correct, but the login (on the HP 3000,
user, group, or account) is not defined
on the remote machine.
* The login and password parameters do not
supply required passwords for the login.
* The login and password parameters were
correct, but the logon failed for some
reason (on the HP 3000: jobfence too
high, session limit exceeded).
ACTION Correct the login and password parameters, if
necessary. If login and password are correct,
determine the reason for the remote logon
failure: possibly wait until the remote logon
resources are available.
7 MESSAGE INVALID PROGRAM NAME.
CAUSE The program indicated by the progname (and
namelen) parameters of an RPMCREATE was not
found on the remote computer.
ACTION Correct the progname (and namelen) parameters,
if necessary. Make sure the program file exists
on the remote node. Note that, if the program
name is not fully qualified, the logon group and
account (determined by login) will be used.
8 MESSAGE INVALID PROGRAM DESCRIPTOR.
CAUSE The program descriptor (pd) parameter of an
RPMKILL contained a program descriptor that was
not defined on the remote node. There are two
cases in which this can happen:
1. The (pd) value was not generated by PRM
on the remote node. This would happen if
the program descriptor were incorrect or
corrupted, or if the RPMCREATE that was
supposed to return the descriptor failed.
2. The (pd) value was generated for a
program on the remote node, but the
program terminated itself, or was
terminated by an abort or an RPMKILL. In
this case the program's descriptor is
deleted when the program terminates, and
a later RPMKILL receives the Invalid
Program Descriptor error.
ACTION Depending on the cause:
1. Correct the program descriptor. Do not
issue an RPMKILL when the RPMCREATE
failed.
2. Do not issue an RPMKILL if the created
process is supposed to terminate itself.
Do not issue more than one RPMKILL for
the same process.
9 MESSAGE REMOTE PROCESS LIMIT.
CAUSE A resource needed to create the process is not
available. On a remote HP 3000 (or the local HP
3000 if the created process is local), this can
include:
* Process Control Block entry for created
process
* stack space for created process
* RPM Table entry for created process
* pseudo terminal for created session
On the local HP 3000, some resources needed for
a process creating a dependent process may not
be available:
* RPM Table entry for creator process
* AFT entry in creator process' stack
ACTION Wait for the resource(s) to become available.
If the Remote Process Limit error occurs often,
resources like the number of PCB and DST entries
or number of configured pseudo terminals may
have to be increased.
10 MESSAGE REMOTE MEMORY LIMIT.
CAUSE Memory was not available for storage of data.
The possible reasons for this include:
* RPM String could not be stored
* buffers in the RPM server could not be
allocated
ACTION Wait until the resource(s) become available.
11 MESSAGE PROGRAM ACCESS ERROR.
CAUSE The program to be created by an RPMCREATE could
not be accessed. This may be due to one of the
following reasons:
1. The program file is secured against
access from the login user and account.
2. The program file has a lockword that was
not specified in progname.
3. The program name in progname is not
syntactically correct.
ACTION Depending on the cause:
1. Change the program file's security or the
login user and account to allow Execute
access to the program.
2. Insert the program file's lockword into
the progname parameter. The syntax is:
progname/lockword[.acct][,group]]
3. Correct the syntax of the progname.
12 MESSAGE UNKNOWN ERROR.
CAUSE Internal software error. For example, the RPM
Table (which is always supposed to be there) was
not found.
ACTION See "Submitting an SR" in appendix A of this
manual.
13 MESSAGE PROTOCOL ERROR.
CAUSE An RPM message is incorrect or has been
corrupted.
ACTION Turn on tracing for RPM and see "Submitting an
SR" in appendix A of this manual.
14 MESSAGE NETWORK ERROR.
CAUSE An error occurred in using a transport
connection to send or receive an RPM message.
The transport error will be logged by Network
Management logging, log class 6, subclass 5.
ACTION Examine the log file and see "Submitting an SR"
in appendix A of this manual.
15 MESSAGE INCOMPATIBLE VERSIONS.
CAUSE The versions of the RPM software on the local
and remote computers are incompatible.
ACTION Check the versions of the RPM software on the
local and remote computers. On an HP 3000, the
RPM version can be obtained by running
NMMAINT.PUB.SYS, or by NSCONTROL VERSION=MOD.
The RPM version is listed as ASRPMVERS. Update
the software on the local or remote nodes to
compatible versions.
16 MESSAGE UNSUPPORTED OPTION.
CAUSE A legal option specified in the opt parameter of
the RPMCREATE is not supported by the remote RPM
software.
ACTION Modify the option, or update the remote RPM
software to a version that supports the option.
17 MESSAGE RPMCREATE LENGTH ERROR.
CAUSE An RPMCREATE resulted in a message that could
not be handled by the remote node RPM software.
ACTION Decrease the size of the RPMCREATE message by
shortening the program name or the lengths of
options.
18 MESSAGE ILLEGAL OPTION PARAMETER.
CAUSE The value of an option in the opt parameter of
an RPMCREATE was invalid.
ACTION Check the options for validity. In some cases
(like the Initial Stack Size option), the option
value might exceed maximum configured limits for
the remote system.
19 MESSAGE INVALID NODE NAME.
CAUSE The node name specified by the location and
loclen parameters of an RPMCREATE call is not a
valid node. It may be syntactically incorrect,
or it may not be defined in the network.
ACTION Correct the location and loclen parameters.
20 MESSAGE NO RPM STRING.
CAUSE A program called the RPMGETSTRING intrinsic, but
there was no RPM string to be passed to the
program. This could be caused by one of the
following:
1. The program was not created by an
RPMCREATE (but by a RUN, CREATE, or
CREATEPROCESS).
2. The creating process did not pass an RPM
string in the opt parameter in its
RPMCREATE call.
3. The created process has called
RPMGETSTRING more times than the number
of RPM strings passed by the creating
process.
ACTION Either add the RPM string to the creating
process's RPMCREATE call, or remove the
RPMGETSTRING from the created program.
21 MESSAGE RPM STRING LENGTH
CAUSE In a call to RPMGetString, the parameter
specifying the maximum string length was less
than zero.
ACTION Check that the parameter specifying string
length is set to a positive integer in the
RPMGetString intrinsic. If the string length is
positive, and you are getting the error anyway,
submit an SR. See "Submitting an SR" in appendix
A of this manual.
22 MESSAGE REMOTE SON ABORTED.
CAUSE The remote process aborted abnormally.
ACTION Check the remote program to ascertain what
caused the premature termination.
100 MESSAGE INSUFFICIENT STACK SPACE.
CAUSE The program calling RPMCREATE, RPMKILL,
RPMCONTROL, or RPMGETSTRING could not expand its
stack to accommodate the requirements of the RPM
software.
ACTION Increase the stack size and/or maxdata of the
program and rerun.
101 MESSAGE NOT AT THE STACK.
CAUSE RPMCREATE, RPMKILL, or RPMGETSTRING was called
when the DB register was not at the process'
stack ("split- stack mode").
ACTION Switch the DB register to the process stack
before calling any RPM intrinsic.
102 MESSAGE PARAMETER OUT OF BOUNDS.
CAUSE A parameter for an RPMCREATE, RPMKILL,
RPMCONTROL, or RPMGETSTRING call was not fully
within the stack of the calling process.
ACTION Check each parameter of the call to make sure it
is between the DL and S registers. For arrays,
also check that the end of the array (beginning
+ length) is also between DL and S.
103 MESSAGE PROGRAM DOES NOT HAVE PH CAPABILITY.
CAUSE A program without PH (Process Handling)
capability called RPMCREATE or RPMKILL.
ACTION PREP the program with CAP=PH...and rerun. (Only
users with PH capability can PREP a program with
CAP=PH.)
104 MESSAGE REQUIRED PARAMETER OMITTED.
CAUSE A required parameter for RPMCREATE or RPMKILL
has been omitted. The required parameters are:
RPMCREATE progname, namelen
RPMKILL pd
ACTION Add the required parameter to the call.
106 MESSAGE RPM OR PTOP PROCESS AT location
CAUSE An RPM- or PTOP-created process already exists
in the remote session specified by the location
parameter. Because of the design of the RPM and
PTOP services, only one RPM or PTOP process can
exist in a remote session.
ACTION Terminate the first RPM or PTOP process, or
change the location to a different remote
session. By means of the environment facility
of Network Services, it is possible to have more
than one remote session on the same remote node.
Use DSLINE commands to set up the environments;
for example:
DSLINE S1=NODE
DSLINE S2=NODE
Then use the different environment IDs (S1 and
S2) in the location parameter of the
RPMCREATE(s) (and of a POPEN).
107 MESSAGE LOGON TIME OUT.
CAUSE The logon of the remote session for an RPMCREATE
did not complete in a set amount of time. This
time can be set by the Logon TimeOut option in
an RPMCREATE; if the Logon TimeOut is not set, a
default of 1 hour (3600.0 seconds) is used.
ACTION Increase the timeout with the Logon TimeOut
option; the timeout depends on factors like the
load on the remote system and set-up and
execution time of UDCs for the remote session.
It is possible to have a logon UDC that never
completes (for example, one that runs a program
that does not terminate), so in this case no
logon timeout is sufficient.
108 MESSAGE LOCAL RPM SERVICE NOT STARTED.
CAUSE The local RPM service (RPML) has not been
started, or has been stopped and aborted.
ACTION Start the local RPM service with NSCONTROL
START=RPML or NSCONTROL START. (Only users with
NM capability can use the NSCONTROL command.)
111 MESSAGE RPMDAD CREATE ERROR.
CAUSE The remote node was unable to create the RPMDAD
process.
ACTION Check to verify that RPMDAD.PUB.SYS exists on
the remote node. Also check that the process
limit has not been exceeded on the remote node.
The log file (NMLGxxxx.PUB.SYS) may contain
additional information.
112 MESSAGE RPMDAD DEAD ERROR.
CAUSE RPMDAD is terminating and exiting the session
because the session has been aborted or because
all sons created by RPM have terminated.
ACTION Try again. A new RPMDAD and a new session are
created at the next RPMCREATE request.
113 MESSAGE BAD RPMCONTROL STATE.
CAUSE RPMCONTROL was unable to suspend the remote
process. A system process may have impeded the
remote process, or the remote process may be
waiting for a system resource.
ACTION Call RPMCONTROL again with the suspend option,
or attempt to use another method of
synchronization such as NetIPC.
114 MESSAGE SWITCH FAILURE.
CAUSE RPM was unable to call a native mode procedure.
ACTION See "Submitting an SR" in appendix A of this
manual. The log file (NMLGxxxx.PUB.SYS) may
contain additional information.
115 MESSAGE ADOPT FAILURE
CAUSE RPMDAD was unable to enter the remote session
because the remote session was being aborted.
ACTION Try again. Make sure the session is not aborted
before the RPM son is created. The log file
(NMLGxxxx.PUB.SYS) may contain additional
information.