Reason:
CA Spool has successfully completed an xxxx start, where xxxx is cold or warm. Processing continues.
Action:
None.
Reason:
CA Spool detected an out-of-work condition. This message is displayed only in single-system configurations and indicates that no logical process is currently active in the system, and CA Spool may be terminated using the shutdown command. CA Spool enters wait state until work becomes ready.
Action:
None.
Reason:
CA Spool has completed a normal termination sequence. CA Spool terminates processing.
Action:
None.
Reason:
An ESF command has been issued by the operator. This is not allowed, and the command has been rejected. Processing continues.
Action:
To stop CA Spool use the shutdown command.
Reason:
A command string which was too long or all blanks has been entered by the operator. The command string is disregarded, and processing continues.
Action:
Re-enter a valid command.
Reason:
CA Spool was unable to allocate an internal command buffer. The command string is disregarded, and processing continues.
Action:
Try to re-enter the command later.
Reason:
File xxxxxx with owner name oooooooo and destination name dddddddd has been successfully purged. The purge was initiated due to reason vvvvvvvv which may be any of the following:
Purged by automatic scan of the file queue. This file was in 'E' status and has exceeded the combination of FILELIM and RETAIN values.
Purged by automatic scan of the file queue. This file was not in 'E' status and has exceeded the combination of PURGELIM and RETAIN values.
Purged by the print processor due to the printer NODE specification of PURGE=YES. PURGE=YES can be set on the NODE statement or in the menu interface.
Purged by the NJE processor due to the NJE statement specification of PURGE=YES.
Purged by the print processor after the file is placed in 'E' status and the file's RETAIN value is found to be equal to '-1'.
Purged by the print processor after the file is placed in 'E' status and the printer's RETAIN value is found to be equal to zero.
Purged by the cross memory processor due to ESFPARM specification BACKOUT=YES.
Purged by the cross memory processor due to ESFPARM specification XEQOPT=8.
Purged by the print processor or the cross memory processor due to an OUTDISP setting of 'W' or 'P' on the file.
Purged due to a request by a user. aaaaaaaa is the userid of the requestor, if known.
Processing continues.
Action:
None.
Reason:
A get-buffer request has been issued, but no buffer was available. xxxx defines the type of buffer requested:
Processing continues.
Action:
None.
Reason:
CA Spool has been waiting for work for a period of time exceeding the timer introduced by USERZAP 127. TNET and SHUTDOWN commands are automatically issued and CA Spool is terminated.
Action:
None.
Reason:
When trying to dynamically add node xxxxxxxx, CA Spool found an existing DCE with a different type. Processing continues.
Action:
Contact your systems programmer.
Reason:
The node xxxxxxxx could not be defined because the node name or the alias name or the virtual printer name already exists. Processing continues.
Action:
Use unique names when defining users and nodes.
Reason:
The node xxxxxxxx could not be defined because the total number of nodes added to the parameter deck exceeded the DYNDISP/DYNPRT parameters. Processing continues.
Action:
Decrease the number of nodes in the parameter deck, then re-issue the REINIT command, or shutdown, then restart CA Spool.
Reason:
The group number on node xxxxxxxx was greater than the maximum-group parameter. Processing continues.
Action:
Change the MAXGROUP parameter and shutdown, then restart CA Spool.
Reason:
The DEFNODE sub-parameter on node xxxxxxxx specified a non-existent DEFNODE. Processing continues.
Action:
Change the DEFNODE sub-parameter to a valid default node, or add the missing DEFNODE.
Reason:
CA Spool tried to connect node xxxxxxxx, which was already related to a network group. Processing continues.
Action:
Contact your systems programmer.
Reason:
The node xxxxxxxx could not be redefined because it was in session with CA Spool when the REINIT command was issued. Processing continues.
Action:
Re-issue the REINIT command when the node is drained if the node definition was changed.
Reason:
The specified alias name for node xxxxxxxx was already assigned to another node. Processing continues.
Action:
If the alias name was moved from one node to another node, re-issue the REINIT command.
Reason:
A logon request has been rejected because an invalid password was specified. The logon request is discarded.
Action:
Enter correct password.
Reason:
A logon request has been rejected because the user specified a group which was not authorized for his use. The logon request is discarded.
Action:
Enter valid group.
Reason:
A logon request has been rejected because the user was not authorized to use this terminal. The logon request is discarded.
Action:
Logon from a valid terminal.
Reason:
A logon request has been rejected because the user specified an undefined user ID. The logon request is discarded.
Action:
Specify a valid user ID.
Reason:
A logon request has been rejected because the user specified an undefined group. The logon request is discarded.
Action:
Specify a valid group.
Reason:
A logon request has been rejected because the user specified an undefined related node. The logon request is discarded.
Action:
Specify a valid node name.
Reason:
The user xxxxxxxx could not be defined because the total number of users added to the parameter deck exceeded the DYNUSER parameter. Processing continues.
Action:
Decrease the number of users in the parameter deck, then re-issue the REINIT command, or shutdown, then restart CA Spool.
Reason:
The user xxxxxxxx could not be defined because the name already existed. Processing continues.
Action:
Use unique names when defining users and nodes.
Reason:
CA Spool could not send a command to the network owning member xxxxxxxx in an EMAS configuration. yyyyyyyy is a self-explanatory message text. The command is executed in the originating CA Spool system.
Action:
Re-enter the command later.
Reason:
The file 999999 with the destination xxxxxxxx and the filename yyyyyyyy is ready for processing. Processing continues.
Action:
None.
Reason:
File xxxxxx with owner name oooooooo and destination name dddddddd has been successfully physically purged, that is, it has been overwritten on the spool data set. Processing continues.
Action:
None.
Reason:
No valid APD DEFNODE statement could be found for printer aaaaaaaa. The print file will be rejected with ESFOPEN return code 22.
Action:
Contact your systems programmer.
Reason:
When using the automatic printer definition feature, the ESFU008 exit can change the printer attributes after the best match DEFNODE has been found. ESFU008 can return with RC=4 to find a new best match DEFNODE, after which the ESFU008 exit is invoked again. If ESFU008 returns with RC=4 for the same printer more than 10 times, this message is issued. The print file is rejected with ESFOPEN return code 22.
Action:
Contact your systems programmer.
Reason:
Node aaaaaaaa was not dynamically defined. A message explaining the reason is also issued. The print file is rejected with ESFOPEN return code 22.
Action:
Contact your systems programmer.
Reason:
Node aaaaaaaa was dynamically defined with attributes from the bbbbbbbb DEFNODE. Processing continues.
Action:
None.
Reason:
Node aaaaaaaa was not dynamically defined because it was rejected by the ESFU008 exit. The print file is rejected with ESFOPEN return code 22.
Action:
Contact your systems programmer.
Reason:
The translate table aaaaaaaa is not recognized. The print file will be rejected with ESFOPEN return code 22.
Action:
Contact your systems programmer. The translate table could have been inserted by the APD exit ESFU008.
Reason:
The data encryption/decryption module failed for service cccccccc with ICSF return code 99 and ICSF reason code 88 and Entry request code 77.
The following Entry codes 77 may be observed:
8 - Get current key label.
20 - Encrypt data.
24 - Decrypt data.
For documentation of the ICSF return and reason codes, see Appendix A in the z/OS ICSF Application Programmer Guide.
Action:
Correct the reported ICSF configuration problem.
Reason:
The data encryption/decryption module failed for service cccccccc with ICSF return code 99 and ICSF reason code 88 and Entry request code 77.
The following Entry codes 77 may be observed:
8 - Get current key label.
20 - Encrypt data.
24 - Decrypt data.
For documentation of the ICSF return and reason codes, see Appendix A in the z/OS ICSF Application Programmer Guide.
Action:
Start ICSF.
Reason:
The ICSF encryption key for key label 9999999 for Entry request code 77 was not found.
The following Entry codes 77 may be observed:
8 - Get current key label.
20 - Encrypt data.
24 - Decrypt data.
Action:
Check if the current ICSF CKDS data set has been destroyed.
Reason:
The data encryption/decryption module failed because service code 99 is not defined.
Action:
Report the problem to CA Support.
Reason:
The preceding message ESF160 provides information about why ICSF data encryption/decryption is not working. CA Spool waits for the operator reply.
Action:
Correct the error and reply RETRY. If that does not work, reply HALT to halt the SUBSYS interface so that no more spool files are created or processed; then correct the problem and restart the SUBSYS interface and possibly other interfaces (see ESFLOG for more stopped interfaces). If the problem cannot be corrected in a timely manner, reply TERMINATE to terminate CA Spool.
Reason:
The data decryption failed because the encryption key label used to encrypt the data was not found in ICSF.
Action:
Report the problem to your system programmer to check if the current ICSF CKDS data set has been destroyed or if the spool file has created a CA Spool system which does not share the same ICSF CKDS data sets.
Processing continues.
Reason:
The IXLCONN connect request to the CKPT Coupling Facility structure failed with return code 99 and reason code xxxxyyyy. The use of the Coupling Facility is disabled and the CA Spool startup continues.
Action:
Contact your systems programmer.
Reason:
The IXLLIST zzzzz request to the CKPT Coupling Facility structure failed with return code 99 and reason code xxxxyyyy. CA Spool terminates.
Action:
Contact your systems programmer.
Reason:
The IXLDISC disconnect request to the CKPT Coupling Facility structure failed with return code 99 and reason code xxxxyyyy. CA Spool terminates.
Action:
Contact your systems programmer.
|
Copyright © 2011 CA.
All rights reserved.
|
|