Reason:
The job was not entered into the request queue because the JCL could not be attached. kkkk indicates the reason, as follows:
Empty member.
Member not found on CA Workload Automation SE CA Librarian or CA Panvalet for z/OS libraries; or JCL INDEX not specified. Also, if a CA Workload Automation SE CA Librarian or CA Panvalet for z/OS data set, it has been unavailable for two minutes. Also, a ++INCLUDE may be referring to an invalid name.
JCL data set not found on DASD volume.
JCL data set is not a PDS - invalid DSORG.
JCL data set has invalid DCB attributes.
JCL data set resides on a DASD volume not accessible to CA Workload Automation SE.
JCL member not found in data set.
READ I/O error was encountered.
JCL data set is READ password protected.
JCL data set is USERID protected or CA Workload Automation SE does not have access to the JCL data set when external security is used for data sets.
Data set is busy.
Dynamic allocation for JCL data set failed.
Error occurred during OPEN. The DCBABCOD field is nonzero.
JCLID is not in the product's initialization file.
Problem with interface to CA Librarian or CA Panvalet for z/OS.
EOF reached in SQADD. The job may have too many lines of JCL for CA Workload Automation SE to put in the Trailer queue (31 track maximum).
Error on TRLQ.
Error loading module SASSPCEJ. Return code from SLOAD macro is in the first two characters.
Bad SLINK to SASSPCEJ. See also 0490 and 0890.
SASSXX05 determined job should be canceled.
Error in SASSXX05 - invalid return code.
Invalid data on # statement.
JCL attach rejected by user exit SASSXX11 with a return code of 4. Job will be flagged for retry if the RETRY interval option is specified on the SCHEDULE statement in the initialization file. If the RETRY option is not specified, the job will be left in SKELETON status.
JCL attach rejected by user exit SASSXX11 with a return code other than 4. Job will be left in SKELETON status.
Error return from SASSPCEJ indicating invalid conversion request.
Out of space in TRLQ.
Error return from SASSPCEJ indicating invalid conversion request.
Action:
Determine the reason for the problem and correct it, if possible. If the job must run this cycle, it must be demanded unless the job's status is RETRY on an LQ display. The following list shows corrective action for the messages keyed to the codes shown in the previous list.
Try LLIB command for a more detailed error message and try JCL panel (DB.7 - fill in the panel for a more detailed error message).
Verify that the data set in on the volume requested. Specify the correct volume if in error.
Data set organization must be PS or PO. If PDS, the member name must be provided.
Either BLKSIZE=0 or KEYLEN=0 or RECFM not = F or LRECL not = 80.
No //U7volser DD statement exists for the volume where the data set resides. Supply a //U7volser DD statement in the CA Workload Automation SE execution JCL. The ALLOC command may be issued to make the volume available.
Provide a valid member name.
Try again. If the problem persists, contact your installation specialist for assistance.
This update would require a WTOR reply from the system operator's console which would put CA Workload Automation SE in a hard wait; that is, no terminal processing, job scheduling, job submittal, and so forth, until the operator responded. Updates to such a data set are not allowed from CA Workload Automation SE. The update must be made from outside of CA Workload Automation SE by using TSO, batch, and so forth, so as not to impede production scheduling.
1) This request has violated User Security as defined in the module referenced by the USER keyword of the SECURITY statement in the CA Workload Automation SE initialization file. Use a different operator ID at logon time or change the USER ID Security module.
2) CA Workload Automation SE does not have access to the JCL data set.
Wait and try again. If the problem persists, contact your installation specialist for assistance.
Try to edit the JCL using the DB.7 panel. Error messages should be returned with codes indicating the specific problem.
Check the MVS console log for errors at the time the job came into the request queue.
Use the LJOB command to check the JCLID defined for the job then use /DISPLAY,ST=JCL to verify the IDs defined to CA Workload Automation SE. Correct the job definition or add the JCL definition to the initialization file and restart CA Workload Automation SE using WARM.
Try to demand the job identified by using DEMANDH so that it will be in HOLD status and can be canceled if necessary. You may want to specify the SCHID and DOTM values if the job needs to run. If the error repeats, the DEMAND command will produce messages to explain the error.
Take the same action as in code 0084 above.
Verify that module SASSPCEJ is in a library pointed to by STEPLIB. Take the same action as in code 0084.
Take same action as in code 008C above.
If you want the job, use DEMAND command. You may want to check with your installation specialist as to why the exit (SASSXX05) canceled the job.
Take same action as in code 0094 above.
Use QM.5 panel to examine and correct any errors on Special Override (#) statements in the JCL.
Probably none. If the JCL retry option is specified, JCL attach will be attempted at the next retry interval. This will continue until the exit accepts the JCL attach or the job is canceled. If the job must be scheduled, check with your installation specialist concerning the SASSXX11 exit and why it is preventing JCL for this job to be attached.
Because the job is left in SKELETON status, it must be canceled to remove it from the request queue. If it must be scheduled, try using the DEMAND command. If the reason for JCL attach rejection is not clear, you should check with your installation specialist concerning the SASSXX11 exit.
Take same action as in code 0090 above.
If the error occurred while attaching the JCL, issue a /DISPLAY,Q=TRL and check the space availability. If the number of tracks is low, increase the size of the Trailer queue, at a convenient time, using the DMPQ/MOVQ shutdown and startup facility.
Take same action as in code 0090 above.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|