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 e3000 implementation of RPM. The first range (0-99) includes
generic RPM errors. The second range (100-199) includes errors specific to the
HP e3000 implementation.
Level: 1
CAUSE: The transport is not available for use by RPM.
ACTION: Wait until the transport is available.
MESSAGE: ILLEGAL PROGRAM NAME LENGTH.
Level: 2
CAUSE: The program namelen parameter in an
RPMCREATE call is greater than the allowed maximum of 256
(characters).
ACTION: Shorten the program name.
MESSAGE: ILLEGAL FLAG.
Level: 3
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
MESSAGE: ILLEGAL OPTION.
Level: 4
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
MESSAGE: ILLEGAL OPTION FORMAT.
Level: 5
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.
MESSAGE: INVALID LOGIN.
Level: 6
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 e3000, the logon syntax is:
user[/userpass].acct[/acctpass],group[grouppass]
The password parameter is syntactically incorrect for the remote
machine. For the HP e3000, the password syntax is:
[userpass][acctpass][,grouppass]
The login and password are syntactically correct, but the login
(on the HP e3000, 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 e3000: 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.
MESSAGE: ILLEGAL PROGRAM NAME.
Level: 7
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.
MESSAGE: INVALID PROGRAM DESCRIPTOR.
Level: 8
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:
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.
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:
Correct the program descriptor. Do not issue an RPMKILL
when the RPMCREATE failed.
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.
MESSAGE: REMOTE PROCESS LIMIT.
Level: 9
CAUSE: A resource needed to create the process is not available.
On a remote HP e3000 (or the local HP e3000 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 e3000, 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.
MESSAGE: REMOTE MEMEORY LIMIT.
Level: 10
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.
MESSAGE: PROGRAM ACCESS ERROR.
Level: 11
CAUSE: The program to be created by an RPMCREATE could
not be accessed. This may be due to one of the following reasons:
The program file is secured against access from the login user and
account.
The program file has a lockword that was not specified in
progname.
The program name in progname is not syntactically correct.
ACTION: Depending on the cause:
Change the program file's security or the login user and account
to allow Execute access to the program.
Insert the program file's lockword into the progname parameter.
The syntax is:
progname/lockword[.acct][,group]]
Correct the syntax of the progname.
MESSAGE: UNKNOWN ERROR.
Level: 12
CAUSE: Internal software error. For example, the RPM
Table (which is always supposed to be there) was not found.
ACTION: See Appendix A "Submitting a CR"
of this manual.
MESSAGE: PROTOCOL ERROR.
Level: 13
CAUSE: An RPM message is incorrect or has been corrupted.
ACTION: Turn on tracing for RPM and see
Appendix A "Submitting a CR" of this
manual.
MESSAGE: NETWORK ERROR.
Level: 14
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 Appendix A
"Submitting a CR" of this manual.
MESSAGE: INCOMPATIBLE VERSIONS.
Level: 15
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 e3000, 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.
MESSAGE: UNSUPPORTED OPTION.
Level: 16
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.
MESSAGE: RPMCREATE LENGTH ERROR.
Level: 17
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.
MESSAGE: ILLEGAL OPTION ERROR.
Level: 18
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.
MESSAGE: INVALID NODE NAME.
Level: 19
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.
MESSAGE: NO RPM STRING.
Level: 20
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:
The program was not created by an RPMCREATE (but by a
RUN, CREATE, or CREATEPROCESS).
The creating process did not pass an RPM string in the
opt parameter in its RPMCREATE call.
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.
MESSAGE: RPM STRING LENGTH.
Level: 21
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 CR. See
Appendix A "Submitting a CR"
MESSAGE: REMOTE SON ABORTED.
Level: 22
CAUSE: The remote process aborted abnormally.
ACTION: Check the remote program to ascertain what caused
the premature termination.
MESSAGE: INSUFFICIENT STACK SPACE.
Level: 100
CAUSE: The program calling RPMCREATED, 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.
MESSAGE: NOT AT THE STACK.
Level: 101
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.
MESSAGE: PARAMETER OUT OF BOUNDS.
Level: 102
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 DS and S.
MESSAGE: PROGRAM DOES NOT HAVE PH CAPABILITY.
Level: 103
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.)
MESSAGE: REQUIRED PARAMETER OMITTED.
Level: 104
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.
MESSAGE: RPM OR PTOP PROCESS AT LOCATION.
Level: 106
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=NODEDSLINE S2=NODE
Then use the different environment IDs (S1 and S2) in the location
parameter of the RPMCREATEs and of a
POPEN.
MESSAGE: LOGON TIME OUT.
Level: 107
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 hours (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.
MESSAGE: LOCAL RPM SERVICE NOT STARTED.
Level: 108
CAUSE: The local RPM service (RPML) has not been started,
or has been stopped and aborted.
ACTION: Start the RPM service with NSCONTROL START=RPML or
NSCONTROL START. (Only users with NM capability can use the
NSCONTROL command.
MESSAGE: RPMDAD CREATE ERROR.
Level: 111
CAUSE: The remote node was unable to create the RPMDAD
process.
ACTION: Check to verify that RPMDAT.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.
MESSAGE: RPMDAD DEAD ERROR.
Level: 112
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.
MESSAGE: BAD RPMCONTROL STATE.
Level: 113
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.
MESSAGE: SWITCH FAILURE.
Level: 114
CAUSE: RPM was unable to call a native mode procedure.
ACTION: See Appendix A "Submitting a CR"
in this manual. The log file (NMLGxxxx.PUB.SYS) may contain
additional information.
MESSAGE: ADOPT FAILURE.
Level: 114
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.
Chapter 8 Remote File Access Error Messages
Chapter 10 Network Transport Protocol (PMERR) Error Messages
Complete PDF