0% found this document useful (0 votes)

426 views138 pages

CA

Uploaded by

Mounika27

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

426 views138 pages

CA

Uploaded by

Mounika27

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 138

AllFusion CA-InterTest for CICS

Getting Started
r8

This documentation and any related computer software help programs (hereinafter referred to as the
Documentation) is for the end users informational purposes only and is subject to change or withdrawal by CA at
any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in
part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA
and protected by the copyright laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for
their own internal use, and may make one copy of the related software as reasonably required for back-up and
disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy.
Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for
the product are permitted to have access to such copies.
The right to print copies of the documentation and to make a copy of the related software is limited to the period
during which the applicable license for the Product remains in full force and effect. Should the license terminate for
any reason, it shall be the users responsibility to certify in writing to CA that all copies and partial copies of the
Documentation have been returned to CA or destroyed.
EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY
APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING
WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY
LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT
LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY
ADVISED OF SUCH LOSS OR DAMAGE.
The use of any product referenced in the Documentation is governed by the end users applicable license
agreement.
The manufacturer of this Documentation is CA.
Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the
restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.2277014(b)(3), as applicable, or their successors.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
Copyright

2006 CA. All rights reserved.

Contents
Chapter 1: Introduction
Interactive System Productivity Facility-Like Menu Interface ..................................... 1-1
Test and Debug Directly from Your Source Listing............................................... 1-1
Prevent Abends by Trapping All Application Errors Online ........................................ 1-2
Set Breakpoints to Interrupt Program Execution ................................................ 1-2
Control Program Execution to Test All Program Paths ........................................... 1-3
CICSPlex Exploitation ......................................................................... 1-3
Ease-of-Use Features ......................................................................... 1-3
Symbolic Support Facilitates Problem Solving ................................................... 1-4
Display and Update Data Values from Your Source Listing Display ............................... 1-4
View and Modify Storage/Files without Interrupting the Test Session ............................. 1-4
Structured File Display Makes Data Easy on the Eyes ........................................... 1-5
Trace Program Execution ...................................................................... 1-5
Code Coverage ............................................................................... 1-5
Dynamically Change Program Execution ........................................................ 1-6
Monitoring by CICS User ID ................................................................... 1-6
Interactively Debug Applications That Access DB2 .............................................. 1-6
Helpful Diagnostic Information ................................................................ 1-6
Synchronized Processing ...................................................................... 1-7
Immediate Support for CICS Releases ......................................................... 1-7
Debug Production Applications Symbolically from Any CICS Region .............................. 1-7

Chapter 2: Getting Started

What You Need to Get Started ................................................................. 2-1
Major SMP Operations ........................................................................ 2-2

Chapter 3: System Requirements

Operating Environments ...................................................................... 3-1
CA Common Services for z/OS Requirements ................................................... 3-1
CAIRIM .................................................................................. 3-2
CA LMP................................................................................... 3-2
CAICCI ................................................................................... 3-3

Contents

iii

CA-Hardware Requirements................................................................... 3-3

Distribution Libraries ..................................................................... 3-3
Target Libraries .......................................................................... 3-4
Special Considerations........................................................................ 3-5
PL/I Programs............................................................................ 3-5
Global User Exits ......................................................................... 3-5
Terminal Input/Output Area Compression Routine Users .................................... 3-6
CICSPlex Support ........................................................................ 3-6
Dynamic Symbolic Support for AllFusion Endevor Change Manager .......................... 3-7
eTrust CA-ACF2 and RACF Users .......................................................... 3-8
AllFusion CA-Realia II Workbench Option for CICS Users .................................... 3-8
Database Support ........................................................................ 3-8
HOGAN Users ............................................................................ 3-8
MRO Users ............................................................................... 3-9
Omegamon Users ........................................................................ 3-9
TMON Users ............................................................................. 3-9
User CORE Commands .................................................................... 3-9
User Macros and Software Calls Support ................................................... 3-9
Data Monitoring .......................................................................... 3-9
6.1 to r8 Migration Considerations............................................................ 3-10
6.0 to r8 Migration Considerations............................................................ 3-11

Chapter 4: Base Product Installation Steps

Summary of Installation Steps ................................................................ 4-2
Step 1. Review System Requirements ......................................................... 4-3
Step 2. Enter LMP Product Key Certificate Information .......................................... 4-3
Use CA LMP .............................................................................. 4-3
Enter CA LMP Key Information for the PL/I Symbolic Options ................................ 4-5
Step 3. Complete the Installation Worksheet ................................................... 4-6
Step 4. Load Sample Installation JCL from the Tape ............................................ 4-7
Step 5. Allocate Target and Distribution Libraries ............................................... 4-7
Step 6. Allocate Private SMP/E Libraries and Define SMP Zones ................................. 4-8
Task 1. Allocate and Initialize CA Base SMP Libraries ....................................... 4-8
Task 2. Define Additional Product Target and Distribution Zones ............................. 4-8
Step 7. Customize the SMP Procedure ......................................................... 4-9
Step 8. Receive the Product................................................................... 4-9
Step 9. Apply the Product.................................................................... 4-10
Step 10. Accept the Product ................................................................. 4-11
Step 11. Install the Help Facility ............................................................. 4-12
Step 11a. Create the User-Defined Abend Description File ..................................... 4-12

Getting Started

Step 12. Create the Symbolic File............................................................. 4-12

Symbolic File Entries ..................................................................... 4-13
Concurrently Updating the PROTSYM File .................................................. 4-13
Step 13. Create the Checkpoint File ........................................................... 4-13
Step 14. Add the Required CICS Resource Definitions .......................................... 4-14
Step 15. Update the CICS startup JCL and Startup Parameters ................................. 4-14
Step 16. Install DB2 Support ................................................................. 4-15
Support DB2 Calls in the FILE and CORE Facilities .......................................... 4-15
Monitor DB2 Applications ................................................................. 4-16
Step 17. Restart CICS and Run Check-out Program ............................................ 4-16
Step 18. Install Dynamic Symbolic Support for AllFusion Endevor Change Manager .............. 4-17
Step 19. Check for Latest Maintenance ........................................................ 4-18
Activate AllFusion CA-InterTest for CICS ...................................................... 4-18
Deactivate AllFusion CA-InterTest for CICS .................................................... 4-19
PL/I Option Installation Steps ................................................................ 4-20

Chapter 5: Options
Modify AllFusion CA-InterTest for CICS Options ................................................. 5-1
Procedure for Modifying Options ............................................................... 5-1
Sample JCL to Assemble the Options Program .............................................. 5-3
IN25OPTS Keywords ...................................................................... 5-4
Implement Composite Support ............................................................... 5-22
Declare User-Defined CORE Commands ....................................................... 5-22
CORUCOM Macro ........................................................................ 5-22
Code the CORUCOM Macros .............................................................. 5-23
Sample JCL for Assembling IN25UCOM .................................................... 5-24
Add Assembler DSECTs to the Symbolic File ................................................... 5-25
Sample JCL for Adding Members to the Symbolic File ....................................... 5-25
Sample JCL for Defining CORE Keywords .................................................. 5-26
Unprotect Main Storage with User Exit IN25LETX .............................................. 5-27
IN25LETX COMMAREA .................................................................... 5-27
LETX Table .............................................................................. 5-28
Sample IN25LETX Program ............................................................... 5-29
Disable IN25LETX ........................................................................ 5-30
Add COBOL File Structures to the Symbolic File ................................................ 5-31
Specify Non-Intercepted Abend Codes ........................................................ 5-32
Customize Help for Abend Codes ............................................................. 5-34

Contents

Chapter 6: Handling Special Situations

Special Considerations for MRO Support ....................................................... 6-1
Monitor Considerations for DFLTUSER...................................................... 6-2
Additional Monitoring Considerations ...................................................... 6-4
Remote FILE Support ..................................................................... 6-5
DB2 Application Program Support ............................................................. 6-5
Calls to Software and User Macro Support ..................................................... 6-7
How Support Is Provided.................................................................. 6-7
Code IN25UEX Macros for Called Software ................................................. 6-8
Support Your Site's Global Routines ...................................................... 6-10
Code the ROUT= Routine ................................................................ 6-11
Sample JCL for Generating the IN25UEXI Programs ........................................ 6-12
IN25UEXI Instructions for Additional Vendor Products...................................... 6-14
Handle Wild Branches ....................................................................... 6-16
Monitor a Wild Branch ................................................................... 6-16
Use the FOL=ON Option ................................................................. 6-17
IBM's EXEC Debugging Facility (EDF) Support ................................................. 6-17
Advantages of AllFusion CA-InterTest for CICS over EDF ................................... 6-17
Use AllFusion CA-InterTest for CICS with EDF ............................................. 6-18
HOGAN Software Support.................................................................... 6-19
Use Considerations ...................................................................... 6-19
Installation Procedure ................................................................... 6-19

Chapter 7: Password Protection

Required Parameters ......................................................................... 7-2
Specify Passwords for the CORE Facility ....................................................... 7-2
Specify Passwords for Files and DL/I Databases ................................................ 7-3
Specify Passwords for CNTL Commands and Options ........................................... 7-4
Password Protected CNTL Commands ...................................................... 7-5
Password Protected CNTL Options ......................................................... 7-6
Sample IN25SEC2 Assembly JCL .............................................................. 7-8

Chapter 8: Automatically Starting AllFusion CA-InterTest for

CICS
Use the PROMMAC Macro ..................................................................... 8-1
Enter CNTL Commands from a CRLP-type Terminal ............................................. 8-3
Activate AllFusion CA-InterTest for CICS from a Program ....................................... 8-3

Getting Started

Start AllFusion CA-InterTest for CICS from a PLT ............................................... 8-4

Automatic Startup in CICSPlex Regions ........................................................ 8-5

Chapter 9: Troubleshooting
Diagnostic Procedures ........................................................................ 9-2
Collect Diagnostic Data ....................................................................... 9-3
Interprete Diagnostic Data ................................................................ 9-3
Access the Online Client Support System ................................................... 9-4
Call Technical Support .................................................................... 9-4
Product Releases and Maintenance ......................................................... 9-5
Request Enhancements ................................................................... 9-5

Chapter 10: Applying Maintenance

Overview ................................................................................... 10-1
SMP/E Libraries .......................................................................... 10-1
APPLY and ACCEPT Commands ........................................................... 10-1
Maintenance Delivery ........................................................................ 10-2
Informational APAR or PIB ................................................................ 10-2
Program Temporary Fixes ................................................................ 10-3
PTF Maintenance Installation ................................................................. 10-3
Overview of Maintenance Steps ............................................................... 10-3
Step 1. Review and Follow the Instructions .................................................... 10-4
Step 2. Unload the ZIP File ................................................................... 10-4
Step 3. Upload the Binary Files ............................................................... 10-4
Step 4. Receive Maintenance ................................................................. 10-5
Step 5. Run APPLY CHECK Maintenance ....................................................... 10-5
Step 6. Restore Any Applicable SYSMODs ..................................................... 10-5
Step 7. Apply Maintenance ................................................................... 10-6
Step 8. Reapply Any Applicable SYSMODs ..................................................... 10-6
Step 9. Execute IVP to Validate Maintenance .................................................. 10-6
Step 10. Accept Maintenance ................................................................. 10-7
Step 11. Save All Materials and Output........................................................ 10-7

Index

Contents

vii

Chapter 1: Introduction
AllFusion CA-InterTestTM for CICS is a powerful interactive tool for testing and
debugging CICS COBOL, PL/I, and Assembler programs. Testing and
debugging is one of the most time consuming and important phases of
application development. The interactive testing facilities of AllFusion
CA-InterTest for CICS dramatically improve testing efficiency and application
quality.
AllFusion CA-InterTest for CICS works online to trap all application errors
known to CICS. It lets you resolve multiple errors interactively as they occur,
without having to recompile or end the test session.

Interactive System Productivity Facility-Like Menu Interface

A high-level Interactive System Productivity Facility (ISPF)-like menu interface
makes it easy for both experienced and novice users to take advantage of the
power of AllFusion CA-InterTest for CICS and navigate among its many
functions. For example, you can do the following:

Select the program you want to debug

Display the monitoring options in effect for a program

Set and remove breakpoints

Display and modify main storage

Display and modify files and databases

Invoke the optional AllFusion CA-SymDump for CICS dump analysis

facility

Test and Debug Directly from Your Source Listing

You can also work directly from the comfort of your familiar source code to do
the following:

Initiate program monitoring

Set and remove breakpoints

Correct problems and continue testing from any program location

Single-step through the executed code path

Change program execution with pseudocode

Chapter 1: Introduction

Prevent Abends by Trapping All Application Errors Online

Display and modify main storage

Display and modify files and databases

You never have to wait for printouts because AllFusion CA-InterTest for CICS
provides immediate, online access to your programs source listing and
compiler information such as maps, cross-reference tables, and messages
information your online editor cannot provide.

Prevent Abends by Trapping All Application Errors Online

As your program executes, the AllFusion CA-InterTest for CICS monitor works
online to check all statements before they are executed. This lets AllFusion
CA-InterTest for CICS detect any application error that could cause a program
to fail or damage CICS. When an error is detected, AllFusion CA-InterTest for
CICS automatically suspends program execution before the program fails or
the CICS region is corrupted. This halt in execution is called an automatic
breakpoint. When an automatic breakpoint occurs, your system is protected
and your interactive debugging can begin immediately.

Set Breakpoints to Interrupt Program Execution

You can set breakpoints to interrupt program execution at any point. At each
breakpoint, the source listing positioned at the breakpoint is displayed. You
can then change program variables or data areas in main storage, set or
remove other breakpoints, dynamically change the programs execution path,
retrace the programs execution path, inspect and modify files and databases,
abend the program, and perform many other debugging tasks.
AllFusion CA-InterTest for CICS provides several types of breakpoints to give
you maximum flexibility in designing test scenarios:
Unconditional
The program stops whenever execution reaches a specified location.
Variable-Change
The program stops whenever the value of a variable changes.
Request
The program stops when it reaches specified CICS commands or macros,
calls to DL/I and DB2, or calls to subroutines, such as database software.
Single-Step
The program stops each time it executes a specified number of COBOL
verbs, PL/I statements, or Assembler instructions.

Getting Started

Control Program Execution to Test All Program Paths

AllFusion CA-InterTest for CICS lets you completely control program
execution. Not only can you stop execution at any point, you can also
resume execution from any point. Such flexibility makes it easy to test
particular program sections or circumvent an error. You can also write and
execute pseudocode to dynamically change your programs execution path
during testingwithout recompiling. By using one or more of these methods to
control program execution, you can be sure that all program paths have been
tested.

CICSPlex Exploitation
AllFusion CA-InterTest for CICS exploits the CICSPlex environment by
monitoring a program wherever it executes in the CICSPlex. Breakpoint and
other debugging information is sent to you, regardless of the region in which
the program actually executes. AllFusion CA-InterTest for CICS also supports
non-CICSPlex multiregion operations and intersystem communications
(MRO/ISC) configurations.

Ease-of-Use Features
CICS programmers can quickly benefit from the many features of AllFusion
CA-InterTest for CICS because it so easy to learn and use. The following list
describes some of the reasons:

High-level, ISPF-like menu interface.

Online access to source listings and compiler output.

The ability to perform most tasks directly from source listing displays.

A fast path for experienced users.

No need to worry about displacement or address changes after recompiling

because all locations can be referenced by program-defined names
(symbolic reference).

A comprehensive Help facility that is available from every AllFusion

CA-InterTest for CICS screen and directly from CICS, which includes
detailed information about all CICS abend codes and AllFusion
CA-InterTest for CICS error messages.

Demo sessions for COBOL, COBOL II, COBOL/370, PL/I, and Assembler
users that demonstrate key AllFusion CA-InterTest for CICS features and
help train new users.

Chapter 1: Introduction

Symbolic Support Facilitates Problem Solving

To speed error resolution, AllFusion CA-InterTest for CICS lets you identify
program locations symbolically without computing addresses or displacements,
and without worrying about address changes after recompilation. Full symbolic
support is provided, even for modules that consist of separately compiled
programs link-edited together. These statically-called programs can be written
in different languages, and each subprogram can be debugged as a separate
program. AllFusion CA-InterTest for CICS can also debug dynamically-called
programs.

Display and Update Data Values from Your Source Listing

Display
You can display and update any data values from the convenience of the
AllFusion CA-InterTest for CICS source code display without having to
interrupt or leave your test session. AllFusion CA-InterTest for CICS lets you
invoke Keep windows from the source listing. These specialized windows
display user-specified data values, registers, or storage area contents at
breakpoints. You can also use the Keep window to automatically display the
contents of all data items on the current program statement. From within the
Keep window you can easily change any of the displayed items by simply
overtyping their contents. The data in a Keep window can be displayed in HEX
or Display format.

View and Modify Storage/Files without Interrupting the Test

Session
AllFusion CA-InterTest for CICS main storage and file access facilities save
time and effort during testing. You can access these facilities, which can be
secured, directly from any AllFusion CA-InterTest for CICS screen. The storage
facility lets you easily display and modify data in main storage by simply
overtyping the displayed data, or you can use the AllFusion CA-InterTest for
CICS COBOL-like MOVE statement to change the value of a variable when you
do not know the type of data (binary, packed, and others) or its length.
AllFusion CA-InterTest for CICS takes care of all of the details for you.
A power STORAGE command may be used to list all CICS storage, which was
acquired using EXEC CICS GETMAIN. This lets the application programmer
quickly navigate to individual pieces of storage.
The AllFusion CA-InterTest for CICS FILE facility lets you update files or create
test data without writing one-time programs or leaving the test session.

Getting Started

Structured File Display Makes Data Easy on the Eyes

Authorized users can perform any I/O function provided by CICS or DL/I for
accessing and updating Virtual Storage Access Method (VSAM), Basic Direct
Access Method (BDAM), and DL/I database data. The DB2 facility lets you
display and update DB2 tables using SQL.

Structured File Display Makes Data Easy on the Eyes

Structured File Display makes it easy to view and modify data accessed
through the AllFusion CA-InterTest for CICS FILE facility. It presents the
records of a file, transient data queue, temporary storage queue, or DL/I
segment. The information is presented in a field-by-field manner, mapped to
the data structure you are accustomed to, providing an immediate frame of
reference. Structured fields are shown in hexadecimal or character format, and
you can change data by overtyping the contents right on the screen.

Trace Program Execution

The Backtrace facility lets you retrace a programs path of execution and
understand its logic. With both statement-by-statement and block-by-block
tracing capabilities, AllFusion CA-InterTest for CICS helps you answer the
question, How did I get to this point?
A powerful CALLTRACE command may be used while at a breakpoint to show
program and csect flow, of all active programs at the point of the breakpoint.
CALLTRACE will work for any application which uses EXEC CICS LINKs and
CSECT to CSECT tracing must follow standard register save area conventions.

Code Coverage
The Code Coverage (or COUNTS) feature lets you view the number of times
each program statement was executed during your program testing. This
feature makes it easy to identify program statements that were or were not
executedquickly identifying untested code. You can accumulate program
statement counts across multiple executions of the same program.

Chapter 1: Introduction

Dynamically Change Program Execution

The Indirect Commands facility lets you dynamically correct errors for all users
during a debug session. Using this facility, you can write and execute
pseudocode to change the flow of COBOL and PL/I programs without
recompiling. Indirect commands are executed automatically at a
predetermined location in a monitored program.

Monitoring by CICS User ID

You can restrict monitoring and breakpoints to a specific CICS user IDa
capability that lets a user switch terminals or terminal sessions and retain
established monitoring options. In addition, user ID monitoring makes it
possible to isolate a test session from sessions of other users of the same
program. This function is ideally suited to testing and debugging CICS Web
applications, or isolating and debugging a rogue production application without
affecting other users.

Interactively Debug Applications That Access DB2

In addition to performing SQL functions, AllFusion CA-InterTest for CICS
provides facilities for testing and debugging CICS applications that access
DB2. When you are testing DB2 applications, you can even set breakpoints
based upon SQL return codes. At each breakpoint, you can symbolically
display DB2 areas and perform other CICS and DB2-related debugging
functions. Moreover, the DB2 return code and its related message are
available online at any breakpoint. You can also use the CORE=LASTSQL
command to view the last SQL statement that was executed while sitting at a
breakpoint.

Helpful Diagnostic Information

Whenever AllFusion CA-InterTest for CICS detects an error, it provides
diagnostic information to help you find the error and determine why it
occurred. In addition, the Help facility provides context-sensitive explanations
of each abend and suggestions on how to use AllFusion CA-InterTest for CICS
to correct the error. Sites can define their own user abend codes with
associated problem descriptions to identify the cause of a preprogrammed
abend. An abend code can be associated with a particular program or it can
override the AllFusion CA-InterTest for CICS default description.

Getting Started

Synchronized Processing

Synchronized Processing
To ensure that the correct version of your source code is used, AllFusion
CA-InterTest for CICS provides symbolic file and load module synchronization.
When a program is selected for testing, AllFusion CA-InterTest for CICS
compares the date and time in the source listing to the date and time in the
load module. If no matching files are found, AllFusion CA-InterTest for CICS
displays a File Selection List from which you can select the correct file.

Immediate Support for CICS Releases

AllFusion CA-InterTest for CICS supports all current CICS releases, including
z/OS, CICS/ESA releases, and CICS/VSE releases. Immediate support helps
MIS managers implement successful migration projects.

Debug Production Applications Symbolically from Any CICS

Region
Even the most thoroughly tested program can abend in production. AllFusion
CA-SymDump for CICS, an optional component of AllFusion CA-InterTest for
CICS for z/OS users, lets you debug transaction abends symbolically without
having to analyze dumps.
By using AllFusion CA-InterTest for CICS breakpoint facilities, AllFusion
CA-SymDump for CICS automatically pinpoints the source listing statement
responsible for the abend. Its powerful trace and program call facilities make it
easy to determine the execution path. The full power of AllFusion CA-InterTest
for CICS is available to help you quickly solve each problem interactively.
In addition, AllFusion CA-SymDump for CICS gives you all of the control of a
complete dump management package. You can manage the AllFusion
CA-SymDump for CICS data set online by listing all dumps, selecting dumps to
view, deleting dumps, and holding dumps for later use.

Chapter 1: Introduction

Chapter 2: Getting Started

This guide is for z/OS systems running under CICS/TS 2.2, CICS/TS 2.3,
CICS/TS 3.1, and CICS/TS 3.2. It explains how to install AllFusion
CA-InterTest for CICS.
Do not use this guide to install AllFusion CA-InterTest for CICS on VSE
systems; there are separate installation tapes and guides available for these
systems. For additional information on how to contact CA, see the chapter
Troubleshooting.

What You Need to Get Started

CA provides the following materials for installing and using AllFusion
CA-InterTest for CICS.

A standard label magnetic cartridge, electronically downloaded tape image

files, or standard label magnetic tape recorded at 6250 BPI (DCB=DEN=4)
containing the AllFusion CA-InterTest for CICS product. The Volume Serial
number is BAyymm. The tape contents are:
-

DSN=CAI.SAMPJCL (File number 9): This is an unloaded PDS

containing the entire sample JCL referred to in this document that
pertains to the installation and execution of AllFusion CA-InterTest for
CICS. Load using IEBCOPY.

DSN=SMPMCS (File number 32): This file contains the SMP

modification control statements (MCS) used by SMP to install AllFusion
CA-InterTest for CICS.

Files beyond 32 are the SMP RELFILES, which SMP downloads to disk
during RECEIVE processing.

Comprehensive documentation that explains how to use, install,

customize, and maintain AllFusion CA-InterTest for CICS.

Tape Contents and FormatThe machine-readable program materials

required for installation are distributed as a multifile installation tape in
SMP format. This tape contains all the necessary data to install and
execute AllFusion CA-InterTest for CICS.

Distribution tapes contain pre-generated versions of AllFusion CA-InterTest for

CICS. The pre-generated versions use all of the default installation options. If
you think you need to customize the product for a particular need, see the
chapters Options and Handling Special Situations.

Chapter 2: Getting Started

Major SMP Operations

Use the IBM-supplied System Modification Program/Extended (SMP/E) to

install, customize, and maintain AllFusion CA-InterTest for CICS. This program
lets you control these activities in a consistent manner.

Major SMP Operations

SMP performs three major operations when installing a product or performing
maintenance. These operations manage a structure where a product is present
in two places: distribution libraries and target system libraries. The distribution
libraries are used for maintenance operations only. The product executes from
the target system libraries.
The operations performed are:
RECEIVE ProcessingSMP loads the installation tape into temporary data
sets. If an error is detected or you want to stop the process at this point, you
can run a REJECT operation, which will undo anything done during RECEIVE
processing.
APPLY ProcessingDuring APPLY processing, SMP performs the operations
dictated by the modification control statements (MCS) and updates the target
system libraries. You can then test the modification. If the installation is to be
terminated at this point, you can run a RESTORE operation, which restores the
system libraries from the distribution libraries.
ACCEPT ProcessingRunning the ACCEPT operation permanently places the
modification in the distribution libraries. There is no direct way to undo the
modification once the ACCEPT process has been run.

Getting Started

Chapter 3: System Requirements

This chapter helps you prepare for installation by listing the hardware and
software components needed to install and operate AllFusion CA-InterTest for
CICS and by discussing cross-product considerations.
Topics discussed include the following items:

Operating environments

CA Common Services for z/OS

Hardware requirements for distribution and target libraries

Special considerations

Migration considerations

Operating Environments
The pre-generated versions provided on this tape support any z/OS operating
system running on any hardware with IBM CICS Transaction Server (TS)
Release 2.2, 2.3, 3.1, and 3.2. This tape includes pre-generated versions of
AllFusion CA-InterTest for CICS, for CICS TS 2.2, 2.3, 3.1, and 3.2.
Database management systems DL/I and DB2 are fully supported by the
pre-generated versions without modification. If you need to support other
systems (such as TOTAL, AllFusion CA-IDMS/DB Database or AllFusion
CA-Datacom/DB Database) or calls to software that should not be monitored
by AllFusion CA-InterTest for CICS, see the chapter Handling Special
Situations.

CA Common Services for z/OS Requirements

AllFusion CA-InterTest for CICS requires the following CA Common Services
for z/OS:

CAIRIM

CA LMP

AllFusion CA-InterTest for CICS support for CICSPlex and/or dynamic symbolic
support for AllFusion Endevor Change Manager require the following
additional CA Common Services for z/OS: CAICCI for MVS.

Chapter 3: System Requirements

CA Common Services for z/OS Requirements

The CA Common Services for z/OS must be installed or maintained at the

genlevel indicated on the cover letter for the product. If you have other CA
products installed at your site, some of these services may already be
installed. If the CA Common Services for z/OS have not been installed already
on your system, you must do so before proceeding with this installation.
See the CA Common Services for z/OS Getting Started for more information
about CA Common Services for z/OS and for detailed installation instructions.

CAIRIM
CAIRIM, CAI Resource Initialization Manager, is the common driver for a
collection of dynamic initialization routines that eliminate the need for user
SVCs, SMF exits, subsystems, and other installation requirements commonly
encountered when installing systems software. The following list contains
some of the features of CAIRIM:

Obtaining SMF data

Verification of proper software installation

Installation of MVS interfaces

Automatic startup of CA and other vendor products

Proper timing and order of initialization

Note: CAIRIM is required to run CA LMP

CA LMP
The CA License Management Program provides a standardized and automated
approach to the tracking of licensed software. It uses common real-time
enforcement software to validate the users configuration. CA LMP reports on
activities related to the license, usage, and financials of program solutions. CA
LMP includes the following features:

A common key data set that can be shared among many CPUs

Using check digits to detect errors in transcribing key information

Execution keys can be entered without affecting any CA software solution

already running

No special maintenance requirements

Note: CA LMP is required to run AllFusion CA-InterTest for CICS

Getting Started

CA-Hardware Requirements

CAICCI
AllFusion CA-InterTest for CICS installations that do not require CICSPlex
support do not need to install CAICCI. However, if you plan to use AllFusion
CA-InterTest for CICS support for CICSPlex environments, CAICCI for MVS is
required. For CICSPlex support, CAICCI must be installed in each MVS/CICS
region that is a CICSPlex family member.
CAICCI (CAI Common Communications Interface) enables CA products to
communicate with one another. This facility provides a layer that isolates
application software from the specifics of the communications environment.
CAICCI is a started task used for sending messages between CA products. It
usually runs continuously whenever the operating system is active.
AllFusion CA-InterTest for CICS uses CAICCI to facilitate testing and
debugging in CICSPlex environments. In particular, it uses CAICCI to send and
receive the monitoring commands to and from the CICSPlex family member
CICS regions. This automatically propagates monitoring activity to all regions
participating in the CICSPlex environment.

CA-Hardware Requirements
Estimates for the amount of disk space needed to install AllFusion
CA-InterTest for CICS are given next.

Distribution Libraries
The following table estimates disk space for the distribution libraries required
to install AllFusion CA-InterTest for CICS.
Name

Blksize

Blocks

Dir. Blks.

Description

CAI.CBA8062D

6144

600

Load modules CICS TS 2.2

CAI.CBA8063D

6144

600

Load modules CICS TS 2.3

CAI.CBA8064D

6144

600

Load modules CICS TS 3.1

CAI.CBA8065D

6144

600

Load modules CICS TS 3.2

CAI.CBA80SLD

3120

250

Sample source and JCL

CAI.CVH80LLD

6144

300

Testing and Fault Management Symbolic

Component load modules

CAI.CVH80SLD

3120

Testing and Fault Management Symbolic

Component macros and samples

Chapter 3: System Requirements

CA-Hardware Requirements

Target Libraries
The following table estimates disk space for the target libraries required to
install AllFusion CA-InterTest for CICS. These libraries must be allocated if
they do not already exist for some other CA product at your site.
Name

Blksize

Blocks

Dir. Blks.

Description

CAI.SAMPLIB

3120

250

Sample source library

CAI.CACICS62

6144

600

CICS TS 2.2 load library

CAI.CACICS63

6144

600

CICS TS 2.3 load library

CAI.CACICS64

6144

600

CICS TS 3.1 load library

CAI.CACICS65

6144

600

CICS TS 3.2 load library

CAI.PROTHLF

4096(CI)

1000

N/A

Help file (VSAM)

CAI.PROTUHF

4096(CI)

1000

N/A

User-defined help file for abend codes

(VSAM)

CAI.PROTSYM

2048(CI)

8000
(records)

N/A

Symbolic file (VSAM)

CAI.PROTCPF

4096(CI)

N/A

Checkpoint file (VSAM)

CAI.CAILIB

6144

300

Testing and Fault Management Symbolic

Component load library

CAI.CAIMAC
CAI.CAIPROC

Getting Started

3120
3120

20
20

2
2

Testing and Fault Management Symbolic

Component macros
Testing and Fault Management Symbolic
Component sample procedures

Special Considerations

Special Considerations
Additional considerations apply under the circumstances described next.

PL/I Programs
Programs that contain arrays must be recompiled with the IN25SYMP
post-processor provided with 6.1, or later, if the support for complex arrays is
to be available.

Global User Exits

This AllFusion CA-InterTest for CICS release requires the use of the following
global user exits:
XPCFTCH and XPCTARequired for the CNTL=START and CNTL=END
commands to operate AllFusion CA-InterTest for CICS and control monitoring.
XDUREQRequired for dump suppression.
XMEOUTRequired for suppression of abend messages.
When monitoring programs observe the following rules:

Do not disable the previous global user exits in any way. This action
causes AllFusion CA-InterTest for CICS to stop functioning.

The AllFusion CA-InterTest for CICS global user exits honor the return
codes set by previous exits, which may have an impact on whether
AllFusion CA-InterTest for CICS successfully monitors a program. If you
are having problems caused by other CICS global user exits setting a
return code before AllFusion CA-InterTest for CICS exits receive control,
you can guarantee that the AllFusion CA-InterTest for CICS exits are first
to receive control by adding the program entry IN25PLTX to the CICS
startup PLT. IN25PLTX is required as the first program entry in Phase 1
(prior to the DFHDELIM entry) of the PLT.

If other exits receive control after AllFusion CA-InterTest for CICS, they
must not change the return code or entry point fields in the user exit
parameter list.

To disable AllFusion CA-InterTest for CICS you must use the CNTL=END
command.

Failure to observe the above rules will disable monitoring. For example,
AllFusion CA-InterTest for CICS monitoring is not performed if another exit
receives control before AllFusion CA-InterTest for CICS and passes on a
modified return code or entry point.

Chapter 3: System Requirements

Special Considerations

Terminal Input/Output Area Compression Routine Users

AllFusion CA-InterTest for CICS transactions and programs must be excluded
from any Terminal Input/Output Area (TIOA) compression packages or
routines, such as 3270 Super Optimizer/CICS and CTOP. Failure to do so will
produce unpredictable results because AllFusion CA-InterTest for CICS uses
saved TIOAs. In addition, the AllFusion CA-InterTest for CICS FILE facility may
not work properly with data files that have been put through data compression
routines.

CICSPlex Support
AllFusion CA-InterTest for CICS provides special, optional support for CICS
regions participating in a CICSPlex environment. If AllFusion CA-InterTest for
CICS is installed with CICSPlex support, participating CICS regions have
AllFusion CA-InterTest for CICS commands and breakpoints automatically
propagated to all regions in the CICSPlex. This allows for easier debugging of
dynamically routed transactions and programs. For details on which
commands are propagated across a CICSPlex, see the User Guide.

Installation Requirements for CICSPlex Support

CICSPlex command propagation is accomplished mainly through CAICCI for
MVS, a CA Common Service for z/OS. Other than installing CAICCI for MVS
and setting a few customization options, as listed next, you do not need
anything else to obtain CICSPlex support.
To install AllFusion CA-InterTest for CICS with CICSPlex support, you need to
perform these steps:
1.

Install CAICCI in all participating CICSPlex regions as discussed in the

section CA Common Services for z/OS Requirements.

Follow normal installation instructions for the product, as discussed in the

chapter Base Product Installation Steps.

Use the following IN25OPTS customization options in each participating

CICSPlex region:

CICSPLEX=YES

CPLXFMID=a-CICSPlex-family-name

CPLXCKPI=hhmm (a checkpoint interval)

For details on setting these options, see the chapter Options.

Note: Support for multiple CICSPlex families within or across multiple MVS
regions can be obtained by changing the CPLXFMID family name associated
with each region.

Getting Started

Special Considerations

Startup and Termination with CICSPlex Support

AllFusion CA-InterTest for CICS regions installed with CICSPLEX=YES are
affected during startup and termination in the following ways:

The CNTL=START and CNTL=RESTART commands automatically have

AllFusion CA-InterTest for CICS resynchronize monitoring with any active
regions in the CICSPlex upon startup

The CNTL=END, SCOPE=GLOBAL command can be issued to concurrently

terminate all AllFusion CA-InterTest for CICS processing in all connected
regions in the CICSPlex

Dynamic Symbolic Support for AllFusion Endevor Change Manager

AllFusion CA-InterTest for CICS provides special, optional support for
AllFusion Endevor Change Manager users to dynamically load application
program symbolic information from AllFusion Endevor when the Footprint
option is in use. If AllFusion CA-InterTest for CICS is installed with AllFusion
Endevor support, participating CICS regions will load program symbolics using
this feature. This allows debugging to proceed when application program
symbolics are not found in the CICS regions Protsym files.
To support this feature, the following products are required:

AllFusion Endevor Change Manger r7 SP 2 or later.

AllFusion Endevor AUTHLIB, CONLIB, and the data set containing

C1DEFLTS must be in the LNKLIST.

C1DEFLTS. Add the keyword COMPLISTWD=.LIST to the CIDEFLTS

TYPE=MAIN section. This keyword identifies the text string that AllFusion
Endevor looks for in an elements component list to identify the listing data
set for the print element listing function. The period (.) before the
variable LIST is used as a wildcard to denote anywhere within the DSN
(LISTLIB, LISTING, COBLIST, for example). Change the variable LIST to
conform to your DSN naming conventions for compiler and assembler
output files.

Note the following:

The listings must be created by an AllFusion Endevor generate process.

The listing data set created by the AllFusion Endevor generate process
must be monitored by AllFusion Endevor with the following DD statement
coded:
MONITOR=COMPONENT,FOOTPRINT=CREATE

The object and load module libraries must use the footprint feature with
the following coded on their respective DD statements:
FOOTPRINT=CREATE

Chapter 3: System Requirements

Special Considerations

eTrust CA-ACF2 and RACF Users

For eTrust CA-ACF2 Users To use AllFusion CA-InterTest for CICS with
eTrust CA-ACF2, add the transactions IPLX, ISER, VTAT, LIST, and VIRC to
your ACF2 SAFELIST.
For additional information on these AllFusion CA-InterTest for CICS
transactions, see the chapter Options. For instructions on adding
transactions to the SAFELIST, see the eTrust CA-ACF2 for z/OS CICS Support
Guide.
For RACF Users To use AllFusion CA-InterTest for CICS with RACF, the
AllFusion CA-InterTest for CICS transactions IPLX, ISER, VIRC, LIST, and VTAT
must be defined to CICS with CMDSEC(NO) and RESSEC(NO). All AllFusion
CA-InterTest for CICS transactions and programs require UACC(READ) for
EXEC CICS INQUIRE commands to give all users RACF READ access. Without
these settings, the symbolics for a source listing breakpoint display may not
be available to users.
If RACF file level security is in use, you must also add the following statements
to the xCICSFCT resource class:
PROTSYM, PROTHLF ...UACC(READ)
PROTCPF, PROTUHF ...UACC(UPDATE)

AllFusion CA-Realia II Workbench Option for CICS Users

This version provides full support for AllFusion CA-Realia II Workbench Option
for CICS. Refer to the AllFusion CA-Realia II Workbench Option for CICS User
Guide for instructions on using the WH= parameter with the appropriate
COBOL post-processor.

Database Support
Database management systems DL/I, DB2, and ADABAS are fully supported
by the pre-generated versions without modification. If you need to support
other systems (such as AllFusion CA-IDMS/DB, AllFusion CA-Datacom/DB, or
TOTAL) or calls to software that should not be monitored by AllFusion
CA-InterTest for CICS, see the chapter Handling Special Situations.

HOGAN Users
For detailed instructions on setting up AllFusion CA-InterTest for CICS to
support HOGAN, see the chapter Handling Special Situations.

Getting Started

Special Considerations

MRO Users
For detailed instructions on setting up AllFusion CA-InterTest for CICS to
support MRO, see the chapter Handling Special Situations.

Omegamon Users
To use AllFusion CA-InterTest for CICS with Omegamon Version 450 or
subsequent versions, you must start Omegamon before you start AllFusion
CA-InterTest for CICS.
To use AllFusion CA-InterTest for CICS with Omegamon, AllFusion
CA-InterTest for CICS transactions must be excluded from the Omegamon
Resource Limit (Time Out) Specification.

TMON Users
To use AllFusion CA-InterTest with TMON, AllFusion CA-InterTest for CICS
transactions must be excluded from the TMON Resource Limit (Time Out)
Specification.

User CORE Commands

To generate your own CORE commands, see the chapter Handling Special
Situations.

User Macros and Software Calls Support

If you need to support user macros and software calls, see the chapter
Handling Special Situations.

Data Monitoring
The data monitoring feature of AllFusion CA-InterTest for CICS requires a
significant amount of storage over and above the storage required by the
programs being monitored. Compute the storage requirements as follows:
500 bytes * number of transaction entries as defined by the STMTTRCE
option + size of mirror area for each program in the transaction for which data
monitoring is active, where the mirror area is equal to the size of storage for
the monitored program.

Chapter 3: System Requirements

C6.1C to r8 Migration Considerations

If you should encounter storage problems while using the data monitoring
feature, perform one or more of the following actions:

Reduce the use of data monitoring in the region.

Make the STMTTRCE value smaller in the default options table, IN25OPTS.

Increase the EDSALIM for the CICS region.

6.1 to r8 Migration Considerations

Pre-existing AllFusion CA-InterTest for CICS CustomizationIf you
have customized AllFusion CA-InterTest for CICS (IN25OPTS, IN25LETX,
IN25UCOM, and IN25UEXI) make sure you redo the modifications after
AllFusion CA-InterTest for CICS is installed.
Additionally, the symbolic file format for r8 is compatible with all of the
following releases:

At least AllFusion CA-InterTest Batch 3.1

At least AllFusion CA-Optimizer/II r7

At least AllFusion CA-SymDump Batch r7

At least AllFusion CA-SymDump for CICS 6.1 and (with compatibility PTFs)

CICS Program Definition RequirementsThis release requires new

AllFusion CA-InterTest for CICS programs. The resource definitions from
previous releases will not work properly with this release.
CICS/COMET SupportSupport is provided for both mixed- and macro-level
programs controlled by Technologic Software's CICS/COMET.
IN25UEXIPre-generated IN25UEXI is provided for AllFusion CA-IDMS/DB,
AllFusion CA-Datacom/DB, AllFusion CA-Telon, Unicenter CA-Sort, DB2, and
MQSERIES, CICSPlex/SM, and TCP/IP Sockets Interface.
CA-ACF2 and RACFAdditional transactions must be granted unrestricted
security. For details, see the section eTrust CA-ACF2 and RACF Users.

310

Getting Started

C6.0C to r8 Migration Considerations

6.0 to r8 Migration Considerations

If you are migrating from an AllFusion CA-InterTest for CICS 6.0 to AllFusion
CA-InterTest for CICS r8, you may have some additional considerations, which
are discussed next.
Symbolics produced by AllFusion CA-InterTest for CICS r8 are not downward
compatible with AllFusion CA-InterTest for CICS 6.0.
IN25OPTS Macro Changes The IN25OPTS macro differs from the IN25OPTS
macro in 6.0. New parameters have been added to support various new
features of AllFusion CA-InterTest for CICS. For more information, see the
chapter Options.

Chapter 3: System Requirements

311

Chapter 4: Base Product Installation

Steps
AllFusion CA-InterTest for CICS is installed using SMP/E. The installation
process consists of the following steps:

Installing required CA Common Services for z/OS

Entering AllFusion CA-InterTest for CICS product keys for CA LMP check

Loading and modifying the supplied sample JCL library

Allocating libraries

Executing an SMP/E RECEIVE function

Executing an SMP/E APPLY function

Executing an SMP/E ACCEPT function

Defining and loading the Help data set

Creating the user-defined help file for abend descriptions (optional)

Defining and loading the symbolic file

Creating the checkpoint file

Adding entries to the CICS tables

Updating the CICS JCL and Startup parameters

Installing DB2 support (optional)

Executing the check-out program

Installing PL/I support (optional)

Installing dynamic symbolic support for AllFusion Endevor Change Manager

(optional)

Note: You must install the required CA Common Services for z/OS components
before proceeding with an SMP/E installation of AllFusion CA-InterTest for
CICS.

Chapter 4: Base Product Installation Steps

Summary of Installation Steps

Note: AllFusion CA-InterTest for CICS and AllFusion CA-SymDump for CICS
share common components. The release and maintenance level of the two
products must be equivalent. If your site has previously installed AllFusion
CA-SymDump for CICS as a separate product, the following procedures must
install AllFusion CA-InterTest for CICS to the same set of libraries. In this
case, skip Steps 5, 6, and 11; Steps 11a and 12 are optional. The creation of
the User Help File and any new symbolic files is left completely up to you.
The following table lists the steps involved in the AllFusion CA-InterTest for
CICS installation process. Review this table before installing AllFusion
CA-InterTest for CICS, and then use it as a checklist during the actual
installation.
Step

Description

Step 1.

Review system requirements.

Be sure all of the requirements are met before installing
AllFusion CA-InterTest for CICS.

Step 2.

Enter LMP product key certificate Information.

Step 3.

Complete the installation worksheet.

Modify the default values that do not meet your data centers
standards. Use the worksheet as a guide when modifying the
installation JCL.

Getting Started

Step 4.

Load the sample installation JCL from the tape.

Step 5.

Allocate target and distribution libraries.

Step 6.

Allocate private SMP/E libraries and define SMP zones.

Step 7.

Customize the SMP procedure.

Step 8.

Receive the product.

Step 9.

Apply the product.

Step 10.

Accept the product.

Step 11.

Install the Help facility.

Step 11a.

Create the user-defined abend description file (optional).

Step 12.

Create the symbolic file

Step 13.

Create the checkpoint file.

Step 14.

Add the required CICS resource definitions.

Step 15.

Update the CICS startup JCL and startup parameters.

Step 16.

Install DB2 support (optional).

Step 1. Review System Requirements

Step

Description

Step 17.

Restart CICS and run check-out program.

Step 18.

Install dynamic symbolic support for AllFusion Endevor

Change Manager (optional).

Step 19.

Check for latest maintenance.

After installing AllFusion CA-InterTest for CICS (and the PL/I option if you are
licensed for it), adjust the compile and assemble procedures for COBOL,
COBOL II and higher, Assembler, and PL/I. See the AllFusion Testing and Fault
Management Symbolic guide for details.
Existing users should begin by reviewing ITST Option 8 Whats New. New
users should begin by using the demo programs before using
AllFusion CA-InterTest for CICS on their own programs.

Step 1. Review System Requirements

Be sure that your system meets all of the requirements given in the System
Requirements chapter before installing AllFusion CA-InterTest for CICS.

Step 2. Enter LMP Product Key Certificate Information

You must enter the LMP key information for AllFusion CA-InterTest for CICS. If
you purchased the PL/I Symbolic Facility and AllFusion CA-SymDump for CICS
options, you also need to enter the LMP key information for these options.

Use CA LMP
AllFusion CA-InterTest for CICS requires CA LMP (License Management
Program) to initialize correctly. CA LMP also provides a standardized and
automated approach to the tracking of licensed software.
Examine the CA LMP Key Certificate you received with your AllFusion
CA-InterTest for CICS installation or maintenance tape. The certificate
provides an LMP key for the AllFusion CA-InterTest for CICS base product and,
if you have purchased the PL/I Symbolic Option or AllFusion CA-SymDump for
CICS, an additional key for each option purchased.

Chapter 4: Base Product Installation Steps

Step 2. Enter LMP Product Key Certificate Information

The certificate contains the fields shown in the following table:

Fields

Descriptions

Product Name

The trademarked or registered name of the

AllFusion CA-InterTest for CICS licensed for the
designated site and CPUs.

Supplement

The reference number of your license for

AllFusion CA-InterTest for CICS in the format
nnnnnn nnn. This format differs slightly inside
and outside North America and may not be
provided in some cases.

Expiration Date

The date your license expires in the format

MONTH dd, yyyy (as in OCTOBER 21, 2001).

Technical Contact

The name of the technical contact at your site

responsible for the installation and maintenance
of AllFusion CA-InterTest for CICS. This is the
person to whom CA addresses all CA LMP
correspondence.

MIS Director

The name of the Director of MIS or the person

who performs that function. If the title, but not
the individuals name, is indicated on the
Certificate, supply the actual name when
correcting and verifying the Certificate.

CPU Location

The address of the building where the CPU is

installed.

Execution Key

An encrypted code required by CA LMP for

AllFusion CA-InterTest for CICS initialization.
During installation, it is referred to as the LMP
Code.

Product Code

A two-character code that corresponds to

AllFusion CA-InterTest for CICS.

CPU ID

The code that identifies the specific CPU on which

this installation of AllFusion CA-InterTest for CICS
is valid.

CA LMP is provided as an integral part of CAIRIM (Resource Initialization

Manager). Once CAIRIM has been installed or maintained as specified in the
cover letter for this product release, CA LMP support is available for all CA
LMP-supported software solutions.

Getting Started

Step 2. Enter LMP Product Key Certificate Information

The CA LMP execution key, provided on the Key Certificate, must be added to
the CAIRIM parameters to ensure proper initialization of the CA software
solution. To define a CA LMP execution key to the CAIRIM parameters, modify
member KEYS in OPTLIB data set. The parameter structure for member KEYS
is shown next.
PROD(pp) DATE(ddmmmyy) CPU(tttt-mmmm/ssssss)
LMPCODE(kkkkkkkkkkkkkkkk)
pp

Required. The two-character product code. For any given

CA LMP software solution, this code agrees with the
product code already in use by the CAIRIM initialization
parameters for earlier genlevels of AllFusion CA-InterTest
for CICS.

ddmmmyy

The CA LMP licensing agreement expiration date.

tttt-mmmm

Required. The CPU type and model (for example:

3090-600) on which the CA LMP software solution is to
run.
If the CPU type or model requires less than four
characters, blank spaces are inserted for the unused
characters.

ssssss

Required. The serial number of the CPU on which the CA

LMP software solution is to run.

kkkkkkkkkkkkk

Required. The execution key needed to run the CA LMP

software solution. This CA LMP execution key is provided
on the Key Certificate shipped with each CA LMP software
solution.

An example of a control card for the CA LMP execution software parameter is

shown next. In this example, the CA LMP execution key value is invalid and
provided as an example only.
PROD(BA) DATE(01JAN94) CPU(3090-600 /370623) LMPCODE(52H2K06130Z7RZD6)

Enter CA LMP Key Information for the PL/I Symbolic Options

If you purchased the PL/I Symbolic Facility option, you received an additional
execution key for each option you purchased. To define these CA LMP
execution keys to the CAIRIM parameters, modify member KEYS in the OPTLIB
data set (see the section, Using CA LMP, for instructions).

Chapter 4: Base Product Installation Steps

Step 3. Complete the Installation Worksheet

The installation worksheet, shown next, simplifies the task of tailoring the
supplied JCL. Answer each question on the worksheet, filling in the blanks with
the appropriate information. Default values are noted, so if the default value is
acceptable, leave the item blank on the worksheet. However, you must supply
appropriate volume serial numbers. The worksheet items are listed in the
approximate order in which you encounter them during the installation.
1.

What is your installation generic unit name for temporary work DASD?
Default: WORK=SYSDA

WORK=_____________

What is your installations generic unit name for the shipped installation tape?
Default: TAPE=TAPE

TAPE=______________

What is your installation standard SYSOUT class for CA product installations and SMP output?
Default: SYSOUT=*

SYSOUT=___________

What is the dsname high-level qualifier for the AllFusion CA-InterTest for CICS installation
libraries (both target and distribution libraries)?
Default: CAI=CAI.
a.

CAI=_______________

What VOL=SER do you want to use for the target libraries?

Default: TARGET=

What VOL=SER do you want to use for the distribution libraries?

Default: DLIB=

PUNIT=____________

What is the dsname high-level qualifier for the SMP libraries to be used for the installation of
CA products?
Default: CAISMP=CAI.
a.

CAISMP=___________

What VOL=SER do you want for the SMP libraries, if these libraries do not already
exist?

Default: VOLSER=

VOLSER=___________

What is your installation generic unit name for the permanent DASD SMP volumes?

Default: PERMDA=SYSDA
6.

DLIB=______________

What is your installation generic unit name for the above library volumes?
Default: PUNIT=SYSDA

TARGET=___________

PERMDA=__________

What VOL=SER do you want for the SMP temporary libraries?

TLIB=______________

Getting Started

Step 4. Load Sample Installation JCL from the Tape

The AllFusion CA-InterTest for CICS product installs using SMP/E. The product
tape received with this package contains all of the necessary data to install
and execute AllFusion CA-InterTest for CICS. Before installing the product,
load the sample JCL library from the tape. This file, DSN=CAI.SAMPJCL, is the
ninth file on the tape and is in IEBCOPY unloaded format. Use the following
JCL as a model to load the sample JCL library to DASD:
//LOAD

EXEC PGM=IEBCOPY

//SYSPRINT

SYSOUT=A

//SYSUT1

DISP=(OLD,KEEP),

DSN=CAI.SAMPJCL,
<=== generic 3480 tape cartridge

UNIT=CART,

VOL=SER=BAyymm,

LABEL=(9,SL)

<=== tape label

//SYSUT2

DSN=CAI.INTERTST.SAMPJCL,

DISP=(NEW,CATLG,DELETE),

UNIT=SYSDA,

VOL=SER=XXXXXX, <=== permanent DASD volser

<=== your DSN

<=== your generic DASD

SPACE=(3120,(40,20,10)), <=== minimum space required

DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)

//SYSUT3

SPACE=(TRK,(5,5))

//SYSUT4

SPACE=(TRK,(5,5))

//SYSIN

UNIT=SYSDA,
UNIT=SYSDA,
DUMMY

Once this job has ended, your library will contain all of the JCL needed to
complete the installation of AllFusion CA-InterTest for CICS.
To satisfy your data centers needs, certain tailoring of the JCL is necessary
while executing the steps on the following pages. Refer to the Installation
Worksheet you completed earlier in this chapter to obtain values for the
various JCL parameters.

Step 5. Allocate Target and Distribution Libraries

Note: If your site has previously installed AllFusion CA-SymDump for CICS as a
separate product, skip this step.
Member BA80ALC allocates all of the target and distribution libraries required
by AllFusion CA-InterTest for CICS during installation and maintenance.
However, many CA products have common components and libraries that may
already have been installed. Therefore, carefully analyze the installation steps
to ensure that completed steps are not repeated.

Chapter 4: Base Product Installation Steps

Step 6. Allocate Private SMP/E Libraries and Define SMP Zones

Edit the JCL to conform to your installation standards and the previously
completed worksheet. However, never change any of the ddnames or the last
qualifier of the data set names.
All space allocations supplied in this member are in blocks to allow for
compatibility between DASD types. The allocations given are the minimum
required for installing AllFusion CA-InterTest for CICS. You may want to adjust
these for your installation device types, and to allow enough free space for
maintenance (the more free space you allocate, the less often the libraries will
be compressed during maintenance). For common libraries that are already
present, be sure there is sufficient space for AllFusion CA-InterTest for CICS.
Submit member BA80ALC and review the output.

Step 6. Allocate Private SMP/E Libraries and Define SMP

Zones
Important! If you have already created SMP data sets during the installation
of another CA product, skip this task and go to Task 2, Define Additional
Product Target and Distribution Zones. Even if you skip Task 1, you must still
perform Task 2.
This step allocates and initializes the CA base SMP libraries and defines
additional product target and distribution zones.

Task 1. Allocate and Initialize CA Base SMP Libraries

This step is not required if SMP data sets have been created already during the
installation of another CA product.
Use member BAINITE5 to allocate and initialize a set of private SMP data sets
for all CA products.
We recommend that you keep CA products as distinct entities from other SMP
data sets. These members also set up CAI global, target, and distribution
zones for CA products.

Task 2. Define Additional Product Target and Distribution Zones

Next, use member BA80INIT to define additional SMP zones for a set of target
and distribution libraries for CTS 2.2, CTS 2.3, CTS 3.1, and CTS 3.2.

Getting Started

Step 7. Customize the SMP Procedure

Edit the procedure to conform to the installation standards and specifications
you entered on the installation worksheet. This procedure can be placed into a
system or user procedure library or executed instream. The procedure is used
in the following SMP RECEIVE, APPLY, and ACCEPT steps.
Note: There is a model JCL procedure called BA80SMPE in the sample JCL
library.

Step 8. Receive the Product

Member BA80REC receives all of the components (functional SYSMODs) of
AllFusion CA-InterTest for CICS and executes the procedure edited in Step 7,
Customize the SMP Procedure.
If your site has previously installed AllFusion CA-SymDump for CICS as a
separate product, use member BA80RECS. This member will receive only the
necessary components for the addition of AllFusion CA-InterTest for CICS to
your AllFusion CA-SymDump for CICS software.
Edit the JCL to conform to your installation standards and the previously
completed worksheet.
If you require the uppercase version of AllFusion CA-InterTest for CICS
because you cannot use the mixed case English character set for your
terminals, you no longer have to specify a different FMID during the SMP
RECEIVE, APPLY, and ACCEPT processes. Support for the uppercase version is
now controlled by the IN25OPTS UCONLY=YES parameter.
Submit the job and review the output to verify that the RECIEVE process ran
successfully. If the RECEIVE process completed with an SMP return code
greater than 4, review the output, correct the problem, and resubmit.
If other CA products have been installed, some of these functions may have
been received already. If this is the case, SMP can receive the SYSMODs
again. Therefore, you should be aware that not all SYSMODs received will later
apply and accept. Failing SYSMODs should be removed and the job
resubmitted.
Important! To ensure proper installation and maintenance of this product, all
SYSMODs specified in the SMP control statements for this job must be
selected. During the APPLY and ACCEPT steps, SMP propagates all zones that
are appropriate for the product. Eliminating any SYSMOD from the installation
process may cause failures in customization or future maintenance of the
product.

Chapter 4: Base Product Installation Steps

Step 9. Apply the Product

Member BA80APP applies all of the components (functional SYSMODs) of
AllFusion CA-InterTest for CICS to the target libraries. SMP does not require
the distribution libraries to be allocated during APPLY processing.
If your site has previously installed AllFusion CA-SymDump for CICS as a
separate product, use member BA80APPS. This member will apply only the
necessary components for the addition of AllFusion CA-InterTest for CICS to
your AllFusion CA-SymDump for CICS software.
Edit the JCL to conform to your installation standards and the previously
completed worksheet.
Review and edit the SMP SELECT control statement as described in the sample
JCL.
If other CA products have been installed, some of these functions may have
been applied already. If this is the case, a return code of 12 will occur.
Remove any failing SYSMODs and resubmit the job. Optionally, you can
specify REDO on the APPLY command statement to reapply the SYSMOD.
Submit the job and review the output to verify that the APPLY process ran
successfully.
If the APPLY process completed with an SMP return code greater than 4,
review the output, correct the problem, and resubmit.
Important! To ensure proper installation and maintenance of this product, all
SYSMODs specified in the SMP control statements for this job must be
selected. During the APPLY and ACCEPT steps, SMP propagates all zones that
are appropriate for the product. Eliminating any SYSMOD from the installation
process may cause failures in customization or future maintenance of the
product.

410

Getting Started

Step 10. Accept the Product

Member BA80ACC accepts all the components (functional SYSMODs) of
AllFusion CA-InterTest for CICS to the distribution libraries.
If your site has previously installed AllFusion CA-SymDump for CICS as a
separate product, use member BA80ACCS. This member will accept only the
necessary components for the addition of AllFusion CA-InterTest for CICS to
your AllFusion CA-SymDump for CICS software.
Important! If your site has previously installed AllFusion CA-SymDump for
CICS as a separate product and you are installing AllFusion CA-InterTest for
CICS only on a trial basis, skip this step. If you perform this step, you will not
be able to restore your libraries back to the original AllFusion CA-SymDump
for CICS installation. Once the product has been purchased and licensed, you
must perform this step before any additional maintenance can be applied.
Edit the JCL to conform to your installation standards and the previously
completed worksheet.
Review and edit the SMP SELECT control statement as described in the sample
JCL.
If other CA products have been installed some of these functions may have been
accepted already. If this is the case, a return code of 12 will occur. Remove the
failing SYSMODs and resubmit the job. SMP/E users have the option of specifying
the operand REDO on the ACCEPT command statement and should expect an SMP
return code of 8, which is permissible in this case.
Submit the job and review the output to verify that the ACCEPT process ran
successfully. If the ACCEPT process completed with an SMP return code
greater than 4, view the output, correct the problem, and resubmit the job.
We strongly recommend that you accept the AllFusion CA-InterTest for CICS
product immediately after you have successfully run the APPLY process. This
ACCEPT step provides a backup of the base product on the distribution
libraries. This backup is necessary for future SMP restores.
Note: To ensure proper installation and maintenance of this product, all
SYSMODs specified in the SMP control statements for this job must be
selected. During the APPLY and ACCEPT steps, SMP propagates all zones that
are appropriate for the product. Eliminating any SYSMOD from the installation
process may cause failures in customization or future maintenance of the
product.

Chapter 4: Base Product Installation Steps

411

Step 11. Install the Help Facility

Note: If your site has previously installed AllFusion CA-SymDump for CICS as a
separate product, skip this step.
The member DEFHELP creates and loads the VSAM file that contains the
AllFusion CA-InterTest for CICS online help information. Edit the JCL to
conform to your installation standards and the previously completed
worksheet. This member and other referenced members are found in the
CAI.SAMPLIB library after the APPLY step.

Step 11a. Create the User-Defined Abend Description File

Note: If your site has previously installed AllFusion CA-SymDump for CICS as a
separate product and this step was optionally performed during that
installation, skip this step.
The member DEFUHLP creates the VSAM file that contains the user-defined
abend description information. Edit the JCL to conform to your installation
standards and the previously completed worksheet. This member and other
referenced members are found in the CAI.SAMPLIB library after the APPLY
step.

Step 12. Create the Symbolic File

Note: If your site has previously installed AllFusion CA-SymDump for CICS as a
separate product, skip this step. However, if you want to expand your
symbolic file at this time, you can optionally perform this step.
The member DEFSYM creates the PROTSYM VSAM file, which contains the
symbolic information and source listings for your application programs. Edit
the JCL to conform to your installation standards and the previously completed
worksheet.
Note the following items when creating the symbolic file:

412

Getting Started

Do not specify a secondary space allocation.

The DEFSYM utility job (running the IN25UTIL program) could run for a
long time depending on the size of the file. This occurs only the first time
after the file is created by the IDCAMS job.

Step 13. Create the Checkpoint File

Each symbolic file has an upper limit of about four million 2 KB records
and holds approximately 147,000 programs. See the AllFusion Testing and
Fault Management Symbolic Guide for instructions on how to delete
members.

The symbolic file must not reside in the LSR pool.

Symbolic File Entries

After the job DEFSYM runs, the symbolic file contains a number of entries.
These entries provide the symbolic information for CICS system data areas
and AllFusion CA-InterTest for CICS data areas, and the symbolic information
for the various programs used to demonstrate the product.
Demonstration programs written in COBOL, COBOL II, COBOL/370, PL/I, and
Assembler are available; COBOL and PL/I programs demonstrating composite
support are also available. There are separate guides for COBOL, PL/I, and
Assembler users; see the appropriate AllFusion CA-InterTest for CICS Primer
for details.

Concurrently Updating the PROTSYM File

The MVS RESERVE and DEQ macros are used by AllFusion CA-InterTest for
CICS to allow sharing of the AllFusion CA-InterTest for CICS PROTSYM file
between regions and 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.

Step 13. Create the Checkpoint File

The member DEFCKPT creates the checkpoint file that is used to periodically
record the status of AllFusion CA-InterTest for CICS for a possible restart. Edit
the JCL to conform to your installation standards and the entries on the
previously completed worksheet.
For information on the checkpoint recording facility, see the chapter
Monitoring Menu Options in the User Guide.

Chapter 4: Base Product Installation Steps

413

Step 14. Add the Required CICS Resource Definitions

The CSDINT member in CAI.SAMPLIB adds the CICS resource definitions for
the AllFusion CA-InterTest for CICS programs, files, and transactions. Modify
the JCL according to the instructions in this member.
Add the corresponding RDO group to your CICS startup list (the SIT parameter
GRPLIST=) as listed in the following table:
CICS Level

RDO Group for CICS Startup List

CTS 2.2

INT80062

CTS 2.3

INT80063

CTS 3.1

INT80064

CTS 3.2

INT80065

The use of the AllFusion CA-InterTest for CICS transactions ISER, VIRC, and
VTAT must not be protected to a specific sign on, and for CA-ACF2 and RACF
users must meet the special considerations given in the chapter System
Requirements.
Do not change any of the options specified for the AllFusion CA-InterTest for
CICS entries. If you believe there is an error in any of the entries, contact CA
Technical Support.

Step 15. Update the CICS startup JCL and Startup

Parameters
Note: If your site has previously installed AllFusion CA-SymDump for CICS as a
separate product, some DD statements may already exist.
If you use DD statements in your CICS startup JCL, your AllFusion CA-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.
Sample DD statements are shown next:

414

Getting Started

//PROTCPF

DD DSN=CAI.PROTCPF,DISP=OLD

//PROTSYM

DD DSN=CAI.PROTSYM,DISP=SHR

//PROTHLF

DD DSN=CAI.PROTHLF,DISP=SHR

//PROTUHF

DD DSN=CAI.PROTUHF,DISP=SHR

Step 16. Install DB2 Support

If you need more than one symbolic file, see the SYMFIL option in the section
Modifying AllFusion CA-InterTest for CICS Options in the chapter Options.
Also, add the AllFusion CA-InterTest for CICS load library to the DFHRPL in the
CICS startup JCL for your release of CICS:
//

DD DSN=CAI.CACICS62.DISP=SHR

CTS 2.2

DD DSN=CAI.CACICS63.DISP=SHR

CTS 2.3

DD DSN=CAI.CACICS64.DISP=SHR

CTS 3.1

DD DSN=CAI.CACICS65.DISP=SHR

CTS 3.2

CICS Startup DSA Limit parameterAllFusion CA-InterTest for CICS makes

calls to IEWBIND when using the new 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 insure 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.

Step 16. Install DB2 Support

Instructions for installing DB2 support are provided next. Note that additional
considerations apply if you have programs that issue calls or require special
handling.

Support DB2 Calls in the FILE and CORE Facilities

The FILE facility supports dynamic SQL calls to DB2. This feature lets users
view, alter, add, or delete data in DB2 tables without leaving CICS. The CORE
facility lets you view the last SQL statement executed (CORE=LASTSQL).
The pre-generated versions of IN25DB2 and IN25AIDB are preassembled with
DB2 Release 3.1. The pre-generated version of IN25AID8 is preassembled with
DB2 Release 8.1.
Perform the following steps to install DB2 support:
1.

The CSDDB2 member on CAI.SAMPLIB provides RDO entries.

Bind the DBRM members provided on the CAI.SAMPLIB into an InterTest

DB2 plan (the recommended name is IN80PLAN), as indicated following:

For DB2 subsystems running in new function mode (version 8.1.0 or

higher), bind IN80FIDB and IN80AID8.
For all other DB2 subsystems, bind IN80FIDB and IN80AIDB.

Chapter 4: Base Product Installation Steps

415

Step 17. Restart CICS and Run Check-out Program

The DBA must grant bind and execute authority to the plan created in task
2.

For DB2 subsystems running in new function mode (version 8.1.0 or

higher), ensure that the library containing the customized DSNHDECP
(either SDSNEXIT or SDSNLOAD) is in the DFHRPL DD concatenation after
the CICS program libraries.

Monitor DB2 Applications

A pre-generated version of IN25UEXI, assembled for DB2 Releases 3.1 and
above, is provided in your AllFusion CA-InterTest for CICS load library.
If you do not have any other special software situations that will be handled by
the IN25UEXI program, you need not perform any additional installation steps
for DB2 support. However, if you have programs that issue calls or require
special handling, see the section Calls to Software and User Macro Support in
the chapter Handling Special Situations.
For additional information on using AllFusion CA-InterTest for CICS with DB2,
see the section Using AllFusion CA-InterTest for CICS with DB2 Application
Programs in the chapter Handling Special Situations.

Step 17. Restart CICS and Run Check-out Program

After AllFusion CA-InterTest for CICS has been installed, restart CICS and run
the AllFusion CA-InterTest for CICS check-out program IN25VRPT. This program
checks for common mistakes that may have been made during the installation
of AllFusion CA-InterTest for CICS.
Important! You are strongly advised to perform this step so errors can be
detected quickly.
To check out the installation of AllFusion CA-InterTest for CICS, perform the
following steps:

416

Getting Started

Enter the transaction code VRPT. AllFusion CA-InterTest for CICS displays
the selection menu.

Enter 1 in the Option field and press Enter. AllFusion CA-InterTest for CICS
displays the first screen of programs.

Continue to press Enter to display the next screen.

The AllFusion CA-InterTest for CICS check-out procedure is completed when

the selection menu is displayed with the option field set to 4 or beyond.

Step 18. Install Dynamic Symbolic Support for AllFusion Endevor Change Manager

Important! If you are upgrading from a previous release, urge your users to
use ITST Option 8 to review Whats New in this release.

Step 18. Install Dynamic Symbolic Support for AllFusion

Endevor Change Manager
If the AllFusion Endevor Change Manager source management product is
installed, and the AllFusion Endevor footprint option is turned on, AllFusion
CA-InterTest for CICS can dynamically retrieve symbolic information.
Note: Dynamic symbolic support requires AllFusion Endevor Change Manager
r7 SP 2 or later.
To install AllFusion CA-InterTest for CICS with dynamic symbolic support, you
need to perform the following steps:
1.

Install CAICCI as discussed in the section CA Common Services for z/OS

and Requirements.

Follow normal installation instructions for the product, as discussed in the

chapter Base Product Installation Steps.

Copy the INDVSPWN CAIPROC member to the CA-ENF parameter library

and add the spawn parameter to the CA-ENF spawn parameter list.

CAIPROC member INTNDVR is the procedure that is started to extract a

listing file from AllFusion Endevor. This procedure should be edited and
copied to a system procedure library with the AllFusion Endevor site ID
appended to the name. For example, if the site ID is 3, the name of this
procedure should be INTNDVR3. The seven-character prefix for this
procedure name is specified and can be changed by editing the NDVRPROC
parameter in the IN25OPTS macro. If multiple AllFusion Endevor
C1DEFLTS tables are used, a procedure for each C1DEFLTS must be added
to the system procedure library. Each procedure name should be the
seven-character prefix specified in IN25OPTS plus the one-character
C1DEFLTS site ID.

Include an NDVRSYM ddname in the IN25OPTS SYMFIL= parameter to

indicate the PROTSYM file to be used for dynamic symbolic loading. The
presence of an NDVRSYM PROTSYM ddname in the CICS startup JCL
indicates to AllFusion CA-InterTest for CICS to invoke the dynamic
symbolic load option.
SYMFIL=(PROTSYM,xxxxxxx,xxxxxxx,NDVRSYM)
For details on setting these options, see the chapter Options.
NDVRSYM used as a ddname for one of the PROTSYM files indicates to
AllFusion CA-InterTest for CICS that AllFusion Endevor support is active.

Chapter 4: Base Product Installation Steps

417

Step 19. Check for Latest Maintenance

The NDVRPROC procedure requires read security access to any load library
data sets that application programs requiring symbolic support may reside
in. It also requires write security access to any PROTSYM file specified on
an NDVRSYM DD statement.

Important! CA-ENF will need to be refreshed to activate the new spawn

parameters added for this feature.

Step 19. Check for Latest Maintenance

For instructions to acquire and apply the latest maintenance for AllFusion
CA-InterTest for CICS, see Chapter 10: Maintenance.

Activate AllFusion CA-InterTest for CICS

After you have completed the installation steps, you can activate AllFusion
CA-InterTest for CICS in your CICS system at any time. To activate AllFusion
CA-InterTest for CICS, issue the following command:
CNTL=START

For AllFusion CA-InterTest for CICS regions installed with CICSPlex support
(CICSPLEX=YES in IN25OPTS), the CNTL=START and CNTL=RESTART
commands automatically have AllFusion CA-InterTest for CICS resynchronize
monitoring with any active regions in the CICSPlex. The chapter Automatically
Starting AllFusion CA-InterTest for CICS explains how to start AllFusion
CA-InterTest for CICS automatically with your CICS system.
At this time, you can compile and assemble your programs with the AllFusion
CA-InterTest for CICS symbolic post-processor programs as described in the
AllFusion Testing and Fault Management Symbolic Guide. These programs let
you use symbolic references during testing.
Remember, however, that you do not have to compile your programs with one
of the AllFusion CA-InterTest for CICS symbolic post-processor programs. All
of the AllFusion CA-InterTest for CICS monitoring facilities are available for
current programs without recompiling or reassembling them. We do
recommend that you recompile or reassemble current programs if AllFusion
CA-InterTest for CICS detects errors because symbolic support greatly
facilitates debugging.

418

Getting Started

Deactivate AllFusion CA-InterTest for CICS

To activate AllFusion CA-InterTest for CICS at CICS startup, perform the

following procedures:
1.

Manually activate AllFusion CA-InterTest for CICS by issuing the

CNTL=START command.

Automatically activate AllFusion CA-InterTest for CICS using the PROMMAC

macro or the IN25PLT PLTPI program. For details, see the chapter
Automatically Starting AllFusion CA-InterTest for CICS.

Deactivate AllFusion CA-InterTest for CICS

AllFusion CA-InterTest for CICS can be deactivated at any time by issuing the
following command:
CNTL=END

For regions using the CICSPlex support option, you can issue the following
command to concurrently deactivate AllFusion CA-InterTest for CICS in all
connected CICSPlex regions:
CNTL=END,SCOPE=GLOBAL

AllFusion CA-InterTest for CICS maintains a permanent service task that runs
under the transaction ID ISER. The program is IN25SERV. CICS cannot
complete a normal shutdown until this task ends. It is important that you
deactivate AllFusion CA-InterTest for CICS before CICS shutdown to terminate
this task.
To deactivate AllFusion CA-InterTest for CICS at CICS shutdown, perform one
of the following procedures:

Manually deactivate AllFusion CA-InterTest for CICS by issuing the

CNTL=END command.

Automatically deactivate AllFusion CA-InterTest for CICS using the

IN25PLTE program. If you add this AllFusion CA-InterTest for
CICS-supplied shutdown PLT program to your shutdown program list,
AllFusion CA-InterTest for CICS will be deactivated automatically at normal
CICS termination.

Add the following AllFusion CA-InterTest for CICS PLTSD entry before
DFHDELIM so that it is part of Stage 1 processing:
DFHPLT TYPE=ENTRY,PROGRAM=IN25PLTE

Chapter 4: Base Product Installation Steps

419

PL/I Option Installation Steps

If you are licensed to use the AllFusion CA-InterTest for CICS option for PL/I,
you must install the key. The batch symbolic processors for PL/I support are
now included automatically during all installations.
For instructions, see section Step 2. Enter LMP Product Key Certificate
Information.
Note: If your site has previously installed AllFusion CA-SymDump for CICS with
PL/I support as a separate product, skip these steps.

420

Getting Started

Chapter 5: Options
This chapter describes the various option settings, their defaults, and how to
change them. This chapter also explains how to further customize AllFusion
CA-InterTest for CICS to meet your sites needs.

Modify AllFusion CA-InterTest for CICS Options

The following topics are discussed:

Implementing composite support

Declaring user-defined CORE commands

Adding Assembler DSECTs to the symbolic file

Unprotecting main storage with the user exit IN25LETX

Adding COBOL file structures to the symbolic file

Specifying abend codes that should not be interceptedIN25ABEN

Customizing help for abend codes

Procedure for Modifying Options

AllFusion CA-InterTest for CICS installation options are contained in the
IN25OPTS load module. You can change option settings easily by changing the
load module without recompiling AllFusion CA-InterTest for CICS programs.
To change an AllFusion CA-InterTest for CICS option, follow these steps:
1.

Create an IN25OPTS load module that contains the modified options with a
batch assemble-and-linkedit job (sample JCL follows).

Activate the changes by performing the following steps:

Turn off AllFusion CA-InterTest for CICS.

Issue this command:

CEMT

SET

PROG(IN25*)

NEWCOPY

Ignore any failures of IN25HOOK to newcopy.

Restart AllFusion CA-InterTest for CICS.

Chapter 5: Options

Procedure for Modifying Options

Option DefaultsThe option defaults used in the pre-generated version of

AllFusion CA-InterTest for CICS r8 follow and are presented in option=default
format:

Getting Started

AUDIT=NO

NDVRPROC=INTNDVR

AUTMON=YES

OSGETM=YES

BKPTERM=

PROMD=00000020

BREAK=YES

READBUF=YES

CICSPLEX=NO

REALIA2=NO

CKPTFIL=PROTCPF

RECNTMU=NO

CNTLSEC=YES

RECNTNW=YES

CNTLT=CNTL*

SDISPLAY=DATA

CNTOSEC=YES

SLB=YES

CNTSQLG=YES

SLBAKEEP=YES

CORET=CORE*

SLBMARG=1

CORSEC=YES

SLBSCRL=PAGE

CPF11=7B

SLBTIT=YES

CPLXCKPI=0020

STBTRN=STB4*

CPLXFMID=INTERTST

STMTTRCE=500

CWALET=no value

STUAR=NO

DFLTUSER=.ANY

SYMDFIL=PROTDMP

DL1SIZE=8192

SYMDINT=YES

EXTSEC=NO

SYMDL=SYMD

FDISP=FC

SYMDT=SYMD*

FFORM=D

SYMDWILD=

FILET=FILE

SYMFIL=PROTSYM

FILSEC=YES

SYMPSWD=12345678

FSYMP=PROTFILE

TRCFDCLS=

GLOG=CSSL

TRCFFMID=SYMDTRCF

HELPFIL=PROTHLF

TRCFMCLAS=

HELPT=HELP*

TRCFMEGM=120

ICMDBUF=1024

TRCFMEGT=15

ICMDEXE=50

TRCFSCLS=

ICMDMAX=50

TRCFTOUT=240

IGLUT=IGLU*

TRCFTRHD=50

IPLXT=IPLX*

TRCFUNIT=

IRCTT=VIRC*

TRCFVOL=

ISERT=ISER*

UCONLY=NO

ITSTT=ITST*

USERHELP=PROTUHF

Procedure for Modifying Options

LETSVC=YES

VERCOR=NO

LISTT=LIST*

VRPTT=VRPT*

MONOM=NO

VTATT=VTAT*

MONOMSEC=YES

XRMIO=YES

NDVRASML=NO
*If you change a transaction ID, also change the CICS transaction definition.

Sample JCL to Assemble the Options Program

The following example shows the JCL needed to assemble the AllFusion
CA-InterTest for CICS Options Program (IN25OPTS).
//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

DSN=CAI.SAMPLIB,DISP=SHR

DSN=CICS.MACLIB,DISP=SHR

//SYSUT1

UNIT=SYSDA,SPACE=(CYL,(1,1))

//SYSUT2

UNIT=SYSDA,SPACE=(CYL,(1,1))

//SYSUT3

UNIT=SYSDA,SPACE=(CYL,(1,1))

//SYSIN

*** CWA USER DSECT REQUIRED HERE IF USING THE CWALET OPTION ***
USING CWADS,0

ALLFUSION CA-INTERTEST REQUIREMENT

CWADS

DSECT

USER CWA

CWAFLD1

CL20

CWAFLD2

CL15

CWAFLD3

CL100

ALLFUSION CA-INTERTEST OPTION SPECIFICATIONS**************

IN25OPTS TYPE=CSECT,
FILSEC=YES,

X
X

LETSVC=NO
IN25OPTS TYPE=CSECT,

CWALET=(CWAFLD1,CWAFLD2+15)
IN25OPTS TYPE=FINAL
END
/*

Chapter 5: Options

Procedure for Modifying Options

//LKED

EXEC PGM=IEWL,PARM=(XREF,LIST,MAP),

REGION=1M,COND=(4,LT,ASM)

//SYSPRINT DD

SYSOUT=*

//SYSLIN

DSN=&&OBJECT,DISP=(OLD,DELETE)

//SYSLMOD

DSN=CAI.CACICSxx(IN25OPTS),DISP=SHR

//SYSUT1

UNIT=SYSDA,SPACE=(CYL,(1,1))

In this example, the options FILSEC, LETSVC, and CWALET have been generated.
All other options use the default settings. In the SYSLMOD DD statement, replace
xx with your two-digit CICS release number (for example, 62 for CTS 2.2, 63 for
CTS 6.3, 64 for CTS 3.1, or 65 for CTS 3.2).
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.

IN25OPTS Keywords
This section lists the IN25OPTS keywords. Defaults are underlined. Slashes (/)
between parameters indicate you must make a choice.
AUDIT= NO/YESFor auditing purposes, certain installations require that all
CORE, FILE, and CNTL commands be recorded.
NO

Specify NO if you did not specify the GLOG= option or if you want to
dynamically activate and deactivate global logging with CNTL=GLOG,ON
and CNTL=GLOG,OFF commands.
If you specify NO, the user can request logging of FILE commands by
specifying FUNC=LOG on the FILE menu.

YES Specify YES if you specified the GLOG= option and you need the global
logging facility always active.
With AUDIT=YES, neither the CNTL=GLOG,ON command nor the
CNTL=GLOG,OFF command are accepted. The CNTL commands and
AllFusion CA-InterTest for CICS responses are always recorded in the
transient data queue or data set that was specified with the GLOG=
keyword. CORE changes to storage areas not owned by the task (usually
password protected) are always recorded. The FILE transaction operates
in the LOG=ON mode; that is, all user requests and resulting FILE screen
images are recorded.
Note: If you do not specify the GLOG= keyword, the AUDIT=YES
specification is ignored.

Getting Started

Procedure for Modifying Options

AUTMON=YES/NOIndicates whether a new Monitor Table entry is created.

YES Creates a new Monitor Table entry for a program when an automatic
breakpoint is about to occur if the program is being monitored under a
Monitor Table entry that does not name this program by its full name (for
example, if the entry names a transaction). The new entry assumes all
monitoring options currently in effect. This option makes it easier to
debug the program.
NO

Does not create a separate Monitor Table entry.

BKPTERM=(_) /MOD2
no value The breakpoint display will not force a MOD2 terminal.
MOD2 The breakpoint display will always be treated as a MOD2 terminal.
BREAK=YES/NOIndicates whether AllFusion CA-InterTest for CICS is
allowed to execute breakpoints.
YES Allows AllFusion CA-InterTest for CICS to execute breakpoints; that is, to
stop execution of the application program at certain points. Select this
option if you intend to use AllFusion CA-InterTest for CICS as an
interactive debugging tool.
NO

Does not allow AllFusion CA-InterTest for CICS to execute breakpoints.

This option might be desirable in a separate version of AllFusion
CA-InterTest for CICS used solely for monitoring production applications.
AllFusion CA-InterTest for CICS generated with BREAK=NO monitors with
less overhead, which is important in production.
Instead of causing automatic breakpoints, AllFusion CA-InterTest for
CICS abnormally terminates transactions with a transaction dump when
it detects a standards violation. The abend/dump code is INTE. The dump
contains all of the usual diagnostic information.

CICSPLEX=YES/NOAllFusion CA-InterTest for CICS provides special

support for CICS regions participating in a CICSPlex environment.
Participating CICSPlex regions have AllFusion CA-InterTest for CICS
commands propagated across all regions in the CICSPlex.
YES Indicates that this CICS region is participating in at least one CICSPlex
family of regions, as named in the CPLXFMID keyword. Invokes AllFusion
CA-InterTest for CICS CICSPlex processing by using CAICCI.
If CICSPLEX=YES, CAICCI processing must be installed on the z/OS
operating system and available to CICS.
NO

Indicates that this CICS region is not participating in a CICSPlex family.

CKPTFIL=PROTCPF/ filenameSpecify the file name for the AllFusion

CA-InterTest for CICS checkpoint file. The name must not exceed seven
characters. If you do not use the default, be sure to adjust the CICS file
definition.

Chapter 5: Options

Procedure for Modifying Options

CNTLSEC=YES/NOIndicates whether certain CNTL commands can be

protected with a password.
YES Protects certain CNTL commands with a password and allows for
password protection of certain CNTL options. Specify CNTLSEC=YES if
the CNTL command functions should be available only to authorized
personnel. With CNTLSEC=YES, the keyword CNTOSEC further specifies
whether the subset of CNTL options should also be password protected.
The passwords are defined in the IN25SEC2 macros. See the Password
Protection chapter for the list of CNTL commands and options subject to
password protection and details on specifying passwords using
IN25SEC2.
With CNTLSEC=YES, you must use the IN25SEC2 macro to generate the
AllFusion CA-InterTest for CICS program IN25SEC2 or use the IN25SEC2
delivered with AllFusion CA-InterTest for CICS.
NO

Does not protect certain CNTL commands with passwords and does not
allow for password protection of certain CNTL options.

CNTLT= CNTL/transaction-idSpecify a four-character transaction ID for

the AllFusion CA-InterTest for CICS CNTL 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 begins with the
character C is not strict. IDs such as CNTL and CORE can be used if the
CICS system does not use them.
CNTOSEC=YES/NOWhen the value for the keyword CNTLSEC is YES,
specify this keyword to include or exclude certain CNTL options from
password protection. When CNTLSEC=NO, this keyword is ignored.
YES Protects certain CNTL options with a password. The password is defined
in an IN25SEC2 macro, as discussed in the chapter Password
Protection.
NO

Does not protect any CNTL options with passwords.

CNTSQLG=YES/NOIndicates whether CNTL commands are logged.

YES Logs CNTL commands executed from a sequential terminal and
responses to them into the transient data destination defined in the
GLOG option.
NO

Does not log CNTL commands.

CORET=CORE/transaction-idSpecify a four-character transaction ID for

the AllFusion CA-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.

Getting Started

Procedure for Modifying Options

CORSEC=YES/NOIndicates whether a password is required to modify a

main storage area protected by AllFusion CA-InterTest for CICS.
YES Requires a password when a user of the CORE facility is about to modify
a main storage area that is protected by AllFusion CA-InterTest for CICS,
but does not require the password during normal debugging. Specify
CORSEC=YES if you will use the AllFusion CA-InterTest IN25SEC2 macro
to generate a password that would prevent the CORE facility from being
used by unauthorized personnel.
The IN25SEC2 macro must be used to generate the AllFusion
CA-InterTest for CICS program IN25SEC2 or use the IN25SEC2 delivered
with AllFusion CA-InterTest for CICS. The use of the IN25SEC2 macro is
described in the Password Protection chapter.
Without the password, the CORE transaction lets you modify only those
storage areas that belong to a task that is waiting in a breakpoint and
are not protected by AllFusion CA-InterTest for CICS from being modified
by the monitored program.
NO

Does not require a password before allowing modification of any field

within the CICS region in main storage.
See the description of the CORE transaction in the User Guide. The
CORSEC specification also applies to data modification in the LIST Keep
window.
Note: Regardless of the CORSEC= specification, the following main
storage areas are not available for modification by the CORE transaction:

CICS/VS Sign-on Table (DFHSNT)

Main storage outside of the CICS region

CPF11=7B/BFActivates the PF11 key on the Detailed Breakpoint screen.

Allows application programmers to use the PF11 key on the Detailed

Breakpoint screen to tell AllFusion CA-InterTest for CICS to force the
execution of any error condition that AllFusion CA-InterTest for CICS has
detected even though the error condition that caused the automatic
breakpoint still exists. In effect, the user tells AllFusion CA-InterTest for
CICS that this is really not a violation and to execute regardless of the
consequences.
Before enabling this facility, be aware of the following considerations:

As a result of this execution, not only the tested transaction's data

could be damaged but other concurrent transactions could also be
affected and the entire CICS system may crash.
Using PF11 ignores not only the immediate error condition, but also all
subsequent error conditions until the next breakpoint or CICS Service
Request (whichever comes first).

Chapter 5: Options

Procedure for Modifying Options

Specify CPF11=BF if you do not want to provide this facility.

CPLXCKPI=0020/hhmmIf CICSPLEX=YES and the checkpoint facility is

started by a CICSPLEX resynchronization request, defines the time
interval in hours (HH) and minutes (MM) between checkpoints.
CPLXFMID=INTERTST/CICSPlex-familynameDefines a CICSPlex family
name to be associated with the CICS region.
YES Defines an eight-character CICSPlex family name associated with the
CICS region. The same family name must be given to all CICS regions
participating in that family to obtain CICSPlex support throughout the
family.
AllFusion CA-InterTest for CICS supports multiple CICSPlex families
within or across multiple z/OS regions. For example, all regions
associated with CPLXFMID=REGIONA participate in one CICSPlex family,
while all regions associated with CPLXFMID=REGIONB participate in
another.
NO

Disregards this keyword; the default.

CWALET=( )/(label,label)Specify the CWALET keyword only if you want

to remove AllFusion CA-InterTest for CICS storage protection from
certain CWA fields.
Important! If you choose to specify one or more CWALET areas, you
must code a separate IN25OPTS TYPE=CSECT macro for each CWALET
area (one area per macro).
IN25OPTS macros with CWALET must follow other IN25OPTS macros
except for the TYPE=FINAL macro, which must be the last one.
no value AllFusion CA-InterTest for CICS protection will not be removed. Use
the CSA= and LET= online options to let specific monitored programs
modify additional areas of main storage. See the User Guide for details
about online options.
(label,label) Specify two Assembler labels, separated by a comma and
enclosed in parentheses; for example, CWALET=(CSAUTA1,CSAUTA4).
The first label defines the first byte of the area to be unprotected; the
second label defines the first byte past the area.
When using labels, they must be defined in the DSECT for the CWA and
inserted in the IN25OPTS compile; see the section Sample JCL to
Assemble the Options Program for details.
If your CWA has an existing DSECT, use existing labels and offsets from
the labels to define the unprotected area.

Getting Started

Procedure for Modifying Options

If you do not have an existing DSECT in your CWA, add the following two
statements to the IN25OPTS module to create one:
*********** CWA USER DSECT REQUIRED HERE ************
USING CWADS,0
CWADS

DSECT

ALLFUSION CA-INTERTEST REQUIREMENT

USER CWA

** ALLFUSION CA-INTERTEST SPECIFICATIONS

You can then specify offsets from the beginning of the CWA. For example,
the following macro unprotects a 20-byte area starting at the beginning of
the CWA:
IN25OPTS TYPE=CSECT,CWALET=(CWADS,CWADS+20)
DFLTUSER=.ANY/SPECIFIC/BACKGROUNDDFLTUSER stands for default
user and controls how AllFusion CA-InterTest for CICS monitoring
functions by default. A user can override the default settings established
by this parameter at any time.
.ANYWhen this setting is used, AllFusion CA-InterTest for CICS monitoring
pays no attention to the CICS user ID of the session, even if the user is
signed on to CICS. Monitoring is set for all users, and breakpoints, by
default, are directed to the same terminal used to set them.
SPECIFICThis setting is only valid in a secure AllFusion CA-InterTest for
CICS region where the users log on to CICS. When DFLTUSER=SPECIFIC
is used, AllFusion CA-InterTest for CICS qualifies each monitoring entry
with the users CICS user ID. In addition, AllFusion CA-InterTest for CICS
directs all options to monitoring to .ANY terminal. This setting allows
many users to test the same program or transaction independently. This
also allows users to move from terminal to terminal and have their
monitoring entries and monitoring options follow them.
T

BACKGROUNDThis setting is only valid in a secure AllFusion CA-InterTest

for CICS region where the users log on to CICS. Code this if your CICS
system is used predominantly as an Application Server, where most
transactions are not attached to terminals (that is, web interface
transactions). This setting sets the FROM terminal to .ANY, and the
breakpoint (TO) terminal to the current terminal that is setting the
breakpoints.
DL1SIZE=8192/nnnnnSpecifies the number of bytes in the largest DL/I
segment to be retrieved using the AllFusion CA-InterTest for CICS FILE
facility. Storage corruption may occur if the size specified here is smaller
than a DL/I segment that is retrieved using FILE.
Important! When DFLTUSER=SPECIFIC is used and a user does not sign
on to the CICS region, AllFusion CA-InterTest for CICS uses the value of
the CICS DFLTUSER for the monitoring entry. The CICS default user ID is
optionally specified in the SIT parameters. If not specified in the SIT, its
value is CICSUSER.

Chapter 5: Options

Procedure for Modifying Options

EXTSEC=YES/NOIndicates=YES/NOIndicates External Security Manager

is to be used.
YES AllFusion CA-InterTest for CICS and AllFusion CA-SymDump for CICS call
the External Security Manager to verify access to secured functions.
Note: For details regarding AllFusion CA-SymDump for CICS calls to
external security, see the AllFusion CA-SymDump for CICS Getting
Started.
NO

AllFusion CA-InterTest for CICS and AllFusion CA-SymDump for CICS

bypass the calls to the External Security Manager. When first installing
AllFusion CA-InterTest for CICS and AllFusion CA-SymDump for CICS,
this setting is useful until the product is tested and the security rules are
written.

FDISP=FC/DL/TD/TS/DBDetermines the default menu for the FILE

transaction. The various menu types are described in the User Guide.
The user can change the menu of the FILE facility online at any time.
FC

The FILE transaction shows its first display in the DATATYPE=FC format;
that is, ready to process CICS files defined in the CICS file definition (File
Control Table).

The FILE transaction shows its first display in the DATATYPE=DL format;
that is, ready to process DL/I segments.

The FILE transaction shows its first display in the DATATYPE=TD format;
that is, ready to process CICS transient data queues.

The FILE transaction shows its first display in the DATATYPE=TS format;
that is, ready to process CICS temporary storage.

The FILE transaction shows its first display in the DATATYPE=DB format;
that is, ready to process DB2 data.

FFORM=D/C/V/SDetermines the default format in which the FILE

transaction displays the data. The user can change the format of the FILE
display online at any time. For illustrations of FILE displays, see the User
Guide.

510

Getting Started

The FILE transaction shows its first display in dump format, similar to the
nonstructured display of the CORE transaction. Shows both character and
hexadecimal images.

The FILE transaction shows its first display in character format. This
format displays the largest amount of data, but is useless for
noncharacter data records.

Procedure for Modifying Options

The FILE transaction shows its first display in vertical format, similar to
the DITTO utility. This format displays the least amount of data.

The FILE transaction shows its first display in structured format if

symbolic information for the program containing the structures is stored
in the AllFusion CA-InterTest for CICS symbolic file. COBOL and PL/I
structures use 01 level names; Assembler structures use DSECT names.
Shows both character and hexadecimal images. See the FSYMP option.

FILET=FILE/transaction-idSpecify a four-character transaction ID for the

AllFusion CA-InterTest for CICS FILE transaction. Be sure to adjust the
CICS transaction definition if you do not use the default.
FILESEC=YES/NOIndicates whether the AllFusion CA-InterTest IN25SEC2
macro generates passwords for security purposes.
YES The AllFusion CA-InterTest IN25SEC2 macro generates passwords to
prevent the FILE transaction from being used by unauthorized personnel.
More comprehensive security enforcement has to be implemented on the
CICS level or on the operating system level.
With FILSEC=YES the IN25SEC2 macro must be used to generate the
AllFusion CA-InterTest for CICS IN25SEC2 program, or use the IN25SEC2
delivered with AllFusion CA-InterTest for CICS. Failure to do so will make
the FILE transaction useless. Using the IN25SEC2 macro is described in
the Password Protection chapter.
NO

Permits users of the FILE transaction to access any CICS file or DL/I data
without an AllFusion CA-InterTest for CICS-enforced password.

FSYMP=PROTFILE/symbolic-programnameSpecify the name of the

default dummy COBOL or PL/I program that contains all of the 01 level
structures used at the site or the Assembler program that contains all the
DSECTs. Symbolic information for this program must be stored in the
AllFusion CA-InterTest for CICS symbolic file.
Users of the FILE transaction requesting records or DL/I segments in
structured format must specify the symbolic name of the program that
contains the structure. However, if a default program containing all of
the structures has been compiled or assembled, users can omit the
symbolic program name.
See the section Adding COBOL File Structures to the Symbolic File in the
chapter Options for a sample default COBOL program. The Adding
Assembler DESCTs to the symbolic file section in that chapter describes
how to add Assembler file structures.

Chapter 5: Options

511

Procedure for Modifying Options

GLOG=CSSL/DCT-destination-idSpecify a four-character name of a

transient data destination in the CICS Destination Control Table (DCT).
The default, GLOG=CSSL, provides the statistics destination that is
always present in the CICS system and is usually printed when the CICS
system is terminated.
The destination must specify a direct or indirect extra partition transient
data set that has a record size of at least 84 bytes (variable-length
format, including the length field).
AllFusion CA-InterTest for CICS writes records to the specified transient
data queue (destination) after the command CNTL=GLOG,ON is entered.
See the description of the AUDIT keyword; also see the description of the
AllFusion CA-InterTest for CICS global logging facility in the User Guide.
HELPFIL=PROTHLF/filenameSpecify the file name for the AllFusion
CA-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
If CICSPLEX=NO, the default, this task does not run.
IRCTT=VIRC/transaction-idSpecify a four-character transaction ID for
the AllFusion CA-InterTest for CICS VIRC transaction. This is an internal
AllFusion CA-InterTest for CICS transaction used only for handling
breakpoints. Its use must not be protected by a specific signon. If started
by mistake from a terminal, the transaction program does nothing.
In an MRO or ISC environment, the VIRC transaction must be installed as
local in all Terminal Owning Regions and Application Owning Regions that
use AllFusion CA-InterTest for CICS.
In a CICS environment that does not use MRO or ISC, the VIRC
transaction must be installed to support automatic single-stepping.
Note: If you change the transaction ID, also change the CICS
transaction definition.
ISERT=ISER/transaction-idSpecify a four-character transaction ID for the
internal AllFusion CA-InterTest for CICS ISER transaction. Do not assign
protection to a specific user.
Note: If you change the transaction ID, also change the CICS
transaction definition.
ITSTT=ITST/transaction-idSpecify a four-character transaction ID for the
AllFusion CA-InterTest for CICS ITST transaction. This transaction
displays the AllFusion CA-InterTest for CICS Primary Option menu from a
CICS prompt. Do not assign protection to a specific user.
Note: If you change the transaction ID, also change the CICS
transaction definition.

512

Getting Started

Procedure for Modifying Options

LETSVC=YES/NOIndicates whether SVCs are permitted.

YES Permits any SVCs in application programs except:
SVC 13 (hex 0D)ABEND macro
NO

Indicates that application programs do not use any SVCs except:

SVC 11 (hex 0B)TIME macro
These are the SVCs often used implicitly in applications, but any other
SVCs should not be used in CICS programming.
Regardless of this keyword, you can use BYP= options during an
AllFusion CA-InterTest for CICS test session to permit the monitored
program to use SVCs.

LISTT=LIST/transaction-idSpecify a four-character transaction ID for the

AllFusion CA-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.
MONOM=NO/MENU/NOMENUControls the activation of the segmented
monitoring feature.
NO

Deactivates the segmented monitoring feature and removes any previous

MON and NOM entries from the CNTL main menu.

MENU Activates the feature and displays the MON and NOM options on the
CNTL main menu.
NOMENU Activates the segmented monitoring feature, but limits users to
implementing segmented monitoring through CNTL commands or the
LIST facility. NOMENU disables the use of the MON and NOM options on
the Monitoring menus, and removes the MON and NOM entries from the
CNTL main menu.
MONOMSEC=YES/NOControls password protection for the segmented
monitoring options in the CNTL facility. If MONOM=NO, MONOMSEC is
ignored.
YES Implements password protection of the segmented monitoring feature.
The password is controlled by a keyword in the IN25SEC2 macro.
Instructions for specifying passwords for CNTL options are in the
Password Protection chapter.
NO

Permits the use of the segmented monitoring feature without password

protection.

Chapter 5: Options

513

Procedure for Modifying Options

NDVRASML=NO/YESNon 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 AllFusion 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=INTNDVR/procedure nameSpecify the name of the
dynamic symbolic support for AllFusion Endevor procedure defined in
step 18 of 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.
OSGETM=YES/NOIndicates whether a GETMAIN SVC is allowed to be
issued.
YES Permits COBOL programs monitored by AllFusion CA-InterTest to issue
the GETMAIN SVC. As suggested by the CICS Application Programmer's
Reference Manual, any CICS COBOL program should be coded so that no
COBOL facilities require a GETMAIN SVC. Such a GETMAIN SVC obtains
storage from the OSCORE storage pool outside the storage controlled by
the CICS Storage Management. There is no FREEMAIN if the COBOL
program terminates. When, eventually, a GETMAIN cannot be satisfied,
the CICS system will be abended by the operating system.
OSGETM=YES is implied by the LETSVC=YES specification.
NO

Does not permit the GETMAIN SVC to be issued by COBOL programs.

Unless you run software that issues the GETMAIN SVC, we recommend
that you specify OSGETM=NO as GETMAINs should not be permitted.
With this specification, an automatic breakpoint will occur when the
GETMAIN SVC is detected. However, OSGETM=NO is overridden by
LETSVC=YES.

PROMD=00000020/name/numberThe name or the number in this

keyword is used for the default value of the PROM= parameter of the
CNTL=START command.
name Specify the AllFusion CA-InterTest IN25SEC2 macro generates
passwords the name (up to eight characters) of the AllFusion
CA-InterTest for CICS Startup Table that has to be generated with the
PROMMAC macro. The use of the macro is described in the chapter
Automatically Starting AllFusion CA-InterTest for CICS.

514

Getting Started

Procedure for Modifying Options

number Specify the number to be used as the default value of the PROM=
parameter of the CNTL=START command, which specifies the initial
number of entries in the Monitoring Table. This number must be eight
characters long. For the initial period of use, the default value should
suffice.
The number of entries in the table should be no less than the number of
names to be declared for monitoring. However, for efficiency, allow
enough entries at the beginning by specifying the PROM= parameter
here or in the CNTL=START command. A large number of unoccupied
entries use more storage but do not increase the overhead because only
occupied table entries are examined when the table is scanned.
READBUF=YES/NOIndicates whether the read buffer function is supported.
YES Before sending a breakpoint to a terminal, AllFusion CA-InterTest for
CICS issues a read buffer to save the last user screen from that terminal.
If your AllFusion CA-InterTest for CICS demonstration session runs
successfully, specify YES.
NO

You must specify NO if all terminals that would be used by AllFusion

CA-InterTest for CICS users run under TCAM or do not support the read
buffer function. If you do not specify NO, you must declare the NRB=ON
online option whenever monitoring is declared.

REALIA2=YES/NO/ONLYIndicates whether AllFusion CA-Realia II

Workbench Option for CICS is active in the CICS region.
YES Indicates that both AllFusion CA-Realia II Workbench Option for CICS
and AllFusion CA-InterTest for CICS are active in the CICS region.
NO

Indicates that AllFusion CA-Realia II Workbench Option for CICS is not

active in the CICS region.

ONLY Indicates that only AllFusion CA-Realia II Workbench Option for CICS is
active in the CICS region.
RECNTMU=YES/NOIndicates whether CNTL commands are displayed
before execution.
YES Displays the CNTL commands generated by the AllFusion CA-InterTest
for CICS menus just before the commands are executed. The user can
learn these commands from the screen and, for efficiency, use them
instead of menus.
NO

Suppresses display of CNTL commands.

RECNTNW=YES/NOIndicates whether CNTL commands are displayed

before execution.
YES Displays the CNTL commands that are automatically generated by
CNTL=RESTART or CNTL=NEW,PROG= commands. These appear just
before they are executed so that the user can see what is being done.
NO

Suppresses display of CNTL commands. Specify NO if users are not

interested in these details.

Chapter 5: Options

515

Procedure for Modifying Options

SDISPLAY=HEX/DATAFacility of the Structure display and AutoKeep

display feature. Specifies the global default value for Structure Display
Format. Regardless of this setting, the value can be adjusted online by
program name.
HEX Display data in hexadecimal character format
DATA Display data in Structure Display Format
SLB=YES/NOIndicates whether Source Listing Breakpoint displays are
available.
YES Uses Source Listing Breakpoint displays for the terminal from which the
program was declared for monitoring if the compile (assembly) listing is
available in the AllFusion CA-InterTest for CICS symbolic file.
NO

Uses Detailed Breakpoint displays when a program is declared for

monitoring.
In either case, Source Listing Breakpoint displays can be turned on or off
during the online test session.
Note: The AllFusion CA-InterTest for CICS LIST facility (the online
viewing of compile and assembly listings before program execution) is
not affected by this setting.

SLBAKEEP=YES/NOSpecifies the default value for the LIST facility of the

AutoKeep display feature. Regardless of this setting, the value can be
adjusted online at any time.
YES Displays items in the Keep window concerning the currently highlighted
line and any data items you have requested to be displayed in the Keep
Window.
NO

Displays only the data items you have requested to be displayed in the
Keep Window.

SLBMARG=1/nnSpecifies 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.

Presents the right-most portion.

Suppresses the machine code.

Suppresses the machine code and statement numbers.

SLBSCRL=PAGE/HALF/STOP/nnnnSpecifies the default scroll value for

the LIST facility (online viewing of compile and assembly listings) when
the user presses the PF7 or PF8 keys. Regardless of this setting, the
value can be adjusted online at any time.
PAGE Scrolls the display one page.
HALF

516

Getting Started

Scrolls the display half a page.

Procedure for Modifying Options

STOP

Scrolls the display to the next declared breakpoint.

nnnn

Scrolls the display the specified number of lines (1 to 9999).

SLBTIT=YES/NO/REGSSpecifies the default top portion of the display of

the LIST facility (online viewing of compile and assembly listings); that
is, whether the titles for the options and PF keys should be presented or
not. Regardless of this setting, the value can be adjusted online at any
time.
YES Displays the entire top portion of the display, leaving less space for the
source listing.
NO Displays only the entry fields and a command line, leaving more space for
the source listing. Pressing the PF4 or PF16 key displays the entire top
portion so a user can review the options or PF key assignments.
REGS Displays the same fields as SLBTIT=NO, but also displays the general
registers and the condition code at a breakpoint.
STMTTRCE=500/nnnnnSpecify the number of entries in the statement
trace table. This table will be allocated to any transaction which executes
one or more COBOL programs for which the TRACE option is active. The
maximum value is 32767.
STUAR= NO/YESAffects breakpoint processing in regard to the TCTTE user
area (an area embedded in the TCTTE, whose address is in the field
labeled TCTTECIA).
NO

The contents of the area are not saved for the duration of the breakpoint
or restored when the task continues execution from the breakpoint.
There is no need to preserve the data in the area if the breakpoint
display is to be sent to another terminal, or if the area is to be modified
(during the breakpoint) only by the person performing the test. Because
command level (EXEC CICS) applications rarely use this area,
STUAR=NO should be appropriate.
Also specify STUAR=NO if the area may be affected during the
breakpoint by a facility other than the tested application.

YES The contents of the area are preserved for the duration of the
breakpoint. Specify STUAR=YES if the logic of the tested application
depends on saving this area while your task waits at a breakpoint, and
then restoring it to its previous value, possibly with your modifications.
STUAR=YES is desirable if the area can be used during the breakpoint
and use of the area must not affect the tested program.
SYMDFIL=PROTDMP/filenameFor AllFusion CA-SymDump for CICS
users, specify the file name for the AllFusion CA-SymDump for CICS (the
Symbolic Dump option) file. This is the name of the file from which
dumps can be viewed; AllFusion CA-SymDump for CICS always writes to
the file PROTDMP. The name cannot exceed seven characters. Be sure to
adjust the CICS file definition if you do not use the default.

Chapter 5: Options

517

Procedure for Modifying Options

SYMDINT=YES/NOFor AllFusion CA-SymDump for CICS users viewing a

source listing, this option specifies whether the user can invoke AllFusion
CA-InterTest for CICS functions for the abended program.
YES AllFusion CA-SymDump for CICS users can invoke AllFusion CA-InterTest
for CICS functions when viewing a source listing for an abended
program. For example, users can set monitoring, invoke the FILE facility,
and perform other AllFusion CA-InterTest for CICS functions directly from
AllFusion CA-SymDump for CICS.
NO

AllFusion CA-SymDump for CICS users cannot invoke AllFusion

CA-InterTest for CICS functions when viewing a source listing for an
abended program. To invoke AllFusion CA-InterTest for CICS functions,
users must access AllFusion CA-InterTest for CICS directly.

SYMDL=SYMD/transaction-idFor AllFusion CA-SymDump for CICS users,

specify a four-character transaction ID for the AllFusion CA-SymDump
for CICS transaction for the capture for the last SQL statement in
background during dump capture. Be sure to adjust the CICS transaction
definition if you do not use the default. If no value is specified for this
option, then no transaction will be scheduled.
SYMDT=SYMD/transaction-idFor AllFusion CA-SymDump for CICS users,
specify a four-character transaction ID for the AllFusion CA-SymDump
for CICS transaction that allows dumps to be viewed online. Be sure to
adjust the CICS transaction definition if you do not use the default.
SYMDWILD=Specify a wild card prefix for the Dump File ID that is specified
on the DUMP/TRACE ANALYSIS screen. This limits what can be specified
as a wildcard. For example, coding SYMDWILD=PROT lets you specify file
names with a wildcard prefix of PROT in the Dump File ID input field of
the AllFusion CA-SymDump Analysis screen. In this case, PROT* would
be valid input but PRO* would be in error.
SYMFIL=PROTSYM/file/(file1,file2,....)Specify the CICS file definition
names for the AllFusion CA-InterTest for CICS symbolic files. The names
cannot exceed seven characters. If more than one name is specified, the
names must be separated by commas and the entire list enclosed in
parentheses. Be sure to adjust the CICS file definition if you do not use
the default.
This option tells AllFusion CA-InterTest for CICS the CICS file definitions
of the AllFusion CA-InterTest for CICS symbolic files and their search
order for program data. When monitoring is turned on for a program,
AllFusion CA-InterTest for CICS searches the symbolic files in the
sequence specified and for COBOL and PL/I programs finds the symbolic
file member that matches the corresponding load module compile
date/time. If a matching date/time cannot be found or a symbolic file
member has a more recent date than the date in the load module, a
symbolic file mismatch screen will appear and the customer must chose
which symbolic file member to use for debugging. For Assembler
programs, the symbolic file mismatch screen will always appear if a
program is found on more than one symbolic file.

518

Getting Started

Procedure for Modifying Options

Once a matching date/time member is found or a member is selected

from a mismatch screen, AllFusion CA-InterTest for CICS will continue to
use the selected symbolic file member until all breakpoints and
monitoring has been turned off for the program.
There is no upper limit to the number of symbolic files that you can
specify. However, limit the number of files to reduce the overhead and
the storage required for the VSAM buffers because each CICS file
definition must be defined with LSRPOOL=NONE.
SYMPSWD=12345678/character-stringSpecify an eight-character
password used by the symbolic file utility program IN25UTIL to guard
against an inadvertent change to the symbolic file. The password
generated here will be required when doing the following utility
functions: INITIALIZE, RELOAD, DELETE, or PURGE.
To change the default password, specify any character string up to eight
characters long.
TRCFDCLS=For AllFusion CA-SymDump for CICS users, specify an
allocation DATA CLASS that the TRACE FORMAT REGION will use to
allocate storage for trace formatting. This parameter is used only by the
TRACE FORMAT REGION and is ignored by a CICS region.
TRCFFMID=SYMDTRCF/8 character unique idFor AllFusion
CA-SymDump for CICS users, specify the unique TRACE FAMILY ID that
a CICS region will use to locate and form an affinity with a TRACE
FORMAT REGION that has an IN25OPTS with the same TRCFFMID. This
parameter is used by both the CICS region and the TRACE FORMAT
REGION.
TRCFMCLS=For AllFusion CA-SymDump for CICS users, specify an
allocation MANAGEMENT CLASS that the TRACE FORMAT REGION will use
to allocate storage for trace formatting. This parameter is used only by
the TRACE FORMAT REGION and is ignored by a CICS region.
TRCFMEGM=120/ total number of megs For AllFusion CA-SymDump for
CICS users, specify the maximum size of extended private area storage
in megabytes that the TRACE FORMAT REGION will allocate for use by all
threads. This amount of extended private must be available to the TRACE
FORMAT REGION when it starts, or the job will terminate. If this number
is exceeded when a trace is selected for formatting, the user is invited to
try again later, this allows performance tuning of the formatted trace
facility. This parameter is used only by the TRACE FORMAT REGION and
is ignored by a CICS region.
TRCFMEGT=15/megs per threadFor AllFusion CA-SymDump for CICS
users, specify the maximum size of extended private area storage in
megabytes that the TRACE FORMAT REGION will allocate for use by one
thread. If this is not available when a trace is selected for formatting, the
user is invited to try again later. This will allow performance tuning of the
formatted trace facility. This parameter is used only by the TRACE
FORMAT REGION and is ignored by a CICS region.

Chapter 5: Options

519

Procedure for Modifying Options

TRCFSCLS=For AllFusion CA-SymDump for CICS users, specify an

allocation STORAGE CLASS that the TRACE FORMAT REGION will use to
allocate storage for trace formatting. This parameter is used only by the
TRACE FORMAT REGION and is ignored by a CICS region.
TRCFTHRD=8/ number of threads For AllFusion CA-SymDump for CICS
users, specify the number of simultaneous threads that will be supported
for trace format requests. This parameter should be used as a
rudimentary throttle to allow performance tuning of the formatted trace
facility. This parameter is used only by the TRACE FORMAT REGION and
is ignored by a CICS region.
TRCFTOUT=240/ trace timeout in secondsFor AllFusion CA-SymDump
for CICS users, specify trace timeout value in seconds that both the
TRACE FORMAT REGION and the CICS task will wait on CCI calls used to
communicate between the CICS task and the TRACE FORMAT REGION.
When this value is exceeded, the CCI session is terminated, and the
formatted trace resources are freed. The operator remains within the
reloaded dump, and is given the option of reformatting the trace. This
will allow performance tuning of the formatted trace facility. This
parameter is used by both the CICS region and the TRACE FORMAT
REGION.
TRCFUNIT=For AllFusion CA-SymDump for CICS users, specify an
allocation UNIT that the TRACE FORMAT REGION will use to allocate
storage for trace formatting. This parameter is used only by the TRACE
FORMAT REGION and is ignored by a CICS region.
TRCFVOL=For AllFusion CA-SymDump for CICS users, specify an allocation
VOLUME that the TRACE FORMAT REGION will use to allocate storage for
trace formatting. This parameter is used only by the TRACE FORMAT
REGION and is ignored by a CICS region.
UCONLY=NO/YESDetermines whether certain terminal output will be
dynamically translated from lowercase to uppercase.
NO

Terminal output is not dynamically translated.

YES Terminal output is dynamically translated to uppercase characters. If you

previously installed the uppercase version of the AllFusion CA-InterTest
for CICS load libraries because your terminals did not support the mixed
case English character set, you should specify YES.
USERHELP=PROTUHF/ filenameSpecify the file name for the optional
help file of user-defined abend descriptions. The name cannot exceed
seven characters. Be sure to adjust the CICS file definition if you do not
use the default.

520

Getting Started

Procedure for Modifying Options

VERCOR=NO/YESDetermines whether changes to main storage must be

verified.
NO

Changes to main storage requested in a CORE transaction command can,

but need not be, verified in the same command.
If CORSEC=YES is specified, the user cannot modify any foreign piece of
storage by mistake because the CORE transaction will ask for the
password. As a result, you can specify VERCOR=NO because a careless
user can harm only the tested program's data.

YES Any change to main storage requested in a CORE transaction command

must be verified in the same command regardless of password protection
(see the CORSEC= keyword). This compulsory verification could make a
debugging session unnecessarily tedious, thus decreasing productivity.
The system programmer will find this specification a hindrance,
especially in situations when a certain value must be forced upon an area
whose content continually changes.
For more information, see the Accessing Main Storage: CORE chapter
in the User Guide.
VRPTT=VRPT/transaction-idSpecify a four-character transaction ID for
the AllFusion CA-InterTest for CICS VRPT transaction used to verify the
installation and display the installation options. Be sure to adjust the
CICS transaction definition if you do not use the default.
VTATT=VTAT/transaction-idSpecify a four-character transaction ID for
the AllFusion CA-InterTest for CICS VTAT transaction. This is an internal
AllFusion CA-InterTest for CICS transaction used only for handling
breakpoints. Since it is not used by any operator, its use must not be
protected by a specific user. If started by mistake from a terminal, the
program does nothing. Be sure to adjust the CICS transaction definition
if you do not use the default.
XRMIO=NO/YESFor AllFusion CA-InterTest for CICS users, determines
whether or not to use the CICS XRMIOUT Global User Exit to keep track
of the last SQL call issued by an application program.
NO

Allows capture of SQL information provided that an EXEC CICS command

has not occurred between the SQL call and the abend.

Yes Provides the last SQL call to the applications programmer for the
CORE=SQLCA and CORE=LASTSQL commands, but there is an overhead
associated with the use of the XRIMIOUT exit that not all shops will want
to incur.

Chapter 5: Options

521

Implement Composite Support

Composite support lets users test composite modulesload modules named in
a CICS program definition that consist of separately compiled or assembled
parts brought together when the module is link-edited. The main program and
called subroutines can be written in the same or different languages. With
composite support, users can test and debug a subroutine as if it were a
separate program.
See the User Guide for a detailed description of how to add composite support
dynamically using the COMPOSITE command. Composite support may also be
added with the batch facility IN25LINK. For details on using IN25LINK, see the
AllFusion Testing and Fault Management Symbolic Guide.

Declare User-Defined CORE Commands

This section explains how to define your own CORE keywords. User-defined
CORE keywords provide a shorthand method for entering a complex CORE
command by specifying a simple command that contains one or more of your
own keywords. The new keyword is automatically replaced with a string of
command elements that could otherwise be difficult to remember.
Among the new commands can be some to display your own areas in main
storage, such as crucial control tables for running an application system. If
your replacement command includes the USE= element, the storage areas can
be displayed as COBOL or Assembler structures, with names and offsets
attached to each data field.
For details, see the AllFusion CA-InterTest for CICS Help facility. Select the
CORE Facility, then Structured Data Displays, and then Additional Features.

CORUCOM Macro
The CORUCOM macro lets you define any number of new CORE command
keywords, each an abbreviation for a series of CORE command elements. For
instance, there is a user table that is pointed to by an address located eight
bytes into the CWA. There is a counter 12 bytes into this table that contains
the number of times a service request transaction was issued. Add the
following CORUCOM entry and assemble the CORUCOM table:
CORUCOM CODE=SERVCNT,COMND=CWA@8+C
To display the service request count online, issue:
CORE=SERVCNT

522

Getting Started

Declare User-Defined CORE Commands

Code one CORUCOM macro for each new CORE keyword. Submit the resulting
source code to assemble a new AllFusion CA-InterTest for CICS load module
named IN25UCOM. The module is used by the CORE facility as a table to
convert your own keywords into strings of CORE keywords.
Since the CORUCOM macro generates a separate CICS load module, you can
add new or modified commands at any time. To do this, code the commands,
assemble the module, and then do a NEWCOPY for the load module IN25UCOM
by issuing:
CEMT SET PROG(IN25UCOM) NEWCOPY

Code the CORUCOM Macros

The CORUCOM macro is delivered in the AllFusion CA-InterTest for CICS
source library. The first CORUCOM statement must be coded as follows:
1

COL= 1...5....0....5
CORUCOM TYPE=INITIAL

The last CORUCOM statement must be coded as follows:

COL= 1...5....0....5
CORUCOM TYPE=FINAL

Each user-defined CORUCOM statement specifies one user-defined element of

the CORE command and one string of CORE commands that will replace that
user-defined element.
The user-defined element is specified by the CODE= keyword. Each element
keyword must be less that eight characters long, must consist only of
alphanumeric characters and, to prevent confusion with a hexadecimal
number, must contain at least one of these characters:
GHIJKLMNOPQRSTUVWXYZ. When two or more keywords have the same
prefix (for example, ICE2, ICE), the longer keyword must be specified first, as
illustrated in the following example.
The string of CORE command elements is specified by the COMND= keyword.
The string must be enclosed in apostrophes and, within the string, any
apostrophe must be coded as two apostrophes. All elements of the CORE
command are permitted, including other user-defined elements. In the
following example:

The new keyword ICE2 (second macro) uses another new keyword ICE (in
the third macro). Notice that the longer keyword is specified first.

Chapter 5: Options

523

Declare User-Defined CORE Commands

The fourth macro defines the keyword MYTABLE, which displays a storage
area pointed to by the address in the CWA, and produces a display
formatted as a structure named MYTABLE in the AllFusion CA-InterTest for
CICS symbolic file records identified by the name MYSYMDEF. For more
details, see the section Adding Assembler DSECTs to the symbolic file.

The * in column 72 means continuation.

COL= 1...5....0.....6............................................2
CORUCOM TYPE=INITIAL

(required)

CORUCOM CODE=ICE2,COMND='ICE@4'
CORUCOM CODE=ICE,COMND='=CSA@54'
CORUCOM CODE=MYTABLE,COMND='=CWA@8,USE=MYSYMDEF.MYT*
ABLE'
CORUCOM TYPE=FINAL

(required)

Sample JCL for Assembling IN25UCOM

The following IN25UCOM JCL example uses the standard IBM procedure to
assemble and link-edit macro level programs.
//UCOM JOB ...
//*

(COMMENT: A STANDARD IBM PROC FOR ASSEMBLER MACRO LEVEL)

//STEP

EXEC ASMFCL

//ASM.SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR
//ASM.SYSIN

DD *

CORUCOM TYPE=INITIAL
*

YOUR FIRST CORUCOM STATEMENT GOES HERE

.....

CORUCOM TYPE=FINAL
END
/*
//LKED.SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR
//LKED.SYSIN DD *
NAME IN25UCOM(R)
/*
//

In the LKED.SYSLMOD DD statement, replace xx with your two-digit CICS

release number (for example, 62 for CTS 2.2, 63 for CTS 6.3, 64 for CTS 3.1,
or 65 for CTS 3.2).
Note: The IN25UCOM member of the AllFusion CA-InterTest for CICS source
library contains sample source for assembling the IN25UCOM load module.

524

Getting Started

Add Assembler DSECTs to the Symbolic File

AllFusion CA-InterTest for CICS lets you display the major CICS areas in
Assembler DSECT format. You can also display your own user areas in DSECT
format. One way to do this is to add your DSECTs to the ones supplied by
AllFusion CA-InterTest for CICS. However, if you do this, your entries will
disappear when you install a new release of AllFusion CA-InterTest for CICS. A
better way is to create one or more symbolic file members to contain your
DSECTs.
Saving all of the DSECTs used at your site in one symbolic file member allows
users of the FILE transaction to omit the symbolic program name when
requesting records or DL/I segments in structured format. The name of this
member must be referenced in the FSYMP installation option. The default
name is PROTFILE.
Complete the following steps to create your own symbolic file members:
1.

Run a job to add the members containing the DSECTs to the symbolic file.

Run a job to define the CORE keywords needed to display the DSECTs.

Sample JCL for Adding Members to the Symbolic File

This sample JCL adds member USERDSEC to the symbolic file. This member
contains the DSECT USERTWAF.
//USERDSEC

JOB

your JOB card goes here

//ASM

EXEC

PGM=ASMA90,REGION=1024K

//SYSLIB

DSN=USER.SOURCE,DISP=SHR

//SYSUT1

DSN=&SYSUT1,SPACE=(1024,(120,120),,,ROUND),
UNIT=VIO,

DCB=BUFNO=1

//SYSPUNCH

SYSOUT=B

//SYSTERM

SYSOUT=*

//SYSPRINT

DSN=&&TEMP,DISP=(,PASS),UNIT=SYSDA,
SPACE=(CYL,(3,2)),

DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)

//SYSIN

USERTWAF

DSECT

COPY USERTWAF
USERDSEC

CSECT
END

//*
//PARM

EXEC

PGM=IN25PARM,REGION=512K,
PARM='USERDSEC,LISTER=REF,NOPURGE'

//STEPLIB

DSN=CAI.CAILIB,DISP=SHR

//CARDS

DSN=&&CARDS,DISP=(,PASS),UNIT=SYSDA,
SPACE=(80,1)

//*
//SA

EXEC

PGM=IN25SYMA,REGION=512K

Chapter 5: Options

525

Add Assembler DSECTs to the Symbolic File

//STEPLIB

DSN=CAI.CAILIB,DISP=SHR

//INPUT

DSN=&&TEMP,DISP=(OLD,DELETE)

//OUTPUT

SYSOUT=*,

//MESSAGE

SYSOUT=*

//PROTSYM

DSN=INTRTST.PROTSYM,DISP=SHR

//CARDS

DSN=&&CARDS,DISP=(OLD,DELETE)

DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)

For instructions on the STEPLIB DD, see the section Adding COBOL File
Structures to the symbolic files.
For an explanation of the IN25PARM and IN25SYMA programs, see the chapter
Adding Symbolic Information in the AllFusion Testing and Fault Management
Symbolic Guide.
Note: This job does not require a link-edit step because it only updates the
symbolic file. No load module is produced.

Sample JCL for Defining CORE Keywords

After you have added the necessary members to the symbolic file, run a job to
define the commands needed to access your DSECTs. The sample job below
uses CORUCOM macros to define the user CORE keyword TWAF. See the
section Declaring User-Defined CORE Commands for a detailed explanation.
//UCOM JOB ...
//*

(COMMENT: A STANDARD IBM PROC FOR ASSEMBLER MACRO LEVEL)

//STEP

EXEC ASMFCL

//ASM.SYSLIB
//ASM.SYSIN

DD
DD

DSN=CAI.SAMPLIB,DISP=SHR

COPY CORUCOM
CORUCOM TYPE=INITIAL
CORUCOM CODE=TWAF,COMND='TWA,USE=USERDSEC.USERTWAF'
CORUCOM TYPE=FINAL
END
/*
//LKED.SYSLMOD

DD DSN=CAI.CACICSxx,DISP=SHR

//LKED.SYSIN

NAME IN25UCOM(R)
/*
//

In the LKED.SYSLMOD DD statement, replace xx with your two-digit CICS

release number (for example, 62 for CTS 2.2, 63 for CTS 6.3, 64 for CTS 3.1,
or 65 for CTS 3.2).

526

Getting Started

Unprotect Main Storage with User Exit IN25LETX

IN25LETX is an optional exit program coded by the user that specifies areas in
main storage that should not be protected by AllFusion CA-InterTest for CICS.
The areas to be unprotected are indicated by beginning and ending storage
addresses.
This exit program provides a programmable function equivalent to the
AllFusion CA-InterTest for CICS interactive LET option. This is a particularly
useful option, because frequently an application program is designed to modify
a storage area that is protected by AllFusion CA-InterTest for CICS. Ordinarily
when that happens, AllFusion CA-InterTest for CICS initiates an automatic
breakpoint and halts the program's execution.
IN25LETX must follow the rules for command-level programs. It executes
within the task of the monitored application program, and must not do
anything that would affect normal execution of the application. IN25LETX is
invoked each time AllFusion CA-InterTest for CICS begins monitoring and also
when it resumes monitoring, such as after a CICS command or after any kind
of breakpoint.
The interface to IN25LETX is a CICS command level LINK with a COMMAREA.
This allows a user's IN25LETX module to issue CICS SPI or API commands to
locate key module addresses.
Note: The interface permits IN25LETX to return a variable-length table of pairs to
AllFusion CA-InterTest for CICS in a single pass. Previous non-ESA versions of
IN25LETX branched to AllFusion CA-InterTest for CICS for each address pair until
all address pairs were passed.

IN25LETX COMMAREA
The IN25LETX COMMAREA contains the fields discussed next. See the section
Sample IN25LETX Program for the COMMAREA layout.
COMMAREA Field

Length

Primed By

Table Address

Fullword

User

Monitored Program

8 bytes

AllFusion CA-InterTest for

CICS

Application Registers

Fullword

AllFusion CA-InterTest for

CICS

Chapter 5: Options

527

Unprotect Main Storage with User Exit IN25LETX

Table Address This field is set to zeros upon entry to the exit. AllFusion
CA-InterTest for CICS assumes it was passed a valid table address if this field
is modified. Leaving this field set to zeros causes AllFusion CA-InterTest for
CICS to remove any address pairs previously set by this exit for this task.
Monitored ProgramContains the name of the program being monitored by
AllFusion CA-InterTest for CICS at the time this exit was invoked.
Application RegistersThe fullword address of the 16-fullword area
containing the application's registers (0 to 15) that were saved just before the
entry to this exit.

LETX Table
For each area of main storage that is to be unprotected, IN25LETX stores a
pair of addresses in a table (the LETX table). Each pair of addresses represents
a from and a to area of storage that will not be protected by AllFusion
CA-InterTest for CICS if those areas are modified by the application. For
example, if the area to be unprotected resides at address X'11AA2E0' and is
X'2000' bytes long, the address pair is 11AA2E0 and 11AC2E0.
The last entry in the table must contain two full words of X'FFFFFFFF'.
In many cases, the declared addresses may only need to be unprotected for a
particular CICS task or program execution. Thus the logic of IN25LETX may
need to consider the varying circumstances of execution, including the
following tasks:

Transaction identification

Terminal identification

Logical level of execution

Program identification

IN25LETX must deliver a full table of address pairs each time it is invoked.
IN25LETX does not have to be reentrant, meaning it can contain save areas
and tables in which permanent addresses can be stored. There is no need to
rebuild the LETX table if the addresses do not change. In this case, a one-time
routine can find the areas, build the LETX table, and save the table in the
IN25LETX module for the next time. IN25LETX can make itself resident by
loading itself again (see the section Sample IN25LETX Program).
IN25LETX can reside above or below the 16 MB line and execute in either
addressing mode. All table addresses, however, must have the X'80000000'
bit turned off; that is, the address X'01234567' must not be passed as
X'81234567'.

528

Getting Started

Unprotect Main Storage with User Exit IN25LETX

Sample IN25LETX Program

The sample IN25LETX program that follows locates two areas, both
permanently resident in storage, which are to be unprotected for all monitored
programs running under transaction code ABCD. The first area is a table
pointed to by an address in the user's TWA. The second area is a table loaded
as a member of the CICS program definition named ATABLE. Both areas are
established before AllFusion CA-InterTest for CICS becomes active and remain
resident in main storage.
*
TITLE 'IN25LETXALLFUSION CA-INTERTEST LET EXITUSER CODED'
DFHREGS

*
DFHEISTG DSECT
XPROGLEN DS

WORKING STORAGE DSECT

PROGRAM LENGTH

****************************************************************
*

I N 2 5 L E T X

C O M M A R E A

****************************************************************
COMMAREA DSECT

COMMAREA

CTBLADDR DS

ADDRESS OF USER LET TABLE

INTPROG

CL8

NAME OF MONITORED PROGRAM

INTREGS

ADDR OF APPL REGISTERS (0-15)

*
USERTWA

DSECT

DSECT FOR USER TWA

UTBLADDR DS

ADDRESS OF USER TABLE

UTBLLEN

LENGTH OF USER TABLE

*
*****************************************************************
IN25LETX DFHEIENT EIBREG=R11,CODEREG=R12,DATAREG=R13
*
L

R10,DFHEICAP

POINT TO COMMAREA

USING COMMAREA,R10
*
CLC

EIBTRNID,=C'ABCD'

IS THIS THE TRANSACTION?

BNE

RETURN

NO, RETURN, DO NOT SET ANY

ADDRESSES FOR THIS TASK

*
PROCESS

CLC

LTWATBL,=D'0'

HAVE THEY BEEN ALREADY SAVED?

GETAREAS

NO, GO GET THEM

R1,LTABLE

THEN, THE LET TABLE IS BUILT...

R1,CTBLADDR

PUT LET TABLE ADDR IN THE COMMAREA

*
RETURN

EXEC CICS RETURN

*
GETAREAS DS

*
EXEC CICS ADDRESS TWA(R5)
USING USERTWA,R5

Chapter 5: Options

529

Unprotect Main Storage with User Exit IN25LETX

*
L

R1,UTBLADDR

GET THE START OF THE TWA AREA

R1,=X'7FFFFFFF'

ENSURE HIGH-ORDER BIT IS TURNED

R1,LTWATBL

STORE THE AREA'S START ADDRESS

R1,UTBLLEN

ADD THE TABLE LENGTH

R1,LTWATBL+4

STORE THE AREA'S END ADDRESS

OFF IN USER'S ADDRESS

*
EXEC CICS INQUIRE PROGRAM('ATABLE') LOADPOINT(R0)

LENGTH(XPROGLEN)
*
ST

R0,LPROGTBL

STORE THE AREA'S START ADDRESS

R0,XPROGLEN

ADD THE PROGRAM'S LENGTH

R0,LPROGTBL+4

STORE THE AREA'S END ADDRESS

*
**********************************************************************
* LOAD THIS EXIT AGAIN SO IT WILL NOT HAVE TO REOBTAIN THE ADDRESSES *
* ON THE NEXT CALL TO THIS EXIT.

**********************************************************************
EXEC CICS LOAD PROGRAM('IN25LETX') HOLD
*
LA

R1,LTABLE

R1,CTBLADDR

RETURN

LTABLE

LET TABLE

LTWATBL

2F'0'

ADDRESSES OF TWA TABLE

LPROGTBL DC

2F'0'

ADDRESSES OF PROGRAM TABLE

LEND

X'FFFFFFFF'

END OF TABLE INDICATOR

PUT ADDR OF LET TABLE IN COMMAREA

DC
LTORG
END

Disable IN25LETX
AllFusion CA-InterTest for CICS uses IN25LETX during all monitoring; that is,
for all entries of the AllFusion CA-InterTest for CICS monitoring table. To
prevent AllFusion CA-InterTest for CICS from executing IN25LETX, you must
disable it or remove it from the program library.
Once a link to IN25LETX fails (because the program is disabled), AllFusion
CA-InterTest for CICS will not try the link again, thus avoiding much overhead.
In such a case, the execution of IN25LETX will not resume until the next
AllFusion CA-InterTest for CICS start.

530

Getting Started

Add COBOL File Structures to the Symbolic File

The COBOL II program shown next is an example of a dummy default program
that contains 01 level structures. Saving all of the 01 level structures used at a
site in one file allows users of the FILE transaction to omit the symbolic
program name when requesting records or DL/I segments in structured
format. Symbolic information for the default program must be saved in the
symbolic file, and its name must be referenced in the FSYMP installation
option. The default name is PROTFILE.
//PROTFILE JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A
//*
//COB
//

EXEC PGM=IGYCRCTL,REGION=1024K,

PARM='OBJECT,APOST,FLAG(I,W),LIST,XREF,MAP,NOOPT,VBREF'

//STEPLIB

DD DSN=SYS1.COB2COMP,DISP=SHR

//SYSLIB

DD DSN=CICS.COBLIB,DISP=SHR

//SYSLIN

DD DSN=&&LOADSET,DISP=(MOD,PASS),

UNIT=SYSDA,SPACE=(80,(250,100))

//SYSUT1