Re: Pause technique

["Tom Jedrzejewicz" <tomjedrz@xxxxxxxxx>]

Given that the job runs only once a year and must be babysat anyway, I am
wondering why you are trying the mess with it.  What are you trying to
accomplish?  I strikes me that the amount of time you can save will be eaten
up pretty quickly in programming time.  It may take 10 years to return the
amount of time you spend automating this thing.

If the concern is running things out of order, you could add a data area
with sequence info, and processing to check the data area at the start of
each step and update it at the end of each step.  Then have the CL read the
data, run the next step based on the data area and exit. Effectively, you
call the same CL repeatedly, and it will execute only the next step, and you
can move the status data area back if necessary.

Pseudo code for a 3 step chain ...
===========
Read the status data area

If DA = COMPLETE
 notify user process has already been done
 exit

If DA = LAST
 call laststep program
 set DA to COMPLETE
 exit

if DA = MIDDLE
 call middlestep program
 set DA to LAST
 exit

if DA = FIRST
 call first step program
 set DA to MIDDLE
 exit

if DA is anything else
 notify user process of an error
 exit
==============

You could also soft code the status values into a file with the program to
call and the next status to set.

===========
Read the status data area

Read the status code file  (values: status code, program, next status code)
if not found in status code file
 notify user of an error
 exit
else
 call program
 set DA to next status code
 exit

==============

Take care.

On 9/27/06, Greg Wenzloff <GWenzloff@xxxxxxxxxxx> wrote:
> I've got a multi step job that is run only once at the end of each
> fiscal year (this weekend).   Each step updates data related to standard
> costs.   Each subsequent step is dependant on the success of the one
> before it and I need to verify this by examining the data at each step
> else I can end up with a real mess.
>
> The job is designed to run in batch mode although it could be run
> interactively since I will be the only one on the computer when it is
> run.
>
> My question is what is a simple technique to pause the CLP after each
> step of the job?
>
> If I set it to run interactively I could add a simple program to put up
> a display file which waits for the Enter key.   But I would like to keep
> this in batch mode for speed.
>
> Any suggestions?    Simple is better.
>
> Thanks,
> Greg