Author: Bill Woodger
Subject: Reply to: How to supply called sub-program from test loadlib
Posted: Thu Sep 15, 2016 12:53 am (GMT 5.5)
Perhaps I was unclear:
So, although you can have both, for any given step, only one will be used. So you can't have a test module from a test library and the rest from production by using JOBLIB and STEPLIB (which is the task at hand). Only one is relevant for each step.
Note that in the quote, three libraries are being talked about. The "system library" you get for free.
Subject: Reply to: How to supply called sub-program from test loadlib
Posted: Thu Sep 15, 2016 12:53 am (GMT 5.5)
Perhaps I was unclear:
| 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. |
So, although you can have both, for any given step, only one will be used. So you can't have a test module from a test library and the rest from production by using JOBLIB and STEPLIB (which is the task at hand). Only one is relevant for each step.
Note that in the quote, three libraries are being talked about. The "system library" you get for free.