I would think client/server, or client requester for the enquiry end of the

In case I have my terminology wrong, what I mean is that, I would have a
process that allowed you to inquire or feedback the progress of the payroll
job IF someone wanted to track it or see where it was up to, but (unless I
am misunderstanding) you are proposing making the display part of the process.

What happens if the interactive portion of the program abends ? Will this
prevent anything continuing ?

Update a user space or something and allow some kind of on-going or one-off
enquiry to retrieve where the process is up to rather than communicating
directly with it. Write some kind of API to allow user jobs to retrieve the
process name and where the progress details are kept and display them if
thats what the user wants. Side effect is that more than one user can watch
the process :)

Is this something that is/should be an asynchronous process ?

Do you get what I mean or have I just sounded dense ? Am I using
terminology I'm not sure of ? :)

Evan Harris

>Nathan, Richard, all,
>I've used the data area technique in the past with a status of 1) need to run,
>2) am running, and 3) am done, for each step.  It worked great for an abend
>during any step and a programmed recovery/restart.
>That works well for the individual steps and the whole process.
>Back to my original question and the problem I'm trying to solve:  How do
>I lock
>up the work station, showing step progress bars, while submitting the whole
>process to batch to use the better CPW?
>"Nathan M. Andelin" wrote:
> >
> > As Richard Reeve suggested, having each batch program update a data area
> > (indicating progress), sounds like a good solution.  If the batch programs
> > are called from a CL program, the CL program can monitor for abnormal end
> > conditions and pass that event back to the interactive job via the data
> area
> > too.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.