Chapter 9 Remote Process Management Error Messages

CAUSE: Successful execution.

ACTION: None.

CAUSE: The transport is not available for use by RPM.

ACTION: Wait until the transport is available.

CAUSE: The program namelen parameter in an RPMCREATE call is greater than the allowed maximum of 256 (characters).

ACTION: Shorten the program name.

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:

CAUSE: An RPMCREATE call includes an opt parameter with one or more invalid options.

ACTION: Correct the opt parameter. The valid options are:

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.

CAUSE: This may be caused by several conditions relating to the login (Env) and password parameters of RPMCREATE:

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.

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.

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:

ACTION: Depending on the cause:

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:

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.

CAUSE: Memory was not available for storage of data. The possible reasons for this include:

ACTION: Wait until the resource(s) become available.

CAUSE: The program to be created by an RPMCREATE could not be accessed. This may be due to one of the following reasons:

ACTION: Depending on the cause:

CAUSE: Internal software error. For example, the RPM Table (which is always supposed to be there) was not found.

ACTION: See Appendix A “Submitting an SR ” of this manual.

CAUSE: An RPM message is incorrect or has been corrupted.

ACTION: Turn on tracing for RPM and see Appendix A “Submitting an SR ” of this manual.

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 an SR ” of this manual.

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.

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.

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.

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.

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.

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:

ACTION: Either add the RPM string to the creating process's RPMCREATE call, or remove the RPMGETSTRING from the created program.

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 Appendix A “Submitting an SR ” in this manual.

CAUSE: The remote process aborted abnormally.

ACTION: Check the remote program to ascertain what caused the premature termination.

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.

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.

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.

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.)

CAUSE: A required parameter for RPMCREATE or RPMKILL has been omitted. The required parameters are:

ACTION: Add the required parameter to the call.

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 RPMCREATEs and of a POPEN.

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.

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.

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.

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.

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.

CAUSE: RPM was unable to call a native mode procedure.

ACTION: See Appendix A “Submitting an SR ” in this manual. The log file (NMLGxxxx.PUB.SYS) may contain additional information.

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.