Re: Retiring a job from CA-7.
- From: "Hugh Candlin" <sure@xxxxxxxx>
- Date: Fri, 28 Apr 2006 05:38:34 GMT
"arrbee" <arrbee@xxxxxxxxx> wrote in message
news:1146124655.874355.49980@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,Whatever you come up with, it probably will not be enough.
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?
This is a process where you really cannot ask too many questions,
yet you probably won't ask enough, no matter how good you are.
Trust me.
The major steps seem to be fairly straightforward at first.
1 Identify jobs that this job is dependent upon.
2 Identify jobs that are dependent upon this job.
3 Identify flat files that are created by this job,
and determine if, and if so where, they need
to be created/catalogued in the future.
4 Identify flat files that are updated by this job,
and determine if, and if so where, they need
to be updated in the future.
5 Identify flat files that are deleted by this job,
and determine if, and if so where, they need
to be deleted/uncatalogued in the future.
6 Identify databases that are updated by this job,
and determine if, and if so where, they need
to be updated in the future.
7 Identify the reports produced, obtain their
distribution lists, and get the users to either
sign off on their discontinuation,
or affirm their continued need, in which case
you need to relocate that process to another job.
That's the easy parts. [I'm probably still a little
shell-shocked from the last time I shoehorned
on one of these projects, so I probably left
out an essential cog or three, but, never fear,
you should discover them during integration testing.]
Now you need to look at ALL of the jobs
that are dependent on this job completing,
and determine where you will relocate
essential file processing and database updates,
based on everything that you have learned
during your analysis.
Then [shudder], based upon the job restructuring
and reorganization that you have determined to be necessary,
you need to determine the new dependencies,
..
If there is one step in this process that will trip you up,
that is it.
Trust me.
Care should also be taken to communicate
your intention to all of the IT staff, secure
in the knowledge that someone is almost certain
to know of a fact that will become a showstopper
if you overlook it. Dare I say "when" instead?
Care should also be taken to communicate the proposed change
to the user community, as there may be surprising uses being made
of the outputs from that job that are not widely known within IT,
if at all. Do not forget to check with Audit and Legal.
Did I mention, do NOT forget to check with Audit and Legal.
Trust me.
You will of course work VERY closely with
the Master Scheduler at all times during this process.
He or she MAY get a little testy with you at the disruption
that you are introducing when you do, but that will pale
in comparison if you do NOT work very closely
with the Master Scheduler during this process.
Master Schedulers do not like surprises,
particularly ones which come with deadlines attached.
Trust me.
.
- References:
- Retiring a job from CA-7.
- From: arrbee
- Retiring a job from CA-7.
- Prev by Date: Re: Retiring a job from CA-7.
- Next by Date: Re: Beautify code
- Previous by thread: Re: Retiring a job from CA-7.
- Next by thread: Beautify code
- Index(es):
Relevant Pages
|
