Reason:
The CA Spool VTAM interface has established a session with network node xxxxxxxx belonging to network group yyyyy. Processing continues.
Action:
None.
Reason:
The CA Spool VTAM interface was unable to establish a session with network node xxxxxxxx. The session request is discarded, and processing continues.
Action:
Try to re-establish the session, and if the problem still persists, contact your systems programmer.
Reason:
The CA Spool VTAM interface has successfully terminated a session with network node xxxxxxxx in network group yyyyy. Processing continues.
Action:
None.
Reason:
The CA Spool/VTAM interface has rejected a logon request because one or more of the bind parameters were not acceptable. The logon request is discarded.
Action:
Contact your systems programmer.
Reason:
The CA Spool VTAM interface has rejected a logon request because storage for a SNA buffer could not be obtained. The logon request is discarded.
Action:
Contact your systems programmer.
Reason:
The CA Spool VTAM interface has rejected a logon request because the logon-reply parameters were not acceptable. The logon request is discarded.
Action:
Enter correct reply.
Reason:
CA Spool has detected that the network-display node xxxxxxxx has exceeded its timeout interval. CA Spool terminates the session with the network node.
Action:
None.
Reason:
The user pressed the PA1 key, causing the processing mode of the display device to be altered to automatic wrap around mode. Processing continues, but new messages will now automatically wrap-around from the bottom line to the top line.
Action:
None.
Reason:
The user pressed the PA1 key, causing the processing mode of the display device to be altered so automatic message wrap-around will not occur. Processing continues, but new messages will not automatically wrap-around from the bottom line to the top line. User intervention or a one minute timeout interval must occur before the first line on the screen will be overlaid.
Action:
None.
Reason:
No more work was available for printer node xxxxxxxx servicing output classes yyyyyyyy. Processing continues.
Action:
None.
Reason:
The printer node xxxxxxxx has selected file yyyyyy for output processing. A total of zzzzzzz pages or zzzzzzz lines are to be printed, which means the number of copies multiplied by the number of output pages or lines per copy. Processing continues.
Action:
None.
Reason:
Printer node xxxxxxxx has selected file yyyyyy for output processing, but the operator has to change form and/or FCB to ffffffff and/or cccc. CA Spool assumes this form to be pp lines high and will print d lines per inch. The printer is placed in halted state. Processing continues.
Action:
Enter a start command when the printer is ready. (SCS printers only: The start command may also be given by pressing the PA1 key on the printer-control panel.)
Reason:
The processing state of printer node xxxxxxxx has been changed. The specified action is performed. Processing continues.
Action:
None.
Reason:
Printer node is unable to queue an FCB image request to image-loader. The printer node is drained and the file held. Processing continues.
Action:
If a new start of the printer node does not work, then restart CA Spool as soon as possible.
Reason:
CA Spool was unable to delete an FCB image. Return code from the DELETE SVC was xx. The printer node is drained and the file held. Processing continues.
Action:
If a new start of the printer node does not work, then restart CA Spool, or contact the systems programmer.
Reason:
CA Spool was unable to load an FCB image from SYS1.IMAGELIB. The return code from the LOAD SVC was xx. The printer node is drained and the file held. Processing continues.
Action:
If a new start of the printer node does not work, then try to restart the entire CA Spool system, or contact the systems programmer.
Reason:
A printer node has requested a load of FCB image xxxx, but the image was not found in SYS1.IMAGELIB. The printer node is drained and the file held. Processing continues.
Action:
Add requested image to SYS1.IMAGELIB, start printer node.
Reason:
An intervention-required condition 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. CA Spool waits for the printer to signal that it is ready. Processing continues.
Action:
Ready the printer node.
Reason:
An uncorrectable I/O 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 is interrupted and drained. Processing continues.
Action:
Correct any hardware problems and start the printer node.
Reason:
A forward-space command for printer node xxxxxxxx reached end-of-file on the spool file. The spool file is backspaced 10 pages from end-of-file, and print processing continues from that point.
Action:
None.
Reason:
The printer node xxxxxxxx has finished printing file yyyyyy. PRINTED means that the file has printed to end-of-file. INTERRUPTED means that the file has not printed to end-of-file. Processing continues.
Action:
None.
Reason:
CA Spool was unable to allocate virtual-storage space for a spool buffer during start of printer xxxxxxxx. The printer node is drained. Processing continues.
Action:
Contact your systems programmer. It may be necessary to increase the region size for CA Spool.
Reason:
FCB image xxxx contains an invalid ESF specification in extension. The printer node is drained and the file held. Processing continues.
Action:
Correct the FCB in error and start the printer node.
Reason:
A file could not be printed with the GDDM interface because the VTAM ACB was closed. The printer node is drained, and file is held. Processing continues.
Action:
Ensure that the ACB used by GDDM is open. To reactivate the GDDM ACB, the network interface must be stopped and restarted. Use either the PNET or TNET command to stop the network and the SNET to restart it.
This message number represents two different messages. Both of these messages can be written at the same time.
Reason:
CA Spool has received a non-zero return code from the GDDM interface. The second line contains another CA Spool message or a GDDM message. The printer node is drained, and the file is held. Processing continues.
Action:
Contact your systems programmer.
Reason:
The printer node xxxxxxxx does not support the SCS command yyy. The yyy specification may have the value SVF or PPM. The printer node is drained and the file held. Processing continues.
Action:
Correct the device type or the logmode entry of the printer, and start the printer node.
Reason:
The printer node xxxxxxxx is drained on request from the printer user exit. Processing continues.
Action:
None.
Reason:
CA Spool was unable to allocate virtual storage for the GDDM interface. The printer node is drained, and the file is held. Processing continues.
Action:
Report this message to your systems programmer; it may be necessary to increase the region size.
Reason:
The file yyyyyy on printer node xxxxxxxx has been interrupted and held on request from the printer user exit. Processing continues.
Action:
Report this message to your systems programmer.
Reason:
If PRTOPT=24 used and the specified file FCB ffff was not found then the default printer FCB dddd will be used.
Action:
None.
Reason:
An IMAGE load was rejected. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Contact your systems programmer.
Reason:
The FORMDEF specified for this print file does not exist. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Change the FORMDEF to an existing one.
Reason:
The PAGEDEF specified for this printfile does not exist. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Change the PAGEDEF to an existing one.
Reason:
An IMAGE delete was rejected. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Contact your systems programmer.
Reason:
The module HRESET does not exist in IMAGELIB. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
The module HRESET must be created.
Reason:
One of the fonts specified in the CHARS parameter for this file does not exist. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Change the FONT to an existing one.
Reason:
One of the fontdef modules for a temporary soft font specified in the CHARS parameter for this file does not exist. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
The fontdef module must be added to IMAGELIB.
Reason:
The module HDEVTYPS was not found in IMAGELIB. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
An HDEVTYPS module must be assembled and linked into IMAGELIB.
Reason:
A message from a module, which the CA Spool HP-LASERJET support tried to send, was greater than the VTAM buffer, and could not be sent. The message is probably located in the named module. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Either increase the SNABSIZE in the CA Spool startup parameters, or split the message into smaller messages and assemble and link into IMAGELIB.
Reason:
Load or delete of a module from IMAGELIB was rejected because the IMAGE subtask has abended. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Browse the CA Spool log for messages related to the IMAGE subtask abend. Stop, then restart CA Spool as soon as possible and keep the dump. Contact the systems programmer.
Reason:
A load of a module from IMAGELIB failed because the module could not be found or because storage for the module was not available. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Check if the module is present in the IMAGELIB used by CA Spool. If this is not the problem then increase the REGION parameter in the CA Spool procedure.
Reason:
The module zzzzzzzz did not contain a $LPDVP macro call naming the device type yyyyyyyy of the printer xxxxxxxx. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Correct the error.
Reason:
The module yyyyyyyy could not be deleted, since it was not in storage. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
This is probably a logical error in the laser interface. Report the problem to the systems programmer.
Reason:
Storage to load a module was not available. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Increase the REGION in the CA Spool procedure.
Reason:
The maximum number of current fonts for a file is exceeded. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Reduce the number of fonts used in file.
Reason:
The direction in which writing is to be done is not supported by the font xxxx. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Correct the problem.
Reason:
A control block error was detected in the module xxxxxxxx. Processing of this file is terminated, and the printer is drained. Processing continues.
Action:
Correct the problem.
Reason:
A logon request from network node xxxxxxxx has been rejected because the node name is unknown to CA Spool. The logon request is discarded. Processing continues.
Action:
If the node must be made available for CA Spool, add the node definition to the CA Spool initialization parameter data set, then restart CA Spool.
Reason:
VTAM reason code yy shows that contact with network node xxxxxxxx has been lost. Network node interrupted and terminated, processing continues.
Action:
Re-activate the network node, if applicable.
Reason:
CA Spool has been notified by VTAM that the entire network is to be halted. VTAM reason code is xx. Reason code is 00, the VTAM interface stopped when all active sessions have been terminated. Reason code is not 00, all sessions will be interrupted, and the VTAM interface will be stopped immediately.
Action:
None.
Reason:
CA Spool has been notified by VTAM that another application wants to use network node xxxxxxxx. Session with the network node is terminated if allowed in the initialization parameter data set. Otherwise, this condition is ignored.
Action:
None.
Reason:
CA Spool notified by VTAM that the network node xxxxxxxx has requested a transmission-recovery sequence. The session with the network node is interrupted and terminated.
Action:
None.
Reason:
VTAM-network interface has received an RPL with no user field. The RPL is ignored, because CA Spool cannot relate it to any active session. Processing continues.
Action:
Contact your systems programmer.
Reason:
CA Spool has been notified by VTAM that some network service is requested for node xxxxxxxx. The field zzzzzzzz contains the first 38 bytes of the request unit received from VTAM. See the VTAM Programming. manual for more information about NSEXIT exit routines. The session or the pending session request with the affected network node is interrupted and terminated. Processing continues.
Action:
Re-activate the network node, if applicable.
Reason:
A disastrous error has occurred in the VTAM network interface, and the ESTAE exit has received control. The VTAM network interface is marked inactive, and can only be started if the entire CA Spool system is restarted.
Action:
Restart CA Spool as soon as possible.
Reason:
The VTAM network interface was unable to establish an ESTAE environment. CA Spool will terminate initialization.
Action:
Report this message to your systems programmer.
Reason:
The CA Spool VTAM interface has rejected a session request because xxxxxxxx was not a valid NJE node. The session request is discarded.
Action:
Contact your systems programmer.
Reason:
The CA Spool VTAM network-interface has been successfully started, and logon requests can be processed. Processing continues.
Action:
None.
Reason:
The CA Spool/VTAM network interface has been successfully stopped, and logon requests can no longer be processed. Processing continues.
Action:
None.
Reason:
The CA Spool VTAM-network interface has received an RPL with no user field. The RPL is ignored because CA Spool cannot relate it to any active session. Processing continues.
Action:
Contact your systems programmer.
Reason:
A VTAM error has been detected on network node xxxxxxxx. The VTAM request was st and tttttt. rc was the VTAM return code; f2 was the VTAM feedback code 2; f3 was the VTAM feedback code 3; ssei was the VTAM system-sense information; and usei was the VTAM user-sense information.
For OPEN/CLOSE VTAM application requests the rc and f2 information are actual the OPEN/CLOSE return code and the ACB ERROR value, which are both documented in the VTAM Programming manual in the documentation for the OPEN and CLOSE macro-instructions.
Action:
Depends on request type. For more information, see VTAM Messages and Codes (SC23-0114) and VTAM Programming (SC23-0115).
|
Copyright © 2011 CA.
All rights reserved.
|
|