id stringlengths 14 14 | text stringlengths 3 7k | source stringclasses 1
value |
|---|---|---|
a6632dde0712-1 | Limit total number of CICS requests (MXR)
Limits the number of requests a transaction issues. This option is useful when a program is in a loop that includes
a CICS request.
Setting for Structure Display Format (SDF)
Use this option to override, by program, the global default setting. Specify the following:
HEX
Display... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ab5fae51327d-0 | InterTest™ and SymDump ® 11.0
Limit monitoring (TON)
Specifies that the program be monitored and that the special options, if specified, take effect only when the
program executes at the current terminal (*), at a specific terminal (termid), or without a terminal (.NO).
User ID (or .ANY) who will execute the program (U... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ab5fae51327d-1 | Monitoring Menu Option 5 Active-Tasks, lets you reconnect, disconnect, and purge active tasks. From CICS, enter ITST
2.5 and the Active Tasks menu displays.
Type an R next to a task you want to reconnect to your terminal, or type a P next to a task you want to purge.
NOTE
For more information, see Special Consideration... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b3bca8e03775-0 | InterTest™ and SymDump ® 11.0
ABP Option: Automatic breakpointing sets the Automatic Breakpoint Facility for the entire system. Default. Breakpoint
displays are routed to the terminal where the program is running. Specify a terminal ID to indicate where breakpoint
displays should be routed for non-terminal attached ta... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b3bca8e03775-1 | above each column header. Use the command area to the left of each record to browse, cancel, delete, load, or stop the
recording session. If a debug session is currently active, the menu display shows the date as "*ACTIVE" and the time as
"------".
You can use the following line commands in the action field:
B
Browse t... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a42ef8968aea-0 | InterTest™ and SymDump ® 11.0
_ BROWETST CICSUSER U11IC9N4 2016239 150803
_ COBDEMO CICSUSER U11IC9N4 2016218 105545
_ DATANEW CICSUSER U11IC9N4 2016274 082857 ANOTHER DATAPGM SESSION TEST
_ DATAPGM CICSUSER U11IC9N4 2016195 152741
_ LOADACTV CICSUSER U11IC9N4 2016288 143051
_ MSGTEST CICSUSER U11IC9N4 201630... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a42ef8968aea-1 | SORT Session D
Special Monitoring Situations
Special Monitoring Situations
This article describes the following special monitoring situations:
•Monitoring programs with LE/370 condition handlers
•Monitoring dynamically called COBOL II and COBOL/370 programs
•Production environment monitoring
•Monitoring tasks that exec... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ac83b8f37350-0 | InterTest™ and SymDump ® 11.0
Monitor Programs with LE/370 Condition Handlers
LE/370 condition handlers do not receive control in the same manner as a normal CICS COBOL program. Therefore, they
must be monitored using the InterTest Segmented Monitoring and ABI=OFF options.
To monitor COBOL/370 programs containing calls... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ac83b8f37350-1 | The monitoring and debugging of dynamically called COBOL programs is handled as follows:
•In the same way as other CICS COBOL programs without necessarily monitoring higher level programs
•Using the FOL=PPT option
Request monitoring for dynamically called COBOL programs through the Source Listing and CNTL facilities th... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
412d55d39e28-0 | InterTest™ and SymDump ® 11.0
Abend the Task
If you want InterTest to abend the task before it damages CICS and writes a transaction dump (INTE), deactivate the
global automatic breakpoint facility. This facility instructs InterTest for CICS to generate a breakpoint each time it detects
an error in a program that it is... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
412d55d39e28-1 | option, select Special Options from the Monitoring submenus (2.1, 2.2, or 2.3) and specify the programs, transactions, or
terminals. On the Special Options menu, specify the number of times monitoring should occur in the MUS field. You can
also enter this command:
CNTL=ON,promid,MUS=nnn
Monitor a Program for a Singl... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
6ae22010ffd0-0 | InterTest™ and SymDump ® 11.0
Monitor a Program at a Single Terminal
When a program fails in the production system, use InterTest for CICS to monitor it to find and correct the error.
Restricting monitoring to a single terminal means you test the program thoroughly without interfering with the work of other
users.
If ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
6ae22010ffd0-1 | program at an automatic breakpoint and automatically creates a Monitoring Table entry for that program. The monitoring
status report provides that information. As soon as you see that InterTest for CICS has identified the problem program,
turn monitoring off for the system and monitor the problem program for a single u... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8e0f4cf9ad72-0 | InterTest™ and SymDump ® 11.0
Specify the ID of the terminal to receive breakpoint displays. If omitted, it defaults to the terminal at which the breakpoint
was set. Do not specify .ANY for the terminal to receive breakpoint displays.
NOTE
If you set a breakpoint, the local automatic breakpoint option is automatically ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8e0f4cf9ad72-1 | Set Monitoring for Non-Terminal Execution
Monitor a task only when it executes without a terminal. Specify this by selecting Replacement Options, Protection
Options, or Special Options from the Monitoring submenus, and then specify .NO in the Limit Monitoring field. For more
information, see Monitoring Menu Options. Yo... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
94b3b8f64a86-0 | InterTest™ and SymDump ® 11.0
If InterTest for CICS was installed with the DFLTUSER value in IN25OPTS set to SPECIFIC, Terminal ID =.ANY is the
default terminal setting. When the DFLTUSER option is set to .ANY, the default terminal ID is the terminal used to set the
breakpoint. To view your IN25OPTS settings, use Prima... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
94b3b8f64a86-1 | Place a MON option to start InterTest for CICS monitoring at the beginning of your application program's
Procedure Division. Monitoring begins at the MON location and continues until an activity #1 PEM call is
encountered. The InterTest for CICS IN25UEX routine for HOGAN applications detects this call and stops the
mon... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
e244fccf1733-0 | InterTest™ and SymDump ® 11.0
NOTE
For MSA programs set the MON after the secondary entry point.
The Segmented Monitoring Options Monitor (MON) and No Monitor (NOM)
Segmented monitoring consists of two independent monitoring options:
•MON, an option to turn monitoring on
•NOM, an option to turn monitoring off (No Monit... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
e244fccf1733-1 | the same location as a breakpoint or other option, the MON or NOM option executes first. This means the MON option
starts monitoring and hits the breakpoint, but since NOM drops monitoring before the breakpoint is encountered, you
never receive the breakpoint that is set where a NOM is also set.
Installation Requirem... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
c1b42b8972e5-0 | InterTest™ and SymDump ® 11.0
NO
Segmented monitoring is disabled.
The MONOMSEC keyword option tells you if a password is required. If MONOMSEC=YES, you need the password to set
MON or NOM using any method.
NOTE
InterTest for CICS releases prior to 5.1 do not support segmented monitoring.
Methods for Setting and Removi... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
c1b42b8972e5-1 | 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
_ 01057 MOVE ALL '*' TO TASKTEXT OF TASKSTRUCTURE2.
_ 01... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
56632e03b589-0 | InterTest™ and SymDump ® 11.0
_ 01070 GO TO SENDMAP00.
_ 1071 SETVARREC.
Set breakpoints within the execution path of the MON and the NOM locations in the program by using the + and - line
commands. The + line command activates or starts segmented monitori... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
56632e03b589-1 | Monitoring Off).
Notes:
•If Options 14 and 15 do not display on the Function Selection menu, menu support for segmented monitoring is not
available to you.
•If segmented monitoring is password protected, you are prompted to enter the password.
•Specifying NOM options with the menus is tricky because of double negatives... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b4c8bb1e1488-0 | InterTest™ and SymDump ® 11.0
CA InterTest MONITORING COMMAND BUILDER SEGMENTED MONITORING LOCATIONS 14
SET `monitor on' option for PROG=COBDEMO in any of the following fields:
(For qualification by nested program name, specify 'Programid:Label')
→ Paragraph A-TEST_______________________ _... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b4c8bb1e1488-1 | user ID (or .ANY) used to set the options.
The following screen is used to remove the monitor on locations that were previously set in the program for user ID
CARAR01.
CA InterTest MONITORING COMMAND BUILDER SEGMENTED MONITORING LOCATIONS 14
Remove `monitor on' option for PROG=COBDEMO in any of the foll... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3e6044170623-0 | InterTest™ and SymDump ® 11.0
After specifying the locations, press Enter .
CNTL Function 15S Set Monitor Off Screen
The following screen is used to set locations for no monitoring in COBOL programs; it specifies two locations:
•Specifies the first executable statement in paragraph A-TEST-EXIT.
•Indicates statement num... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3e6044170623-1 | After specifying the locations, press Enter .
CNTL Function 15R Remove Monitor Off Screen
Specify individual locations to be removed exactly as you set them, or by the ID number shown on the InterTest for CICS
status display. To quickly remove all locations at once, enter .ALL in the first field on the menu and the sa... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
aefe815151a7-0 | InterTest™ and SymDump ® 11.0
CNTL=ON,PROG=progname,MON=locn
CNTL=ON,PROG=progname,MON=(locn1,locn2, ...,locn9)
progname
Indicates one program.
locn
Specifies an address (from six- to eight-hexadecimal digits), offset (from one- to five-hexadecimal digits),
statement number (a decimal number preceded by #), COBOL p... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
aefe815151a7-1 | CNTL=INQ or, at breakpoint, by pressing PF3).
locn
Specifies an address (from - to eight-hexadecimal digits), offset (from one to five hexadecimal digits), statement
number (a decimal number preceded by #), COBOL paragraph name, Assembler or PL/I label (enclosed in
apostrophes).
To specify a location, use the same form... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ecec9b8aa66d-0 | InterTest™ and SymDump ® 11.0
NOTE
The command CNTL=OFF,PROG=progname does not remove the MON or NOM entries for a program. To
remove the MON and NOM options, you must explicitly specify them.
Examples
The following are command examples of specifying MON and NOM options.
To selectively monitor the program COBPROGA fro... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ecec9b8aa66d-1 | NOTE
Any non-sequential passing of control (such as PERFORM, GO TO, and so on), executed between the MON
location at A-TEST and the NOM location at
A-TEST-EXIT could result in InterTest for CICS monitoring outside the designated range.
Notes and Warnings
The following information contains notes and warning that you sho... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
eadf4a1d621e-0 | InterTest™ and SymDump ® 11.0
•Regardless of how they are set (Source Listing, Menu, or single-line command); each of these options must be placed
on the first byte (the op-code) of a machine instruction that resides in non-store-protected virtual storage. Because the
code must not be store-protected, the application p... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
eadf4a1d621e-1 | affected program. The CEMT SET PROG (xxxxxxxx) NEWCOPY must not be performed until all MON and NOM
options have been removed.
•RELOAD=YES cannot be used for a Program Definition if the program will be debugged using MON or NOB options.
•You cannot use the CICS installation parameter 'RENTPGM=PROTECT' if you plan on usi... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
eadf4a1d621e-2 | automatically shows, in dump format, up to three data areas named in the CALL statement parameters. There is no need
to enter CORE commands to display these areas. However, if there are more than three data areas, use the command
CORE=ARGnn to display them.
If you are using the Source Listing Breakpoint facility, Inter... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
f927887ce64f-0 | InterTest™ and SymDump ® 11.0
The programmed breakpoint will not occur unless the automatic breakpoint facility is active. If this facility is not active,
the programmed breakpoint CALL has no effect on program execution. The programmed breakpoint also does not affect
program execution if the program is not monitored ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
f927887ce64f-1 | DC C'PBPINTERTEST'
END PBP
Declare a Programmed Breakpoint in a PL/I Program
A PL/I program with a programmed breakpoint must be coded to define the entry point as passing parameters in
Assembler fashion, as shown next:
DCL PBP ENTRY OPTIONS(ASSEMBLER);
Once this is done, code the calls in the usual manner... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
4f42fd8ab0c8-0 | InterTest™ and SymDump ® 11.0
Declare a Programmed Breakpoint in a COBOL Program
The CALL statement that sets up a programmed breakpoint in a COBOL program is coded in the standard manner as
follows:
WRITE-RESPONSE.
MOVE ERROR-CODE TO RESPONSE.
CALL 'PBP' USING RESPONSE.
At this programmed breakpoint, the brea... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
4f42fd8ab0c8-1 | performance.
Monitoring CICS/FEPI Applications
The Front-End Programming Interface (FEPI) provides terminal emulation using virtual terminals defined to a CICS region.
These virtual terminals, called nodes, communicate with back-end processes that run either in the same CICS region or
in a remote region. Front-end proc... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
eba450a193f7-0 | InterTest™ and SymDump ® 11.0
To set breakpoints for a back-end process running in a local region, specify both the terminal at which the process is
running and the terminal to receive breakpoints, as follows:
•Term ID where breakpoints take effect: (F=)
The virtual terminal assigned by CICS. Specify either an actual v... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
eba450a193f7-1 | If the back-end process is running in a remote CICS region, perform these steps:
1.Set monitoring and breakpoints for the front-end process in the local region.
2.Set monitoring and breakpoints for the back-end process in the remote region from any real terminal.
TIMEOUT Values
If a TIMEOUT(seconds) parameter is spec... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
94f8511b35ed-0 | InterTest™ and SymDump ® 11.0
•The ability to set breakpoints anywhere in the program (not just at EXEC CICS commands).
•Data display/modification by symbolic names. This means the programmer does not need the most recent listing of the
tested program, as long as the data names or paragraph names (labels in Assembler) ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
94f8511b35ed-1 | •If an InterTest for CICS breakpoint is set at an EXEC CICS command, the InterTest for CICS breakpoint occurs before
the command is passed to CICS.
•At the breakpoint, the programmer reviews and changes any parameters of the command before telling InterTest for
CICS to continue with the task.
•InterTest for CICS checks... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a02306457593-0 | InterTest™ and SymDump ® 11.0
Breakpoints
Set and remove unconditional or conditional breakpoints.
Set and remove request breakpoints prior to CICS commands, calls to DL/I or DB/2, and calls to database software.
Monitoring Options
With the InterTest for CICS CNTL feature, you can:
•Set and remove statement tracing opt... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
a02306457593-1 | •ITST menus and fill-in screens
•CNTL menus and fill-in screens
•CNTL commands
With the CNTL facility use one method exclusively or use the mix-and-match method -- even during one test session,
depending on your specific testing needs.
Example
Use the source listing facility to initiate monitoring and set breakpoints, ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
7a460b8e2454-0 | InterTest™ and SymDump ® 11.0
breakpoint by entering a single keystroke directly on your program's source listing. For more information about this facility
and what to do when your program halts at a breakpoint, see Source Listing Facility for InterTest.
To take advantage of the full range of InterTest for CICS monitor... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
7a460b8e2454-1 | Set and remove unconditional breakpoints.
Setting and Removing Conditional Breakpoints
Set and remove conditional breakpoints.
Setting and Removing Request Breakpoints
Set and remove request breakpoints before CICS commands, calls to DL/I, DB2, and SQL/DS, and calls to
database software.
Setting and Removing Statement ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8232127a1aef-0 | InterTest™ and SymDump ® 11.0
System-Wide Options
Request monitoring options on a system-wide basis.
Resume Task Execution
Resume execution of a task stopped at a breakpoint.
Access the Monitoring Command Builder Main Menu
To display the Monitoring Command Builder main menu (the Function Selection Menu), enter CNTL on... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8232127a1aef-1 | names, or a user ID value.
NOTE
If a program is stopped at a breakpoint and you type CNTL in the command line to access the Function
Selection Menu, InterTest for CICS displays the name of the monitored entry (program, transaction, or terminal)
on this screen.
When you have entered all the necessary information, press... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
39e1f3db8be1-0 | InterTest™ and SymDump ® 11.0
•An asterisk specifies any number of characters, including no characters. Specify more than one asterisk in a program
name, transaction code, or terminal name. Do not, however, specify an asterisk by itself.
•A plus sign specifies just one character in a particular position. Specify more t... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
39e1f3db8be1-1 | as part of that transaction. When ABC1 executes, the options specified for ABC1 override the options specified for TRN1.
Similarly, it is important to understand the priorities InterTest for CICS observes when a program, transaction, or terminal
is specifically and generically declared for monitoring. A specific entry ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
f7c0cafea544-0 | InterTest™ and SymDump ® 11.0
PF Keys
Exit from the Function Selection Menu by pressing a PF key. Most of these PF keys are also in effect on other Monitoring
Command Builder screens. The following bullets describe the function of each PF key.
PF1 or 13
Initiates the InterTest for CICS online help facility.
PF2 or 14
U... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
f7c0cafea544-1 | Transaction
InterTest for CICS monitors all of the transaction's programs.
Terminal
InterTest for CICS monitors every program that executes at that terminal.
NOTE
InterTest for CICS will not monitor programs that begin with the prefix DFH (IBM CICS programs) or IN25
(InterTest for CICS programs).
1090 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
881c8e63f522-0 | InterTest™ and SymDump ® 11.0
If you set monitoring for a transaction or terminal, and a program executing as part of that transaction or at that terminal
is stopped at an automatic breakpoint, InterTest for CICS automatically creates an individual entry in the monitoring
table for that program. This lets you set break... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
881c8e63f522-1 | Set Unconditional Breakpoints
Use the Breakpoint Locations screen to set unconditional breakpoints.
To set breakpoints, enter the following information:
Specify up to nine breakpoint locations in fields.
COBOL
For COBOL program, specify a paragraph name or data name, a statement number, or the hexadecimal displacement
... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
1f7b709ca2c4-0 | InterTest™ and SymDump ® 11.0
•If you specify statement #1, InterTest for CICS sets a breakpoint at the first executable instruction in a COBOL
Procedure Division, Assembler CSECT, or PL/I procedure.
•COBOL statements can contain more than one verb. In specifying statement numbers, indicate the verb at which
the breakp... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
1f7b709ca2c4-1 | terminal. Enter .ANY to have breakpoint screens displayed at the terminal where the program is executing when
breakpoints occur.
•Specify the statement number of the indirect command that you want to invoke at the breakpoint you have set.
•Specify the user ID who must be executing the program for the breakpoint to take... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
eca531978af6-0 | InterTest™ and SymDump ® 11.0
•Paragraph RETURN-TRANSID
•Statement 1 (the beginning of the Procedure Division)
•First verb in statement 136
•Third verb in statement 174
Because the user ID field specifies a single user and the terminal ID fields are left blank, the breakpoints take effect at any
terminal under which Us... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
eca531978af6-1 | A special feature lets you set a conditional breakpoint at all instructions.
To set conditional breakpoints:
1.Enter an x in the All Instructions field to request this option. If you request the All Instructions option and set a variable-
change breakpoint, the breakpoint takes effect whenever the value of the variabl... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b500c0ba9d68-0 | InterTest™ and SymDump ® 11.0
Variable-Change Breakpoints
•COBOL and Assembler users set a conditional breakpoint to take effect whenever the value of a variable changes. To
do this, type x in the All Instructions field on the Conditional Locations screen.
•COBOL users must then specify the variable name on the Conditi... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b500c0ba9d68-1 | H'-12'.
Fullword
Specify fullword literals for comparisons with COBOL data items defined as COMP with a length of eight, as in
S9(8) COMP. Enter the literal as F'number' . The number can be preceded by a minus sign. For example, F'100'
or F'-100'.
Figurative Constants
Specify the following figurative constants for the ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5ba417ca5d12-0 | InterTest™ and SymDump ® 11.0
Enter OPERATOR (EQ, NE, GT, LT, GE, LE): lt
Enter RIGHT SIDE ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
f08ecee1d118-0 | InterTest™ and SymDump ® 11.0
–EQ for equal
–NE for not equal
–GT for greater than
–LT for less than
–GE for greater than or equal to
–LE for less than or equal to
•(Optional) The length of the left side or right side of the comparison. For more information, see Length of the
Comparison.
•The right side of the comparis... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
f08ecee1d118-1 | only one length. If you define both lengths, the smaller length is used.
The maximum permissible length for the left side or right side is 16 bytes for packed decimal data and 255 bytes for all
other data types.
Literal Formats
For more information about specifying literals, see Figurative Constants.
CORE Keywords
Spec... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
869c5f818041-0 | InterTest™ and SymDump ® 11.0
CWK
First byte of the COBOL program's Working-storage
DSA
First byte of the program's DSA
ITBE
First byte of the next instruction to be executed
LCL
First byte of the COBOL program's local-storage
MXR
InterTest for CICS maximum CICS request counter (implicit length = 4)
MXS
InterTest for C... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
869c5f818041-1 | To set or remove request breakpoints:
1.Specify function 13, S or R.
2.Specify the program names, transaction codes, or terminal names on the Function Selection Menu, and press Enter.
InterTest for CICS displays the Request Breakpoint Selection menu. Enter an x next to the options you want to select.
You can specify an... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8e6047e167fe-0 | InterTest™ and SymDump ® 11.0
DL/I
The program halts prior to all DL/I calls.
DB2
The program halts prior to all calls to DSNHLI (for DB2 users) or prior to all calls to ARIPRDI (for SQL/DS users).
CALLS
The program is halted prior to calls to software that InterTest has been instructed to recognize at installation tim... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8e6047e167fe-1 | Data monitoring (DM)
Instructs InterTest for CICS to capture data values for every executed COBOL statement. If data monitoring is
selected, statement tracing is automatically activated. In addition, a specific terminal ID or user ID is required.
Term ID (or .ANY or .NO) where trace options will take effect
Specifies t... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8b16b81a512a-0 | InterTest™ and SymDump ® 11.0
Replacement Options
Set replacement options to dynamically change the names of CICS resources (programs, files, transient data queues, and
temporary storage) specified in CICS CALLS by a monitored program. Remove the replacement options when you want
the program to use the resources define... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8b16b81a512a-1 | STORAGE1 in all temporary storage requests issued by the program.
TS selection mask: C'STORAGE1'
TS replacement mask: C'STORAGE2'
Limit monitoring (TON)
Specifies that the program be monitored and that replacement options, if specified, take effect only when the
program executes at the current terminal (*), a specific ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b4ec732837fd-0 | InterTest™ and SymDump ® 11.0
Set Protection Options
Set options to override the InterTest for CICS default protection rules for modifying main storage, the CSA, and load
modules. Remove the protection options to reinstate the default protection rules.
WARNING
Because the protection options can potentially damage your ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b4ec732837fd-1 | the current instruction.
Unprotect CSA (CSA)
Permits a program to modify areas in the CSA. Specify the offset and the length in hexadecimal.
Unprotect CWA (CWA)
Permits a program to modify areas in the CWA. Specify the offset and the length in hexadecimal.
Unprotect main storage area (LET)
Permits a program to modify a... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
7357708a28fb-0 | InterTest™ and SymDump ® 11.0
Special Options
This section discusses special options.
Set Special Options
Set special options to alter the InterTest for CICS standard monitoring procedures. Remove the special options to
reinstate the default monitoring rules.
To set or remove special options, follow these steps.
1.Spec... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
7357708a28fb-1 | Number of times to be monitored (MUS)
Limits the number of times a program should be monitored.
Limit total size of CICS storage (MXS)
Limits the amount of storage, including program storage, a program acquires.
Limit total number of CICS requests (MXR)
Limits the number of requests a transaction issues. This option is... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b3396da3ad21-0 | InterTest™ and SymDump ® 11.0
•Asterisk (*) routes the display to the current terminal
•termid routes the display to a particular terminal
•.ANY routes the display to all terminals
•OFF instructs InterTest for CICS to abend the task instead of halting it at an automatic breakpoint
NOTE
This option is useful when you do... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b3396da3ad21-1 | subprograms . The main program and subprograms are written in the same or different languages.
Composite support lets you test and debug a subprogram as if it were a separate program. This means you set
breakpoints and other monitoring options individually for any subprogram.
InterTest for CICS provides full symboli... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3bc89c236166-0 | InterTest™ and SymDump ® 11.0
•Change the flow of control in your program
•Test conditions based on specified variables
•Change the value of specified variables
•Create and execute commands as a group, like adding a new subroutine
•Automatically resume execution of your program at the same or different location
•Define... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3bc89c236166-1 | order in which you specified the entries.
NOTE
The status display accessed from the CNTL menu does not include the same formatting as the monitoring status
report discussed in other areas of this documentation.
WARNING
It is advisable to determine the monitoring status of a program, transaction, or terminal before alte... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ff75824e3edf-0 | InterTest™ and SymDump ® 11.0
CKPT intrval=00:10 hh:mm
CKPT done at 11:37 a.m.
COBDEMO Symbolic file is PROTDEM
UBP offset= +01B44 id=56A7D208 at=#898
from=L903... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
ff75824e3edf-1 | following table.
–offset=
The breakpoint location is defined as a hexadecimal offset from the beginning of the program.
–id=hhhhhhhh
The breakpoint ID number assigned by InterTest for CICS.
–at=location
The symbolic location specified when the breakpoint was set. A number preceded by a # sign refers to a statement
numb... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8908a7079e5d-0 | InterTest™ and SymDump ® 11.0
To select utility functions, specify Function 31 on the Function Selection Menu, and press Enter . The Utility Options
screen opens.
Specify the following functions on this screen. The equivalent function used in single-line commands is specified in
parentheses.
List InterTest tables (LIST... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
8908a7079e5d-1 | Set SystemWide Options
Set certain options on a system-wide basis. Specify Function 32 on the Function Selection Menu, and press Enter. The
System-Wide Options screen opens.
Specify the following options on this screen. Specify in parentheses the equivalent option used in single-line commands.
Enter ON to set an option... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
49b361803170-0 | InterTest™ and SymDump ® 11.0
Purge breakpointed tasks (PURGE)
Instructs InterTest for CICS to periodically purge tasks halted at a breakpoint for longer than the specified interval.
The first purge occurs when the option is specified. Subsequent purges occur at the end of the interval, specified
in hours and minutes i... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
49b361803170-1 | To RESUME EXECUTION at a different location, enter ONE new location:
COBOL paragraph, Assembler or PL/1 label: tasknumberformsg____________
COBOL or PL/1 statement number: _____ Offset: _____
T... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5268fe0215db-0 | InterTest™ and SymDump ® 11.0
options. For example, to set monitoring for the program COBDEMO when executed by the user ID BARNEY1, and also
set a breakpoint at the beginning of the program, enter the following single command from CICS:
CNTL=ON,PROG=COBDEMO,USR=BARNEY1,UBP=#1
CNTL Commands at a Glance
The following tab... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5268fe0215db-1 | EXEC Executes a module of CNTL
commands.Not available Not available.
MLOG Records a monitoring session
so that it can be repeated.Primary 2.7 Not available
NOTE
For more information about specifying CNTL Monitoring Options, see CNTL Monitoring Options.
CNTL Command propagation in a CICSPlex Environment
For CICSPlex env... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b281e80e13ee-0 | InterTest™ and SymDump ® 11.0
CNTL=ADD
CNTL=CKPT
CNTL=DUMP
CNTL=END, {SCOPE=GLOBAL} Propagated if SCOPE=GLOBAL is
specified.
CNTL=EXCL
CNTL=FOL
CNTL=GLOG
CNTL=INCL
CNTL=ITTRACE
CNTL=NEW
CNTL=OFF
CNTL=ON
CNTL=OFF,ALL
CNTL=EXEC Commands in the module are propagated if
they are eligible for propagation.
CNTL=GO
CNTL=INQ
C... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
0dbd6e4db5ee-0 | InterTest™ and SymDump ® 11.0
progname
Identifies a program.
locn
Identifies a program location. Specify a location in one of the following ways:
•One- to five-digit hexadecimal displacement (offset) from the beginning of the program
•Six- or eight-digit hexadecimal address
•A COBOL paragraph name enclosed in single qu... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
0dbd6e4db5ee-1 | To specify all four-character program names that begin with ABC followed by any one character, enter:
PROG=ABC+
NOTE
A plus sign, +, specifies only one character in a particular position.
To specify all four-character program names that begin with any character followed by ABC, enter:
PROG=+ABC
1109 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b00aea8e01b6-0 | InterTest™ and SymDump ® 11.0
To specify all four-character program names that begin with AB followed by any one character and C, enter:
PROG=AB+C
NOTE
Specify more than one plus sign in a promid. Do not specify a plus sign by itself: PROG=+ because it is invalid.
To specify all programs that begin with AB followed by ... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
b00aea8e01b6-1 | programs beginning with ABC that have their own entries in the monitoring table). Monitoring for ABC1 is controlled by the
specific entry for that program. However, if you specify CNTL=INQ,PROG=ABC*, you get monitoring status reports for all
programs that begin with ABC, including programs such as ABC1, which have sepa... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
10cf0cca24cf-0 | InterTest™ and SymDump ® 11.0
The command has the following parameters:
TODAY=ONLY
(Optional) Specifies that InterTest for CICS only restarts if the checkpoint occurred on the same day
NOWAIT
(Optional) Suppresses displays of messages and makes the restart much faster
When InterTest for CICS is restarted from a sequent... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
10cf0cca24cf-1 | This enables you to set breakpoints and monitoring options for that individual program. Similarly, if you specified
CNTL=ON,PROG=.ALL or you specified a generic program name, InterTest for CICS creates an individual monitoring
table entry for any program monitored under that entry that InterTest for CICS stops at an au... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
10b3d3abbb5f-0 | InterTest™ and SymDump ® 11.0
CNTL=ON,PROG=.OPTIONS,USR=.ANY,options
Options specified on a system-wide basis take effect for all programs InterTest for CICS monitors.
NOTE
Specify only the following options on a system-wide basis: ABI, CSA, FOL, ICT, LET, MXR, MXS, NUP, PRO,
RFC, RNT, RPC, RTD, RTS, SLB, STR, and TRC.... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
10b3d3abbb5f-1 | terminal or user ID.
Exclude Programs from Monitoring
To exclude a program from monitoring, enter:
CNTL=EXCL,promid
To remove the monitoring exclusion set by the CNTL=EXCL command, enter:
CNTL=INCL,promid
NOTE
INCL and EXCL are not sensitive to the monitoring user ID.
Examples
To exclude all of transaction PYRLs progra... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3a74fc71d2de-0 | InterTest™ and SymDump ® 11.0
CNTL=INCL,PROG=payroll1
Resume Task Execution
To resume task execution at a breakpoint, enter:
CNTL=GO,TASK=taskid,C[,options]
taskid
Represents the number of the task at a breakpoint. Use the CNTL=INQ command to determine the taskid .
C instructs InterTest for CICS to continue execution.
... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
3a74fc71d2de-1 | statements are executed.
•S=nnn[,I=nn][,N=CALL/ xxxx] instructs InterTest for CICS to halt program execution after nnn machine instructions are
executed.
•I=nn instructs InterTest for CICS to repeat the single-stepping after pausing for nn seconds
•N=CALL halts automatic single-stepping at a CALL or CICS commands
•N=xx... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5f8162f63115-0 | InterTest™ and SymDump ® 11.0
Examples
To specify that task 12345 resume at COBOL paragraph name TASK-NUMBER-FOR-MSG, enter:
CNTL=GO,TASK=12345,C,GO=`task-number-for-msg'
To specify that the task currently at a breakpoint at your terminal resume at statement number 142 and that the program
execute five COBOL verbs or P... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
5f8162f63115-1 | a branch (GO TO) to the intended routine using the GO= element and, in the process, you cross the boundaries of
SERVICE RELOAD, then it is necessary to set the addresses.
In PL/I, you not only must secure the proper addressability of data, but also remain within the same logical level (such as
the same DO block or call... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
40af54b5fbfe-0 | InterTest™ and SymDump ® 11.0
AT=locn moves the breakpoint to a different location
AT=X disables the breakpoint
Examples
To abend task number 54321 with a dump and a transaction dump code of DMP1, enter:
CNTL=GO,TASK=54321,Admp1
To abend task number 54321 without a dump, enter:
CNTL=GO,TASK=54321,AXXXX
To abend the cur... | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
40af54b5fbfe-1 | CNTL=INQ,PROG=cobdemo
To request a monitoring status report for all programs that is routed to the CSSL transient data queue, enter:
CNTL=INQ,TODEST=CSSL
To request a report listing information on all programs in the symbolic file that is routed to the CSSL transient data queue,
enter:
1115 | /Users/ilidiolopes/Documents/ca-intertest-and-ca-symdump-11-01.pdf |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.