Re: IBM job scheduler

On 14 Mar 2013 11:27, rob@xxxxxxxxx wrote:

broehmer on 03/14/2013 12:14 PM wrote:

That brings up a point where if Michael only wants to hold the
scheduler for a specific period of time, then the HLDJOBSCDE would
work with a subsequent RLSJOBSCDE. If the intent is to carefully
reinstate the scheduler entries just the way the were, assuming that
some might be on hold already, then a program using QWCLSCDE would be
more appropriate.
Interesting problem.

This is the way we did it.

I supposed you could figure out some job scheduler job properties.
Renaming the job scheduler program may not be appropriate - an IPL
could be to apply ptfs and that program could be an object replaced
by that PTF.

Renaming a system program is inappropriate, probably especially so, one that is running in and controls a system job. However doing so probably would have no ill effects to the function, because the name of the object likely is of no consequence; i.e. likely will have no effect whatsoever because it is the address of the object, not the name, that implements the feature. Yet at PTF application or CHKPRDOPT, the system might balk at the /missing/ object. Renaming just seems like a really bad idea all around; i.e. likely *not* to effect what is desire, and likely to effect that which would be *undesirable* :-(