Problem:
In MVS JCL, the JCL processor finds procs that are used via the default system proclibs. In JCL, it is necessary to tell the JCL processor to look elsewhere, before it goes to the default system proclibs, via the JCL Lib statement.
Resolution:
By using the DSNDIR.MAP file, the "map" can designate a library to a directory. A JCLLIB statement in the JCL will cause the JCL Preprocessor to look in the "libraries"/directories which are contained on the JCLLIB statement.
Before Project is created:
One way is a direct mapping. When encountering the library, the project will look in this file to find the correct directory.
Create a DNSDIR.MAP file with the following information:
[DSNMAP] keyword
Name of the PDS referenced in the JCL = Path to be used instead of PDS
Example of a DSNDIR.MAP file:
[DSNMAP]
TEST1=D:\\TPS624X\\SAMPLES\\REVOLVE\\TEST1
TEST2=D:\\TPS624X\\SAMPLES\\REVOLVE\\TEST2
Another way to map a Library to a Directory is to use the USEBASE=1 Method. This means that the LIBARIES are actually directory names (as in Mellon's case) directly underneath the base directory.
[DSNBASE]
BASEDIR=X:\\
[DSNMAP]
USEBASE=1
This says that if the project looks at the X drive the project will find a directory named the same as the library.
Create Project:
Put the DSNDIR.MAP file in the project directory.
If a Shared Project is used, this has to be in the SHA folder as well.
Add JCL to the project.
Press DONE.
Press NO to pop up box
In Project Manager, highlight the JCL folder and press the OPTIONs icon, pressing YES to include all JCL files.
Check Process control-cards for all JCL that will use the DSNDIR translation. Press OK.
It is imperative to NOT add the control cards, or search paths for control-cards named in the DSNDIR.MAP file. If there are other control-cards that are being added the project that are not affected by the DSNDIR.MAP file, add them at this point before proceeding to next step.
MAKE the project.
#SupportTip
#EnterpriseAnalyzer