Re: Need to record the timing of each CALL step in a batch job...

[Albert York <alfromme@xxxxxxxxx>]

I would not mess with the CALL command. You can get the machine in an
unmanageable state.

I would put something just before the call to log the time and program
name to a file.

Albert

On Wed, Dec 8, 2010 at 1:32 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
> I have a request to start tracking the time each step takes in a batch
> process...
>
> A manual process might be, to look through the job log for
>
> *NONE      Command                      12/08/10  02:29:44.407088
> QCLCLCPR     QSYS        04CB     FS001C      HLTHPRDPGM  0242
>                                     Message . . . . :    34100 - CALL
> PGM(PR002R)          /* The CALL command
>                                       contains parameters */
>
> *NONE      Command                      12/08/10  02:29:57.622312
> QCLCLCPR     QSYS        04CB     FS001C      HLTHPRDPGM  0251
>                                     Message . . . . :    34900 - CALL
> PGM(PR051R)          /* The CALL command
>                                       contains parameters */
>
> Obviously, a manual process would not be my prefer method, given that
> this needs to be done for multiple jobs and is not a one-time thing.
> Additionally, I need the specifics of the parameters used during the
> call.
>
> My thoughts
> 1) Use command exit point(s) process/log the CALLs, but it appears
> that CALL is one command for which the exit point is not envoked.
> 2) Replace CALL command with custom command whose CPP does the logging needed
> 3) DSPJOBLOG OUTPUT(*FILE) or maybe OUTPUT(*APIDFN) at the end of the
> process, but *FILE at least doesn't provide the parameters used during
> the call
> 4) List Job Log Messages (QMHLJOBL) API or Open List of Job Log
> Messages (QGYOLJBL) API, guessing that niether of these will have the
> parameter info I need either...
>
> So it appear that my only option is option 2....
>
> Does anybody have any thoughts, comments or alternatives?
>
> Thanks!
> Charles
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.