Reason:
Confirmation; command has been successfully queued for execution. Processing continues.
Action:
None.
Reason:
A SHUTDOWN command has been successfully processed, and the system-termination sequence is in progress. Processing continues until the network interface and all opened files have been closed, at which time CA Spool terminates.
Action:
None.
Reason:
A start-net, stop-net, or reset-net command has been entered but is rejected because no network nodes have been defined to CA Spool. The command is discarded, and processing continues.
Action:
None.
Reason:
A start-net, stop-net, or reset-net command has been rejected because the network interface is busy processing another start, stop, or reset command. The command is discarded, and processing continues.
Action:
Enter the command again later.
Reason:
A start-net command has been rejected because the network interface is already started. The command is discarded, and processing continues.
Action:
None.
Reason:
A stop-net command has been rejected because the network interface is already stopped. The command is discarded, and processing continues.
Action:
None.
Reason:
A stop-net command has been rejected because the network interface already is in the process of being stopped. The command is discarded, and processing continues.
Action:
None.
Reason:
A reset-net command has been rejected because the network interface is already stopped. The command is discarded, and processing continues.
Action:
None.
Reason:
An explicit checkpoint request (CHKPT command) has been successfully completed. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display (DS) command. x.x specifies the current CA Spool release number and yyyy the current CA Spool service level. Processing continues.
Action:
None.
Reason:
A command has been entered which specified a file destination which was neither defined in CA Spool or JES2/JES3. The command is discarded, and processing continues.
Action:
Re-enter the command with a valid node name.
Reason:
A network command has been entered which specifies an invalid node name. The command is discarded, and processing continues.
Action:
Re-enter the command with a valid node name.
Reason:
A file-control command has been entered which contains an invalid file sequence number or an invalid file sequence range. Processing continues.
Action:
Re-enter the command with a valid file sequence number or file sequence range.
Reason:
A file-control command has been entered which specifies a non-existing file. Processing continues.
Action:
Re-enter the command with a valid file sequence number.
Reason:
A close file command has been entered which specifies a file which was not in the temporarily closed state. Processing continues.
Action:
Re-enter the command with a valid file sequence number.
Reason:
A close-file command has been successfully completed, and the requested file is now permanently closed. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command. xxxxx specifies the current number of incomplete DASD I/O requests in the system. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command. xxx specifies the current percentage of spool space in use. yyy specifies the highest percentage of spool space in use since last cold start. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status request if the system is in the process of being terminated. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command. xxxxxx specifies the number of files currently in the system, yyyyyy specifies the maximum number of concurrent files allowed and zzzzzz specifies the maximum number of files since the last cold start. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command. xxxxx specifies the current number of active network sessions. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command when the network interface is stopped. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command when the network interface is started, and logon requests can be processed. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command when the network interface is in the process of being stopped. No logon requests can be processed. xxxx is SLOW if a stop-net command or a VTAM Z NET command has been entered. xxxx is FAST if a reset-net or a VTAM Z NET,QUICK command has been entered or if the VTAM system is abending. Processing continues.
Action:
None.
Reason:
A message has been received from the network session xxxxxxxx. Processing continues.
Action:
None.
Reason:
A WRITELOG command has been rejected because the log-writer task is not active. Processing continues.
Action:
If logging is required, then restart the CA Spool system with the LOG option.
This message number represents one of the following messages:
Reason:
This message is displayed in response to a display (DS) command. xxxxxxxxxxxxxxxxx specifies the name of the SAR database and 999999 specifies the number of files currently being processed by the CA View interface. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-active (DA) command. File xxxxxx (with owner name oooooooo and destination name dddddddd) was found to be active in a CA Spool system where:
ss sssss specifies the processing status of the file and is one of the following:
Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-active (DA) command if no files were active in the system. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-node command where:
Specifies the device type of the display node
Specifies the node name
Specifies the status of the network session
Specifies the number of the network group to which this node belongs
Specifies a bit setting such as F8. This bit setting is mapped in DSECT $IQSECPM which resides in the AESFSRC library. The flag byte is SECAUTF and is found at offset x'30' into $IQSECPM. Note that a value of AUTF=F8 is a user without security restrictions; any other value means that this user is restricted in some way by internal or external security.
Specifies whether a release request must be accepted for this node (N if no, D if delayed, or I if immediate).
Processing continues.
Action:
None.
This message number represents one of the following messages:
Reason:
These messages are displayed in response to a display printer node command where:
Specifies the device type
Specifies the node name
Specifies the device status (DRAINED, ACTIVE (FILE xxxxxx), INT REQ, DRAINING,.HALTING, INACTIVE, QUEUED, HALTED, or HALTED (SETUP))
Specifies the number of the network group to which the printer node belongs
Specifies the first four characters of the current form number
Specifies the complete current form number
Specifies the current FCB being simulated
Specifies the output class currently being processed by the printer (Y if automatic file selection mode is on or N if automatic file-selection mode is off)
Specifies Y if the printer operates in automatic purge mode or N if not
Specifies the number of separator pages being produced between files (0, 1, or 2)
Specifies Y if the printer operates in restricted file-selection mode or N if not
Specifies the name of the translate table in use on this printer if any
Specifies the sense code received from the last SIMLOGON request, if any
Specifies the total number of replies for the command causing this message, provided the command has been issued from the MENU system
Specifies the number of output lines/pages multiplied by the number of copies for the current file
Specifies the total number of output lines/pages printed of the current file
Processing continues.
Action:
None.
This message number represents one of the following messages:
Reason:
The status of the file-transfer subtask and the two interfaces ESFTOJES and JESTOESF are defined. If XFERSAPI=THREADS is specified, the current and maximum thread counts are given. Processing continues.
Action:
None.
Reason:
A halt file-transfer-interface command has been rejected because the file-transfer subtask has abended. Processing continues.
Action:
If the file-transfer interface is required, then restart CA Spool. Save the dump output.
Reason:
A halt file-transfer-interface command has been rejected because the interface is already halted. Processing continues.
Action:
None.
Reason:
A halt file-transfer-subtask command has been successfully completed.
Both the ESFTOJES the JESTOESF interface are halted.
Action:
None.
Reason:
A halt-file-interface xxxxxxxx command has been successfully completed. The xxxxxxxx can be either ESFTOJES or JESTOESF. Processing continues.
Action:
None.
Reason:
A start-file-transfer-interface command has been rejected because the file-transfer subtask has abended. Processing continues.
Action:
If the file-transfer interface is required, then restart CA Spool. Save the dump output.
Reason:
A start-file-transfer interface command has been rejected because the interface is already active. Processing continues.
Action:
None.
Reason:
A start-file-transfer subtask command has been successfully completed.
Both ESF-TO-JES interface and JES-TO-ESF interface are started, and processing continues.
Action:
None.
Reason:
A start-file-transfer interface command has been successfully completed. Processing continues.
Action:
None.
This message number represents one of the following messages:
Reason:
This message is displayed in response to a display-file command.
Specifies the total number of file satisfying the display command. This field only appears when the TOTAL operand has been specified on the display command where:
Specifies file sequence number
Specifies file-owner name
Specifies file-destination name
Specifies output class
Specifies form number
Specifies FCB name
Specifies the number of output lines
Specifies the number of copies
Specifies the files output priority
Specifies the system ID of the system on which the file is active or to which it has affinity
Specifies the files status; the file status is one or more of the following characters:
Processing continues.
Action:
None.
Reason:
Message indicates no files were found. Processing continues.
Action:
None.
Reason:
xxxxxx specifies the number of files scheduled for purge processing. Processing continues.
Action:
None.
Reason:
Response to a display-status (DS) command. ACB status is xxxxxx. Processing continues.
Action:
None.
Reason:
File queue elements are displayed in hexadecimal format. Processing continues.
Action:
None.
Reason:
User ID does not have sufficient authorization for the file. Processing continues.
Action:
None.
Reason:
User ID does not have sufficient authorization for the node. Processing continues.
Action:
None.
Reason:
Command rejected because file was queued for purge processing. Processing continues.
Action:
None.
Reason:
Command rejected because file is in the temporarily closed state. Processing continues.
Action:
Issue a close-file command followed by the reset command.
Reason:
Command rejected because file is being transferred to the JES system. Processing continues.
Action:
None.
Reason:
Command rejected; file being processed by network-print processor. Processing continues.
Action:
None.
Reason:
xxxxxx specifies the number of files routed. Processing continues.
Action:
None.
Reason:
xxxxxx specifies the number of files requeued. Processing continues.
Action:
None.
Reason:
Internal response to a display printer command from the menu system. Processing continues.
Action:
None.
Reason:
xxxxxx specifies the number of files released. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command. xxx specifies the current number of TCP/IP printer subtasks active. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command. Files, pages and lines for current hour, maximum hour and grand total since last restart are displayed.
Action:
None.
Reason:
xxxxxx specifies the number of files held. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display-status (DS) command. xxxxxx specifies the current number of printers defined. yyyy specifies how many more printers may be defined. Processing continues.
Action:
None.
Reason:
A start command / NJE node xxxxxxxx has been rejected because the network node is inactive. Processing continues.
Action:
Activate the printer node through a VTAM V NET,ACT command, and enter the start-printer command again.
Reason:
A simlogon error has been detected on network node xxxxxxxx. rc is the VTAM return code, f2 is the VTAM feedback code 2, sysi is the VTAM system-sense information, and ussi is the VTAM user-sense information.
The printer node enters Edrained status. Processing continues.
Action:
Correct any communication problems and start the printer node.
Reason:
A start-printer command or a start NJE command has been rejected because the network interface is in the process of being terminated. Processing continues.
Action:
None.
Reason:
Start command for printer / NJE node xxxxxxxx rejected; previous start command queued to VTAM which will not start node processing before release. Processing continues.
Action:
None.
Reason:
Network interface is stopped. Processing continues.
Action:
Start the interface, then re-enter the start printer command.
Reason:
Start printer command for printer xxxxxxxx rejected by VTAM. Processing continues.
Action:
Contact your systems programmer.
Reason:
A message command was entered, but no user received the message. Processing continues.
Action:
None.
Reason:
Processing continues.
Action:
None.
Reason:
xxxxx specifies the current number of active communication channels. Processing continues.
Action:
None.
Reason:
Command rejected; file being printed by the GDDM interface. Processing continues.
Action:
None.
Reason:
Rejected because the network interface is being terminated. Processing continues.
Action:
None.
Reason:
The SNET, PNET or TNET command was rejected because the network for the specified new Network Owner ssss was not active. Processing continues.
Action:
None.
Reason:
This message displays in response to a display status (DS) command.
Action:
None.
Reason:
This message is displayed in response to a display (DS) command. Processing continues.
Action:
None.
Reason:
Displayed in response to LSYS command where:
Action:
None.
Reason:
Reset system command rejected; previous ESYS not completed. Processing continues.
Action:
Wait for the previous command to complete and then re-enter.
Reason:
Reset system command rejected because the affected system is active.
Action:
None.
This message number represents one of the following messages:
Reason:
Displayed in response to cancel ESF to SAR interface (CSAR). The ESF to SAR interface is halted.
Action:
None.
This message number represents one of the following messages:
Reason:
Displayed in response to a halt ESF to SAR interface (HSAR). The ESF to SAR interface is halted.
Action:
None.
This message number represents one of the following messages:
Reason:
Displayed in response to a start ESF to SAR interface (SSAR). See the actual message text.
Action:
None.
Reason:
This message is displayed in response to a display (DS) command and shows the current status of the Transformer interface. If Transformer interface is active 999999 specifies the number of files currently being processed by the Transformer interface. Processing continues.
Action:
None.
This message number represents one of the following messages:
Reason:
This message is displayed in response to a HT - halt Transformer interface command. The Transformer interface is halted.
Action:
None.
This message number represents one of the following messages:
Reason:
This message is displayed in response to a ST - start Transformer interface command. See the actual message text.
Action:
None.
Reason:
A REINIT (reinitialize) command has been successfully completed. All changes to the parameter deck are updated in CA Spool. Processing continues.
Action:
None.
Reason:
REINIT (reinitialize) command successfully completed. Some changes could not be updated due to nodes in session with CA Spool. Processing continues.
Action:
Re-issue the REINIT command.
Reason:
REINIT (reinitialize) command has been completed. One or more of the changed node definitions were not successfully updated. Processing continues.
Action:
Contact your systems programmer.
Reason:
REINIT failed because syntax errors found in the parameter deck. Processing continues.
Action:
Contact your systems programmer.
Reason:
This message is displayed in response to a display (DS) command and shows the currently used names and addresses of the ESFSSSM and ESFUSS load modules. Processing continues.
Action:
None.
Reason:
This message is displayed in response to a display (DS) command and shows the current status of the LPD interface. Processing continues.
Action:
None.
Reason:
This message is displayed in response to an LPD command, if the LPD interface has not been defined. Processing continues.
Action:
None.
There are four versions of this message with variable text.
Reason:
A request to queue a refresh of ECSA module ESFSSSM, ESFUSS, and ESFUSO has been successfully processed and the refresh will occur at the next CA Spool startup.
Action:
None.
Reason:
A request to queue a refresh of ECSA modules ESFSSSM, ESFUSS, and ESFUSO has been rejected because a refresh request is already pending.
Action:
None.
Reason:
A request to cancel a pending request to refresh ECSA modules ESFSSSM, ESFUSO, and ESFUSS has been successfully processed and the pending request has been canceled.
Action:
None.
Reason:
A request to cancel a pending request to refresh ECSA modules ESFSSSM, ESFUSO, and ESFUSS has been rejected because there is no pending request to refresh the modules.
Action:
None.
Reason:
A file control command has been rejected because the affected file is active on another system in the multi-access-spool configuration. Processing continues.
Action:
None.
Reason:
Reset-printer command rejected because a file is active on the printer. Processing continues.
Action:
Interrupt the printer, then re-enter the reset command.
Reason:
A printer-control command has been rejected because the specified printer node is not connected to the system. Processing continues.
Action:
Start the printer (using the start command), then re-enter command.
Reason:
An operand on a command was too long.
The command string is discarded, and processing continues.
Action:
Re-enter the correct command.
Reason:
A command has been entered with one or more invalid operands. The command is discarded, and processing continues.
Action:
Re-enter the command with valid operands.
Reason:
One or more required operands missing from command. The command is discarded. Processing continues.
Action:
Enter the correct command.
Reason:
A command has been entered which CA Spool does not recognize as a valid CA Spool command. The command is discarded. Processing continues.
Action:
Enter the correct command.
Reason:
String was too long to be contained in an internal command buffer. The command string entered is discarded, and processing continues.
Action:
Enter the commands in smaller pieces.
Reason:
The command processor was unable to allocate an internal command buffer to contain the specified command string. The command string is discarded, and processing continues.
Action:
Enter the command again later.
|
Copyright © 2011 CA.
All rights reserved.
|
|