NS3000/iX Error Messages Reference Manual (36923-90041)

Chapter 9 97
Remote Process Management Error Messages
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.
MESSAGE: REMOTE PROCESS LIMIT.
9 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.
MESSAGE: REMOTE MEMEORY LIMIT.
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.