LogMessage | Meaning |
| Action |
|
|
|
|
18009 FMPerror xx xx | Remote process limit exceeded. | 1. | Make sure that RPM software |
| One of the following problems |
| installed at the child's and |
| has occurred: |
| parent's nodes is compatible. |
| 1. The remote node cannot | 2. | Check the FMP error and the |
| handle RPM messages |
| option in RPMCreate. |
| greater than 1024 bytes, and | 3. | Wait for resources to be |
| it received a message that is |
| deallocated and try the RPM |
| greater than 1024 bytes. |
| call later. |
| 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 |
|
|
| FMPerror field of the log |
|
|
| record header. |
|
|
| 3. Too many child programs are |
|
|
| executing at the child's node. |
|
|
| RPM cannot allocate another |
|
|
| child program. |
|
|
|
|
|
|
18010 xx xx xx | Insufficient memory to create a | 1. | Increase DSAM on the child's |
| child program. |
| node. |
| 1. There is not enough DSAM | 2. | Increase the number of ID |
| to create a new child |
| segments on the child's |
| program. |
| node. Or wait until ID |
| 2. There are no more ID |
| segments are released and |
|
| try the RPM call later. | |
| segments for another |
| |
| 3. | Wait until child programs | |
| program to run. | ||
| 3. The RPM child table is full |
| have terminated and try the |
|
| RPM call later. | |
| and another child program |
| |
|
|
| |
| cannot be created. |
|
|
|
|
| |
18011 xx xx xx | Security violation or device error. | This error message is not used | |
|
| in NSARPA/1000 RPM. | |
|
|
| |
18012 xx xx xx | Unknown internal error. An | Check the log file for other | |
| unexpected error was returned | errors, possibly from IPC, and | |
| to RPM from another internal | refer to the documentation on | |
| NSARPA routine. | those errors. | |
|
|
| |
18013 xx xx xx | Bad RPM packet structure. | The structure of the RPM | |
| RPM received an internal packet | message packet is incorrect. | |
| which is not formatted according | This error requires HP | |
| to RPM protocol or the length of | notification. | |
| the packet is too long. |
|
|
|
|
| |
18014 ipcerror xx xx | Network transport error. RPM | Refer to the NetIPC error codes | |
| received a NetIPC error | in the •Numeric Error Codes" | |
| (ipcerror) when it tried to | section of this manual for more | |
| send or receive an RPM packet. | information. | |
|
|
| |
18015 vn xx xx | 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. |
|
|
|
|
|
|
634 Logging Codes and Messages