Reason:
A SUBSYS request has been passed to a subsystem-support converter function, and a logical error was detected during modification of the internal text. The SUBSYS request is not processed.
Action:
Contact your systems programmer.
Reason:
The SUBSYS request could not be processed because no storage was available in subpool 230. The SUBSYS request is rejected.
Action:
Contact your systems programmer.
Reason:
DD SUBSYS sub-parameter number 1 or the ESFALLOC CLASS parameter is not valid. Valid output classes are A-Z, 0-9, or national characters. The allocation request is rejected.
Action:
Correct the sub-parameter in the SUBSYS parameter or the ESFALLOC operand.
Reason:
A sequence number was assumed to be specified in the first sub-parameter of the SUBSYS request or as a sub-parameter of the SEQNR keyword parameter of ESFALLOC, but the format was invalid. The allocation request is rejected (JCL error).
Action:
Correct the sequence number.
Reason:
The SUBSYS sub-parameter number 4 or the ESFALLOC parameter FORM specifying the forms number is invalid. The value must be expressed as alphanumeric or national characters. The allocation request is rejected (JCL error).
Action:
Correct the forms specification.
Reason:
The SUBSYS sub-parameter number 2 or the ESFALLOC OWNER parameter specifying the owner name is invalid. Only alphanumeric or national characters are valid. The allocation request is rejected (JCL error).
Action:
Correct the owner name, then rerun the job.
Reason:
A SUBSYS/ESFALLOC request was passed to CA SPOOL, but no destination was specified, in either the SUBSYS sub-parameter number 3 or the DEST parameter on the DD statement (JCL allocation only), or the specified destination is invalid (JCL allocation and ESFALLOC requests). If present, xxxxxxxx specifies the invalid destination name. The allocation request is rejected (JCL error).
Action:
Correct the DD statement to specify a valid destination name, either in the SUBSYS sub-parameter or in the DEST parameter.
Reason:
The SUBSYS parameter number 13 specifying the RETAIN time is invalid. The allocation request is rejected.
Action:
Correct the sub-parameter field and then rerun the job.
Reason:
The system-affinity name in the SUBSYS sub-parameter number 5 or in the ESFALLOC AFFINITY operand is invalid. Valid characters are alphanumeric or national characters. The allocation request is rejected (JCL error).
Action:
Correct the system-affinity name, then rerun the job.
Reason:
The SUBSYS request specifies more than 13 sub-parameters. The SUBSYS request is rejected (JCL error).
Action:
Remove the extra sub-parameters and then rerun the job.
Reason:
During allocation processing of the SUBSYS request CA Spool detected that the CA Spool subsystem was not active. The SUBSYS request were rejected (JCL error).
Action:
Start the CA Spool subsystem and then rerun the job.
Reason:
The SUBSYS/ESFALLOC request was rejected by the interface exit. The allocation request is rejected (JCL error).
Action:
Contact your systems programmer.
Reason:
During allocation processing, the allocation function was unable to locate the interface exit in LPA/MLPA. The SUBSYS request(s) were the rejected (JCL error).
Action:
Make sure that the CA Spool subsystem is properly started, then rerun the job. If problems still exist, contact your systems programmer.
Reason:
CA Spool was not active at allocation time. The system operator was asked to start CA Spool but canceled this job instead. The SUBSYS request was rejected (JCL error).
Action:
Make sure the CA Spool subsystem is started; then rerun the job.
Reason:
The SUBSYS sub-parameter specifying the user field cannot contain more than 4 characters. The SUBSYS request is rejected (JCL error).
Action:
Correct the user field, then rerun the job.
Reason:
The SUBSYS sub-parameter number 8 must be omitted or specified as HOLD. The SUBSYS request is rejected (JCL error).
Action:
Correct the sub-parameter field and then rerun the job.
Reason:
The SUBSYS sub-parameter number 9 must be omitted or specified as DELETE. The SUBSYS request is rejected (JCL error).
Action:
Correct the sub-parameter field, then rerun the job.
Reason:
The SUBSYS sub-parameter number 10 or the ESFALLOC FCB parameter, specifying the FCB name, is invalid. The allocation request is rejected (JCL error).
Action:
Correct the sub-parameter field and then rerun the job.
Reason:
The SUBSYS sub-parameter number 11 or the ESFALLOC COPIES parameter, specifying the copy count, is invalid. The parameter must be specified as 1 to 3 numeric characters in the range 1 to 255. The allocation request is rejected (JCL error).
Action:
Correct the sub-parameter field, then rerun the job.
Reason:
The SUBSYS sub-parameter number 12 or the ESFALLOC OUTLIM parameter, specifying the output limit, is invalid. The parameter must be specified as 1 to 8 numeric characters in the range 1 to 16777215. The allocation request is rejected (JCL error).
Action:
Correct the sub-parameter field, then rerun the job.
Reason:
The SUBSYS-allocation request could not be processed, because the CA Spool file to be read could not be properly opened or closed. The allocation request is rejected (JCL error). xx is replaced by the error code returned from the ESFOPEN or ESFCLOS routine.
Action:
Interpret the return code from the ESFOPEN/ESFCLOS routine and take appropriate action.
Reason:
Job jjjjjjjj requests allocation of file ffffffff to the subsystem ssss, but subsystem ssss is not active. If the reply is CANCEL, the job will be terminated with a JCL error. If the reply is WAIT, the allocation function goes into a loop for 5 minutes testing each minute to see if the subsystem has been started. If it has been started, the allocation processing continues. If it has not been started, this message will be issued again. This is repeated 5 times before the job is terminated with a JCL error. The allocation function enters wait state until the operator enters the reply.
Action:
Reply CANCEL if subsystem ssss cannot be started in the next 5 to 10 minutes. Reply WAIT if you are just about to start subsystem ssss.
Reason:
The interface exit has redirected the file ffffffff to be allocated to subsystem ssss instead of the one requested in the SUBSYS parameter. Processing continues.
Action:
None.
Reason:
An error was detected during processing of an OUTPUT JCL reference. The allocation request is rejected (JCL error).
Action:
Specify a valid OUTPUT reference, then rerun the job.
Reason:
The subsystem data set allocation request could not be processed successfully. xxxx-xxxx are the S99ERROR and S99INFO codes from the DYNALLOC request block. A description of these codes can be found in the OS manual Authorized Assembler Programming Guide. Processing is terminated.
Action:
Interpret the codes returned and take appropriate action.
Reason:
An ESFALLOC command was issued, but the first positional operand, specifying the DDname to be assigned to the data set, is not valid. The allocation request is not processed.
Action:
Correct the parameter, then retry the request.
Reason:
An ESFALLOC command was issued, but the first positional operand, specifying the DDname to be assigned, already has an allocation associated with it. The allocation request is not processed.
Action:
Free the current allocation (use the FREE FILE (ddname) command), or select another name for the file.
Reason:
The ESFALLOC command processor could not issue the STAX macro to catch later attention interrupts (PA1). The allocation request is not processed.
Action:
Consult your systems programmer.
Reason:
The PARSE service routines did not complete successfully because of a no-storage condition. The allocation request is not processed.
Action:
Increase the SIZE operand on the LOGON request or contact your systems programmer.
Reason:
The PARSE service routines returned a completion code indicating a programming error in ESFALLOC. The allocation request is not processed.
Action:
Save the issued calling sequence and contact your systems programmer.
Reason:
The file named in the LIKE operand of ESFALLOC is not a CA Spool subsystem data set. The allocation request is not processed.
Action:
Omit the LIKE operand or specify the DDname of a CA Spool subsystem data set allocated either by ESFALLOC or allocated in the LOGON procedure.
Reason:
The file named in the LIKE operand of ESFALLOC is not allocated; that is, a DD statement is missing. The allocation request is not processed.
Action:
Omit the LIKE operand, or specify the DDname of a CA Spool-subsystem data set allocated either by ESFALLOC or allocated in the LOGON procedure.
Reason:
The subsystem name specified in the SUBSYS parameter of ESFALLOC is not an active CA Spool-subsystem. The allocation request is not processed.
Action:
Specify an active CA Spool subsystem name in the SUBSYS operand or allow the value to default.
Reason:
ESFALLOC found no active CA Spool subsystem to process the allocation request. The allocation request is not processed.
Action:
Contact your systems programmer.
Reason:
The subsystem which you have named in the SUBSYS operand of ESFALLOC is not a CA Spool-subsystem. The allocation request is not processed.
Action:
Specify the name of a CA Spool subsystem or allow the parameter to default.
Reason:
The CA Spool subsystem specified in the SUBSYS operand of ESFALLOC is not started or is terminating, or the subsystem interface has been halted. The allocation request is not processed.
Action:
Select another CA Spool subsystem or allow the subsystem name to default.
Reason:
It was not possible to determine from the combination of specified parameters of ESFALLOC if an input data set or an output data set was to be allocated. This will be the case if you, for example, specify CLASS together with SEQNR. CLASS assigns an output attribute, and SEQNR specifies the number of an existing file. The allocation request is not processed.
Action:
Specify parameters applicable to the type of data set you require allocated.
Reason:
The CA Spool subsystem has not responded to an allocation request for 60 seconds. In rare instances, multiple abends in CA subtasks could leave the region active, but unable to respond to sysout allocation requests. This WTOR will be issued for each new request that occurs when this condition is encountered, unless an H response is received or the problem condition clears.
Action:
Before replying, the status of the CA Spool task must be investigated.
A reply of 'C' continues the attempt to process the sysout allocation attempt. The task issuing this WTOR must be monitored to be sure that continued processing is successful.
A reply of 'H' disables the CA Spool Sysout Allocation intercept globally and current and future allocations are skipped. Sysout files are written to the JES spool until HS and SS commands are issued or a recycle of the CA Spool task is done. Any files that are bypassed due to this action can be processed by the XFERSAPI interface after the problem condition is identified and resolved.
Note: To begin monitoring the Sysout Allocation response time so that a decision can be made to issue ESF538, XEQOPT=29 must be specified in the ESFPARM file.
Reason:
During SUBSYS de-allocation of the file ffffffff, a permanent close is performed for the file. This permanent close could not be done because subsystem ssss was not active. Processing terminates.
Action:
Restart the CA Spool subsystem.
Reason:
During de-allocation a permanent close is to be performed for the file ffffffff. To do this, the de-allocation function needs storage for a parameter list, but this storage could not be obtained. Processing terminates; no permanent close is affected.
Action:
Contact your systems programmer.
Reason:
During de-allocation a permanent close is to be performed for the file using the normal CA Spool close interface. CA Spool was unable to close the file and returned a return code cc. Processing terminates; the file is not permanently closed.
Action:
Contact your systems programmer.
Reason:
During de-allocation a permanent close is to be performed, but the interface exit rejected the close request. Processing terminates; no close is done.
Action:
Contact your systems programmer.
Reason:
During de-allocation a permanent close is to be performed, and if the file has been temporarily closed, it is necessary to reopen the file before the permanent close can be done. For some reason CA Spool could not reopen the file and returned return code cc to describe the error. Processing terminates and the file remains temporarily closed.
Action:
Contact your systems programmer.
Reason:
File ffffffff could not be opened because subsystem ssss was not active. Processing terminates.
Action:
Start subsystem ssss and then rerun the job.
Reason:
No storage was available to build a CA Spool open parmlist for this SUBSYS request. Processing terminates.
Action:
Contact your systems programmer.
Reason:
The CA Spool open failed for the file associated with DD statement dddddddd, for CA Spool subsystem ssss. The file being created did not have enough USERDATA space to store all OUTPUT statement USERDATA and MAIL parameters. The file was not created in CA Spool.
Action:
Review the job that created the file, to determine how to reduce its USERDATA or MAIL parameter requirements and fit into the 960 byte USERDATA area.
Reason:
CA Spool was unable to open the file for this subsystem request. xxx will contain a 3-byte identification of the field in error, if the return code is PE. Processing terminates.
Action:
Contact your systems programmer.
Reason:
An error was detected during open processing of file ffffffff. Processing terminates.
The reason code explains the error:
Action:
Correct the problem or contact the systems programmer.
Reason:
The interface exit rejected the open request for file ffffffff. Processing terminates.
Action:
Contact your systems programmer.
Reason:
A non-zero return code was received from an SJFREQ macro during the processing of an OUTPUT JCL statement reference. Processing terminates.
Action:
Check that the OUTPUT reference is valid.
Reason:
During close processing of a SUBSYS file, only a temporary close is performed for the file. This temporary close could not be done because subsystem ssss was not active. Processing terminates.
Action:
Restart the CA Spool subsystem.
Reason:
During close of a SUBSYS request, only a temporary close is performed. For some reason CA Spool was unable to close the file and returned a return code cc. Processing terminates, the file is not temporarily closed.
Action:
Contact your systems programmer.
Reason:
The interface exit rejected the temporary- close request. Processing terminates, no temporary close is performed.
Action:
Contact your systems programmer.
Reason:
A start-SUBSYS-interface command has been rejected because the interface is already active. Processing continues.
Action:
None.
Reason:
A start-SUBSYS-interface command has been successfully completed. The SUBSYS-parameter-interface is started.
Action:
None.
Reason:
A halt-SUBSYS-interface command has been rejected because the interface is already halted. Processing continues.
Action:
None.
Reason:
A halt-SUBSYS-interface command has been successfully completed. The SUBSYS-parameter interface is stopped.
Action:
None.
Reason:
The subsystem support module has received a subsystem request not supported by CA Spool. If an SVC DUMP was taken, register 10 points to the SSOB requesting the function not supported. If no SVC DUMP was taken, the reason is that no storage was available for work areas. Processing continues and the request is rejected.
Action:
Contact your systems programmer.
|
Copyright © 2011 CA.
All rights reserved.
|
|