Update your library and promotion process
If you use a library to maintain your program and a promotion process to move programs through levels of quality and testing, you might have to update these processes to ensure that z/OS® Debugger can find the files it needs to obtain information about your programs. For example, if your final production level does not have access to the same libraries as your development level, and you want to be able to debug programs that are in the final product level, you might need to update the environment in your final production level so that it can access to the following resources:
- All the data sets required to debug your program, for example, the source file, listing file, separate debug file, or EQALANGX file.
- Access to all the libraries required by your program or z/OS Debugger.
If you are using other Application Delivery Foundation for z/OS tools, see IBM® Application Delivery Foundation for z/OS Common Components Customization Guide and User Guide that correspond to the compilers or assembler that you are using. Those topics give instructions on which files to move through your levels so that the Application Delivery Foundation for z/OS tools can find the files they need.
If you manage your source code with
a library system that requires you specify the SUBSYS=ssss parameter
when you allocate a data set, you or your site need to specify the
EQAOPTS SUBSYS command, which provides the value
for ssss. You must do this for the following
types of programs:
- Enterprise PL/I program
that was compiled without the
SEPARATEsuboption ofTESTcompiler option - C/C++ programs
This support is not available for CICS® programs. To learn how to specify EQAOPTS commands, see the IBM z/OS Debugger Reference and Messages or the IBM z/OS Debugger Customization Guide.