How to load Symbolic Information from Endevor, Librarian and Panvalet for Testing Tools
Article ID: 27718
Updated On:
Products
Issue/Introduction
Integration between Mainframe testing tools and with Life cycle management products helps to ensure that user is working with the best set of symbolic information available.
Powerful integration between these products simplifies the transfer of symbolic information from your Endevor listings library to your PROTSYM file(s).
The PROTSYM file is the VSAM repository for symbolic information used by:
- InterTest for CICS
- InterTest Batch
- SymDump for CICS
- SymDump Batch
- Optimizer/II
Since these testing tools share a common set of symbolic utilities, it is easy to master the techniques for loading symbolic information.
Once stored in the PROTSYM file, symbolic information can be accessed from any of the testing and fault management tools to enhance
debugging sessions, abend reports or performance analysis.
To populate the PROTSYM file with symbolic information, COBOL, PL/I and Assembler listings may be loaded from any number of input sources.
Common types of input sources include temporary files, sequential files, and partitioned data sets.
For customers who license any of the following life cycle management solutions, listings can be directly loaded from listing libraries either automatically or in batch
using utilities described below. This loading process can be automated, managed through a batch utility or performed on an ad-hoc basis using symbolic utilities:
- Endevor
- Librarian
- Panvalet
Resolution
For example, when using Endevor to create and store listings, there is several options for loading these listings into the PROTSYM file.
- Modify Processors
Many administrators modify processors to load listings into the PROTSYM file.
This is the easiest method to load symbolic information because, once this is set up, all the symbolic information is loaded automatically.
This means users utilizing the symbolic information can be assured that the information is current and consistently maintained.
With this method, it is probably not needed to save compiler listings permanently since the listings will be stored in compressed format in the PROTSYM file.
- Use Batch Utility
Some users choose to save all compiler listings in Endevor and elect not modify processors as described above.
Since the testing and fault management tools each provide a symbolic library loader for batch, loading the symbolic information into the PROTSYM file is as easy as submitting a batch job.
The name of the symbolic library loader is called IN25SYMD. This utility allows to load individual members, groups of members, or the entire contents of the Endevor listing library.
Simply identify the library type as "NDV" for Endevor and the loading process is as easy as loading information from a PDS.
- Utilize Symbolic Utilities
For customers that use Optimizer/II, SymDump Batch, or InterTest Batch, symbolic utilities are provided with the TSO/ISPF interface to make loading the PROTSYM file very convenient.
These symbolic utilities allow to list, view and update the symbolic files with just a few simple key strokes.
First, identify the library type as "NDV" for Endevor, then load one or more members whenever needed - on demand.
The flexibility of this technique makes it extremely effective for adding symbolic information to the SymDump Batch abend reports,
for debugging a subroutine with InterTest Batch, or for viewing execution counts and timings with Optimizer/II on an 'ad-hoc' basis.
Mainframe testing and fault management tools contain a common set of symbolic utilities, allowing direct access to the listings from any of these products,
regardless of the method you choose to load the symbolic information.
Additional Information
For more information about the symbolic utilities or maintaining your PROTSYM files, please refer to the INTERTEST™ AND SYMDUMP® - Symbolic Support guide.
Feedback
