Author: steve-myers
Posted: Thu Sep 15, 2016 11:12 am (GMT 5.5)
JCL Reference manual -
Something like this should work -
Just to be sure, in words, for the step testing the new module, prepare a STEPLIB DD statement that specifies the library containing the module you want to test followed by additional DD statements that reflect the libraries in the JOBLIB DD statement.
HTH
Posted: Thu Sep 15, 2016 11:12 am (GMT 5.5)
JCL Reference manual -
| Quote: |
| Use a JOBLIB DD statement to define a private library that the system is to use for an entire job. If you include a JOBLIB DD statement for the job and a STEPLIB DD statement for an individual job step, the system first searches the step library and then the system library for the program requested in the EXEC statement. The system ignores the JOBLIB library for that step. |
Something like this should work -
| Code: |
| //JOBLIB DD DISP=SHR,DSN=first-library // DD DISP=SHR,DSN=next-library // DD DISP=SHR,DSN=last-library //xxx EXEC PGM=program to test //STEPLIB DD DISP=SHR,DSN=library containing new version of module // DD DISP=SHR,DSN=first-library libraries in // DD DISP=SHR,DSN=next-library the JOBLIB // DD DISP=SHR,DSN=last-library |
HTH