Reason:
The file-transfer subtask was unable to establish an ESTAE environment.
CA Spool will terminate initialization.
Action:
Try to restart CA Spool, or contact the systems programmer.
Reason:
A disastrous error has occurred in the file-transfer subtask, and the ESTAE exit routine has received control. The file-transfer interface is marked inactive, and can only be started if the entire CA Spool system is restarted. Processing continues with the interface halted.
Action:
Restart CA Spool as soon as possible. Save the dump output.
Reason:
The automatic file-transfer service routine has allocated file xxxxx for transfer to JES2/JES3 destination yyyyyyyy. The ESFTOJES file-transfer interface will initiate transfer of the allocated spool file.
Action:
None.
Reason:
The ESFTOJES file-transfer interface has successfully completed the transfer of file xxxxxx to JES2/JES3 destination yyyyyyyy. The file is marked as printed, and processing continues.
Action:
None.
Reason:
The ESFTOJES file-transfer interface was unable to allocate a spinoff SYSOUT file. Return code was xx, and error/info code was yyyyyyyy. The ESFTOJES file-transfer interface has abended and is halted.
Action:
Contact your systems programmer. The ESFTOJES interface can be restarted with the SX,ESFTOJES command when the cause of the dynamic allocation failure has been corrected.
Reason:
The ESFTOJES file-transfer interface was unable to open the JES2/JES3 SYSOUT file. The ESFTOJES file-transfer interface has abended and is halted.
Action:
Contact your systems programmer. The ESFTOJES interface can be restarted with the SX,ESFTOJES command when the cause of the open SYSOUT failure has been corrected.
Reason:
The file-transfer service processor found that no more files were awaiting transfer. The file-transfer interface enters the wait state.
Action:
None.
Reason:
During ESFTOJES file transfer, an incomplete spool-block chain was detected. This message is only written to the JES2/JES3 sysout file. The ESFTOJES file-transfer interface terminates the JES2/JES3 sysout file, and the CA Spool file is marked as printed.
Action:
None.
Reason:
File xxxxxx has been queued for automatic file transfer to destination yyyyyyyy in the JES2/JES3 system zzzz. The ESFTOJES file-transfer interface will perform the transfer.
Action:
None.
Reason:
A subsystem remote-destination validation-check request to the primary subsystem xxxx has been rejected with return code yy. Processing continues.
Action:
Contact your systems programmer. The subsystem-request return codes are documented in the MVS Debugging Handbook under the description of the SSOB data area.
Reason:
File 999999 queued for processing by the ESF to SAR interface. Processing continues.
Action:
None.
Reason:
File 999999 has successfully been processed by the automatic ESF to SAR transfer interface. The xxxxxxxxxxxx specifies the action performed BACKED UP, TRANSFERRED or ARCHIVED. The tttttttt and dddddddd shows the time and date of the transfer. The nnnnnnnnnnnn shows the assigned SAR report ID. The ggggg and sssss shows the assigned SAR generation number and SAR sequence number. Processing continues.
Action:
None.
Reason:
The attach of the ESF to SAR subtask for file 999999 failed. The xxxxxxxx specifies the ESF to SAR load module name and the 99 is the return code from the ATTACH MVS service. The ESF to SAR interface is halted.
Action:
Contact your systems programmer.
Reason:
The load or delete of the SARPAM load module xxxxxxxx in the ESF to SAR interface failed with the aaaa abend code and rrrr reason code. The ESF to SAR interface is halted.
Action:
Contact your systems programmer.
Reason:
The specified processing for file 999999 failed. The xxxxxxxx specifies the ESF to SAR load module name and the 99 is the return code from the SARPAM interface. The ESF to SAR interface is halted.
Action:
Contact your systems programmer.
Reason:
The specified processing for file 999999 failed with the request-status code xx. The ESF to SAR interface is halted.
Action:
Contact your systems programmer.
Reason:
The specified processing for file 999999 failed with the request-status code xx. The ESF to SAR interface is halted.
Action:
Contact your systems programmer.
Reason:
The current state of the ESF to SAR interface has changed as shown in the message. Displayed in the message text.
Action:
None.
Reason:
File 999999 is being processed by the ESF to SAR interface as shown in the message text. The file is being processed by the ESF to SAR interface.
Action:
None.
Reason:
This message is issued for each LMP enabled CA Spool optional feature during CA Spool startup. The options have the following LMP codes:
Action:
None.
Reason:
The CA Common Services for z/OS LMP support is not initialized correctly. CA Spool terminates processing.
Action:
Contact your systems programmer.
Reason:
During initialization the SMF-writer subtask was unable to establish an ESTAE recovery environment. Initialization is terminated.
Action:
Contact your systems programmer.
Reason:
The SMF-writer subtask has abended. SMF data will be lost. Processing continues without SMF recording.
Action:
Restart the entire CA Spool system as soon as possible. Save the dump output.
Reason:
A non-zero return code xx has been received from the SMF-writer interface. SMF data will be lost. SMF recording is suspended until the SMF writer interface is operational again.
Action:
Check that normal MVS SMF recording is operational.
Reason:
The SMF-writer interface has switched from the non-operational to the operational state. SMF recording is resumed.
Action:
None.
Reason:
The CA Spool log-writer subtask was unable to establish an ESTAE-recovery environment. Initialization is terminated.
Action:
Contact your systems programmer.
Reason:
The log-writer subtask has abended. Logging is terminated.
Action:
Restart CA Spool as soon as possible if logging is required. Save the dump output.
Reason:
The log-writer subtask was unable to allocate a spin-off SYSOUT file. Logging is terminated.
Action:
Restart CA Spool as soon as possible if logging is required.
Reason:
The log-writer subtask was unable to open the allocated spin-off SYSOUT file. Logging is terminated.
Action:
Restart CA Spool as soon as possible if logging is required.
Reason:
An ESFLOG output data set has been successfully closed and released. Logging continues.
Action:
None.
Reason:
The Service Desk Interface subtask was unable to establish an ESTAE-recovery environment. Initialization is terminated.
Action:
None.
Reason:
The Service Desk interface subtask has abended. The subtask is terminated. Processing continues.
Action:
Restart CA Spool as soon as possible if the Service Desk Interface is required. Save the dump output.
Reason:
CAISDI/med returned a non-zero reason code to CA Spool's attempt to create a Unicenter Service Plus HelpDesk issue. aaaaaaaa is the CA Spool message number that initiated the request. xx is the reason code passed back by the CA-SDI/med task.
Possible values include:
Action:
Contact your systems programmer.
Reason:
A storage request made by the Service Desk interface has failed. The subtask is terminated.
Action:
Restart CA Spool as soon as possible if the Service Desk Interface is required. For repeated occurrences, a dump of the CA Spool task is recommended.
Reason:
CA Health Checker returned a non-zero return code for CA Spool's attempt to perform a Health Check function.
Action:
Contact CA Technical Support and provide the Joblog for the task.
Reason:
The image-loader subtask was unable to establish an ESTAE-recovery environment. Initialization is terminated.
Action:
Contact your systems programmer.
Reason:
Either the volume containing SYS1.IMAGELIB is not mounted, or a required catalog volume was not mounted. Initialization is terminated.
Action:
Mount the required volume, then restart CA Spool.
Reason:
Either SYS1.IMAGELIB does not exist on the volume to which the catalog points, or it is not cataloged. Initialization is terminated.
Action:
Contact your systems programmer.
Reason:
An error occurred in reading the catalog or VTOC. Initialization is terminated.
Action:
Contact your systems programmer.
Reason:
The image-loader subtask has abended. All pending image requests canceled, no new requests accepted.
Action:
Restart CA Spool. Save the dump output.
Reason:
During initialization the OMR subtask was unable to establish an ESTAE recovery environment. Initialization is terminated.
Action:
Contact your systems programmer.
Reason:
The OMR subtask has abended. The subtask is terminated. Processing continues.
Action:
Contact your systems programmer.
Reason:
The OMR subtask has reset the current hour statistics for all printers defined. Processing continues.
Action:
None.
Reason:
During halt of the JESTOESF interface, a subsystem-request error occurred. The return codes xx and yy are documented in the MVS Debugging Handbook under the SSOB and SSSO data areas, respectively. The ESFTOJES interface is halted.
Action:
Contact your systems programmer.
Reason:
A subsystem-request error occurred in the JESTOESF interface. The return codes xx, yy and zz are documented in the MVS Debugging Handbook under the SSOB and SSSO data areas, respectively. The ESFTOJES interface has abended and is halted.
Action:
Contact your systems programmer.
Reason:
An error occurred in the JESTOESF interface during allocate, open, read, or unallocate of a JES2/JES3 SYSOUT file belonging to job 9999. The ESFTOJES interface enters wait state until the operator enters a reply to the outstanding WTOR message.
Action:
Place job 9999 in hold status, and reply C to let the JESTOESF interface continue or reply T to halt the JESTOESF interface.
Reason:
The JESTOESF interface was unable to allocate the JES2/JES3 SYSOUT file. A reason of the return code and the error/info code can be found in either the MVS Job Management manual or the MVS/XA System Macros and Facilities manual. The ESFTOJES interface issues the WTOR message ESF762. A blank DSNAME may be caused by a missing SUBID destination name definition in JES2 or JES3.
Action:
Contact your systems programmer.
Reason:
The JESTOESF interface was unable to open the JES2/JES3 SYSOUT file xxxxxxxxxx. The ESFTOJES interface issues the WTOR message ESF762.
Action:
Contact your systems programmer.
Reason:
The JESTOESF interface detected a CA Spool error during transfer of a JES2/JES3 SYSOUT file belonging to JOBID/jobname job 9999/jobnamex. The failed CA Spool request yyyyyy may be OPEN, WRITE, CLOSE, or ROUTE. The ESFTOJES interface may have abended and halted, depending on the request type and RC.
If ESFOPEN failed with RC=PE, the id zzz of the parameter in error is included in the message.
FILE 99999 is the file number in CA Spool. If the message is issued during open, there is no file number and the dummy number 99999 is displayed.
Action:
Contact your systems programmer.
Reason:
The JESTOESF interface detected a CA Spool error during transfer of a JES2/JES3 SYSOUT file belonging to JOBID jobidxxx, job name jobnamex. The file being transferred did not have enough space in its USERDATA area to store all OUTPUT statement USERDATA and MAIL parameters.
The file was not transferred to CA Spool.
Action:
Review the job that created the file that was rejected, to determine how to reduce its USERDATA or MAIL parameter requirements, and fit into the 960 byte USERDATA area.
Reason:
One or more JES2/JES3 SYSOUT files from job 9999/jobnamex was successfully transferred from the primary subsystem jesx to CA Spool esfx, where it has been saved in file 999999 with the destination xxxxxxxx. The resulting CA Spool file is now ready to be printed.
Action:
None.
Reason:
The JESTOESF interface detected an I/O error during read of a JES2/JES3 SYSOUT file. The ****error message**** information is the error description provided by the MVS SYNADAF routine. The ESFTOJES interface issues the WTOR message ESF762.
Action:
Contact your systems programmer.
Reason:
The JESTOESF interface detected an I/O error during read of a SYSOUT file from the primary subsystem JESx. The ESFTOJES interface issues the WTOR message ESF762.
Action:
Contact your systems programmer.
Reason:
The JESTOESF interface has been terminated as a result of message ESF765.
Action:
Contact your systems programmer. You must either restart the JESTOESF interface or recycle CA Spool.
This message number represents one of the following messages:
Reason:
The storage related to XFERSAPI threads processing is being released or has been released due to a REINIT, HX or SHUTDOWN command.
Action:
None.
Reason:
XFERSAPI threads processing has terminated with an error.
Action:
Retain the logs. Report the error to your systems programmer and/or CA Technical Support.
This message number represents one of the following messages:
Reason:
When XFERSAPI=YES is specified and XFEROPT=24 is set, the number of unique requests made at each XFERTIME interval will be reported during the initial start of the JESTOESF interface.
When XFERSAPI-THREADS is specified, the number of threads being initialized will be reported each time the threads are being initialized. This can occur when the interface is started and when a REINIT command has resulted in a change to the printer definitions.
Action:
None.
Reason:
XFERSAPI threads processing has initialized nnnnnnnn threads.
Action:
None.
Reason:
The number of XFERSAPI threads that would have been started based on the CA Spool parameters and printer definitions has exceed the the maximum defined in the XFERTHCT parameter.
Action:
Each thread uses approximately 12K of storage above the line. Determine if there is enough storage available to increase the XFERTHCT parameter. If so, update that value and recycle. If not, investigate the use of the NODE parameter XFERNODE to eliminate threads for destinations that will never use the SAPI interface to receive files.
Reason:
A SAPI request made by CA Spool was flagged as an error with SSOBRETN=32 for an undefined destination or SSOBRETN=20 for an invalid destination. The SAPI interface stops requesting files for the destination that resulted in the error.
Action:
The interface continues without terminating. Determine why the destination specified in the message resulted in this error. Consider adjusting the XFERNODE settings on the NODE statement to permanently disable requests for this destination. If the reason for the failure is temporary, a REINIT command causes an attempt to request files for all eligible nodes again. This allows destinations to be defined to JES dynamically and processed by the CA Spool SAPI interface without a recycle.
Reason:
The security subtask is unable to establish an ESTAE environment. CA Spool terminates initialization.
Action:
Contact your systems programmer.
Reason:
The security subtask has abended. CA Spool continues running, but security requests which need to be checked by the security subtask will fail.
Action:
Stop and restart CA Spool as soon as possible. Keep the dump in order to find the reason for the abend.
Reason:
An invalid security request type was found in a security parameter list. The security subtask abends. CA Spool continues running, but security requests which need to be checked by the security subtask will fail.
Action:
Stop and restart CA Spool as soon as possible. Keep the dump in order to find the reason for the abend. If ESFSECU4 has been modified, then check for errors there.
This message number represents one of the following message formats; each format is related to Internal SAF:
Reason:
A user unknown to Internal SAF has attempted to access the system. The user is not logged-on to the Internal SAF system. Access may still be granted through an external security system.
Action:
Confirm that this message is to be expected by checking with the systems programmer.
Reason:
A user tried to logon to the ESF VTAM console, but entered an invalid password. Access is not granted to the user.
Action:
None.
Reason:
A user tried to access a resource, but no profile could be matched. If external checking must be performed for the same SAFTYPE, the external security system is checked. Otherwise, access will not be granted.
Action:
None.
Reason:
A user tried to access a resource, but the user's level is lower than the requested access. Access will not be granted.
Action:
None.
When XEQOPT=26 is set via ESFPARM.
Reason:
The CA Spool Sysout allocation interface has created a file with name oooooooo in the CA-Spool task using subsystem id ssss for destination dddddddd. It has been assigned file number nnnnnn.
Action:
None.
|
Copyright © 2011 CA.
All rights reserved.
|
|