Enhance JCL TYPRUN=SCAN testing to JES2 Symbol Replace in Instream Data

In z/OS 2.1 TYPRUN=SCAN finds more Job Errors if INTERPRET JES is activated in JESparm.

This is nice, but i´ld like to see an additional enhancement related to z/OS 2.1 JES2 Symbol Replacement in Instream Data using
//xyz DD *,SYMBOLS=(...)

TYPRUN=SCAN output only has the symbols resolved at conversion time in Jesjcl. Its more difficult to test symbol replace in instream data without submitting the real job.
If its a complex job there is no easy way to test this (only alternative tedious testing with iebgener steps etc.)

Enhancement Request:

I´d like to see another SCAN option , that also resolves all Instream data. This cannot be done at conversion time. A slim version of the job has to execute.

New Typrun Option e.g. TYPRUN=DRYRUN

JES should do the following with a JOB submitted with TYPRUN=DRYRUN

1) Internally do a TYPRUN=SCAN

2) If this results in error free jcl then continue with the following

* Remove all Conditional statements COND, IF/THEN from job

Dummy out or remove every Jobstep DD Statement except

a) Instream-Data DD *, and
b) MVS Datasets or Paths part of a concatenation that also has instream data

Change or add a hardcoded LOG-DD to every *,SYMBOL=(..) Statement and
add //LOGDD DD SYSOUT=* to every jobstep

Change every EXEC PGM= to EXEC PGM=IEAsomething (Program is
in SYS1.LINKLIB)

Submit this slim version of the job

This PGM IEAxxx should make a bpxwdyn Tiot scan and read all Instream-Data allocated in this jobstep and write it to a sysout and by doing this a Tailoring log is written to the LOG-DD.

Also if PARMDD is in Jobstep read the parm and put it to a sysout.

If such a job is running it does no production work. It only tests Symbol replacement