Why are jobs LOCKED IN LOAD STATUS in CA WA CA 7 Edition?
If a job must have entered the queue but did not, look at the browse data set for messages produced during the time it would have entered the queue. If you see the message SP07-03, SATO-35, or SCNJ-15 saying that the job is in LOCKED STATUS, issue an LLOCK,JOB=* top line command. If the job is still in LOCKED status, a stated reason is present.
If the reason is LOCKED IN LOAD, the job needs a successful load before it schedules into the queue. Do a LOAD,JOB=jobname command. Let the load execute and the job flush from the request queue. Next, look at the browse file for a message of LOAD SUCCESSFUL or LOAD UNSUCCESSFUL. Usually, you can find the name of this file by looking for the ddname of BROWSE in the CA7ONL procedure.
If the load is successful, nothing else is required.
If the load is unsuccessful, the message gives insight as to what in the load data was not able to be added or updated in the database.
If you must get a successful load of a job and cannot readily fix the issue (perhaps the issue is with database size and you cannot REORG the database right now), you can do the following to get the job loaded. Do a LOADH on the job. Edit the QJCL, changing it to execute only an IEFBR14. Next, release the hold and let the LOAD continue with the updated JCL. When you can LOAD the real JCL for this job, fix the reason for unsuccessful LOAD.
Business Value:
Understanding how the load process works helps when troubleshooting an issue with load processing.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|