In many cases, customers have set up a PROMMAC table to execute various CNTL commands at InterTest startup. One possible use is set up automatic region wide monitoring of all application programs that may execute in a CICS region; possibly to QA programs prior to moving them into production. At the same time, however, this may hinder development since monitoring some programs may lead to unnecessary breakpoints of different types and prevent effective testing during this verification phase. A way to avoid this is to incorporate commands into the PROMMAC to exclude various programs from being automatically monitored by InterTest.
I have a large number of programs I would like to exclude from monitoring by CA InterTest for CICS. Does an InterTest "PROMMAC" table allow generic wildcarding or do I need to list the programs individually?
A CA InterTest for CICS PROMMAC table will allow generic wildcarding for programs and transactions that begin with a common set of characters. The generic values can be carried out as far as necessary.
In many cases, users have set up a PROMMAC to monitor an entire CICS region automatically, possibly to QA programs prior to moving them into production. At the same time, however, this may hinder testing since monitoring some programs may lead to unnecessary breakpoints of different types. This can prevent effective testing prior to moving a specific application into a production region. A way to avoid this is to incorporate commands into the PROMMAC to exclude various programs from being automatically monitored by InterTest.
The following sample PROMMAC source statements will:
- Set up a default number of 20 monitoring table entries (PROM) and 40 exclusion table entries (PROX) when InterTest is started. If more entries are needed for either table, they will be added dynamically.
- Set up automatic monitoring for the entire CICS region using the 'PROG=.ALL' statement.
- As a result, the Cobol Demo program, COBDEMO, will receive the Automatic Breakpoint (ABP) at the 'Add +1 to Tasknum' source statement when the DEMC transaction is executed.
- Conversely, due to the generic exclude of ASM* and PL1* , the Assembler Demo program, ASMDEMO, and PL1 Demo program, PL1DEMO will receive the ASRA abend when the DEMA and/or DEMP transactions are executed.
- Exclude several additional sets of programs due to the wildcarding of the program names.
- Exclude a specific program from InterTest monitoring.
PROMMAC 'CNTL=START,PROM=20,PROX=40' <== Takes effect when InterTest starts.
PROMMAC 'CNTL=ON,PROG=.ALL' <== Monitor an entire CICS region
PROMMAC 'CNTL=EXCL,PROG=(ASM*)' <== Exclude all programs that begin with "ASM"
PROMMAC 'CNTL=EXCL,PROG=(PL1*)' <== Exclude all programs that begin with "PL1"
PROMMAC 'CNTL=EXCL,PROG=(CEE*)' <== Exclude all programs that begin with"CEE"
PROMMAC 'CNTL=EXCL,PROG=(P1*,IDX*,TM*)' <== Exclude all programs beginning with P1, IDX, and TM
PROMMAC 'CNTL=EXCL,PROG=(TS23TS23)',END <== Exclude this specific program
Please note the ",END" on the last "PROMMAC" statement that denotes the end of the PROMMAC control statements followed by the "END" on the next line to mark the finish of the macro.