Re: Retiring a job from CA-7.



arrbee wrote:
Hi,

Can any of you please explain me what are all the things one must
consider or practice to retire a job from CA-7 job scheduler? What care
should be taken?

Forgive me if this topic is not covered in this forum.

Thanks for your time.

I assume you mean changing job schedules so that a particular job is no longer executed. While this is not a COBOL issue, many COBOL programmers must deal with job schedules that run their batch COBOL program. We used to have CA-7 and now have TWS/OPC. Seems to me in TWS we can mark a job "NOEX", which means it remains in the schedule as if it were still being executed, but it is not executed.

This is something I have frequently done, although I have to ask the operations staff to make the actual schedule changes, since I don't have authority to update job schedules.

You need to determine what jobs are triggered by the job you are removing. If you intend to remove job A, but Job A's successful completion triggers job B to run, you must arrange some other trigger to get Job B to run.

The more difficult problem is to determine if any output files created by Job A are used elsewhere. For this I generally run ISRSUPC scans or Endevor scans against prod proclibs and jcllibs. But a huge complication is that sometimes JCL symbolics can obsure the true dataset name. You need to make sure that no other jobs need any of the output files produced by Job A.

Then I just tell operations, "please remove Job A from all schedules where it is currently executed". Depending on your shop standards, there may be bureaucratic paperwork to fill out.

You should always have a backout plan, so if any problems occur you can restore Job A to the scheduler and also make up any missed work.

I hope that helps.


--
http://arnold.trembley.home.att.net/

.