Source Listing Facility for InterTest

Use the CA InterTest for CICS Source Listing facility to debug your program while viewing your source code. You can access all of the other CA InterTest for CICS facilities -- ITST, CNTL, CORE, FILE, HELP and SYMD (for CA SymDump for CICS licensed users) directly from the Source Listing facility using menus or single-line commands.
caitsd-11-0
Use the CA InterTest for CICS Source Listing facility to debug your program while viewing your source code. You can access all of the other CA InterTest for CICS facilities -- ITST, CNTL, CORE, FILE, HELP and SYMD (for CA SymDump for CICS licensed users) directly from the Source Listing facility using menus or single-line commands.
As you become familiar with the Source Listing facility, keep in mind that there is no such thing as a cookbook method of using CA InterTest for CICS. How you use it depends on your particular testing needs.
For more information, see Composite Module Testing.
1
Prepare Your Program
  • This section describes the procedure for using PROTSYM as a symbolic format. For instructions on preparing your program with DWARF as a debugging format, see DWARF.
  • For detailed instructions on how to modify your JCL, see Symbolic Support.
To prepare a program for source listing testing and symbolic testing, you must modify the compile or assemble JCL to include a CA InterTest for CICS post-processor step. For source listing testing, the LISTER parameter of the post-processor is required. After modifying the JCL, recompile or reassemble the program. This puts the program's listing in the CA InterTest for CICS Symbolic File.
Start CA InterTest in Your CICS Region
CA InterTest for CICS is generally started once a day. At many sites, CA InterTest automatically starts during CICS initialization. Additionally, CA InterTest automatically starts whenever you complete a monitoring-related request from the Monitoring Menus or Submenus (Option 2 on the Primary Option Menu).
To start CA InterTest for CICS or to verify that CA InterTest for CICS is up and running, sign on to CICS and issue the following command on a Clear screen:
CNTL=START
CA InterTest for CICS responds with a message stating either that it has successfully started or that it is already active. If CICS responds with a message stating that CNTL is an invalid transaction, the systems programmer who installed CA InterTest for CICS probably changed the name of the CNTL transaction. Find out the new transaction ID and try again.
CA InterTest for CICS Transaction IDs
CA InterTest for CICS has the following standard transaction IDs: ITST, CNTL, CORE, FILE, LIST, HELP, and an additional transaction ID for licensed CA SymDump for CICS users: SYMD. These IDs might have been modified when CA InterTest for CICS was installed. If the HELP transaction ID was not modified, you can learn your current transaction IDs by entering Help on a Clear screen.
Start a Test Session
To begin testing, be sure you have compiled or assembled your program with the CA InterTest for CICS post-processor step using the LISTER parameter, and then set monitoring and breakpoints in your program.
Follow these steps:
  1. Perform CICS sign on.
  2. Display your source code.
  3. Set monitoring.
  4. Set breakpoints.
  5. Initiate your program and begin testing.
Perform CICS Sign On
If you are working in a secure CICS region, always sign on to CICS before using CA InterTest for CICS. CA InterTest for CICS monitoring is sensitive to CICS user IDs.
Display Your Source Code
Access the CA InterTest for CICS Source Listing facility using the following methods to view the compiled or assembled listing of your program:
  • ITST Primary Menu Option access, Option
    1 Source
  • Command access:
    LIST=
    progname
Menu Access
Use the ITST Primary Menu, Option
1 Source
, to select your program from a selection list by program name or by SYMBOLIC file name. For details, see Source Selection List.
Command Access
To use the single-line CICS command, sign on to CICS. On a clear screen, enter:
LIST=progname
  • progname
    Specifies the name of your program.
CA InterTest for CICS displays your program on the Source Listing Display screen. From this screen set monitoring and breakpoints.
If a message informs you that the listing is not available, consider the following:
  • Is the program name correct?
  • Is the program in the CA InterTest for CICS Symbolic File?
  • Was the program compiled or assembled with the LISTER option?
If there are multiple copies of the program you specified, CA InterTest for CICS asks you to select the program that you want to run. When you make your selection and press Enter, CA InterTest for CICS displays the Source Listing of your program. For more information, see Maintain Synchronized Processing.
Set Monitoring
While viewing the program listing, enter
monitor
in the top Command Line. This is the same as pressing
PF5 Monitor
.
CA InterTest for CICS monitoring and breakpoints include a CICS user ID option. For a discussion of this option, see Set Monitoring.
Set Breakpoints
Setting breakpoints enables you to control program execution. CA InterTest for CICS halts program execution when the program reaches a breakpoint, which lets you use any CA InterTest for CICS facility before continuing execution.
Initiate Program and Begin Testing
To exit to CICS, press
PF3 End
or
Clear
to terminate the Source Listing facility. If you entered through the menus, exit the menus using
=X
or
PF3 End.
To begin testing, execute the program as you normally would. In a secure CICS region, be sure to sign on to CICS before executing the program.
The Source Selection List
From CICS, use the ITST transaction to display the CA InterTest for CICS Primary Option Menu. Select Option
1 Source
to display the CA InterTest Source Menu.
This menu has two uses:
  • Display a listing or a list of listings (type
    1
    in the Option field).
  • Display a symbolic file or a list of symbolic files (type
    2
    in the Option field), and then select a Symbolic file to display the Program Listings for that file.
In the unlabeled text fields, enter either the listing name or the CA InterTest for CICS Symbolic File name. Use masks to filter the selection list for items matching the filter criteria:
  • Use
    *
    in place of a string of any length.
  • Use
    +
    for a single character.
Example
A mask of COBD++O filters for any seven letter item that begins with the letters COBD, has an O in the last position, and has any valid character in the fifth and sixth positions. For instance, COBDEMO, COBDXXO, and COBDABO would all meet the mask criteria, but COBDEML or COBDEM would not.
  • Leave the fields blank to display
    all
    symbolic files or listings.
Once you specify a listing, file or mask and press
Enter,
CA InterTest for CICS displays the Source Listing Selection menu, showing all the files or listings meeting the criteria you specified on the Source Menu. Type
S
next to the file or listing you want and press
Enter
to display that file or listing in the Source Listing display. The following screen shows a sample result of the criteria entered on the Source Menu shown previously.
CA InterTest for CICS SOURCE LISTING SELECTION COMMAND ===> Name File Created Size Attributes _ CICSCOBA PRTSYM1 09/20/13 16:38 29 COBOL II, no purge _ CICSCOBB PRTSYM1 09/20/13 16:13 21 COBOL II, no purge _ COBDEML PROTSYM 07/07/13 09:32 17 COBOL, no purge, composite _ COBDEMO PROTSYM 07/07/13 09:25 70 COBOL, no purge _ COB2DEML PROTSYM 07/07/13 09:33 25 COBOL II, no purge, composite _ COB2DEMO PROTSYM 07/21/13 10:34 158 COBOL II, no purge _ COB2DMLX PRTSYM1 09/21/13 16:10 26 COBOL II, no purge, composite _ COB2INSP PRTSYM1 02/01/13 09:11 155 COBOL II, no purge _ COB2IN25 PROTSYM 07/07/13 09:31 11 COBOL II, no purge _ COB2XCTL PRTSYM1 09/22/13 13:38 159 COBOL II, no purge _ CSBIN25 PROTSYM 07/07/13 09:29 8 COBOL, no purge _ C370DEML PROTSYM 07/07/13 09:33 27 COBOL/370, no purge, composite _ C370DEMO PROTDGG 12/12/13 12:51 161 COBOL/370, no purge _ C370DEMO PROTWSD 12/12/13 12:51 161 COBOL/370, no purge _ C370DEMO PROTSYM 07/21/13 16:35 161 COBOL/370, no purge _ C370IN25 PROTSYM 07/07/13 09:32 12 COBOL/370, no purge *** End of data *** PF1 Help 2 Refresh 3 End 4 Return 5 6 PF7 Backward 8 Forward 9 10 11 12
Examine the Source Listing Display Screen
A sample COBOL source listing is shown next:
CA InterTest for CICS - PROTSYM FILE SOURCE LISTING DISPLAY COMMAND ==> Program= COBDEMO Option # Stmt # Margin= 01 Search= OPTS 1 Proc div 2 Workstor 3 Link sect 4 Dmap 5 Clst/Pmap More: ‘+ 6 Data xref 7 Proc xref 8 Err msgs 9 Srch fwd 10 Srch bwd PFKS 1 Help 2 3 End 4 Profile 5 Monitor 6 Menu 7 Backward 8 Forward 9 Next Wnd 10 11 12 Status ------------------------------------------------------------------------------ _ 00001 ID DIVISION. _ 00002 PROGRAMID. COBDEMO. _ 00003 ENVIRONMENT DIVISION. 00004 DATA DIVISION. _ 00005 WORKINGSTORAGE SECTION. _ 00006 77 S999FIELD1 PIC S9(3). _00007 77 S999FIELD2 PIC S9(3) VALUE +50. _ 00008 77 999FIELD1 PIC 9(3). _ 00009 77 999FIELD2 PIC 9(3) VALUE 50. _ 00010 77 FIRSTSCREENLEN PIC S9(4) COMP VALUE +1696. _ 00011 77 MSGSCREENLEN PIC S9(4) COMP VALUE +1040. _ 00012 77 THIRDSCREENLEN PIC S9(4) COMP VALUE +960. _ 00013 77 FOURTHSCREENLEN PIC S9(4) COMP VALUE +1761. _ 00014 77 ERRORSCREENLEN PIC S9(4) COMP VALUE +960. 00015*77 COMMAREALEN PIC S9(4) COMP VALUE +39.
Field Definitions
This section explains the Source Listing Display screen.
The top of the screen displays the title and indicates when a monitor session is being recorded. A flashing "REC" at the end of the title indicates active recording.
Fields in which you enter commands and information:
  • COMMAND ===>
    Enter any CA InterTest for CICS transaction, transaction-based command, or a Source Listing Display command. Enter =X.Y.Z for fast-path menu access to Primary Option Menu X.Y.Z. You cannot use this command line to enter a system-wide CNTL command.
  • Program=
    Change the program whose code displays.
  • Option #
    Enter an option listed on OPTS lines by number, or enter shortcut codes for CNTL functions.
  • Stmt #
    Display a specific statement.
  • Nested=
    Indicates the displayed COBOL nested program or the program to be searched.
    The COBDEMO program does
    not
    contain nested programs. However, if a program does contain a nested program, it displays here.
  • Margin=
    Adjust the display margins to view code past position 80.Source Listings Command Line
  • Search=
    Instruct CA InterTest for CICS to search for a data name or string.
  • OPTS
    Lists entries for the Option # field. Valid options for COBOL, Assembler, and PL/I are listed in Source Listing Option Field Entries.
  • PFKS
    Describes the PF key functions. The bottom half of the Source Listing display screen displays source code from the program named in the Program= field.
Position 1 (represented by the underscore _) of each line is reserved for entering single-letter commands and for breakpoint-related functions.When a breakpoint takes effect during execution, it is identified in position 1 with one of the following letters:
  • A
    Automatic, detected by CA InterTest for CICS
  • U
    Uncon
    ditional "before" breakpoint (stops execution
    before
    the specified item)
  • )
    Unconditional "after" breakpoint (stops execution
    after
    the specified item)
  • C
    Conditional
  • V
    Variable-change
  • R
    Request
The bottom of the Source Listing Display contains the source code. The numbers on the left side of each line are the COBOL or PL/I statement numbers from the compiled listing, or the Assembler hexadecimal location number from the assembled listing.
For COBOL and PL/I programs, there are more OPTS to view. A
More
field displays to the right of the OPTS entries. Tab to
More +
and press
Enter
to view OPTS 5 to the end. Tab to
More -
and press Enter to view OPTS 1 to 10.
The display screen's format varies by terminal type. For 132-column terminals, lines of code display as is and you view them in full. For 80-column terminals, CA InterTest for CICS automatically reformats the compiler output so that you view most of the code in columns 1 to 80. Code beyond column 80 is viewed by changing the display margins in the Margin= field. For details, see Adjust the Margins.
Source Listing Option Field Entries
The numbers listed in the following table are used in the Option # field to display specific sections of the source listing or to search for data. Using these options makes it easy to locate specific sections of your program.
For PL/I programs, all of the OPTS labels cannot be displayed at once. Tab to the
More
field and press
Enter
to view options not currently displayed.
Option
COBOL
PL/I
Assembler
1
* Procedure Division
Data Name XREF
First CSECT
2
* Working-Storage
Aggregate Length Table
-
3
* Linkage Section
Storage Requirements
-
4
Data Division Map
Static Storage Map
-
5
CLIST/Pmap
Variable Storage Map
Macro and Copy Source Catalog for high level output
6
Data Name XREF
Table of Offsets
Cross Reference
7
Procedure Cross Reference
Generated Code (Assembler-like)
Literals Cross Reference
8
Error Messages
Error Messages
Error Messages
9
Search Forward
Search Forward
Search Forward
10
Search Backward
Search Backward
Search Backward
11
Indirect Commands
Indirect Commands
12
Unconditional/Conditional   Breakpoint Options
Unconditional/Conditional Breakpoint Options
Unconditional/Conditional   Breakpoint Options
13
*Local-Storage
Procedure Cross Reference
-
14
-
Labels Cross Reference
-
20
Window: None
Window: None
Window: None
21
Window: Titles
Window: Titles
Window: Titles
22
Window: Registers
Window: Registers
Window: Registers
23
Window: Keep
Window: Keep
Window: Keep
24
Window: Program
Window: Program
Window: Program
*
Use these options with NESTED= entries to request a display of these sections for a specific nested program.
The sections available for display depend on which version of the post-processor LISTER parameter was used to compile or assemble the program.
Source Listing Command Line
The command line is located at line 2 of the Source Listing display so it is always available, regardless of what view options are currently in use. Use this command line to enter any CA InterTest for CICS transaction, a transaction-based line command (such as a CNTL command or CORE command), and the Source Listing Display commands listed in the following table.
You cannot use this command line to enter CA InterTest for CICS system-wide CNTL options.
Command
PF Key
Description
ABEND
None
Display the Abend Breakpointed Task screen (this command is available only at a breakpoint)
ABI ON
None
Default. Turn Abend Intercept on -- intercepts all CICS abends and produce an automatic breakpoint screen providing there a CICS HANDLE ABEND LABEL/PROGRAM is not active. If you want to intercept CICS abends for programs that have an active CICS HANDLE LABEL/PROGRAM then see the ABI FORCE command.
ABI OFF
None
Turn Abend Intercept off -- causes CA InterTest for CICS to stop intercepting CICS abends. No automatic breakpoint screen appears and the program abends.
ABI FORCE
None
Turn Abend Intercept on for all CICS ABENDS -- even if a program has an outstanding HANDLE ABEND active or issues a CICS HANDLE ABEND command.
Use this option when you want an automatic breakpoint screen for programs that also have active HANDLE ABENDS to process their own errors.
ADVANCE n
ADV n
A n
None
Advances n entries in the statement trace table and displays the resulting statement. (If n is not specified, it defaults to 1.) If data monitoring is active, past data values for the statement can also be displayed. Use this command to redisplay the execution sequence of a program. Statement tracing must be active for the ADVANCE command to function (see the TRACE option).
Note:
This command is only valid for COBOL programs.
AUTOSTEP x y
AS x y
None
Resume execution x verbs at a time displaying the current source statement for a y interval of time. This command is only available at a breakpoint. One verb at a time until next CALL/COMMAND is the default.
Note:
This command is available only at a breakpoint.
BOTTOM
BOT
None
GO to bottom of source
BPO
None
Jump to Breakpoint Option screen
BWD
PF7
Scrolls backward. The scroll amount is set on the Source Listing Profile.
CALLTRACE
None
Shows the program call flow leading up to the currently breakpointed program. Select programs having symbolic support from the list and display their data areas.
CHANNEL
None
Displays the currently allocated channel and the containers in the channel. From the selection list you can also display the data within a container. This feature is only valid in CICS releases that support CHANNELs and Containers.
CNTL
None
Displays the CNTL Command Menu.
Note:
The Monitoring Menu (2) is an alternative to using the CNTL menu; for details, see Monitoring Menu Options.
COMPOSITE
None
Sets composite monitoring options for monitoring of subprograms. This command is used to establish the current load module name when setting/removing breakpoint options on subprograms that are monitored under the same name in more than one composite load module. For more details, see Composite Support.
CORE
None
Displays the Main Storage menu. Select an option to view a main storage (CORE) display.
COUNTS SHOW
None
Turns the Code Coverage COUNTER display on. To activate Code Coverage see Customizing the Source Listing Profile or issue PROFILE command.
COUNTS NOSHOW
None
Turns the Code Coverage COUNTER display off. To deactivate Code Coverage see Customizing the Source Listing Profile or issue the PROFILE command.
COUNTS RESET
None
Resets the program Code Coverage statement counters to zero.
COUNTS op value
None
Turns the Code Coverage COUNTER display on and highlights program statements that match the criteria. The source listing is repositioned to the first statement matching the criteria.
Op can be: EQ or =, NE or <>, LT or <, GT or >, LE or <= or =<, GE or >= or =>
Valid values: 0 to 9999
COUNTS NEXT
None
Repositions the source listing to the next statement that matches the previously specified COUNT op value criteria.
COUNTS ALL
None
Removes previously specified COUNT op value criteria and redisplays source listing without special COUNTER highlighting.
DATAMON
DM
None
Displays the Monitoring Command Builder menu to set and remove statement tracing and data monitoring.
Note:
This command is only valid for COBOL programs.
DATAMON ON
DM ON
None
Turns data monitoring on. This causes CA InterTest for CICS to capture data values for each executed statement in the program. You will then be able to redisplay these values at a breakpoint, by tracing backward and forward through the entries in the statement trace table using the PREV and ADVANCE commands. DATAMON ON forces TRACE ON.
Note:
This command is only valid for COBOL programs.
DATAMON OFF
DM OFF
None
Turns data monitoring off. This causes CA InterTest for CICS to stop capturing data values for each executed statement in the program. In addition, you are no longer able to display captured data values when tracing backward and forward through the entries in the statement trace table using the PREV and ADVANCE commands.
Note:
This command is only valid for COBOL programs.
DISPLAY data-item
D data-item
None
Displays the storage of a data-name. (this command is available only at a breakpoint)
DOWN
None
Shifts listing down
END
PF3
Returns to the prior display or menu.
FILE
None
Displays the Auxiliary Storage Menu. Select an option to view a file or queue.
FIND
F
None
Find a string.
FP
None
Find paragraph.
FS
None
Find statement number.
FWD
PF8
Scrolls forward the amount indicated on the Source Listing Profile.
HELP
PF1
Displays help for the Source Listing Facility.
IC
None
Jump to Indirect Command screen.
ITST
See MENU
Displays the ITST Primary Option Menu.
KEEP data-item
K data-item
None
Add a data-item to the static Keep window
LEFT
None
Shift listing left.
LOCATE
LOC
L
None
Locate line number, a label, or part of the listing.
MARGIN
MAR
None
Shift listing to specific margin.
MENU
PF6
Displays the high-level menu. When not at a breakpoint, it is the ITST Primary Option Menu; when at a breakpoint, it is the Breakpoint Primary Option Menu.
MLOG
None
Displays, starts, stops, cancels, or loads recorded monitoring sessions.
MONITOR
PF5
Sets monitoring for the current program using the CICS user ID displayed on the Profile.
OFFALL
None
Removes all breakpoints set by active USER or TERMINAL Active USERID is used if a valid USERID is signed on. Otherwise, the active TERMINAL is used
ALL breakpoints for ALL programs/transactions/ will be removed that were set by the active USERID or active TERMINAL.
OFFALL TERM
None
Removes all breakpoints set by active TERMINAL
OFFALL USER
None
Removes all breakpoints set by active USER.
PO
None
Sets or removes storage protection options
PREV n
P n
None
Backs up n entries in the statement trace table and displays the resulting statement. (If n is not specified, it defaults to 1.) If data monitoring is active, you can also display past data values for the statement. Use this command to step backward through the execution of a program. Statement tracing must be active for the
PREV command to function (see the TRACE option).
Note:
This command is only valid for COBOL programs.
PROFILE
PF4
Displays Source Listing Profile, where you can change settings for the current session.
RBP
None
Sets or removes request breakpoints
RIGHT
Shifts listing right
RO
None
Sets or removes replacement options
RUN
None
Resumes execution ignoring all breakpoints. This command is available only at a breakpoint.
SET
None
Initializes a data-item's value. This command is available only at a breakpoint.
SO
None
Sets or removes special options
SDFDATA
None
Set to display data in structure display format for the current program.
SDFHEX
None
Set to display data in hexadecimal/ character format for the current program.
STATUS
PF12
Displays the Monitoring Status report (Option 2.4 on the Primary Option Menu) for the current program. You can remove monitoring, breakpoints, and options directly from the Status display.
STATUS ALL
None
Displays the Monitoring Status report for all programs, transactions, and terminals CA InterTest for CICS is monitoring in the region.
STORAGE
None
Displays a listing off all USER and CICS class storage associated with the currently breakpointed task (most storage acquired by CA InterTest for CICS is not displayed), this command also validate the crumple zones for each piece of storage. See The STORAGE Facility.
TOP
None
Go to top of source.
TRACE
TR
None
Displays the Monitoring Command Builder menu to set and remove statement tracing and data monitoring.
Note:
This command is only valid for COBOL programs and is unrelated to the backtrace facility.
TRACE ON
TR ON
None
Turns statement tracing on. The number of entries saved in the statement trace table is determined by the STMTTRCE option in IN25OPTS. The default is 1000.
Note:
This command is only valid for COBOL programs and is unrelated to the backtrace facility.
TRACE OFF
TR OFF
None
Turns statement tracing off. TRACE OFF forces DATAMON OFF.
Note:
This command is only valid for COBOL programs and is unrelated to the backtrace facility.
UP
None
Shift listing up.
=x.y.z
None
Fast-path to Primary Menu Option x.y.z.
Action Characters Supported from a Source Listing Display or Breakpoint
You can perform the following list of the functions by entering a single character on your source listing.
Documentation
Action Character
Function
Using Breakpoints
u
Unconditional; sets an unconditional breakpoint that stops
before
the specified item.
)
Unconditional; sets an unconditional breakpoint that stops
after
the specified item.
c
Conditional; sets a conditional breakpoint.
v
Variable-change; sets a variable-change conditional breakpoint (for COBOL or Assembler programs).
x
Remove; removes a breakpoint or removes a variable from the Keep window.
+
Start Segmented Monitoring  at this program statement.
-
Stop Segmented Monitoring  at this program statement.
Breakpoint Activities
d
Display; displays program or variable storage at a breakpoint.
k
Keep; keeps a variable in the Keep window.
m
Modify; modifies a variable at a breakpoint.
@
Display; displays the main storage area pointed to by a data item for a 24-bit address.
%
Display; displays the main storage area pointed to by a data item for a 31-bit address.
<
Scroll keep data left the   width of the display area. To scroll a specific number of bytes,   specify a value after the < .
>
Scroll keep data right the   width of the display area. To scroll a specific number of   bytes, specify a value after the > .   
+
Increment (Keep window only); increases COBOL index item value. To increase by a specific value, specify a value after the +.
-
Decrement (Keep window only); decreases COBOL index item value. To decrease by a specific value, specify a value after the -.
Resume and Execution Options
b
Bypass; bypasses monitoring of an instruction at an automatic breakpoint.
g
Go (resume execution) at this program statement.
The v, d, @, %, k, and m functions should be entered next to a statement that references or defines the variable that you want to display, keep, or modify. If the statement references the variable, you must also position the cursor under the variable name before pressing Enter.
Shortcut Commands for CNTL Functions
To access a CNTL function, enter a code using the following format in the Option # field, and press Enter:
=nns OR =nnr
  • =
    Required.
  • nn
    Specifies function number (10 to 33) from the CNTL main menu.
  • s
    or
    r
    S
    pecifies setting or removing the option .
While the CNTL shortcut commands are supported, you will find it easier to use the Monitoring Menus, available from Primary Option Menu Option
2 Monitoring
.
The following table summarizes the Option # codes you can enter for the standard CNTL Selection Menu functions:
Option # Command
CNTL Selection Menu Function
=10s
Sets monitoring for the program displayed; same as PF5.
=10r
Removes monitoring, breakpoints, and all other options for the program displayed.
=11s and 11r
Sets and removes unconditional breakpoints.
=12s and 12r
Sets and removes conditional breakpoints.
=13s and 13r
Sets and removes request breakpoints.
=14s and 14r
Sets and removes Segmented Monitoring On option.
=15s and 15r
Sets and removes Segmented Monitoring Off option.
=16s and 16r
Sets and removes statement tracing and data monitoring.
=20s and 20r
Sets and removes Replace options.
=21s and 21r
Sets and removes Protection options.
=22s and 22r
Sets and removes Special options.
=23s
Sets Composite Support.
=24
Accesses the Indirect Commands facility.
=30
Shows the Status Display screen.
=31
Sets Utility Options screen.
=33
Resumes task execution.
Source Listing PF Keys
The following table summarizes the PF key functions for the Source Listing Display screen. PF key assignments are standard across all CA InterTest for CICS menus.
The ITST menus and relocated command line eliminate the need to assign CNTL, CORE, and FILE to PF keys. Navigate to these facilities using the menus, or use the command line to enter the transaction or desired single-line command.
PF Key
Function
PF1 Help
Help; displays a Help menu relating to the current Source Listing Display screen.
PF2
Unassigned.
PF3 End
End or Clear; terminates the Source Listing Facility. Displays an earlier ITST panel, if applicable, or CICS.
PF4 Profile
Displays the Source Listing Profile screen, where you can set values for your current session.
PF5 Monitor
Turns monitoring on for the program whose listing is being viewed using the CICS user ID on the Profile.
PF6 Menu
Displays the Primary Option Menu.
PF7 Backward
Scrolls the compiler output backward by one page unless the setting was changed on the Profile. Does not apply within the Keep window.
PF8 Forward
Scrolls the compiler output forward by one page unless the setting was changed on the Profile. Does not apply within the Keep window.
PF9
Switch to next window
PF10, PF11
Unassigned.
PF12 Status
Displays the Monitoring Status for the current program. You can remove breakpoints and options directly from the Status display.
Search for Data
You can request CA InterTest for CICS to define, search for, and display any character string (such as a data item, label, or paragraph name). This is a quick way to go to different areas in a listing when you want to set a breakpoint or check your code.
Search for data using the Search=field, or by entering a FIND or LOCATE command on the command line.
If you know the line number that you want to view, use the line command to position the listing accordingly. For details, see View the Online Listing.
Find a Definition or Search Using the Search = Field
Use the Search= field to define or search for data as follows.
To display the definition of a data item:
  1. Enter a data item name up to 31 characters in the
    Search=
    field.
  2. Press Enter to begin the search. CA InterTest for CICS highlights the data item and its definition.
To search for a data item:
  1. Enter up to 31 characters in the
    Search=
    field.
  2. Specify the search direction in the Option # field. (Option # 9 is Search Forward; Option # 10 is Search Backward.)
  3. Press
    Enter
    to begin the search.
For COBOL nested programs, CA InterTest for CICS first searches the current nested program (indicated in the NESTED= field) for the specified data item. If the data item is not found in the indicated program, CA InterTest for CICS then searches the main program and other nested programs for the item.
It is not necessary to enter the entire data item, label, or paragraph name; enter the first few characters to start your search.
Example
If you wanted to search for TASKNUM, you could enter TASK, TASKN, and so on, in the Search= field.
Search the Program Online Listing
To find the next string within a program online listing, enter:
FIND string NEXT
  • String
    Specifies any valid string (up to 31 characters in length). If the string contains a blank, it must be enclosed in apostrophes ('). If the string contains an apostrophe ('), it must be enclosed in quotes (").
To find the previous string within a program online listing, enter:
FIND string PREV
To repeat the find request, press
Enter
.
Locate an Area Within the Program Online Source Listing
To locate a label, line-number, offset, or special area within the program online source listing, enter:
LOCATE label | line-number | hex-offset | .xx
  • label
    Indicates any valid label with an ASSEMBER, COBOL or PL/1 program including datanames, CSECT, procedure, and paragraph names (up to 31 characters in length).
An all numeric COBOL paragraph name cannot be located; it is interpreted as a line number.
  • Line-number
    Indicates any line number within an ASSEMBLER, COBOL or PL/1 program.
  • Hex-offset
    Indicates any offset within an ASSEMBER program and is indicated with a leading + character.
  • .xx
    Indicates a special indicator depending on language as follows:
    • COBOL:
      PD = Procedure Division
      WS = Working-Storage Section
      LC = Local-Storage Section
      LS = Linkage Section
      DM = DMAP
      PM = COBOL/VS PMAP/CLIST
      CL = COBOL/VS PMAP/CLIST
      OF = COBOL II OFFSET/LIST
      LI = COBOL II OFFSET/LIST
      DX = Data Name Cross Reference
      .PX = Procedure Cross Reference
      .EM= Error Messages
    • PL/1:
      .AG = Aggregate List
      .SR = Storage Registers
      .SS = Static Storage
      .VS = Variable Storage
      .OF = Offsets
      .GC = Generated Code
      .PX = Procedure Cross Reference
      .LX = Label Cross Reference
      .DX = Data Name Cross Reference
      .EM = Error Messages
    • ASSEMBLER:
      .C1 = 1st CSECT
      .1C = 1st CSECT
      .MC = Macro Catalog
      .XR = Cross Reference
      .LI = Literals
      .EM = Error Messages
View the Online Listing
Use the command line commands to position or shift the view of the listing. You can go to the top or bottom of the listing, shift the listing to the right or left a specific number of characters, or position the listing to a specific line.
Position Listing at Top
To position the listing at the top of the source code within the complete online listing, enter
TOP
.
Position Listing at Bottom
To position the listing at the bottom of the source code within the complete online listing, enter
BOTTOM
.
Shift Listing to the Right
To shift the listing to the right a specific number of characters, enter
RIGHT char-count
  • char-count
    Indicates any valid number of characters between 1 and 49.
    Default
    :
    10
The RIGHT command cannot be used on Mod5 terminals.
Shift Listing to the Left
To shift the listing to the left a specific number of characters, enter:
LEFT char-count
  • char-count
    Indicates any valid number of characters between 1 and 49.
    Default
    :
    10
The LEFT command cannot be used on Mod5 terminals.
Shift Listing Down
To shift the listing down a specific number of lines, enter:
DOWN line-count
  • line-count
    Indicates any valid number of lines between 1 and 9999.
    Default
    : 1
Shift Listing Up
To shift the listing up a specific number of lines, enter:
UP line-count
  • line-count
    Indicates any valid number of lines between 1 and 9999.
    Default
    : 1
Shift Listing to a Margin Position
To shift the listing to a specific margin position, enter:
MARGIN margin value
  • margin value
    Indicates any valid number of characters between 1 and 50.
The MARGIN command cannot be used on Mod5 terminals.
Position Listing to a Line Number
To position the listing to a specific line number, enter:
FS line-number
  • line-number
    Indicates any line number within an ASSEMBLER, COBOL, or PL/1 program.
Position Listing to a Label
To position the listing to a specific paragraph, procedure, or label, enter:
FP label
  • label
    Indicates any valid label within an ASSEMBLER, COBOL or PL/1 program including datanames, CSECT, procedure, and paragraph names.
Navigate to the Indirect Commands Build Screen
To navigate to the Indirect Commands build screen, enter
IC
.
Navigate to the Breakpoint Options Build Screen
To navigate to the Breakpoint Options build screen, enter
BPO
.
The BPO command does not require any parameters. However a corresponding U, ), R, or C must be placed in the left line command area of the statement requiring the breakpoint option.
Scroll Forward and Backward
PF7 and PF8 scroll the compiler output backward and forward, respectively. The default scroll amount is one page; however, you can change the scroll amount on the Source Listing Profile screen.
PF7 and PF8 do not apply to the Keep window, within which PF19 and PF20 perform the scroll forward and backward functions.
Change the Program
At any time during testing, CA InterTest for CICS lets you to change the program with which you are working.
Program=
To change the program displayed, follow these steps:
  1. Enter the desired program name in the Program= field.
  2. Press Enter to display the listing from the beginning of the program, or use the Option #, Statement #, or Search= fields to select another point of initial display before pressing Enter.
Position the Display
When you initiate the Source Listing Facility, you can easily name the program and position the display at any statement number with a single command:
LIST=progname,#nnnnn
  • progname
    Specifies the name of the program you want to view
  • #
    Required
  • nnnnn
    Indicates the statement number from 1 to 99999. If the requested statement number is greater than the number of statements in the listing, the greatest number is displayed.
Assembler Programs
When you initiate the Source Listing Facility you can position the Assembler display at a specific offset location in a CSECT. Use the command form:
LIST=progname,offset
  • progname
    Specifies the name of the program you want to view
  • offset
    Specifies a one to six hexadecimal number from 0 to FFFFFF
Example
To position the Source Listing display of program COBDEMO with statement 99 highlighted near the top of the display area enter:
LIST=COBDEMO,#99
Position the Source Listing display of program ASMDEMO with offset 0007E8 highlighted near the top of the display area enter:
LIST=ASMDEMO,7E8
Position the display area to include more data, source listing, or storage items using the Option #, Statement #, Margin=, and Search = fields of any Source Listing screen.
  • Option #
    To display a specific section, select an Option # from the OPTS.
  • Statement #
    To display a particular statement, enter the desired statement number from 1 to 9999 in the Statement # field, and press
    Enter
    .
  • Nested=
    To display a particular nested program, enter the program name in the Nested = field, and press
    Enter
    .
  • Search=
    To display the code defining a particular data item in Working-storage, Local-Storage, or the Linkage section, enter the data name in the Search = field, and press
    Enter
    .
    To display the code surrounding a particular paragraph or label, enter the paragraph name or label name in the Search = field, and press
    Enter.
  • Displacement=
    To display the listing at a specific displacement in an Assembler program, enter the displacement from 0 to FFFFFF in the Displacement= field.
Adjust the Margins
Because certain compiler output (particularly Assembler and CA Optimizer/II output) extends beyond 80 positions, it might be necessary to adjust the display margins to view more of your program's Source Listing.
Margin=
To adjust the output display to view portions of the listing to the right of position 80, perform the following steps:
  1. Enter the position number of the desired left margin in the Margin= field. Valid entries are 1 through 50.
  2. Press
    Enter
    . The screen displays the output beginning at the position specified, as shown in the following example.
Example
Assembler users often set the Margin= field to 28 as shown next.
CA InterTest for CICS - PROTDEM FILE SOURCE LISTING DISPLAY COMMAND ==> Program= ASMDEMO Option # Stmt # Displacement= Margin= 28 Search= OPTS 1 1st CSECT 2 3 4 5 6 Xref 7 Literals 8 Err msgs 9 Srch fwd 10 Srch bwd 11 12 Bkpt opts PFKS 1 Help 2 3 End 4 Profile 5 Monitor 6 Menu 7 Backward 8 Forward 9 Next Wnd 10 11 12 Status -----------+--------------------------------------------------------------- LOC STMT SOURCE STATEMENT 000000 463+ STM 14,12,12(13) SAVE CALLER'S REGISTERS 464+************************************************************* 465+* ESTABLISH CODE ADDRESSIBILITY 466+************************************************************* 467+ USING *4,2,3,4,7 000004 468+ LR 2,15 000006 469+ LR 3,2 000008 470+ AH 3,DFHEI4K 00000C 471+ LR 4,3 00000E 472+ AH 4, DFHEI4K 000012 473+ LR 7,4 000014 474+ AH 7,DHEI4K 475+************************************************************** 476+ OBTAIN DYNAMIC STORAGE
  • The statement or location numbers stay on the screen as the rest of the display shifts left or right. A plus sign (+) in the line above the display area indicates the column where shifting begins.
  • If there is no output beyond position 80, CA InterTest for CICS overrides a margin setting greater than 1 and redisplays positions 1 through 80.
Log a Monitoring Session
When you monitor a program, you can log, or record, the monitoring session and save it to PROTMLOG. You can then use this file to repeat your monitoring session later.
You can issue the following monitoring session commands from the listings facility command line. All monitoring session commands are applied to the user ID and terminal that issue the commands:
  • MLOG
    Displays the CA InterTest for CICS SAVED DEBUG SESSIONS screen (ITST 2.7).
  • MLOG START [
    name
    [
    description
    ]]
    Starts recording a new monitor session.
    • name
      (Optional) Specifies a name for the session. If you omit the name, the session is saved with the same name as the program.
      Limits:
      1 to 8 characters
    • description
      (Optional) Describes the session.
      Limits:
      1 to 35 characters
    When you issue the START command, the active recording session is indicated by a flashing REC on the Source Listing Display screen.
  • MLOG STOP
    Stops recording and saves the monitor session.
    When you issue the STOP command, the flashing REC disappears from the Source Listing Display screen.
  • MLOG CANCEL
    Cancels the current session and deletes all entries that were recorded since the START command was issued.
    When you issue the CANCEL command, the flashing REC disappears from the Source Listing Display screen.
  • MLOG LOAD [
    name
    ]
    Loads an existing session.
    • name
      (Optional) Specifies the session. If you omit the name, the session that has the same name as the program is loaded.
      Limits:
      1 to 8 characters
Customize the Source Listing Profile
CA InterTest for CICS was designed with the user in mind. The Source Listing Profile lets you set specific functions that help you meet your testing needs.
Access
To access the Profile, type
profile
on the command line and press
Enter
, or press
PF4
while viewing the Source Listing or Breakpoint screen. The Profile appears at the bottom of your screen.
It is not necessary to change the options in the Profile screen unless you want to change the default settings for your test session.
Info Area
The info area is located at the top of the Source Listing Display screen under the Search field. The info area displays various windows depending on the value in the Display window field in the Source Listing Profile.
To change the information displayed in the info area, change the value in the Display window field.
Follow these steps:
  1. On the Source Listing screen, either type
    profile
    in the command line and press
    Enter
    , or press
    PF4.
    The Profile screen appears.
  2. Specify the desired value in the Display window field, and press
    Enter
    .
    The info area displays the information that you requested.
  3. Alternatively, type 20-24 in the Option # field to display the required window. See Source Listing Option Field Entries.
    • Press PF9 to switch between the windows in order. PF9 does not switch between the windows when the Backtrace Facility is active.
The Display window field has the following values:
  • N (None)
    Disables the info area so that you are able to see more of the source code.
  • T (Titles)
    Displays the Title window in the info area. The Title window shows the title and header lines of your Source Listing Display, including the option and PF key descriptions.
    T
    is the default value for the Display window field unless changed during the product installation.
  • R (Registers)
    Displays the Register window in the info area. The Register window shows the registers and attributes of your program.
  • K (Keep)
    Displays the Keep window in the info area. The Keep window shows your program data items. If the AUTOKEEP option is ON, the window always switches to the Keep window whenever there are any data items to be displayed.
  • P (Program)
    Displays the Program window in the info area. The Program window enables you to specify the load module name and view the symbolic file information.
Register Window
The Register window allows you to display and modify the contents of registers, and view an area where a register points to.
The following screen shows the Register window:
CA InterTest for CICS - PROTSYM FILE ABEND DETECTED BREAKPOINT COMMAND ===> Program= COBDEMO Option # Stmt # Search= ------------------------------------------------------------------------------------ R0-R7 3520A424 35209220 00100100 3520B5C8 3520A540 350F79E0 350F7998 B5200108 R8-R15 3520A5C8 3520A2C0 3651B15C 3651B904 3651B11C 352090D0 B651C242 00000000 Cond. Code = 0 Amode = 31 ExecKey = USER TransIsolate = YES ------------------------------------------------------------------------------------ _ 000412 CONTINUE-TASK. 000413**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED A ==> ADD +1 TO TASKNUM. ...
The Register window contains the following fields:
  • R0-R7
  • R8-R15
    Displays the contents of registers at the current statement of the program.
  • Cond. Code
    Indicates the current condition code.
  • Amode
    Displays the current addressing mode of the program.
  • ExecKey
    Displays the ExecKey for the current program if the CICS Storage Protection Option is active, depending on the option specified in the program definition.
  • TransIsolate
    Displays the transaction isolation option of the current task if the CICS Transaction Isolation Option is active.
To modify the program registers, overtype the displayed contents with the desired value, and press
Enter
. To view the area pointed to by a register, overtype the first displayed character of the register with either an at sign (@) for a 24-bit address, or with a percent sign (%) for a 31-bit address, and press
Enter
.
Program Window
The Program window enables you to specify the name of a composite load module, and set breakpoints for subprograms that belong to that composite load module.
The following screen shows the Program window:
CA InterTest for CICS - PROTSYM FILE SOURCE LISTING DISPLAY COMMAND ===> Program= CSBIN25 Option # Stmt # Search= Load module= COBDEML Symbolic file: PROTSYM Timestamp: 2014-05-27 05:05 Language: IBMCOB 4.2 ---------+-------------------------------------------------------------------------- _ 000023 PROCEDURE DIVISION USING COMM-TEXT. _ 000024 MOVE ZERO TO DIVCT. ...
The Symbolic file, Timestamp and Language fields provide information about the subprogram specified in the Program field, not the load composite module in the Load module field.
Scroll Amount
The scroll amount determines how much more of your source listing displays each time you use PF7 or PF8.
To set the scroll amount for scrolling backward and forward (PF7 and PF8), perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    from a Source Listing screen to display the Profile screen.
  2. Overtype the current PF7/8 Amount=entry with one of the following:
    • PAGE
      The size (number of lines) of the display area on the Source Listing Display and Breakpoint screens.
    • HALF
      Half the size of the display area.
    • nnnn
      Any number of lines from 1 to 9999.
    • STOP
      Go to the next or previous breakpoint in the program.
  3. Press Enter. The change takes effect immediately, and you return to the Source Listing Display screen.
  • Setting the Scroll Amount to STOP is an excellent way to review all of the breakpoints set in your program
  • PF7 and PF8 do not apply to the Keep window, within which PF19 and PF20 perform the forward and backward functions
Step Timing
Step timing determines where the Step or Next command stops statement execution.
To set Step timing to After, type
After
and press
Enter
.
  • AFTER
    The program is stopped after the next verb, statement or instruction is executed.
  • BEFORE
    The program is stopped before the next verb, statement or instruction is executed. (Default)
Step Amount
The step amount determines how many COBOL verbs, Assembler instructions, or PL/I statements will be executed at a time when you use PF10 to single-step through your program.
Stepping Amount=
To set the step amount for PF10, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    to access the Profile screen from any Source Listing screen.
  2. Enter the desired number of COBOL verbs, Assembler instructions, or PL/I statements from 1 to 999 in the Stepping amount= field.
  3. Press
    Enter
    . When the Source Listing Breakpoint screen is redisplayed, the new step amount is reflected in the
    PF10
    (Single-step) definition, as shown in the following example.
Example
The Source Listing Breakpoint display in the following figure shows a PF10 step amount set to
004 Verbs
.
CA InterTest for CICS - PROTDEM FILE SOURCE LISTING BREAKPOINT Command ==> Program= COBDEMO Option # Stmt # Margin= 01 Search= OPTS 1 Proc div 2 Work-stor 3 Link sect 4 D-map 5 Clst/Pmap More: + 6 Data xref 7 Proc xref 8 Err msgs 9 Srch fwd 10 Srch bwd PFKS 1 Help 2 3 Det Bkpt 4 Profile 5 Resume 6 Menu 7 Backward 8 Forward 9 10 004 Verbs 11 Backtrace 12 Status ---------------------------------------------------------------------------- _ 00880 CONTINUETASK. 00881**** TASKNUM *NOTE* FIELD MUST BE INITIALIZED A ==> ADD +1 TO TASKNUM. ==> ==> ASRA abend (0C7) detected and prevented. Caused by invalid decimal ==> arithmetic data format. ==> ==> Press PF1 for a detailed description. ==> _ 00883 IF TASKNUM = 1 _ 00884 MOVE 'DMAPASR' TO MAPNAME. _ 00885 IF TASKNUM = 2 _ 00886 MOVE 'DMAPSUM' TO MAPNAME. _ 00887 IF TASKNUM GREATER 2 _ 00888 GO TO SENDENDMSG.
The step value of PF10 on the Source Listing Breakpoint screen does not apply to the PF10 definition on the Detailed Breakpoint screen.
Use the Stepping Amount parameter to enable the automatic tracing feature of the Source Listing Backtrace. When the Stepping Amount is set to any number greater than one, the new value becomes the number of statements CA InterTest for CICS traces on the Source Listing Backtrace. (PF9 traces backward; PF10 traces forward).
Turn on Automatic Single-Stepping
Automatic single-stepping lets you to go through your source listing a specified number of steps at specified time intervals.
Auto-stepping= ON
To access the Auto-stepping Parameters screen, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    from any Source Listing display. The Source Listing Profile is displayed.
  2. Specify Auto-stepping=
    ON
    .
  3. Press
    PF4
    to activate your specification. The auto-stepping parameters are displayed.
When Auto stepping= ON, the defaults are as follows:
  • Pause
    one second
    before repeating single-stepping or automatic tracing
  • Stop at the
    next CICS command or call
To change the automatic stepping amount, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    from the Profile screen to access the auto-stepping parameters.
  2. Specify the following options:
    • Wait amount
      Enter the number of seconds from 1 to 59 that CA InterTest for CICS should pause at each single-step breakpoint.
    • Stop value
      Enter a value that determines when automatic single-stepping should terminate, either at a CICS command or call, or after a specified number of steps are executed.
  3. Press Enter to process the new settings and return to the Profile screen.
  4. Press Enter
    again to return to the Source Listing display or breakpoint screen.
Breakpoint Display Mode
CA InterTest for CICS has two breakpoint displays:
  • The Source Listing Breakpoint version lets you to test directly from your source listing.
  • The Detailed Breakpoint display requires you to use one-line CA InterTest for CICS commands and other menus.
The initial display mode depends on the setting chosen when CA InterTest for CICS was installed; however, you can change the display mode at any time by using the Profile screen. This change remains in effect until the Source List BKPT= setting is changed.
Source List BKPT=
To change the breakpoint display mode, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    to display the Profile screen. The Source List BKPT= field shows the current setting.
  2. Overtype the current value with one of the following:
    • ON
      Displays the Source Listing Breakpoint.
    • OFF
      Displays the Detailed Breakpoint.
  3. Press Enter to process the new setting and to return to the Source Listing Display screen.
From and BKPT Terminal IDs
From Terminal ID=
From Terminal ID identifies where the program executes. The default for the From Terminal ID setting depends on your system's installation option value for DFLTUSER.
  • When DFLTUSER=.ANY is in effect, the default is the terminal displaying the source listing.
  • When DFLTUSER=SPECIFIC is in effect and you are signed on to CICS, the default is .ANY. This entry tells CA InterTest for CICS to monitor the program when it runs from .ANY terminal wherever you are signed on to CICS.
To change the default From Terminal ID, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    from the Source Listing display to access the Source Listing Profile screen.
  2. Overtype the entry in the From Terminal ID field to specify where the program will run. Valid entries are as follows:
    • terminal ID
      Runs from the specified terminal
    • *
      Runs from current terminal displaying this profile screen
    • .ANY
      Runs from any terminal or even without a terminal
    • .NO
      Monitors only when this program runs as a background transaction without a terminal.
      The BKPT terminal ID must be set to a specific 3270-type terminal that will receive the breakpoints. If From terminal ID is .N and the BKPT terminal ID is .NO or .ANY, the breakpointed task is abended with an INTE abend when the first breakpoint is encountered.
  3. Press Enter to process the new From Terminal ID setting and to return to the Source Listing Display.
BKPT Terminal ID=
From Terminal ID identifies the terminal where breakpoints display. The default for the BKPT Terminal ID depends on your system's installation option value for DFLTUSER. To view your system's installation options online, use ITST Option 7.1.2.
  • When DFLTUSER=.ANY is in effect, the default is the terminal that is displaying the source listing.
  • When DFLTUSER=SPECIFIC is in effect and you are signed on to CICS, the default is .ANY. This entry tells CA InterTest for CICS to send the breakpoints to any terminal where the user is signed on to CICS.
To change the default, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    from the Source Listing display to access the Source Listing Profile screen.
  2. Overtype the entry in the BKPT Terminal ID field to specify the terminal to receive the breakpoint displays. Valid entries are:
    • terminal ID
      Displays breakpoints at the specified terminal.
    • *
      Displays breakpoints at the terminal displaying this profile screen.
    • .ANY
      For transactions executing at a 3270-type terminal, the breakpoint displays on the executing terminal.
    • .NO
      If the transaction runs as a background task without a terminal, the transaction abends with an INTE abend when the first breakpoint is displayed.
      The breakpointed task abends with an INTE abend when the first breakpoint is displayed.
  3. Press Enter to process the new BKPT Terminal ID setting and to return to the Source Listing Display.
Set the User ID
CA InterTest for CICS monitoring is sensitive to user IDs. Monitor programs and set breakpoints and other monitoring options with the user ID set to .ANY, or the user ID set to a specific CICS user ID (in a secure CICS region). When the user ID is set to .ANY, everyone is monitored and the breakpoints and other monitoring options that you set take effect only if the program executes from the terminal used to set the breakpoints. When the user ID is set to a specific user ID, only that user is monitored, and the breakpoints and other monitoring options are directed to wherever the specified user is logged onto CICS.
User ID=
The default is either the current CICS user, or .ANY. To change the default, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    from the Source Listing display, to access the Source Listing Profile screen.
  2. Overtype the entry in the User ID field to specify the CICS user who must execute the program for monitoring and breakpoints to take effect. Valid entries are:
    • specific user-ID
      Monitoring and breakpoints take effect only when the specific CICS user executes the program.This establishes a personal debugging session for the CICS user and directs breakpoints to the terminal on which the user is signed on.
    • .ANY
      Monitoring and breakpoints take effect when anyone executes the program.
  3. Press Enter to process the new user ID setting and to return to the Source Listing Display.
If you override the default user ID setting, check the Profile before each Source Listing Session and before you set additional breakpoints during a test session.
Set the Keep Window to Display Variables in Current Statement
AUTOKEEP lets you display items in the Keep window concerning the currently highlighted statement.
The initial setting for AUTOKEEP is chosen when CA InterTest for CICS is installed. If the IN25OPTS parameter SLBAKEEP is set to yes, which is the default, AUTOKEEP will be active. However, use the Profile screen to turn AUTOKEEP off or on again at any time.
AutoKeep Display=
To change the setting for AUTOKEEP, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    to access the Profile screen from any Source Listing Screen. The AutoKeep Display = field shows the current setting.
  2. Overtype the current value with one of the following:
    • YES
      Displays in the Keep window, the variables being manipulated in the current statement, along with any data items you requested.
    • NO
      Displays in the Keep window only the data items you requested.
  3. Press Enter to process the new setting and to return to the Source Listing Display screen.
Set Code Coverage
Code Coverage (Counts) lets you see the number of times a verb was executed.
The initial setting for Code Counting is off, which is the default. However, use the Profile screen to turn Code Coverage off or on again at any time.
How the counts are displayed or not displayed is handled by the primary line command COUNTS with its associated parameters.
This feature, due to its nature, causes overhead during monitoring and should be turned off as soon as it is no longer needed.
Code Counting=
To change the setting for Code Coverage, perform the following steps:
  1. Type
    profile
    on the command line and press Enter, or press
    PF4
    to access the Profile screen from any Source Listing Screen. The Code Counting= field shows the current setting.
  2. Overtype the current value with one of the following:
    • YES
      Enables code counting and turns on the COUNTER display feature.
    • NO
      Removes the COUNTER display and stops the counting feature.
  3. Press Enter to process the new setting and to return to the Source Listing Display screen.
Set Structure Display Form
SDF defaults to the value set in the IN25OPTS macro, a value of HEX displays structured data in dump format and a value of DATA displays structured data in display format.
To change the current structure display format type
profile
on the command line and press Enter, or press
PF4
to access the Profile screen from the Source Listing Screen. The SDF = field shows the current setting.
Testing Activities
This section discusses testing activities for monitoring users.
Set Monitoring
A CICS user ID is assigned to all monitoring requests. Depending on how CA InterTest for CICS was installed at your site, the default may be to set monitoring for
.ANY
user, or to set monitoring for a specific CICS user. The following topics discuss how these settings affect your test session.
As long as you are working in a secure CICS region, you can override the default user ID setting using the Profile display. You should check how the user ID is set prior to setting breakpoints or monitoring for a program.
Monitor with User ID=.ANY
Setting monitoring with a user ID of
.ANY
is the same as monitoring in earlier CICS releases: the program is monitored when ANY user executes the program, and breakpoints are displayed by default on the same terminal where they were set.
Monitor with a Specific User ID
When you set monitoring for a program with a specific user ID, CA InterTest for CICS only monitors the program when it is executed by that user. In addition, breakpoints display at whatever terminal that user is signed on to. Of course, this option requires a secure CICS region and the user to be signed on to CICS when testing the program.
Monitoring with your specific user ID has the following advantages over monitoring with user ID=.ANY:
  • You can change terminals and your breakpoints and monitoring options will follow you
  • Your testing will not interfere with any one else testing the same program
  • You can use a multi-session terminal emulator package and have breakpoints directed to whatever terminal session you are using
View and Set the User ID
To view or set the user ID that will be used for monitoring and breakpoints, access the Source Listing Profile. To access the Profile, either enter
PROFILE
on the command line and press Enter, or press
PF4
. The User ID field is at the bottom of the Profile. To change its value, delete the current entry, type in the new entry, and press
Enter
.
Also check the Terminal ID field just above the User ID field. Generally, you want Terminal ID set to .ANY when User ID is
specific
, and Terminal ID set to a specific terminal ID when User ID is .ANY.
Set Monitoring for a Displayed Program
To set monitoring for the program you are viewing, enter
MONITOR
in the command line, or press
PF5.
CA InterTest for CICS processes the request immediately using the user ID value currently set in the Source Listing Profile.
If you are going to set any breakpoints, skip this step; setting a breakpoint automatically sets monitoring for the program.
Monitoring Multiple Programs
If you plan to test more than one program, you need to set monitoring and breakpoints for each program. If a program to be tested passes control to another program using XCTL or LINK, you also must set monitoring for the receiving program.
To display another program, overtype the program name in the Program= field. Specify where you want to begin the program's display by using the Option #, Stmt #, and Search = or Assembler Displacement fields. Press Enter to process your request. For details, Change the Program and Position the Display.
With the new program displayed, repeat the steps to set monitoring and breakpoints.
Display and Search Through Nested Programs
CA InterTest for CICS provides support for COBOL nested programs.
COBOL nested programs let non-unique paragraph and data names to be defined across nested programs. Therefore, CA InterTest for CICS supports qualified
names for COBOL programs. A qualified name consists of a one- to 30-byte COBOL program name, a colon, and a one- to 30-byte paragraph or data name.
Example
program1:datanam1 is a qualified name. Qualified names ensure that the correct version of datanam1, which you define in multiple programs, is displayed. Qualified names are supported by the Source Listing facility, the Breakpoint facility, CNTL commands and menus, and by the Indirect Commands facility.
When CA InterTest for CICS displays the source code for a nested program, the Nested= field appears below the Program=
field. The Nested= field is 30 bytes long, and indicates the name of the nested program for the currently displayed source code. If you are using the Source Listing facility to display a COBOL nested program and you press PF8 to scroll through the entire source code of the program, the Nested= field changes each time the source code for a different nested program is displayed.
The names of all nested programs within a specific COBOL program are listed at the end of the Procedure Name Cross Reference section (Option
# 7).
CA InterTest for CICS - PROTDEM FILE SOURCE LISTING DISPLAY COMMAND ===> Program= ACME2000 Option # Stmt # Margin= 01 Nested= Search= OPTS 1 Proc div 2 Work-stor 3 Link sect 4 D-map 5 Clst/Pmap More: + 6 Data xref 7 Proc xref 8 Err msgs 9 Srch fwd 10 Srch bwd PFKS 1 Help 2 3 End 4 Profile 5 Monitor 6 Menu 7 Backward 8 Forward 9 Next Wnd 10 11 12 Status ---------+------------------------------------------------------------------ _ DEFINED PROCEDURE NAMES REFERENCES _ 122 3000REGISTERHANDLER P107 _ 131 4000FORCEABEND P108 _ 139 5000HANDLEROUTINE D129 _ 152 9000RETURN P109 _ 168 9999GOBACK _ 227 9999GOBACK P221 DEFINED CROSSREFERENCE OF PROGRAMS REFERENCES EXTERNAL ACME200A . . . . . . . . . . . 120 171 ACME200N . . . . . . . . . . . 229 114 2 ACME2000 . . . . . . . . . . . 230 EXTERNAL ACME2001 . . . . . . . . . . . 117 EXTERNAL DFHEI1 . . . . . . . . . . . . 127 137 147 160 166 NESTED PROGRAM MAP PROGRAM ATTRIBUTE CODES (RIGHTMOST COLUMN) HAVE THE FOLLOWING MEANINGS:
The Nested= field also indicates the nested program to which Option # 1, 2, 3, and 13 apply, and the nested program that CA InterTest for CICS searches first for any data name or paragraph name that you specify in the Search= field. If a paragraph name or data name is not found in the specified nested program, CA InterTest for CICS then searches the main program.
Example
If Option # 2 and Nested=program2 are specified, the Working Storage section for nested program program2 appears. Also, if Nested=program3 and Search=datanam1are specified, nested program program3 is searched first for datanam1; if datanam1 is
not
found, the main program is searched for datanam1.
Maintain Synchronized Processing
When CA InterTest for CICS searches the symbolic files for the COBOL and PL/I programs that you specify, it tries to match the date and time in the symbolic file to that of the load module. If a match is not found, either a Symbolic Version List or a warning message displays.
When CA InterTest for CICS searches the symbolic files for the Assembler programs you specified, the Symbolic Version List displays if multiple symbolic versions of a program are found.
COBOL and PL/I Symbolic Version Processing
When you use LIST=
program
, ITST, or CNTL to request a COBOL or PL/I program that has no previously declared breakpoints or monitoring options set, CA InterTest for CICS matches the date and time of the
most recently compiled
version of the program from the symbolic files to the load module date and time.
  • If an exact match is found and there are no later versions, CA InterTest for CICS automatically selects that version of the listing and displays it.
  • If a match is not found, CA InterTest for CICS displays the Symbolic Version List from which you can either:
    • Select the appropriate symbolic file and program version
    • Ignore symbolic processing for the program
    • The Symbolic Version List screen might also explain the cause of the mismatch. The following are possible causes for the mismatch:
    • There was no matching program listing for the load module.
    • A matching listing was found for the load module, but it is not the most recently compiled version. You can select the matching listing at this point or new copy the load module so that it matches the most recently compiled version and then retry the LIST or CNTL command.
During Automatic Breakpoint processing, if a program has no previously selected symbolic file, CA InterTest for CICS will attempt to match the load module's date and time to a symbolic file program listing.
  • If an exact match is found, CA InterTest for CICS automatically selects and displays it.
  • If a match is not found, CA InterTest for CICS displays the Symbolic Version List from which you can choose a non-matching program listing version or ignore symbolic processing for the program.
Once a symbolic file is selected for a program, CA InterTest for CICS continues to use the selected file and program version. If a new version of the program is compiled and linked and you have one or more breakpoints set by Statement # or Offset, then you should deactivate monitoring for the program, new copy the program , and then reset any
Statement #
or
Offset
breakpoints. This will insure that your breakpoints are in sync with the new program version. Alternatively, if you do not have any breakpoints set or only breakpoints set by paragraph-name, you can execute a CNTL=NEW,PROG= command or ITST Option 2.1 NEWCOPY, which will reset monitoring for the new program version.
For PL/I Programs
Successful date and time matching for PL/I modules requires that PL/I programs be compiled using the default TSTAMP=YES option.
Assembler Symbolic Version Processing
Assembler programs have no internal date and time generated by the compiler, which prevents date and time matching. However, when LIST=
program
or CNTL=ON,PROG=
program
is requested for an Assembler program with multiple symbolic versions of the listing and no previously declared breakpoints or monitoring options, CA InterTest for CICS displays a Symbolic Version List from which you select the appropriate symbolic file and listing version or ignore symbolic processing for the program.
Once a symbolic file and program version is selected for an Assembler program, CA InterTest for CICS continues to use the selected file and program version. If a new version of the program is compiled and linked and you have one or more breakpoints set by
Statement #
or
Offset
, then you should deactivate monitoring for the program, new copy the program , and then reset any Statement # or Offset breakpoints. This will insure that your breakpoints are in sync with the new program version. Alternatively, if you do not have any breakpoints set or only breakpoints set by paragraph-name, you can execute a CNTL=NEW,PROG= command or ITST Option 2.1 NEWCOPY, which will reset monitoring for the new program version.
The Symbolic Version List
The Symbolic Version List lets you select the appropriate symbolic file or exit CA InterTest for CICS and find out why a date and time mismatch occurred.
  • To select a symbolic File ID, place an
    S
    next to the File ID.
  • To exit CA InterTest for CICS without viewing any symbolic file, press
    PF3
    .
  • To see why a mismatch occurred, consult the Comment column.
The following screen shows a sample Symbolic Version List that appears when the LIST or CNTL transactions cannot determine which symbolic file to use.
CA InterTest for CICS - Symbolic Version List Program = COBDEMO Load Module Date and time = 07/07/94 9.44.13 Loadlib = COBDEMO.loadlib Volume = volser File ID Date Time Language Comments _ PROTDEM 07/24/94 11.44.13 COBOL Latest Version _ PROTTST 07/24/94 10.59.00 COBOL Update Mode _ PROTACC 07/23/94 12.52.00 COBOL _ PROTPRO 07/23/94 10.01.00 COBOL S Select which Symbolic file to use for program display ----------------------------------------------------------------------- ’ PFKEYS: 1 Help 2 3 No File 4 5 6 7 8 9 10 11 12 “CAIN8000 The latest Symbolic version does not match the current load module
This screen shows the following information:
  • Specifies the name of the program being processed.
  • Displays the internal date and time from the COBOL or PL/I load module. This field is
    not
    displayed for Assembler programs or for PL/I programs compiled with a compiler that was installed with the TSTAMP=NO installation option.
  • Displays the names of each version of the symbolic file containing a copy of the specified program.
  • Lists dates and times that each version of the symbolic file was compiled.
  • Displays the language of the compiled program.
  • Displays information about the version listed in the File ID column, and also explains the reason for the date and time mismatch. Comments include:
    • Update Mode
      Specifies the program is being updated by the batch post-compiler utility. It could also mean that the PROTSYM ran out of space while a post-compiler was processing this program.
    • Date and time Match
      Specifies the program compile date and time matches the load module date and time, but it is not the most recently compiled version of the program.
    • Latest Version
      Specifies the program compile date and time is the most recently compiled version of the program, but it does not match the load module date and time.
  • Lists the PF keys available from this screen.
    • PF1
      Accesses the Help facility.
    • PF3
      Exit the Symbolic Version List and ignore symbolic processing.
Set Breakpoints
A breakpoint halts execution of your program. CA InterTest for CICS halts the program before the instruction at a breakpoint location is executed.
The following table shows the types of breakpoints that you can set in a program:
Breakpoint
Action
Unconditional
Stops at a specified program location.
Conditional
Stops at a specified program location when a specified condition is met.
Variable-change
Stops when the value of a specified variable changes; for
COBOL and Assembler only.
Request
Stops at a CICS command or at calls to software.
Set breakpoints from the Source Listing Display prior to program execution, from any breakpoint during program execution, or from the Monitoring menus at any time.
Remove Breakpoints
Remove user breakpoints as quickly as they were set. In addition to the previously supported methods of removing breakpoints, use the Monitoring Status display to quickly remove any type of breakpoint.
Remove automatic breakpoints only if the error is corrected. However, you can go around the error and begin execution from another point.
Statement Tracing
Statement tracing causes CA InterTest for CICS to add entries to the statement trace table for each executed statement. Then view the executed statements at any breakpoint by stepping backward and forward through the trace table entries using the PREV and ADVANCE commands. Statement tracing is only valid for COBOL programs and is unrelated to the backtrace facility.
Set statement tracing from the Source Listing Display prior to program execution, from any breakpoint during program execution, or from the Monitoring menus at any time. Remove statement tracing using one of those methods. In addition, use the Monitoring Status display to quickly remove statement tracing.
Data Monitoring
Data monitoring causes CA InterTest for CICS to capture data values for each statement executed in a program. The captured data values are associated with an entry in the statement trace table. Redisplay them at any breakpoint by stepping backward and forward through the trace table entries using the PREV and ADVANCE commands. Data monitoring requires that statement tracing be active and is only valid for COBOL programs.
Set or remove data monitoring from the Source Listing Display prior to program execution, from any breakpoint during program execution, or from the Monitoring menus at any time.
Run Your Program
After setting monitoring and breakpoints for each program you want to test, you are ready to begin testing. To begin testing, perform the following steps:
  1. Exit the Source Listing facility by pressing
    PF3
    or
    Clear
    . If you accessed a CA InterTest for CICS screen outside the Source Listing facility, you might have to press
    Clear
    more than once to return to CICS. CA InterTest for CICS responds with the message:
    Lister Function Terminated.
  2. Initiate the program as you normally would from CICS. Depending on the breakpoints you set and the processing paths your program takes, one of the following occurs:
    • CA InterTest for CICS stops the transaction at a breakpoint (either one you set or one CA InterTest for CICS automatically triggered) because the program was about to violate a CICS coding standard.
    • The application runs to completion without being stopped by CA InterTest for CICS. The results might not be correct.
If the program ends and you get incorrect results or need to test other logic paths, initiate LIST again and set additional breakpoints before retesting the program. You do not have to reset monitoring -- it remains in effect until specifically removed.
Exit the Source Listing Facility
Type
END
on the command line and press Enter to exit the Source Listing Facility or exit the menus using
=X
.