InterTest™ and SymDump ® 11.0
This job allocates your zFS data sets.
c.Open the SAMPJCL member AVH06MKD in an edit session and execute the AVHSEDIT macro from the command
line.
AVH06MKD is customized.
d.Submit AVH06MKD.
This job creates all directories and mounts the file system.
5.Open the SAMPJCL member AVH10CSI in an edit session and execute the AVHSEDIT macro from the command line.
AVH10CSI is customized.
6.Submit AVH10CSI.
This job produces the following results:
–Defines the CSI data set.
–Allocates the SMPPTS and SMPLOG data sets.
–Initializes the global, target, and distribution zones.
–The DDDEF entries for your product are created.
–The DDDEFs for the required SMP/E data sets are created.
7.Complete the following steps to add the DDDEFs that are required for the zFS file system to your SMP/E environment:
WARNING
If the following member does not exist in SAMPJCL, ignore this step. This step does not apply to your
product. Go to Run the Installation Jobs for a Pax Installation.
a.Open the SAMPJCL member AVH15CSU in an edit session and execute the AVHSEDIT macro from the command
line.
AVH15CSU is customized.
b.Submit AVH15CSU.
This job customizes the CSI by adding the DDDEFs associated with the directory.
You are now ready run the installation jobs that are used to receive, apply, and accept SMP/E base functions. Go to Run
the Installation Jobs for a Pax Installation.
Run the Installation Jobs for a Pax Installation


the Installation Jobs for a Pax Installation.
Run the Installation Jobs for a Pax Installation
The members in the following procedure are used to receive, apply, and accept SMP/E base functions. Submit and run
these SAMPJCL members in sequence. Do not proceed with any job until the previous job has completed successfully.
NOTE
The following steps include instructions to execute the AVHSEDIT macro each time that you open a new
SAMPJCL member. To edit all SAMPJCL members simultaneously, read and follow the instructions in the
AVHAREAD member, and submit the AVHEDALL member.
1.Open the SAMPJCL member AVH20RCB in an edit session, and execute the AVHSEDIT macro from the command
line.
AVH20RCB is customized.
NOTE
To include optional components, uncomment the applicable FMID in the customized job.
2.Submit AVH20RCB to receive SMP/E base functions.
Your product is received and now resides in the global zone.
3.Open the SAMPJCL member AVH30APB in an edit session, and execute the AVHSEDIT macro from the command
line.
AVH30APB is customized.
4.Submit AVH30APB to apply SMP/E base functions with the CHECK option.
a.Note any unresolved errors.
b.Verify that resolving PTFs are applied before implementing products in production.
c.After successful completion, rerun APPLY with the CHECK option removed.
 131


InterTest™ and SymDump ® 11.0
Your product is applied and now resides in the target libraries.
5.Open the SAMPJCL member AVH40ACB in an edit session, and execute the AVHSEDIT macro from the command
line.
AVH40ACB is customized.
6.Submit AVH40ACB to accept SMP/E base functions with the CHECK option. After successful completion, rerun
ACCEPT with the CHECK option removed.
Your product is accepted and now resides in the distribution libraries.
You can now clean up the USS directory (optional) or apply preventive maintenance as described in Maintain Products
using SMP/E JCL.
Clean Up the USS Directory
This procedure is optional. If you decide to perform this procedure, do so after you complete the installation process and
when you do not need the installation files. When this procedure is done, you are ready to install preventive maintenance.
To free file system disk space for subsequent downloads after downloading and processing the pax files for your
Broadcom  mainframe product, remove files from your USS directory and delete unnecessary z/OS data sets. You can
delete the following items:
•Pax file
•Product-specific directory that the pax command created and all the files in it
•SMP/E RELFILEs, SMPMCS, and HOLDDATA MVS data sets. These data sets have the HLQ that you assigned in the
UNZIPJCL job.
NOTE
Retain non-SMP/E installation data sets such as yourHLQ .INSTALL.NOTES for future reference.
1.Navigate to your Pax ESD USS directory.
Your view is of the applicable USS directory.
2.Delete the pax file by entering the following command:
rm paxfile
paxfile Specifies the name of the product pax file that you downloaded.
The pax file is deleted.


The pax file is deleted.
3.Delete the product-specific directory by entering the following command:
rm -r product-specific-directory
product-specific-
directorySpecifies the product-specific directory that you created previously using the pax command or sample
JCL.
The product-specific directory is deleted.
NOTE
You can also use TSO ISHELL to navigate to the pax file and product-specific directory, and delete them using
the D line command.
When you are done with this step, you are ready to install maintenance.
Configuring
Configure InterTest and SymDump  products.
This article contains information about the steps you need to take to configure InterTest and SymDump  products. To
configure your product, follow the instructions in either Configure Your Product With CSM  or Configure Your Product
Without CSM .
 132


InterTest™ and SymDump ® 11.0
IMPORTANT
For consistent product behavior when you upgrade to a newer InterTest release, ensure that you:
•Carry your configurations forward to the new version.
•Review the configuration checklists for each product to determine which features apply to your site.
Configuration Best Practices
This article contains configuration best practices for your product.
Symbolic Files
Before you configure your Broadcom  testing tool product, carefully consider how to best organize your symbolic
information that is stored in your PROTSYM files. Well-organized symbolic information allows for the most effective and
efficient access to your symbolics during testing.
There is no best way to organize symbolic information that works for everyone. How your symbolic information is
organized depends on your environments, your application systems, and the number of programs and programmers
involved in your testing. Consider the following guidelines when you plan for symbolic support:
•In a production environment , consider maintaining a separate PROTSYM file for each application system that can be
shared by all of your programmers. Because only one copy of each program is typical in a production environment, the
same symbolic information could be shared by any programmer debugging in that environment.
In production environments, symbolic information is often limited to a single version of each program, and testing or
debugging is typically less frequent and often limited to critical, real-time failures. Separate, shared PROTSYM files
allow you to maintain a single set of symbolic information for each production application system that is accessible if
there is a failure.
•In a test environment , multiple versions of the same program are more likely to exist, and shared executable libraries
are complimented by sandbox libraries that house test fixes or works in progress. For this environment, a single shared
symbolic repository is adequate for the shared executables. However, each programmer might want to own their


symbolic repository is adequate for the shared executables. However, each programmer might want to own their
own PROTSYM file. This arrangement provides programmers with the freedom to test using the correct symbolic
information without impacting other team members.
Business Value:
Well-organized symbolic information lets your application programmers easily locate, access, and share symbolic
information for their programs. The result is improved performance for your Broadcom  testing tools, optimal use of your
DASD space, and optimum productivity for your application programmers.
Additional Considerations:
Generally, think of your PROTSYM files as nothing more than a match for your load libraries, remembering that for each
unique version of a load module you may require symbolic information for testing or debugging. Like the load libraries
that exist at each level or stage of your development environment, the corresponding symbolic files should vary in size
depending on the maximum number of programs that are expected at each level, with the individual PROTSYM files being
the smallest by far.
If you are also licensed for Endevor  Software Change Manager ( Endevor ), Broadcom  testing tools provide an extra level
of automation through dynamic symbolic support. This feature lets you populate your PROTSYM file dynamically on
demand with symbolic information for programs built using Endevor .
We recommend that you set the threshold for used space in the symbolic file to monitor the space utilization percentage.
When the threshold is reached, a message indicates that the symbolic file is almost full. Set the threshold by specifying
the USEDSPACEMSG parameter with the INITIALIZE or UPDATE functions of IN25UTIL.
More Information:
For more information about creating, populating, maintaining, and using your PROTSYM symbolic repositories to enhance
your testing, see Symbolic Support which is provided with each Broadcom  testing tool product.
 133


InterTest™ and SymDump ® 11.0
For more information about dynamic symbolic support, see Installing .
Dynamic Symbolic Support for Endevor
If you are licensed for Endevor  Software Change Manager ( Endevor ), Broadcom  recommends using the dynamic
symbolic support feature that is provided by the Broadcom  testing tools. This feature allows you to populate your
PROTSYM file dynamically on demand with symbolic information for programs built using Endevor .
Because there multiple ways to maintain the content of your PROTSYM files, you may encounter the situation where you
have multiple versions of the same program for which you need to locate and select the correct symbolic information.
Dynamic symbolic support gives you the option to create your symbolic information only when it is needed, rather than
always reloading your PROTSYM file after each compilation or assembly. This can save you time, CPU utilization, and
even DASD space.
Business Value:
The dynamic symbolic support feature is available with many of Broadcom  testing tool products including InterTest Batch,
InterTest for CICS, SymDump  Batch, and SymDump  for CICS. This feature simplifies the setup requirements for using
symbolic support, while simultaneously eliminating most potential associated setup errors. By improving the accuracy
of your symbolic file content, and eliminating common setup errors, dynamic symbolic support greatly increases the
productivity of your programmers.
Additional Considerations:
Dynamic symbolic support requires that you compile or assemble your applications using an Endevor  process with the
footprint feature active. When symbolic information is required by one of the Broadcom  testing tools, your PROTSYM
files are inspected first for the matching symbolic information. When no matching information is found, the executable
is inspected for an Endevor  footprint. If this footprint is found, that footprint is used to locate the matching listing that


is dynamically loaded into your specified PROTSYM file. The matching symbolic information is then used by your test
session.
For specific instructions related to setting up and using dynamic symbolic support, see Installing and Batch Debugging.
Starting and Stopping InterTest for CICS in a CICS Region
To ensure that the CICS global user exits required by InterTest are the first to receive control, Broadcom  recommends that
customers start InterTest for CICS during CICS PLT processing.
Business Value:
This practice ensures that other global user exits do not interfere with InterTest for CICS when the product makes a
decision to monitor or debug a CICS program.
More Information:
For more information on starting InterTest for CICS, during CICS PLT processing, see Activate Your Product.
Performance Considerations for CICS Regions Using DB2
SymDump  recommends that customers starting InterTest or SymDump for CICS in a region with DB2 activity reviews the
XRMIO option and sets the option according to their needs.
When the XRMIO option is set to YES (the default), InterTest and SymDump for CICS provides additional diagnostic
information about the application by using the CORE=LASTSQL command. This command causes InterTest and
SymDump for CICS to display the last SQL statement executed by the application. However, if you set XRMIO to YES and
the applications that run in your CICS region heavily use EXEC SQL calls, performance in that region might degrade.
Business Value:
 134


InterTest™ and SymDump ® 11.0
Although using the XRMIOUT global user exit from IBM can affect performance in regions that use EXEC SQL calls
extensively, this exit can provide valuable diagnostic information for DB2 applications that contain EXEC SQL statements.
This information can be useful in identifying or resolving problems and improve time to resolution.
Additional Considerations:
You must carefully weigh the value of the information you receive against the performance considerations of using
XRMIOUT in regions where heavy DB2 activity exists. Especially in production regions where performance is most critical,
consider carefully whether the additional diagnostic information provided by XRMIOUT is valuable enough to risk the
possible performance impact of using this option where extensive DB2 activity exists.
SymDump  Batch Installation with Other SVC 51 Intercepts
If you have multiple products that use an intercept for SVC 51, run CAIRIM to initialize SymDump  Batch after all other
products.
Business Value:
Initializing SymDump  Batch after all other products have been initialized helps ensure that SymDump  Batch gets control
first. This enables the most accurate analysis and reporting possible before interference occurs.
Additional Considerations:
When SymDump  Batch is initialized, it replaces the address of SVC 51, the DUMP SVC. When the product is finished with
its reporting, it takes one of the following actions, depending on the SymDump option.
•If the SymDump option is OFF, control is returned to the operating system.
•If the SymDump option is ON, control is given to the address that was replaced when SymDump  Batch was initialized.
Therefore, if another product, such as SymDump  System, that intercepts SVC 51 was initialized before SymDump  Batch,
that product does not get control unless the SymDump option is set to ON.
SymDump  Batch PRTLIB Repositories Management


SymDump  Batch PRTLIB Repositories Management
When you configure SymDump  Batch, you must set your default PRTLIB. The PRTLIB repository is the VSAM data set
that maintains your abend reports. You can have one repository for multiple z/OS systems, or one per system. However,
care must be taken to determine if your installation requires the use of more than one PRTLIB.
Business Value:
Well-managed repositories let your application programmers easily locate, access, and share abend reports for their
applications. You can use multiple repositories per system with the use of multiple default tables, or by using a user exit.
As a result, you get better performance from your Broadcom  testing tools, optimal use of your DASD space, and the best
possible productivity for your application programmers.
Additional Considerations:
When SymDump  Batch is configured, the default PRTLIB data set is defined with the PRTLIB option of CAOETABL.
However, not all installations may prefer writing all abend reports to one repository. Specific installations may want a few
groups to write to a specific repository. To provide this flexibility, you can override the PRTLIB value in several ways.
•Use the existing user exit, CAOCUPRT to return the PRTLIB to use based on JOBNAME, STEPNAME, abending
program name, and USERID.
•Define the PRTLIB by specifying a PRTLIB value in your CAIOPTS DD within the job step JCL.
•Allocate the CAIOPTS DD dynamically for each user by following the naming convention userid.CAIOPTS.
Repository Maintenance
Use the following SymDump  Batch options to automatically manage aspects of PRTLIB repository maintenance:
 135


InterTest™ and SymDump ® 11.0
•Set the PRTLHCT of CAOETABL to receive notification when the PRTLIB reaches the designated percentage full
•Set the DUPLIM of CAOUDFRX to eliminate duplicate reports
•Set the EXPDAYS of CAOUDFRX to delete expired reports.
More information:
For specific instructions on setting up the user exit CAOCUPRT, the PRTLIB option, or dynamic allocation of your
CAIOPTS data set, see Installing and Batch Abend Analysis.
SymDump  for CICS PROTDMP Files
You can view transaction dumps from multiple CICS regions using a single dump viewing CICS region. Because the
SymDump  for CICS dump viewer runs as a CICS transaction, it is possible to view dumps from multiple CICS regions
from a single dump viewing region. To do this, add remote CICS file definitions for the dump data sets from all CICS
regions.
NOTE
The CICS releases for all related dump data sets must match the dump viewing region. You cannot mix dump
data sets from different CICS releases in the same dump viewing region.
Business Value:
By providing access to dumps from multiple CICS regions through a single viewing region, SymDump  for CICS simplifies
the process of locating dumps and ensures that dumps remain available even when the CICS region in which those
dumps were produced becomes unavailable. This improves programmer productivity, reduces time to resolution, and
helps to control or eliminate costly down time .
More Information:
For more information on creating PROTDMP files and estimating their size, see Allocate Files. For more information on
maintaining and reporting on the contents of your PROTDMP files, see Batch Utility.
Configure an InterTest and SymDump Software Instance Using z/OSMF
Workflows


Configure an InterTest and SymDump Software Instance Using z/OSMF
Workflows
Instructions to configure InterTest and SymDump product instances using z/OSMF Workflows.
As a systems programmer, security administrator, or someone responsible for managing the configuration of your z/OS
systems, you can use z/OSMF workflows to configure a product software instance with less effort, time, and mainframe
expertise. The workflows guide you through the configuration process and help automate configuration of a product
instance. This approach significantly reduces the time that is required to perform configuration tasks.
During installation of your product using z/OSMF Deployments, you can execute z/OSMF configuration workflows
to configure the product software instance. Alternatively, you can execute the product configuration workflows after
installation from the Workflows page or software instance in z/OSMF Software Management as shown in the following
procedures. You can also use these procedures to configure a software instance that is installed using native SMP/E or
CSM  or to re-execute a workflow that was initially executed during installation using z/OSMF Deployments.
To configure a software instance using z/OSMF workflows:
•Address prerequisites
•Register z/OSMF workflows
•Execute z/OSMF workflows
When these tasks are completed, the product or component is ready for use on the system where the software instance
was configured.
Address Prerequisites
 136


InterTest™ and SymDump ® 11.0
Before you begin this process:
•Ensure that your site has configured z/OSMF as described in the IBM Knowledge Center and addressed the z/OSMF
security requirements for ACF2 , Top Secret, or IBM RACF  as applicable. Appropriate permissions are required to
register and execute workflows and add software instances in z/OSMF.
•If you installed using CSM  or native SMP/E JCL, register your SMP/E environment (CSI) as a software instance in z/
OSMF. To do so, see Adding software instances  in the IBM Knowledge Center documentation.
•Apply all z/OSMF related product maintenance to ensure that all defined workflows are available for use. Workflows
are provided as part of a portable software instance or through PTF maintenance.
Register z/OSMF Workflows
Before you can execute a workflow that you acquired through PTF maintenance, register it in z/OSMF. Experienced
system programmers typically perform this task.
NOTE
If you have already downloaded and installed a portable software instance using z/OSMF Deployments, the
workflows are included and already registered. Skip this task.
To register the workflows, gather the fully qualified name of the workflow definition file (.xml) and optional workflow
variable input file (.properties). These files typically reside in the SMP/E target zFS file system that was mounted during
installation. You can use these files to customize product software instances and to automate workflow execution, saving
time and effort when deploying multiple standardized product software instances.
Use either  of the following procedures to add a new workflow instance in z/OSMF:
•Register Workflows from a Software Instance
•Register Workflows from the Workflows Task
NOTE
For more information about registering the workflows, see Create a workflow  in the IBM Knowledge Center
documentation.


documentation.
Register Workflows from a Software Instance
Use the following procedure to register workflows from an existing software instance in z/OSMF.
Follow these steps:
1.Log in to z/OSMF and go to Software , Software Management , and select Software Instances .
2.Right-click your software instance from the list and select Modify  from the Actions menu.
3.Select the Workflows tab, and select Add from the Actions menu.
4.Specify the following values:
–Specify the sequence in which the workflow should be performed.
–Specify the workflow name and description.
–Indicate whether the workflow steps must be performed on the host system or whether they can be performed on
another system in the same sysplex.
–Specify the location of the workflow definition file. The workflow is located in the SMP/E target library and includes
your three-character product identifier in the workflow name. Include the SMP/E element type and name for your
product or the location of the partitioned data set member, sequential data set, or UNIX file.
5.Select OK.
The workflow is available for execution. Go to Execute z/OSMF Workflows.
Register Workflows from the Workflows Task
Use the following procedure to register workflows from the Workflows task in z/OSMF.
 137


InterTest™ and SymDump ® 11.0
Follow these steps:
1.Select Workflows in z/OSMF.
2.Select Create Workflow from the Actions  menu.
The Create Workflow panel appears.
3.Specify the following values:
–Specify the path to the following files:
•Workflow Definition File
The workflow is located in the SMP/E target library, hlq.CAVHXML(CAVHWCNF).
•(Optional) Workflow Variable Input File
NOTE
Specify a value for this field only when you have predefined the values by editing the .properties file
manually. Editing the .properties file lets you customize the product configurations and establish the
operational settings that are processed when the product starts. For example, the data set name prefix
to be used for the final configured run-time libraries and the serial number (VOLSER) of the volume on
which the data sets are to be allocated.
–Select the system where the workflow resides. This system is where the workflow steps are performed.
4.Select Next .
5.Complete the following fields:
–Specify a unique name for the workflow.
–Select or enter an Owner user ID  for the workflow, and select Assign all steps to owner user ID .
6.Select Finish .
The workflow is available for execution. Go to Execute z/OSMF Workflows.
Execute z/OSMF Workflows
The following procedure describes how to execute the workflow steps to complete the configuration of your product
software instance. z/OSMF presents the workflow customization steps in sequence and guides you through the required
steps and changes. When you complete all workflows, the product is ready for use.
You can execute z/OSMF workflows from an existing software instance or from the Workflows task.
NOTE
Before you execute the workflow steps, provide a valid JOB statement that includes your ACCOUNTINFO and


NOTE
Before you execute the workflow steps, provide a valid JOB statement that includes your ACCOUNTINFO and
MSGCLASS information. To prevent errors, do not use the default MSGCLASS value. For more information
about customizing the JOB statement for z/OSMF workflows, see the IBM documentation.
Follow these steps:
1.Complete either  of the following steps:
–Select the software instance that you want to configure from the Software Instances page in z/OSMF ( Software
Management, Software Instances ). Right-click the software instance, and select Perform Workflows from the
Actions menu.
The registered workflows for the software instance display.
–Select Workflows to display the existing workflows for your installation. Sort the workflows by product using the
Configure Columns  action to display product information (name, ID, and version).
The available workflow instances display.
2.Select the workflow that you want to execute.
The required execution steps display.
3.Execute the steps in order. Select Refresh  until the job completes. A return code of zero (0) is expected.
For general information about how to execute z/OSMF workflow steps, refer to the IBM documentation.
4.Repeat steps 2 and 3 for each required workflow.
When all workflows are executed, the software instance is configured and you are ready to start using the product or
component.
 138


InterTest™ and SymDump ® 11.0
Configure Your Product With CSM
This article describes the manual tasks you perform when configuring your product using CSM .
Data sets are created by CSM  after successfully completing each step, that is the SMP/E installation, deployment, and
configuration procedures.
NOTE
Broadcom  strongly advises that you perform the initial installation and configuration of your product and its
components in a test environment as a precaution. This testing will let you detect any possible conflicts with
other vendor products.
Configure the Deployed Product
Configuration is a process of copying the deployed libraries to run-time libraries and customizes the product for your
site to bring it to an executable state. You can configure Broadcom  products that you have already acquired, installed,
and deployed using CSM . You cannot use CSM  to configure a product unless you have already used CSM  to deploy the
product.
You perform the following high-level tasks to configure your products using CSM :
1.Select a configurable deployment on the Deployments tab to view details and products for that deployment.
2.Select a product in the deployment and start the Configuration wizard to create a configuration. Complete each of
the steps in the wizard. The wizard has multiple levels of detailed instructions and guides you through choosing
configuration settings for your site. At any point, you can save your work and can come back to it later. Configurations
where you have partially completed the steps in the wizard are listed on the Configurations tab. The steps in the
wizard include the following:
a.Define a configuration name and select a system for the configuration.
b.Select configuration functions and options.
c.Define system preferences.
d.Create target settings.
e.Select and edit resources.
3.Build the configuration. The last step of the Configuration wizard lets you build the configuration. If needed, you can


edit the configuration and can build the configuration again. Building the configuration closes the wizard and creates a
configuration with all your settings.
4.(Optional) Validate the configuration. Validation verifies access to resources that are going to be used when you
implement the configuration.
5.Implement the configuration. You implement a configuration to make your deployed software fully functional.
Implementation executes on the destination system, applying the variables, resources, and operations that are defined
in the configuration.
CSM  configures the product.
After the configuration process completes, the product is ready for you to use.
InterTest Batch Tasks
Configure the external tasks for InterTest Batch.
Follow these steps:
1.APF authorize the application runtime load library. For more information, see the Activate Batch Link article.
2.Allocate a profile data set for each user. Required, if the USERPROFLIBS configuration options is selected. If the
USERPROFLIBS option is not selected, a single PROFLIB will be created automatically. For more information, see
Allocate Files.
3.Allow users to concurrently update PROTSYM files. Required, if the NEWPROTSYM option is selected.
 139


InterTest™ and SymDump ® 11.0
4.Allocate an ALIB for each user.  Required, if both the ALIB and USERALIBS configuration options are selected or you
will be using the Foreground debugging feature.
5.Allocate an INCLUDE library for each user. Required, if both the INCLIB and USERINLIBS options are selected.
6.(Optional) Add the product to the ISPF main menu. For more information, see Batch Interfaces and Compatibility.
7.Add InterTest Batch to your TSO logon procedure.
8.(Optional) Customize Roscoe  for use with the application.
9.Customize the application started task for Endevor  Dynamic Symbolic Support. For more information, see Interfaces
and Compatibility.
NOTE
Required, if the MULTNDVRSITES option is selected, indicating that the customer is using multiple Endevor
site IDs.
10.(Optional) Update the OS/VS COBOL procedure, COBINT and compile, bind, and post-process the OS/VS COBOL
foreground demonstration program, CAMRCOB.
NOTE
Required, if the COBOL configuration option is selected and the customer still compiles with the OS/VS
COBOL compiler.
Activate Batch Link
This operation updates your CAS9 procedure and PARMLIB then executes the CAS9 procedure to activate Batch Link.
Use the following procedure to activate the Batch Link feature of InterTest Batch.
Follow these steps:
1.Add and APF-authorize the InterTest Batch runtime load libraries (CAI.CAVHAUTH and CAI.CAVHLOAD) to the
STEPLIB concatenation in your CAS9 procedure.
NOTE
All customized configuration elements must be available through STEPLIB.
2.Add the following control card to the member or data set pointed to by the PARMLIB DD in your CAS9 procedure:


PRODUCT(CA INTERTEST/SYMDUMP) VERSION(VHA0) INIT(CAVHINIT) PARM(220)
3.Execute CAIRIM using your CAS9 procedure.
You have activated Batch link.
MSM can execute this step automatically during the implementation process when you change the default value of
Manual operation to Automatic operation before releasing it. Otherwise, specify Confirm manual operation when you
implement the configuration.
SymDump  Batch Tasks
Follow these steps to configure the external tasks for SymDump  Batch:
1.Allow Concurrent Updates to Symbolic Files.
2.Customize for Dynamic Symbolic Support.
3.Add Support for File Master Plus .
4.Review Language Environment (LE) Considerations.
5.Add Runtime Load Library to LNKLST.
6.APF-Authorize Runtime Load Library.
7.Activate SymDump  Batch.
8.Establish Access to the TSO Facility.
 140


InterTest™ and SymDump ® 11.0
Allow Concurrent Updates to Symbolic Files
The MVS RESERVE and DEQ macros are used to allow sharing of a PROTSYM file between regions or systems. The
resource major name used in the RESERVE and DEQ macros is INTERTST. Place the major name INTERTST into an
MVS service that converts the RESERVE into a cross-system ENQ if this service is available at your site.
Customize for Dynamic Symbolic Support
If you are an existing Endevor  user and the FOOTPRINT feature is used when applications programs are generated in
Endevor , you can customize Endevor  for dynamic symbolic support by editing the started task procedure.
NOTE
This step is not required if you have only one C1DEFLTS.
Follow these steps:
1.Use the CAI.CAVHJCL member INTNDVR, the started task procedure, to access DSS to dynamically load program
symbolic information.
This started task must be an APF-authorized task.
2.Modify this procedure to conform to your installation standards.
3.Copy the procedure to a system procedure library.
The member name of the procedure must have the Endevor  C1DEFLTS table site ID appended to it. For example, if
the site ID is 3, the procedure member name should be INTNDVR3.
The first seven-character prefix of the procedure member name you copied to the system procedure library must
match the value defined in the NDVRPROC option in CAOUDFRX.
NOTE
Create a procedure for each unique site ID.
Add Support for File Master Plus
If you are an existing File Master Plus  user and want to use the FM viewer command, you must perform the following
additional set up. Before you can use FM viewer command you must perform the following procedure.


additional set up. Before you can use FM viewer command you must perform the following procedure.
Follow these steps:
1.Set up the File Master Plus  to use LIBDEFs (LIBALLOC='Y').
2.Verify that the FM1 executable exists in a data set allocated to SYSPROC or SYSEXEC.
3.Allocate CAI.CAVHCLS0 to SYSPROC or SYSEXEC.
Review Language Environment (LE) Considerations
Use the following procedure to add abnormal termination exit entry for CAOECEEX.
Follow these steps:
1.Edit CEE.SCEESAMP(CEEEXTAN).
2.Follow the instructions in this member to add an abnormal termination exit entry for CAOECEEX.
3.Apply the applicable SYSMOD to make these changes take effect.
NOTE
For more information about the CEEEXTAN exit, see the IBM z/OS Language Environment Customization
guide.
 141


InterTest™ and SymDump ® 11.0
Add Runtime Load Library to LNKLST
Add the SymDump  Batch runtime load library, CAI.CAVHLOAD, to the LNKLST concatenation. This can be done
dynamically by creating and activating a new LNKLST set. For example, a new LNKLST set called LNKLST01 can be
created by copying the existing set, LNKLST00, and adding CAI.CAVHLOAD to the end of the concatenation.
Follow these steps:
1. SETPROG LNKLST,DEFINE,NAME=LNKLST01,COPYFROM=LNKLST00
2. SETPROG LNKLST,ADD,NAME=LNKLST01,DSNAME=CAI.CAVHLOAD,ATBOTTOM
3. SETPROG LNKLST,ACTIVATE,NAME=LNKLST01
The PROGxx or LNKLSTxx member of SYS1.PARMLIB should be updated to permanently add CAI.CAVHLOAD to the
IPL LNKLST set at the desired location in the concatenation.
APF-Authorize Runtime Load Library
To APF-authorize the SymDump  Batch runtime load library, add an entry for CAI.CAVHAUTH to member IEAAPFxx of
SYS1.PARMLIB.
NOTE
Authorization does not take effect until the next IPL.
Activate SymDump  Batch
Follow these steps:
1.Add the SymDump  Batch load library CAI.CAVHAUTH to the STEPLIB concatenation in your CAS9 procedure
(SYS1.PROCLIB(CAS9)).
2.Add the following control card to the member or data set pointed by the PARMLIB DD (in SYS1.PROCLIB(CAS9)):


PRODUCT(CA INTERTEST/SYMDUMP) VERSION(VHA0) INIT(CAVHINIT) PARM(220)
3.Execute CAIRIM using the CAS9 procedure.
Establish Access to the TSO Facility
You must include the SymDump  Batch ISPF libraries in your session ISPF files concatenation to access the SymDump
Batch panels. Use the following procedure to concatenate the ISPF file and tailor the Master panel.
Follow these steps:
1.Concatenate the following data sets into the indicated ddnames (if they were not previously concatenated):
Data Set Name DDName Description
CAI.CAVHPNL0 ISPPLIB ISPF panels for SymDump  Batch
CAI.CAVHSKL0 ISPSLIB ISPF skeletons for SymDump  Batch
CAI.CAVHMSG0 ISPMLIB ISPF messages for SymDump  Batch
CAI.CAVHTBL0 ISPTLIB ISPF tables for SymDump  Batch
CAI.CAVHCLS0 SYSPROC ISPF CLISTs for SymDump  Batch
CAI.CAVHLOAD ISPLLIB or STEPLIB SymDump  Batch Load Library
2.Perform the following steps if your site uses variable-length CLISTs:
a.Execute CAI.CAVHJCL(CARXCNVT) to change the CLISTs from fixed to variable length format.
b.Point the SYSPROC DD to the CAI.VCAICLIB data set (instead of CAI.CAVHCLS0).
 142


InterTest™ and SymDump ® 11.0
3.Allocate the following data sets into the indicated ddname (if they were not previously allocated):
Data Set Name DDName Description
CAI.CAVHTBL0 CAOEXTBL ISPF tables for SymDump  Batch
CAI.CAVHHELP CAOIHELP ISPF Help library
You have now placed the SymDump  Batch ISPF libraries into your session ISPF files concatenation.
To tailor the ISPF Master panel, do one of the following
•Copy the ISP@MSTR panel supplied with SymDump  Batch (named CARXSBA0)
•Add new lines to your existing ISP@MSTR panel.
Use the following procedure to add new lines to your existing panel.
Follow these steps:
1.Add the first line after the last option selection displayed on the panel.
2.Define this line as an option number for the user to select with a brief description of the function. For example:
% 6 +CA SYMDUMP BATCH - Options Panels
% 7 +CA SYMDUMP BATCH - Invoke the CAIPRINT Repository Viewer
3.Add the lines containing the commands required to execute the options to the list of &SEL variables defined at the end
of the panel. For example:
6. 'PANEL(CAOEP001) NEWAPPL(CA$Z)'
7, 'PGM(CAOIF000) NEWAPPL(CAOI)'
InterTest for CICS Tasks
We recommend that you configure your product using CSM .
When you configure your product using CSM , perform the manual tasks described in following procedure to configure
the external tasks. Data sets are created by CSM  after successfully completing each step that is the SMP/E installation,
deployment, and configuration procedures.
Follow these steps:
1.Allow concurrent updates to symbolic files.


deployment, and configuration procedures.
Follow these steps:
1.Allow concurrent updates to symbolic files.
The MVS RESERVE and DEQ macros are used to allow sharing of a PROTSYM file between regions or systems. The
resource major name used in the RESERVE and DEQ macros is INTERTST. Place the major name INTERTST into an
MVS service that converts the RESERVE into a cross-system ENQ if this service is available at your site.
2.Customize for Dynamic Symbolic Support.
a.Edit member INTNDVR of the Broadcom  Testing and Fault Management common runtime procedure library
(CAI.CAVHPROC), modify it to conform to your installation standards, then save it.
b.To create a started task for an Endevor  site ID, copy INTNDVR to a system procedure library as member
INTNDVRn, where n is the Endevor  C1DEFLTS table site ID. Create a procedure for each unique Endevor  site ID.
NOTE
The INTNDVRn procedures require read security access to any load library data sets in which application
programs that were created by Endevor  reside and which may require symbolic support for debugging with
InterTest for CICS. They also require write security access to any PROTSYM files they will populate.
3.Add CCI spawn parameters.
This step adds the CCI spawn parameters for the InterTest for CICS dynamic symbolic support feature to the JCL
procedure used to start CAIENF. If you want this step to be executed automatically by CSM , use the 'Action' button to
change it from a 'Manual' to an 'Automatic' operation before releasing it at implementation time.
To perform this step manually, add the following DD statement to the SPNPARMS DD in the JCL procedure used to
start CAIENF:
 143


InterTest™ and SymDump ® 11.0
    // DD DISP=SHR,DSN=avhproclib(INDVSPWN)
4.Refresh CAIENF.
Schedule a refresh of CAIENF to activate the CCI spawn parameters for InterTest for CICS dynamic symbolic support
of Endevor . The dynamic symbolic support feature will not be available until CAIENF has been refreshed.
5.Update CICS startup JCL and restart CICS.
NOTE
If your site has previously installed SymDump  for CICS as a separate product, some DD statements may
already exist.
If you use DD statements in your CICS startup JCL, your InterTest for CICS files, as defined in the CSD, require
DD statements in the JCL for CICS. DISP=SHR must be specified for PROTSYM to allow batch compiles to run
concurrently with CICS. Alternatively, you may directly add the data set names to the CEDA FILE definition, defined in
the CSDINT member in CAI.CAVHJCL and remove the DD statements for those files.Add the following DD statements
to your CICS startup JCL:
//PROTCPF DD DSN=CAI.PROTCPF,DISP=OLD
//PROTSYM DD DSN=CAI.PROTSYM,DISP=SHR
//PROTHLF DD DSN=CAI.CAVHHLF,DISP=SHR
//PROTUHF DD DSN=CAI.PROTUHF,DISP=SHR
//PROTMLOG DD DSN=CAI.PROTMLOG,DISP=SHR
If you are using the InterTest for CICS dynamic symbolic support feature for Endevor , add an NDVRSYM DD


statement to specify the PROTSYM file to be used for dynamic symbolic loading. The NDVRSYM DD must be
specified in the CICS startup JCL for InterTest for CICS to invoke the dynamic symbolic load option. A sample
NDVRSYM DD statement follows:
//NDVRSYM DD DSN=CAI.PROTSYM,DISP=SHR
If you specified more than one symbolic file in the SYMFIL variable of the IN25OPTS variable group, include a DD for
each SYMFIL specified.
Add both InterTest for CICS load library and the symbolic common component load library to the DFHRPL in the CICS
startup JCL:
// DD DSN=CAI.CAVHLOAD,DISP=SHR
If you execute the demo programs, add the following DD to the DFHRPL in your CICS startup JCL to specify the same
load library data set name that you used when you ran the demo program's compile and link JCL:
// DD DSN=CAI.demoload,DISP=SHR
NOTE
InterTest for CICS makes calls to IEWBIND when using the online COMPOSITE module command and
IEWBIND requires about 750 KB of below the line storage. To ensure there is sufficient storage available
(below the line for IEWBIND calls), you must ensure that your DSALIM is at least 750 KB less than your
below the line private area size. Failure to do this could result in S0F4 and U900 abends in your CICS region
during dump capture.
SymDump  for CICS Tasks
This section describes the manual tasks that you perform when configuring SymDump  for CICS (SYMC) using CSM .
Follow these steps:
1.(Optional) Add CCI Spawn Parameters.


Follow these steps:
1.(Optional) Add CCI Spawn Parameters.
This step is only required if the ENDEVOR option is selected. This step adds the CCI spawn parameters for the
InterTest for CICS dynamic symbolic support feature to the JCL procedure used to start CAIENF. If you want this step
to be executed automatically by CSM , use the Action button to change it from a ‘Manual’ to an ‘Automatic’ operation
before releasing it at implementation time.
To perform the step manually, add the following DD statement to the SPNPARMS DD in the JCL procedure used to
start CAIENF:
 144


InterTest™ and SymDump ® 11.0
// DD DISP=SHR,DSN=CAI.CAVHPROC(INDVSPWN)
2.(Optional) Refresh CAIENF.
This step is only required if the ENDEVOR option is selected. Schedule a refresh of CAIENF to activate the CCI spawn
parameter for InterTest for CICS dynamic symbolic support of Endevor . The dynamic symbolic support feature will not
be available until CAIENF has been refreshed.
3.Install or Customize DFHPEP.
If your site does not have a custom DFHPEP module implemented, the DFHPEP included in the product load library
must be installed in a library concatenated before the IBM CICS library suffixed with SDFHLOAD, so that it replaces
the IBM supplied dummy version of DFHPEP. If your site already uses a customized DFHPEP it should be customized
and relinked to include the following source statement:
EXEC CICS LINK PROGRAM('IN25PEP')
Using the supplied copy of DFHPEP or customizing your own DFHPEP to link to IN25PEP is not a hard requirement
for installation of SymDump  for CICS. The dump capture still functions without DFHPEP/IN25PEP processing.
However the failure to configure DFHPEP as suggested previously prevents capture of the last screen display in an
MRO environment.
4.Update CICS Startup JCL and Restart CICS.
NOTE
If your site has previously installed InterTest for CICS as a separate product, some DD statements may
already exist.
If you use DD statements in your CICS startup JCL, your SymDump  for CICS files, as defined in the CSD, require


DD statements in the JCL for CICS. DISP=SHR must be specified for PROTSYM to allow batch compiles to run
concurrently with CICS. Alternatively, you may add the dataset names directly to the CEDA FILE definition defined in
the CSDSYM member in CAI.CAVHJCL and remove the DD statements for those files.
Add the following DD statements to your CICS startup JCL:
//PROTDMP  DD DSN=CAI.PROTDMP,DISP=SHR
//PROTSYM  DD DSN=CAI.PROTSYM,DISP=SHR
//PROTHLF  DD DSN=CAI.CAVHHLF,DISP=SHR
//PROTUHF  DD DSN=CAI.PROTUHF,DISP=SHR
//PROTMLOG DD DSN=CAI.PROTMLOG,DISP=SHR
If you are using the InterTest for CICS dynamic symbolic support feature for Endevor , add an NDVRSYM DD
statement to specify the PROTSYM file to be used for dynamic symbolic loading. The NDVRSYM DD must be
specified in the CICS startup JCL for InterTest for CICS to invoke the dynamic symbolic load option. A sample
NDVRSYM DD statement follows:
//NDVRSYM  DD DSN=CAI.PROTSYM,DISP=SHR
NOTE
To view dumps from another concurrently active CICS region, each region must have its own SymDump  for
CICS file. In addition, the region used to view the dumps must have a separate FCT entry for each dump file.
If you specified more than one symbolic file in the SYMFIL variable of IN25OPTS, include a DD for each SYMFIL
specified.


specified.
Add the SymDump  for CICS load library to the DFHRPL in the CICS startup JCL.
//   DD DSN=CAI.CAVHLOAD,DISP=SHR         <productname>
NOTE
SymDump  for CICS makes calls to IEWBIND when using the online COMPOSITE module command and
IEWBIND requires about 750 KB of below the line storage. To make sure that there is sufficient storage
available (below the line for IEWBIND calls), you must verify that your DSALIM is at least 750 KB less than
your below the line private area size. Failure to do this may result in S0F4 and U900 abends in your CICS
region during dump capture.
When you have completed the changes to your CICS startup JCL, restart the CICS region.
 145


InterTest™ and SymDump ® 11.0
Configure Your Product Without CSM
Configure your product manually without CSM .
While we recommend that you use CSM  to configure your product, you can also configure your product manually. This
section describes the tasks you need to configure your product without CSM . Click on the link for the product that you are
configuring to see the tasks for that product.
Configuring SymDump  for CICS
After you complete the installation process, configure SymDump  for CICS using CSM  or using the manual process
outlined in this article.
Follow these steps to manually configure your installation of SymDump  for CICS:
1.Customize Global Options  in CAVHCONF.
2.Configure the default SymDump  for CICS options .
3.Configure the dump capture  options.
4.Configure external security options  in CAVHCONF.
5.Define the SymDump  for CICS user exits .
6.Allocate files.
7.Configure dynamic symbolic support.
8.Customize the following options:
–DB2 support
–Language Environment (LE)
–DSA limit parameters
–CICS JCL and startup parameters
–CICS resource definitions
–Assembler DSECTs
–DFHPEP
9.Review Performance Considerations under CICS Interfaces and Compatibility .
10.Activate your product.
11.Verify your installation
Configuring InterTest for CICS
After you complete the installation process, configure InterTest for CICS using CSM  or using the manual process outlined
in this article.
Follow these steps to manually configure your installation of InterTest for CICS:
1.Customize  Global Options  in CAVHCONF.
2.Configure the default CICS options
3.Configure the InterTest for CICS options
4.Configure external security options  in CAVHCONF.


4.Configure external security options  in CAVHCONF.
5.Define the InterTest for CICS user exits.
6.Allocate files.
7.Configure dynamic symbolic support.
8.Customize the following options:
 146


InterTest™ and SymDump ® 11.0
–DB2 support
–DSA limit parameters
–CICS JCL and startup parameters
–CICS resource definitions
–Assembler DSECTs
9.Customize the following interface and compatibility options for InterTest for CICS :
–PROMMAC macro
–CNTL commands
–Calls to software and macro support
–DB2 support for InterTest for CICS
–Wild branch handling
–Add COBOL file structures to the symbolic file
–User-defined CORE commands
–HOGAN software support
–EDF support
–MRO support
10.Review performance considerations.
11.Activate your product.
12.Verify your installation.
Configuring SymDump  Batch
After you complete the installation process, configure SymDump  Batch using CSM  or using the manual process outlined
in this article.
Follow these steps to manually configure your installation of SymDump  Batch:
1.Customize Global Options  in CAVHCONF.
2.Configure the default SymDump  Batch Options .
3.Configure external security options  in CAVHCONF.
4.Define the SymDump  Batch user exits .
5.Allocate files.
6.Configure dynamic symbolic support.
7.Customize the following Interfaces and Compatibility  options:
–DB2 support
–Language Environment (LE)
–CLISTs
–ISPF main panel
–Log and notify procedures
–Netman
8.Activate your product.
9.Verify your installation.
Configuring InterTest Batch
After you complete the installation process, configure InterTest Batch using CSM  or using the manual process outlined in
this article.
 147


InterTest™ and SymDump ® 11.0
Follow these steps to manually configure your installation of InterTest Batch:
1.Customize Global Options  in CAVHCONF.
2.Configure ISPF options .
3.Configure batch Link and SYSPLEX .
4.Configure external security options  in CAVHCONF.
5.Define the InterTest Batch user exits  .
6.Allocate files.
7.Configure dynamic symbolic support.
8.Customize the following  batch interfaces and compatibility  options:
–CLISTs
–Compile procedures
–ISPF main panel
–TSO logon procedure
–Roscoe
–BTS extended support
–DB2 SP and IMS/DC Debugging
9.Activate your product.
10.Verify your installation
Options
This article describes options that apply to all InterTest and SymDump  products.
For all products, you must update CAVHCONF or the application uses the default values. After you review and optionally
update CAVHCONF, set the options that apply to the specific products that you are installing. These options are described
in the following pages in this section of the documentation.
Global Options
The options that control all products are stored in CAVHCONF. Modify the CAI.CAVHJCL(CAVHCONF) sample JCL to
update the default values before you submit the modified job.
You can update any of the following keywords.
NOTE
SYMPSWD and EXTSEC=ALL|SYMBOLIC are mutually exclusive and SYMPSWD is ignored if EXTSEC=ALL
or EXTSEC=SYMBOLIC is specified.
ABEND_PGM_FILTER
Activates the abend program filtering option in SymDump  Batch. The default is OFF. To activate this option,
specify ON and create a list of abend program names in the CAVHFMOD module. The specified abend program


names are then from the dump index and replaced with a meaningful program name. This name is obtained by
going up one level on the active program call chain. Use ABEND_PGM_FILTER to avoid filling the dump index
with multiple instances of a common error handling program name.
NOTE
This filtering applies only to the dump index. The abending program name and offset are not changed in
the abend report.
Syntax:
ABEND_PGM_FILTER=( OFF|ON)
 148


InterTest™ and SymDump ® 11.0
NOTE
For more information, see Define the Abend Filter Table CAVHFMOD.
EXTSEC
Specifies the external security settings in IN25UTIL and InterTest Batch. Specify SYMBOLIC to activate external
security for the symbolic file INITIALIZE, UPDATE, DELETE, PURGE, and RELOAD functions. Specify INTBAT to
activate external security for mismatched symbolic members.
Syntax :
EXTSEC=( NONE|ALL|SYMBOLIC,INTBAT)
IBSYSPLEX
Specifies whether the sysplex support of InterTest Batch is enabled.
Values: Y, N
Default:  N
PINT
Specifies whether a product can be used on a specific LPAR. If permitted, then the normal LMP checks for that
product are performed. If not permitted, a message appears stating that the product is unavailable on this LPAR.
(This message appears in place of an LMP warning.) The default value is DYNAMIC. This value causes the
product to determine which products have valid LMP keys on an LPAR. The product then sets the product intent
values accordingly.
Syntax :
PINT=(INTBAT,INTCICS,SYMBAT,SYMCICS|ALL| DYNAMIC)
SCHTBSIZE
Specifies the maximum number of entries in the Batch Link Scheduling Table for monitoring DB2 stored
procedures and IMS/DC transactions.
Limits:  0 (disables the schedule function) - 60
Note:  With the schedule function disabled (SCHTBSIZE=0), all DB2 SP and IMS/DC transactions run
unmonitored.
Default:  20
SYMPSWD
Specifies the PROTSYM password.
Default: 12345678
Limits: Up to eight characters
WORKUNIT
Specifies the unit name for temporary data sets.
Default : SYSDA


WORKUNIT
Specifies the unit name for temporary data sets.
Default : SYSDA
Limits:  Up to eight characters
Examples:
 CAVHCONF TYPE=CSECT,PINT=DYNAMIC,ABEND_PGM_FILTER=ON

 CAVHCONF TYPE=CSECT,PINT=(SYMBAT,INTBAT)

 CAVHCONF TYPE=CSECT,PINT=ALL

 CAVHCONF TYPE=CSECT,PINT=DYNAMIC

 CAVHCONF TYPE=CSECT,SYMPSWD=87654321

 CAVHCONF TYPE=CSECT,PINT=(SYMBAT,INTBAT),EXTSEC=SYMBOLIC
 149


InterTest™ and SymDump ® 11.0

 CAVHCONF TYPE=CSECT,IBSYSPLEX=Y,SCHTBSIZE=30

SymDump  Batch Options
This article describes the following SymDump  Batch options:
Data set CAI.CAVHJCL contains members CAOUDFRX, CAOETABL, and CAOCAB80. These members contain the JCL
to assemble and link the product defaults.
Data set CAI.CAVHPROC contains the CAOUASML PROC to assemble and link the default table.
All SymDump  Batch options default to unfixed, indicating that they can be overridden in the JCL. To fix an option, insert an
asterisk (*) between the equal sign (=) and the option value.
Optionally copy and update each member to conform to your installation standards. Submit each job to create a new set
of defaults.
WARNING
Ensure that you change the following data set names to conform to your installation standards:
•The default symbolic libraries (member CAOUDFRX, macro CAOUSYM)
•The CAIPRINT repository library (member CAOETABL, option PRTLIB)
Execution-Time Options CAOUDFRX
This section describes the options that SymDump  Batch uses at execution time.
NOTE
Default options member CAOUDFRX contains references to options that are not documented here. These
options are used by other Broadcom  products that share this member. These options have no effect on
SymDump  Batch.
CAOUSYM dsname
Adds a symbolic file (a PROTSYM or CSL) to the search list for abend and Snap reports. Insert one CAOUSYM
statement for each symbolic file used at your installation.
CAOUXDUP modname
Specifies whether to add a control section name to the exclusion list for duplicate dump suppression. Control


Specifies whether to add a control section name to the exclusion list for duplicate dump suppression. Control
sections in the exclusion list are not subject to the duplication limit (DUPLIM) value. Exclude as many control
sections as needed by including one CAOUXDUP statement for each name.
CAOUXMOD modname
Specifies whether to add a control section name to the exclusion list for abend reports. Control sections in the
exclusion list are not displayed in dump format as part of an abend report. Exclude as many control sections as
needed by including one CAOUXMOD statement for each name.
DUPLIM=5| nnn
Specifies the maximum number of duplicate reports to store in a single repository. Specify a number from 1 to
999, or specify 0 to suppress duplication checking. Duplicate reports have the same abending program name,
program offset, and completion code. Lowering the value of DUPLIM does not delete any existing reports in the
repository.
EXPDAYS=0|nnn
Specifies the maximum number of days to retain a report in the repository, starting from the day it is added.
Specify the number of days from 1 to 999, or specify 0 to suppress report expiration. Expired reports are
 150


InterTest™ and SymDump ® 11.0
automatically deleted during the auto-maintenance cycle. This cycle occurs immediately before any new report
is added. During auto-maintenance, the age of each report is compared to the current  EXPDAYS value. (Auto-
maintenance does not use the EXPDAYS value when the reports were added.)
LANGMSG=ENGLISH| xxxxxxxx
Specifies the language in which to write all execution-time messages. Only ENGLISH is supported currently.
LANGWTO=ENGLISH|xxxxxxxx
Specifies the language in which to write all execution-time WTOs. Only ENGLISH is supported currently.
LIBDD=SYSLIB| ddname
Specifies the ddname that MRS uses to identify the load library being reported on.
LINECNT=60| nnn
Specifies the maximum number of lines to display on a page for all execution-time reports.
NDVRDD=CAINDVR| ddname
Specifies the ddname that is used in the execution JCL to define the symbolic file. The symbolic file is populated
dynamically when Dynamic Symbolic Support (NDVRDSS) is active for Endevor .
NDVRDSN= dsname
Specifies the symbolic file that is populated dynamically when Dynamic Symbolic Support (NDVRVSS) is active
for Endevor . Specify a PROTSYM file. When a data set is specified, it is included in the symbolic file search list
automatically. If you do not want to specify a default dsname, leave this option blank.
NDVRPROC= procname
Specifies the seven-character prefix of the procedure name. This procedure is started when Dynamic Symbolic
Support (NDVRDSS) is active for Endevor  and when multiple site IDs are used by the installation.
OPTSDD=CAIOPTS| ddname


OPTSDD=CAIOPTS| ddname
Specifies the ddname that references the execution-time options data set.
PANACCS=PANEACCS|pgmname
Specifies the Panexec  library access routine. This option is ignored at execution time if PANEXEC=OFF is
specified.
PANEXEC=OFF|ON
Specifies whether Panexec  is present on the system.
PRINTDD=CAIPRINT| ddname
Specifies the ddname that references the report file.
PRTLBDD=CAIPRTLB|ddname
Specifies the ddname that references the central VSAM repository.
REGMAX=( nnnn |128,nnnn |256)
Specifies the number of storage bytes to format before and after each register address for Assembler programs.
SAVEHEAP=ON|OFF
Specifies whether to save LE or PL/I heap storage for abending applications.
SHOWHEAP=ON|OFF
Specifies whether to format LE or PL/I heap storage. For LE enabled Assembler or PL/I programs,
SHOWHEAP=ON requires SAVEHEAP=ON at execution time.
SHOWUNMRG=ALL|NONE|TBLS
Specifies whether to display storage for which symbolic names are not merged. This option applies only when
merging options are used. This storage can result from slack  bytes between fields. This storage can also result
from table entries which are not merged because of limits imposed by the OCCURS option. The following options
are valid:
ALL
Formats all unmerged storage.
 151


InterTest™ and SymDump ® 11.0
NONE
Suppresses unmerged storage.
TBLS
Formats only table storage which is unmerged because of the limits imposed by the OCCURS option.
SNAPS=0| nnnnn |ON|OFF
Specifies the maximum number of Snap reports to produce during a job step. When this value is exceeded, all
calls to CAODSNAP are ignored.
The default value for nnnnn is 32767.
NOTE
Each call to CAODSNAP generates a separate SNAP report in your central VSAM repository. If your
program contains multiple SNAP calls or a SNAP call within a loop, you can flood the repository. To
avoid this problem, you can write the output to the CAIPRINT DD alone. See the PRTREPT option.
SPBLKLN=0| nnnnn
Specifies the default block length to use for dynamic allocation.
SPPRIM=1| nnnnnnnn
Specifies the primary space allocation to use for dynamic allocation.
SPSECND=1| nnnnnnnn
Specifies the secondary space allocation to use for dynamic allocation.
SPUNITS=CYL|TRK|BLK
Specifies the default space units to use for dynamic allocation.
STORCLS=storclas
Specifies the default storage class to use for dynamic allocation. Currently, this option is used only for temporary
files that the viewer creates.
SUPPRS=OFF|ON
Specifies whether to suppress the following items:
•The CAIOPTS File Processing report and Report Summary for programs containing snap calls when the
SNAP option is OFF.
•The CAIOPTS File Processing report and Execution Monitor Summary for applications containing one or more
programs that were optimized using the Optimizer/II  DTECT option and which terminate normally.
SYMDD=CAISYM| ddname


SYMDD=CAISYM| ddname
Specifies the ddname that is used in your execution JCL to define a symbolic file override.
SYSOUT=*| x
Specifies the default SYSOUT class to use when report files or dump files are allocated dynamically.
SYSOUTD=destination
Specifies the default destination for SYSOUT data sets that are allocated dynamically for report or dump files. The
default is blank. When blank, no destination is used.
UNIT=SYSDA| xxxxx
Specifies the default UNIT name to use for dynamic allocation.
USERID='CA'| string
Specifies a text string that appears in the top left corner of each page of the execution reports.
Abend Handler and Reporter CAOETABL
NOTE
If SymDump  System is also installed, set the DUMP option to ON in the default member CAOETABL.
 152


InterTest™ and SymDump ® 11.0
Exclusion Options
CAOETABL includes the CAOETXCL macro, which lets you specify exclusion criteria for your abend reports.
You can use the following wildcard characters when specifying your criteria:
*
Denotes a prefix. For example,
ABC*
excludes all items that start with ABC.
?
Indicates a single character. For example,
AB??EFGH
excludes any items that start with "AB" and have "EFGH" in positions 5-8.
:
Delimits a range. For example,
100:200
excludes any account number from 100 to 200.
NOTE
This wildcard applies only to the ACCOUNT= keyword.
You can specify the following keywords in the CAOETXCL macro:
ABNDCDE=
Specifies a list of the system abend codes to exclude. Each entry is exactly 3 bytes.
ACCOUNT=
Specifies a list or range of account numbers to exclude. If an account number includes subfields, they are
concatenated and treated as a single field. The maximum length is 25 bytes.
JOBNAME=
Specifies a list of job names to exclude. The maximum length is 8 bytes.
PGMNAME=
Specifies a list of program names to exclude. These names correspond to the name of the job step program.
These names do not necessarily match the name of the abending program. The maximum length is 8 bytes.
SMFIDS=
Specifies the SMF ID of the running system to exclude. The maximum length is 4 bytes.
SUBSYS=
Specifies the subsystem type to exclude. Subsystem means a batch job (INIT), a started task (STC), a TSO
session (TSO), IMS, DB2, or Datacom/DB .
USRABND=


USRABND=
Specifies a list of the user abend codes to exclude. Each entry is exactly 4 bytes.
Reporting, Logging, and Security Options
Use the following keywords in macro CAOETGEN to set the reporting, logging, and security options:
ACB=OFF|ON
Specifies whether to print the access method control blocks for open VSAM files.
AMB=OFF|ON
Specifies whether to print the access method blocks for open VSAM files.
 153


InterTest™ and SymDump ® 11.0
AMBL=OFF|ON
Specifies whether to print the access method block list for open VSAM files.
ASMINST=ON|OFF
Displays the abending Assembler instruction and associated operands on the abend page.
BLLMAX=512|nnnnn
Specifies the maximum number of bytes to format for an unknown BLL cell range. (The length of an 01-item in the
LINKAGE SECTION cannot always be determined.) The maximum value is 4096.
BINDER=ON|OFF
Specifies whether to access user load modules through the binder API function calls or the standard I/O macros.
BINFRMT=DEC|HEX
Specifies whether to display the binary data values in decimal display or hexadecimal format.
BLOCKS=OFF|ON
Specifies whether to print all data management control blocks. This keyword overrides all other options that
control the formatting of control blocks.
COBONLY=OFF|ON
Specifies whether to suppress an abend report when the ABEND does not occur in a COBOL program.
DB2ACTIV=OFF|ON
Specifies whether to display summary information for packages and DBRMs that are active when an ABEND
occurs.
DCB=OFF|ON
Specifies whether to format the data control blocks for all open files.
DEB=OFF|ON
Specifies whether to format the data extent blocks for all open files.
DUMP=OFF|ON
Specifies whether to produce a system dump after the abend report is written.
FILES=ON|OFF
Specifies whether to report on all open files that did not appear in the File Section displays for any COBOL
program in the abend report.
FST128=OFF|ON
Specifies whether to limit the display of file buffers to the first 128 bytes. This option affects the File Section


displays and the Open Files report.
GRPADDR=ON|OFF
Specifies whether to display the base locator, displacement, and address of a group item on the merged Data
Division displays.
IOB=OFF|ON
Specifies whether to format the input/output blocks for all open files.
LINECNT=60| nnn
Specifies the maximum number of lines to display on each page of an abend or Snap report.
LINKAGE=ON|OFF
Specifies whether to format the LINKAGE SECTION of any COBOL program being reported on.
LCLSTOR=ON|OFF
Specifies whether to format the LOCAL-STORAGE SECTION of any COBOL program being reported on.
LISTLINE=0| nn
Specifies the number of extra listing lines to merge into a report before and after the source statement at ABEND,
snap, or transfer.
 154


InterTest™ and SymDump ® 11.0
LOGNET=OFF|ON
Specifies whether to write a record to Netman  to use for automated problem tracking. If ON is specified, also set
the Netman  files that are required for Machine-Generated Problem Tracking (MGPT).
LOGROS=ON|OFF
Specifies whether to send a message describing the ABEND to the Roscoe  IE user who submitted the job. If ON
is specified, also specify the Roscoe  IE job name in the ROSCOE option.
LOGTSO=ON|OFF
Specifies whether to send a message describing the ABEND to the TSO user who submitted the job.
LOGUNI=ON|OFF
Specifies whether to send a message describing the ABEND to the NSM  console.
MEMMAP=ON|OFF
Specifies whether to format the DSA, TGT, and PGT Memory Maps for any COBOL program being reported on.
MERGEDB=ON|OFF
Specifies whether to map areas in the DB2, IDMS/DB , and IMS database reports symbolically.
MRGAUTO=ON|OFF
Specifies whether to merge symbolic names onto automatic storage for PL/I procedures.
MRGBASED=ON|OFF
Specifies whether to merge symbolic names onto based variable storage for PL/I procedures.
MRGCNTLD=ON|OFF
Specifies whether to merge symbolic names onto controlled storage for PL/I procedures.
MRGDATA=ON|OFF
Specifies whether to turn all merging options ON or OFF.
MRGDSECT=ON|OFF
Specifies whether to merge symbolic names onto Assembler program storage when DSECTs are used and
USINGs are defined.
MRGFILES=ON|OFF
Specifies whether to map the FILE SECTION display symbolically.
MRGLINK=ON|OFF


Specifies whether to map the FILE SECTION display symbolically.
MRGLINK=ON|OFF
Specifies whether to map the LINKAGE SECTION display symbolically.
MRGLOCAL=ON|OFF
Specifies whether to map the LOCAL-STORAGE SECTION display symbolically.
MRGPARMS=ON|OFF
Specifies whether to merge symbolic names onto parameter storage for PL/I procedures.
MRGSTAT=ON|OFF
Specifies whether to merge symbolic names onto static storage for PL/I programs.
MRGWORK=ON|OFF
Specifies whether to map the WORKING-STORAGE SECTION display symbolically.
NDVRASM=OFF|ON
Specifies whether the symbolic file is always populated dynamically for assembler programs which are not LE
enabled. This option takes effect only when Dynamic Symbolic Support (NDVRDSS) is active for Endevor .
NDVRDSS=OFF|ON
Specifies whether Dynamic Symbolic Support is active for Endevor .
NTMGCTL=CAI.NTMMGCTL|OFF
Specifies the Netman  NTMMGCTL file that is allocated dynamically when LOGNET=ON is specified.
 155


InterTest™ and SymDump ® 11.0
NTMPI=CAI.NTMPI| dsname
Specifies the Netman  NTMPI file that is allocated dynamically when LOGNET=ON is specified.
NTMSC=CAI.NTMSC| dsname
Specifies the Netman  NTMSC file that is allocated dynamically when LOGNET=ON is specified.
OCCURS=1| nnnnnnnn |MAX
Specifies the maximum number of table occurrences to map symbolically when using the merging options. MAX
sets the option to its maximum value of 16777215.
OPMEM=xxxxxxx
Specifies the member name that contains the execution options when the options file is a dynamically allocated
PDS.
OPSUFIX=CAIOPTS| xxxxxxxx
Specifies the suffix to append to the user ID that submitted the job. This suffix is used when no options data set is
included in the JCL. The suffix and ID create the options data set name for dynamic allocation.
OPTSDD=CAIOPTS| ddname
Specifies the ddname for the options file that is dynamically allocated when it is not specified in the JCL. The
abend Handler/Reporter performs the dynamic allocation, but the Execution Monitor reads the file. This name
must match the name that is specified for the same variable in the CAOETGEN defaults member.
PLH=OFF|ON
Specifies whether to format the place holders for open VSAM files.
PRTLHCT=80|nn
Specifies the percent full the PRTLIB dataset must reach to trigger a health check exception condition. If this
percentage is reached the health check program will go into exception state and issue consol messages every 15
minutes until the problem is corrected.
PRTLIB=CAI.PRTLIB|dsname


minutes until the problem is corrected.
PRTLIB=CAI.PRTLIB|dsname
Specifies the central VSAM repository to write abend and Snap reports. If you do not want to use a repository,
leave this option blank. For more information, see Allocate CAIPRINT Repository Library.
PRTREPT=BOTH|REPOS|PRTDD
Specifies whether to write abend or Snap reports to the central VSAM repository (REPOS), the CAIPRINT DD
(PRTDD), or both.
READLL=ON|OFF
Specifies whether SymDump  Batch reads the LINKLIST libraries to obtain module information for abend and
Snap reports. If READLL is OFF, SymDump  Batch may not be able to report on programs that were loaded from
LINKLIST.
REGMAX=( nnnn |128,nnnn |256)
Specifies the number of storage bytes to format before and after each register address for Assembler programs.
ROSCOE= list of names
Specifies the Roscoe  IE job names to use when LOGROS=ON is specified. You can include up to four names.
RPL=OFF|ON
Specifies whether to format the request parameter list for open VSAM files.
RPTSZ80=OFF|ON
Specifies whether to force all data that is in dump format to appear in an 80-column format.
SAVEHEAP=ON|OFF
Specifies whether to save LE or PL/I heap storage for abending applications.
SHOWHEAP=ON|OFF
Specifies whether to format LE or PL/I heap storage. For LE enabled Assembler or PL/I programs,
SHOWHEAP=ON requires SAVEHEAP=ON at execution time.
 156


InterTest™ and SymDump ® 11.0
SHOWUNMRG=ALL|NONE|TBLS
When merging options are used, this option specifies whether to display storage for which symbolic names are
not merged. This storage can result from "slack" bytes between fields. This storage can also result from table
entries that are not merged because of limits imposed by the OCCURS option. The following options are valid:
ALL
Formats all unmerged storage.
NONE
Suppresses unmerged storage.
TBLS
Formats only table storage which is unmerged because of the limits imposed by the OCCURS option.
SMF=OFF|ON
Specifies whether to write a record to the System Management Facility. If ON is specified, include the SMF record
number in the SMFREC option.
SMFREC= nnn
Specifies the SMF record number for SMF recording when SMF=ON is specified. This value must be from 128
through 255, and it cannot conflict with an existing record number.
SNAPS=ON|OFF
Specifies whether to support SNAP requests in a program.
NOTE
Each call to CAODSNAP generates a separate SNAP report in your central VSAM repository. If your
program contains multiple SNAP calls or a SNAP call within a loop, you can flood the repository. To
avoid this problem, write the output to the CAIPRINT DD alone. See the PRTREPT option.
STOPDD=CAOESTOP|ddname
Specifies the ddname that is used in the execution JCL to suppress abend reports.
SVAREA=ON|OFF
Specifies whether to produce a Save Area Trace report. This report shows the changed save areas, starting with
the program that abended.
SYSOUT=*| x
Specifies the default SYSOUT class to use at execution time when report files or dump files are allocated


Specifies the default SYSOUT class to use at execution time when report files or dump files are allocated
dynamically.
UCB=OFF|ON
Specifies whether to format the unit control blocks list for open files.
VSAMCAT=OFF|ON
Specifies whether to format the VSAM catalog information for each open VSAM file.
VSMIDX=OFF|ON
Specifies whether to format the VSAM indexed control blocks for the index portion of each open VSAM file
with the control blocks for the data portion.
WRKSTOR=ON|OFF
Specifies whether to format the WORKING-STORAGE of each COBOL program in an abend report.
WTL=OFF|ON
Specifies whether to send a message describing the ABEND to the system log.
WTO=ON|OFF
Specifies whether to send a message describing the ABEND to the job log (using WTO with ROUTCDE=11).
 157


InterTest™ and SymDump ® 11.0
WTOXCL=OFF|ON
Specifies whether to send a message which describes the reason that a report was not generated because of
exclusion criteria.
Define the User Abend Control Table CAOCAB80
The following tables control the abend processing:
Product Table
Contains predefined controls. The product table contains only the common system abend codes.
User Table
Contains user-defined abend control entries. These entries can define new controls, and can also override
existing controls in the product table.
NOTE
The user abend control table must be link-edited with the load module name CAOCAB80.
Each entry in a control table defines the processing options for a specific abend code.
You can design diagnostic programs for the user abends and system abends.
Follow these steps:
1.Add an entry to the user abend control table, CAOCAB80, for the specific abend using the DMOD parameter.
2.Use the CPXACODE macro (included with the product) to define user abend control table entries for CAOCAB80. The
following example shows the syntax to use. The first positional parameter is required.
[label] CPXACODE START
        CPXACODE abendcode [,keyword=ON|OFF[,...]] [,DMOD= modulename ]
        CPXACODE END
–label
Identifies a specific code section.
–START
Generates a CSECT statement. If a label is specified, the label is used as the CSECT name. Otherwise, the
generated CSECT name is the default, CAOCAB80.
NOTE
The CSECT must be link-edited as a single CSECT load module. The module must be named
CAOCAB80.
–abendcode


CAOCAB80.
–abendcode
Specifies the abend code. The following values are valid:
•S001-SFFF (for the system abend codes)
•U0001-U4095 (for the user abend codes)
–keyword
Specifies a keyword and whether to enable the abend reporting function:
ON
Enables the abend reporting function for this keyword.
OFF
Disables the abend reporting function for this keyword.
The keywords in this macro have the same function as the keywords in the CAIOPTS (SYSIN) data set. For  more
information about these keywords, see SymDump  Keyword Descriptions and Data Management Control Block
Keywords.
–DMOD
(Optional) Specifies the program name of an existing user diagnostic module.
 158


InterTest™ and SymDump ® 11.0
The SymDump  Batch diagnostic modules are still called when the user CPXACODE macro definitions do not
specify the DMOD operand.
–END
Generates a trailer table entry that must be specified last.
Example:
The following syntax adds a new entry to the user control table:
CAOCAB80 CPXACODE START
         CPXACODE U1005,BLOCKS=ON,DUMP=OFF
         CPXACODE S322,DUMP=OFF,DMOD=TIMEOUT
         CPXACODE END
         END
SymDump  Batch Keyword Descriptions
This section describes the SymDump  Batch keywords:
DTECT
Turns abend reporting on and off.
Default:  ON
DUMP
Forces a SYSUDUMP.
Default:  OFF
F128
Prints only the first 128 bytes of a record.
Default:  OFF
MEMMAP
Prints the DSA, TGT, and PGT memory map.
Default:  ON
FILES
Prints open files report.
Default:  ON
SAVEAREA
Prints the save area trace report.
Default:  ON
Data Management Control Block Keywords
This section describes the Data Management Control Block keywords:
BLOCKS
Sets all Data Management keywords to OFF.
Default:  OFF
ACB
Includes the VSAM Access Method Control Block.
Default:  OFF
AMB
Includes the VSAM Access Method Block.
Default:  OFF
 159


InterTest™ and SymDump ® 11.0
AMBL
Includes the VSAM Access Method Block List.
Default:  OFF
DCB
Includes the Data Control Block.
Default:  OFF
DEB
Includes the Data Extent Block.
Default:  OFF
IOB
Includes the I/O Block.
Default:  OFF
PLH
Includes the VSAM Place Holder.
Default:  OFF
RPL
Includes the VSAM Request Parameter List.
Default:  OFF
UCB
Includes the Unit Control Block.
Default:  OFF
VSAMIDX
Includes the VSAM Indexed Control Blocks.
Default:  OFF
NOTE
Use ON to print the indicated control blocks; use OFF if you do not want the control block to print.
User-Supplied Abend Diagnostic Modules
You can develop abend diagnostics modules to supplement SymDump  Batch processing. These programs provide
diagnostic material for the abend and diagnostic logic to determine the abend cause.
SymDump  Batch provides a CPXDIAG macro to help you build diagnostic modules. This macro provides entry logic and
exit logic, user workspace, and addressability to parameter information. This macro also provides the Abend Reporter
interface for printing lines and altering abend control information.
The use of the CPXDIAG macro assumes the following register conventions:
Register Description
R0, R1, R14, R15 Standard macro linkage and usage
R13 Provides addressability to register save area, parameter
information, print line build area, and user workspace
R12 Program base register
See the following CPXDIAG function definitions:
•The following syntax establishes the CSECT name and the program and DSECT addressability, and saves the caller
registers. Specify this function type first and code a label.
label CPXDIAG TYPE=START


label CPXDIAG TYPE=START
•The following syntax restores the caller registers and returns. Specify this function at the end of your processing.
 160


InterTest™ and SymDump ® 11.0
label CPXDIAG TYPE=END
•The following syntax writes a block of text to the abend report. The text is automatically centered on the report.
Enclose each line of text in apostrophes. Verify that each line is less than or equal to 76 bytes. Generate blank lines by
coding two or more contiguous commas.
label CPXDIAG TYPE=BLKTEXT,'L1', 'L2', 'L3',…'Ln'
•The following syntax writes a 133-byte line of data to the abend report. Provide the address of this line by using the
AREA keyword. The first byte of the line is reserved for an ASA control character; you must place one there.
label CPXDIAG TYPE=PRINT,Rx,AREA= < label>
•The following syntax alters the abend control table options, but only for the current execution. You can specify one
or more of the listed keywords. Assign a value of ON or OFF to each keyword. See the third point in the following
example.
label CPXDIAG TYPE=ALTER, ACB=, AMB=, AMBL=,BLOCKS=, DCB=, DEB=,DTECT=, DUMP=, FILES=,F128=, IOB=,
 MEMMAP=,PLH=, RPL=, SAVAREA=,UCB=,
Example:
The following example shows a user diagnostic module:
SR1234  CPXDIAG  TYPE=START  establish CSECT name and addressability
1.           CPXDIAG  TYPE=BLKTEXT,                                   x
                      'U1234 - PAYROLL SYSTEM ABEND.',                X
                      'FICA TABLE IS NOT CURRENT'                     X
                .
                .
                .


.
                .
                .
         user diagnostic logic
                .
                .
                .
2.          MVI CPXLINE,C'0'                DOUBLE SPACE
            MVC CPXLINE+1(132),FICATABLE    LOAD 132 CHARACTER AREA
            CPXDIAG     TYPE=PRINT,AREA=CPXLINE

3.          CPXDIAG     TYPE=ALTER,                                   X
                        DUMP=OFF,DTECT=OFF
            CPXDIAG     TYPE=END Notes:
Consider the following important points:
•When printing a text block, create a double space by specifying a NULL operand. (This operand consists of two
apostrophes with no intervening spaces; for example,  '' .) Enclose all text in single quotes. Each text block can
contain up to 76 characters between the quotes.
•When using carriage control characters, consider the following information:
–'blank' represents a single space.
–'0' represents a double space.
–'-' represents a triple space.
•Instruct SymDump  Batch not to perform any additional abend processing and to suppress the system dump.
The following information is available to the user diagnostic module automatically. The CPXDIAG TYPE=START macro
automatically provides addressability using Register 13. You can build your own print lines in the CPXLINE space
provided, or by using the TYPEPRINT macro. In addition, 120 bytes of workspace are provided at CPXUSPCE for your
own routines.
CPXDSECT  DSECT
 161


InterTest™ and SymDump ® 11.0
CPXSAVE   DS   18F    REGISTER SAVE AREA
CPXIFACE  DS   A      ADDRESS OF MACRO INTERFACE TO DETECTOR
CPXMDGBL  DS   A      INTERFACE PARM
CPXIPRM   DS   5A     PARM LIST TO INTERFACE RTN
CPXTCB    DS   A      ADDRESS OF ABENDING TASK TCB
CPXTIOT   DS   A      ADDRESS OF ABENDING TASK TIOT
CPXCSECT  DS   CL8    ABENDING CSECT NAME
CPXENTRY  DS   A      ABENDING CSECT ENTRY POINT ADDRESS
CPXDATE   DS   CL8    CURRENT DATE "MM/DD/YY" GREGORIAN FORMAT
CPXTIM    DS   CL8    TIME OF ABEND "HH.MM.SS" FORMAT
CPXSFLAG  DS   X      STAE/ESTAE FLAGS
CPXREQ    EQU  X'80'  DUMP REPORT HAS BEEN TERMINATED, STEP OPTION
                      SPECIFIED ON ABEND MACRO
CPXSTCC   EQU  X'10'  DON'T STORE COMPLETION CODE, NOT USED IN OS/VS2
CPXRETCD  DS   XL1    SYSTEM RETURN CODE FOR GIVEN ABEND
          DS   XL1    FUTURE USE
CPXATYPE  DS   CL1    ABEND TYPE
CPXUSER   EQU  C'U'   USER ABEND
CPXSYSTEM EQU  C'S'   SYSTEM ABEND
CPXACODE  DS   CL4    ABEND CODE 0001-FFFF
CPXAPSW   DS   XL8    PSW AT ENTRY TO ABEND
CPXPPSW   DS   XL8    LAST PROBLEM PROGRAM PSW


CPXPPSW   DS   XL8    LAST PROBLEM PROGRAM PSW
CPXRO     DS   F      REGISTERS AT ABEND
  .       .    .      .
  .       .    .      .
  .       .    .      .
CPXR15    DS   F
          DS   8A     FUTURE USE
CPXLINE   DS   CL133  USER PRINT LINE WORK AREA
          DS   XL3    FUTURE USE
          DS   OF
CPXUSPCE  DS   XL120  USER WORK SPACE
CPXLENGTH EQU  *-CPXDSECT  LENGTH OF DIAGNOSTIC INFORMATION AREA
The following table contains the default product settings. You can update CAOCAB00 to change these settings.
Abend Code FIRST128 MEMMAP FILES SAVEAREA DUMP
001 ON ON ON
002 ON ON
013 ON ON
031 ON
038 ON
03D
0C1 ON ON ON ON
0C2 ON ON ON ON
0C4 ON ON ON ON
0C5 ON ON ON ON
0C6 ON ON ON ON
0C7 ON ON
 162


InterTest™ and SymDump ® 11.0
0C8 ON ON
0C9 ON ON
0CA ON ON
0CB ON
137 ON ON
213 ON ON
214 ON ON
237 ON ON
314 ON ON
322 ON ON ON
413 ON
513 ON ON ON
522 ON
613 ON ON
637 ON ON
706 ON
713 ON
714 ON ON ON
722 ON ON ON
804 ON
806 ON ON
80A ON ON
813
913 ON ON
A13 ON ON
B37 ON ON
C13 ON ON
D37 ON ON
E37 ON ON
Default Entry (for
any abend types not
shown)ON ON ON ON
Define the Abend Filter Table CAVHFMOD
The CAI.CAVHJCL(CAVHFMOD) member controls which abend program names are filtered from your dump index. This
member is used by SymDump  Batch.
Many of your applications may use a common abend handling program. When an abend occurs, the common program
name and its offset appear in the dump index for all application failures. Multiple occurrences of a common name make
it difficult to identify the abending application correctly. This problem also makes it difficult to implement automatic
notification of the appropriate personnel when production failures occur.
 163


InterTest™ and SymDump ® 11.0
However, you can use CAVHFMOD to specify one or more program names to filter. When an application abends, the
specified names do not appear in the dump index. Instead, they are replaced with a meaningful program name and offset.
These values are obtained by going up one level on the active program call chain.
NOTE
•The program names that you specify here are not filtered from the dump index unless you activate the
filtering option. Specify ABEND_PGM_FILTER ON in CAI.CAVHJCL(CAVHCONF).
•This filtering applies only to the dump index. The abending program name and offset are not changed in the
abend report.
To configure the CAVHFMOD options, access the member and edit its JCL. This member contains sample JCL to
assemble and link the CAVHFMOD filter table.
Use the following syntax to specify which program names to filter:
CAVHFMOD START
CAVHFMOD FILTER,PROGRAM= name
CAVHFMOD END
START
Indicates the start of the abend program list. Specify START once, before any FILTER syntax.
•FILTER,PROGRAM=name
Specifies a program name to filter. You can specify a fully qualified program name. You can also use the following
wildcards:
*
Denotes a prefix. For example,
ABC*
selects all program names that start with ABC.
?
Indicates a single character. For example,
AB??EFGH
selects all program names that start with "AB" and have "EFGH" in positions 5-8.
END
Indicates the end of the abend program list. Specify END once, after all FILTER syntax.
Example: Filter Four Program Names From the Dump Index


Example: Filter Four Program Names From the Dump Index
The following syntax sample specifies four abend program names to filter:
CAVHFMOD START
CAVHFMOD FILTER,PROGRAM=IEFBR14
CAVHFMOD FILTER,PROGRAM=CEE*
CAVHFMOD FILTER,PROGRAM=I?BABEND
CAVHFMOD FILTER,PROGRAM=USERDUMP
CAVHFMOD END END ,
When this syntax is submitted, the specified program names are filtered out. These names are replaced with the program
name from the preceding level of the active program call chain.
Facilitate Multiple Default Execution Options
The SymDump  Batch defaults are established during installation. Each application programming area that uses SymDump
Batch can require different run-time defaults. In that case, the desired options are passed to the Execution Monitor by
using the CAIOPTS data set.
 164


InterTest™ and SymDump ® 11.0
Follow these steps:
1.Establish a library for the default options.
2.Create a library member for each programming area. Populate each member with the appropriate execution options
for that area.
3.Verify that the CAIOPTS DD points to the correct library member.
Examples:
Use the following syntax when the program is executed directly:
//CAIOPTS DD DSN=EXEC.PARAMLIB(MEMBERA),DISP=SHR
Use the following syntax to override a default option in the library member. After this syntax, add the syntax for those
options that are different from, or not specified in, the MEMBERA member.
//CAIOPTS DD DSN=EXEC.PARAMLIB(MEMBERA),DISP=SHR
//        DD *
Use the following syntax when a GO step in a cataloged procedure executes the program. Specify your member name
using the symbolic parameter PARAMEM when invoking the procedure.
//CAIOPTS DD DSN=EXEC.PARAMLIB(&PARAMEM).,DISP=SHR
Use the following syntax to override a default option in the library member. After this syntax, add the syntax for those
options that are different from, or not specified in, the MEMBERA member.
//GO.CAIOPTS DD DSN=EXEC.PARAMLIB(MEMBERA),DISP=SHR
//           DD *
NOTE
If SymDump  System is also installed, specify DUMP=ON in the default member CAOETABL.
InterTest Batch Options
This section contains instructions how to customize InterTest Batch ISPF options, batch link options and enable the Cross-
LPAR debugging feature.
Configure ISPF Options
When you configure InterTest Batch without CSM , use member INTISPF in the CAVHSAMP library to customize the


options that are passed to the application when it is invoked under ISPF.
The INTISPF member parameters are as follows:
ISPF
This is required to run the application under the ISPF dialog manager.
SYMLDYN
This parameter is no longer used.
TRACE(n)
Specifies the number of entries to be saved in the trace table and displayed by the TRACE and TRACE SOURCE
commands. The default is 1000 and n is an integer between 1 and 32760.
EXTSTOR(nM|nK)
The extended storage parameter allows you to set the amount of extended storage that is accessed by InterTest
Batch under the z/OS operating system. This storage is used when formatting data preceding the 16 MB line. The
 165


InterTest™ and SymDump ® 11.0
default amount is 64M. Specify the amount in megabytes (M) or kilobytes (K), and n is any integer between 1 and
100.
LINKPARM(n)
Specifies the maximum number of linkage parameters that can be set by the installation. The default is 32 and n
is any integer between 1 and 1000. Each linkage parameter requires a page of memory (4096 bytes) unless the
default has been changed.
LINKSIZE(n)
Specifies the amount of memory to be getmained for each linkage parameter. The default is 4096. It is not
recommended to specify less than 1024 or more than 32768. The parameters are always on page boundaries.
NOSLOW
Turns off the SLOW command at the installation. The users are notified with a message stating this when
attempting to use the SLOW command. Comment this parameter out if you do not want the SLOW command
disabled.
SLOWFAST(n)
Specifies the duration of the wait time in hundredths of a second between executable statements when using the
SLOWFAST command. The default is one quarter of a second (n=25). The value is any integer between 1 and
4096. This might be helpful to TCAM users with buffering problems.
NOSTAX
This is a required startup parameter.
NOESTAE
This is a required startup parameter.
NOSTAE
This is a required startup parameter.
NOESTAI
This is a required startup parameter.
NOJSCB
This is a required startup parameter.
Configure Batch Link and Sysplex
Configure the batch link schedule feature to leverage your DB2 stored procedure and IMS/DC testing environment.
Define the Batch Link Scheduling Table


Define the Batch Link Scheduling Table
The batch link schedule feature helps you to leverage your DB2 stored procedure and IMS/DC testing environment by
allowing you to specify exactly which of these programs you want InterTest Batch to monitor. To enable the batch link
schedule feature, customize the SCHTBSIZE option in CAVHCONF. For more information, see Options.
The SCHTBSIZE parameter of macro CAVHCONF defines the number of entries of an in-core table you want the product
to maintain in CSA.
Set SCHTBSIZE to a reasonable value (for example SCHTBSIZE=30) to stay in your testing threshold. Each entry uses
27 bytes of CSA storage.
The maximum value for SCHTBSIZE is 60. Setting SCHTBSIZE to zero (SCHTBSIZE=0) disables the schedule function.
When the schedule function is disabled, all DB2 SP and IMS/DC transactions run unmonitored.
The contents of the table are maintained through the product interface. For more information about maintaining this table,
see Batch Link Facility.
If you want the product to load a fixed schedule at every IPL, insert the following DD card to the CAS9 initialization job
stream:
 166


InterTest™ and SymDump ® 11.0
 //INT1SKUT DD DISP=SHR,DSN=xxxx

xxxx is a fully qualified data set containing schedule entries to be imported. This data set can be a sequential data set or
a partitioned data set. If it is a partitioned data set, provide a member name in parenthesis. Create this data set using the
EXPORT function. For more information about the EXPORT function, see DB2 and IMS Schedule Menu.
Enable the SYSPLEX (Cross-LPAR) Debugging Feature
You can view and debug jobs that are executing on different (foreign) LPARs than the one you are currently logged on to.
For more information about debugging jobs executing on foreign LPARs, see Batch Link Selection Panel.
Follow these steps:
1.Ensure that TCP/IP is active and accessible across the SYSPLEX, and that the Broadcom  Testing Tools Server is
running on all LPARs within the SYSPLEX.
2.Specify the port number that you want to use for InterTest Batch SYSPLEX support. Update BLSPORT="XXXXX" in
CAVHUOPT member which is located in CAVHOPTN target library data set.
3.Specify IBSYSPLEX=Y in your CAVHCONF configuration module.
4.Restart the Broadcom  Testing Tools server if the server is already running.
CICS Options
This article describes how to change the default installation options for InterTest for CICS and SymDump for CICS.
To create an IN25OPTS load module, all users must use the following sample JCL. To make changes to IN25OPTS after
you install your product, you will also perform the procedure to Refresh IN25OPTS.
Configure IN25OPTS Options


Configure IN25OPTS Options
InterTest for CICS and SymDump  for CICS installation options are contained in the IN25OPTS load module. Create an
IN25OPTS load module that contains the modified options with a batch assemble-and-linkedit job.
Sample JCL to Assemble the Options Program
The following example shows the JCL needed to assemble the InterTest for CICS and SymDump for CICS Options
Program (IN25OPTS). Member CABAOPTJ in CAI.CAVHJCL contains sample JCL that can be used to assemble and link
IN25OPTS. In the following example, the options LETSVC, EXTSEC and CWALET have been generated:
//IN25OPTS JOB
//************************************************************
//*       IN25OPTS SAMPLE JCL                                *
//************************************************************
//ASM      EXEC PGM=ASMA90,REGION=1M,
//             PARM='LIST,XREF(SHORT),DECK,NOOBJ'
//SYSPRINT DD  SYSOUT=*
//SYSPUNCH DD  DSN=&&OBJECT,UNIT=SYSDA,DISP=(NEW,PASS),
//       DCB=BLKSIZE=3200,SPACE=(TRK,(1,1))
//SYSLIB   DD  DSN=CAI.CAVHMAC,DISP=SHR
//         DD  DSN=CICS.MACLIB,DISP=SHR
//SYSUT1   DD  UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT2   DD  UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSUT3   DD  UNIT=SYSDA,SPACE=(CYL,(1,1))
//SYSIN    DD  *
 167


InterTest™ and SymDump ® 11.0
*** CWA USER DSECT REQUIRED HERE IF USING THE CWALET OPTION ***
         USING CWADS,0                 CA INTERTEST REQUIREMENT
CWADS    DSECT                         USER CWA
CWAFLD1  DS    CL20
CWAFLD2  DS    CL15
CWAFLD3  DS    CL100
******** CA INTERTEST AND SYMDUMP OPTION SPECIFICATIONS********
        IN25OPTS TYPE=CSECT,                                   X
              LETSVC=NO,                                       X
              EXTSEC=Y
        IN25OPTS TYPE=CSECT,                                   X
              CWALET=(CWAFLD1,CWAFLD2+15)
        IN25OPTS TYPE=FINAL
        END
/*
//LKED EXEC PGM=IEWL,PARM=(XREF,LIST,MAP),
// REGION=1M,COND=(4,LT,ASM)
//SYSPRINT DD SYSOUT=*
//SYSLMOD DD DSN=USER.LOADLIB(IN25OPTS),DISP=SHR
//SYSLIN DD DSN=&&OBJECT,DISP=(OLD,DELETE)
//       DD *
      ENTRY IN25OPTS
      NAME IN25OPTS(R)
//
NOTE
The CWALET option requires you to place your user CWA DSECT before the first IN25OPTS specification in the
assembly. The USING statement for this DSECT is required. The register value for the USING statement can be
any value from 0 to 15.
Refresh IN25OPTS Options
If you have already installed and configured the product, you can follow this procedure to change the existing IN25OPTS


options. Create a new copy of the IN25OPTS load module, and then take the following steps to refresh the options.
Follow these steps:
1.Terminate InterTest for CICS and SymDump for CICS.
2.Update the IN25OPTS load module that contains the modified options with a batch assemble-and-linkedit job.
3.Run the following commands.
CEMT SET  PROG(IN25*)  NEWCOPY
CEMT SET  PROG(IN##*)  NEWCOPY
NOTE
Replace ## with your two-digit CICS release number (68 for CICS 5.1, 69 for CICS 5.2, 70 for CICS 5.3, 71
for CICS 5.4, 72 for CICS 5.5, 73 for CICS 5.6, and 74 for CICS 6.1).
Ignore any failures of IN##HOOK and IN25INIT to newcopy.
4.Restart InterTest for CICS and SymDump for CICS.
IN25OPTS Keywords
The following list describes the IN25OPTS keywords.
 168


InterTest™ and SymDump ® 11.0
Keywords apply to either InterTest for CICS, SymDump  for CICS, or to both products.
If you change a transaction ID, also change the  CICS transaction definition.
Defaults are underlined. Slashes (/) between parameters indicate you must make a choice.
Common Keywords
BKPTERM
BKPTERM=  <no value>   /MOD2
no value
The breakpoint display will not force a MOD2 terminal.
MOD2
The breakpoint display will always be treated as a MOD2 terminal.
CORET
CORET= CORE /transaction-id
Specify a four-character transaction ID for the InterTest for CICS CORE transaction. Be sure to adjust the CICS
transaction definition if you do not use the default.
NOTE
The CICS restriction that no user transaction ID starts with the character C is not strict. You can use IDs such as
CNTL and CORE if the CICS system does not use them.
EXTSEC
EXTSEC=YES/ NO
Indicates whether External Security Manager is to be used.
YES
InterTest for CICS and SymDump  for CICS call the External Security Manager to verify access to secured
functions.
NO
InterTest for CICS and SymDump  for CICS bypass the calls to the External Security Manager. When first installing
InterTest for CICS and SymDump  for CICS, this setting is useful until the product is tested and the security rules
are written.
HELPFIL
HELPFIL= PROTHLF /filename
Specify the file name for the InterTest for CICS Help file. The name cannot exceed seven characters. Be sure to adjust the
CICS file definition if you do not use the default.
HELPT
HELPT= HELP /transaction-id


HELPT
HELPT= HELP /transaction-id
Specify a four-character transaction ID for the InterTest for CICS HELP transaction. Be sure to adjust the CICS transaction
definition if you do not use the default.
 169


InterTest™ and SymDump ® 11.0
IGLUT
IGLUT= IGLU /transaction-id
Specify a four-character transaction ID for the InterTest for CICS IGLU transaction. This transaction displays the
InterTest/SymDump  for CICS global user exit list.
NOTE
Adjust the CICS transaction definition if you do not use the default.
LISTT
LISTT= LIST /transaction-id
Specify a four-character transaction ID for the InterTest for CICS LIST transaction (viewing of the compile or assembly
listing). Be sure to adjust the CICS transaction definition if you do not use the default.
NDVRASML
NDVRASML= NO/YES
Non LE assembler programs do not have a standard date/time stamp within the load module to compare against the date/
time stamp of the program symbols in the PROTSYM file. Without a date/time stamp the symbols, verification fails and
causes symbols for assembler programs to always be loaded by the Endevor  dynamic symbolic load feature if the feature
is active.
NO
Indicates you do not want symbols for non-LE assembler programs to be dynamically loaded on every request.
YES
Indicates you want symbols for non-LE assembler programs to be dynamically loaded on every request.
NDVRPROC
NDVRPROC= INTNDVR  procedure name
Specify the name of the dynamic symbolic support for Endevor  procedure defined in the install procedure. This is the
seven-character name prefix of the procedure, which starts when dynamic symbolic support is active and a dynamic
symbols load is necessary.
SLBMARG
SLBMARG=  1 /nn
Specifies a decimal number, from 1 to 41, of the default margin value on the LIST facility screens for Assembler programs.


Regardless of this setting, the Location field of each source listing line is shown. The margin value can be adjusted online
at any time.
1
Presents the left-most portion of each source listing line.
41
Presents the right-most portion.
28
Suppresses the machine code.
34
Suppresses the machine code and statement numbers.
 170