Code

Meaning

Action

 

 

 

9

Remote process limit exceeded.

(1) Make sure that RPM software

 

One of the following problems

installed at the child's and

 

has occurred: (1) The remote

parent's nodes is compatible.

 

node cannot handle RPM

(2) Check the FMP error and the

 

messages greater than 1024

option in RPMCreate. (3) Wait

 

bytes, and it received a

for resources to be deallocated

 

message that is greater than

and try the RPM call later.

 

1024 bytes. (2) RPM at the

 

 

child's node encountered an

 

 

FMP error while either executing

 

 

the FmpRunProgram option

 

 

(23110) or the Restore Program

 

 

option (23010) in RPMCreate.

 

 

The FMP error is contained in

 

 

the xx field of the log record

 

 

header. (3) Too many child

 

 

programs are executing at the

 

 

child's node. RPM cannot

 

 

allocate another child program.

 

 

 

 

10

Insufficient memory to create a

(1) Increase DSAM on the

 

child program. (1) There is not

child's node. (2) Increase the

 

enough DSAM to create a new

number of ID segments on the

 

child program. (2) There are no

child's node. Or wait until ID

 

more ID segments for another

segments are released and try

 

program to run. (3) The RPM

the RPM call later. (3) Wait until

 

child table is full and another

child programs have terminated

 

child program cannot be

and try the RPM call later.

 

created.

 

 

 

 

11

Security violation or device error.

This error message is not used

 

 

in NSARPA RPM.

 

 

 

12

Unknown internal error. An

Check the log file for other

 

unexpected error was returned

errors, possibly from NetIPC,

 

to RPM from another internal

and refer to the documentation

 

NSARPA routine.

on those errors.

 

 

 

13

Bad RPM packet structure.

The structure of the RPM

 

RPM received an internal packet

message packet is incorrect.

 

which is not formatted according

Retry the call. If the problem

 

to RPM protocol or the length of

persists, call your HP

 

the packet is too long.

representative.

 

 

 

14

Network transport error. RPM

Check the log file for NetIPC

 

received a NetIPC error when it

errors. Refer to the NetIPC error

 

tried to send or receive an RPM

codes in this section for more

 

packet.

information.

 

 

 

15

Incompatible version number ID.

Make sure that the RPM

 

The RPM version number in the

versions are compatible. If not,

 

RPM message packet is not the

update the older system.

 

same as the version number for

 

 

RPM installed at the local node.

 

 

 

 

16

Unsupported RPM option or

Correct the option or request

 

request. The option specified in

code.

 

the RPMCreate call is not

 

 

supported, or the request

 

 

specified in the RPMControl

 

 

call is not supported.

 

 

 

 

228 Numeric Error Codes