Re: Brainstorming

[CRPence <CRPbottle@xxxxxxxxx>]

On 06 Jun 2013 12:20, John Allen wrote:
> Run the program in debug, add breakpoint where subfile is
> being loaded.
> When it breaks use DSPJOB and check the jobs library list
> and the open files and the overrides.
> Compare this on both systems

  FWiW: A job trace could provide trace data to identify the files [and 
members] that were opened, which could be compared between the two 
systems without having to use debug on the customer system [albeit if 
OPM programs, then debug breakpoints using instructions vs statements 
can also be done without debug capable programs].  The trace would not 
identify any overrides in effect [but would show an override command 
request in trace data], but it would show the effect of a member being 
opened, other than the one of the desired library or file.  The job 
trace would also show the program flow, which could also identify any 
differences in the programs being called; e.g. allowing identification 
of a program of the same name getting called from the wrong library 
[implied to be higher in the *LIBL for an unqualified call; hopefully 
unlikely], or perhaps just seeing that a program flow is different 
and\or unexpected as compared to the in-house version.

  Because the actual code and files from the customer system are on 
both systems, the comparison for program flow is best made with 
known-to-be identical copies of the code, thus making mismatches more 
conspicuous in a [side-by-side] compare of the [spooled] trace output.