Int60oG1

IntGSms.doc, printed on 12/21/00, at 2:33 PM

Getting Started6.0

CA-InterTest® for CICS

MAN10140445E


This documentation and related computer software program (hereinafter referred to as the“Documentation”) is for the end user’s informational purposes only and is subject to change orwithdrawal by Computer Associates International, Inc. (“CA”) at any time.

THIS DOCUMENTATION MAY NOT BE COPIED, TRANSFERRED, REPRODUCED,DISCLOSED OR DUPLICATED, IN WHOLE OR IN PART, WITHOUT THE PRIOR WRITTENCONSENT OF CA. THIS DOCUMENTATION IS PROPRIETARY INFORMATION OF CA ANDPROTECTED BY THE COPYRIGHT LAWS OF THE UNITED STATES AND INTERNATIONALTREATIES.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THISDOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUTLIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR APARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TOTHE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT ORINDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUTLIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL OR LOST DATA, EVENIF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.

THE USE OF ANY PRODUCT REFERENCED IN THIS DOCUMENTATION AND THISDOCUMENTATION IS GOVERNED BY THE END USER’S APPLICABLE LICENSEAGREEMENT.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227.7013(c)(1)(ii) or applicable successor provisions.

� 1985, 2000 Computer Associates International, Inc., One Computer Associates Plaza, Islandia, New York11749. All rights reserved.

All trademarks, trade names, service marks, or logos referenced herein belong to their respective companies.

Contents iii


Contents

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

iv CA-InterTest for CICS Getting Started


Chapter 2: Getting Started with CA-InterTest forCICSWhat You Need to Get Started .................................................. 2–2Summary of Changes for This Release ........................................... 2–3Release Notes for Existing Users................................................. 2–4

Starting a Test Session ...................................................... 2–4Source Listing Facility Features .............................................. 2–4New Monitoring Menus and Status Display .................................. 2–5CNTL Menus .............................................................. 2–6New Breakpoint Menu (PF 6 Menu).......................................... 2–6

Major SMP Operations ......................................................... 2–7

Chapter 3: System RequirementsOperating Environments ....................................................... 3–1Unicenter TNG Framework for OS/390 Common Services Requirements............ 3–2

CAIRIM ................................................................... 3–3CA LMP................................................................... 3–3CAICCI ................................................................... 3–4

CA-Hardware Requirements.................................................... 3–5Distribution Libraries....................................................... 3–5Target Libraries ............................................................ 3–6

Special Considerations ......................................................... 3–6PL/I Programs............................................................. 3–6Global User Exits........................................................... 3–7TIOA Compression Routine Users ........................................... 3–8CICSPlex Support .......................................................... 3–8

Installation Requirements for CICSPlex Support........................... 3–8Startup and Termination with CICSPlex Support .......................... 3–9

CA-ACF2 and RACF Users.................................................. 3–9CA-Realia II Workbench For OS/390 CICS Users.............................3–10Database Support .........................................................3–10HOGAN Users............................................................3–10MRO Users ...............................................................3–11

Contents v


Omegamon Users......................................................... 3–11TMON Users ............................................................. 3–11User CORE Commands ................................................... 3–11User Macros and Software Calls Support.................................... 3–11

CA-InterTest 6.0 Migration Considerations...................................... 3–12CA-InterTest 4.x to 6.0 Migration Considerations ................................ 3–14

Chapter 4: Base Product Installation StepsSummary of Installation Steps .................................................. 4–2Step 1. Review System Requirements ............................................ 4–3Step 2. Enter LMP Product Key Certificate Information............................ 4–4

Using CA LMP ............................................................ 4–4Enter CA LMP Key Information for the PL/I Symbolic and CA-SymDump Options4–7

Step 3. Complete the Installation Worksheet ..................................... 4–7Step 4. Load Installation Sample JCL Library ..................................... 4–9Step 5. Allocate Target and Distribution Libraries ............................... 4–10Step 6. Allocate Private SMP/E Libraries and Define SMP Zones .................. 4–10

Task 1. Allocate and Initialize Computer Associates Base SMP Libraries ....... 4–11Task 2. Define Additional Product Target and Distribution Zones ............. 4–11

Step 7. Customize the SMP Procedure .......................................... 4–12Step 8. Receive the CA-InterTest for CICS Product ............................... 4–12Step 9. Apply the CA-InterTest for CICS Product ................................ 4–13Step 10. Accept the CA-InterTest for CICS Product............................... 4–14Step 11. Install the CA-InterTest for CICS Help Facility........................... 4–15Step 11a. Create the User-Defined Abend Description File ........................ 4–16Step 12. Create the CA-InterTest for CICS Symbolic File .......................... 4–16

Symbolic File Entries...................................................... 4–17Concurrently Updating the PROTSYM File.................................. 4–17

Step 13. Create the CA-InterTest for CICS Checkpoint File........................ 4–18Step 14. Add the Required CICS Resource Definitions............................ 4–18Step 15. Adjust the CICS JCL .................................................. 4–19

vi CA-InterTest for CICS Getting Started


Step 16. Install DB2 Support....................................................4–19Supporting DB2 Calls in the FILE and CORE Facilities ........................4–19Monitoring DB2 Applications ..............................................4–20

Step 17. Restart CICS and Run Check-out Program ...............................4–21Step 18. Install Support for the PL/I Option (Optional) ...........................4–21Step 19. Unload Documentation Set.............................................4–22

Unloading BookManager Files from the Distribution Tape ....................4–22Changing the Prefix in the Bookshelf Definition ..........................4–23Downloading OS/390 Files for Use on a PC ..............................4–23

Unloading the Acrobat PDF File from the Distribution Tape...................4–24Printing the Quick References ..............................................4–25

Activating CA-InterTest for CICS...............................................4–26Deactivating CA-InterTest for CICS.............................................4–27

Chapter 5: PL/I Option Installation StepsStep 1. Receive the CA-InterTest PL/I Option..................................... 5–2Step 2. Apply the CA-InterTest PL/I Option ...................................... 5–2Step 3. Accept the CA-InterTest PL/I Option ..................................... 5–3

Chapter 6: Symbolic SupportCOBOL Compilers ............................................................. 6–1

IBM COBOL Compiler Options.............................................. 6–3CA-Optimizer and CA-Optimizer/II Option.................................. 6–4

Using the Post-Processors with Multiple CA-InterTest Releases .................... 6–5CA-InterTest Post-Processor Program Options ................................ 6–5Controlling Printed Output with the CUTPRINT Option ....................... 6–6Saving Your Listing for Online Display with the LISTER Option ................ 6–6Setting Data as Nonpurgable ................................................ 6–7

COBOL JCL Examples.......................................................... 6–8COBOL/VS or CA-Optimizer Example....................................... 6–8COBOL II, CA-Optimizer/II, COBOL/370, IBM COBOL for MVS, or IBM COBOL forOS/390 Example ..........................................................6–10

Contents vii


Assembler Programs.......................................................... 6–12Assembler Options ....................................................... 6–13IN25SYMA Options....................................................... 6–14Controlling Printed Output with the CUTPRINT Option ..................... 6–14Saving Your Listing for Online Display with the LISTER Option .............. 6–15Setting Data as Nonpurgable............................................... 6–15Assembler JCL Example................................................... 6–17

PL/I Programs ............................................................... 6–18Compiler Options......................................................... 6–19Installation Options ....................................................... 6–19IN25SYMP Options ....................................................... 6–20Controlling Printed Output with the CUTPRINT Option ..................... 6–20Saving Your Listing for Online Display with the LISTER Option .............. 6–21Setting Data as Nonpurgable............................................... 6–22PL/I JCL Example ........................................................ 6–23

Chapter 7: Modifying CA-InterTest for CICS OptionsProcedure for Modifying Options ............................................... 7–1Sample JCL to Assemble the Options Program ................................... 7–4IN25OPTS Keywords .......................................................... 7–5

Chapter 8: Additional CA-InterTest for CICSCustomization ProceduresImplementing Composite Support .............................................. 8–1

IN25LINK Program........................................................ 8–2Identifying the Composite Module .......................................... 8–3Identifying the Main Program and Subroutines ............................... 8–4Excluding Subroutines ..................................................... 8–5Example .................................................................. 8–5

Declaring User-Defined CORE Commands ...................................... 8–9The CORUCOM Macro.................................................... 8–10Coding the CORUCOM Macros ............................................ 8–10

viii CA-InterTest for CICS Getting Started


Sample JCL for Assembling IN25UCOM ....................................8–12Adding Assembler DSECTs to the Symbolic File .................................8–13

Sample JCL for Adding Members to the Symbolic File ........................8–14Sample JCL for Defining CORE Keywords...................................8–15

Unprotecting Main Storage with the User Exit IN25LETX .........................8–16The IN25LETX COMMAREA ..............................................8–17The LETX Table ...........................................................8–17Sample IN25LETX Program ................................................8–18Disabling IN25LETX.......................................................8–20

Adding COBOL File Structures to the Symbolic File ..............................8–20Specifying Abend Codes That Should Not Be Intercepted .........................8–22Customizing Help for Abend Codes ............................................8–24

Chapter 9: Handling Special SituationsSpecial Considerations for MRO Support......................................... 9–1

Monitoring Considerations for DFLTUSER ................................... 9–3Monitoring in a Nonsecure MRO Environment............................ 9–4Monitoring in a Secure MRO Environment................................ 9–4

Additional Monitoring Considerations ....................................... 9–5Remote FILE Support....................................................... 9–6

Using CA-InterTest for CICS with DB2 Application Programs...................... 9–6Calls to Software and User Macro Support ....................................... 9–9

How Support Is Provided ..................................................9–10Coding IN25UEX Macros for Called Software................................9–11Supporting Your Site's Global Routines......................................9–13Coding the ROUT= Routine ................................................9–14Sample JCL for Generating the IN25UEXI Programs ..........................9–16IN25UEXI Instructions for Additional Vendor Products.......................9–18

Calls for COMPUTATIONS Users.......................................9–18Calls for SHRINK Users................................................9–19Calls for Patient Care System (PCS) Users................................9–19Calls for HOGAN Users................................................9–19Calls for CICS/COMET Users .......................................... 9–19

Contents ix


Handling Wild Branches ...................................................... 9–20Monitoring a Wild Branch ................................................. 9–20Using the FOL=ON Option ................................................ 9–21

Using CA-InterTest for CICS with IBM's EXEC Debugging Facility (EDF) .......... 9–21Advantages of CA-InterTest for CICS Over EDF ............................. 9–22Using CA-InterTest for CICS with EDF ..................................... 9–22

Using CA-InterTest for CICS and HOGAN Software............................. 9–23Use Considerations ....................................................... 9–24Installation Procedure..................................................... 9–24

Chapter 10: Password Protection with CA-InterTestfor CICSRequired Parameters.......................................................... 10–2Specifying Passwords for the CORE Facility..................................... 10–3Specifying Passwords for Files and DL/I Databases.............................. 10–4Specifying Passwords for CNTL Commands and Options ........................ 10–5

Password Protected CNTL Commands ..................................... 10–6Password Protected CNTL Options......................................... 10–8

The PROT$OPT Name Option ......................................... 10–9The PROT$MNO Name Option ........................................ 10–9

Sample IN25SEC2 Assembly JCL.............................................. 10–10

Chapter 11: Automatically Starting CA-InterTest forCICSUsing the PROMMAC Macro.................................................. 11–1Entering CNTL Commands from a CRLP-type Terminal ......................... 11–4Activating CA-InterTest for CICS from a Program ............................... 11–5Starting CA-InterTest for CICS from a PLT...................................... 11–6Automatic Startup in CICSPlex Regions ........................................ 11–6

x CA-InterTest for CICS Getting Started


Chapter 12: Symbolic File MaintenanceControl Cards ................................................................12–1Examples ....................................................................12–2

Initializing the CA-InterTest for CICS Symbolic Files .........................12–3Purging Programs.........................................................12–3Deleting Symbolic Data ....................................................12–4Generating Reports and Purging Programs ..................................12–4Unloading Programs ......................................................12–5Reloading Programs.......................................................12–5Printing a Program Listing .................................................12–6Reorganizing the Symbolic File .............................................12–6

Chapter 13: TroubleshootingDiagnostic Procedures.........................................................13–1

Collecting Diagnostic Data .................................................13–3Interpreting Diagnostic Data ...............................................13–3

Accessing the Online Client Support System.....................................13–4Requirements for Using StarTCC ...........................................13–4StarTCC Security..........................................................13–5Access StarTCC ...........................................................13–5

StarTCC Introduction ..................................................13–6StarTCC Registration ..................................................13–6Accessing StarTCC ....................................................13–6Accessing the Technical Support Phone Services Directory................13–7StarTCC Hotline.......................................................13–7

CA-TLC: Total License Care ...................................................13–7Calling Technical Support .....................................................13–8Generating a Problem Report ..................................................13–9Product Releases and Maintenance ............................................13–10Requesting Enhancements ....................................................13–10

Contents xi


Chapter 14: MaintenancePL/I Option Maintenance ..................................................... 14–2CA-InterTest for CICS Maintenance ............................................ 14–2

SMP/E Libraries.......................................................... 14–2APPLY and ACCEPT Commands .......................................... 14–3The RESTORE Command ................................................. 14–4

Maintenance Delivery......................................................... 14–4Informational APAR or PML............................................... 14–4Program Temporary Fixes ................................................. 14–5

PTF Maintenance Tape Installation............................................. 14–5Overview of Maintenance Steps................................................ 14–6Step 1. Review and Follow the Cover Letter Instructions ......................... 14–6Step 2. Load the Sample JCL from the Tape..................................... 14–7Step 3. Customize the SMP Procedure.......................................... 14–8Step 4. Edit Maintenance JCL to Exclude Previously Applied SYSMODs .......... 14–8Step 5. Receive CA-InterTest for CICS Maintenance ............................ 14–10Step 6. Apply Check CA-InterTest for CICS Maintenance ....................... 14–10Step 7. Restore Any Applicable SYSMODs..................................... 14–11Step 8. Apply CA-InterTest for CICS Maintenance ............................. 14–11Step 9. Reapply Any Applicable SYSMODs.................................... 14–12Step 10. Execute CA-InterTest for CICS to Validate Maintenance ................ 14–12Step 11. Accept CA-InterTest for CICS Maintenance ............................ 14–13Step 12. Unload the Documentation Set ........................................ 14–13Step 13. Save All Materials and Output........................................ 14–13

INDEX

Introduction 1–1


Chapter

1 Introduction

CA-InterTest for CICS is a powerful interactive tool for testingand debugging CICS COBOL, PL/I, and Assembler programs.Testing and debugging is one of the most time-consuming andimportant phases of application development. The interactivetesting facilities of CA-InterTest dramatically improve testingefficiency and application quality.

CA-InterTest works online to trap all application errors knownto CICS. It lets you resolve multiple errors interactively as theyoccur, without having to recompile or end the test session.

ISPF-Like Menu Interface

A high-level ISPF-like menu interface makes it easy for bothexperienced and novice users to take advantage of the power ofCA-InterTest and navigate among its many functions. Forexample, you can:

� 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 CA-SymDump for CICS dump analysisfacility

Test and Debug Directly from Your Source Listing

1–2 CA-InterTest for CICS Getting Started


Test and Debug Directly from Your Source Listing

You can also work directly from the comfort of your familiarsource code to:

� Initiate program monitoring

� Set and remove breakpoints

� Correct problems and continue testing from any programlocation

� Single-step through the executed code path

� Change program execution with pseudocode

� Display and modify main storage

� Display and modify files and databases

You never have to wait for printouts because CA-InterTestprovides immediate, online access to your program's sourcelisting and compiler information such as maps, cross-referencetables, and messages—information your online editor cannotprovide.

Prevent Abends by Trapping All Application ErrorsOnline

As your program executes, the CA-InterTest monitor worksonline to check all statements before they are executed. Thisallows CA-InterTest to detect any application error that couldcause a program to fail or damage CICS. When an error isdetected, CA-InterTest automatically suspends programexecution before the program fails or the CICS region iscorrupted. This halt in execution is called an automatic breakpoint.When an automatic breakpoint occurs, your system is protectedand your interactive debugging can begin immediately.

Set Breakpoints to Interrupt Program Execution

Introduction 1–3


Set Breakpoints to Interrupt Program Execution

You can set breakpoints to interrupt program execution at anypoint. At each breakpoint, the source listing positioned at thebreakpoint is displayed. You can then change program variablesor data areas in main storage, set or remove other breakpoints,dynamically change the program's execution path, retrace theprogram's execution path, inspect and modify files anddatabases, abend the program, and perform many otherdebugging tasks.

CA-InterTest provides several types of breakpoint to give youmaximum flexibility in designing test scenarios:

Unconditional—The program stops whenever execution reachesa specified location.

Variable-Change—The program stops whenever the value of avariable changes.

Request—The program stops when it reaches specified CICScommands or macros, calls to DL/I and DB2, or calls tosubroutines, such as database software.

Single-Step—The program stops each time it executes aspecified number of COBOL verbs, PL/I statements, orAssembler instructions.

Control Program Execution to Test All ProgramPaths

CA-InterTest lets you completely control program execution.Not only can you stop execution at any point, you can alsoresume execution from any point. Such flexibility makes it easyto test particular program sections or circumvent an error. Youcan also write and execute pseudocode to dynamically changeyour program's execution path during testing—withoutrecompiling. By using one or more of these methods to controlprogram execution, you can be sure that all program paths havebeen tested.

CICSPlex Exploitation



CICSPlex Exploitation

CA-InterTest exploits the CICSPlex environment by monitoringa program wherever it executes in the CICSPlex. Breakpoint andother debugging information is sent to you, regardless of theregion in which the program actually executes. CA-InterTest alsosupports non-CICSPlex MRO/ISC configurations.

Ease-of-Use Features

CICS programmers can quickly benefit from the many featuresof CA-InterTest because it so easy to learn and use. Here aresome 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 listingdisplays

� A "fast path" for experienced users

� No need to worry about displacement or address changesafter recompiling because all locations can be referenced byprogram-defined names (symbolic reference).

� A comprehensive Help facility that is available from everyCA-InterTest screen and directly from CICS, which includesdetailed information about all CICS abend codes andCA-InterTest error messages.

� Demo sessions for COBOL, COBOL II, COBOL/370, PL/I,and Assembler users that demonstrate key CA-InterTestfeatures and help train new users.

Symbolic Support Facilitates Problem Solving

Introduction 1–5


Symbolic Support Facilitates Problem Solving

To speed error resolution, CA-InterTest lets you identifyprogram locations symbolically without computing addresses ordisplacements, and without worrying about address changesafter recompilation. Full symbolic support is provided, even formodules that consist of separately compiled programs link-edited together. These statically-called programs can be writtenin different languages, and each subprogram can be debugged asa separate program. CA-InterTest can also debug dynamically-called programs.

Display and Update Data Values from Your SourceListing Display

You can display and update any data values from theconvenience of the CA-InterTest source code display withouthaving to interrupt or leave your test session. CA-InterTest letsyou invoke Keep windows from the Source Listing. Thesespecialized windows display user-specified data values,registers, or storage area contents at breakpoints. You can alsouse the Keep window to automatically display the contents of alldata items on the current program statement. From within theKeep window you can easily change any of the displayed itemsby simply overtyping their contents.

View and Modify Storage/Files without Interrupting the Test Session



View and Modify Storage/Files without Interruptingthe Test Session

CA-InterTest main storage and file access facilities save time andeffort during testing. You can access these facilities, which can besecured, directly from any CA-InterTest screen. The storagefacility allows you to easily display and modify data in mainstorage by simply overtyping the displayed data, or you can usethe CA-InterTest COBOL-like MOVE statement to change thevalue of a variable when you do not know the type of data(binary, packed, and others) or its length. CA-InterTest takescare of all of the details for you.

The CA-InterTest FILE facility lets you update files or create testdata without writing one-time programs or leaving the testsession.

Authorized users can perform any I/O function provided byCICS or DL/I for accessing and updating VSAM, BDAM, andDL/I database data. The DB2 facility lets you display andupdate DB2 tables using SQL.

Structured File Display Makes Data Easy on theEyes

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

Trace Program Execution

Introduction 1–7


Trace Program Execution

The Backtrace facility lets you retrace a program's path ofexecution and understand its logic. With both statement-by-statement and block-by-block tracing capabilities, CA-InterTesthelps you answer the question, "How did I get to this point?"

Code Coverage

The Code Coverage (or COUNTS) feature lets you view thenumber of times each program statement was executed duringyour program testing. This feature makes it easy to identifyprogram statements that were or were not executed—quicklyidentifying untested code. You can accumulate programstatement counts across multiple executions of the sameprogram.

Dynamically Change Program Execution

The Indirect Commands facility lets you dynamically correcterrors for all users during a debug session. Using this facility,you can write and execute pseudocode to change the flow ofCOBOL and PL/I programs without recompiling. Indirectcommands are executed automatically at a predeterminedlocation in a monitored program.

Monitoring by CICS User ID



Monitoring by CICS User ID

You can restrict monitoring and breakpoints to a specific CICSuser ID—a capability that allows a user to switch terminals orterminal sessions and retain established monitoring options. Inaddition, user ID monitoring makes it possible to isolate a testsession from sessions of other users of the same program. Thisfunction is ideally suited to testing and debugging CICS Webapplications, or isolating and debugging a rogue productionapplication without affecting other users.

Interactively Debug Applications That Access DB2

In addition to performing SQL functions, CA-InterTest providesfacilities for testing and debugging CICS applications that accessDB2. When you are testing DB2 applications, you can even setbreakpoints based upon SQL return codes. At each breakpoint,you can symbolically display DB2 areas and perform other CICSand DB2-related debugging functions. Moreover, the DB2 returncode and its related message are available online at anybreakpoint. You can also use the CORE=LASTSQL command toview the last SQL statement that was executed while sitting at abreakpoint.

Helpful Diagnostic Information

Whenever CA-InterTest detects an error, it provides diagnosticinformation to help you find the error and determine why itoccurred. In addition, the Help facility provides context-sensitiveexplanations of each abend and suggestions on how to useCA-InterTest to correct the error. Sites can define their own userabend codes with associated problem descriptions to identify thecause of a preprogrammed abend. An abend code can beassociated with a particular program or it can override theCA-InterTest default description.

Synchronized Processing

Introduction 1–9


Synchronized Processing

To ensure that the correct version of your source code is used,CA-InterTest provides symbolic file and load modulesynchronization. When a program is selected for testing,CA-InterTest compares the date and time in the source listing tothe date and time in the load module. If no matching files arefound, CA-InterTest displays a File Selection List from whichyou can select the correct file.

Immediate Support for CICS Releases

CA-InterTest supports all current CICS releases, includingOS/390, CICS/ESA releases, and CICS/VSE releases. Immediatesupport helps MIS managers implement successful migrationprojects.

Debug Production Applications Symbolically fromAny CICS Region

Even the most thoroughly tested program can abend inproduction. CA-SymDump for CICS, an optional component ofCA-InterTest for OS/390 users, lets you debug transactionabends symbolically without having to analyze dumps.

By using CA-InterTest breakpoint facilities,CA-SymDump/System automatically pinpoints the sourcelisting statement responsible for the abend. Its powerful traceand program call facilities make it easy to determine theexecution path. The full power of CA-InterTest is available tohelp you quickly solve each problem interactively.

Debug Production Applications Symbolically from Any CICS Region



In addition, CA-SymDump for CICS gives you all of the controlof a complete dump management package. You can manage theCA-SymDump for CICS data set online by listing all dumps,selecting dumps to view, deleting dumps, and holding dumpsfor later use.

Getting Started with CA-InterTest for CICS 2–1


Chapter

2Getting Started withCA-InterTest for CICS

This guide is for OS/390 systems running under CICS Releases4.1 and above. It explains how to:

� Install:

– CA-InterTest for CICS

– the CA-InterTest PL/I option

� Implement symbolic support for these programs:

– COBOL

– Assembler

– PL/I

� Customize CA-InterTest

� Use CA-InterTest in special situations

� Apply maintenance and get support

Do not use this guide to install CA-InterTest on:

� VSE systems

� OS/390 systems running CICS releases below 4.1

Separate installation tapes and guides are available for thesesystems. For additional information, contact ComputerAssociates. Contact information is in the “Customer Support”chapter.

What You Need to Get Started



What You Need to Get Started

Computer Associates provides the following materials forinstalling and using CA-InterTest.

� A standard label magnetic cartridge or standard labelmagnetic tape recorded at 6250 BPI (DCB=DEN=4)containing the CA-InterTest product. The Volume Serialnumber is BAyymm. The tape contents are:

1. DSN=CAI.SAMPJCL (File number 9): This is anunloaded PDS containing all of the sample JCL referredto in this document that pertains to the installation andexecution of CA-InterTest. Load using IEBCOPY.

2. DSN=SMPMCS (File number 32): This file contains theSMP modification control statements (MCS) used bySMP to install CA-InterTest.

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

� Comprehensive documentation that explains how to use,install, customize, and maintain CA-InterTest.

Tape Contents andFormat

The machine-readable program materials required forinstallation are distributed as a multifile installation tape inSMP format. This tape contains all of the necessary data toinstall and execute CA-InterTest.

Distribution tapes contain pregenerated versions ofCA-InterTest. The pregenerated versions use all of the defaultinstallation options. If you think you need to customize theproduct for a particular need, see the chapters on “ModifyingCA-InterTest for CICS Options” and “Additional CA-InterTestfor CICS Customization Procedures.”

Use the IBM-supplied System Modification Program/Extended(SMP/E) to install, customize, and maintain CA-InterTest. Thisprogram lets you control these activities in a consistent manner.

Summary of Changes for This Release



Summary of Changes for This Release

CA-InterTest Release 6.0 includes the following new features.

Year 2000 Support CA-InterTest is fully Year 2000 compliant.

CICS TS 1.3Enhancements

The Request Breakpoint screens have been modified to allowrequest breakpoints to be specified for the new CICS commandsprovided for the Web Interface, Business Transaction Services,and the 3270 Bridge. Commands and modules that aredependent on the DB2 RCT control block have been modified tosupport the removal of the DB2 RCT and to use the new EXECCICS INQUIRE DB2 commands. The Auxiliary Storage Displayand Modify features have been modified to support both theeight and sixteen byte Temporary Storage Queue names.

AutoKeep The AutoKeep feature allows you to request that the contents ofall program variables or data-names references in the activestatement of a program be automatically displayed whendebugging a program. AutoKeep is implemented using a SourceListing Profile option. The default for the AutoKeep SourceListing Profile is controlled by a product installation parameter.AutoKeep can be turned on for all programs as a company-wideor CICS region default.

While the new AutoKeep and Code Coverage (see below)features will run with existing programs, the post-processor hasbeen enhanced for these features and it is recommended thatprograms wishing to use them be recompiled.

Keep WindowModified

The Keep window is scrollable to allow you to view more thansix Keep table entries.

PL/I Arrays You can display complex PL/I arrays. You must recompile allPL/I programs with arrays using the 6.0 version of IN25SYMP.

Source CodeCoverage

This new feature appears on the Source Listing Display menuand allows you to view which program statements have beenexecuted and how many times. This feature is controlled by anew user-specified command.

Release Notes for Existing Users



Additional Commandsto Find and LocateStrings in SourceProgram Listing

Version 6.0 supports the following new commands that youspecify on the command line to locate parts of a listing or findstrings within the listing: FIND, LOCATE, TOP, BOTTOM, CS,FS, FO, FP, GO,NEXT, RUN, and AUTOSTEP. This enhancementallows you to use the same command syntax to navigate throughthe CA-InterTest Source Program Listings that you use in aSource Program Editor or Browser Utility.


CA-InterTest Version 6.0 contains new features for debuggingCICS application programs. This version contains a newPrimary Options menu and menu interface that was designed toaid both new and experienced users. Using the new menuinterface is optional, for details, see the chapter “Menus andDisplays” in the CA-InterTest for CICS User Guide.

Starting a Test Session

From CICS, enter ITST to use the new Primary Option menu orenter LIST=progname to display your Source Listing and begin atest session. Both access methods let you perform anyCA-InterTest function.

Note: Do not start a session from the CNTL menu, CORE, orFILE facility for accessing your Source listing. Instead, typeLIST=progname or use ITST option 1 (Source selection frommenus).

Source Listing Facility Features

The Source Listing facility provides new, user-friendly featuresto take advantage of the new menu interface and a newmonitoring option:




� A new USER ID field has been added to the PROFILE screento limit monitoring to a specific user ID. For details onmonitoring by user ID, see ITST Option 8: What’s New forThis Release, or the “Monitoring Menu Options” chapter inthe CA-InterTest for CICS User Guide. The default formonitoring by user ID is set using an installation option.

� A command line is always available for navigating toanother facility by entering the transaction ID (ITST, FILE,CORE, or CNTL). You can also use the command line tojump directly to an ITST or breakpoint menu option (=n.n.n)or to enter a long form CORE or CNTL command.

� To abend a task, enter the ABEND command.

� New commands are supported from the Source Listingfacility. The supported commands vary by breakpointstatus. To access this list from online help, do the following:

1. Display a program using ITST Option 1 orLIST=progname

2. Press PF1 Help

3. Select 32 Line Commands from the Help menu

New Monitoring Menus and Status Display

Option 2 of the ITST Primary Option menu displays a newMonitoring menu designed to replace the use of the CNTLMonitoring Command Builder menu. Try it.

The new Monitoring Status display—available from ITST option2.4 or by typing STATUS or STATUS ALL on a Source Listingcommand line—allows you to easily view and removemonitoring options. Simply type an R next to the option to beremoved.




CNTL Menus

The CNTL menus are integrated with the new ITST Option 2monitoring menus. However, the CNTL transaction is stillavailable for existing users and accesses the CNTL MonitoringCommand Builder menu. Regardless of access path, the CNTLmenus remain essentially unchanged, with the followingexceptions:

� A new USER ID field to limit monitoring to a specific userID

� Removal of many PF key assignments, which affects yourtest session navigation

Because many PF keys were removed, the CNTL menus cannotbe used as the access path to other CA-InterTest functions. Useeither the ITST menu options or the new Source Listingcommands to access other CA-InterTest facilities.

New Breakpoint Menu (PF 6 Menu)

A new PF key assignment, PF6 menu, provides immediate accessto a new Breakpoint menu from any CA-InterTest breakpoint.The breakpoint menu lets you access the Primary Option menu(Option 1) and perform any of the following breakpointfunctions:

2. View and remove monitoring options of breakpointedprogram (Status Display)

3. Abend the task

4. Resume task execution (several options)

5. Override an error

6. Produce a dump and resume execution

7. Disconnect from the breakpoint

Major SMP Operations



You can select breakpoint menu options directly from anybreakpoint display by entering the fast path notation (=n.n) inthe command line and pressing Enter. For example, users whofrequently select the Override PF key from the DetailedBreakpoint display can now override from the Source ListingBreakpoint using command entry =5 and pressing Enter.

Major SMP Operations

SMP performs three major operations when installing a productor performing maintenance. These operations manage astructure where a product is present in two places: distributionlibraries and target system libraries. The distribution librariesare used for maintenance operations only. The product executesfrom the target system libraries.

The operations performed are:

� RECEIVE Processing

SMP loads the installation tape into temporary data sets. Ifany error is detected or you want to stop the process at thispoint, you can run a REJECT operation, which undoesanything done during RECEIVE processing.

� APPLY Processing

During APPLY processing, SMP performs the operationsdictated by the modification control statements (MCS) andupdates the target system libraries. You can then test themodification. If the installation is to be terminated at thispoint, you can run a RESTORE operation, which restores thesystem libraries from the distribution libraries.

� ACCEPT Processing

Running the ACCEPT operation permanently places themodification in the distribution libraries. There is no directway to undo the modification once the ACCEPT process hasbeen run.

System Requirements 3–1


Chapter

3 System Requirements

This chapter helps you prepare for installation by listing thehardware and software components needed to install andoperate CA-InterTest for CICS and by discussing cross-productconsiderations.

Topics discussed include:

� Operating environments

� Unicenter TNG Framework for OS/390 Common Services

� Hardware requirements for distribution and target libraries

� Special considerations

� Migration considerations

Operating Environments

The pregenerated versions provided on this tape support anyMVS/ESA operating system running on any hardware withCICS Release 4.1 or above. This tape includes pregeneratedversions of CA-InterTest for:

� CICS 4.1

� CICS TS 1.2 and 1.3

Unicenter TNG Framework for OS/390 Common Services Requirements



Database management systems DL/I, DB2, and ADABAS arefully supported by the pregenerated versions withoutmodification. If you need to support other systems (such asTOTAL, CA-IDMS or CA-Datacom) or calls to software thatshould not be monitored by CA-InterTest, see the “HandlingSpecial Situations” chapter.

Unicenter TNG Framework for OS/390 CommonServices Requirements

CA-InterTest requires the following Unicenter TNG Frameworkfor OS/390 Common Services:

� CAIRIM

� CA LMP

CA-InterTest support for CICSPlex requires the followingadditional Unicenter TNG Framework for OS/390 CommonService: CAICCI for MVS.

These Unicenter TNG Framework for OS/390 Common Servicesmust be installed or maintained at the genlevel indicated on thecover letter for the product. If you have other CA productsinstalled at your site, some of these services may already beinstalled. If these Unicenter TNG Framework for OS/390Common Services have not been installed already on yoursystem, you must do so before proceeding with this installation.

Refer to the Unicenter TNG Framework for OS/390 GettingStarted guide for more information about Unicenter TNGFramework for OS/390 Common Services and for detailedinstallation instructions.




CAIRIM

CAIRIM, CAI Resource Initialization Manager, is the commondriver for a collection of dynamic initialization routines thateliminate the need for user SVCs, SMF exits, subsystems, andother installation requirements commonly encountered wheninstalling systems software. Some of the features of CAIRIM are:

� Obtaining SMF data

� Verification of proper software installation

� Installation of MVS interfaces

� Automatic startup of Computer Associates and other vendorproducts

� Proper timing and order of initialization

CAIRIM is required to run CA LMP.

CA LMP

The CA License Management Program provides a standardizedand automated approach to the tracking of licensed software. Ituses common realtime enforcement software to validate theuser‘s configuration. CA LMP reports on activities related to thelicense, usage, and financials of program solutions. CA LMPfeatures include:

� A common Key Data Set that can be shared among manyCPUs

� Using check digits to detect errors in transcribing keyinformation

� Execution Keys can be entered without affecting any CAsoftware solution already running

� No special maintenance requirements

CA LMP is required to run CA-InterTest.




CAICCI

CA-InterTest installations that do not require CICSPlex supportdo not need to install CAICCI. However, if you plan to useCA-InterTest support for CICSPlex environments, CAICCI forMVS is required. For CICSPlex support, CAICCI must beinstalled in each MVS/CICS region that is a CICSPlex familymember.

CAICCI (CAI Common Communications Interface) enablesComputer Associates products to communicate with oneanother. This facility provides a layer that isolates applicationsoftware from the specifics of the communications environment.

CAICCI is a started task used for sending messages betweenComputer Associates products. It usually runs continuouslywhenever the operating system is active.

CA-InterTest uses CAICCI to facilitate testing and debugging inCICSPlex environments. In particular, it uses CAICCI to sendand receive the monitoring commands to and from the CICSPlexfamily member CICS regions. This automatically propagatesmonitoring activity to all regions participating in the CICSPlexenvironment.

CA-Hardware Requirements



CA-Hardware Requirements

Estimates for the amount of disk space needed to installCA-InterTest follow.

Distribution Libraries

The following table estimates disk space for the distributionlibraries required to install CA-InterTest.

Name Blksize Blocks Dir. Blks. Description

CAI.CBA6041D 6144 600 50 Load modules CICS 4.1

CAI.CBA6052D 6144 600 50 Load modules CICS TS 1.2

CAI.CBA6053D 6144 600 50 Load modules CICS TS 1.3

CAI.CBA60SLD 3120 250 30 Sample source and JCL

Special Considerations



Target Libraries

The following table estimates disk space for the target librariesrequired to install CA-InterTest. These libraries must beallocated if they do not already exist for some other ComputerAssociates product at your site.

Name Blksize Blocks Dir. Blks. Description

CAI.SAMPLIB 3120 250 30 Sample source library

CAI.CACICS41 6144 600 50 CICS 4.1 load library

CAI.CACICS52 6144 600 50 CICS TS 1.2 load library

CAI.CACICS53 6144 600 50 CICS TS 1.3 load library

CAI.PROTHLF 4096(CI) 1000 N/A Help file (VSAM)

CAI.PROTUHF 4096(CI) 1000 N/A User-defined help file forabend codes (VSAM)

CAI.PROTSYM 2048(CI) 4500 N/A Symbolic file (VSAM)

CAI.PROTCPF 4096(CI) 5 N/A Checkpoint file (VSAM)


Additional considerations apply under the circumstancesdescribed next.

PL/I Programs

PL/I programs that contain arrays must be recompiled with theIN25SYMP post-processor provided with version 6.0 if thesupport for complex arrays is to be available.




Global User Exits

This CA-InterTest release requires the use of the following globaluser exits:

� XPCFTCH and XPCTA

Required for the CNTL=START and CNTL=END commandsto operate CA-InterTest and control monitoring.

� XDUREQ

Required for dump suppression.

� XMEOUT

Required for suppression of abend messages.

When monitoring programs observe the following rules:

� You must not disable the above global user exits in any wayor CA-InterTest will stop functioning.

� The CA-InterTest global user exits will honor the returncodes set by previous exits, which may have an impact onwhether CA-InterTest successfully monitors a program. Ifyou are having problems caused by other CICS global userexits setting a return code before CA-InterTest exits receivecontrol, you can guarantee that the CA-InterTest exits arefirst to receive control by adding the program entryIN25PLTX to the CICS startup PLT. IN25PLTX is requiredas the first program entry in Phase 1 (prior to theDFHDELIM entry) of the PLT.

� If other exits receive control after CA-InterTest, they mustnot change the return code or entry point fields in the userexit parameter list.

� To disable CA-InterTest you must use the CNTL=ENDcommand.

Failure to observe the above rules will disable monitoring. Forexample, CA-InterTest monitoring is not performed if anotherexit receives control before CA-InterTest and passes on amodified return code or entry point.




TIOA Compression Routine Users

CA-InterTest transactions and programs must be excluded fromany TIOA compression packages or routines, such as 3270 SuperOptimizer/CICS and CTOP. Failure to do so will produceunpredictable results because CA-InterTest uses saved TIOAs.In addition, the CA-InterTest FILE facility may not workproperly with data files that have been put through datacompression routines.

CICSPlex Support

CA-InterTest provides special, optional support for CICS regionsparticipating in a CICSPlex environment. If CA-InterTest isinstalled with CICSPlex support, participating CICS regionshave CA-InterTest commands and breakpoints automaticallypropagated to all regions in the CICSPlex. This allows for easierdebugging of dynamically routed transactions and programs.For details on which commands are propagated across aCICSPlex, refer to the CA-InterTest for CICS User Guide.

Installation Requirements for CICSPlex Support

CICSPlex command propagation is accomplished mainlythrough the services of CAICCI for MVS, a Unicenter TNGFramework for OS/390 Common Service. Other than installingCAICCI for MVS and setting a few customization options, aslisted below, there is nothing else needed to obtain CICSPlexsupport.

To install CA-InterTest with CICSPlex support, you need toperform these steps:

1. Install CAICCI in all participating CICSPlex regions asdiscussed in the section Unicenter TNG Framework forOS/390 Common Services Requirements.

2. Follow normal installation instructions for the product, asdiscussed in the chapter “Base Product Installation Steps.”




3. Use the following IN25OPTS customization options in eachparticipating CICSPlex region:

� CICSPLEX=YES

� CPLXFMID=a-CICSPlex-family-name

� CPLXCKPI=hhmm (a checkpoint interval)

For details on setting these options, see the chapter“Modifying CA-InterTest for CICS Options.”

Note: Support for multiple CICSPlex families within oracross multiple MVS regions can be obtained by changingthe CPLXFMID family name associated with each region.

Startup and Termination with CICSPlex Support

CA-InterTest regions installed with CICSPLEX=YES are affectedduring startup and termination in the following ways:

� The CNTL=START and CNTL=RESTART commandsautomatically have CA-InterTest resynchronize monitoringwith any active regions in the CICSPlex upon startup

� The CNTL=END, SCOPE=GLOBAL command can be issuedto concurrently terminate all CA-InterTest processing in allconnected regions in the CICSPlex

CA-ACF2 and RACF Users

For CA-ACF2 Users To use CA-InterTest with CA-ACF2, add the transactions IPLX,VTAT, LIST, and VIRC to your ACF2 SAFELIST.

For additional information on these CA-InterTest transactions,see the chapter “Modifying CA-InterTest Options.” Forinstructions on adding transactions to the SAFELIST, see theCA-ACF2 for OS/390 CICS Support Guide.




For RACF Users To use CA-InterTest with RACF, the CA-InterTest transactionsIPLX, ISER, VIRC, LIST, and VTAT must be defined to CICSwith CMDSEC(NO) and RESSEC(NO). All CA-InterTesttransactions and programs require UACC(READ) for EXECCICS INQUIRE commands to give all users RACF READaccess. Without these settings, the symbolics for a sourcelisting breakpoint display may not be available to users.

If RACF file level security is in use, you must also add thefollowing statements to the xCICSFCT resource class:

PROTSYM, PROTHLF ...UACC(READ)PROTCPF, PROTUHF ...UACC(UPDATE)

CA-Realia II Workbench For OS/390 CICS Users

This version provides full support for the CA-Realia IIWorkbench For OS/390 CICS. Refer to the CA-Realia IIWorkbench For OS/390 CICS User Guide for instructions onusing the WH= parameter with the appropriate COBOLpost-processor.

Database Support

Database management systems DL/I, DB2, and ADABAS arefully supported by the pregenerated versions withoutmodification. If you need to support other systems (such asCA-IDMS, CA-Datacom, or TOTAL) or calls to software thatshould not be monitored by CA-InterTest, see the chapter“Handling Special Situations.”

HOGAN Users

If you want CA-InterTest to support HOGAN, see the chapter“Handling Special Situations” for detailed instructions.




MRO Users

If you want CA-InterTest to support MRO, see the chapter“Handling Special Situations” for detailed instructions.

Omegamon Users

To use CA-InterTest with Omegamon Version 450 or subsequentversions:

� You must start Omegamon before you start CA-InterTest.

� If you are starting Omegamon with the PLT, you must addthe Omegamon program EISET to the list of PLT programs.

TMON Users

To use CA-InterTest with TMON, CA-InterTest transactionsmust 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 thechapter “Handling Special Situations.”

CA-InterTest 6.0 Migration Considerations




Pre-existingCA-InterTestCustomization

If you have customized CA-InterTest (IN25OPTS, IN25LETX,IN25UCOM, IN25UEXI) make sure you redo the modificationsafter CA-InterTest is installed.

Symbolic FileConsiderations

If the IDCAMS SHAREOPTIONS parameter of your existingPROTSYM file is SHR(3 3), you must create a new PROTSYMfile using SHR(4 4). You can use the data that resides in theoriginal PROTSYM file to create the new PROTSYM file (seethe chapter “Symbolic File Maintenance”).

The Symbolic Files from this release are downward compatiblewith Version 5.4. The Symbolic Files from Version 5.4 areupward compatible with this release. However, if you have PL/Iprograms that contain arrays, you must recompile thoseprograms to use the new complex array support provided inVersion 6.0. In addition, while the new AUTOKEEP and CodeCoverage features will run with existing programs, thepost-processor has been enhanced for these features and it isrecommended that you recompile the programs with which youwant to use these features.

Automatic Startup If you start CA-InterTest using a predefined PROM table(assembled PROMMAC macros) or the EXEC= option of theCNTL=START command, you may want to add the USR=option to any embedded CNTL=ON... commands to assign theentries to a specific user ID.

CA-Optimizer/IIOptions

This release supports the CA-Optimizer/II EOS and MMAPoptions.

IN25CAPX Alias The IN25CAPX alias for IN25COB2 is not available in thisrelease. If you have pre-existing JCL that references programIN25CAPX, you must change the JCL to reference IN25COB2.

High Level AssemblerSupport

This release supports High Level Assembler.




COBOL/370, IBMCOBOL for MVS, IBMCOBOL for OS/390

The IN25COB2 post-compiler supports COBOL/370, IBMCOBOL for MVS, and the IBM COBOL for OS/390 compilers.

IN25PLTX SourceCodes

Source code for IN25PLTX programs is no longer shipped. Ifyou need to invoke any of the IN25PLTX programs, see thesection ”Starting CA-InterTest for CICS from a PLT “.

CICS ProgramDefinitionRequirements

This release requires a number of new CA-InterTest programs.The resource definitions from previous releases will not workproperly with this release.

UpperCase Option If you require the uppercase version of CA-InterTest for CICS,you no longer have to specify a different FMID during the SMPRECEIVE, APPLY, and ACCEPT processes. Support for theuppercase version is now controlled by the new IN25OPTSUCONLY=YES parameter.

3270 LowercaseTerminals

When processing CA-InterTest breakpoints, 3270 lowercaseterminal input will automatically be translated touppercaseCA-. This eliminates manual translation ofCA-InterTest commands from lowercase to uppercase and theneed for special terminal definitions.

Global User Exits The XDUREQ, XMEOUT, XPCFTCH, and XPCTA Global UserExits now honor return codes set by previously executed exits.If a previously executed exit sets a nonzero return code,CA-InterTest will honor the return code and not monitor theaffected program. If a previously executed exit sets the returncodes to zeros and you decide to monitor, CA-InterTestoverrides the previous return code and begins programmonitoring.

CICS USERID The CICS USERID is now written to the CA-InterTest log whenthe monitoring environment, a CICS file, or a CICS storage areais modified. This provides improved auditing information.

Dynamically CalledPrograms

COBOL II, COBOL/370, IBM COBOL for MVS, or IBM COBOLfor OS/390 dynamically called programs can now bemonitored without monitoring all programs that precede thedynamic call.

CA-InterTest 4.x to 6.0 Migration Considerations



CICS/COMET Support Support is provided for both mixed- and macro-level programscontrolled by Technologic Software's CICS/COMET.

IN25UEXI Pregenerated IN25UEXI is provided for CA-IDMS,CA-Datacom, CA-Telon, CA-Sort, CA-Masterpiece,CA-InfoPoint, DB2, and MQSERIES, CICSPlex/SM, andTCP/IP Sockets Interface.

CA-ACF2 and RACF Additional transactions must be granted unrestricted security.See the section “CA-ACF2 and RACF Users” for details.


If you are migrating from a CA-InterTest 4.x version toCA-InterTest Version 6.0, you may have some additionalconsiderations, which are discussed next.

CICS/ESA Support CA-InterTest Version 6.0 supports CICS/ESA 4.1 and abovesystems only, and will not function properly if installed on aCICS/ESA 3.3 or below system. CICS/ESA 4.1 and abovesupport includes support for the Transaction Isolation feature.

Object CodeDistribution andMaintenance

CA-InterTest Version 6.0 programs are not shipped in sourcecode format. The contents of the distribution tape arediscussed in the installation chapter. Procedures for objectcode maintenance are in the maintenance chapter.

IN25PLT StartupChanges

The IN25PLT program starts CA-InterTest after PLT processingis complete. Before Version 5.1, the program startedCA-InterTest during PLT processing.

IN25OPTS MacroChanges

The IN25OPTS macro differs from the IN25OPTS macro inVersions 4.x. New parameters have been added to supportvarious new features of CA-InterTest. Additionally, theCWALET parameter no longer supports the following formatfor CWA data: X‘base(displacement)‘. See the chapter“Modifying CA-InterTest for CICS Options” for moreinformation.




IN25LETX Exit Changes The IN25LETX exit interface has been modified to a command-level exit. If you have an IN25LETX exit from a CA-InterTestrelease prior to 5.0, you must re-write the IN25LETX exit. Seethe chapter “Additional CA-InterTest for CICSCustomization Procedures” for details.

IN25UEXI MacroChanges

The IN25UEXI macro has been modified. The parameterCWAD no longer supports the CWA global exit format:X‘base(displacement)‘. See the chapter “Handling SpecialSituations” for information.

CICS/ESA DPLSupport

Program monitoring using CICS/ESA Distributed ProgramLink (DPL) is supported when the remote program executes asa DPLSUBSET on the local region or when the DPL programexecutes on a remote region as a nonterminal transaction.

CICS/ESA StorageProtection

The CICS/ESA Storage Protection feature is supported. Inaddition, CA-InterTest continues to provide storage protectionon a task level.

Remote File Support Remote file support for the CA-InterTest FILE transaction isavailable in CA-InterTest Version 4.2 and above. This featureonly works if the CA-InterTest version executing on the remoteCICS system is Version 4.2 or above. See the chapter“Handling Special Situations” for details.

DB2 Support Special IN25UEXI macros are supplied for DB2 support inCA-InterTest Versions 4.2 and above. See the chapter“Handling Special Situations” for details.

HOGAN Support Support for monitoring HOGAN applications in Versions 5.xand above is handled differently from previous releases. Seethe chapter “Handling Special Situations” for details.

Global User ExitRequirement

CA-InterTest requires the use of the global user exits to operateand monitor programs.

LPA Restriction Lifted The CICS program control module (DFHPCP) can now residein the LPA. Earlier CA-InterTest releases required that theDFHPCP reside outside the LPA.

Base Product Installation Steps 4–1


Chapter

4Base Product InstallationSteps

CA-InterTest for CICS is installed using SMP/E. The installationprocess consists of:

� Installing required Unicenter TNG Framework for OS/390Common Services

� Entering CA-InterTest 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

� Installing DB2 support (optional)

� Executing the Check-out Program

� Installing PL/I support (optional)

WARNING! Install the required Unicenter TNG Framework forOS/390 Common Services components before proceedingwith an SMP/E installation of CA-InterTest.

Summary of Installation Steps



Summary of Installation Steps

Note: CA-InterTest for CICS and CA-SymDump for CICS sharecommon components. The release and maintenance level of thetwo products must be equivalent. If your site has previouslyinstalled CA-SymDump as a separate product, the followingprocedures must install CA-InterTest 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 isleft completely up to you.

The following list summarizes the steps involved in theCA-InterTest installation process. Review this list beforeinstalling CA-InterTest, and then use it as a checklist during theactual installation.

1. Review CA-InterTest system requirements. Be sure all of therequirements are met before installing CA-InterTest.

2. Enter the LMP codes for the CA-InterTest product.

3. Complete the CA-InterTest Installation Worksheet. Modifythe default values that do not meet your data center‘sstandards. Use the worksheet as a guide when modifyingthe installation JCL.

4. Load the sample installation JCL from the tape.

5. Allocate target and distribution libraries using memberBA60ALC JCL.

6. If this is your first or only Computer Associates product,define the CA SMP data sets using sample JCL memberBAINITE for SMP/E Release 1.4 or member BAINITE5 forSMP/E Release 1.5 or higher. Also, define SMP zones usingBA60INIT.

7. Customize the SMP JCL procedures using the BA60SMPEmember.

8. Execute an SMP RECEIVE function using the BA60REC JCLmember.

9. Execute an SMP APPLY function using the BA60APP JCLmember.

Step 1. Review System Requirements



10. Execute an SMP ACCEPT function using JCL memberBA60ACC.

11. Install the Help facility.

11a.Create the help file for user-defined abend descriptions(optional).

12. Create the Symbolic File.

13. Create the Checkpoint File.

14. Add the CICS table entries.

15. Update the CICS startup JCL.

16. Install DB2 support (optional).

17. Restart CICS and run the check-out program.

18. Install PL/I support, if licensed for this option. See thechapter “PL/I Option Installation Steps” for details.

19. Unload the documentation set.

After installing CA-InterTest (and the PL/I option if you arelicensed for it), adjust the compile and assemble procedures forCOBOL, COBOL II and higher, Assembler, and PL/I programsso that CA-InterTest can obtain symbolic information.

Existing users should begin by reviewing ITST Option 8 “What’sNew.” New users should begin by using the demo programsbefore using CA-InterTest on their own programs.

Step 1. Review System Requirements

Be sure that your system meets all of the requirements given inthe “System Requirements” chapter before installingCA-InterTest.

Step 2. Enter LMP Product Key Certificate Information



Step 2. Enter LMP Product Key CertificateInformation

You must enter the LMP Key Information for CA-InterTest. Ifyou purchased the PL/I Symbolic Facility and CA-SymDumpfor CICS options, you also need to enter the LMP KeyInformation for these options.

Using CA LMPCA-InterTest requires CA LMP (License Management Program),one of the Unicenter TNG Framework for OS/390 CommonServices, to initialize correctly. CA LMP also provides astandardized and automated approach to the tracking oflicensed software.

Examine the CA LMP Key Certificate you received with yourCA-InterTest installation or maintenance tape. The certificateprovides an LMP key for the CA-InterTest base product and, ifyou have purchased the PL/I Symbolic Option orCA-SymDump for CICS, an additional key for each optionpurchased.

The certificate contains the fields shown in the following table.




Fields Descriptions

Product Name The trademarked or registered name of theCA-InterTest licensed for the designated siteand CPUs.

Supplement The reference number of your license forCA-InterTest in the format nnnnnn nnn.This format differs slightly inside andoutside North America and may not beprovided in some cases.

Expiration Date The date your license expires in the formatMONTH dd, yyyy (as in OCTOBER 21,2001).

Technical Contact The name of the technical contact at your sitewho is responsible for the installation andmaintenance of CA-InterTest. This is theperson to whom CA addresses all CA LMPcorrespondence.

MIS Director The name of the Director of MIS or theperson who performs that function. If thetitle, but not the individual‘s name, isindicated on the Certificate, supply theactual name when correcting and verifyingthe Certificate.

CPU Location The address of the building where the CPUis installed.

Execution Key An encrypted code required by CA LMP forCA-InterTest initialization. Duringinstallation, it is referred to as the LMPCode.

Product Code A two-character code that corresponds toCA-InterTest.

CPU ID The code that identifies the specific CPU onwhich this installation of CA-InterTest isvalid.




CA LMP is provided as an integral part of CAIRIM (ResourceInitialization Manager), one of the Unicenter TNG Frameworkfor OS/390 Common Services. Once CAIRIM has been installedor maintained as specified in the cover letter for this productrelease, CA LMP support is available for all CA LMP-supportedsoftware solutions.

The CA LMP execution key, provided on the Key Certificate,must be added to the CAIRIM parameters to ensure properinitialization of the Computer Associates software solution. Todefine a CA LMP execution key to the CAIRIM parameters,modify member KEYS in OPTLIB data set. The parameterstructure 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 codealready in use by the CAIRIM initializationparameters for earlier genlevels ofCA-InterTest.

ddmmmyy The CA LMP licensing agreementexpiration date.

tttt-mmmm Required. The CPU type and model (forexample: 3090-600) on which the CA LMPsoftware solution is to run.

If the CPU type or model requires less thanfour characters, blank spaces are insertedfor the unused characters.

ssssss Required. The serial number of the CPU onwhich the CA LMP software solution is torun.

kkkkkkkkkkkkk Required. The execution key needed to runthe CA LMP software solution. This CALMP execution key is provided on the KeyCertificate shipped with each CA LMPsoftware solution.

Step 3. Complete the Installation Worksheet



An example of a control card for the CA LMP execution softwareparameter is shown next. In this example, the CA LMP executionkey value is invalid and provided as an example only.

PROD(BA) DATE(01JAN94) CPU(3090-600 /370623)LMPCODE(52H2K06130Z7RZD6)

For a full description of the procedure for defining the CA LMPexecution key to the CAIRIM parameters, see the Unicenter TNGFramework for OS/390 Common Services Getting Started

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

If you purchased the PL/I Symbolic Facility or theCA-SymDump for CICS option, you received an additionalExecution Key for each option you purchased. To define theseCA LMP execution keys to the CAIRIM parameters, modifymember KEYS in the OPTLIB data set (see the section, Using CALMP, for instructions).


The installation worksheet, shown next, simplifies the task oftailoring the supplied JCL. Answer each question on theworksheet, filling in the blanks with the appropriateinformation. Default values are noted, so if the default value isacceptable, leave the item blank on the worksheet. However,you must supply appropriate volume serial numbers. Theworksheet items are listed in the approximate order in whichyou encounter them during the installation.

1. What is your installation generic unit name for temporarywork DASD?

Default: WORK=SYSDA WORK=_____________




2. What is your installation’s generic unit name for the shippedinstallation tape?

Default: TAPE=TAPE TAPE=______________

3. What is your installation standard SYSOUT class forComputer Associate product installationss and SMP output?

Default: SYSOUT=* SYSOUT=___________

4. What is the dsname high-level qualifier for the CA-InterTestinstallation libraries (both target and distribution libraries)?

Default: CAI=CAI. CAI=_______________

a. What VOL=SER do you want to use for the targetlibraries?

Default: TARGET= TARGET=___________

b. What VOL=SER do you want to use for the distributionlibraries?

Default: DLIB= DLIB=______________

c. What is your installation generic unit name for the abovelibrary volumes?

Default: PUNIT=SYSDA PUNIT=____________

5. What is the dsname high-level qualifier for the SMP librariesto be used for the installation of Computer Associateproducts?

Default: CAISMP=CAI. CAISMP=___________

a. What VOL=SER do you want for the SMP libraries, ifthese libraries do not already exist?

Default: VOLSER= VOLSER=___________

b. What is your installation generic unit name for thepermanent DASD SMP volumes?

Default: PERMDA=SYSDA PERMDA=__________

6. What VOL=SER do you want for the SMP temporarylibraries?

TLIB=______________

Step 4. Load Installation Sample JCL Library



Step 4. Load Installation Sample JCL Library

The CA-InterTest product installs using SMP/E. The producttape received with this package contains all of the necessary datato install and execute CA-InterTest. Before installing theproduct, load the sample JCL library from the tape. This file,DSN=CAI.SAMPJCL, is the ninth file on the tape and is inIEBCOPY unloaded format. Use the following JCL as a model toload the sample JCL library to DASD.

//LOAD EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=A//SYSUT1DD DISP=(OLD,KEEP),// DSN=CAI.SAMPJCL,// UNIT=CART, <=== generic 3480 tape cartridge// VOL=SER=BAyymm, <=== tape label// LABEL=(9,SL)//SYSUT2DD DISP=(NEW,CATLG,DELETE),// DSN=CAI.INTERTST.SAMPJCL, <=== your DSN// UNIT=SYSDA, <=== your generic DASD// VOL=SER=XXXXXX, <=== permanent DASD volser// SPACE=(3120,(40,20,10)), <=== minimum space required// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//SYSUT3DD UNIT=SYSDA,// SPACE=(TRK,(5,5))//SYSUT4DD UNIT=SYSDA,// SPACE=(TRK,(5,5))//SYSIN DD DUMMY

Once this job has ended, your library will contain all of the JCLneeded to complete the installation of CA-InterTest.

To satisfy your data center‘s needs, certain tailoring of the JCL isnecessary while executing the steps on the following pages.Refer to the Installation Worksheet you completed earlier in thischapter to obtain values for the various JCL parameters.

Step 5. Allocate Target and Distribution Libraries



Step 5. Allocate Target and Distribution Libraries

Note: If your site has previously installed CA-SymDump forCICS as a separate product, skip this step.

Member BA60ALC allocates all of the target and distributionlibraries required by CA-InterTest during installation andmaintenance. However, many Computer Associates productshave common components and libraries that may already havebeen installed. Therefore, carefully analyze the installation stepsto ensure that completed steps are not repeated.

Edit the JCL to conform to your installation standards and thepreviously completed worksheet. However, never change any ofthe ddnames or the last qualifier of the data set names.

All space allocations supplied in this member are in blocks toallow for compatibility between DASD types. The allocationsgiven are the minimum required for installing CA-InterTest.You may want to adjust these for your installation device types,and to allow enough free space for maintenance (the more freespace you allocate, the less often the libraries will be compressedduring maintenance). For common libraries that are alreadypresent, be sure there is sufficient space for CA-InterTest.

Submit member BA60ALC and review the output.

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

Important! If you have already created SMP data sets during theinstallation of another Computer Associates product, skip this task andgo 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 Computer Associates baseSMP libraries and defines additional product target anddistribution zones.

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



Task 1. Allocate and Initialize Computer Associates Base SMPLibraries

This step is not required if SMP data sets have been createdalready during the installation of another Computer Associatesproduct.

Use member BAINITE or BAINITE5 to allocate and initialize aset of private SMP data sets for all Computer Associatesproducts.

� Use member BAINITE if you are using SMP/E Release 1.4 orlower

� Use BAINITE5 if you are using SMP/E Release 1.5 or higher

We recommend that you keep Computer Associates products asdistinct entities from other SMP data sets. These members alsoset up CAI global, target, and distribution zones for ComputerAssociates products.

To find out which release of SMP/E you are running, execute thefollowing JCL.

//jobname JOB acnt,pgmr//SMP EXEC PGM=GIMSMP,REGION=4M//SMPOUTDD SYSOUT=*

This JOB produces condition code 16 and a short status report.The report shows the SMP level in both the title line and thetermination message. The release is the second digit of the level(for example, LVL 15.11 indicates Version 1, Release 5,Modification level 11).

Task 2. Define Additional Product Target and Distribution Zones

Next, use member BA60INIT to define additional SMP zones fora set of target and distribution libraries for CICS 4.1, CTS 1.2, orCTS 1.3.

Step 7. Customize the SMP Procedure




Edit the procedure to conform to the installation standards andspecifications you entered on the installation worksheet. Thisprocedure can be placed into a system or user procedure libraryor executed instream. The procedure is used in the followingSMP RECEIVE, APPLY, and ACCEPT steps.

Note: There is a model JCL procedure called BA60SMPE in thesample JCL library.

Step 8. Receive the CA-InterTest for CICS Product

Member BA60REC receives all of the components (functionalSYSMODs) of CA-InterTest and executes the procedure edited inStep 7, Customize the SMP Procedure.

Note: If your site has previously installed CA-SymDump forCICS as a separate product, use member BA60RECS. Thismember will receive only the necessary components for theaddition of CA-InterTest to your CA-SymDump software.

Edit the JCL to conform to your installation standards and thepreviously completed worksheet.

Note: If you require the uppercase version of CA-InterTest forCICS because you cannot use the mixed case English characterset for your terminals, you no longer have to specify a differentFMID during the SMP RECEIVE, APPLY, and ACCEPTprocesses. Support for the uppercase version is now controlledby the IN25OPTS UCONLY=YES parameter.

Submit the job and review the output to verify that the RECIEVEprocess ran successfully. If the RECEIVE process completedwith an SMP return code greater than 4, review the output,correct the problem, and resubmit.

Step 9. Apply the CA-InterTest for CICS Product



Note: If other Computer Associates products have beeninstalled, some of these functions may have been receivedalready. If this is the case, SMP can receive the SYSMODs again.Therefore, you should be aware that not all SYSMODs receivedwill later apply and accept. Failing SYSMODs should beremoved and the job resubmitted.

WARNING! To ensure proper installation and maintenance of thisproduct, all SYSMODs specified in the SMP control statements forthis job must be selected. During the APPLY and ACCEPT steps,SMP propagates all zones that are appropriate for the product.Eliminatiing any SYSMOD from the installation process may causefailures in customization or future maintenance of the product.

Step 9. Apply the CA-InterTest for CICS Product

Member BA60APP applies all of the components (functionalSYSMODs) of CA-InterTest to the target libraries. SMP does notrequire the distribution libraries to be allocated during APPLYprocessing.

Note: If your site has previously installed CA-SymDump forCICS as a separate product, use member BA60APPS. Thismember will apply only the necessary components for theaddition of CA-InterTest to your CA-SymDump software.


Review and edit the SMP SELECT control statement as described inthe sample JCL.

Note: If other Computer Associates products have beeninstalled, some of these functions may have been appliedalready. 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 toreapply the SYSMOD.

Step 10. Accept the CA-InterTest for CICS Product



Submit the job and review the output to verify that the APPLYprocess ran successfully.

If the APPLY process completed with an SMP return codegreater than 4, review the output, correct the problem, andresubmit.

WARNING! To ensure proper installation and maintenance of thisproduct, all SYSMODs specified in the SMP control statements forthis 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 causefailures in customization or future maintenance of the product.

Step 10. Accept the CA-InterTest for CICS Product

Member BA60ACC accepts all the components (functionalSYSMODs) of CA-InterTest to the distribution libraries.

Note: If your site has previously installed CA-SymDump forCICS as a separate product, use member BA60ACCS. Thismember will accept only the necessary components for theaddition of CA-InterTest to your CA-SymDump software.

WARNING! If your site has previously installed CA-SymDump forCICS as a separate product and you are installing CA-InterTest onlyon a trial basis, skip this step. If you perform this step, you will notbe able to restore your libraries back to the original CA-SymDumpinstallation. Once the product has been purchased and licensed, youmust perform this step before any additional maintenance can beapplied.

Step 11. Install the CA-InterTest for CICS Help Facility




Review and edit the SMP SELECT control statement as described inthe sample JCL.

Note: If other Computer Associates products have been installedsome of these functions may have been accepted already. If this isthe case, a return code of 12 will occur. Remove the failingSYSMODs and resubmit the job. SMP/E users have the option ofspecifying the operand REDO on the ACCEPT command statementand should expect an SMP return code of 8, which is permissiblein this case.

Submit the job and review the output to verify that the ACCEPTprocess ran successfully. If the ACCEPT process completed withan SMP return code greater than 4, view the output, correct theproblem, and resubmit the job.

We strongly recommend that you accept the CA-InterTestproduct immediately after you have successfully run the APPLYprocess. This ACCEPT step provides a backup of the baseproduct on the distribution libraries. This backup is necessaryfor future SMP restores.

WARNING! To ensure proper installation and maintenance of thisproduct, all SYSMODs specified in the SMP control statements forthis 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 causefailures in customization or future maintenance of the product.

Step 11. Install the CA-InterTest for CICS HelpFacility

Note: If your site has previously installed CA-SymDump forCICS as a separate product, skip this step.

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



The member DEFHELP creates and loads the VSAM file thatcontains the CA-InterTest online help information. Edit the JCLto conform to your installation standards and the previouslycompleted worksheet. This member and other referencedmembers are found in the CAI.SAMPLIB library after theAPPLY step.

Step 11a. Create the User-Defined AbendDescription File

Note: If your site has previously installed CA-SymDump forCICS as a separate product and this step was optionallyperformed during that installation, skip this step.

The member DEFUHLP creates the VSAM file that contains theuser-defined abend description information. Edit the JCL toconform to your installation standards and the previouslycompleted worksheet. This member and other referencedmembers are found in the CAI.SAMPLIB library after theAPPLY step.

Step 12. Create the CA-InterTest for CICS SymbolicFile

Note: If your site has previously installed CA-SymDump forCICS as a separate product, skip this step. However, if youwant to expand your Symbolic File at this time, you canoptionally perform this step.

The member DEFSYM creates the PROTSYM VSAM file, whichcontains the symbolic information and source listings for yourapplication programs. Edit the JCL to conform to your installationstandards and the previously completed worksheet.

Step 12. Create the CA-InterTest for CICS Symbolic File



Note the following items when creating the Symbolic File:

� 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 theIDCAMS job.

� Each Symbolic File has an upper limit of about four million 2KB records and holds approximately 147,000 programs. The“Symbolic File Maintenance” chapter explains how to deletemembers.

� The Symbolic File must not reside in the LSR pool.

Symbolic File Entries

After the job DEFSYM runs, the Symbolic File contains a numberof entries. These entries provide the symbolic information forCICS system data areas and CA-InterTest data areas, and thesymbolic information for the various programs used todemonstrate the product.

Demonstration programs written in COBOL, COBOL II,COBOL/370, PL/I, and Assembler are available; COBOL andPL/I programs demonstrating composite support are alsoavailable. There are separate guides for COBOL, PL/I, andAssembler users; see the appropriate CA-InterTest GettingStarted guide for details.

Concurrently Updating the PROTSYM File

The MVS RESERVE and DEQ macros are used by CA-InterTestto allow sharing of the CA-InterTest PROTSYM file betweenregions and systems.

The resource major name used in the RESERVE and DEQ macrosis INTERTST. Place the major name INTERTST into an MVSservice that converts the RESERVE into a cross-system ENQ ifthis service is available at your site.

Step 13. Create the CA-InterTest for CICS Checkpoint File



Step 13. Create the CA-InterTest for CICSCheckpoint File

The member DEFCKPT creates the Checkpoint File that is usedto periodically record the status of CA-InterTest for a possiblerestart. Edit the JCL to conform to your installation standardsand the entries on the previously completed worksheet.

See the chapter “Monitoring Menu Options” in the CA-InterTestUser Guide for information on the checkpoint recording facility.

Step 14. Add the Required CICS ResourceDefinitions

The CSDINT member in CAI.SAMPLIB adds the CICS resourcedefinitions for the CA-InterTest programs, files, andtransactions. Modify the JCL according to the instructions in thismember.

Add the corresponding RDO group to your CICS startup list (theSIT parameter GRPLIST=) as listed in the following table.

CICS Level RDO Group for CICS Startup List

4.1 INT60041

CTS 1.2 INT60052

CTS 1.3 INT60053

Step 15. Adjust the CICS JCL



Notes:

� The use of the CA-InterTest transactions ISER, VIRC, andVTAT must not be protected to a specific signon, and forCA-ACF2 and RACF users must meet the specialconsiderations given in the chapter “System Requirements.”

� Do not change any of the options specified for theCA-InterTest entries. If you believe there is an error in any ofthe entries, contact Computer Associates Technical Support.

Step 15. Adjust the CICS JCL

Note: If your site has previously installed CA-SymDump forCICS as a separate product, some DD statements may alreadyexist.

If you use DD statements in your CICS startup JCL then yourCA-InterTest files, as defined in the CSD, require DD statementsin the JCL for CICS. DISP=SHR must be specified for PROTSYMto allow batch compiles to run concurrently with CICS.

Sample DD statements are shown next:

//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

Refer to the SYMFIL option in the “Modifying CA-InterTest forCICS Options” chapter if you need more than one SymbolicFile.

Also, add the CA-InterTest load library to the DFHRPL in theCICS startup JCL for your release of CICS:

// DD DSN=CAI.CACICS41,DISP=SHR CICS 4.1// DD DSN=CAI.CACICS52,DISP=SHR CTS 1.2// DD DSN=CAI.CACICS53,DISP=SHR CTS 1.3

Step 16. Install DB2 Support



Step 16. Install DB2 Support

Instructions for installing DB2 support is provided next. Notethat additional considerations apply if you have programs thatissue calls or require special handling.

Supporting DB2 Calls in the FILE and CORE Facilities

The FILE facility supports dynamic SQL calls to DB2. Thisfeature lets users view, alter, add, or delete data in DB2 tableswithout leaving CICS. The CORE facility lets you view the lastSQL statement executed (CORE=LASTSQL).

The pregenerated versions of IN25DB2 and IN25AI## arepreassembled with DB2 Release 3.1.

Perform the following steps to install DB2 support:

1. CICS 4.1 sites must add the FILE, VTAT, CNTL, LIST, HELP,CORE, and ITST transactions to the RCT (Resource ControlTable). See the IBM Database2 Installation Manual for adescription of the DSNCRCT macro. CTS 1.2 and 1.3 sitesare provided with the RDO entries in the CSDDB2 memberon the CAI.SAMPLIB.

2. Bind the DBRM members IN60FIDB and IN60AIDBprovided on the CAI.SAMPLIB into an InterTest DB2 plan(the recommended name is IN60PLAN).

3. The DBA must grant Bind and Execute authority to the plancreated in Step 2.

Step 17. Restart CICS and Run Check-out Program



Monitoring DB2 Applications

A pregenerated version of IN25UEXI, assembled for DB2Releases 3.1 and above, is provided in your CA-InterTest loadlibrary.

If you do not have any other special software situations that willbe handled by the IN25UEXI program, you need not performany additional installation steps for DB2 support. However, ifyou have programs that issue calls or require special handling,see the Calls to Software and User Macro Support MacroSupport section.

For additional information on using CA-InterTest with DB2, seethe section Using CA-InterTest for CICS with DB2 ApplicationPrograms.

Step 17. Restart CICS and Run Check-out Program

After CA-InterTest has been installed, restart CICS and run theCA-InterTest check-out program IN25VRPT. This programchecks for common mistakes that may have been made duringthe installation of CA-InterTest.

Important! You are strongly advised to perform this step so errorscan be detected quickly.

To check out the installation of CA-InterTest:

1. Enter the transaction code VRPT. CA-InterTest displays theselection menu.

2. Enter 1 in the Option field and press Enter. CA-InterTestdisplays the first screen of programs.

3. Continue to press Enter to display the next screen.

4. The CA-InterTest check-out procedure is completed whenthe selection menu is displayed with the option field set to 4or beyond.

Step 18. Install Support for the PL/I Option (Optional)

4�22 CA-InterTest for CICS Getting Started

IntGSms.doc, printed on 12/27/00, at 11:59 AM

Important! If you are upgrading from a previous release, urge yourusers to use ITST Option 8 to review �What�s New� in this release.

Step 18. Install Support for the PL/I Option(Optional)

If you need support for PL/I programs, you must perform theSMP/E RECEIVE, APPLY and ACCEPT procedures in additionto the base product installation. The PL/I option installationuses the same target and distribution libraries as theCA-InterTest base product. See the chapter �PL/I OptionInstallation Steps� for details.

Step 19. Unload Documentation Set

The CA-InterTest for CICS documentation set is provided inAdobe Acrobat PDF format and in IBM BookManager format. Inaddition, two quick references are provided in PDF format foryou to print. Procedures for unloading the documentation andfor printing the quick references follow.

Unloading BookManager Files from the Distribution Tape

In addition to the PDF files provided for printing, updates to theCA-InterTest for CICS documentation are provided in IBMBookManager format on the CA-InterTest for CICS installationand maintenance cartridge in file 14. Unload the BookManagerREAD files using the JCL in SAMPJCL member BA60BOOK.Edit the JCL to conform to your installation standards andsubmit the job.


Base Product Installation Steps 4�23

IntGSms.doc, printed on 12/27/00, at 11:59 AM

The CA-InterTest for CICS documentation set consists of sixsequential data sets that contain the following:

� The bookshelf definition

� A search index

� The CA-InterTest for CICS User Guide

� The CA-InterTest for CICS and CA-SymDump for CICSMessage Guide

� The CA-InterTest for CICS Getting Started

� The CA-InterTest for CICS Assembler Primer

� The CA-InterTest for CICS COBOL Primer

� The CA-InterTest for CICS PL/I Primer

Changing the Prefix in the Bookshelf Definition

The bookshelf definition (prefix BKSHELF) contains the MVSdata set names BookManager uses to reference the other books.The original bookshelf definition uses CAI as the prefix in thosedata set names. To use BookManager Read on MVS, you mustchange the references to those data sets by replacing CAI withthe prefix used to unload the files.

Downloading OS/390 Files for Use on a PC

Perform the actions in this section only if you want to downloadthe OS/390 files to a PC. To use the PC versions of BookManagerREAD, be sure that the book files have been downloaded with afile extension of .BOO. The bookshelf must have an extension of.BKS and the index should have an extension of .BKI.




The following table describes the sequential files that areprovided on the product tape and lists the commands you canissue to transfer them to a PC.

OS/390 Name/Description OS/390 Format File Transfer Command on PC

prefix.CAINT60.BKSHELFBookshelf definition

Variable blockASCII CRLF

RECEIVE <dir>\CAINT60.BKS‘prefix.CAINT60.BKSHELF’

prefix.CAINT60.BKINDEXSearch index

Fixed blockLRECL 4096 Binary

RECEIVE <dir>\CAINT60.BKI‘prefix.CAINT60.BKINDEX’

prefix.CAINT60.INT60OG1Getting Started


RECEIVE <dir>\INT60OG1.BOO‘prefix.CAINT60.INT60OG1’

prefix.CAINT60.INT60OM1Message Guide


RECEIVE <dir>\INT60OM1.BOO‘prefix.CAINT60.INT60OM1’

prefix.CAINT60.INT60OU1User Guide


RECEIVE <dir>\INT60OU1.BOO‘prefix.CAINT60.INT60OU1’

prefix.CAINT60.INT60OA1Assembler Primer


RECEIVE <dir>\INT60OA1.BOO‘prefix.CAINT60.INT60OA1’

prefix.CAINT60.INT60OC1COBOL Primer


RECEIVE <dir>\INT60OC1.BOO‘prefix.CAINT60.INT60OC1’

prefix.CAINT60.INT60OP1PL/I Primer


RECEIVE <dir>\INT60OP1.BOO‘prefix.CAINT60.INT60OP1’




Unloading the Acrobat PDF File from the Distribution Tape

The CA-InterTest for CICS installation and maintenancecartridge contains updates to the CA-InterTest for CICSdocumentation in Adobe Acrobat PDF format in file 12. Unloadthe PDF file using the SAMPJCL member BA60PDF. Edit the JCLto conform to your installation standards and submit the job.

Download this file to a platform that supports Adobe Acrobat,such as a PC, with an extension of .tgz.

Decompress the file on the target platform.

For Windows 9x If available, use WinZip 6.2 or above. Save the restored files tothe drive and directory of your choice.

For Windows NT and2000

Use one of the following methods:

� If available, use WinZip 6.2 or above. Save the restored filesto the drive and directory of your choice.

� Enter the following at a command prompt:

gzip –d BA60PDF.tgzpax –r –f BA60PDF.tar

Move the files to the drive and directory of your choice.

Note: gzip is a free, nonstandard utility available fromhttp://www.gnu.org/software/gzip/gzip.html. The pax(Portable Archive Interchange) utility comes with yourWindows operating system.

http://www.gzip.org/




For UNIX (IncludingOS/390 USS and Linux)

Use one of the following sets of commands:

gzip –d BA60PDF.tgzpax –r –f BA60PDF.tar

Note: gzip is a free, nonstandard utility available fromhttp://www.gnu.org/software/gzip/gzip.html. The pax (PortableArchive Interchange) utility comes with your Windowsoperating system.

uncompress BA60PDF.tar.ztar xvf BA60PDF.tar

Move the files to the drive and directory of your choice.

Start your Adobe Acrobat Reader to open the restored PDF files.

Printing the Quick References

The following two quick references are included in the PDF filethat you unloaded from the tape using the SAMPJCL memberBA60PDF:

� Quick Reference for All Users

� Quick Reference for Assembler, COBOL, and PL/I Users

To print the quick reference PDF files, set the laser printer PrintProperties to Legal (8.5"x14"), 2-sided/Duplex, 'Flip' or 'Rotate'on Short Edge. These settings give you the correct size anddirection of the text. You can print the reference on letter sizepaper; however, the reference will be easier to read if printed onthe larger size legal paper. If using legal size paper, you mayneed to manually load the legal size paper in the printer. Afterprinting, you can fold the paper between the three columnsaccordion style to create an easy-to-read quick reference.

http://www.gzip.org/

Activating CA-InterTest for CICS



Activating CA-InterTest for CICS

After you have completed the installation steps, you can activateCA-InterTest in your CICS system at any time. To activateCA-InterTest, issue the following command:

CNTL=START

For CA-InterTest regions installed with CICSPlex support(CICSPLEX=YES in IN25OPTS), the CNTL=START andCNTL=RESTART commands automatically have CA-InterTestresynchronize monitoring with any active regions in theCICSPlex. The “Automatically Starting CA-InterTest” chapterexplains how to start CA-InterTest automatically with your CICSsystem.

At this time, you can compile and assemble your programs withthe CA-InterTest symbolic post-processor programs as describedin the “Symbolic Support” chapter. These programs let you usesymbolic references during testing.

Remember, however, that you do not have to compile yourprograms with one of the CA-InterTest symbolic post-processorprograms. All of the CA-InterTest monitoring facilities areavailable for current programs without recompiling orreassembling them. We do recommend that you recompile orreassemble current programs if CA-InterTest detects errorsbecause symbolic support greatly facilitates debugging.

To activate CA-InterTest at CICS startup, you can:

� Manually activate CA-InterTest by issuing theCNTL=START command.

� Automatically activate CA-InterTest using the PROMMACmacro or the IN25PLT PLTPI program. For details, see thechapter “Automatically Starting CA-InterTest for CICS.”

Deactivating CA-InterTest for CICS



Deactivating CA-InterTest for CICS

CA-InterTest can be deactivated at any time by issuing thefollowing command:

CNTL=END

For regions using the CICSPlex support option, you can issue thefollowing command to concurrently deactivate CA-InterTest inall connected CICSPlex regions:

CNTL=END,SCOPE=GLOBAL

CA-InterTest maintains a permanent service task that runsunder the transaction ID ISER. The program is IN25SERV.CICS cannot complete a normal shutdown until this task ends.It is important that you deactivate CA-InterTest before CICSshutdown to terminate this task.

To deactivate CA-InterTest at CICS shutdown, you can do one ofthe following:

� Manually deactivate CA-InterTest by issuing theCNTL=END command.

� Automatically deactivate CA-InterTest using the IN25PLTEprogram. If you add this CA-InterTest-supplied shutdownPLT program to your shutdown program list, CA-InterTestwill be deactivated automatically at normal CICStermination.

� Add the following CA-InterTest PLTSD entry beforeDFHDELIM so that it is part of Stage 1 processing:

DFHPLT TYPE=ENTRY,PROGRAM=IN25PLTE

PL/I Option Installation Steps 5–1


Chapter

5 PL/I Option Installation Steps

If you are licensed to install and use the CA-InterTest PL/Ioption, you must perform the following SMP/E RECEIVE,APPLY, and ACCEPT procedures in addition to the baseproduct installation. The PL/I option installation procedureuses the same target and distribution libraries as CA-InterTest.

Note: If you did not modify member KEYS in the OPTLIB dataset to include the PL/I option LMP key, you must do this tosuccessfully run the PL/I option. See the section Step 2. EnterLMP Product Key Certificate Information for instructions.

Installation Checklist The following list summarizes the steps involved in the PL/Ioption installation.

Note: If your site has previously installed CA-SymDump forCICS as a separate product with PL/I support, skip these steps.

Step 1. Execute an SMP RECEIVE function using the MA60RECJCL member.

Step 2. Execute an SMP APPLY function using the MA60APPJCL member.

Step 3. Execute an SMP ACCEPT function using the MA60ACCJCL member.

Step 1. Receive the CA-InterTest PL/I Option



Step 1. Receive the CA-InterTest PL/I Option

Member MA60REC receives all of the components (functionalSYSMODs) of the CA-InterTest PL/I option and executes theprocedure edited in Step 7, Customize the SMP Procedure in the“Base Product Installation Steps” chapter.


Submit the job and review the output to verify that the RECEIVEprocess ran successfully. If the RECEIVE process completedwith an SMP return code greater than 4, review the output,correct the problem, and resubmit.

Step 2. Apply the CA-InterTest PL/I Option

Member MA60APP applies all of the components (functionalSYSMODs) of the CA-InterTest PL/I option to the targetlibraries. SMP does not require the distribution libraries to beallocated during APPLY processing.


Submit the job and review the output to verify that the APPLYprocess ran successfully. If the APPLY process completed withan SMP return code greater than 4, review the output, correct theproblem, and resubmit.

Step 3. Accept the CA-InterTest PL/I Option

PL/I Option Installation Steps 5–3


Step 3. Accept the CA-InterTest PL/I Option

WARNING! If your site has previously installed CA-SymDump forCICS as a separate product and you are installing CA-InterTest onlyon a trial basis ,skip this step. If this step is performed, you will notbe able to restore your libraries back to the original CA-SymDumpinstallation. Once the product has been purchased and licensed, youmust perform this step before any additional maintenance can beapplied.

Member MA60ACC accepts all of the components (functionalSYSMODs) of the CA-InterTest PL/I option to the distributionlibraries.


Submit the job and review the output to verify that the ACCEPTprocess ran successfully. If the ACCEPT process completed withan SMP return code greater than 4, view the output, correct theproblem, and resubmit the job.

We strongly recommend that you accept the CA-InterTest PL/Ioption product immediately after you have successfully run theAPPLY process. This ACCEPT step provides a backup of thebase product on the distribution libraries. This backup isnecessary for future SMP restores.

Symbolic Support 6–1


Chapter

6 Symbolic Support

To be able to use symbolic references in COBOL, Assembler, andPL/I programs, you must make a one-time change to your compileand assemble procedures. This new procedure will not change yourprogram or load module in any way. It simply runs a CA-InterTestprogram to save information for online use.

The new procedure can be executed by as many concurrent jobsas necessary. Concurrent compiles or assemblies do not interferewith each other in updating the Symbolic File.

After you change your compile and assemble procedure, youshould compile and assemble a few CICS programs to test thenew procedure.

COBOL Compilers

The post-processor program that you use to change yourcompile procedure depends on your COBOL compiler. Thesample JCL described later in this section explains whichpost-processor to use.

Here is how the CA-InterTest post-processor works:

1. The CA-InterTest post-processor operates after yourcompiler step and collects information from the compiler's//SYSPRINT DD statement.

2. This temporary data set is passed to the CA-InterTest jobstep through the //INPUT DD statement.

COBOL Compilers



3. The original input from your compiler's //SYSPRINT iswritten to the //OUTPUT DD data set declared in theCA-InterTest job step. This data set is specified in the sameway as the //SYSPRINT DD was specified for the compilewithout CA-InterTest.

4. Messages from the CA-InterTest program are written to the...//MESSAGE DD SYSOUT=... statement to be printed.

5. The CA-InterTest Symbolic VSAM File is referenced throughthe //PROTSYM DD statement with DISP=SHR.

6. Old records in the PROTSYM file are replaced by new onesduring each run of the CA-InterTest program.

See the “Symbolic File Maintenance” chapter for instructionson removing old program data from the file.

Additional Notes forCOBOL Programs

To use symbolic references in COBOL, you should also beaware of the following considerations:

� For CICS MVS, the following options must not be used in aCOBOL program that is a CICS application: COUNT,ENDJOB, FLOW, DYNAM, STATE, SYMDMP, SYST, andTEST.

� At least one data item must be declared in Working Storage.

� If compiling a program using the COBOL for MVS and VMcompiler, the program must be defined to CICS as LE/370and not COBOL or COBOL II. Failure to do so can causeunpredictable results.

COBOL Compilers



IBM COBOL Compiler Options

The following options must be used with the IBM COBOLcompiler.

COBOL COBOL II, COBOL/370,IBM COBOL for MVS,IBM COBOL for OS/390

Produces

NONUM NONUMBER Suppress CompilerGenerated Line Numbers

DMAP MAP Data Division Map

VERB no option Verb Names

SXREF XREF Cross-Reference of DataNames & Cross-Referenceof Paragraph Names

CLIST orPMAP

OFFSET orLIST

Condensed ProcedureDivision Map

ASSEMBLER-likeProcedure Division Map

See the section Additional Notes for COBOL Programs in thischapter for other compiler considerations.

COBOL Compilers



CA-Optimizer and CA-Optimizer/II Option

The options listed in the following table must be used withCA-Optimizer and CA-Optimizer/II if you are not using theNOCOPT option. (The NOCOPT option specifies that theprogram will not be optimized by CA-Optimizer even ifCA-Optimizer is active.)

If you are using the NOCOPT option, use the options for IBMCOBOL compilers specified in the previous section. See theCA-Optimizer User Guide or CA-Optimizer/II User Guide formore information.

CA-Optimizer CA-Optimizer/II Produces

MLIST MLIST or MOFFSET Integrated ProcedureDivision Map

NONUM NONUMBER Suppress Compiler-Generated LineNumbers

DMAP MAP or MMAP Data Division Map

INTERTST CA-InterTestrequirement. Indicatesthat the program isbeing optimized for usewith CA-InterTest.

XREF XREF Cross-Reference of DataNames and Cross-Reference of ParagraphNames

Using the Post-Processors with Multiple CA-InterTest Releases



Using the Post-Processors with Multiple CA-InterTestReleases

WARNING! The symbolics produced by this release's version of thepost-processor are not downward compatible with earlier CA-InterTestreleases.

Symbolics produced by earlier CA-InterTest releases are upwardcompatible with all CA-InterTest releases.

� If you need programs to run under multiple CA-InterTestreleases, compile or assemble these programs with thelowest CA-InterTest release you are using.

� If you require support for both CA-Realia Host Test Optionand a release level of CA-InterTest that requires a separateversion of the post-processors, you can either create andmaintain separate Symbolic Files or mix the output of thedifferent post-processors in the same Symbolic File.

CA-InterTest Post-Processor Program Options

Options are passed to the CA-InterTest post-processor using aparameter statement. The parameter statement can be specifiedin a control card or created in a PARM= parameter of apreceding job step. The "//GENPARM" step (indicated by 2->)in the JCL example at the end of this section illustrates how tospecify the statement.

� The only required field on the parameter statement is aprogram name. The program name is the name in the CICSprogram definition or, for composite support, the monitor-name.

� If you pass options using a control card, the program namemust start in column 1.

The following example saves symbolic references for theprogram named ORDEDIT using a control card:

COL = 1...5....0 ORDEDIT




Controlling Printed Output with the CUTPRINT Option

Since all COBOL source code and compiler information can beavailable online, you can request that the CA-InterTest programnot print all or part of the listing produced by the compiler. Tomake this request, add one of the following keywordsimmediately after the program name on the parameterstatement:

,CUTPRINT=ALL produces no COBOL listing

,CUTPRINT=MAP prints only the part that precedes the DataDivision map

,CUTPRINT=REF prints only the parts that precede the datanames Cross-Reference list

The following sample parameter statement saves symbolicinformation for the program ORDEDIT and prints only thesource code portion of the compiler output.

ORDEDIT,CUTPRINT=MAP

Note: Specify the CUTPRINT parameter only when you do notwant all or part of your listing printed. The entire listing will beprinted if this parameter is missing from the parameterstatement.

Saving Your Listing for Online Display with the LISTER Option

You can also request that all or a portion of your source code besaved for online viewing. If saved, CA-InterTest automaticallydisplays the relevant part of the listing when a breakpointoccurs.

To make this request you must add one of the followingkeywords to the parameter statement:

,LISTER=ALL saves the entire COBOL listing

,LISTER=MAP saves only the parts that precede the DataDivision map (recommended for COBOL)




,LISTER=REF saves only the parts that precede the data namesCross-Reference list (recommended for COBOL II)

For example, to save the symbolic references for the programORDEDIT, not print any portion of the listing, and save thesource code portion of the program, specify the following:

ORDEDIT,CUTPRINT=ALL,LISTER=MAP

Notes:

� If the LISTER parameter is omitted, no listing is saved in theSymbolic File.

� We recommend that you use LISTER=MAP for COBOL andLISTER=REF for COBOL II for minimum overhead and diskspace usage.

� If only the LISTER parameter is specified, it must follow theprogram name.

Setting Data as Nonpurgable

You could also request that any saved symbolic data for thisprogram be marked as nonpurgable. If a program's data ismarked as nonpurgable, the data will not be removed from theSymbolic File when deleting programs using a purge intervalbatch run. However, the data could be deleted by programname. See the “Symbolic File Maintenance” chapter forinstructions on deleting data from the Symbolic File.

To mark data as nonpurgable, add the following keyword to theparameter statement as the last option:

,NOPURGE

In the following example, the parameter specification records thesymbolic references for the program ORDEDIT, prints thelisting, does not save any portion of the listing, and does notallow symbolic data to be removed from the Symbolic File by apurge interval batch run.

ORDEDIT,NOPURGE

COBOL JCL Examples



In the next example, the parameter specification records thesymbolic references for the program ORDEDIT, does not print acopy of the listing, does not save any portion of the listing, anddoes not allow data to be removed from the Symbolic File by apurge interval batch run.

ORDEDIT,CUTPRINT=ALL,NOPURGE

In this example, the parameter specification records the symbolicreferences for the program ORDEDIT, does not print a copy ofthe listing, saves the source code portion of the listing for onlinedisplay, and does not allow data to be removed from theSymbolic File by a purge interval batch run.

ORDEDIT,CUTPRINT=ALL,LISTER=MAP,NOPURGE

COBOL JCL Examples

The following sections show JCL examples.

COBOL/VS or CA-Optimizer Example

All changes to the normal procedure are specified by ->.

//*//* YOUR EXISTING CICS PREPROCESSOR JCL GOES HERE//* (IF DOING A COMMAND LEVEL COMPILE)//////* YOUR EXISTING COBOL OR CA-OPTIMIZER JCL GOES HERE WITH//* THE FOLLOWING MODIFICATIONS://*

For COBOL/VS only:

1-> //SYSPRINT DD DSN=&&INPUT,DISP=(,PASS),UNIT=SYSDA,1-> // SPACE=(TRK,(15,5)),1-> // DCB=(DSORG=PS,LRECL=121,BLKSIZE=2420,RECFM=FBA)

//*

For CA-Optimizer only:

1-> //SYSPRINT DD DSN=&&INPUT,DISP=(MOD,PASS),UNIT=SYSDA,1-> // SPACE=(TRK,(15,5)),1-> // DCB=(DSORG=PS,LRECL=121,BLKSIZE=2420,RECFM=FBA)

//*

COBOL JCL Examples



For all symbolic users:

//*//* IF THE COMPILER GIVES A RETURN CODE NOT HIGHER THAN 4 -//*//* RUN THE CA-INTERTEST POST-PROCESSOR -//*//* BELOW, THE //STEPLIB AND THE //STEPCAT MAY BE UNNECESSARY.//*

2-> //GENPARM EXEC PGM=IN25PARM,PARM='PARAMETER STATEMENT'2-> //STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR2-> //CARDS DD DSN=&&CARDS,DISP=(,PASS),UNIT=SYSDA,

SPACE=(TRK,(1,1))//*//POSTCOB EXEC PGM=IN25SYMC,COND=(4,LT,COBOL),REGION=512K//SYSUDUMP DD SYSOUT=A//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//INPUT DD DSN=&&INPUT,DISP=(OLD,DELETE)//OUTPUT DD SYSOUT=A,DCB=(RECFM=FBA,LRECL=121,BLKSIZE=2420)//MESSAGE DD SYSOUT=A//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR

3-> //CARDS DD DSN=&&CARDS,DISP=(OLD,DELETE)//*//* IF THE COMPILER GIVES A RETURN CODE HIGHER THAN 4 -//* THEN RUN AN IEBGENER TO PRINT THE COBOL LISTING -//*//PRINT EXEC PGM=IEBGENER,COND=(5,GT,COBOL)//SYSPRINT DD DUMMY//SYSIN DD DUMMY//SYSUT1 DD DSN=&&INPUT,DISP=(OLD,DELETE)//SYSUT2 DD SYSOUT=A//*//* YOUR EXISTING LINKAGE-EDITOR JCL GOES HERE

In the STEPLIB DD statements, replace xx with your two-digitCICS release number (for example: 41 for CICS 4.1, 52 for CTS1.2, or 53 for CTS 1.3). The following JCL modifications must bemade to your existing compile procedure:

1. Specify the //SYSPRINT data set in the COBOL/VScompiler or CA-Optimizer step.

2. Insert a new job step to execute the CA-InterTest programafter the compiler or CA-Optimizer step.

COBOL JCL Examples



This JCL example assumes that you will pass the parameterstatement in the PARM parameter of the EXEC statement. If youprefer to pass the parameter statement using a control card:

1. Remove all of the statements in the example that are markedby a 2->.

2. Change the following JCL statement:

3-> //CARDS DD DSN=&&CARDS,DISP=(OLD,DELETE)

to

3-> //CARDS DD *

3. Add the parameter statement after this JCL statement.

Note: The CA-InterTest post-processor is shown with a regionsize of 512 KB. Processing larger programs may require a largerregion size.

COBOL II, CA-Optimizer/II, COBOL/370, IBM COBOL for MVS, or IBMCOBOL for OS/390 Example

All changes to the normal procedure are specified by ->.

//*//* YOUR EXISTING CICS PREPROCESSOR JCL GOES HERE//* YOUR EXISTING CICS PREPROCESSOR JCL GOES HERE//* YOUR EXISTING CICS PREPROCESSOR JCL GOES HERE//* YOUR EXISTING CICS PREPROCESSOR JCL GOES HERE//* (IF DOING A COMMAND LEVEL COMPILE)//////* YOUR EXISTING COBOL II OR CA-OPTIMIZER/II JCL GOES HERE WITH//* THE FOLLOWING MODIFICATIONS://*

For COBOL II, COBOL/370, IBM COBOL for MVS, or IBMCOBOL for OS/390 only:


For CA-Optimizer/II only:

1-> //SYSPRINT DD DSN=&&INPUT,DISP=(MOD,PASS),UNIT=SYSDA,1-> // SPACE=(TRK,(15,5)),1-> // DCB=(DSORG=PS,LRECL=133,BLKSIZE=3990,RECFM=FBA)

//*

COBOL JCL Examples



For all symbolic users://*//* IF THE COMPILER GIVES A RETURN CODE NOT HIGHER THAN 4 -//* RUN THE CA-INTERTEST POST-PROCESSOR -//*//* BELOW, THE //STEPLIB AND THE //STEPCAT MAY BE UNNECESSARY.//*

2-> //GENPARM EXEC PGM=IN25PARM,PARM='PARAMETER STATEMENT'2-> //STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR2-> //CARDS DD

DSN=&&CARDS,DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(1,1))//*//POSTCOB EXEC PGM=IN25COB2,COND=(4,LT,COBOL),REGION=512K//SYSUDUMP DD SYSOUT=A//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//INPUT DD DSN=&&INPUT,DISP=(OLD,DELETE)//OUTPUT DD SYSOUT=A,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=2660)//*//MESSAGE DD SYSOUT=A//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR

3-> //CARDS DD DSN=&&CARDS,DISP=(OLD,DELETE)//*//* IF THE COMPILER GIVES A RETURN CODE HIGHER THAN 4 -//* THEN RUN AN IEBGENER TO PRINT THE COBOL LISTING -//*//PRINT EXEC PGM=IEBGENER,COND=(5,GT,COBOL)//SYSPRINT DD DUMMY//SYSIN DD DUMMY//SYSUT1 DD DSN=&&INPUT,DISP=(OLD,DELETE)//SYSUT2 DD SYSOUT=A//*//* YOUR EXISTING LINKAGE-EDITOR JCL GOES HERE

In the STEPLIB DD statements, replace xx with your two-digitCICS release number (for example: 41 for CICS 4.1, 52 for CTS1.2, or 53 for CTS 1.3).

The following JCL modifications must be made to your existingcompile procedure:

1. Specify the //SYSPRINT data set in the COBOL II compileror CA-Optimizer/II step.

2. Insert a new job step to execute the CA-InterTest programafter the compiler or CA-Optimizer/II step.

Assembler Programs




1. Remove all of the statements in the example that are markedby a 2->.



to

3-> //CARDS DD *


Note: The CA-InterTest post-processor is shown with a regionsize of 512 KB. Processing larger programs may require a largerregion size.

Assembler Programs

The change to your Assembler procedure requires only one jobstep—to execute the IN25SYMA program. IN25SYMA supportsAssembler F, Assembler H, and High Level Assembler.

Here is how the CA-InterTest procedure works:

1. IN25SYMA operates between your Assembler and link-editor, collecting information from the Assembler's//SYSPRINT DD statement, which should be declared atemporary sequential data set in the Assembler job stepwith:

DCB=(RECFM=FBA,LRECL=121,BLKSIZE=(a multiple of 121))

Note: When using Assembler H, specify RECFM=FBMunless your Assembler H is generated to produce listings inthe RECFM=FBA format.

2. That temporary data set is passed to the IN25SYMA job stepthrough the //INPUT DD statement.

Assembler Programs



3. The original input from your Assembler's //SYSPRINT iswritten to the //OUTPUT DD data set declared in theIN25SYMA job step.

4. Messages from the IN25SYMA program are written to the//MESSAGE DD statement to be printed.

5. The CA-InterTest Symbolic VSAM file is referenced byIN25SYMA through the //PROTSYM DD statement withDISP=SHR.

6. Old records in the PROTSYM file are replaced by new oneswith each run of the IN25SYMA program.

See the “Symbolic File Maintenance” chapter for instructionson removing old program data from the Symbolic File.

Note: For CA-InterTest Source Listing support to workproperly, all CSECTs must appear in the listing and each CSECTstatement must have a label.

Assembler Options

The entire listing produced by the Assembler is required. Thefollowing options must be specified:

Option Produces

ESD External Symbol Dictionary

XREF(FULL) or Full Cross-ReferenceXREF(SHORT) Short Cross-Reference

Important! You must ensure that all statements that define the startof DSECTs are printed. This ensures that the CORE structureddisplay facility shows the correct data in DSECT format.

Note: High Level Assembler Release 2.0 users must also specifythe option LIST(121).

Assembler Programs



IN25SYMA Options

Options are passed to the CA-InterTest post-processor using aparameter statement. The parameter statement can be specifiedin a control card or created in a PARM= parameter of apreceding job step. The //GENPARM step (indicated by 2->) inthe JCL example at the end of this section shows how to specifythe statement.

Note: If you specify the parameter statement as a control card,the program name must start in column 1.

The only required field on this parameter card is the programname. The program name is the name in the CICS programdefinition or, for composite support, the monitor-name.

The following example saves the symbolic references for theprogram named ORDEDIT in control card format:



Since all Assembler output can be made available online, youcan request that the IN25SYMA program not print all or any partof the listing produced by the Assembler. To make this request,you must add one of the following keywords immediately afterthe program name on the parameter card:

,CUTPRINT=ALL produces no Assembler listing

,CUTPRINT=REF prints only the parts that precede the Cross-Reference list

The following example saves symbolic information for theprogram ORDEDIT but will not produce a hardcopy listing.

ORDEDIT,CUTPRINT=ALL

Note: Specify the ,CUTPRINT= parameter only when you donot want all or part of your listing printed. The entire listingprints if this parameter is omitted from the parameter statement.

Assembler Programs





To save the listing you must add one of these keywords to theparameter statement:

,LISTER=ALL saves the entire Assembler listing

,LISTER=REF saves only the parts that precede the Cross-Reference list

The parameter specification in the following example savessymbolic references for program ORDEDIT, does not print thelisting, and saves the entire Assembler output for online display.

ORDEDIT,CUTPRINT=ALL,LISTER=ALL

Notes:


� If only the LISTER parameter is specified, it must follow theprogram name.


You can also request that any saved symbolic data for thisprogram be marked as nonpurgable. If a program's data ismarked as nonpurgable, the data will not be removed from theSymbolic File when deleting programs using a purge intervalbatch run. However, the data can be deleted by program name.See the “Symbolic File Maintenance” chapter for instructionson deleting data from the Symbolic File.

To mark data as nonpurgable, add this keyword to theparameter statement as the last option:

,NOPURGE

Assembler Programs



The parameter specification in the following example records thesymbolic references for the program ORDEDIT, prints thelisting, does not save any portion of the listing, and does notallow symbolic data to be removed from the Symbolic File by apurge interval batch run.

ORDEDIT,NOPURGE

The parameter specification in the following example records thesymbolic references for the program ORDEDIT, does not print acopy of the listing, does not save any portion of the listing, anddoes not allow symbolic data to be removed from the SymbolicFile by a purge interval batch run.


The parameter specification in the following example records thesymbolic references for the program ORDEDIT, does not print acopy of the listing, saves the entire output listing for onlinedisplay, and does not allow symbolic data to be removed fromthe Symbolic File by a purge interval batch run.

ORDEDIT,CUTPRINT=ALL,LISTER=ALL,NOPURGE

Assembler Programs



Assembler JCL Example

All changes to the normal Assembler procedure are indicated by->.

//*//* YOUR EXISTING CICS PREPROCESSOR JCL GOES HERE//* (IF DOING A COMMAND LEVEL ASSEMBLER PROGRAM)//////* YOUR EXISTING ASSEMBLER JCL GOES HERE WITH//* THE FOLLOWING MODIFICATIONS//*


//*//*//* IF THE ASSEMBLER GIVES A RETURN CODE NOT HIGHER THAN 0 -//*//* THEN RUN THE CA-INTERTEST POST-PROCESSOR -//*

2-> //GENPARM EXEC PGM=IN25PARM,PARM='PARAMETER STATEMENT'2-> //STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR2-> //CARDS DD DSN=&&CARDS,DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(1,1))

//*//POSTASM EXEC PGM=IN25SYMA,COND=(0,LT,ASM),REGION=512K

//SYSUDUMP DD SYSOUT=A//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//INPUT DD DSN=&&INPUT,DISP=(OLD,DELETE)//OUTPUT DD SYSOUT=A,DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)//MESSAGE DD SYSOUT=A//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR

3-> //CARDS DD DSN=&&CARDS,DISP=(OLD,DELETE)//*//* IF THE ASSEMBLER GIVES A RETURN CODE HIGHER THAN 0 -//* THEN RUN AN IEBGENER TO PRINT THE ASSEMBLER LISTING -//*//PRINT EXEC PGM=IEBGENER,COND=(0,EQ,ASM)//SYSPRINT DD DUMMY//SYSIN DD DUMMY//SYSUT1 DD DSN=&&INPUT,DISP=(OLD,DELETE)//SYSUT2 DD SYSOUT=A//*//* YOUR EXISTING LINKAGE-EDITOR JCL GOES HERE//*


PL/I Programs



The following JCL modifications must be made to your existingAssembler procedure to use the IN25SYMA program:

1. The //SYSPRINT data set in the Assembler step must bemodified.

2. A new job step to execute the IN25SYMA program must beinserted after the Assembler step.

In the previous example, the parameter statement is specified inthe PARM parameter of the EXEC statement. If you want topass the parameter statement using a control card:

1. Remove all of the statements marked with a 2->.



to

3-> //CARDS DD *


PL/I Programs

To be able to set breakpoints at PL/I statement numbers andlabel names online, a one-time change to your PL/I compileprocedure is required. This new procedure runs a CA-InterTestprogram, IN25SYMP, to save information for online use.

Here is how the CA-InterTest program IN25SYMP works:

1. IN25SYMP operates between your compiler and link-editorand collects information from the compiler's //SYSPRINTDD statement. Declare this data set a temporary, sequentialdata set in the compiler job step with:

DCB=BLKSIZE=a number larger than 129

2. This temporary data set is passed to the IN25SYMP job stepthrough the //INPUT DD statement.

3. The original input from your compiler's //SYSPRINT iswritten to the //SYSPRINT DD data set declared in theIN25SYMP job step.

PL/I Programs



4. Messages from the IN25SYMP program are written to boththe //MSGS DD and the //MESSAGES DD statements.

5. The CA-InterTest Symbolic VSAM File is updated byIN25SYMP through the //PROTSYM DD statement withDISP=SHR.

6. Old records in the PROTSYM file are replaced by new onesduring each run of the CA-InterTest program.

See the “Symbolic File Maintenance” chapter for instructionson removing old program data from the file.

Compiler Options

Suggested parameters for the PL/I optimizing compiler provideenough information for successful symbolic debugging. TheLIST option (Assembler-like listing of the generated code) isoptional, but the tables of offsets must be provided.

The following options must be used with the IBM PL/Icompiler: AGGREGATE, ATTRIBUTES(FULL), MAP, NEST,NOGONUM, NOMARGINI, NONUMBER, OPTIONS,SOURCE, STMT or GOSTMT, STORAGE, and XREF(FULL).

Note: Because of special considerations, if you must use the%NOPRINT compiler option contact CA-InterTest technicalsupport.

Installation Options

For Symbolic File compile date-time to load module checking onPL/I programs to function, your PL/I compiler must have beeninstalled with the TSTAMP=YES option (the default).

PL/I Programs



IN25SYMP Options

Options are passed to the CA-InterTest post-processor using aparameter statement. This statement can be specified in acontrol card or created in a PARM= parameter of a preceding jobstep. The //GENPARM step (indicated by 2->) in the JCLexample at the end of this section shows how to specify thestatement.

Note: If you specify the options in a control card, the programname must start in column 1.

The only required field on the parameter statement is a programname. The program name is the name in the CICS programdefinition or, for composite support, the monitor-name.

The following example saves symbolic references for theprogram named ORDEDIT in control card format:



Since all PL/I source code and compiler information can beavailable online, you can request that the IN25SYMP programnot print all or part of the listing produced by the compiler. Tomake this request, add one of the following keywordsimmediately after the program name:

,CUTPRINT=ALL produces no PL/I listing

,CUTPRINT=REF terminates printing after the XREF table

,CUTPRINT=OFFSET terminates printing after the table ofoffsets

The following example saves symbolic information for theprogram ORDEDIT and terminates printing after the XREF table.

ORDEDIT,CUTPRINT=REF

PL/I Programs



Notes:

� Specify the ,CUTPRINT parameter only when you do notwant all or part of your listing printed. The entire listingprints if this parameter is not specified.

� If only this parameter is specified, it must immediatelyfollow the program name.



To make this request you must add one of the followingkeywords to the parameter statement:

,LISTER=ALL saves the entire PL/I listing

,LISTER=REF saves only the source and XREF sections

,LISTER=OFFSET saves all of the listing up to and including thetable of offsets

The specification in this example saves the entire listing foronline display and does not print any portion of the listing.

ORDEDIT,LISTER=ALL,CUTPRINT=ALL

Notes:

� If only the LISTER parameter is specified, it mustimmediately follow the program name.


PL/I Programs




You can also request that any saved symbolic data for thisprogram be marked as nonpurgable. If a program's data ismarked as nonpurgable, the data will not be removed from theSymbolic File when deleting programs using a purge intervalbatch run. However, the data can be deleted by program name.See the “Symbolic File Maintenance” chapter for instructionson deleting data from the Symbolic File.

To mark data as nonpurgable, add this keyword to theparameter statement as the last option:

,NOPURGE

The parameter specification in the following example records thesymbolic references for the program ORDEDIT, prints thelisting, does not save any portion of the listing, and does notallow symbolic data to be removed from the Symbolic File by apurge interval batch run.

ORDEDIT,NOPURGE

The parameter specification in the following example records thesymbolic references for the program ORDEDIT, does not print acopy of the listing, does not save any portion of the listing, anddoes not allow symbolic data to be removed from the SymbolicFile by a purge interval batch run.


The parameter specification in the following example records thesymbolic references for the program ORDEDIT, does not print acopy of the listing, saves the entire output listing for onlinedisplay, and does not allow symbolic data to be removed fromthe Symbolic File by a purge interval batch run.

ORDEDIT,CUTPRINT=ALL,LISTER=ALL,NOPURGE

PL/I Programs



PL/I JCL Example

All changes to the normal compile procedure are indicated by ->.

//INTRSYMP JOB ...//*//* YOUR EXISTING CICS PREPROCESSOR JCL GOES HERE//* WHEN DOING A COMMAND LEVEL COMPILE////* YOUR EXISTING PL/I COMPILER JCL GOES HERE//* WITH THE FOLLOWING MODIFICATIONS//*

1-> //SYSPRINT DD DSN=&&INPUT,DISP=(MOD,PASS),UNIT=SYSDA,1-> // SPACE=(CYL,(1,1)),DCB=BLKSIZE=5000

//*//* IF THE COMPILER GIVES A RETURN CODE LESS THAN 9,//*//* THEN RUN THE CA-INTERTEST POST-PROCESSOR STEP//*

2-> //GENPARM EXEC PGM=IN25PARM,PARM='PARAMETER STATEMENT'2-> //STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR2-> //CARDS DD DSN=&&CARDS,DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(1,1))

//*//POSTPLI EXEC PGM=IN25SYMP,REGION=2048K,COND=(9,LT,PLI),// PARM='NOREPORT'//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//INPUTT DD DSN=&&INPUT,DISP=(OLD,PASS)//MSGS DD SYSOUT=*//MESSAGE DD SYSOUT=*//SYSPRINT DD SYSOUT=*//PLIDUMP DD SYSOUT=*

3-> //CARDS DD DSN=&&CARDS,DISP=(OLD,DELETE)//*//*//* YOUR EXISTING LINKAGE-EDITOR JCL GOES HERE//*

//* IF THE COMPILER GIVES A RETURN CODE HIGHER THAN 9//* THEN RUN AN IEBGENER TO PRINT THE PL/I LISTING//*//GENP EXEC PGM=IEBGENER,COND=(9,GT,PLI)//SYSPRINT DD SYSOUT=*//SYSIN DD DUMMY//SYSUT1 DD DSN=&&INPUT,DISP=(OLD,DELETE)//SYSUT2 DD SYSOUT=*//*


PL/I Programs



The following are the JCL modifications that must be made toyour existing compile procedure:

1. Specify the //SYSPRINT data set in the PL/I compiler step.

2. Insert a new job step to execute the CA-InterTest programafter the compiler step.


1. Remove all of the statements in the previous example thatare marked with a 2->.



to:

3-> //CARDS DD *


Modifying CA-InterTest for CICS Options 7–1


Chapter

7Modifying CA-InterTest forCICS Options

The various option settings are described in this chapter, alongwith their defaults and how to change them.

Procedure for Modifying Options

CA-InterTest for CICS installation options are contained in theIN25OPTS load module. You can change option settings easilyby changing the load module without recompiling CA-InterTestprograms. To change a CA-InterTest option, follow these steps:

� Create an IN25OPTS load module that contains the modifiedoptions with a batch assemble-and-linkedit job (sample JCLfollows).

� Activate the changes by performing these steps:

1. Turn off CA-InterTest

2. Issue this command:

CEMT SET PROG(IN25*) NEWCOPY

Note: Ignore any failures of IN25HOOK to newcopy.

3. Restart CA-InterTest




Option Defaults The option defaults used in the pregenerated version ofCA-InterTest Version 6.0 are listed in the following table:

Option=Default Value Option=Default Value

AUDIT=NO IPLXT=IPLX*

AUTMON=YES IRCTT=VIRC*

BREAK=YES ISERT=ISER*

CICSPLEX=NO ITSTT=ITST*

CKPTFIL=PROTCPF LETSVC=YES

CNTLSEC=YES LISTT=LIST*

CNTLT=CNTL* MONOM=NO

CNTOSEC=YES MONOMSEC=YES

CNTSQLG=YES OSGETM=YES

CORET=CORE* PROMD=00000020

CORSEC=YES READBUF=YES

CPF11=7B REALIA2=NO

CPLXCKPI=0020 RECNTMU=NO

CPLXFMID=INTERTST RECNTNW=YES

CWALET= no value SLB=YES

DFLTUSER=.ANY SLBAKEEP=YES

DL1SIZE=8192 SLBMARG=1

EXTSEC=N SLBSCRL=PAGE

FDISP=FC STBTIT=YES

FFORM=D STBTRN=STB4*

FILET=FILE STUAR=NO




FILSEC=YES SYMDFIL=PROTDMP

FSYMP=PROTFILE SYMDINT=YES

GLOG=CSSL SYMDT=SYMD*

HELPFIL=PROTHLF SYMFIL=PROTSYM

HELPT=HELP* SYMPSWD=12345678

ICMDBUF=1024 UCONLY=YES

ICMDEXE=50 USERHELP=PROTUHF

ICMDMAX=50 VERCOR=NO

IGLUT=IGLU* VRPTT=VRPT*

VTATT=VTAT*

*If you change a transaction ID, also change the CICS transactiondefinition.

Sample JCL to Assemble the Options Program



Sample JCL to Assemble the Options Program

The following example shows the JCL needed to assemble theCA-InterTest Options Program (IN25OPTS).

//IN25OPTS JOB//************************************************************//* IN25OPTS SAMPLE JCL *//************************************************************//ASM EXEC PGM=IEV90,REGION=1M,// PARM='LIST,XREF(SHORT),DECK,NOOBJ'//SYSPRINT DD SYSOUT=*//SYSPUNCH DD DSN=&&OBJECT,UNIT=SYSDA,DISP=(NEW,PASS),// DCB=BLKSIZE=3200,SPACE=(TRK,(1,1))//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR// DD DSN=CICS.MACLIB,DISP=SHR//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(1,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(1,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1))//SYSIN DD **** CWA USER DSECT REQUIRED HERE IF USING THE CWALET OPTION *** USING CWADS,0 CA-INTERTEST REQUIREMENTCWADS DSECT USER CWACWAFLD1 DS CL20CWAFLD2 DS CL15CWAFLD3 DS CL100******** CA-INTERTEST OPTION SPECIFICATIONS********************** IN25OPTS TYPE=CSECT, X FILSEC=YES, X LETSVC=NO IN25OPTS TYPE=CSECT, X CWALET=(CWAFLD1,CWAFLD2+15) IN25OPTS TYPE=FINAL END/*//LKED EXEC PGM=IEWL,PARM=(XREF,LIST,MAP),// REGION=1M,COND=(4,LT,ASM)//SYSPRINT DD SYSOUT=*//SYSLIN DD DSN=&&OBJECT,DISP=(OLD,DELETE)//SYSLMOD DD DSN=CAI.CACICSxx(IN25OPTS),DISP=SHR//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(1,1))//

In this example, the options FILSEC, LETSVC, and CWALET havebeen generated. All other options use the default settings. In theSYSLMOD DD statement, replace xx with your two-digit CICSrelease number (for example: 41 for CICS 4.1, 52 for CTS 1.2, or 53for CTS 1.3).

IN25OPTS Keywords



Note: The CWALET option requires you to place your userCWA DSECT before the first IN25OPTS specification in theassembly. The USING statement for this DSECT is required.The register value for the USING statement can be any valuefrom 0 to 15.

IN25OPTS Keywords

This section lists the IN25OPTS keywords. Defaults areunderlined. Slashes (/) between parameters indicate you mustmake a choice.

AUDIT= NO/YES For auditing purposes, certain installations require that allCORE, FILE, and CNTL commands be recorded.

No Specify No if you did not specify the GLOG= option or ifyou want to dynamically activate and deactivate globallogging with CNTL=GLOG,ON and CNTL=GLOG,OFFcommands.

If you specify No, the user can request logging of FILEcommands by specifying FUNC=LOG on the FILEmenu.

Yes Specify Yes if you specified the GLOG= option and youneed the global logging facility always active.

With AUDIT=YES, neither the CNTL=GLOG,ONcommand nor the CNTL=GLOG,OFF command areaccepted. The CNTL commands and CA-InterTestresponses are always recorded in the transient dataqueue or data set that was specified with the GLOG=keyword. CORE changes to storage areas not owned bythe task (usually password protected) are alwaysrecorded. The FILE transaction operates in theLOG=ON mode; that is, all user requests and resultingFILE screen images are recorded.

Note: If you do not specify the GLOG= keyword, theAUDIT=YES specification is ignored.

IN25OPTS Keywords



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

Yes Creates a new Monitor Table entry for a program whenan automatic breakpoint is about to occur if the programis being monitored under a Monitor Table entry thatdoes not name this program by its full name (forexample, if the entry names a transaction). The newentry 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.

BREAK=YES/NO Indicates whether CA-InterTest is allowed to executebreakpoints.

Yes Allows CA-InterTest to execute breakpoints; that is, tostop execution of the application program at certainpoints. Select this option if you intend to useCA-InterTest as an interactive debugging tool.

No Does not allow CA-InterTest to execute breakpoints.This option might be desirable in a separate version ofCA-InterTest used solely for monitoring productionapplications. CA-InterTest generated with BREAK=NOmonitors with less overhead, which is important inproduction.

Instead of causing automatic breakpoints, CA-InterTestabnormally terminates transactions with a transactiondump when it detects a standards violation. Theabend/dump code is INTE. The dump contains all ofthe usual diagnostic information.

IN25OPTS Keywords



CICSPLEX=YES/NO CA-InterTest provides special support for CICS regionsparticipating in a CICSPlex environment. ParticipatingCICSPlex regions have CA-InterTest commands propagatedacross all regions in the CICSPlex. For details on using thisoption, see the section CICSPlex Support.

Yes Indicates that this CICS region is participating in at leastone CICSPlex family of regions, as named in theCPLXFMID keyword. Invokes CA-InterTest CICSPlexprocessing by using CAICCI.

If CICSPLEX=YES, CAICCI processing must be installedon the OS/390 operating system and available to CICS.

No Indicates that this CICS region is not participating in aCICSPlex family.

CKPTFIL=PROTCPF/filename

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

CNTLSEC=YES/NO Indicates whether certain CNTL commands can be protectedwith a password.

Yes Protects certain CNTL commands with a password andallows for password protection of certain CNTL options.Specify CNTLSEC=YES if the CNTL command functionsshould be available only to authorized personnel. WithCNTLSEC=YES, the keyword CNTOSEC furtherspecifies whether the subset of CNTL options shouldalso be password protected.

The passwords are defined in the IN25SEC2 macros. Seethe chapter “Password Protection with CA-InterTestfor CICS” for the list of CNTL commands and optionssubject to password protection and details on specifyingpasswords using IN25SEC2.

With CNTLSEC=YES, you must use the IN25SEC2macro to generate the CA-InterTest program IN25SEC2or use the IN25SEC2 delivered with CA-InterTest.

IN25OPTS Keywords



No Does not protect certain CNTL commands withpasswords and does not allow for password protectionof certain CNTL options.

CNTLT= CNTL/transaction-id

Specify a four-character transaction ID for the CA-InterTestCNTL transaction. Be sure to adjust the CICS transactiondefinition if you do not use the default.

Note: The CICS restriction that no user transaction ID beginwith the character C is not strict. IDs such as CNTL and COREcan be used if the CICS system does not use them.

CNTOSEC=YES/NO When the value for the keyword CNTLSEC is YES, specify thiskeyword to include or exclude certain CNTL options frompassword protection. When CNTLSEC=NO, this keyword isignored.

Yes Protects certain CNTL options with a password. Thepassword is defined in an IN25SEC2 macro, as discussedin the chapter “Password Protection with CA-InterTestfor CICS.”

No Does not protect any CNTL options with passwords.

CNTSQLG=YES/NO Indicates whether CNTL commands are logged.

Yes Logs CNTL commands executed from a sequentialterminal and responses to them into the transient datadestination defined in the GLOG option.

No Does not log CNTL commands.

CORET=CORE/transaction-id

Specify a four-character transaction ID for the CA-InterTestCORE transaction. Be sure to adjust the CICS transactiondefinition if you do not use the default.

Note: The CICS restriction that no user transaction ID beginwith the character C is not strict. You can use IDs such as CNTLand CORE if the CICS system does not use them.

IN25OPTS Keywords



CORSEC=YES/NO Indicates whether a password is required to modify a mainstorage area protected by CA-InterTest.

Yes Requires a password when a user of the CORE facility isabout to modify a main storage area that is protected byCA-InterTest, but does not require the password duringnormal debugging. Specify CORSEC=YES if you willuse the CA-InterTest IN25SEC2 macro to generate apassword that would prevent the CORE facility frombeing used by unauthorized personnel.

The IN25SEC2 macro must be used to generate theCA-InterTest program IN25SEC2 or use the IN25SEC2delivered with CA-InterTest. The use of the IN25SEC2macro is described in the “Password Protection withCA-InterTest for CICS” chapter.

Without the password, the CORE transaction lets youmodify only those storage areas that belong to a taskthat is waiting in a breakpoint and are not protected byCA-InterTest from being modified by the monitoredprogram.

No Does not require a password before allowingmodification of any field within the CICS region in mainstorage.

See the description of the CORE transaction in theCA-InterTest for CICS User Guide. The CORSECspecification also applies to data modification in theLIST Keep window.

Note: Regardless of the CORSEC= specification, thefollowing main storage areas are not available formodification by the CORE transaction:

� CICS/VS Sign-on Table (DFHSNT)

� Main storage outside of the CICS region

IN25OPTS Keywords



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

7B Allows application programmers to use the PF11 key onthe Detailed Breakpoint screen to tell CA-InterTest toforce the execution of any error condition thatCA-InterTest has detected even though the errorcondition that caused the automatic breakpoint stillexists. In effect, the user tells CA-InterTest that this isreally not a violation and to execute regardless of theconsequences.

Before enabling this facility, be aware of theseconsiderations:

� As a result of this execution, not only the testedtransaction's data could be damaged but otherconcurrent transactions could also be affected andthe entire CICS system may crash.

� Using PF11 ignores not only the immediate errorcondition, but also all subsequent error conditionsuntil the next breakpoint or CICS Service Request(whichever comes first).

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

CPLXFMID=INTERTST/CICSPlex-familyname

Defines a CICSPlex family name to be associated with the CICSregion.

Yes Defines an eight-character CICSPlex family nameassociated with the CICS region. The same family namemust be given to all CICS regions participating in thatfamily to obtain CICSPlex support throughout thefamily.

CA-InterTest supports multiple CICSPlex familieswithin or across multiple OS/390 regions. For example,all regions associated with CPLXFMID=REGIONAparticipate in one CICSPlex family, while all regionsassociated with CPLXFMID=REGIONB participate inanother.

No Disregards this keyword; the default.

IN25OPTS Keywords



CPLXCKPI=0020/hhmm

If CICSPLEX=YES and the checkpoint facility is started by aCICSPLEX resynchronization request, defines the time intervalin hours (HH) and minutes (MM) between checkpoints.

CWALET=( )/(label,label)

Specify the CWALET keyword only if you want to removeCA-InterTest storage protection from certain CWA fields.

Important! The storage fields specified with this keyword areunprotected for all programs that run under CA-InterTest monitoring;all programs are permitted to modify these fields.

If you choose to specify one or more CWALET areas, you mustcode a separate IN25OPTS TYPE=CSECT macro for eachCWALET area (one area per macro).

IN25OPTS macros with CWALET must follow other IN25OPTSmacros except for the TYPE=FINAL macro, which must be thelast one.

no value CA-InterTest protection will not be removed. Usethe CSA= and LET= online options to let specificmonitored programs modify additional areas ofmain storage. See the CA-InterTest for CICS UserGuide for details about online options.

(label,label) Specify two Assembler labels, separated by acomma and enclosed in parentheses; for example,CWALET=(CSAUTA1,CSAUTA4). The first labeldefines the first byte of the area to beunprotected; the second label defines the firstbyte past the area.

When using labels, they must be defined in the DSECT for theCWA and inserted in the IN25OPTS compile; see the sectionSample JCL to Assemble the Options Program for details.

If your CWA has an existing DSECT, use existing labels andoffsets from the labels to define the unprotected area.

IN25OPTS Keywords



If you do not have an existing DSECT in your CWA, add thefollowing two statements to the IN25OPTS module to create one:

*********** CWA USER DSECT REQUIRED HERE ************ USING CWADS,0 CA-INTERTEST REQUIREMENTCWADS DSECT USER CWA************** CA-INTERTEST SPECIFICATIONS *********

You can then specify offsets from the beginning of the CWA.For example, the following macro unprotects a 20-byte areastarting at the beginning of the CWA:

IN25OPTS TYPE=CSECT,CWALET=(CWADS,CWADS+20)

DL1SIZE=8192/nnnnn Specifies the number of bytes in the largest DL/I segment to beretrieved using the CA-InterTest FILE facility. Storagecorruption may occur if the size specified here is smaller than aDL/I segment that is retrieved using FILE.

DFLTUSER=.ANY/SPECIFIC/BACKGROUND

DFLTUSER stands for default user and controls howCA-InterTest monitoring functions by default. A user canoverride the default settings established by this parameter atany time.

.ANY When this setting is used, CA-InterTest monitoringpays no attention to the CICS user ID of thesession, even if the user is signed on to CICS.Monitoring is set for all users, and breakpoints, bydefault, are directed to the same terminal used toset them. DFLTUSER=.ANY keeps CA-InterTestmonitoring the same as it was in Versions 5.3 andbelow.

SPECIFIC This setting is only valid in a secure CA-InterTestregion where the users log on to CICS. WhenDFLTUSER=SPECIFIC is used, CA-InterTestqualifies each monitoring entry with the user’sCICS user ID. In addition, CA-InterTest directs alloptions to monitoring to .ANY terminal. Thissetting allows many users to test the same programor transaction independently. This also allowsusers to move from terminal to terminal and havetheir monitoring entries and monitoring optionsfollow them.

IN25OPTS Keywords



Important! When DFLTUSER=SPECIFIC is usedand a user does not sign on to the CICS region,CA-InterTest uses the value of the CICS DFLTUSERfor the monitoring entry. The CICS default user ID isoptionally specified in the SIT parameters. If notspecified in the SIT, its value is CICSUSER.

BACKGROUNDThis setting is only valid in a secure CA-InterTestregion where the users log on to CICS. Code this ifyour CICS system is used predominantly as anApplication Server, where most transactions arenot attached to terminals (that is, web interfacetransactions). This setting sets the FROM terminalto .ANY, and the breakpoint (TO) terminal to thecurrent terminal that is setting the breakpoints.

EXTSEC=YES/NO Indicates whether the External Security Manager is to be used.

Yes CA-InterTest and CA-SymDump for CICS call theExternal Security Manager to verify access to securedfunctions.

Note: For details regarding CA-SymDump for CICScalls to external security, see the CA-SymDump forCICS Getting Started.

No CA-InterTest and CA-SymDump for CICS bypass thecalls to the External Security Manager. When firstinstalling CA-InterTest and CA-SymDumpfor CICS, thissetting is useful until the product is tested and thesecurity rules are written.

IN25OPTS Keywords



FDISP=FC/DL/TD/TS/DB

Determines the default menu for the FILE transaction. Thevarious menu types are described in the CA-InterTest for CICSUser Guide. The user can change the menu of the FILE facilityonline at any time.

FC The FILE transaction shows its first display in theDATATYPE=FC format; that is, ready to process CICSfiles defined in the CICS file definition (File ControlTable).

DL The FILE transaction shows its first display in theDATATYPE=DL format; that is, ready to process DL/Isegments.

TD The FILE transaction shows its first display in theDATATYPE=TD format; that is, ready to process CICStransient data queues.

TS The FILE transaction shows its first display in theDATATYPE=TS format; that is, ready to process CICStemporary storage.

DB The FILE transaction shows its first display in theDATATYPE=DB format; that is, ready to process DB2data.

FFORM=D/C/V/S Determines the default format in which the FILE transactiondisplays the data. The user can change the format of the FILEdisplay online at any time. For illustrations of FILE displays, seethe CA-InterTest for CICS User Guide.

D The FILE transaction shows its first display in dumpformat, similar to the nonstructured display of the COREtransaction. Shows both character and hexadecimalimages.

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

V The FILE transaction shows its first display in verticalformat, similar to the DITTO utility. This formatdisplays the least amount of data.

IN25OPTS Keywords



S The FILE transaction shows its first display in structuredformat if symbolic information for the programcontaining the structures is stored in the CA-InterTestSymbolic File. COBOL and PL/I structures use 01 levelnames; Assembler structures use DSECT names. Showsboth character and hexadecimal images. See the FSYMPoption.

FILET=FILE/transaction-id

Specify a four-character transaction ID for the CA-InterTestFILE transaction. Be sure to adjust the CICS transactiondefinition if you do not use the default.

FILSEC=YES/NO Indicates whether passwords are needed to use the FILEtransaction.

Yes The CA-InterTest IN25SEC2 macro generates passwordsto prevent the FILE transaction from being used byunauthorized personnel. More comprehensive securityenforcement has to be implemented on the CICS level oron the operating system level.

With FILSEC=YES the IN25SEC2 macro must be used togenerate the CA-InterTest IN25SEC2 program, or use theIN25SEC2 delivered with CA-InterTest. Failure to do sowill make the FILE transaction useless. Using theIN25SEC2 macro is described in the “PasswordProtection with CA-InterTest for CICS” chapter.

No Permits users of the FILE transaction to access any CICSfile or DL/I data without a CA-InterTest-enforcedpassword.

FSYMP=PROTFILE/symbolic-programname

Specify the name of the default dummy COBOL or PL/Iprogram that contains all of the 01 level structures used at thesite or the Assembler program that contains all the DSECTs.Symbolic information for this program must be stored in theCA-InterTest Symbolic File.

Users of the FILE transaction requesting records or DL/Isegments in structured format must specify the symbolic nameof the program that contains the structure. However, if a defaultprogram containing all of the structures has been compiled orassembled, users can omit the symbolic program name.

IN25OPTS Keywords



See the “Additional CA-InterTest for CICS CustomizationProcedures” chapter for a sample default COBOL program. TheAdding Assembler DESCTs to the Symbolic File section in thatchapter describes how to add Assembler file structures.

GLOG=CSSL/DCT-destination-id

Specify a four-character name of a transient data destination inthe CICS Destination Control Table (DCT). The default,GLOG=CSSL, provides the statistics destination that is alwayspresent in the CICS system and is usually printed when theCICS system is terminated.

The destination must specify a direct or indirect extrapartitiontransient data set that has a record size of at least 84 bytes(variable-length format, including the length field).

CA-InterTest 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 thedescription of the CA-InterTest global logging facility in theCA-InterTest for CICS User Guide.

HELPFIL=PROTHLF/filename

Specify the file name for the CA-InterTest Help file. The namecannot exceed seven characters. Be sure to adjust the CICS filedefinition if you do not use the default.

HELPT=HELP/transaction-id

Specify a four-character transaction ID for the CA-InterTestonline HELP transaction. If you change the transaction ID, alsochange the CICS transaction definition.

ICMDBUF=1024/nnnnn Defines the size of the work area used to store an indirectcommand. This number should be equal to or greater than thelargest single indirect command you expect your applicationprograms to specify. The default, 1024, should be adequate. Ifthe value of this parameter is too small, message CAIN1256displays when specifying an indirect command.

ICMDEXE=50/nnnn Defines the maximum number of indirect commands that canbe executed for a single indirect command breakpoint. Thisparameter prevents indirect command logic loops. MessageCAIN1266 displays when this value is exceeded.

IN25OPTS Keywords



ICMDMAX=50/nnnn Defines the maximum number of indirect commands that canbe defined for a program. CAIN1259 displays when this valueis exceeded.

IGLUT=IGLU/transaction-id

Specify a four-character transaction ID for the CA-InterTestIGLU transaction, which lists the installed global user exits. Ifyou change the transaction ID, also change the CICStransaction definition.

IPLXT=IPLX/transaction-id

If CICSPLEX=YES, specify a four-character transaction ID forthe task that performs CAICCI RECEIVE ANY processing in aCICSPlex environment. IPLX is a long-running task that runswithout a terminal. This task must not be purged. It is endedby terminating CA-InterTest. If you change the transaction ID,also change the CICS transaction definition.

If CICSPLEX=NO, the default, this task does not run.

IRCTT=VIRC/transaction-id

Specify a four-character transaction ID for the CA-InterTestVIRC transaction. This is an internal CA-InterTest transactionused only for handling breakpoints. Its use must not beprotected by a specific signon. If started by mistake from aterminal, the transaction program does nothing.

In an MRO or ISC environment, the VIRC transaction must beinstalled as local in all Terminal Owning Regions andApplication Owning Regions that use CA-InterTest.

In a CICS environment that does not use MRO or ISC, the VIRCtransaction must be installed to support automatic single-stepping.

Note: If you change the transaction ID, also change the CICStransaction definition.

ISERT=ISER/transaction-id

Specify a four-character transaction ID for the internalCA-InterTest ISER transaction. Do not assign protection to aspecific user.

IN25OPTS Keywords




ITSTT=ITST/transaction-id

Specify a four-character transaction ID for the CA-InterTestITST transaction. This transaction displays the CA-InterTestPrimary Option menu from a CICS prompt. Do not assignprotection to a specific user.


LETSVC=YES/NO Indicates 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 SVCsexcept:

SVC 11 (hex 0B) - TIME macro

These are the SVCs often used implicitly in applications, but anyother SVCs should not be used in CICS programming.

Note: Regardless of this keyword, you can use BYP= optionsduring a CA-InterTest test session to permit the monitoredprogram to use SVCs.

LISTT=LIST/transaction-id

Specify a four-character transaction ID for the CA-InterTestLIST transaction (viewing of the compile or assembly listing).Be sure to adjust the CICS transaction definition if you do notuse the default.

IN25OPTS Keywords



MONOM=MENU/NOMENU/NO

Controls the availability of the segmented monitoring options(MON and NOM) in the CNTL facility. Security forsegmented monitoring is available through the MONOMSECkeyword.

Menu Activates the feature and displays the MON andNOM options on the CNTL main menu.

Nomenu Activates the segmented monitoring feature, butlimits users to implementing segmentedmonitoring through CNTL commands or the LISTfacility. NOMENU disables the use of the MONand NOM options on the Monitoring menus, andremoves the MON and NOM entries from theCNTL main menu.

No Deactivates the segmented monitoring feature andremoves any previous MON and NOM entriesfrom the CNTL main menu.

MONOMSEC=YES/NO Controls password protection for the segmented monitoringoptions in the CNTL facility. If MONOM=NO, MONOMSEC isignored.

Yes Implements password protection of the segmentedmonitoring feature. The password is controlled by akeyword in the IN25SEC2 macro. Instructions forspecifying passwords for CNTL options are in the“Password Protection with CA-InterTest for CICS”chapter.

No Permits the use of the segmented monitoring featurewithout password protection.

IN25OPTS Keywords



OSGETM=YES/NO Indicates whether a GETMAIN SVC is allowed to be issued.

Yes Permits COBOL programs monitored by CA-InterTest toissue the GETMAIN SVC. As suggested by the CICSApplication Programmer's Reference Manual, any CICSCOBOL program should be coded so that no COBOLfacilities require a GETMAIN SVC. Such a GETMAINSVC obtains storage from the OSCORE storage pooloutside the storage controlled by the CICS StorageManagement. There is no FREEMAIN if the COBOLprogram terminates. When, eventually, a GETMAINcannot be satisfied, the CICS system will be abended bythe operating system.

OSGETM=YES is implied by the LETSVC=YESspecification.

No Does not permit the GETMAIN SVC to be issued byCOBOL programs. Unless you run software that issuesthe GETMAIN SVC, we recommend that you specifyOSGETM=NO as OS/390 GETMAINs should not bepermitted. With this specification, an automaticbreakpoint will occur when the GETMAIN SVC isdetected. However, OSGETM=NO is overridden byLETSVC=YES.

PROMD=00000020/name/number

The name or the number in this keyword is used for the defaultvalue of the PROM= parameter of the CNTL=STARTcommand.

name Specify the name (up to eight characters) of theCA-InterTest Startup Table that has to be generatedwith the PROMMAC macro. The use of the macro isdescribed in the chapter “Automatically StartingCA-InterTest for CICS.”

number Specify the number to be used as the default value ofthe PROM= parameter of the CNTL=START command,which specifies the initial number of entries in theMonitoring Table. This number must be eightcharacters long. For the initial period of use, thedefault value should suffice.

IN25OPTS Keywords



The number of entries in the table should be no less than thenumber of names to be declared for monitoring. However, forefficiency, allow enough entries at the beginning by specifyingthe PROM= parameter here or in the CNTL=START command.A large number of unoccupied entries use more storage but donot increase the overhead because only occupied table entriesare examined when the table is scanned.

READBUF=YES/NO Indicates whether the read buffer function is suported.

Yes Before sending a breakpoint to a terminal, CA-InterTestissues a read buffer to save the last user screen from thatterminal. If your CA-InterTest demonstration sessionruns successfully, specify Yes.

No You must specify No if all terminals that would be usedby CA-InterTest users run under TCAM or do notsupport the read buffer function. If you do not specifyNo, you must declare the NRB=ON online optionwhenever monitoring is declared.

REALIA2=YES/NO/ONLY

Indicates whether CA-Realia II Workbench for OS/390 CICS isactive in the CICS region.

Yes Indicates that both CA-Realia II Workbench for OS/390CICS and CA-InterTest are active in the CICS region.

No Indicates that CA-Realia II Workbench for OS/390 CICSis not active in the CICS region.

Only Indicates that only CA-Realia II Workbench for OS/390CICS is active in the CICS region.

RECNTMU=YES/NO Indicates whether CNTL commands are displayed beforeexecution.

Yes Displays the CNTL commands generated by theCA-InterTest menus just before the commands areexecuted. The user can learn these commands from thescreen and, for efficiency, use them instead of menus.

No Suppresses display of CNTL commands.

IN25OPTS Keywords



RECNTNW=YES/NO Indicates whether CNTL commands are displayed beforeexecution.

Yes Displays the CNTL commands that are automaticallygenerated by CNTL=RESTART or CNTL=NEW,PROG=commands. These appear just before they are executedso that the user can see what is being done.

No Suppresses display of CNTL commands. Specify No ifusers are not interested in these details.

SLB=YES/NO Indicates whether Source Listing Breakpoint displays areavailable..

Yes Uses Source Listing Breakpoint displays for the terminalfrom which the program was declared for monitoring ifthe compile (assembly) listing is available in theCA-InterTest Symbolic File.

No Uses Detailed Breakpoint displays when a program isdeclared for monitoring.

In either case, Source Listing Breakpoint displays can be turnedon or off during the online test session.

Note: The CA-InterTest LIST facility (the online viewing ofcompile and assembly listings prior to program execution) is notaffected by this setting.

SLBAKEEP=YES/NO Specifies the default value for the LIST facility of the AutoKeepdisplay feature. Regardless of this setting, the value can beadjusted online at any time.

Yes Displays items in the Keep window concerning thecurrently highlighted line and any data items you haverequested to be displayed in the Keep Window.

No Displays only the data items you have requested to bedisplayed in the Keep Window.

IN25OPTS Keywords



SLBMARG=1/nn Specifies a decimal number, from 1 to 41, of the default marginvalue on the LIST facility screens for Assembler programs.Regardless of this setting, the Location field of each sourcelisting line is shown. The margin value can be adjusted onlineat any time.

1 Presents the left-most portion of each source listing line.

41 Presents the right-most portion.

28 Suppresses the machine code.

34 Suppresses the machine code and statement numbers.

SLBSCRL=PAGE/HALF/STOP/nnnn

Specifies the default scroll value for the LIST facility (onlineviewing of compile and assembly listings) when the userpresses the PF7 or PF8 keys. Regardless of this setting, thevalue can be adjusted online at any time.

Page Scrolls the display one page.

Half Scrolls the display half a page.

Stop Scrolls the display to the next declared breakpoint.

nnnn Scrolls the display the specified number of lines (1 to9999).

SLBTIT=YES/NO/REGS Specifies the default top portion of the display of the LISTfacility (online viewing of compile and assembly listings); thatis, whether the titles for the options and PF keys should bepresented or not. Regardless of this setting, the value can beadjusted online at any time.

Yes Displays the entire top portion of the display, leavingless space for the source listing.

No Displays only the entry fields and a command line,leaving more space for the source listing. Pressing thePF4 or PF16 key displays the entire top portion so a usercan review the options or PF key assignments.

Regs Displays the same fields as SLBTIT=NO, but alsodisplays the general registers and the condition code at abreakpoint.

IN25OPTS Keywords



STBTRN=STB4/transaction-id

For CA-Stabilize/CICS users, specify a four-charactertransaction ID for the CA-Stabilize/CICS STB4 initializationtransaction. Be sure to adjust the CICS transaction definition ifyou do not use the default.

STUAR= NO/YES Affects breakpoint processing in regard to the TCTTE user area(an area embedded in the TCTTE, whose address is in the fieldlabeled TCTTECIA).

No The contents of the area are not saved for the duration ofthe breakpoint or restored when the task continuesexecution from the breakpoint. There is no need topreserve the data in the area if the breakpoint display isto be sent to another terminal, or if the area is to bemodified (during the breakpoint) only by the personperforming the test. Because command level (EXECCICS) applications rarely use this area, STUAR=NOshould be appropriate.

Also specify STUAR=NO if the area may be affectedduring the breakpoint by a facility other than the testedapplication.

Yes The contents of the area are preserved for the durationof the breakpoint. Specify STUAR=YES if the logic ofthe tested application depends on saving this area whileyour task waits at a breakpoint, and then restoring it toits previous value, possibly with your modifications.

STUAR=YES is desirable if the area can be used duringthe breakpoint and use of the area must not affect thetested program.

IN25OPTS Keywords



SYMDFIL=PROTDMP/filename

For CA-SymDump for CICS users, specify the file name for theCA-SymDump for CICS (the Symbolic Dump option) file. Thisis the name of the file from which dumps can be viewed;CA-SymDump for CICS always writes to the file PROTDMP.The name cannot exceed seven characters. Be sure to adjust theCICS file definition if you do not use the default.

SYMDINT=YES/NO For CA-SymDump for CICS users viewing a Source Listing,this option specifies whether the user can invoke CA-InterTestfunctions for the abended program.

Yes CA-SymDump for CICS users can invoke CA-InterTestfunctions when viewing a Source Listing for an abendedprogram. For example, users can set monitoring, invokethe FILE facility, and perform other CA-InterTestfunctions directly from CA-SymDump for CICS.

No CA-SymDump for CICS users cannot invoke CA-InterTest functions when viewing a Source Listing for anabended program. To invoke CA-InterTest functions,users must access CA-InterTest directly.

SYMDT=SYMD/transaction-id

For CA-SymDump for CICS users, specify a four-charactertransaction ID for the CA-SymDump for CICS transaction thatallows dumps to be viewed online. Be sure to adjust the CICStransaction definition if you do not use the default.

SYMFIL=PROTSYM/file/(file1,file2,....)

Specify the CICS file definition names for the CA-InterTestSymbolic Files. The names cannot exceed seven characters. Ifmore than one name is specified, the names must be separatedby commas and the entire list enclosed in parentheses. Be sureto adjust the CICS file definition if you do not use the default.

This option tells CA-InterTest the CICS file definitions of theCA-InterTest Symbolic Files and their search order for programdata. When monitoring is turned on for a program,CA-InterTest searches the Symbolic Files in the sequencespecified and finds the first occurrence of the program's data.

IN25OPTS Keywords



After that first search, CA-InterTest reads only the file in whichthe program was found to satisfy all symbolic needs. Thiseliminates unnecessary I/Os and reduces response time.

If a programmer recompiles a program and inadvertently placesit in a different Symbolic File, you can use the CA-InterTestinquiry function (CNTL=INQ,SYM=program-name) to browseall the specified Symbolic Files and find all occurrences of theprogram. You can also use this command to match theexecutable module with one of the Symbolic Files.

There is no upper limit to the number of Symbolic Files that youcan specify. However, limit the number of files to reduce theoverhead and the storage required for the VSAM buffers becauseeach CICS file definition must be defined withLSRPOOL=NONE.

SYMPSWD=12345678/character-string

Specify an eight-character password used by the Symbolic Fileutility program IN25UTIL to guard against an inadvertentchange to the Symbolic File. The password generated here willbe required when doing the following utility functions:INITIALIZE, RELOAD, DELETE, or PURGE.

To change the default password, specify any character string upto eight characters long.

UCONLY=NO/YES Determines whether certain terminal output will bedynamically translated from lowercase to uppercase. .

No Terminal output is not dynamically translated.

Yes Terminal output is dynamically translated to uppercasecharacters. If you previously installed the uppercaseversion of the CA-InterTest load libraries because yourterminals did not support the mixed case English characterset, you should specify YES.

USERHELP=PROTUHF/filename

Specify the file name for the optional help file of user-definedabend descriptions. The name cannot exceed seven characters.Be sure to adjust the CICS file definition if you do not use thedefault.

IN25OPTS Keywords



VERCOR=NO/YES Determines whether changes to main storage must be verified.

No Changes to main storage requested in a COREtransaction command can, but need not be, verified inthe same command.

If CORSEC=YES is specified, the user cannot modify anyforeign piece of storage by mistake because the COREtransaction will ask for the password. As a result, youcan specify VERCOR=NO because a careless user canharm only the tested program's data.

Yes Any change to main storage requested in a COREtransaction command must be verified in the samecommand regardless of password protection (see theCORSEC= keyword). This compulsory verificationcould make a debugging session unnecessarily tedious,thus decreasing productivity. The system programmerwill find this specification a hindrance, especially insituations when a certain value must be forced upon anarea whose content continually changes.

See the “Accessing Main Storage: CORE” chapter in theCA-InterTest for CICS User Guide for more information.

VRPTT=VRPT/transaction-id

Specify a four-character transaction ID for the CA-InterTestVRPT transaction used to verify the installation and display theinstallation options. Be sure to adjust the CICS transactiondefinition if you do not use the default.

VTATT=VTAT/transaction-id

Specify a four-character transaction ID for the CA-InterTestVTAT transaction. This is an internal CA-InterTest transactionused only for handling breakpoints. Since it is not used by anyoperator, its use must not be protected by a specific user. Ifstarted by mistake from a terminal, the program does nothing.Be sure to adjust the CICS transaction definition if you do notuse the default.

Additional CA-InterTest for CICS Customization Procedures 8–1


Chapter

8Additional CA-InterTest forCICS CustomizationProcedures

This chapter explains how to further customize CA-InterTest forCICS to meet your site's needs. The following topics arediscussed:

� 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 intercepted—IN25ABEN

� Customizing help for abend codes

Implementing Composite Support

This section describes the set-up procedure required to usecomposite support. Composite support lets users test compositemodules—load modules named in a CICS program definition thatconsist of separately compiled or assembled parts broughttogether when the module is link-edited. The main program andcalled subroutines can be written in the same or differentlanguages. With composite support, users can test and debug asubroutine as if it were a separate program. See theCA-InterTest for CICS User Guide for a detailed description ofthe composite support feature.




Follow these steps for composite support:

1. For symbolic support, compile the main program and eachsubroutine you want to test with the CA-InterTest post-processor. Follow the directions in the “Symbolic Support”chapter.

2. Link-edit the programs and execute the CA-InterTest batchprogram IN25LINK to read the link-edit map and store thenecessary information in the Symbolic File.

Note: Skip Step 1 if you do not want symbolic support.

The IN25LINK program does not change the load module in anyway and can be executed by as many concurrent jobs asnecessary. Concurrent jobs do not interfere with each otherwhen updating the CA-InterTest Symbolic File. It is moreefficient to use the IN25LINK program to obtain necessary link-edit information; however, you can provide the link-editinformation online on the CNTL Composite Support menu.

IN25LINK Program

The IN25LINK program processes the link-editor map after thelink-editor step. Here is how it works:

1. IN25LINK collects information from the link-editor's//SYSPRINT DD statement, which should be declared atemporary sequential data set in the link-editor job stepwith:

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

IN25LINK either appends the collected data to an existingsymbolic program entry or creates a new entry.

2. The temporary data set is passed to the IN25LINK job stepthrough the INPUT DD statement.

3. The original input from the link-editor's //SYSPRINT iswritten to the //OUTPUT DD data set declared in theIN25LINK job step.




4. Messages from the IN25LINK program are written to the//MESSAGE DD statement to be printed.

5. The CA-InterTest Symbolic VSAM File is referenced byIN25LINK through the //PROTSYM DD statement withDISP=SHR.

Specify one or more parameter cards to identify the compositemodule, main program, and any subroutines you want to test.The IN25LINK parameters are passed to the IN25LINK programusing one or more parameter cards.

Identifying the Composite Module

The first parameter card is required. It specifies the CICSprogram definition name of the composite module beginning incolumn 1. The first parameter card has this format:

composite-name[,NOPURGE]

Note: The program name specified in the parameter statementfor the post-processor step must also be the CICS programdefinition name of the composite module. See the “SymbolicSupport” chapter for details.

You can also optionally specify the NOPURGE parameter. Thisparameter specifies that symbolic information for the compositemodule not be purged from the Symbolic File during a purgeinterval batch job.




Identifying the Main Program and Subroutines

Subsequent parameter cards identify the main program and eachsubroutine you want to test separately. These cards can be inany order and must specify two parameters, separated bycommas, in this format:

link-name,monitor-name

link-name identifies the name of the COBOL program,Assembler CSECT, or PL/I Control Section aslisted in the link-edit map. This parametermust begin in column 1.

For a PL/I program, specify the name of theControl Section, generated by the compiler,that ends with '1'.

monitor-name specifies the name under which the program isto be monitored. Follow these rules inselecting a monitor-name:

� Each monitor-name must be unique.

� The monitor-name of the main programmust be the CICS program definition nameof the composite module. However, themonitor-name of a subroutine cannot be aCICS program definition name.

� The monitor-name can be identical to thelink-name.

� If you compiled the main program orsubroutine with the CA-InterTest post-processor, the monitor-name must beidentical to the program name specified inthat job step.

Note: You can omit all but the first parameter card, whichidentifies the composite module.




Excluding Subroutines

By default, CA-InterTest excludes subroutines with DFH, DLZ,ILB, IGZ, and IBM prefixes when it reads the link-edit map.Usually, you will not want to test such programs. However, youcan specify a parameter card to change the default exclusionrules. This parameter card can be positioned anywhere in thecard deck except as the first card, and has this format:

.EXCLUDE=

or

.EXCLUDE=xxxxxxxx[,xxxxxxxx,...,xxxxxxxx]

� The .EXCLUDE= specification must begin in column 1.

� .EXCLUDE= instructs CA-InterTest not to exclude anysubroutines.

� .EXCLUDE=xxxxxxxx instructs CA-InterTest to excludesubroutines whose link-names are represented by xxxxxxxx.Specify the entire link-name to exclude a specific subroutine;specify the beginning portion of the link-name to exclude agroup of subroutines. For example, to exclude allsubroutines with the prefix ACA1, specify.EXCLUDE=ACA1.

Example

A composite module with the CICS program definition nameBIGMOD consists of several separately compiled programs andlibrary modules. Its main program is named MAINMOD and iswritten in COBOL. BIGMOD also has three Assemblersubroutines that you want to test separately: SUBMOD-A,SUBMOD-B, and SUBMOD-C. None of the subroutines has itsown CICS program definition entry.

You have already assembled SUBMOD-A, SUBMOD-B, andSUBMOD-C with the CA-InterTest Assembler post-processorprogram. You specified ASMMOD-A, ASMMOD-B, andASMMOD-C, respectively, as the program names in that job step.




Compile MAINMOD with the CA-InterTest COBOL post-processorprogram and specify BIGMOD as the program name. Next, link-editMAINMOD, SUBMOD-A, SUBMOD-B, and SUBMOD-C and executethe CA-InterTest batch program IN25LINK.

The link-edit map output for BIGMOD indicates an entryaddress of 160 and that BIGMOD now is replaced in the data set,and contains the following:

Control Section Name Origin Length Description

DFHECI 00 160 Command levelCOBOL stub

MAINMOD 160 78A8 Main program—COBOL

ILBOATB 7A08 11A COBOL librarymodule

ILBOCOM0 7B28 73 COBOL librarymodule

SUBMOD-A 7CA0 1200 Subprogram—Assembler

SUBMOD-B 8EA0 100 Subprogram—Assembler

SUBMOD-C 9EA1 93 Subprogram—Assembler

Sample JCL for the link-edit step and CA-InterTest job stepfollows.

Note: The link-names specified on the parameter cards for theCA-InterTest job step are the program names as listed in thelink-edit output.

The following specifications let users set breakpoints andoptions for any of the four programs using the monitor-namesspecified: BIGMOD, ASMMOD-A, ASMMOD-B, andASMMOD-C.




Note: If you are using the link editor DFSM S1.1, you must addPARM (MAP,...) to your execute card.

//*//* LINK-EDIT STEP//*//LKED EXEC PGM=IEWL,......//SYSLIB DD.....//SYSLMOD DD.....//SYSUT1 DD.....//SYSLIN DD.....

1-> //SYSPRINT DD DSN=&&INPUT,DISP=(,PASS),UNIT=SYSDA,1-> // SPACE=(TRK,(2,5)),1-> // DCB=(DSORG=PS,LRECL=121,BLKSIZE=2420,RECFM=FB)

//*//* RUN THE CA-INTERTEST POST-PROCESSOR STEP -//*

3-> //* ADD IN25PARM JCL HERE IF NEEDED//*//* BELOW, THE //STEPCAT MAY BE UNNECESSARY.//*

2-> //POSTASM EXEC PGM=IN25LINK,REGION=512K2-> //SYSUDUMP DD SYSOUT=A2-> //STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR2-> //INPUT DD DSN=&&INPUT,DISP=(OLD,DELETE)2-> //OUTPUT DDSYSOUT=A,DCB=(RECFM=FBA,LRECL=121,BLKSIZE=2420)2-> //MESSAGE DD SYSOUT=A2-> //PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR2-> //CARDS DD *2-> BIGMOD CICS program definition name ofcomposite module2-> MAINMOD,BIGMOD link-name and monitor-name of mainprogram2-> SUBMOD-A,ASMMOD-A link-name and monitor-name ofsubprogram2-> SUBMOD-B,ASMMOD-B link-name and monitor-name ofsubprogram2-> SUBMOD-C,ASMMOD-C link-name and monitor-name ofsubprogram2-> /*

In the STEPLIB DD statement, replace xx with your two-digitCICS release number (for example, 41 for CICS 4.1, 52 for CTS1.2, or 53 for CTS 1.3).




Observe these rules:

� The parameter statement for the post-processor step mustspecify the CICS program definition name of the compositemodule as the program name. In this example this isBIGMOD, so an appropriate parameter statement would be:

BIGMOD,LISTER=ALL

See the “Symbolic Support” chapter for details onspecifying this parameter statement.

� The first parameter card for the IN25LINK job step mustidentify the composite module; for example, BIGMOD.

� The monitor-name of the main program must be the CICSprogram definition name of the composite module; forexample, BIGMOD, as illustrated in the second parametercard.

The following JCL modifications are required to use theIN25LINK program:

� The //SYSPRINT data set in the link-edit step must bemodified.

� A new job step to execute the IN25LINK program is insertedafter the link-editor step.

Note: If you are processing only the first parameter controlcard, you can pass it using a PARM= statement. To use aPARM= statement, add the following JCL at the location markedby 3->:

3-> //GENPARM EXEC PGM=IN25PARM,PARM='PARAMETER STATEMENT'3-> //STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR3-> //CARDS DD DSN=&&CARDS,DISP=(,PASS),UNIT=SYSDA,

// SPACE=(TRK,(1,1))


Declaring User-Defined CORE Commands



Change the following JCL statement:

2-> //CARDS DD *2-> ....2-> .... YOUR PARAMETER CARDS GO HERE2-> ....2-> /*

to read:

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

and add the parameter statement after this JCL statement.


This section explains how to define your own CORE keywords.User-defined CORE keywords provide a shorthand method forentering a complex CORE command by specifying a simplecommand that contains one or more of your own keywords. Thenew keyword is automatically replaced with a string ofcommand elements that could otherwise be difficult toremember.

Among the new commands can be some to display your ownareas in main storage, such as crucial control tables for runningan application system. If your replacement command includesthe USE= element, the storage areas can be displayed as COBOLor Assembler structures, with names and offsets attached to eachdata field.

For details, see the CA-InterTest Help facility. Select the COREFacility, then Structured Data Displays, and then AdditionalFeatures.




The CORUCOM Macro

The CORUCOM macro lets you define any number of newCORE command keywords, each an abbreviation for a series ofCORE command elements. For instance, there is a user table thatis pointed to by an address located eight bytes into the CWA.There is a counter 12 bytes into this table that contains thenumber of times a service request transaction was issued. Addthe following CORUCOM entry and assemble the CORUCOMtable:

CORUCOM CODE=SERVCNT,COMND=CWA@8+C

To display the service request count online, issue:

CORE=SERVCNT

Code one CORUCOM macro for each new CORE keyword.Submit the resulting source code to assemble a newCA-InterTest load module named IN25UCOM. The module isused by the CORE facility as a table to convert your ownkeywords into strings of CORE keywords.

Since the CORUCOM macro generates a separate CICS loadmodule, you can add new or modified commands at any time.To do this, code the commands, assemble the module, and thendo a NEWCOPY for the load module IN25UCOM by issuing:

CEMT SET PROG(IN25UCOM) NEWCOPY

Coding the CORUCOM Macros

The CORUCOM macro is delivered in the CA-InterTest sourcelibrary. The first CORUCOM statement must be coded asfollows:

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

The last CORUCOM statement must be coded as follows:

1 1 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 COREcommands 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 preventconfusion with a hexadecimal number, must contain at least oneof these characters: GHIJKLMNOPQRSTUVWXYZ. When twoor more keywords have the same prefix (for example, ICE2,ICE), the longer keyword must be specified first, as illustrated inthe following example.

The string of CORE command elements is specified by theCOMND= keyword. The string must be enclosed in apostrophesand, within the string, any apostrophe must be coded as twoapostrophes. All elements of the CORE command are permitted,including other user-defined elements.

Example In the next example:

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

� The fourth macro defines the keyword MYTABLE, whichdisplays a storage area pointed to by the address in theCWA, and produces a display formatted as a structurenamed MYTABLE in the CA-InterTest Symbolic File recordsidentified by the name MYSYMDEF. For more details, seethe section Adding Assembler DSECTs to the Symbolic File.




� The * in column 72 means continuation.

1 17 COL=1...5....0.....6............................................2 CORUCOM TYPE=INITIAL (required) CORUCOM CODE=ICE2,COMND='ICE@4' CORUCOM CODE=ICE,COMND='=CSA@54' CORUCOMCODE=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 IBMprocedure 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 yourtwo-digit CICS release number (for example, 41 for CICS 4.1, 52for CTS 1.2, or 53 for CTS 1.3).

Note: The IN25UCOM member of the CA-InterTest sourcelibrary contains sample source for assembling the IN25UCOMload module.

Adding Assembler DSECTs to the Symbolic File




CA-InterTest lets you display the major CICS areas in AssemblerDSECT format. You can also display your own user areas inDSECT format. One way to do this is to add your DSECTs to theones supplied by CA-InterTest. However, if you do this, yourentries will disappear when you install a new release ofCA-InterTest or CICS. A better way is to create one or moreSymbolic File members to contain your DSECTs.

Saving all of the DSECTs used at your site in one Symbolic Filemember allows users of the FILE transaction to omit thesymbolic program name when requesting records or DL/Isegments in structured format. The name of this member mustbe referenced in the FSYMP installation option. The defaultname is PROTFILE.

Follow these steps to create your own Symbolic File members:

1. Run a job to add the members containing the DSECTs to theSymbolic File.

2. Run a job to define the CORE keywords needed to displaythe 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=IEV90,REGION=1024K//SYSLIB DD DSN=USER.SOURCE,DISP=SHR//SYSUT1 DD DSN=&SYSUT1,SPACE=(1024,(120,120),,,ROUND), UNIT=VIO,// DCB=BUFNO=1//SYSPUNCH DD SYSOUT=B//SYSTERM DD SYSOUT=*//SYSPRINT DD DSN=&&TEMP,DISP=(,PASS),UNIT=SYSDA, SPACE=(CYL,(3,2)),// DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)//SYSIN DD *USERTWAF DSECT COPY USERTWAFUSERDSEC CSECT END//*//PARM EXEC PGM=IN25PARM,REGION=512K,// PARM='USERDSEC,LISTER=REF,NOPURGE'//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//CARDS DD DSN=&&CARDS,DISP=(,PASS),UNIT=SYSDA, SPACE=(80,1)//*//SA EXEC PGM=IN25SYMA,REGION=512K//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//INPUT DD DSN=&&TEMP,DISP=(OLD,DELETE)//OUTPUT DD SYSOUT=*, DCB=(RECFM=FBM,LRECL=121,BLKSIZE=2420)//MESSAGE DD SYSOUT=*//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD DSN=&&CARDS,DISP=(OLD,DELETE)/*

In the STEPLIB DD statements, replace xx with your two-digitCICS release number (for example, 41 for CICS 4.1, 52 for CTS1.2, or 53 for CTS 1.3).

See the Assembler section of the “Symbolic Support” chapter for anexplanation of the IN25PARM and IN25SYMA programs.

Note: This job does not require a link-edit step because it onlyupdates the Symbolic File. No load module is produced.




Sample JCL for Defining CORE Keywords

After you have added the necessary members to the SymbolicFile, run a job to define the commands needed to access yourDSECTs. The sample job below uses CORUCOM macros todefine the user CORE keyword TWAF. See the section DeclaringUser-Defined CORE Commands for a detailed explanation.

//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 * 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 DD * NAME IN25UCOM(R)/*//

In the LKED.SYSLMOD DD statement, replace xx with yourtwo-digit CICS release number (for example, 41 for CICS 4.1, 52for CTS 1.2, or 53 for CTS 1.3).

Unprotecting Main Storage with the User Exit IN25LETX



Unprotecting Main Storage with the User ExitIN25LETX

IN25LETX is an optional exit program coded by the user thatspecifies areas in main storage that should not be protected byCA-InterTest. The areas to be unprotected are indicated bybeginning and ending storage addresses.

This exit program provides a programmable function equivalentto the CA-InterTest interactive LET option. This is a particularlyuseful option, because frequently an application program isdesigned to modify a storage area that is protected byCA-InterTest. Ordinarily when that happens, CA-InterTestinitiates an automatic breakpoint and halts the program'sexecution.

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 ofthe application. IN25LETX is invoked each time CA-InterTestbegins monitoring and also when it resumes monitoring, such asafter a CICS command or after any kind of breakpoint.

For CICS 4.1 and above, the interface to IN25LETX is a CICScommand level LINK with a COMMAREA. This allows a user'sIN25LETX module to issue CICS SPI or API commands to locatekey module addresses.

Note: The interface permits IN25LETX to return a variable-lengthtable of pairs to CA-InterTest in a single pass. Previous non-ESAversions of IN25LETX branched to CA-InterTest for each addresspair until all address pairs were passed.




The IN25LETX COMMAREA

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

COMMAREA Field Length Primed By

Table Address Fullword User

Monitored Program 8 bytes CA-InterTest

Application Registers Fullword CA-InterTest

Table Address –This field is set to zeros upon entry to the exit.CA-InterTest assumes it was passed a valid table address if thisfield is modified. Leaving this field set to zeros causesCA-InterTest to remove any address pairs previously set by thisexit for this task.

Monitored Program—Contains the name of the program beingmonitored by CA-InterTest at the time this exit was invoked.

Application Registers—The fullword address of the 16-fullwordarea containing the application's registers (0 to 15) that weresaved just prior to the entry to this exit.

The 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 storagethat will not be protected by CA-InterTest if those areas aremodified by the application. For example, if the area to beunprotected resides at address X'11AA2E0' and is X'2000' byteslong, the address pair is 11AA2E0 and 11AC2E0.

The last entry in the table must contain two fullwords ofX'FFFFFFFF'.




In many cases, the declared addresses may only need to beunprotected for a particular CICS task or program execution.Thus the logic of IN25LETX may need to consider the varyingcircumstances of execution, including:

� Transaction identification

� Terminal identification

� Logical level of execution

� Program identification

IN25LETX must deliver a full table of address pairs each time itis invoked. IN25LETX does not have to be reentrant, meaning itcan contain save areas and tables in which permanent addressescan be stored. There is no need to rebuild the LETX table if theaddresses do not change. In this case, a one-time routine canfind the areas, build the LETX table, and save the table in theIN25LETX module for the next time. IN25LETX can make itselfresident by loading itself again (see the section SampleIN25LETX Program).

IN25LETX can reside above or below the 16 MB line and executein either addressing mode. All table addresses, however, musthave the X'80000000' bit turned off; that is, the addressX'01234567' must not be passed as X'81234567'.

Sample IN25LETX Program

The sample IN25LETX program that follows locates two areas,both permanently resident in storage, which are to beunprotected for all monitored programs running undertransaction code ABCD. The first area is a table pointed to by anaddress in the user's TWA. The second area is a table loaded asa member of the CICS program definition named ATABLE.Both areas are established before CA-InterTest becomes activeand remain resident in main storage.* TITLE 'IN25LETX - CA-INTERTEST LET EXIT - USER CODED' DFHREGS REGISTER EQUATES*DFHEISTG DSECT WORKING STORAGE DSECTXPROGLEN DS F PROGRAM LENGTH




***************************************************************** I N 2 5 L E T X C O M M A R E A *****************************************************************COMMAREA DSECT COMMAREACTBLADDR DS F ADDRESS OF USER LET TABLEINTPROG DS CL8 NAME OF MONITORED PROGRAMINTREGS DS F ADDR OF APPL REGISTERS (0-15)*USERTWA DSECT DSECT FOR USER TWAUTBLADDR DS F ADDRESS OF USER TABLEUTBLLEN DS H 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? BE GETAREAS NO, GO GET THEM LA R1,LTABLE THEN, THE LET TABLE ISBUILT... ST R1,CTBLADDR PUT LET TABLE ADDR IN THECOMMAREA*RETURN EXEC CICS RETURN*GETAREAS DS 0H* EXEC CICS ADDRESS TWA(R5) USING USERTWA,R5* L R1,UTBLADDR GET THE START OF THE TWA AREA N R1,=X'7FFFFFFF' ENSURE HIGH-ORDER BIT ISTURNED* OFF IN USER'S ADDRESS ST R1,LTWATBL STORE THE AREA'S STARTADDRESS AH R1,UTBLLEN ADD THE TABLE LENGTH ST R1,LTWATBL+4 STORE THE AREA'S END ADDRESS* EXEC CICS INQUIRE PROGRAM('ATABLE') LOADPOINT(R0)X LENGTH(XPROGLEN)* ST R0,LPROGTBL STORE THE AREA'S STARTADDRESS A R0,XPROGLEN ADD THE PROGRAM'S LENGTH ST R0,LPROGTBL+4 STORE THE AREA'S END ADDRESS*

Adding COBOL File Structures to the Symbolic File



*********************************************************************** LOAD THIS EXIT AGAIN SO IT WILL NOT HAVE TO REOBTAIN THEADDRESSES ** ON THE NEXT CALL TO THIS EXIT.*********************************************************************** EXEC CICS LOAD PROGRAM('IN25LETX') HOLD* LA R1,LTABLE ST R1,CTBLADDR PUT ADDR OF LET TABLE INCOMMAREA B RETURN*LTABLE DS 0H LET TABLELTWATBL DC 2F'0' ADDRESSES OF TWA TABLELPROGTBL DC 2F'0' ADDRESSES OF PROGRAM TABLELEND DC X'FFFFFFFF' END OF TABLE INDICATOR LTORG END

Disabling IN25LETX

CA-InterTest uses IN25LETX during all monitoring; that is, forall entries of the CA-InterTest monitoring table. To preventCA-InterTest from executing IN25LETX, you must disable it orremove it from the program library.

Once a link to IN25LETX fails (because the program is disabled),CA-InterTest will not try the link again, thus avoiding muchoverhead. In such a case, the execution of IN25LETX will notresume until the next CA-InterTest start.


The COBOL II program shown below is an example of a dummydefault program that contains 01 level structures. Saving all ofthe 01 level structures used at a site in one file allows users of theFILE transaction to omit the symbolic program name whenrequesting records or DL/I segments in structured format.Symbolic information for the default program must be saved inthe Symbolic File, and its name must be referenced in the FSYMPinstallation 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 DD UNIT=SYSDA,SPACE=(460,(350,100))//SYSUT2 DD UNIT=SYSDA,SPACE=(460,(350,100))//SYSUT3 DD UNIT=SYSDA,SPACE=(460,(350,100))//SYSUT4 DD UNIT=SYSDA,SPACE=(460,(350,100))//SYSUT5 DD UNIT=SYSDA,SPACE=(460,(350,100))//SYSUT6 DD UNIT=SYSDA,SPACE=(460,(350,100))//SYSUT7 DD UNIT=SYSDA,SPACE=(460,(350,100))//SYSPRINT DDDSN=&&TEMPIN,DISP=(,PASS),UNIT=SYSDA,SPACE=(TRK,(15,5)),// DCB=(DSORG=PS,LRECL=133,BLKSIZE=1330,RECFM=FBA)//SYSIN DD * ID DIVISION. PROGRAM-ID. PROTFILE. ENVIRONMENT DIVISION. DATA DIVISION. WORKING-STORAGE SECTION. 77 PROGRAM-NAME PIC X(8) VALUE 'PROTFILE'.

LINKAGE SECTION.

** CAR SEGMENT ** 01 CAR. 05 CAR-SEGMENT-KEY-FIELD. 15 CAR-SEGMENT-MAKE PIC X(12). 05 CAR-SEGMENT-MODEL PIC X(12). 05 CAR-SEGMENT-TYPE PIC X(10). 05 CAR-SEGMENT-WEIGHT PIC S9(5) COMP-3. 05 CAR-SEGMENT-CYLINDRS PIC S9(3) COMP-3. ** DEALER SEGMENT ** 01 DEALER. 05 CAR-DEALER-SEGMENT-KEY. 15 CAR-DEALER-SHORT-NAME PIC X(9). 15 CAR-DEALER-TIEB PIC S999 COMP-3. 15 CAR-DEALER-NBRWD PIC S9 COMP-3. 05 CAR-DEALER-FIRST-NAME PIC X(24).

PROCEDURE DIVISION. MOVE 'PROTFILE' TO PROGRAM-NAME. GOBACK.//*//SYMSTEP EXEC PGM=IN25COB2,REGION=1024K//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//INPUT DD DSN=&&TEMPIN,DISP=(OLD,DELETE)//OUTPUT DD SYSOUT=A,DCB=(RECFM=FBA,LRECL=133,BLKSIZE=1330)//MESSAGE DD SYSOUT=A//PROTSYM DD DSN=** your protsym file **,DISP=SHR//CARDS DD *PROTFILE,LISTER=ALL,NOPURGE//*

Specifying Abend Codes That Should Not Be Intercepted




Note: A similar job can be used for COBOL/VS.

Specifying Abend Codes That Should Not BeIntercepted

If certain abend codes should not be intercepted regardless of theCA-InterTest Automatic Breakpoint (ABI) setting, use theIN25ABEN macro to specify the codes. CA-InterTest provides adefault IN25ABEN that includes the abend codes AKC3, ATNI,ATCV, and AEXY.

Note: AKC3 is needed to run CA-InterTest with CA-Verify.

To specify your own codes in the IN25ABEN macro, code themacro as described in the following sample IN25ABEN sourcecode assembly:

//ASSEMBLE.SYSIN DD * IN25ABEN TYPE=INITIAL IN25ABEN ABCODE=(ATNI,ATCV,AEXY) IN25ABEN ABCODE=AKC3 IN25ABEN ABCODE=(AKCT,APLE) IN25ABEN ABCODE=(1234,'# Q$',1UMF) IN25ABEN TYPE=FINAL END/*

IN25ABEN CodingRules

Follow these rules when coding IN25ABEN:

� IN25ABEN TYPE=INITIAL must be coded first.

� The ABCODE= parameters must specify four-characterabend codes. The abend codes ATNI, ATCV, and AEXYmust be included. Include the code AKC3 if you arerunning CA-InterTest with CA-Verify.

� If ABCODE specifies a list of abend codes, then separate thecodes with commas and enclose the list in parentheses.

Specifying Abend Codes That Should Not Be Intercepted



� Codes that include spaces or special characters must beenclosed in single quotes.

� IN25ABEN TYPE=FINAL terminates the table.

� END terminates the assembly source.

After coding the macro, assemble the source code according tothe following sample JCL. The following JCL example assemblesthe IN25ABEN source code. Modify this example to meet yoursystem requirements.

//IN25ABEN JOB ...//ASM EXEC PGM=IEV90,REGION=1024K,// PARM='DECK,LIST,XREF(SHORT),ALIGN'//SYSPRINT DD SYSOUT=A//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,//DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSIN DD * IN25ABEN TYPE=INITIAL IN25ABEN ABCODE=(ATNI,ATCV,AEXY) IN25ABEN ABCODE=AKC3 IN25ABEN ABCODE=(AKCT,APLE) IN25ABEN ABCODE=(1234,'# Q$',1UMF) IN25ABEN TYPE=FINAL END/*//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)//SYSLMOD DD DSN=CAI.CACICSxx(IN25ABEN),DISP=SHR//SYSUT1 DD UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))//SYSPRINT DD SYSOUT=A//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)

In the SYSLMOD DD statement, replace xx with your two-digitCICS release number (for example, 41 for CICS 4.1, 52 for CTS1.2, or 53 for CTS 1.3).

Customizing Help for Abend Codes




You can customize the help text displayed at an automaticbreakpoint for abend codes. A separate help file, PROTUHF, isavailable to hold your user-defined abend code descriptions.This file must be created as explained in the section Step 11a.Create the User Help File (Optional) in the “Base ProductInstallation Steps” chapter.

After installation, the online Abend Code Maintenance menu(ITST Option 7.2) lets you add, inquire, update, and deleteentries in the user-defined help file. Press PF1 from this menu toobtain help on using the facility.

--------------- CA-InterTest 5.4 ABEND CODE MAINTENANCE MENU ---------------- OPTION ===>

Enter Option, Abend code, and Program name; then press enter.

1 Add - Add an Abend code/Program name 2 Inquire - Inquire on an Abend code/Program name 3 Update - Update an Abend code/Program name 4 Delete - Delete an Abend code/Program name

Abend code . . ____ Program name . . ________

PF1 Help 2 3 End 4 Return 5 6 PF7 8 9 10 11 12

You can tie an abend code to a specific program by entering boththe abend code and program name fields. You can create ageneric abend code for all program names by entering the abendcode only, with no program name.

During a user session when CA-InterTest intercepts an abend, itfirst searches for a matching abend code entry on the user-defined help file. If a description for the abend code is found onthe user-help file, CA-InterTest displays its contents at thebreakpoint and on related CA-SymDump analysis displays.




If there is no user-defined description or if the user file does notexist, then the abend code description from the CA-InterTesthelp file is used. If there is no abend code description in the CA-InterTest help file, then a default NOTFABCODE is displayed.

Handling Special Situations 9–1


Chapter

9 Handling Special Situations

This chapter discusses how to use CA-InterTest for CICS with:

� MRO

� DB2

� Software invoked by CALLs from your applicationprograms or macros

� Wild branches

� EDF

� HOGAN Software

Special Considerations for MRO Support

To use CA-InterTest in an MRO environment, you must have:

� All CA-InterTest-required CICS definitions in any CICSapplication-owning region (AOR) that will use CA-InterTestfor testing.

� A local program definition for IN25VIRC in the terminal-owning region (TOR).

� A local transaction definition for VIRC in the TOR; thistransaction ID must be identical in the TOR and all AORs.




� One remote transaction definition for VTAT in the TOR foreach AOR that will use CA-InterTest. Of course, the TOR'slocal VTAT transaction IDs must be unique (for example,VTA1, VTA2, VTA3, and so on). However, the remotetransaction IDs can be the same for all AORs (for example,VTAT), so you do not need to maintain a unique IN25OPTSfor each AOR. If you choose to specify an alternate VTATtransaction ID in one or more AORs, you must be sure tospecify the same alternate transaction ID in the TOR'sremote VTAT transaction definition.

In addition, for all CICS regions that will use CA-InterTest—both AOR and TOR—the transaction definition for VIRC mustspecify the same transaction code.

A sample set of definitions is supplied in member CSDINTTO onthe CAI.SAMPLIB. This sample set contains all of the RDOdefinitions required for the CICS TOR region. All CA-InterTesttransaction names are the same as those specified in the AORand can be modified by your site.

Note: We recommend that the CA-InterTest CORE transactionbe installed in the TOR as local to help system support staffresolve problems in that region.

Remote transaction definitions can be defined for all transactionsexcept VIRC, which can be started from the TOR to run in theAOR. Using these transaction definitions is usually preferable tostarting routing sessions with the CRTE SYSID= transaction.

You can add a transaction definition in each TOR.

DEFINE TRANSACTION(LNTL), REMOTENAME(RNTL), REMOTESYSTEM(TROW)

RNTL—a four-character transaction name for the CA-InterTestCNTL transaction in the AOR

LNTL—a four-character transaction name for the CA-InterTestCNTL transaction in the TOR

TROW—the name under which the AOR is known to the TOR




Note: RNTL and LNTL can be the same name.

Monitoring Considerations for DFLTUSER

CA-InterTest qualifies all monitoring entries with a CICS userID. All monitoring entries use the form:

promid.userid

The ATTACHSEC option of the CONNECTION entry in theCSD is used with the DFLTUSER= option setting in IN25OPTSto provide the granularity of monitoring required. Only thecombinations of DFLTUSER and ATTACHSEC given in thefollowing table are supported:

IN25OPTSDFLTUSER=

CSD CONNECTION,ATTACHSEC=

Typical Use Additional Consideration

ANY LOCAL Nonsecure MROenvironment

AOR and TOR need the samedefault CICS user ID (set in theSIT)

SPECIFIC IDENTIFY Secure MROenvironment

TOR’s SIT uses SEC=YES orMIGRATE option

The following sections discuss each combination in detail.




Monitoring in a Nonsecure MRO Environment

The following combination says that monitoring and monitoringoptions should be set by terminal ID and not by CICS user ID.

DFLTUSER=.ANYATTACHSEC=LOCAL

This setting is typically used in a nonsecure MRO environmentwhere the TOR’s SIT uses the SEC=NO option. The user IDpassed from the TOR is the TOR’s default user ID as set in theSIT (typically CICSUSER).

CA-InterTest compares this user ID to the AOR’s default user IDand, if they match, sets the user ID to be monitored by .ANYuser. This entry causes all users of the program to be monitored(as in earlier CA-InterTest releases).

Important! Should the default user IDs of the AOR and TOR notmatch, the results are unpredictable. Thereforet, you should check thatthe default user IDs in the AOR and TOR are the same.

Monitoring in a Secure MRO Environment

The following combination is allowed in a secure MROenvironment where the TOR’s SIT uses the SEC=YES orMIGRATE option.

DFLTUSER=SPECIFICATTACHSEC=IDENTIFY

In this case, the application’s unique user ID is passed from theTOR to the AOR only if the ATTACHSEC option of theCONNECTION entry is IDENTIFY. This requirement andspecifying DFLTUSER=SPECIFIC in IN25OPTS allowsCA-InterTest to assign the user ID to each monitoring commandas a default. This saves the user from having to type it in orspecify it, and allows CA-InterTest to properly monitor useractivity in the TOR.




Additional Monitoring Considerations

The CRT terminal that is to receive the CA-InterTest breakpointdisplay is called the receiving terminal. After receiving thedisplay, the terminal remains ready to execute any CA-InterTestcommand. However, until the user disconnects fromCA-InterTest, it will accept only CA-InterTest commands.

The receiving terminal must meet these specifications:

� IBM 3270-type CRT or compatible:

– The terminal must have ATI (automatic task initiation)capability.

– If its screen is larger than model 2, its default screen size(as defined in the TCT) must be 24 lines x 80 characters(the model 2 size)

� For two-terminal testing:

– The receiving terminal must be logged on to the TOR atthe time the breakpoint is about to be displayed.

– At the time the first breakpoint display is about toappear, the receiving terminal must not be occupied byany task (transaction). This restriction also applies toCRTE.

– The next transaction ID must not be primed in theTCTTE of the receiving terminal. If this occurs,CA-InterTest cannot write the breakpoint screen becauseCICS prevents automatic task initiation.

– The receiving terminal must not be occupied by anexplicit routing session. (Explicit routing sessions arestarted by entering CRTE SYSID= and are normallyended by entering Cancel.) When necessary, thereceiving terminal will have a routing session started forit by CA-InterTest so the terminal can receive abreakpoint display.




– The terminal from which the tested transaction isentered or the terminal that the tested transaction ownsis called the sending terminal. Since a user typically setsbreakpoints without naming the receiving or sendingterminal, the receiving and sending terminal will be theterminal from which the CNTL command was enteredwhen the user ID monitoring option=.ANY.

– If the sending terminal is not the same as the receivingterminal, the sending terminal will be unavailable andtied to the tested transaction during the breakpoint. Thisrestriction does not apply if the receiving terminal is thesame as the sending one because the user can disconnectfrom CA-InterTest.

Remote FILE Support

All CICS regions participating in a remote FILE transactionsession must be at CA-InterTest Version 4.2 or above. Also, theFILE transaction and its associated program entry IN25FLE mustbe defined to the file-owning region. The transaction nameassigned to the FILE transaction must be the same in all regions.

Using CA-InterTest for CICS with DB2 Application Programs



Using CA-InterTest for CICS with DB2 ApplicationPrograms

The installation procedure is explained next. For an informationon how to test and debug DB2 application programs with CA-InterTest, see the CA-InterTest for CICS User Guide.

Using thePregenerated Version

A pregenerated IN25UEXI with DB2 support is provided. Ifyou have no other special software situations that theIN25UEXI program will handle, there are no furtherinstallation steps you have to perform for DB2 support.

Creating the IN25UEXIModule for DB2

To monitor application programs that issue SQL calls, aspecial program named IN25UEXI must exist in yourCA-InterTest load library. A pregenerated version ofIN25UEXI, assembled for DB2 Release 3.1 and above, isprovided. This release includes support for DB2 6.1.

You can also use the IN25UEXI program to support calls toprograms that are not to be monitored by CA-InterTest. If youhave programs that issue calls or require special handling,review the section Calls to Software and User Macro Support. Inthis case, you must combine the two uses in one IN25UEXI.

The source code for the preassembled version of IN25UEXI withDB2 support is provided in the CA-InterTest source(CAI.SAMPLIB) library in member UEXIDB2.

Using CA-InterTest for CICS with DB2 Application Programs



The following JCL example creates the IN25UEXI module forcombined DB2 and special uses. Modify this example to meetyour system requirements.

//IN25UEXI JOB ...//IN25UEXI JOB ...//IN25UEXI JOB ...//IN25UEXI JOB ...//ASM EXEC PGM=IEV90,REGION=1024K,//ASM EXEC PGM=IEV90,REGION=1024K,//ASM EXEC PGM=IEV90,REGION=1024K,//ASM EXEC PGM=IEV90,REGION=1024K,// PARM='DECK,LIST,XREF(SHORT),ALIGN'// PARM='DECK,LIST,XREF(SHORT),ALIGN'// PARM='DECK,LIST,XREF(SHORT),ALIGN'// PARM='DECK,LIST,XREF(SHORT),ALIGN'//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,//////// DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSIN DD *//SYSIN DD *//SYSIN DD *//SYSIN DD * COPY UEXIIDMS COPY UEXIIDMS COPY UEXIIDMS COPY UEXIIDMS CA-IDMSCA-IDMSCA-IDMSCA-IDMS COPY UEXIDATA COPY UEXIDATA COPY UEXIDATA COPY UEXIDATA CA-DATACOMCA-DATACOMCA-DATACOMCA-DATACOM COPY UEXITELN COPY UEXITELN COPY UEXITELN COPY UEXITELN CA-TELONCA-TELONCA-TELONCA-TELON COPY UEXISORT COPY UEXISORT COPY UEXISORT COPY UEXISORT CA-SORTCA-SORTCA-SORTCA-SORT COPY UEXIMAST COPY UEXIMAST COPY UEXIMAST COPY UEXIMAST CA-MASTERPIECECA-MASTERPIECECA-MASTERPIECECA-MASTERPIECE COPY UEXIDB2 COPY UEXIDB2 COPY UEXIDB2 COPY UEXIDB2 DB2DB2DB2DB2 COPY UEXIDB2 COPY UEXIDB2 COPY UEXIDB2 COPY UEXIDB2 DB2DB2DB2DB2 COPY UEXICPSM COPY UEXICPSM COPY UEXICPSM COPY UEXICPSM CICSPLEX SMCICSPLEX SMCICSPLEX SMCICSPLEX SM

COPY UEXISOKT COPY UEXISOKT COPY UEXISOKT COPY UEXISOKT TCP/IP SOCKETSTCP/IP SOCKETSTCP/IP SOCKETSTCP/IP SOCKETS***** * * * INSERT YOUR IN25UEX STATEMENTS FOR SPECIAL CALLS HEREINSERT YOUR IN25UEX STATEMENTS FOR SPECIAL CALLS HEREINSERT YOUR IN25UEX STATEMENTS FOR SPECIAL CALLS HEREINSERT YOUR IN25UEX STATEMENTS FOR SPECIAL CALLS HERE**** IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL***** * * * INSERT ANY USER WRITTEN ROUTINE HEREINSERT ANY USER WRITTEN ROUTINE HEREINSERT ANY USER WRITTEN ROUTINE HEREINSERT ANY USER WRITTEN ROUTINE HERE**** END END END END TERMINATES THE ASSEMBLY OF IN25UEXI TERMINATES THE ASSEMBLY OF IN25UEXI TERMINATES THE ASSEMBLY OF IN25UEXI TERMINATES THE ASSEMBLY OF IN25UEXI/*/*/*/*//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)***** * * * INSERT ANY //SYSLIB STATEMENTS FOR SPECIAL LOADLIBS HERE INSERT ANY //SYSLIB STATEMENTS FOR SPECIAL LOADLIBS HERE INSERT ANY //SYSLIB STATEMENTS FOR SPECIAL LOADLIBS HERE INSERT ANY //SYSLIB STATEMENTS FOR SPECIAL LOADLIBS HERE****//SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR//SYSUT1 DD UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))//SYSUT1 DD UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))//SYSUT1 DD UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))//SYSUT1 DD UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)// DD *// DD *// DD *// DD * ENTRY IN25UEXI ENTRY IN25UEXI ENTRY IN25UEXI ENTRY IN25UEXI NAME IN25UEXI(R) NAME IN25UEXI(R) NAME IN25UEXI(R) NAME IN25UEXI(R)////////

In the SYSLMOD DD statement, replace xx with your two-digitCICS release number (for example, 41 for CICS 4.1, 52 for CTS1.2, 53 for CTS 1.3).

Calls to Software and User Macro Support



The IN25UEXI module created by the previous job stream isused by the monitor program of CA-InterTest. To install thismodule, you must perform the following steps:

1. Terminate CA-InterTest (you can issue the CA-InterTestcheckpoint command before terminating CA-InterTest).

2. Issue a CEMT SET PROG(IN25UEXI) NEW command for thenew copy.

3. Issue a CEMT SET PROG(IN25PGM2) NEW command forthe new copy.

4. Start or restart CA-InterTest.


This section explains how to support software (which must notbe monitored by CA-InterTest) that is invoked by CALLs fromyour application programs or your own macros. For example:

� To support global routines whose addresses are found in theCWA and that are given control from monitored programsby a BALR 14,14 or BALR 14,15 instruction. When suchroutines are given control, they are not monitored byCA-InterTest until they return to the next byte after theBALR in the calling program.

� To make CA-InterTest recognize a call (a COBOL or PL/ICALL verb or the Assembler CALL macro) to specificinterfaces (such as database systems) and execute the callwithout monitoring the interface code.

In both cases, optional routines can be coded to:

� Check the parameters before the global routine is givencontrol

� Display CA-InterTest automatic breakpoints with errorcodes defined by you




WARNING! CA-InterTest assumes that the global routine of theCALL interface always returns control to the point of the CALL. If itdoes not, the user-written routine is mandatory.

How Support Is Provided

To provide support, code a few lines of Assembler source codeusing the IN25UEX macros delivered in the CA-InterTest sourcelibrary. (The next section explains how to code these macros.)Then run assembly and link-edit steps to create the IN25UEXImodule.

The macros create a table that, in addition to identificationnames and other information, contains references to the sameroutines that get link-edited with application programs becauseof CALLs issued by application programs. These references areresolved at link-edit time.

The IN25UEXI module consists of the table and the samemodules that are usually link-edited with application programs.In the IN25UEXI, however, these modules are never executed.They are there only to compare a piece of their code with thecode in the application load module.

CA-InterTest uses the IN25UEXI module to compare the twopieces of code: the one link-edited with the IN25UEXI and theone that is about to receive control from the applicationprogram. The compared pieces of code are at the offset (fromthe entry point) and the length specified in the IN25UEX macros.If a large piece of code is involved, there is no need to include allof it with the IN25UEXI; include just enough to make thecomparison. The comparison is made when a BALR 14,15 orBALR 14,14 instruction (for XA, BASSM or BASR instruction) isabout to be executed.




If the code matches and there is no associated routine (defined inthe IN25UEXI), CA-InterTest drops monitoring and produces astandard CA-InterTest entry in the CICS Trace Table (USER 144code) with the identifier found in the corresponding entry in theIN25UEXI module. Monitoring resumes only upon return fromthe called module to the CALL statement.

If there is a user-defined routine, the routine is performed first.The routine can check the CALL's parameters and decidewhether a particular interface should be given control or anautomatic breakpoint should occur (if the CALL is incorrect),and whether monitoring should continue when the interfacereturns to the calling program.

IN25UEXI routines receive control in:

� AMODE31 (CICS 3.2 and above)

� EXECKEY (CICS) (CICS 3.3 and above)

� BASESPACE MODE (CICS 4.1 and above)

Coding IN25UEX Macros for Called Software

The entry points are specified by using one of the followingformats:

IN25UEX CALL=entry1,ROUT=routine,LENGTH=xx,DISP=xx,ID=xx " " " " " "

or

IN25UEX CALL=(entry1,......,entryn) " " " " " "IN25UEX TYPE=FINAL (REQUIRED)place optional routines here




CALL=entry1 This required parameter specifies the name ofan entry point. Specify the same name usedin your COBOL or PL/I CALL statement orAssembler CALL macro, or specify an arbitraryname.

A name specified in this CALL parameter isdisplayed on the CA-InterTest RequestBreakpoint menus and on the CNTL=INQreports.

Multiple entry point names can be specified, asshown in the second format; however, theoptional parameters listed next cannot be used.

WARNING! Do not specify entry points used in aCALL that is the result of an EXEC CICS.

ROUT=routine This optional parameter specifies the name ofyour special routine. Omit this parameter ifthere is no routine.

LENGTH=xx This optional parameter specifies the length (indecimal) of the comparison. The maximumlength is 64 and the default length is 16. Thedefault is sufficient in most cases.

DISP=xx This optional parameter specifies the offset (indecimal) from the entry point of the code to becompared. The maximum offset (displacement)is 512; the default offset is 0.

ID=xx This optional parameter specifies theidentification value for the CA-InterTest entry inthe CICS Trace Table. Like all such entriesproduced by CA-InterTest, the first byte containsthe character C (USER 144), field A contains thedisplacement, and field B contains the charactersUS followed by the two characters specified inthis parameter. If the ID= parameter is notspecified, CA-InterTest generates a value.




After IN25UEXI is link-edited, verify the total size of the resultas shown in the link-edit listing. There is no need to includeentire interface modules in the IN25UEXI, as the comparisonoccurs only for the specified (or default) length at the specified(or default) offset. If the IN25UEXI module is too large, you cancode little Assembler CSECTs that identically replace the onesused by applications in IN25UEXI. This technique has been usedin the pregenerated version of IN25UEXI. Its source code isprovided in the CAI.SAMPLIB source library in memberDB2UEXI. This technique has reduced the size of IN25UEXIfrom approximately 30 KB to just 192 bytes.

Supporting Your Site's Global Routines

This section does not apply to most CA-InterTest sites. It appliesto global routines that are given control by the following twomachine instructions:

L 14,CWALABEL BALR 14,14

where CWALABEL is the label of a field in the CWA thatcontains the address of the global routine.

The entry points are specified by using one of the followingformats:

********** CWA USER DSECT REQUIRED HERE ********** ********** CWA USER DSECT REQUIRED HERE ********** ********** CWA USER DSECT REQUIRED HERE ********** ********** CWA USER DSECT REQUIRED HERE ********** USING CWADS,0USING CWADS,0USING CWADS,0USING CWADS,0 CACACACA-INTERTEST REQUIREMENT-INTERTEST REQUIREMENT-INTERTEST REQUIREMENT-INTERTEST REQUIREMENT CWADS CWADS CWADS CWADS DSECT DSECT DSECT DSECT USER CWAUSER CWAUSER CWAUSER CWA CWAFLD1 CWAFLD1 CWAFLD1 CWAFLD1 DS DS DS DS CL20CL20CL20CL20 CWAENT1 CWAENT1 CWAENT1 CWAENT1 DS DS DS DS FFFF USER ROUTINEUSER ROUTINEUSER ROUTINEUSER ROUTINE CWAFLD3 CWAFLD3 CWAFLD3 CWAFLD3 DS DS DS DS CL100CL100CL100CL100 ************ CA ************ CA ************ CA ************ CA-INTERTEST S-INTERTEST S-INTERTEST S-INTERTEST SPECIFICATIONS *************PECIFICATIONS *************PECIFICATIONS *************PECIFICATIONS ************* IN25UEX CWAD=label1,ROUT=routine,ID=xx IN25UEX CWAD=label1,ROUT=routine,ID=xx IN25UEX CWAD=label1,ROUT=routine,ID=xx IN25UEX CWAD=label1,ROUT=routine,ID=xx " " " " " " " " " " " " " " " " " " " " " " " " IN25UEX CWAD=labeln IN25UEX CWAD=labeln IN25UEX CWAD=labeln IN25UEX CWAD=labeln IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL (REQUIRED)(REQUIRED)(REQUIRED)(REQUIRED) place optional routines here place optional routines here place optional routines here place optional routines here




or IN25UEX CWAD=(label1,.....,labeln) IN25UEX CWAD=(label1,.....,labeln) IN25UEX CWAD=(label1,.....,labeln) IN25UEX CWAD=(label1,.....,labeln) IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL (REQUIRED)(REQUIRED)(REQUIRED)(REQUIRED) place optional routines here place optional routines here place optional routines here place optional routines here

CWAD=cwadadr This required parameter specifies a label thatis defined in the CWA and contains theaddress of the entry point of a piece ofcommonly used code, such as a dateconversion routine. For example, if theroutine address is 20 bytes from thebeginning of the CWA, you can code:

IN25UEX CWAD=(CWADS+20)

Multiple entry point names can be specifiedas in the second format; however, if specifiedin this manner, the optional parameters listednext cannot be used.

ROUT=routine This optional parameter is used as in theCALL= form.

ID=xx This optional parameter is used as in theCALL= form.

Coding the ROUT= Routine

The ROUT= parameter coded in the IN25UEX macro specifiesthe name of a routine that is performed by CA-InterTest prior tothe execution of the IN25UEXI-supported CWA routine orCALL. The routines are coded in Assembler after the IN25UEXTYPE=FINAL control card. CICS commands are not allowed.

Each routine must be a CSECT whose name is specified by theROUT= keyword. When CA-InterTest passes control to theroutine, the registers are set as follows:

R0 = 0

R1 = address of the BALR instruction

R2 = address of the called routine that is about to receivecontrol by the BALR (or, for XA, by BASSM or BASR)




R3 = address of the CA-InterTest work area

R4 = undetermined

R5 = undetermined

R6 = undetermined

R7 = undetermined

R8 = undetermined

R9 = address of an eight-byte field that contains the namespecified in the CALL= or CWAD= parameter

R10 = undetermined

R11 = undetermined

R12 = user's TWA address

R13 = EIB address

R14 = return address for this routine

R15 = entry point address for this routine

Notes:

� In XA or ESA systems, this routine receives control in thesame AMODE (addressing mode 24 or 31) that the branchinstruction had prior to its execution.

� Registers 3 and 14 must not be changed by the routine. Ifthese registers are used, they must be saved and restored bythe routine.

� The application program registers 0 to 15 (prior to theexecution of the branch instruction) are at 96 (X'60') bytespast the address in register 3.

In addition to checking application-related parameters, theroutine must determine if CA-InterTest should continuemonitoring. Monitoring must not continue if the code that iscalled by the monitored program does not return control to thenext byte after the BALR instruction.




Before the routine returns to the address in register 14, it mustset register 0 to one of the following values:

0 Execute the CALL withoutmonitoring

X'D0' - X'FF' CA-InterTest should issue anautomatic breakpoint with this errorcode

-1 The routine does not return control tothe next byte after the BALR;therefore monitoring must bedropped

any other negative value CA-InterTest should monitor thecalled piece of code

Sample JCL for Generating the IN25UEXI Programs

This example shows a call to the global routine CWAENT1,which has an associated routine called MYCHECK.

//IN25UEXI JOB (123,45),USERID,MSGCLASS=A,TIME=(,09)//IN25UEXI JOB (123,45),USERID,MSGCLASS=A,TIME=(,09)//IN25UEXI JOB (123,45),USERID,MSGCLASS=A,TIME=(,09)//IN25UEXI JOB (123,45),USERID,MSGCLASS=A,TIME=(,09)//ASM EXEC PGM=IEV90,REGION=1024K,//ASM EXEC PGM=IEV90,REGION=1024K,//ASM EXEC PGM=IEV90,REGION=1024K,//ASM EXEC PGM=IEV90,REGION=1024K,// PARM='DECK,LIST,XREF(SHORT),ALIGN'// PARM='DECK,LIST,XREF(SHORT),ALIGN'// PARM='DECK,LIST,XREF(SHORT),ALIGN'// PARM='DECK,LIST,XREF(SHORT),ALIGN'//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,//SYSPUNCH DD DSN=&&LOADSET,DISP=(NEW,PASS),UNIT=SYSDA,////////DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))DCB=(RECFM=FB,LRECL=80,BLKSIZE=400),SPACE=(400,(100,100,1))//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT1 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT2 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(5,1))//SYSIN DD *//SYSIN DD *//SYSIN DD *//SYSIN DD *********** CWA USER DSECT REQUIRED HERE ******************** CWA USER DSECT REQUIRED HERE ******************** CWA USER DSECT REQUIRED HERE ******************** CWA USER DSECT REQUIRED HERE **********

USING CWADS,0USING CWADS,0USING CWADS,0USING CWADS,0 CACACACA-INTERTEST REQUIREMENT-INTERTEST REQUIREMENT-INTERTEST REQUIREMENT-INTERTEST REQUIREMENTCWADS CWADS CWADS CWADS DSECT DSECT DSECT DSECT USER CWAUSER CWAUSER CWAUSER CWACWAFLD1CWAFLD1CWAFLD1CWAFLD1 DS DS DS DS CL20CL20CL20CL20CWAENT1CWAENT1CWAENT1CWAENT1 DS DS DS DS FFFF USER ROUTINEUSER ROUTINEUSER ROUTINEUSER ROUTINECWAFLD3CWAFLD3CWAFLD3CWAFLD3 DS DS DS DS CL100CL100CL100CL100************ CA************ CA************ CA************ CA-INTERTEST SPECIFICATIONS *************-INTERTEST SPECIFICATIONS *************-INTERTEST SPECIFICATIONS *************-INTERTEST SPECIFICATIONS ****************** INSERT YOUR IN25UEX STATEMENTS HERE* INSERT YOUR IN25UEX STATEMENTS HERE* INSERT YOUR IN25UEX STATEMENTS HERE* INSERT YOUR IN25UEX STATEMENTS HERE**** IN25UEX CWAD=CWAENT1,ROUT=MYCHECK IN25UEX CWAD=CWAENT1,ROUT=MYCHECK IN25UEX CWAD=CWAENT1,ROUT=MYCHECK IN25UEX CWAD=CWAENT1,ROUT=MYCHECK




IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL IN25UEX TYPE=FINAL***** INSERT USER WRITTEN ROUTINES HERE* INSERT USER WRITTEN ROUTINES HERE* INSERT USER WRITTEN ROUTINES HERE* INSERT USER WRITTEN ROUTINES HERE**** TITLE 'ROUTINE TO CHECK CWAENT1' TITLE 'ROUTINE TO CHECK CWAENT1' TITLE 'ROUTINE TO CHECK CWAENT1' TITLE 'ROUTINE TO CHECK CWAENT1'MYCHECK CSECTMYCHECK CSECTMYCHECK CSECTMYCHECK CSECT USING MYCHECK,15 ESTABLISH ADDRESSABILITY USING MYCHECK,15 ESTABLISH ADDRESSABILITY USING MYCHECK,15 ESTABLISH ADDRESSABILITY USING MYCHECK,15 ESTABLISH ADDRESSABILITY L 4,X'60'+4(,3) OBTAIN APPLICATION'S L 4,X'60'+4(,3) OBTAIN APPLICATION'S L 4,X'60'+4(,3) OBTAIN APPLICATION'S L 4,X'60'+4(,3) OBTAIN APPLICATION'SREGISTER 1REGISTER 1REGISTER 1REGISTER 1 LTR 4,4 IS REGISTER 1 ZERO ? LTR 4,4 IS REGISTER 1 ZERO ? LTR 4,4 IS REGISTER 1 ZERO ? LTR 4,4 IS REGISTER 1 ZERO ? BZ RETOKAY YES, NOTHING MORE TO CHECK. BZ RETOKAY YES, NOTHING MORE TO CHECK. BZ RETOKAY YES, NOTHING MORE TO CHECK. BZ RETOKAY YES, NOTHING MORE TO CHECK. L 4,0(,4) PICK UP 1ST ADDR FROM PARM L 4,0(,4) PICK UP 1ST ADDR FROM PARM L 4,0(,4) PICK UP 1ST ADDR FROM PARM L 4,0(,4) PICK UP 1ST ADDR FROM PARMLISTLISTLISTLIST LTR 4,4 IS THE HIGH ORDER BIT ON ? LTR 4,4 IS THE HIGH ORDER BIT ON ? LTR 4,4 IS THE HIGH ORDER BIT ON ? LTR 4,4 IS THE HIGH ORDER BIT ON ? BM ONLYONE YES, ONLY ONE PARAMETER. BM ONLYONE YES, ONLY ONE PARAMETER. BM ONLYONE YES, ONLY ONE PARAMETER. BM ONLYONE YES, ONLY ONE PARAMETER. CLC =C'FINAL',0(4) 1ST PARAMETER SAYS 'FINAL' ? CLC =C'FINAL',0(4) 1ST PARAMETER SAYS 'FINAL' ? CLC =C'FINAL',0(4) 1ST PARAMETER SAYS 'FINAL' ? CLC =C'FINAL',0(4) 1ST PARAMETER SAYS 'FINAL' ? BNE NOFINAL NO, TREAT SEPARATELY. BNE NOFINAL NO, TREAT SEPARATELY. BNE NOFINAL NO, TREAT SEPARATELY. BNE NOFINAL NO, TREAT SEPARATELY. LH 0,=H'-1' YES, INDICATE 'DROP LH 0,=H'-1' YES, INDICATE 'DROP LH 0,=H'-1' YES, INDICATE 'DROP LH 0,=H'-1' YES, INDICATE 'DROPMONITORING'MONITORING'MONITORING'MONITORING' BR 14 AND RETURN TO CA BR 14 AND RETURN TO CA BR 14 AND RETURN TO CA BR 14 AND RETURN TO CA-INTERTEST.-INTERTEST.-INTERTEST.-INTERTEST.NOFINAL CLI 0(4),C'0' 1ST CHARACTER NUMERIC ?NOFINAL CLI 0(4),C'0' 1ST CHARACTER NUMERIC ?NOFINAL CLI 0(4),C'0' 1ST CHARACTER NUMERIC ?NOFINAL CLI 0(4),C'0' 1ST CHARACTER NUMERIC ? BNL RETOKAY YES, GO CONTINUE NORMALLY. BNL RETOKAY YES, GO CONTINUE NORMALLY. BNL RETOKAY YES, GO CONTINUE NORMALLY. BNL RETOKAY YES, GO CONTINUE NORMALLY. LH 0,=H'-2' NO, KEEP MONITORING THE LH 0,=H'-2' NO, KEEP MONITORING THE LH 0,=H'-2' NO, KEEP MONITORING THE LH 0,=H'-2' NO, KEEP MONITORING THECALLED-CALLED-CALLED-CALLED- BR 14 - ROUTINE. BR 14 - ROUTINE. BR 14 - ROUTINE. BR 14 - ROUTINE.ONLYONE CLI 0(4),C'X' 1ST CHARACTER EQUAL TO "X"ONLYONE CLI 0(4),C'X' 1ST CHARACTER EQUAL TO "X"ONLYONE CLI 0(4),C'X' 1ST CHARACTER EQUAL TO "X"ONLYONE CLI 0(4),C'X' 1ST CHARACTER EQUAL TO "X" BE RETOKAY YES, GO CONTINUE NORMALLY. BE RETOKAY YES, GO CONTINUE NORMALLY. BE RETOKAY YES, GO CONTINUE NORMALLY. BE RETOKAY YES, GO CONTINUE NORMALLY. LA 0,X'E5' NO,DO A BREAKPOINT WITH CODE LA 0,X'E5' NO,DO A BREAKPOINT WITH CODE LA 0,X'E5' NO,DO A BREAKPOINT WITH CODE LA 0,X'E5' NO,DO A BREAKPOINT WITH CODEE5E5E5E5 BR 14 AND RETURN TO CA BR 14 AND RETURN TO CA BR 14 AND RETURN TO CA BR 14 AND RETURN TO CA-INTERTEST.-INTERTEST.-INTERTEST.-INTERTEST.RETOKAY SR 0,0 INDICATE 'CONTINUE NORMALLY'RETOKAY SR 0,0 INDICATE 'CONTINUE NORMALLY'RETOKAY SR 0,0 INDICATE 'CONTINUE NORMALLY'RETOKAY SR 0,0 INDICATE 'CONTINUE NORMALLY'* (DO NOT MONITOR THE CALL)* (DO NOT MONITOR THE CALL)* (DO NOT MONITOR THE CALL)* (DO NOT MONITOR THE CALL) BR 14 AND RETURN TO CA-INTERTEST. BR 14 AND RETURN TO CA-INTERTEST. BR 14 AND RETURN TO CA-INTERTEST. BR 14 AND RETURN TO CA-INTERTEST. LTORG TERMINATES THE ROUTINE. LTORG TERMINATES THE ROUTINE. LTORG TERMINATES THE ROUTINE. LTORG TERMINATES THE ROUTINE.***** CODE ANY ADDITIONAL ROUTINES HERE* CODE ANY ADDITIONAL ROUTINES HERE* CODE ANY ADDITIONAL ROUTINES HERE* CODE ANY ADDITIONAL ROUTINES HERE**** END TERMINATES THE ASSEMBLY OF END TERMINATES THE ASSEMBLY OF END TERMINATES THE ASSEMBLY OF END TERMINATES THE ASSEMBLY OFIN25UEXIIN25UEXIIN25UEXIIN25UEXI/*/*/*/*//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)//LKED EXEC PGM=IEWL,REGION=512K,PARM=(XREF,LIST,MAP)//SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx,DISP=SHR//SYSUT1 DD//SYSUT1 DD//SYSUT1 DD//SYSUT1 DDUNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))UNIT=SYSDA,DCB=BLKSIZE=1024,SPACE=(1024,(200,200))//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A




//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&LOADSET,DISP=(OLD,DELETE)// DD *// DD *// DD *// DD * ENTRY IN25UEXI ENTRY IN25UEXI ENTRY IN25UEXI ENTRY IN25UEXI NAME IN25UEXI(R) NAME IN25UEXI(R) NAME IN25UEXI(R) NAME IN25UEXI(R)////////

In the SYSLMOD DD statement, replace xx with your two-digitCICS release number (for example, 41 for CICS 4.1).

The IN25UEXI module created by the previous job stream isused by the monitor program of CA-InterTest. To install thismodule, perform the following steps:

1. Terminate CA-InterTest (you can issue the CA-InterTestcheckpoint command before terminating CA-InterTest).

2. Issue a CEMT SET PROG(IN25UEXI) NEWCOPY commandfor the new copy.

3. Issue a CEMT SET PROG(IN25PGM2) NEWCOPYcommand for the new copy.

4. Start or restart CA-InterTest.

IN25UEXI Instructions for Additional Vendor Products

You need intro text here

Calls for COMPUTATIONS Users

To handle a call to the COMPUTATIONS package, code theIN25UEX control statement as follows:

IN25UEX CALL=MGCALL,DISP=12,LENGTH=8

In addition, add an INCLUDE MSSECALL in your link-edit step.

You should exclude the COMPUTATIONS program frommonitoring. To do this, issue the CNTL=EXCL,PROG=PS* andCNTL=EXCL,PROG=PE* commands.




Calls for SHRINK Users

To handle calls to SHRINK, code the IN25UEX controlstatements as follows:

IN25UEX CALL=SHRINKIN25UEX CALL=EXPANDIN25UEX CALL=PUFFUPIN25UEX CALL=PUFFDOWNIN25UEX CALL=CLOSE

where SHRINK, EXPAND, PUFFUP, PUFFDOWN, and CLOSEare the entry points.

Calls for Patient Care System (PCS) Users

To handle calls to PCS, uncomment the COPY statementprovided in the IN25UEXI member in CAI.SAMPLIB:

*** COPY PCSUEXI

Calls for HOGAN Users

To handle calls to HOGAN, add this COPY statement to theIN25UEXI member in CAI.SAMPLIB:

COPY UEXIHOGN

Add the HOGAN.LOADLIB to the LKED step’s SYSLIB.

Calls for CICS/COMET Users

To handle calls to CICS/COMET, you must assemble theIN25UEXI module that is supplied with the COMET software.

Handling Wild Branches



Handling Wild Branches

When a monitored program passes control to another programdirectly by a branch instruction, bypassing the CICS services ofan XCTL or a LINK macro or command, CA-InterTest treats thisas a wild branch (branching outside a module) and causes anautomatic breakpoint. Such direct passing of control, althoughnot advised by CICS coding standards, is used frequently insome applications.

You cannot monitor just the program receiving control by adirect branch from another program. To monitor a receivingprogram, you must also monitor the program passing control toit. Monitoring can begin only with the program that originallyreceived control from CICS.

Most often, the program receives control by a direct branchcaused either by a CALL statement or by a special macro.Usually, such code should not be monitored by CA-InterTest.See the section Calls to Software and User Macro Support for anexplanation of how to make CA-InterTest drop monitoring insuch cases.

Monitoring a Wild Branch

If the program that receives control should be monitored andyou want to debug it with CA-InterTest, there are three possiblesituations:

� The receiving program resides in the same load module asthe program that passes control. In this situation, use thecomposite support facility of CA-InterTest. This facility letsyou debug a subprogram as if it were a separate programand supports all language combinations.

� The receiving program resides in another load module thathas a CICS program definition. In this situation, use theFOL=CICS-program-definition-name online option and, ifneeded, composite support. This approach makes allCA-InterTest debugging features available for the branched-to program.

Using CA-InterTest for CICS with IBM's EXEC Debugging Facility (EDF)



Note: For COBOL II dynamically called programs, the FOL=option is not needed. Simply set breakpoints in thedynamically called program as you would for any otherCICS program.

� The receiving program resides elsewhere and has no CICSprogram definition. In this situation, use the FOL=ON onlineoption. In this case, breakpoints can be set for addresses, notoffsets, and symbolic CA-InterTest support is not available.

Using the FOL=ON Option

We strongly advise that the FOL=ON online option be appliedonly at the program level; that is, monitorg declared with aCNTL=ON,PROG= command as opposed toCNTL=ON,TRAN= or CNTL=ON,TERM= commands. Thisallows online options to be used in the most convenient way,with different options such as breakpoints declared for differentprograms. If necessary, the FOL=ON online option can also bespecified at the terminal or transaction level.

Using CA-InterTest for CICS with IBM's EXECDebugging Facility (EDF)

The EDF facility, which is activated by the CEDF transaction anddescribed in the IBM CICS/VS Application Programmer's GuideCommand Level, does not interfere with the CA-InterTestmonitoring and interactive testing. CA-InterTest also does notinterfere with EDF, except when EDF presents the EDFbreakpoint display of the program that is being monitored byCA-InterTest, EDF incorrectly indicates the location of thecommand since commands are issued by CA-InterTest, not bythe program. Additionally, CEDF will not be supported ontransactions that contain programs that use COMET.




Advantages of CA-InterTest for CICS Over EDF

CA-InterTest offers many advantages over the EDF facility,including:

� The ability to set breakpoints anywhere in the program (notjust at EXEC CICS commands).

� Data display and modification by symbolic names. Thismeans the programmer does not need the most recent listingof the tested program, if the data names or paragraph names(labels in Assembler) remain the same.

� Monitoring, such as the ability to detect any illegal action ofthe program between CICS commands. CICS abends areintercepted by EDF, but damage may have occurred on theway to the abend and EDF may not give any specifics on theproblem.

� The ability to declare an unconditional or conditionalbreakpoint at a specific location—the EXEC CICS call at thepoint when the EXEC CICS call parameters have alreadybeen formatted. At that time you can change the parameters(for example, by issuing the CORE=ARGnn command)before you let the command execute.

� The ability to set request breakpoints for a particular type ofCICS command regardless of where in the program itoccurs, for all EXEC CICS commands, or for all except someEXEC CICS commands. For example, with one specificationyou can set breakpoints at all File Control commands or atall READ or WRITE commands.




Using CA-InterTest for CICS with EDF

If you want to use CA-InterTest with EDF, you can turn on EDFbefore you begin monitoring a program with CA-InterTest.Moreover, when a monitored program is stopped at a requestbreakpoint for an EXEC CICS command, you can activate EDFby entering any character in the field marked EDF in the lower-right corner of the Detailed Breakpoint display.

When CA-InterTest and EDF are being used on the same task, beaware of the following:

� If a CA-InterTest breakpoint is set at an EXEC CICScommand, the CA-InterTest breakpoint occurs before thecommand is passed to CICS.

� At the breakpoint, the programmer can review and changeany parameters of the command before telling CA-InterTestto continue with the task.

� CA-InterTest checks the parameters and, if necessary, haltsthe task at an automatic breakpoint.

� If that does not happen, the command is passed byCA-InterTest to CICS for execution; that is, to the EXECinterface.

� Subsequently, EDF presents the EDF breakpoint display ofthe program that is being monitored by CA-InterTest, beforea command breakpoint. The EDF facility, however, is incontrol at that time and any changes by the user during theEDF breakpoint cannot be checked by CA-InterTest.

� Only after the command is executed and a command EDFbreakpoint display appears and EDF is told to continue withthe task can CA-InterTest resume control and continuemonitoring.

Using CA-InterTest for CICS and HOGAN Software




For users with CICS 3.2 or above, all CA-InterTest features areavailable for debugging HOGAN applications, includingsymbolic support if the CA-InterTest post-compile step wasexecuted.

Use Considerations

Monitoring the PEMModule

The PEM module does not need to be debugged and shouldnot be monitored by CA-InterTest in a CICS 3.2 or aboveenvironment. Monitor only your HOGAN applicationprograms using the segmented monitoring option, as discussednext.

MonitoringApplicationPrograms That UseHOGAN

Application programs that use HOGAN should be monitoredonly by using the CA-InterTest segmented monitoring options. Do not monitor such programs by transaction or terminalname, or by global monitoring. The CA-InterTest for CICSUser Guide explains how to use segmented monitoring.

The USH=ON monitoring option must also be used to preventunnecessary automatic breakpoints from occurring.

All of the CA-InterTest online options are available. However,the FOL= option should not be used. It is advisable to learn howto use the BYP= option and the PF11 override option.




Installation Procedure

To install CA-InterTest for HOGAN support, first complete all ofthe required steps given in the chapter “Base ProductInstallation Steps.” Then complete your installation byperforming the steps below.

1. Create the IN25UEXI module for HOGAN. Instructions aregiven in the section IN25UEXI Instructions for AdditionalVendor Products.

2. Enable the CA-InterTest segmented monitoring options. Todo this, you must set the MONOM installation option in theIN25OPTS module to either MENU or NOMENU.Optionally, you can enable password security for segmentedmonitoring by setting the MONOMSEC installation optionto YES. Refer to the chapter “Modifying CA-InterTest forCICS Options” for details.

This completes the installation for HOGAN support in a CICS3.2 or above environment.

Password Protection with CA-InterTest for CICS 10–1


Chapter

10Password Protection withCA-InterTest for CICS

Online password protection is an optional CA-InterTest for CICSfeature. You can disable it selectively by redefining thepassword installation options CNTLSEC, CNTOSEC, CORSEC,and FILSEC. See the “Modifying CA-InterTest for CICSOptions” chapter for instructions.

The IN25SEC2 macro is used to assemble a CICS CA-InterTestload module that contains the passwords for the CORE facility,FILE facility, and CNTL facility. If you take no action, thedefault passwords are:

MAIN CORE

$FUN CNTL functions (commands)

$OPT CNTL options

$MNO CNTL options for segmented monitoring on and off(MON and NOM)

There is no default password for the FILE facility.

Notes:

� The IN25SEC2 passwords are not stored anywhere in theirunscrambled form. For secrecy, you can code PRINT OFF inyour IN25SEC2 assembly.

� Passwords can be changed at any time, even if someone isusing the CORE or FILE facilities. Just run an IN25SEC2assembly with the new passwords. If the CICS system isactive, enter the following command to put the newpasswords into effect:

CEMT SET PROG(IN25SEC2) NEW

Required Parameters



Required Parameters

The IN25SEC2 macro is delivered in the CA-InterTest sourcecode file and must be unloaded from the distribution tape beforethe assembly job.

IN25SEC2 TYPE=INITIAL,SCRNUM=(x,x,x,x)

The TYPE=INITIAL macro initiates the assembly and specifiesthe four numbers in the SCRNUM keyword that are to be usedin your version of the scrambling algorithm. These numbersmust be a value from 1 to 16, separated by commas, andenclosed in parentheses.

The TYPE=FINAL macro must be the last macro before the ENDstatement. This macro must not contain any other parameters.

Between the TYPE=INITIAL and TYPE=FINAL macros, specifythe IN25SEC2 macros to assign passwords to protected resourcesas follows:

� NAME= keyword specifies the name of the resource

� PASS= keyword specifies the four-character password forthe resource. Only the characters A-Z, 0-9, $, @, and # areallowed.

The following sections explain how to specify IN25SEC2 macrosto assign passwords for CORE, FILE, and CNTL.

Specifying Passwords for the CORE Facility



Specifying Passwords for the CORE Facility

The macro for the CORE password is:

IN25SEC2 NAME=PROTCORE,PASS=xxxx

� NAME=PROTCORE must be specified.

� xxxx specifies the password.

When a user of the CORE facility receives the message ENTERSECURITY PASSWORD, the user must enter the four-characterpassword. This password is then scrambled and compared withthe scrambled password specified in the PASS= parameter. Ifthe codes are equal, the CORE change is made and the passworddoes not have to be entered again during the same session. If thepassword is entered incorrectly, the CORE facility asks for itagain.

Note: Even if the password is entered correctly, areas outsideCICS storage cannot be modified:

The following IN25SEC2 macro, delivered with the pregeneratedversion of CA-InterTest, protects all storage not owned by auser's task:

IN25SEC2 NAME=PROTCORE,PASS=MAIN

PROTCORE—Specifies that this entry is for the COREtransaction.

MAIN—The default password:

� To change this password, reassemble the IN25SEC2program with the new password specified in the abovemacro.

� To remove this password, reassemble the IN25SEC2program with the above macro removed.

Specifying Passwords for Files and DL/I Databases



Specifying Passwords for Files and DL/I Databases

The macros for the FILE facility are:

IN25SEC2 NAME=yyyyyyyy,PASS=xxxx WRITE onlyIN25SEC2 NAME=yyyyyyyy,PASS=xxxx,FPROT=YES READ and WRITE

yyyyyyyy Specifies the name of the file ID (from the CICSfile definition) or the DBD identification.

xxxx Specifies the password.

FPROT=YES Indicates that the file or DBD name should alsobe fetch-protected; that is, data cannot beviewed or changed unless the password iscorrectly entered.

You must code one IN25SEC2 macro for every file or DBD nameyou want to protect; files or DBDs not named in a macro are notpassword protected against unauthorized use. These passwordsapply only to access through the CA-InterTest FILE facility.

When a user of the FILE facility receives the message ENTERSECURITY PASSWORD, the user must enter the four-characterpassword. This password is then scrambled and compared withthe scrambled password specified in the PASS= parameter. Ifthe codes are equal, the specified FILE or DBD is accessed. If thepassword is entered incorrectly, the FILE facility terminates.

Protecting All Fileswith a Password

You can code an IN25SEC2 macro to protect all files and DBDnames that are not specifically protected in individualIN25SEC2 macros.

The following example password protects FILEA against bothreads and writes with the password ASEC, password protectsFILEB against writes only with the password BSEC, andpassword protects all other files against both reads and writeswith the password FSEC.

IN25SEC2NAME=PROTFILE,PASS=FSEC,FPROT=YESIN25SEC2NAME=FILEA,PASS=ASEC,FPROT=YESIN25SEC2NAME=FILEB,PASS=BSEC

Specifying Passwords for CNTL Commands and Options



Note: Any security measures of your CICS installation areapplied by CICS or the operating system after CA-InterTestpassword protection is satisfied. The FILE facility functions as anapplication within CICS.

Specifying Passwords for CNTL Commands andOptions

Password protection is available for certain CNTL commandsand monitoring options as described next.

Note: To use CA-InterTest to protect other commands andoptions or not protect the ones listed here, contact ComputerAssociates for assistance.

CNTL password protection does not apply to the followingsituations:

� Automatic startup of CA-InterTest from the table assembledfrom CA-InterTest PROMMAC macros

� CNTL=RESTART command

� CNTL=NEW command

� CNTL=EXEC command

� Startup of CA-InterTest by the IN25PLT program in the PLTtable

� Execution of a CNTL command from a CRLP terminal; thatis, a simulated terminal consisting of input and outputsequential files

� Execution of a CNTL command from the system console

Passwords are not needed in these situations because they eitherautomatically start CA-InterTest, which is controlled by thesystem programming staff, or reestablish functions that werepassword protected when they were originally requested.




Password Protected CNTL Commands

The following commands are password protected by default;that is, if you use the pregenerated version of CA-InterTest.

CNTL=CKPT Start and end checkpoint

CNTL=END Remove CA-InterTest from CICS

CNTL=EXCL Enter a program, transaction, orterminal in the Exclusion Table toprevent monitoring

CNTL=INCL Remove a program, transaction, orterminal from the Exclusion Table

CNTL=ABP Activate and deactivate the globalautomatic breakpoint facility

CNTL=PURGE Start and end the purging of tasks thatremained at a breakpoint longer than thespecified time

CNTL=GLOG Start and end logging of CNTLcommands and CORE changes

CNTL=ON,PROG=.ALL Declare monitoring for all applicationprograms not specifically declared formonitoring

CNTL=OFF,PROG=.ALL Remove monitoring of all applicationprograms not specifically declared formonitoring

CNTL=ON,PROG=.ALL, Add monitoring options for allapplications not specifically declared formonitoring

CNTL=ALL Declare and remove monitoring for allapplications not specifically declared formonitoring




Note: The CNTL=OFF command that removes monitoringoptions is password protected only to the extent that the optionto be removed is password protected.

The following IN25SEC2 macro, delivered with the pregeneratedversion of CA-InterTest, protects all of the previously listedCNTL commands:

IN25SEC2 NAME=PROT$FUN,PASS=$FUN

PROT$FUN—Identifies the CNTL commands listed previously.

$FUN—The default password.






Password Protected CNTL Options

The following monitoring options are password protected bydefault; that is, if you use the pregenerated version ofCA-InterTest. You can disable password protection for theseCNTL options by redefining the CA-InterTest installation optionCNTOSEC.

CNTL Option Definition

,BYP Bypass storage protection or monitoring ofBALR 14,15 and BALR 14,14 routines (forXA, BASSM, and BASR)

,CSA=(offset,length) Do not protect specified areas of the CSA orCWA

,LET=name Do not protect storage occupied by aspecified program module

,LET=(address,length) Do not protect a specified storage area

,MON=location Set segmented monitoring on

,NOM=location Set segmented monitoring off

,OVR=errcode Disregard an error condition that wouldtypically cause a breakpoint

,STR=ON Preserve a copy of the CICS Trace Table forthe duration of a breakpoint

,TON=* or,TON=terminal

Limit monitoring to a specific terminal

,USH=ON Remove storage protection from storage areasin the shared subpool




The PROT$OPT Name Option

The following IN25SEC2 macro, delivered with the pregeneratedversion of CA-InterTest, protects all of the previously listedCNTL options except MON and NOM:

IN25SEC2 NAME=PROT$OPT,PASS=$OPT

PROT$OPT —Identifies the password protected CNTL options.

$OPT—The default password.



The PROT$MNO Name Option

The following IN25SEC2 macro, delivered with the pregeneratedversion of CA-InterTest, protects the segmented monitoringfunctions (MON and NOM) when MONOM=MENU orNOMENU, and MONOMSEC=YES:

IN25SEC2 NAME=PROT$MNO,PASS=$MNO

PROT$MNO—Identifies the CNTL options MON and NOM.

$MNO—The default password.



Sample IN25SEC2 Assembly JCL




The following is sample JCL for the assembly of IN25SEC2.

//IN25SEC2 JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A//IN25SEC2 JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A//IN25SEC2 JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A//IN25SEC2 JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A//ASSEM EXEC PGM=IEV90,REGION=512K,//ASSEM EXEC PGM=IEV90,REGION=512K,//ASSEM EXEC PGM=IEV90,REGION=512K,//ASSEM EXEC PGM=IEV90,REGION=512K,// PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'// PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'// PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'// PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'//*//*//*//*//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR// DD DSN=CICS.MACLIB,DISP=SHR// DD DSN=CICS.MACLIB,DISP=SHR// DD DSN=CICS.MACLIB,DISP=SHR// DD DSN=CICS.MACLIB,DISP=SHR//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT2 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT2 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT2 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT2 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT3 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT3 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT3 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT3 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,//////// DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS) DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS) DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS) DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS)//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSIN DD *//SYSIN DD *//SYSIN DD *//SYSIN DD *

IN25SEC2 TYPE=INITIAL,SCRNUM=(1,1,1,1)IN25SEC2 TYPE=INITIAL,SCRNUM=(1,1,1,1)IN25SEC2 TYPE=INITIAL,SCRNUM=(1,1,1,1)IN25SEC2 TYPE=INITIAL,SCRNUM=(1,1,1,1)IN25SEC2 NAME=PROTIN25SEC2 NAME=PROTIN25SEC2 NAME=PROTIN25SEC2 NAME=PROTCORE,PASS=CORECORE,PASS=CORECORE,PASS=CORECORE,PASS=COREIN25SEC2 NAME=PROTFILE,PASS=FSECIN25SEC2 NAME=PROTFILE,PASS=FSECIN25SEC2 NAME=PROTFILE,PASS=FSECIN25SEC2 NAME=PROTFILE,PASS=FSECIN25SEC2 NAME=FILE1,PASS=WXYZ,FPROT=YESIN25SEC2 NAME=FILE1,PASS=WXYZ,FPROT=YESIN25SEC2 NAME=FILE1,PASS=WXYZ,FPROT=YESIN25SEC2 NAME=FILE1,PASS=WXYZ,FPROT=YESIN25SEC2 NAME=FILE2,PASS=ABCDIN25SEC2 NAME=FILE2,PASS=ABCDIN25SEC2 NAME=FILE2,PASS=ABCDIN25SEC2 NAME=FILE2,PASS=ABCDIN25SEC2 NAME=PROT$FUN,PASS=CNTLIN25SEC2 NAME=PROT$FUN,PASS=CNTLIN25SEC2 NAME=PROT$FUN,PASS=CNTLIN25SEC2 NAME=PROT$FUN,PASS=CNTLIN25SEC2 NAME=PROT$OPT,PASS=CNTLIN25SEC2 NAME=PROT$OPT,PASS=CNTLIN25SEC2 NAME=PROT$OPT,PASS=CNTLIN25SEC2 NAME=PROT$OPT,PASS=CNTLIN25SEC2 TYPE=FINALIN25SEC2 TYPE=FINALIN25SEC2 TYPE=FINALIN25SEC2 TYPE=FINALENDENDENDEND

/*/*/*/*//LINK EXEC PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K//LINK EXEC PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K//LINK EXEC PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K//LINK EXEC PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K//SYSLMOD DD DSN=CAI.CACICSxx(IN25SEC2),DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx(IN25SEC2),DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx(IN25SEC2),DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx(IN25SEC2),DISP=SHR//SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,10))//SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,10))//SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,10))//SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,10))//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSLIN DD DSN=&&OBJ,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&OBJ,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&OBJ,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&OBJ,DISP=(OLD,DELETE)////////





In this example:

� The CORE password has been changed to CORE.

� All files except FILE1 and FILE2 will be WRITE protectedwith the password FSEC.

� FILE1 will be READ and WRITE protected with passwordWXYZ.

� FILE2 will be WRITE protected with password ABCD.

� CNTL commands and monitoring options are protectedwith the password CNTL.

Automatically Starting CA-InterTest for CICS 11–1


Chapter

11Automatically StartingCA-InterTest for CICS

After CA-InterTest for CICS has been installed, you can start itautomatically with your CICS system. There are four ways to dothis:

� Use the PROMMAC macro

� Enter CNTL commands from a CRLP-type terminal

� Activate CA-InterTest from a program

� Start CA-InterTest from a PLT

Using the PROMMAC Macro

You can use PROMMAC macros in an assembly to create a loadmodule defined in the CICS program definition that contains anumber of CNTL commands. These commands are executedconsecutively in the order of their appearance in the macroswhen either of these commands is submitted:

CNTL=START,PROM=tablname

or

CNTL=EXEC,MODULE=tablname

where tablname is the name of the load module generated by theassembly of the PROMMAC macros.

You can generate several alternate modules with differentnames, each with a CICS program definition, if you wantalternate ways to start CA-InterTest or execute CNTLcommands.




If the PROMD=tablname option is specified in the IN25OPTSmacro, you can achieve the same result by specifying:

CNTL=START

If the CNTL=START command is issued from a CRT terminal orCRLP-type terminal (a terminal whose input and output are twosequential files; see the IBM CICS System Programmer's Guide),the commands from the load module are displayed back. For aCRT terminal, there is a small time delay before each commandis executed so the user can see what is being done.

The first positional parameter of the PROMMAC macro containsthe CNTL command to be executed. The command must beenclosed in apostrophes.

If the table is to be used by the CNTL=START command, thefirst PROMMAC macro must contain this command:

'CNTL=START,PROM=nn,PROX=nn'

where nn sets the sizes of the internal CA-InterTest tables.

The second positional parameter of the PROMMAC macro mustcontain END. It must be coded in the last PROMMAC macrobefore the END statement.

Any CNTL command can be specified except CNTL=LIST andCNTL=INQ.




Sample PROMMACMacros

The following JCL is suitable for OS/390 installations. Theseexamples are shown for illustration purposes only. See theCA-InterTest for CICS User Guide for more information.

//PROMAC JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A//PROMAC JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A//PROMAC JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A//PROMAC JOB (NTSM,473),'JOHN BROWN',CLASS=D,MSGCLASS=A//ASSEM EXEC PGM=IEV90,REGION=512K,//ASSEM EXEC PGM=IEV90,REGION=512K,//ASSEM EXEC PGM=IEV90,REGION=512K,//ASSEM EXEC PGM=IEV90,REGION=512K,// PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'// PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'// PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'// PARM='XREF(SHORT),DECK,NUM,LIST,ALIGN,NOOBJ'//*//*//*//*//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSLIB DD DSN=CAI.SAMPLIB,DISP=SHR//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT1 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT2 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT2 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT2 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT2 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT3 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT3 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT3 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSUT3 DD SPACE=(CYL,(1,1)),UNIT=SYSDA//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,//SYSPUNCH DD DSN=&OBJ,SPACE=(TRK,(1,1)),UNIT=SYSDA,//////// DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS) DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS) DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS) DCB=(BLKSIZE=800,LRECL=80,RECFM=FB),DISP=(,PASS)//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSIN DD *//SYSIN DD *//SYSIN DD *//SYSIN DD * PROMMAC 'CNTL=START,PROM=20,PROX=5' PROMMAC 'CNTL=START,PROM=20,PROX=5' PROMMAC 'CNTL=START,PROM=20,PROX=5' PROMMAC 'CNTL=START,PROM=20,PROX=5' PROMMAC 'CNTL=ABP,ON,T321' PROMMAC 'CNTL=ABP,ON,T321' PROMMAC 'CNTL=ABP,ON,T321' PROMMAC 'CNTL=ABP,ON,T321' PROMMAC 'CNTL=ON,PROG=(CFIL,TERMIO,FILEIO,ERRORS,SCAN,LLASRCH), PROMMAC 'CNTL=ON,PROG=(CFIL,TERMIO,FILEIO,ERRORS,SCAN,LLASRCH), PROMMAC 'CNTL=ON,PROG=(CFIL,TERMIO,FILEIO,ERRORS,SCAN,LLASRCH), PROMMAC 'CNTL=ON,PROG=(CFIL,TERMIO,FILEIO,ERRORS,SCAN,LLASRCH), USR=.ANY' USR=.ANY' USR=.ANY' USR=.ANY' PROMMAC 'CNTL=EXCL,PROG=(TERMIO,FILEIO)' PROMMAC 'CNTL=EXCL,PROG=(TERMIO,FILEIO)' PROMMAC 'CNTL=EXCL,PROG=(TERMIO,FILEIO)' PROMMAC 'CNTL=EXCL,PROG=(TERMIO,FILEIO)' PROMMAC 'CNTL=ON,PROG=PBMASTER,FOL=ON,USR=.ANY' PROMMAC 'CNTL=ON,PROG=PBMASTER,FOL=ON,USR=.ANY' PROMMAC 'CNTL=ON,PROG=PBMASTER,FOL=ON,USR=.ANY' PROMMAC 'CNTL=ON,PROG=PBMASTER,FOL=ON,USR=.ANY' PROMMAC 'CNTL=PURGE,INTRVAL=0100',END PROMMAC 'CNTL=PURGE,INTRVAL=0100',END PROMMAC 'CNTL=PURGE,INTRVAL=0100',END PROMMAC 'CNTL=PURGE,INTRVAL=0100',END END END END END/*/*/*/*//LINK EXEC PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K//LINK EXEC PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K//LINK EXEC PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K//LINK EXEC PGM=IEWL,PARM='LIST,XREF,MAP',REGION=512K//SYSLMOD DD DSN=CAI.CACICSxx(PROMAC),DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx(PROMAC),DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx(PROMAC),DISP=SHR//SYSLMOD DD DSN=CAI.CACICSxx(PROMAC),DISP=SHR//SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,10))//SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,10))//SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,10))//SYSUT1 DD UNIT=SYSDA,SPACE=(TRK,(10,10))//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSPRINT DD SYSOUT=A//SYSLIN DD DSN=&&OBJ,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&OBJ,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&OBJ,DISP=(OLD,DELETE)//SYSLIN DD DSN=&&OBJ,DISP=(OLD,DELETE)////////

Note: A CICS program definition named PROMAC is requiredfor the generated table.


Entering CNTL Commands from a CRLP-type Terminal



Entering CNTL Commands from a CRLP-typeTerminal

If you have at least one CRLP-type terminal defined in yourTCT, its input sequential file can contain CNTL commands.These commands are executed in sequence just as if they wereentered manually from a terminal. Responses to them arewritten in the terminal's output sequential file.

To reduce the amount of time required to process large numbersof CNTL commands, perform the following steps:

1. Create a load module that contains the CNTL commands tobe processed using the PROMMAC macro (see the sectionUsing the PROMMAC Macro).

Note: You can add the USR= option to any embeddedCNTL=ON commands to assign the entries to a specific userID. See the chapter “CNTL Commands and Menus” in theCA-InterTest for CICS User Guide.

2. Add a PPT entry for the load module.

3. Set the following CA-InterTest options (see the “ModifyingCA-InterTest for CICS Options” chapter):

RECNTMU=NORECNTNW=NO

4. Replace the CNTL commands in the sequential input withthe following command:

CNTL=START,PROM=name

where name is the name of the module that was created inStep 1.

Activating CA-InterTest for CICS from a Program



Activating CA-InterTest for CICS from a Program

In one of your programs you can code a routine to activateCA-InterTest for CICS by the CICS command:

EXEC CICS START TRANSID('CNTL') FROM(data-area)...

The data-area must contain the command:

CNTL=START,PROM=tablname

where tablname is the name of the load module assembledthrough PROMMAC macros (see the section Using thePROMMAC Macro). The table name must be followed by aspace.

If the CNTL task to be automatically initiated is to own aterminal, be sure that the terminal is in service and has the ATI(automatic task initiation) capability when the CNTL task isstarted.

Issuing CNTLCommands from aProgram

You can issue any CNTL command using the EXEC CICSSTART command. However, for the CNTL=START command,the only permitted format is:CNTL=START,PROM=tablname

If the CNTL task is activated at a terminal, response messagesare displayed there and the command is executed as if someonehad entered it from that terminal. For example, if the CNTLcommand sets a breakpoint, the from and to terminals are theterminal at which the task was activated.

After CA-InterTest is started, a program can issue an EXEC CICSSTART command with the data record containing:

CNTL=EXEC,MODULE=tablname

This command executes the table of commands contained intablname.

Starting CA-InterTest for CICS from a PLT



Starting CA-InterTest for CICS from a PLT

If the program IN25PLT is included in the PLT, it startsCA-InterTest for CICS as specified in the IN25OPTS member.IN25PLT is delivered in the distribution load library. For moreinformation on IN25PLTx, see the section Global User Exits.

The following CA-InterTest PLTPI entry must be added afterDFHDELIM so that it is part of stage 2 processing:

DFHPLT TYPE=ENTRY,PROGRAM=IN25PLT

The IN25PLT program can be called by another user-written PLTprogram that passes a valid CA-InterTest start command in aCOMMAREA to IN25PLT. An example is given below:

INTSTART DC C'CNTL=START,PROM=PROMTABL ...'...EXEC CICS LINK

PROGRAM('IN25PLT')COMMAREA(INTSTART)LENGTH(=Y(L'INSTART))

Notes:

� The transient data destination specified in the GLOG=CA-InterTest option must be defined to CICS and must beopened. See the chapter “Modifying CA-InterTest for CICSOptions” for details.

� The group DFHINQUI must be defined in the CICS startuplist for IN25PLT to execute.

� The CA-InterTest Help file, PROTHLF, must be defined andavailable.

Automatic Startup in CICSPlex Regions

If CA-InterTest is automatically started in aCICSPlex-participating region (that is, CICSPLEX=YES inIN25OPTS), it will resynchronize its monitoring options withany active CICSPlex members upon startup.

Automatic Startup in CICSPlex Regions



Note: Resynchronization occurs whenever the CNTL=STARTor CNTL=RESTART command is issued in aCICSPlex-participating region.

Symbolic File Maintenance 12–1


Chapter

12 Symbolic File Maintenance

The IN25UTIL batch utility program maintains and reports onthe Symbolic File. This program runs as a separate job. Itsfunctions are specified using control cards.

Control Cards

All control cards must begin in column 1.

PASSWORD=12345678/xxxxxxxx

Specifies a password that is required when maintaining theSymbolic File. You only need to specify the password once, butit must precede the first update request.

The xxxxxxxx specification must match the value of theSYMPSWD= keyword in the IN25OPTS macro.

INITIALIZE Initializes the Symbolic File. This function must always be runafter the Symbolic File is created using VSAM Access MethodServices.

For a newly defined file, the IN25UTIL program preformats allrecords. If you perform this function for an existing file, allsymbolic data is removed.

The PASSWORD control card must precede the INITIALIZEcontrol card.

Control Cards



PURGE=nnn Removes symbolic data for any program that has not beencompiled or assembled within the number of days specified bynnn, a decimal number from 1 to 365.

The PASSWORD control card must precede the PURGE controlcard.

Note: The PURGE function does not remove data for programscompiled or assembled with the post-processor NOPURGEoption.

DELETE=xxxxxxxx Deletes all symbolic data for the program specified byxxxxxxxx.

The PASSWORD control card must precede the DELETE controlcard.

REPORT Produces a Symbolic File report that contains statistics and adetailed report on each program. You can obtain a similarreport online by entering one of these commands:CNTL=INQ,SYM=ALL for all programsCNTL=INQ,SYM=xxxxxxxx for program xxxxxxxx

Note: Either of the above commands reports on all SymbolicFiles.

PRINT=xxxxxxxx Prints the saved source listing for program xxxxxxxx.

UNLOAD=ALL/xxxxxxxx

Writes all symbolic data or just the symbolic data for programxxxxxxxx to the unload device.

RELOAD=ALL/xxxxxxxx Reloads all symbolic data or just the symbolic data for programxxxxxxxx from the device specified by the //RELOAD DDstatement. Programs are reloaded only if they do not exist onthe Symbolic File.

The PASSWORD control card must precede the RELOADcontrol card.

Examples



Examples

The following examples contain sample JCL for performingcommon Symbolic File maintenance tasks.

Initializing the CA-InterTest for CICS Symbolic Files

The following example initializes the CA-InterTest SymbolicFiles.

//UTILITY JOB ........//STEP1 EXEC PGM=IN25UTIL//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//SYSUDUMP DD SYSOUT=*//MESSAGE DD SYSOUT=*//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *PASSWORD=12345678INITIALIZE/*//


Purging Programs

The following example purges all programs that have not beencompiled or assembled within the last 20 days.

//UTILITY JOB ........//STEP1 EXEC PGM=IN25UTIL//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//SYSUDUMP DD SYSOUT=*//MESSAGE DD SYSOUT=*//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *PASSWORD=12345678PURGE=20/*//


Examples



Deleting Symbolic Data

The following example deletes all symbolic data for programsORDEDIT and TEST1.

//UTILITY JOB ........//STEP1 EXEC PGM=IN25UTIL//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//SYSUDUMP DD SYSOUT=*//MESSAGE DD SYSOUT=*//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *PASSWORD=12345678DELETE=ORDEDITDELETE=TEST1/*//


Generating Reports and Purging Programs

The following example generates a system report, purges allprograms that have not been compiled or assembled within 90days, and generates another system report.

//UTILITY JOB ........//STEP1 EXEC PGM=IN25UTIL//SYSUDUMP DD SYSOUT=*//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//MESSAGE DD SYSOUT=*//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *REPORTPASSWORD=12345678PURGE=90REPORT/*//


Examples



Unloading Programs

The following example unloads all programs on the SymbolicFile to tape.

//UTILITY JOB ........//STEP1 EXEC PGM=IN25UTIL//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//SYSUDUMP DD SYSOUT=*//MESSAGE DD SYSOUT=*//UNLOAD DDUNIT=TAPE,VOL=SER=UNLDTAP,LABEL=(,NL),DISP=(OLD,KEEP),// DCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *UNLOAD=ALL/*//


Reloading Programs

The following example reloads all programs on tape to theCA-InterTest Symbolic File.

//UTILITY JOB ........//STEP1 EXEC PGM=IN25UTIL//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//SYSUDUMP DD SYSOUT=*//MESSAGE DD SYSOUT=*//RELOAD DDUNIT=TAPE,VOL=SER=RELDTAP,LABEL=(,NL),DISP=(OLD,KEEP),// DCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *PASSWORD=12345678RELOAD=ALL/*//


Examples



Printing a Program Listing

The following example prints the saved listing for programORDEDIT.

//UTILITY JOB ........//STEP1 EXEC PGM=IN25UTIL//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//SYSUDUMP DD SYSOUT=*//MESSAGE DD SYSOUT=*//OUTPUT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=121,BLKSIZE=2420)//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *PRINT=ORDEDIT/*//


Examples



Reorganizing the Symbolic File

The following example reorganizes or changes the size of theSymbolic File. This job unloads all programs, deletes anddefines the Symbolic File, initializes the Symbolic File, reloads allprograms, and generates a system report.

//UTILITY JOB ........//UNLOAD EXEC PGM=IN25UTIL//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//SYSUDUMP DD SYSOUT=*//MESSAGE DD SYSOUT=*//UNLOAD DD UNIT=TAPE,VOL=SER=RELDTAP,LABEL=(,NL),DISP=(,PASS),// DCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *UNLOAD=ALL/*//IDCAMS EXEC PGM=IDCAMS,COND=(0,NE,UNLOAD)Insert an IDCAMS step to delete the existingSymbolic File and define a new one. We recommendthat this step and the next one run only if thefirst step has a condition code of 0./*//RELOAD EXEC PGM=IN25UTIL,COND=(0,NE,UNLOAD)//STEPLIB DD DSN=CAI.CACICSxx,DISP=SHR//SYSUDUMP DD SYSOUT=*//MESSAGE DD SYSOUT=*//RELOAD DDUNIT=TAPE,VOL=SER=RELDTAP,LABEL=(,NL),DISP=(OLD,KEEP),// DCB=(RECFM=FB,LRECL=2042,BLKSIZE=20420)//PROTSYM DD DSN=INTRTST.PROTSYM,DISP=SHR//CARDS DD *PASSWORD=12345678INITIALIZERELOAD=ALLREPORT/*//

In the STEPLIB DD statements, replace xx with your two-digitCICS release number (for example, 41 for CICS 4.1, 52 for CTS1.2, or 53 for CTS 1.3).

Troubleshooting 13–1


Chapter

13 Troubleshooting

This chapter explains how to troubleshoot problems and obtaincustomer support. The following topics are discussed:

� Identifying and resolving problems

� Contacting Computer Associates Technical Support

� Receiving ongoing product releases and maintenance

� Requesting product enhancements

Diagnostic Procedures

Refer to the following flowchart for a summary of theprocedures you should follow if you have a problem with aComputer Associates software product. Each of theseprocedures is detailed on the following pages.




Collecting Diagnostic Data

In the following table, use the left column to categorize theproblem your site has encountered. Then, follow theinstructions in the corresponding right column to generateuseful diagnostic data.

Type of Problem Procedure

User-initiated functions Check the user and servicemachine console logs. Try toreproduce the problem with[CNTL=ITTRACE,ON]

System or Operator functions Collect the dump or screenprint, if appropriate.

Interpreting Diagnostic Data

When you have collected the specified diagnostic data, writedown your answers to the following questions:

� What was the sequence of events prior to the errorcondition?

� What circumstances existed when the problem occurred andwhat action did you take?

� Has this situation occurred before? What was different then?

� Did the problem occur after a particular PTF was applied orafter a new release of the software was installed?

� Have you recently installed a new release of the operatingsystem?

� Has the hardware configuration (tape drives, disk drives,and so forth) changed?

From your response to these questions and the diagnostic data,try to identify the cause and resolve the problem.

Accessing the Online Client Support System




Computer Associates is making extensive use of the Internet foryour benefit. CA encourages you to surf the net to the CA homepage at http://www.ca.com. The CA Internet site provides agreat variety of information about CA products and services,including:

� Service and support

� Product information and sales

� CA-World conference information

� Press releases

� CA user groups

StarTCC, the web-based portion of CA-TCC (CA-Total ClientCare), gives you realtime, interactive access to CA productsupport information through the Internet. Using StarTCC, youcan:

� Open new issues

� Browse or update your existing issues

� Perform keyword searches

� Download solutions, PTFs, and important notices regardingComputer Associates products, maintenance, anddocumentation

Requirements for Using StarTCC

The following requirements are necessary to use StarTCC:

� You must be a Computer Associates client with a currentmaintenance agreement.

� You must register through the Computer Associates Internetsite.

http://www.ca.com/




� You must access the Internet with a browser that supportsthe HTML specification 2.0 or higher, such as NetscapeNavigator 4.0 or higher or Microsoft Internet Explorer 4.0 orhigher. (You can download browsers from the ComputerAssociates Technical Support page.)

Browsers that meet the HTML requirement support thefollowing functions, which are required for StarTCC:

� Secure sockets layer (SSL) to encrypt your transactiontraffic

� Encrypted data records (known as cookies)

� HTML tables

StarTCC Security

StarTCC runs as a secured server (SSL). You may need toconfigure your browser to enable SSL. Guidelines for doing thisare provided on the Computer Associates Technical Supportpage.

Access StarTCC

To access StarTCC, click Support on the Computer Associateshome page and follow the links for StarTCC. The StarTCCoptions are:

� StarTCC introduction

� StarTCC registration

� Access StarTCC

These options are described next:




StarTCC Introduction

Click Introducing StarTCC to view background information forStarTCC, details about the prerequisites, and instructions forconfiguring your browser. Be sure to review this section forupdates or information not included here.

StarTCC Registration

Click Register to identify yourself to StarTCC. You must registerbefore you can access StarTCC online. There are prompts for allrequired information, including your name, site ID, CA-StarTrakPIN, company name, e-mail address, postal address, and desiredpassword for accessing StarTCC.

Note: If you do not have a CA-StarTrak PIN, StarTCC providesone for you when you register.

Accessing StarTCC

Click Login and select an access option to begin using StarTCC.When prompted, enter your user ID and password. Once yoursignon is validated, you can select one of the following options:

Open a New Issue—Open an issue for, or request anenhancement to, one of your Computer Associates products.

Browse Your Issues—Display all issues for your site. The issuesare grouped into three categories: Open, Closed, andEnhancement Requests (DARs).

Browse/Download Solutions—Specify criteria for selectingsolutions, which you can then view or download.

Search CA Knowledge Base—Specify criteria for searching theComputer Associates database for solutions, problems, andkeywords that can provide you with immediate answers to yourproduct support questions and concerns.

Update Your StarTCC Profile—Make changes to your defaulte-mail address, phone number, and password whenevernecessary.

CA-TLC: Total License Care



Display Your Site’s Licenses—View a list of all of the ComputerAssociates products for which your company site is currentlylicensed.

Display News Items—View and download recently publishedsolutions for Computer Associates products, instructions fordownloading from StarTCC, and helpful information for usingCA-StarTrak, StarTCC, or other Computer Associates products.

Accessing the Technical Support Phone Services Directory

The Computer Associates Technical Support Phone ServicesDirectory lists each Computer Associates product and thetelephone number to call for primary support for that product.To access the Technical Support Phone Services Directory online,click Support on the Computer Associates home page. Followthe links, first to Calling CA for Support, and then TelephoneNumbers.

StarTCC Hotline

If you experience any problems using StarTCC, call the StarTCCTechnical Support hotline.

CA-TLC: Total License Care

Many Computer Associates software solutions use license keysor authorization codes to validate your hardware configuration.If you need assistance obtaining a license key or authorizationcode, contact the CA-TLC: Total License Care group athttp://esupport.ca.com/.

http://esupport.ca.com/

Calling Technical Support



Calling Technical Support

Computer Associates provides telephone support for all itsproducts.

If you are in North America, refer to the Technical Support PhoneServices Directory for the CA-InterTest for CICS TechnicalSupport phone number. Outside North America, call your localComputer Associates Support Center during normal businesshours.

Note: Only your local Computer Associates Support Center canprovide native language assistance. Use English when contactingany North American center.

Emergency phone numbers are available for after-hourstechnical support. You can find the emergency phone numbersfor the United States and Canada, and for international calls athttp://esupport.ca.com/. All after-hours calls should belimited to severity 1 problems.

If you are unable to resolve the problem, have the followinginformation ready before contacting Computer AssociatesTechnical Support:

� All of the diagnostic information described in the section“Collecting Diagnostic Data”

� Product name, release number, operating system, andgenlevel

Note: This information is available online from theCA-InterTest Product Status Menu. To access the menufrom CICS, enter ITST to display the Primary Option Menu,and then select Option 7.1.

� Your CICS release number

� Product name and release number of any other software yoususpect is involved

� Release level and PUTLEVEL of the operating system

� Your name, telephone number, and extension (if any)

http://esupport.ca.com/

Generating a Problem Report



� Your company name

� Your site ID

� A severity code. This is a number from 1 to 4 that you assignto the problem. Use the following definitions to determinethe severity of the problem:

1 = a system down or inoperative condition

2 = a suspected high-impact condition associated with theproduct

3 = a question concerning product performance or anintermittent low-impact condition associated with theproduct

4 = a question concerning general product use orimplementation

Generating a Problem Report

Once a Computer Associates Technical Support representativehas determined that your problem requires further investigation,use CA-ACTIVATOR to generate the problem report required byComputer Associates.

CA-ACTIVATORProblem ReportingFacility

The CA-ACTIVATOR problem reporting facility lets youprovide a description of the problem. It automatically producesa report on:

� Your current system environment

� Computer Associates product installation and maintenanceinformation

� The product runtime options in effect

Product Releases and Maintenance



Product Releases and Maintenance

New users of CA-InterTest receive a distribution tape containingthe current version of the system. Clients are requested tooperate only under currently supported releases of CA-InterTest.

Standard user documentation is also provided to CA-InterTestusers. Updates to this documentation are providedautomatically to all clients having current maintenanceagreements.

Clients with current maintenance agreements also receiveongoing CA-InterTest maintenance. When a new release of thesystem is available, a notice is sent to all current CA-InterTestclients.

Requesting Enhancements

Computer Associates welcomes your suggestions for productenhancements. All suggestions are considered andacknowledged. You can use any of the following methods torequest enhancements:

� Access StarTCC, the Computer Associates web-based,interactive support system, from the Computer AssociatesInternet site to open an issue for the enhancement request.For details, the section Accessing the Online Client SupportSystem.

� Contact your Account Manager or a Technical SupportRepresentative, who will initiate a Demand AnalysisRequest (DAR) for you. The DAR system serves as a centralreceiving point for all enhancement requests.

Maintenance 14–1


Chapter

14 Maintenance

This chapter describes the maintenance process for CA-InterTestfor CICS. Topics include:

� Overview of the SMP/E maintenance process

� CA-InterTest maintenance delivery

� PTF maintenance installation

� Overview of maintenance steps

� Detailed maintenance steps

New users of CA-InterTest receive a distribution tape containingthe current version of the system. Clients are requested tooperate only under currently supported releases of CA-InterTest.

Standard user documentation is also provided to CA-InterTestusers. Updates to this documentation are provided automaticallyto all clients having current maintenance agreements.

Clients with current maintenance agreements also receiveongoing CA-InterTest maintenance. When a new release of thesystem is available, a notice is sent to all current CA-InterTestclients.

PL/I Option Maintenance

14�2 CA-InterTest for CICS Getting Started

InsGS14.doc, printed on 12/21/00, at 5:06 PM

PL/I Option Maintenance

The following maintenance procedure applies to theCA-InterTest PL/I option and the CA-InterTest base product.PL/I option maintenance members substitute MA60 for BA60 inthe maintenance JCL member names.

CA-InterTest for CICS Maintenance

CA-InterTest maintenance is delivered in SMP/E format. Youshould use SMP/E to apply all maintenance modifications.

WARNING! If you attempt to apply maintenance without usingSMP/E, the integrity of your CA-InterTest libraries is at risk and themaintenance tracking capabilities of SMP/E are lost.

SMP/E Libraries

SMP/E uses two sets of libraries:

� Target libraries are the product execution or runtimelibraries.

CAI.CACICSnn�contains the load modules.

CAI.SAMPLIB �contains the sample source and JCL.

� Distribution libraries are the product backup libraries.

CAI.CBA60nnD�contains the load modules.

CAI.CBA60SLD�contains the sample source and JCL.

Note: nn is the two-digit CICS release number

When a product is installed by SMP/E, the target anddistribution libraries are populated. The target libraries arepopulated during the SMP/E APPLY process, and thedistribution libraries are populated during the SMP/E ACCEPTprocess. At this point, the target and the distribution librariescontain identical versions of the product modules.

CA-InterTest for CICS Maintenance

Maintenance 14–3


Maintenance through SMP/E is applied to the runtime system(the target libraries) first. After the maintenance has beenrunning on the system for a period of time or when it appearsthat there are no problems with the maintenance, it is applied tothe backup libraries (the distribution libraries).

Note: When maintenance is installed on the running libraries, itis said to be applied. When installed on the backup libraries, it issaid to be accepted.

APPLY and ACCEPT Commands

APPLY and ACCEPT are the names of two SMP/E commands.The APPLY process updates the target libraries and the ACCEPTprocess updates the distribution libraries.

The cycle of a product under SMP/E generally follows thisschedule:

1. Apply and accept the base product installation material,creating target and distribution libraries.

2. At this point, the target and distribution libraries are at thesame maintenance level. Later, you apply maintenance inthe form of an APAR or a PTF, bringing the target librariesto a new maintenance level.

3. The target and distribution libraries are now at differentmaintenance levels. If there is a problem with themaintenance applied to your target libraries, themaintenance can be removed by the SMP/E RESTOREcommand.

Maintenance Delivery



The RESTORE Command

The RESTORE process replaces the modules in the target librarythat were affected by the maintenance with backup modulesfrom the distribution libraries.

After verifying that the maintenance will not cause any newproblems on your runtime system, install the maintenance intoyour distribution libraries with the SMP/E ACCEPT process.This step synchronizes your target and distribution libraries atthe same maintenance level.

Once you accept the maintenance into your distribution libraries,there is no SMP/E process to remove it.

Maintenance Delivery

Maintenance to your CA-InterTest system is packaged anddelivered as SMP/E USERMODs, APARs, and PTFs. Thevarious types of maintenance delivery are discussed next.

Informational APAR or PML

The informational APAR or Product Maintenance Letter (PML)is official information relative to a product. PMLs are deliveredby hardcopy, CA-TCC, and on maintenance tapes.

The naming convention for PMLs (at the time of the release ofthis manual) is LInnnnn, where:

� LI identifies an informational APAR

� nnnnn is an identification number

PTF Maintenance Tape Installation

Maintenance 14–5


Program Temporary Fixes

A Program Temporary Fix (PTF) is an official replacementmodule or modules that fixes one or more problems. A PTF isusually an accumulation of APARs.

� PTFs are installed as PTF SYSMODs, which you must acceptprior to installing subsequent maintenance

� PTFs are always delivered on a periodic maintenance tape

� PTFs are named (at the time of the release of this manual)LAnnnnn-LZnnnnn

PTF Maintenance Tape Installation

A combined installation and maintenance tape is distributedperiodically on a standard IBM cartridge, which can beprocessed by SMP. It contains the newly published official PTFSYSMODs for CA-InterTest. This cartridge is to be used onlywhere SMP controls installation and maintenance of ComputerAssociates solutions. This tape is in the new combined format,which means that it can be used either to install CA-InterTest atthe genlevel specified on the external label or to applymaintenance to bring an existing CA-InterTest solution up to thegenlevel specified on the external label.

A partitioned data set containing all necessary sample JCL isprovided in the Load Sample JCL Library step. The sample JCLdata set contains all JCL necessary for installation andmaintenance. The maintenance-specific members are prefixedwith an M.

Refer to the external label of the tape for the current volume serialnumber.

Overview of Maintenance Steps



Overview of Maintenance Steps

WARNING! Before applying any new maintenance, the base productand all prior maintenance to CA-InterTest must be accepted.

The following list summarizes the steps involved in theCA-InterTest maintenance process. Review this list beforeperforming maintenance on CA-InterTest.

Step 1. Review and follow the cover letter instructions.

Step 2. Load the sample JCL from the tape.

Step 3. Customize the SMP procedure.

Step 4. Edit the JCL to exclude previously applied SYSMODs.

Step 5. Receive CA-InterTest maintenance.

Step 6. Apply check CA-InterTest maintenance.

Step 7. Restore any applicable SYSMODs.

Step 8. Apply CA-InterTest maintenance.

Step 9. Reapply any applicable SYSMODs.

Step 10. Execute CA-InterTest to verify successfulmaintenance.

Step 11. Accept CA-InterTest maintenance.

Step 12. Unload the documentation set.

Step 13. Save all materials and output.

Step 1. Review and Follow the Cover LetterInstructions

Before starting the maintenance steps, you must first review andfollow the cover letter instructions. This letter details anyadditional steps that may be required by your site.

Step 2. Load the Sample JCL from the Tape

Maintenance 14–7


Additionally, before starting this maintenance procedure youshould:

1. Check the packing list for CA-InterTest against the packagecontents.

2. Review all PTFs (Program Temporary Fixes) and PMLs(Product Maintenance Letters) provided.

Important! If any items are missing or if you have any questions, callyour local Computer Associates Technical Support center beforeperforming the maintenance procedure.

Step 2. Load the Sample JCL from the Tape

Use the following JCL as a model to load the sample JCL libraryto DASD://LOAD EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=A//SYSUT1 DD DISP=(OLD,KEEP),// DSN=CAI.SAMPJCL,// UNIT=CART, <===generic 3480 tape cartridge// VOL=SER=BAyymm, <===VOLSER from tape label// LABEL=(9,SL)//SYSUT2 DD DISP=(NEW,CATLG,DELETE),// DSN=CAIM.INTERTST.SAMPJCL, <===your DSN// UNIT=SYSDA, <===your generic DASD// VOL=SER=XXXXXX, <===permanent DASD volser// SPACE=(3120,(50,10,10)), <===minimum space required// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//SYSUT3 DD UNIT=SYSDA,// SPACE=(TRK,(5,5))//SYSUT4 DD UNIT=SYSDA,// SPACE=(TRK,(5,5))//SYSIN DD DUMMY

Once this job has ended, your library will contain all of the JCLneeded to complete the maintenance for CA-InterTest.





During the installation of CA-InterTest, an SMP/E procedurewas selected and customized. If the SMP procedure used duringthe installation of CA-InterTest is available, this step is notrequired.

If that procedure is not available, a JCL procedure can be foundin the sample JCL library. Member BA60SMPE is the model JCLprocedure using SMP/E. Select and modify this member toconform to your site standards.

Note: This procedure is used in subsequent steps.

Step 4. Edit Maintenance JCL to Exclude PreviouslyApplied SYSMODs

In this step you exclude those PTFs (SMP element replacements)already processed from previous CA-InterTest maintenancecycles.

The sample JCL data set contains the members listed in thefollowing table.

Note: xx is the two-digit CICS release number.

Member Name For Product

CBA60xx (xx = 41, 52, or 53) CA-InterTest

CLQ60xx CA-Realia II Workbench forCICS

CSA60xx Breakpoint

CMA60xx PL/I option

Step 4. Edit Maintenance JCL to Exclude PreviouslyApplied SYSMODs

Maintenance 14–9


To be cumulative, these members contain a list of all PTFs foreach component since the base level of this release. You mustedit these members by either commenting out or deleting thePTF IDs belonging to maintenance levels equal to or lower thanyour current genlevel. These members drive all subsequent SMPsteps.

For example, to edit the PTF list for the CA-InterTest memberCBA60xx, locate the member in the sample JCL file. Theexample below shows sample SYSMOD entries for genlevels9904, 9912, and 0009.

LA14345 /*LVL9904*/LA19222 /*LVL9904*/LA26333 /*LVL9904*/LA29234 /*LVL9912*/LA33123 /*LVL9912*/LA33567 /*LVL9912*/LA33555 /*LVL0009*/LA33735 /*LVL0009*/

Assuming you are at the fictitious genlevel 9805 and going togenlevel 9808, you should edit the list as follows:

/* LA14345 LVL9904*//* LA19222 LVL9904*//* LA26333 LVL9904*//* LA29234 LVL9912*//* LA33123 LVL9912*//* LA33567 LVL9912*/ LA33555 /*LVL0009*/ LA33735 /*LVL0009*/

Note: SMP requires that all comments begin with “/*“ andcomplete with “*/“.

After you edit this member, remember to update the data set sothe changes are not lost.

Note: CA-InterTest for CICS and CA-SymDump for CICS sharecommon components. The release and maintenance level of thetwo products must be equivalent. If your site also hasCA-SymDump for CICS as a separate product and you havealready applied this maintenance level to CA-SymDump forCICS, pay particular attention to the instructions within theSAMPJCL members specified in the following steps.

Step 5. Receive CA-InterTest for CICS Maintenance



Step 5. Receive CA-InterTest for CICSMaintenance

Maintenance JCL member MBA60REC receives all of the PTFscorresponding to CA-InterTest maintenance. Edit memberMBA60REC to conform to your site standards.

Submit the job and verify that the RECEIVE process wassuccessful. If the SMP RECEIVE completed with a return codegreater than 4, review the output, correct the problem, andresubmit.

Step 6. Apply Check CA-InterTest for CICSMaintenance

Maintenance JCL member MBA60APC apply checks all PTFscorresponding to the components specified within theSMPCNTL DD statement. This step identifies any USERMODsand APARs that prevent PTF application and any PTFs alreadyapplied.

Edit member MBA60APC to conform to your site standards.Delete any DD statements within the SMPCNTL DD statementthat correspond to CA-InterTest components not currentlyinstalled.

Submit the job and verify that APPLY CHECK processing wassuccessful. If the SMP APPLY CHECK completed with a returncode greater than 4, review the output, correct the problem, andresubmit.

Note: SMP APPLY CHECK processing performs preliminaryvalidation on SYSMODs individually. Carefully review the SMPgenerated reports, noting any possible regression of SYSMODs.

Step 7. Restore Any Applicable SYSMODs

Maintenance 14–11


Computer Associates requires the removal of any SYSMODpreventing PTF application. To allow PTF application, performSMP RESTORE processing on the SYSMODs identified duringthe SMP APPLY CHECK. The instructions to accomplish thisare in Step 7.

Step 7. Restore Any Applicable SYSMODs

Maintenance JCL member MBA60RES contains the controlstatements for an SMP RESTORE. This step restores SMPUSERMODs and APARs identified by APPLY CHECKprocessing to allow for PTF application. If you do not have anySYSMODs to restore, skip this step and continue to the next step.

Edit member MBA60RES to conform to your site standards.Only the SYSMODs identified by APPLY CHECK processingneed to be restored. Type these SYSMODs within the SMPCNTLDD statement.

After you complete editing, submit the job and verify thatRESTORE processing ran successfully. If SMP RESTOREcompleted with a return code greater than 4, review the output,correct the problem, and resubmit.

We suggest you execute the SMP APPLY CHECK again to verifythat there are no additional SYSMODs inhibiting the applicationof maintenance.

Step 8. Apply CA-InterTest for CICS Maintenance

Maintenance JCL member MBA60APP applies all PTFscorresponding to the components specified within theSMPCNTL DD statement.

Edit member MBA60APP to conform to your site standards.Submit the job and verify that APPLY processing was successful.If the SMP APPLY completed with a return code greater than 4,review the output, correct the problem, and resubmit.

Step 9. Reapply Any Applicable SYSMODs



Step 9. Reapply Any Applicable SYSMODs

Review the USERMODs and APARs restored by Step 7. If noSYSMODs were restored, skip this step and continue to the nextstep.

Note: SYSMODs identified by APPLY CHECK processing maybe at a higher level than the PTFs contained on the CA-InterTestmaintenance tape.

Edit maintenance JCL member MBA60RAP to conform to yoursite standards. Submit the job and verify that APPLY processingran successfully. If the SMP APPLY completed with a returncode greater than 4, review the output, correct the problem, andresubmit the job.

Note: SMP can handle only one update per element per APPLYselect statement. In reapplying SYSMODs, it may be necessaryto use multiple APPLY select statements.

Step 10. Execute CA-InterTest for CICS to ValidateMaintenance

WARNING! If CA-InterTest is currently running, stop it with thecommand:

CNTL=END

Then, activate the maintenance and restart CA-InterTest with thecommands:

CEMT SET PROG(IN25*) NEWCNTL=START

To validate the successful application of maintenance, run theappropriate demonstration program.

Step 11. Accept CA-InterTest for CICS Maintenance

Maintenance 14–13


Step 11. Accept CA-InterTest for CICSMaintenance

After a reasonable period of testing the features of CA-InterTestwith the new maintenance level applied, we recommend thatyou perform an SMP ACCEPT. This will give you a solidbaseline to proceed from and make it easier to apply or restoreany test USERMODs that you may be given by the CA-InterTestsupport staff.

Maintenance JCL member MBA60ACC accepts all PTFscorresponding to the components specified within theSMPCNTL DD statement.

Edit member MBA60ACC to conform to your site standards.Submit the job and verify ACCEPT processing was successful. Ifthe SMP ACCEPT completed with a return code greater than 4,review the output, correct the problem, and resubmit.

Step 12. Unload the Documentation Set

See Step 19. Unload Documentation Set in the chapter "BaseProduct Installation Steps," for an explanation of how to unloadthe CA-InterTest for CICS documentation.

Step 13. Save All Materials and Output

Be sure to save all of your maintenance materials and all outputfrom the maintenance process. This material is essential forfuture problem determination.

Index–1


Index

A

Abend Code Maintenance Menu, 8-24

Abend codescustomizing help for, 8-24specifying, in IN25ABEN macro, 8-22

ACCEPTACCEPTing maintenance, 14-13CA-InterTest, 4-14command, 14-3PL/I option, 5-3

AKC3, 8-22

APAR, 14-4

APPLYAPPLYing maintenance, 14-11CA-InterTest, 4-2, 4-10, 4-12, 4-13, 4-14,4-15, 4-16, 4-19, 5-1, 5-3, 14-9command, 14-3PL/I option, 5-2

APPLY CHECKingmaintenance, 14-10

Assembler DSECTSSymbolic File, adding to, 8-13

Assembler programsAssembler options, 6-13High Level Assembler support, 3-12

non-purgable data, 6-15, 6-22online listing display, 6-15printed output, controlling, 6-14sample JCL, 6-17symbolic support, 6-12

AUDIT, 7-5, 7-6

AUTMON, 7-6

AUTOKEEP, 2-3

Automatic breakpointsabend codes, excluding from, 8-22Monitor Table entries, creating, 7-6

Automatic startupCICSplex regions, 11-6migration considerations, 3-12

B

BA60ACC, 4-14

BA60ALC, 4-10

BA60APP, 4-2, 4-10, 4-12, 4-13, 4-14, 4-15,4-16, 4-19, 5-1, 5-3, 14-9

BA60INIT, 4-11

BA60SMPE, 4-12

BookManagerbookshelf definition, changing prefix,4-23

Index–2 CA-InterTest for CICS Getting Started

downloading OS/390 files, 4-23unloading files, 4-22

BREAK, 7-6

Breakpointsactivating, 7-6display, default, 7-22internal transaction for, 7-17, 7-27lower case terminals, 3-13read buffer, 7-21TCTTE user area, 7-24

C

CA LMP, 3-2, 3-3

CA Total Client Care (CA-TCC), 14-4

CA-ACF2, 3-9

CA-Activator, 13-9

CAI.SAMPJCL, 4-9

CAICCI, 3-4

CA-IDMSJCL for IN25UEXI, 9-16

CA-InterTestactivating, 4-26automatically starting, 11-1changes for this release, 2-3deactivating, 4-27deactivating, all CICSplex regions, 4-27enhancements, 14-1files, JCL for, 4-19libraries, 4-10migration considerations from CA-InterTest 4.x, 3-14prior customization, 3-12releases, 14-1

CAIRIM, 3-2

CA-Optimizer II options, 3-12, 3-13, 6-4

CA-Optimizer options, 6-4

CA-Realia II Workbench For MVS CICS,3-10, 7-21

CA-Stabilize/CICSSTBRN keyword, 7-24

CA-SymDumpCA-InterTest access, 7-25external security option, EXTSEC, 7-13file, naming, 7-25LMP, 4-7transaction ID, 7-25

CA-TCCbrowsers supported, 13-4Registration, 13-6

CA-TCC (CA-Total Client Care), 13-4

CA-TLCTotal License Care, 13-7

CA-UFO support, 3-10

CA-Verifyexcluding abend code AKC3, 8-22

Changes for this release, 2-3

Check-out program, 4-21

Checkpoint filecreating, 4-18naming, 7-7

CICSadding resource definitions, 4-18adjusting startup JCL, 4-19migration considerations, 3-14restarting, 4-21USERID, 3-13

CICS/COMET, 3-14

CICS/ESA 3.3, 3-14DPL support, 3-15storage protection support, 3-15

CICSplexCICSPLEX keyword, 7-7CPLXCKPI checkpoint interval, 7-11CPLXFMID family name, 7-10

Index–3

installation requirements, 3-8startup and termination considerations,3-9

CICSPLEXIPLX task, 7-17

CKPTFIL, 7-7

CNTLCA-InterTest, automatically starting,11-4commands, displaying, 7-21commands, displaying automatic, 7-22commands, issuing from programs, 11-5commands, logging, 7-8, 7-10password protection, 7-7, 10-5, 10-8START command, 7-20, 7-21, 7-22transaction ID, 7-8

CNTLSEC, 7-7, 10-1

CNTLT, 7-8

CNTOSEC, 7-8, 7-9, 7-10, 10-1, 10-8

CNTSQLG, 7-8, 7-10

COBOL and COBOL II programs. See IBMCOBOL for MVS programs

CA-Optimizer options, 6-4compiler options, 6-4dynamically called, 3-13non-purgable data, 6-7online listing display, 6-6post-processors for, 6-1printed output, controlling, 6-6sample JCL, 6-10symbolic support, 6-3

COBOL/370, 3-13

COBOL/370 programssample JCL, 6-10

COMET userssupport, 9-19

Commandslogging, 7-5, 7-6

Composite support

batch preparations, 8-4, 8-5, 8-7composite module, 8-3implementing, 8-1main program, 8-4sample JCL, 8-5subprograms, 8-4subroutines, excluding, 8-5

COMPUTATIONSsupporting, 9-18

COREchanges, verifying, 7-27commands, user-defined, 8-9, 8-15password protection, 7-9, 10-3transaction ID, 7-8

CORET, 7-8

CORSEC, 7-9, 10-1

CORUCOM macro, 8-10, 8-15

CPF11, 7-10

CPLXCKPI, 7-11

CPLXFMID, 7-10

Help file, 4-16

CSA, 7-11

Customer support, 13-1calling, 13-8

Customizationabend codes, specifying ‘no intercept‘,8-22Assembler DSECTs, adding, 8-13CA-InterTest, automatically starting,11-1CICS/COMET users, 9-19composite support, 8-1, 8-3, 8-6COMPUTATIONS, supporting, 9-18CORE commands, 8-9EDF, 9-21global routines, supporting, 9-13help for abend code descriptions, 8-24HOGAN, 9-23HOGAN Users, 9-19


MRO, 9-1options, modifying, 7-1password protection, 10-1Patient Care System CPCS, 9-19SHRINK, 9-19software calls, supporting, 9-9, 9-10,9-13, 9-16user macros, supporting, 9-9, 9-10, 9-13,9-16wild branches, 9-20

CUTPRINT, 6-6, 6-14, 6-20

CWAcreating DSECT, 7-11

CWALET, 7-11creating a CWA DSECT, 7-12

D

Data compressionrestrictions, 3-8

DB2FILE, supporting calls, 4-19JCL for IN25UEXI, 9-16monitoring applications, 4-20supporting, 3-15, 9-8

decompressing PDF files, 4-24

Default userdefining to region, 7-12

DEFCKPT, 4-18

DEFCSD, 4-18

DEFHELP, 4-16

DEFSYM, 4-16

DEFUHLP, 4-16

DELETE, 12-2

Demand Analysis Request (DAR), 14-1

DEQ macros, 4-17

DFHPCPLPA residence, 3-15

DFLTUSER, 7-12CICS default value, 7-13

Diagnostic procedures, 13-1

Distributed Program Link programsmonitoring, 3-15

Distribution libraries, 3-5, 4-10, 14-2

DL/I, 7-12

DL1SIZE, 7-12

DSECTs, adding to Symbolic File, 8-13

DumpsEXTSEC option, 7-13

E

EDF, 9-21

Enhancement requests, 13-10

Errorsdisregarding, 7-10

Exit programIN25LETX, 8-16

EXTSEC, 7-13

F

FDISP, 7-13

FFORM, 7-14

FILEdata display, default, 7-14default COBOL program, 8-20DL/I segment size, 7-12menu, default, 7-13password protection, 7-15, 10-4

Index–5

remote support, 9-6symbolic program name, 7-15transaction ID, 7-15

FILET, 7-15

FILSEC, 7-15, 10-1

FOL option, 9-21

FSYMP, 7-15, 8-20

G

GETMAIN SVC, 7-20

Global routinessupporting, 9-13

Global user exits, 3-7, 3-13in the CICS startup PLT, 3-7requirement, 3-15transaction for viewing, 7-17

GLOG, 7-16

H

Hardware requirements, 3-5

Help file, 4-16customizing abend code descriptions,8-24naming, 7-16transaction ID, 7-16USERHELP keyword, 7-26

HELPFIL, 7-16

HELPT, 7-16

High Level Assembler, 3-12

HOGANconsiderations, 9-23installation steps, 9-24supporting, 3-10, 3-15, 9-23

HOGAN users, 9-19

I

IBM COBOL for MVS programssample JCL, 6-10

ICMDBUF, 7-16

ICMDEXE, 7-16

ICMDMAX, 7-17

IGLUT, 7-17

IN25ABEN, 8-22

IN25ASMP, 4-7

IN25CAPX, 3-12, 6-10

IN25COB2, 3-13, 6-10

IN25DB2, 4-20

IN25LETX, 8-16, 8-18changes for CICS 3.3 and above, 3-15COMMAREA, 8-17disabling, 8-20LETX table, 8-17sample program, 8-18

IN25LINK, 8-2, 8-3, 8-4, 8-5

IN25OPTS, 7-1, 11-2changes for CICS 3.3 and above, 3-14keywords, 7-2, 7-5sample JCL, 7-4

IN25PLT, 11-6changes for CICS 3.3 and above, 3-14

IN25PLTX, 3-7, 3-13

IN25SEC2, 7-7, 7-15, 10-1, 10-10

IN25SYMA, 6-12

IN25SYMC, 6-10

IN25SYMP, 4-7, 4-20, 6-18


IN25UCOM, 8-10, 8-12

IN25UEXI, 3-14, 9-7, 9-10CALLs support, 9-10, 9-11changes for CICS 3.3, 3-15COMET users, 9-19DB2 support, 9-8global routines support, 9-13, 9-14sample JCL, 9-16, 9-18

IN25UTIL, 7-26, 12-1DELETE, 12-2INITIALIZE, 12-1PASSWORD, 12-1PRINT, 12-2PURGE, 12-1RELOAD, 12-2REPORT, 12-2UNLOAD, 12-2

IN25VIRC, 9-2

IN25VRPT, 4-21

Indirect commands, 7-16

Informational APAR or PIB, 14-4

INITIALIZE, 12-1

InstallationACCEPT, 4-14, 5-3APPLY, 4-2, 4-10, 4-12, 4-13, 4-14, 4-15,4-16, 4-19, 5-1, 5-2, 5-3, 14-9CA-InterTest, activating, 4-26CA-InterTest, deactivating, 4-27check-out program, 4-21checkpoint file, 4-18CICS JCL, adjusting, 4-19CICS, restarting, 4-21customizing SMP procedure, 4-12DB2 applications, monitoring, 4-20DB2 calls in FILE, supporting, 4-19distribution libraries, 3-5, 4-10Help facility, 4-16Help facility, user-defined abend codes,4-16JCL library, 4-9LMP, 4-4

LMP for CA-SymDump, 4-7LMP for PL/I, 4-7, 5-2materials, 2-2migrating to CICS 3.3 or above, 3-14options program, 7-1overview, 4-1RECEIVE, 4-12, 5-2resource definitions, adding, 4-18SMP procedure, 4-12SMP zones, defining, 4-11steps, summary of, 4-2Symbolic File, 4-16system requirements, 3-1, 4-3tape, 2-2target libraries, 3-5, 4-10Unicenter TNG Framework for OS/390sServices, 4-4worksheet, 4-7

INT54041, 4-18

Internet, CA site, 13-4

IPLXT, 7-17

IRCTT, 7-17

ISER, 4-27, 7-17

ISERT, 7-17

ITSTT, 7-18

J

JCLediting maintenance JCL, 14-8

JCL library, 4-9

K

Keep window, 2-3

Index–7

L

LET, 7-11, 8-16

LETSVC, 7-18

LETX table, 8-17

Librariesdistribution, 3-5, 4-10, 14-2SMP/E, 14-2target, 3-6, 4-10, 14-2

LicensingCA-TLC

Total License Care, 13-7

LISTAUTOKEEP display, 7-22margin, default, 7-23scroll amount, default, 7-23titles display, default, 7-23transaction ID, 7-18

LISTER, 6-6, 6-15, 6-21

LISTT, 7-18

LMP, 3-2, 3-3key certificate, 4-4key certificate for CA-SymDump, 4-7key certificate for PL/I, 4-7

Logging, 7-5, 7-6CNTL commands, 7-8, 7-10transient data destination, 7-16

Lower case terminals, 3-13

LPArestriction lifted, 3-15

M

MA54ACC, 5-3

MA54APP, 5-2

MA54REC, 5-2

MaintenanceACCEPTing, 14-13APPLY CHECKing, 14-10APPLYing, 14-11CA-SymDump, 14-2customizing SMP procedure, 14-8delivery, 14-4diagnostic procedures, 13-1editing JCL, 14-8overview, 14-2RECEIVing, 14-10saving, 14-13Symbolic File, 12-1validating, 14-12

Migration considerations, 3-14

Monitoring by user IDsetting the default, 7-12

MONOM, 7-19

MONOMSEC, 7-19

MROconsiderations, 9-1monitoring considerations, 9-5

CSD entries, 9-3DFLTUSER, 9-3non-secure regions, 9-4secure regions, 9-4

support, 3-11two-terminal testing, 9-5

N

Naming conventionsfor PTFs, 14-5

NOPURGE, 6-7, 6-15, 6-22


O

Omegamon, 3-11

Operating environmentsCA-InterTest, 3-1CA-SymDump, 3-14

Optionsdefaults, 7-2modifying, 7-1sample JCL, 7-4

OSGETM, 7-20

P

PASSWORD, 12-1

Password protectionCNTL, 7-7, 10-5, 10-8CNTL options, 7-8, 7-9, 7-10, 10-8CNTL options, disabling, 10-8CORE, 7-9, 10-3DL/I, 10-4FILE, 7-15, 10-4overview, 10-1parameters, 10-2sample JCL, 10-10

Patient Care System (PCS), 9-19

PDF files, unloading, 4-24

PL/I arrays, 2-3

PL/I optionACCEPT, 5-3APPLY, 5-2installing, 4-21, 5-1RECEIVE, 5-2

PL/I programscompiler options, 6-19date-time checking, 6-19installation options, 6-19

LMP, 4-7non-purgable data, 6-22online listing display, 6-21printed output, controlling, 6-20sample JCL, 6-23symbolic support, 6-18

PLTCA-InterTest, automatically starting,11-6

Post-processors, 6-1

PRINT, 12-2

Product Information Bulletins (PIBs), 14-4

ProgramsAssembler, 6-12CA-InterTest, automatically starting,11-5CNTL commands, issuing, 11-5COBOL and COBOL II compileroptions, 6-3COBOL/370 compiler options, 6-3listing, printing, 12-2Monitor Table entries, creating atbreakpoint, 7-6PL/I, 6-18printing, 12-6purging, 12-3, 12-4reloading, 12-5Symbolic File, deleting from, 12-2unloading, 12-5

PROMD, 7-20, 7-21, 7-22, 11-2

PROMMAC macro, 11-1

PROTFILE, 8-20

PROTSYM file, 4-19concurrently updating, 4-17

PROTUHF, 7-26maintaining entries to user-help file,8-24

PTFsmaintenance tape installation, 14-5overview, 14-5

Index–9

PURGE, 12-1

Purgingprograms, 12-3, 12-4

Q

Quick references, printing, 4-25

R

RACF, 3-10

Read buffer, 7-21

READBUF, 7-21

REALIA2, 7-21

RE-APPLYingSYSMODs, 14-12

RECEIVECA-InterTest, 4-12maintenance, 14-8PL/I option, 5-2

RECEIVingmaintenance, 14-10

RECNTMU, 7-21

RECNTNW, 7-22

RELOAD, 12-2

Reloading programs, 12-2

Remote FILE Support, 3-15, 9-6

Replacement module, 14-5

REPORT, 12-2

RESERVE/DEQ macro, 4-17

Resource definitionsadding, 4-18

RESTOREcommand, 14-3RESTORing SYSMODs, 14-11

S

Savingmaintenance, 14-13

Secure Sockets Layer (SSL), 13-5

SecurityCA-TCC, 13-5StarTCC, 13-5

Segmented monitoring optionHOGAN usage, 9-24MONOM, 10-9password protection, 10-1, 10-9

SHRINKsupporting, 9-19

SLB, 7-22

SLBMARG, 7-22, 7-23

SLBSCRL, 7-23

SLBTIT, 7-23

SMP/Ecustomize procedure, 14-8introduction, 14-2libraries, 14-2maintenance, 14-2procedure, 4-12zones, 4-11

Softwarecalls, supporting, 9-9, 9-10, 9-13, 9-16

Source Listing Display menu, 2-3

StarTCChotline, 13-7

STB4, 7-24

STBTRN, 7-24


Storageprotection, removing, 7-11protection, with CICS/ESA 3.3, 3-15

STUAR, 7-24

SVCsGETMAIN, 7-20permitting, 7-18

Symbolic Fileadding COBOL file structures, 8-20creating, 4-16data, deleting, 12-2data, reloading, 12-2data, unloading, 12-2entries, 4-17initializing, 12-1maintenance, 12-1migration considerations, 3-12naming, 7-25password protection, 7-26, 12-1purging, 12-1reports, 12-2source listing, printing, 12-2

SYMD, 7-25

SYMDFIL, 7-25

SYMDINT, 7-25

SYMFIL, 7-25

SYMPSWD, 7-26, 12-1

SYSMODsACCEPTing, 4-14APPLYing, 4-13Re-APPLYing, 14-12RECEIVEing, 4-12RESTORing, 14-11

System requirements, 3-1, 4-3

T

Tape

installation, 2-2numbers, 14-7

Target libraries, 3-5, 4-10, 14-2

TCTTE user area, 7-24

Technical supportcalling, 13-8

Technical Support Phone Services Directoryaccessing online, 13-7

TIOA compressionrestrictions, 3-8

TMON, 3-10

TroubleshootingCA-TCC (CA-Total Client Care), 13-4

U

UCONLYtranslate to uppercase, 7-26

UEXIHOGN, 9-19

UNICENTER TNG FRAMEWORK FOROS/390s Services, 3-2

UNLOAD, 12-2

Unloading programs, 12-2

UppercaseUCONLY keyword, 7-26

User macrossupporting, 9-9, 9-10, 9-13, 9-16

USERHELP, 7-26

USERMOD, 14-4

V

VERCOR, 7-27

Index–11

Verification programtransaction definition, 7-27

VIRC, 7-17, 9-2

VRPT, 4-21

VRPTT, 7-27

VTAT, 7-27, 9-1

VTATT, 7-27

W

Wild branchesFOL option, 9-21

handling, 9-20monitoring, 9-20

Worksheet, 4-7

Z

Zonesadditional, 4-11distribution, 4-11global, 4-11target, 4-11

Int60oG1

Documents

Transcript of Int60oG1