Improve how JCL procedures are located with the Debug Tool Batch JCL Utility

Improve how JCL procedures are located with the Debug Tool Batch JCL Utility
DTSU and the IBM Debug Tool Batch JCL Utility do not resolve the location of procedure libraries the same as JCL/JES does.

Consider the following scenario:

A job is submitted with a JES2 Statement below:

/*JOBPARM PROCLIB=PROC01

Where the PROC01 refers to a ddname defined by JES2. PROC01 may define libraries such as:

SYS3.TEST.PROCLIB
SYS2.PROCLIB
etc.

Another job is submitted with
/*JOBPARM PROCLIB=PROC02 where PROC02 defines the procs
SYS3.QA.PROCLIB
SYS3.PROCLIB
SYS4.PROCLIB

Defining the system procedures in the member SEQATLIB(EQAZPROC) does not satisfy the requirement, since the proc MYPROC may be different in SYS3.TEST.PROCLIB as it would in SYS3.QA.PROCLIB.

The Debug Tool utility should recognize PROC01 DD statement, and resolve it from JES3, or at least mimic the resolution using Debug Tool installation tables.

Consider the second scenario:
LPAR1 has the system procs defined as

SYS3.TEST.PROCLIB
SYS3.PROD.PROCLIB

LPAR2 has the system procs defined as

SYS3.PROD.PROCLIB

Other products, such as Fault Analyzer uses the &SYSCLONE variable to define separate IDICNFxx parameters. Something similar could be done for Debug Tool to identify the correct proc libraries by LPAR for the IBM Debug Tool, where the SYSCLONE variable determines the correct set of procedure libraries to use for the LPAR. It would be best if procedure libraries did not have to be defined via Debug Tool, but were derived in the same fashion as done when JCL submitted. One solution is to submit the job with TYPRUN=SCAN, capture the job from the output manager (SDSF?), and retrieve the message IEFC001I PROCEDURE JIMCOBBA WAS EXPANDED USING PRIVATE LIBRARY xxxxxxxxxx