 |
» |
|
|
|
|  | |
- 10
- MESSAGE
The code segment number is invalid.
- CAUSE
The caller passed in a code segment which is invalid for the process whose PIN was passed in, or the code segment is unassigned.
- ACTION
None.
- 30
- MESSAGE
The data segment number is invalid.
- CAUSE
The caller passed in an invalid or an unassigned data segment number.
- ACTION
None.
- 60
- MESSAGE
FREEZE returned a bad status.
- CAUSE
The memory manager failed to freeze a compatibility mode code or data segment into memory.
- ACTION
Examine the process error stack to determine what may have caused the problem.
- 65
- MESSAGE
UNFREEZE returned a bad status.
- CAUSE
The memory manager failed to unfreeze a compatibility mode code or data segment into memory.
- ACTION
Examine the process error stack to determine what may have caused the problem.
- 160
- MESSAGE
SWITCH_TO_CM returned a bad status.
- CAUSE
Corruption of an operating system data structure or operating system code caused SWITCH_TO_CM to fail.
- ACTION
Examine the process error stack to determine what may have caused the problem.
- 301
- MESSAGE
The logical device parameter is not a real device.
- CAUSE
An attempt was made to place a non-existent device or a spooler virtual device into diagnostic mode.
- ACTION
None.
- 302
- MESSAGE
The device is currently not in diagnostic mode.
- CAUSE
An attempt was made to remove a device not owned by the diagnostic system from the diagnostic mode.
- ACTION
None.
- 304
- MESSAGE
The device is already in diagnostic mode.
- CAUSE
An attempt was made to place a device which was already owned by the diagnostic system into the diagnostic mode.
- ACTION
None.
- 305
- MESSAGE
The device is currently in use.
- CAUSE
An attempt was made to place a device currently being accessed by a user into the diagnostic mode.
- ACTION
Try again once the user is no longer accessing the device. The SHOWDEV command can be used to determine the current owner.
- 309
- MESSAGE
The spooler for the device could not be stopped.
- CAUSE
While attempting to place a device into the diagnostic mode, the system could not stop the spooler active on the device.
- ACTION
Use the STOPSPOOL command to stop the spooler. If sucessful, attemp the diagnostic again.
- 311
- MESSAGE
The spooler for the device could not be restarted.
- CAUSE
While removing the device from the diagnostic mode, the system could not restart a spooler for the device.
- ACTION
If desired, use the STARTSPOOL command on the console to start a spooler for the device.
- 312
- MESSAGE
The spooler for the device could not be suspended.
- CAUSE
While attempting to place a device into diagnostic mode, the system could not suspend the currently active spoolfile.
- ACTION
Try using the SUSPENDSPOOL command on the console to suspend the currently active spoolfile.
- 320
- MESSAGE
The logical console cannot be placed in diagnostic mode.
- CAUSE
An attempt was made to place the logical console into diagnostic mode.
- ACTION
Move the logical console to another terminal using the CONSOLE command.
- 321
- MESSAGE
Disks cannot be placed in diagnostic mode.
- CAUSE
An attempt was made to place a disk into diagnostic mode.
- ACTION
None.
- 2550
- MESSAGE
GETSIR returned a bad status to the fast switch stub.
- CAUSE
Corruption of an operating system data structure or operating system code caused GETSIR to fail.
- ACTION
Perform a system dump. Reboot the system using START.
- 2551
- MESSAGE
RELSIR returned a bad status to the fast switch stub.
- CAUSE
Corruption of an operating system data structure or operating system code caused RELSIR to fail.
- ACTION
Perform a system dump. Reboot the system using START.
|
