Code | Meaning | Action |
|
|
|
22 | The child program terminated | Check the child program. |
| abnormally. Either a memory |
|
| protect error occurred or the |
|
| child was accidentally |
|
| terminated by someone (by RTE |
|
| OF command). |
|
|
|
|
23 | Unsupported RPM call. | This RPM call is not used on |
|
| NSARPA RPM. |
|
|
|
302 | Table is full. There is no free | Wait until a parent program |
| entry in the local RPM Parent | completes, and RPM |
| Process Table to accommodate | deallocates resources. Try |
| this RPMCreate call. | again later. |
|
|
|
304 | RPM attach failed. The RPM | Refer to the •Multiuser Log |
| Monitor failed to attach to either | Message Codes" subsection in |
| the parent or child session. A | •Logging Codes and Messages" |
| Multiuser error is logged. | section. |
|
|
|
305 | Schedule error. The RPM | The xx and yy fields of the log |
| Monitor cannot schedule the | header record contain the |
| child because the EXEC call | values of the A and B registers. |
| failed. The values of the A and | Refer to the RTE manuals for an |
| B registers which were returned | explanation of the EXEC error. |
| by the EXEC call are logged in |
|
| the log file. |
|
|
|
|
306 | Cannot find child program's ID | Make sure that the child |
| segment. The child program | program exists and has an ID |
| does not exist anymore. This | segment. Then try again. |
| can occur if the RTE OF |
|
| command is used on the child |
|
| program after it is RPed but |
|
| before RPM can schedule it. |
|
|
|
|
307 | Logoff failed. The RPM Monitor | Refer to the •Multiuser Log |
| failed to logoff the child session. | Message Codes" subsection in |
| A Multiuser error is logged. | the •Logging Codes and |
|
| Messages" section. |
|
|
|
308 | Group 3 option error. An error | Check the Group 3 option in the |
| occurred when executing a | RPMCreate call. |
| Group 3 option in an |
|
| RPMCreate call. |
|
|
|
|
230 Numeric Error Codes