InterTest™ and SymDump ® 11.0
  -------------- CA InterTest Batch EXECUTION CONTROL Panel ---------------------
  COMMAND ===>

  ------------------------------ Allocations ------------------------------------

  ALIB Dsname   ===>
       Member   ===>

  EXEC Job Step ===>             Proc Step ===>

  -------------------------- Execution Overrides --------------------------------

  PGM   ===> DFSRRC00            Initial Commands ===>

  PARM  ===> BMP,PAYROLL,,,,N0003,,2,,,0002,,,IMST
   or Number of Linkage Parameters ===>

  Task Libraries  ===> 'IMS.RESLIB'
     DSNAME       ===> 'USER01.LOAD'
       or         ===>
    (DDNAME)      ===>
                  ===>

From the Monitor Control panel, the process to test a BMP is the same as the process to test an IMS batch program.
Define Your Application
At least one BMP must be added to the IMS/VS Stage 1.
Ask the appropriate technical staff member to add the following application definitions to your IMS/VS System:
1.The APPLCTN MACRO must be defined with the DOPT option so that a new copy of the PSB is obtained each time
that the program executes.
2.The PARMLIM must be zero. The option PGMTYPE=BATCH forces the PARMLIM to zero.
3.Define a different BMP for each applications programmer who is testing in this manner. Each programmer should be
assigned a unique BMP to avoid having one programmer overwriting the PSB of another.
Note: You should only use this on an IMS/VS test system. The DOPT option can have a performance impact on a
production IMS/VS system.
Test Your Application


production IMS/VS system.
Test Your Application
The BMP defined is used to test the online application. Perform the following steps:
1.Replace the PSB for the BMP in the dynamic PSBLIB with the application PSB using the BMP PSB name.
For example, the BMP PSB is ABCD1234 and the application PSB is MYAPPLTN. Thus, the PSB defining MYAPPLTN
should be linked into the dynamic PSB library with a name of ABCD1234.
The programmer can use the same BMP name for any IMS/VS online applications to be tested and debugged.
NOTE
The dynamic PSBLIB data set must be concatenated after the ACBLIB data set. The PSB must reside in
a library with the same format as IMSVS.ACBLIB and be concatenated to the IMSACB DD statement. The
dynamic PSB must not be a member of IMSVS.ACBLIB.
2.Log on to the IMS/VS test system.
3.Enter an IMS/VS SET command in the form:
 738


InterTest™ and SymDump ® 11.0
 /SET TRAN trancode

where trancode  is the trancode of the BMP defined in the previous section. This command directs all input messages
from this LTERM (logical terminal) to trancode . Normally MFS provides the trancode to IMS/VS. The trancode of the
application to be tested is different from the trancode  through which the application Batch gains control.
4.Enter as many transactions as necessary. The transactions remain queued on the IMS/VS message queue until a test
session is initiated.
5.Log off IMS/VS. You might have a VTAM product, which lets you do a VTAM switch without logging off IMS/VS.
6.Log on to TSO.
7.Begin a session with the following entries on the Execution Control panel:
a.The name of the first module to be executed is DFSRRC00
b.The execution parameters for the first program are as follows:
BMP,mbr,psb,in,,ostd,,stimer,,,cputime,,,imsid
where:
•mbr-The name of the application program to be tested
•psb-Psbname of the BMP defined previously containing the PSB of the application program being tested
•in-The trancode of the BMP defined previously
•ostd-&opt&spie&test&dirca
•&opt - Action to be taken if the batch message region starts and no control program is active. Default is N
(ask operator for decision).
•&spie - Turn on the SPIE option (0) or not (1)
•&test - Check (1) or not (0) the addresses in the user call list for validity
•&dirca - Required for dynamic PSBs


•&dirca - Required for dynamic PSBs
•stimer-Whether to set the timer (1) or not (0). Must be set to 1 if CPUTIME 0
•cputime-BMP task timing option. No timing (0) or maximum task time ( n) where n is from 1 to 1440 minutes
•imsid-The IMS/VS system identifier where you want the BMP to execute
8.End the session, after testing and debugging with the application.
9.Log off TSO.
10.Log on to IMS/VS to the LTERM used in Step 3.
11.Review the output messages that may have been sent to your LTERM from your application program.
12.Enter the IMS/VS RESET command as follows:
 /RESET

Application Testing Scenario
If you have two programmers testing online IMS/VS applications, you could define the following MACROS:
 APPLCTN DOPT,PSB=INT01,PGMTYPE=BATCH
 TRANSACT CODE=(INT01A),PRTY=(0,0)
 APPLCTN DOPT,PSB=INT02,PGMTYPE=BATCH
 TRANSACT CODE=(INT02A),PRTY=(0,0)

 (PRTY=(0,0) is the default when PGMTYPE=BATCH.)

Jones would like to test and debug program PAYROLL while Smith tests program MANUFACT. Jones would either do a
PSBGEN or copy his PSB (PAYROLL) into the dynamic PSBLIB member INT01. Likewise, Smith would do the same thing
for his PSB (MANUFACT) but as member INT02.
Jones logs on to IMS/VS. He enters:
 739


InterTest™ and SymDump ® 11.0
 /SET TRAN INT01A

He then enters his FORMAT and data to execute his transaction. He can enter as many transactions as he likes. When
he is done, he may either log off of IMS/VS or do a VTAM switch. He then logs on to TSO to start his test session. On the
Execution Control panel under EXECUTION PARAMETERS he enters the following:
 PARM ==> BMP,PAYROLL,INT01,INT01A,,N00003,,2,,,0002,,,IMST

When he has ended the application, he can log back on to IMS/VS and view any output messages that his application
generated to his LTERM. Once he has viewed all of the IMS/VS output screens, he enters the following command before
logging off IMS/VS:
 /RESET.

Smith logs on to IMS/VS. He enters the following command:
 /SET TRAN INT02A

He then enters his FORMAT and data to execute his transaction. He can enter as many transactions as he likes. When
he is done, he can either log off IMS/VS or do a VTAM switch. He then logs on to TSO to start his test session. On the
Execution Control panel under EXECUTION PARAMETERS he enters the following:
 PARM==> BMP,MANUFACT,INT02,INT02,,N00003,,2,,,0002,,,IMST

When he has ended the application, he can log back on to IMS/VS and view any output messages that his application
sent to his LTERM. Once he has viewed all of the IMS/VS output screens, he enters the following command before
logging off IMS/VS:
 /RESET

Since IMS/VS sees the program with a trancode other than the trancode of the program being tested, different users may


schedule the program into multiple IMS/VS regions.
Test Message Switching Applications
Testing an IMS/VS application whose input messages are placed on the message queue by another IMS/VS program
requires a modification to the procedure outlined in the section Testing Your Application. Remember that you use the /
SET TRAN trancode command on your IMS/VS terminal to direct IMS to queue all transactions that are entered from your
LTERM to the trancode specified in the SET command. Therefore, your application running as BMP transaction trancode
is able to retrieve any messages on the queue destined for your application.
NOTE
The suggested method for testing IMS applications is using Option 5, Batch Link.
Unfortunately, any messages that are inserted to the message queue destined for another program are not tagged with
the BMP trancode. There is a way to work around this situation, as follows:
1.Follow steps 1 through 7 in the section Testing Your Application.
2.Set a breakpoint before the call to insert the message on the message queue. This is usually after the CHNG call.
3.Display the contents of the parms passed to your program using the DI or LI command.
4.Modify the trancode on the message to be inserted to be the BMP trancode and return to the Intercept panel.
5.Continue the testing of the application.
 740


InterTest™ and SymDump ® 11.0
6.Return to the Execution Control panel, split the screen, and select Option 6 (TSO COMMAND PROCESSOR).
7.Copy the PSB for the program that retrieves the inserted messages into the dynamic PSBLIB data set with the BMP
PSB member name. End the split screen mode.
8.Change the second execution parameter, mbr, to the name of the program retrieving the inserted messages, on the
Execution Control panel.
9.Begin testing the application. Follow steps 8 through 12 in the section Testing Your Application.
Test Procedure Using BTS
Like an IMS batch application, a DB/DC application executed using BTS is not the first program executed. The module
BTSTSOST is the first module executed. It in turn attaches the IMS region controller, DFSRRC00, which attaches the
application program to be executed. To facilitate testing of IMS applications with both InterTest Batch and BTS, create
a CLIST to allocate IMS, BTS, and InterTest Batch-related data sets. If you need help in creating the CLIST, ask your
technical support staff for assistance.
The CLIST allocations are given as follows:
IMS-related:
 DFSRESLB  IMS  IEFRDER  DFSVSAMP

BTS-related:
 BTSIN BTSOUT BTSPUNCH BTSSNAP QIOPCB QALTPCB QALTRAN TASKLIB

InterTest Batch -related:
 INT1PARM  INT1LOAD  INT1PNNL  INT1PROF  INT1MSGL  INT1CLOG INT1CLIB INT1REPT

NOTE
For additional information about InterTest Batch-related CLISTs, see Basic Foreground Demo Session.
Preparation for Test Execution - BTS
Replace Step 5  in the section Preparation for Test Execution with the following step:


Replace Step 5  in the section Preparation for Test Execution with the following step:
•On the Execution Control panel, specify the name of the load library containing the BTS load modules. The first
program to be executed is BTSTSOST.
The execution parameters are the same parameters that are specified to BTS. Generally, the parameter that is
specified is DLI,,, . If you specify the program member name, the psbname, or both, as you would to test a batch IMS
program, a USER 0642 abend can occur (parm exceeds maximum length). The programs and the PSBnames to be
tested are identified on ./T cards in the BTSIN data set.
NOTE
The dynamic STEPLIB function is performed by the BTS Tasklib option. Do not specify a TASKLIB ddname on
the Execution Control panel, or BTS will believe that TASKLIB ddname is not allocated and terminate. Allocate
the ddname TASKLIB in the CLIST to invoke the application. The load libraries containing the modules to be
tested must be allocated to the ddname TASKLIB.
Use the Monitor Control panel to identify the programs that have their execution controlled by the application. Identify
only the programs that you want to debug. Also, provide the PROTSYM files that contain the symbolic information for the
programs that you would like to debug.
 741


InterTest™ and SymDump ® 11.0
BTS Interactions
After you have entered the Execution Control panel and the Monitor Control panel, BTS begins execution by reading
the BTSIN data set. A BTS0007I message and images of the BTS input commands are displayed on the terminal.
BTS requests a BTS command, a /FORMAT statement, or a /*. The /FOR modname causes BTS to display a formatted
IMS screen for input. Once the data has been input, BTS attaches the application program. InterTest Batch gains control.
When the application program calls CBLTDLI, BTS again has control until the IMS language interface module passes
control back to the calling program. As a result, the BTS displays are interleaved with the Intercept panels.
If the BTS session ends prematurely and there was no BTS error message displayed on the terminal, review the BTSOUT
data set. The BTSOUT data set often contains data that does not appear on the terminal.
NOTE
The application intercepts all keyed PA1s during the BTS testing session.
Message Switching
Message switching is when an IMS application program inserts a message to the message queue that is either an output
message to another IMS terminal or an input message to another transaction. If the message is an input message to
another transaction, then BTS schedules another program to process the input message. To set breakpoints in the IMS
program that processes the message inserted into the message queue, perform the following steps:
1.Program A inserts a message for program B. When the first executable statement in program A displays on the
terminal, enter QUALIFY B  on the command line. The beginning of the listing for program B displays. Set any
UNCOND or WHEN breakpoints that you want. Enter  QUALIFY A  on the command line to return to the program A
display.


display.
2.You can also accomplish this by specifying UNCOND ALL ENTRY on the command line of the Intercept panel upon
initial entry into the first IMS application program.
BTS0067I MESSAGE
If this message should occur while testing in a BTS environment, ensure the BTSEXT parameter has been added to the
PARMLIB member used to invoke the application.
Display and Figure Verbs in a BTS Environment
When using these verbs in a BTS message switching environment, ensure the BTSSYSO parameter has been added to
the PARMLIB member used to invoke the application. For more information, see Applications Using Message Switching
and DISPLAY or Figure Verbs in InterTest Batch Options. Without this option, abends 0C4 and/or 0C1 can occur.
Test COBOL Programs Which Run Under an ADF Shell
Use this product to test COBOL programs that run under an ADF shell. The recommended procedure for doing this is the
same as for testing COBOL programs under BTS. A programmer specifies BTSTSOST on the Execution Control panel
as shown in the previous section and the names of the COBOL programs to be tested on the Monitor Control panel. Both
of these panels are shown in the previous section Preparation for Test Execution - BTS. Specify the four-character ID of
the ADF SIGN-ON screen on the /FOR statement. All of the functions of the application are available while testing the
specified COBOL programs.
Although this application does not display or intercept code that is written in the ADF Audit Language, some users use the
application facilities to help debug their ADF code. One way is to insert a call to a dummy COBOL program at whatever
point in the ADF code they want to intercept execution. Once in the Breakpoint Intercept panel, you can use the Option 2:


CORE to display ADF work areas and tables. This requires a good knowledge of ADF. The best source for this information
is the IBM IMS ADF II Manuals.
 742


InterTest™ and SymDump ® 11.0
Test IBM DB2 Applications
To test IBM DB2 applications using your product in foreground, you can modify the TSO CLIST CAMRCDB2, which
invokes the application. You find CAMRCDB2 in the CAVHCLS0 data set. A sample batch  execution of DB2 programs
follows to give you some background into the DB2 commands DSN and RUN and how they relate to DB2 foreground
execution.
NOTE
The instructions in this section are for debugging an application under Foreground, Option 1 on the Primary
Option Menu. The suggested method for testing DB2 applications is using Option 5, Batch Link. For more
information on batch link and about debugging your DB2 Stored Procedure, see Batch Link Facility.
NOTE
If you are using the Call Attach Facility of DB2, you may use the CAMRCLST CLIST to debug your application in
foreground.
To run the DB2 program DSN8BC3 under InterTest Batch
1.Modify the TSO CLIST CAMRCDB2 by replacing INTBATCH with the data set prefix defined at install time.
2.Verify that the application's ISPF Panel library is concatenated to the IBM ISPF panel library, ddname ISPPLIB , and
the message library is concatenated to the IBM ISPF message library, ddname ISPMLIB.
NOTE
For more information, see CAMRCDB2 in Customize CLISTs in InterTest Batch Options.
To test a DB2 program (PAYROLL in this example), perform the following steps:
1.EXEC the modified application CLIST.
The DB2 panel displays.
2.Complete the three fields on the InterTest Batch DB2 panel. Each field is defined in the following table:
Field Description
DB2 Subsystem Name ===> The name of the DB2 Subsystem where the program being tested


DB2 Subsystem Name ===> The name of the DB2 Subsystem where the program being tested
runs.
Plan Name ===> The DB2 Plan name for the program being tested.
Library Name ===> The Load Library name where the program being tested resides.
1.Press Enter after completing the panel fields. The Primary Option Menu displays.
2.Select Option 1: Foreground. The Execution Control panel displays.
3.Supply the main application program name and the required STEPLIB to execute the application. Press Enter to see
the Monitor Control panel.
4.On the Monitor Control panel, type in the names of the programs that you want to debug and DSNs of the PROTSYM
files containing the symbolic information for the programs you want to debug. Press Enter to receive the *INITIAL*
Intercept panel.
5.Run the test session in the usual way.
Notice that once you invoke InterTest Batch, there is no difference in the way the application is used to test DB2
programs.
NOTE
This procedure does not let you end the program and return to the Execution Control panel to retest the
same program. You must exit the application and rerun the CLIST (Step 1).
Use the following approach when debugging in foreground with DB2 and InterTest Batch:
1.Get InterTest Batch working for non-DB2 programs.
2.Get the DB2 program running under native TSO.
 743


InterTest™ and SymDump ® 11.0
3.Ensure that the DB2 program is correctly prepared as follows:
a.DB2 pre-processed
b.Compiled and post processed into a PROTSYM file
c.Linked
d.A DB2 bind step or job is run for the recompiled program
e.All other DB2 protocol is done
4.Modify the application CLIST as explained previously.
Test Data Generation
This product assists you in generating test data or files for testing. Consider the following COBOL program:
000100 IDENTIFICATION DIVISION.
000200
000300 PROGRAM-ID.    DATAGEN.
000400 AUTHOR.        J. DOE.
000500 INSTALLATION.  DATACEN.
000600 REMARKS.
000700
000800
000900 ENVIRONMENT DIVISION.
000901 INPUT-OUTPUT SECTION.
000902 FILE-CONTROL.
000910 COPY OUTFILE.
001000
001100 DATA DIVISION.
001200
001300 FILE SECTION.
001400 COPY OUTREC.
001500
001600 PROCEDURE DIVISION.
001700 BEGIN.
001800     OPEN OUTPUT OUT-FILE.
001900 0100-WRITE-IT.
002000     WRITE OUT-RECORD.
002010     GO TO 0100-WRITE-IT.
002100 0100-END-IT.
002200     CLOSE OUT-FILE.
002300     GOBACK.GOBACK Key
Assume that the COPY codes OUTFILE and OUTREC contain the SELECT and FD information respectively. Use the
following command to set a breakpoint at the write statement and display the record contents in COBOL format:
UNCOND 0100-WRITE-IT (RECORDS)
Each time statement 1900 is executed, the COBOL program stops and a formatted display of the record for OUT-FILE


appears. To generate the data, type over the values that you want, press the END key to return to the Intercept panel, and
press the GO key to write the record.
Adding another File Definition, OPEN, and a READ before the WRITE could make this into a COBOL format record editor.
 744


InterTest™ and SymDump ® 11.0
Test Under Roscoe
If you run this product under Roscoe , you should be aware of the following points:
•The suggested method for testing applications with Roscoe  is using Option 5, Batch Link.
•The application runs under the ETSO OR BTSO facility of Roscoe .
•A special JCL conversion facility to simplify file allocations is available for Roscoe  users and is described in JCL
Conversion for Roscoe .
•Your application PF key assignments can differ from your Roscoe  PF key assignments. Define PF keys by selecting
the KEYS option on the Primary Option Menu.
•The application lets you use the split-screen facility to establish a second session using the PF SPLIT key. You also
can use standard Roscoe  commands to initiate a second Roscoe  session.
•Use the Roscoe  SUSPEND function to suspend an InterTest Batch session and return to Roscoe . You can then
perform other Roscoe  functions; however, you cannot call another ETSO OR BTSO application. Resume ETSO OR
BTSO to return to your session.
•Use the PF PRINT key to print to an InterTest Batch data set, which can be allocated to the AWS or any MVS data set.
•Use the Roscoe  print facility to print to a Roscoe  data set.
Allocations Facility for ISPF
Before you can begin a debugging session, you must allocate the data sets that your program will be using. The
allocations facility for TSO/ISPF users provides a number of features that makes this set-up process easier.
Briefly, the allocations facility lets you to do the following actions:
•Create and manage ALIB (Allocations Library) allocations members. ALIB is the internal allocations format for the


application. The ALIB is a PDS that consists of members created through the ALIB editor or JCL converter of this
application. You can create new allocations library members, or edit, browse, allocate and free data sets specified in
existing members. Once you save an ALIB, you can use its allocations in the future, saving you valuable debugging
set-up time.
NOTE
The ALIB dataset is optional and is used by the InterTest Batch foreground testing facility. For more
information, see Allocate ALIBs (Optional) in InterTest Batch Options.
•Convert allocation lists from ALIB to CLIST format. Although ALIB is an efficient format that is sufficient for most
situations, conversion to CLIST is useful in complex allocation situations that are beyond the straightforward free-
and-allocate capabilities of ALIB (conditional data set allocations, for example). Converting to CLIST may also be
necessary if your particular operating environment requires the CLIST format.
•Browse existing JCL members in PDS, Librarian , and Panvalet  libraries.
•Convert JCL to ALIB format. This feature is useful if you have existing JCL that you would like to use for your
allocations. The system's conversion utility fully supports JCL allocation features, and converted JCL is displayed
in Edit mode for further processing. You can also use the resulting ALIB on the Execution Control panel to allocate
and free the required application DDs. You can convert JCL to CLIST format by first converting it to ALIB format, then
converting it from ALIB to CLIST (it is not necessary to save in ALIB format). Using this feature saves you the time
needed to key in and debug ALIB or CLIST statements from scratch.
The allocations facility panels conform to ISPF file name and command conventions (for example, the ISPF Locate
command).
NOTE


command).
NOTE
For more information on how to use the JCL conversion facility, Roscoe  users should see JCL Conversion for
Roscoe .
 745


InterTest™ and SymDump ® 11.0
The Allocations Main Menu
Access the Allocations Main Menu by selecting option 3 from the Primary Option Menu. The Allocations Main Menu the
starting point for accessing all of the allocations facility's features:
The fields on the Allocations Main Menu are as follows:
1 ALIB Create new allocations members, edit and browse existing
members, allocate/free data sets specified in members, and
convert ALIB members into CLIST format.
2 JCL Browse existing JCL members in PDS, Librarian , or Panvalet
libraries. You can also select members for conversion from JCL
to ALIB format. The converted JCL is displayed in Edit mode for
further processing.
3 CURRENT Display current session allocations and free, browse, or edit
allocated data sets.
4 OPTIONS Specify various JCL conversion options and ALIB member
export options, and identify procedure libraries (proclibs) used for
expanding JCL procedures found during JCL conversion.
Option 1 ALIB (Allocations Library) Functions
The ALIB library option lets you create new allocations members, edit and browse existing members, allocate/free data
sets specified in members, export (convert) ALIB members to CLIST format, and import (convert) JCL members to ALIB
format. Selecting this option displays the Allocations Library panel.
Select an ALIB Member from the Allocations Library Panel
The application displays the Allocations Library panel if you select option 1 (ALIB) from the Allocations Main Menu. Use
this panel to enter the name of the member you want to edit.
For ISPF library members: The Allocation Library panel has the following input fields:
For ISPF library members:
Project, Group, Type Required. Enter the three-level qualifier for standard data set names in ISPF.


Member Optional. If you do not know the member name, leave this field blank or enter a member
name pattern. Valid ISPF wild card  member pattern characters are:
% Substitutes for any one character. May be
the first character.
* Substitutes for any number of characters.
May not be the first character.
For PDS members:
Data set name Optional. If your member is not in an ISPF library, enter the actual,
cataloged name of the file. The name can be up to 44 characters
long, with segments up to eight characters long, separated by
periods. You can specify any MVS data set name and use wild
card substitutions, as described for the Member field.
Volume serial Optional. This field identifies the VOLSER of the data set specified
in the data set name field and is necessary only when a file is not
cataloged.
 746


InterTest™ and SymDump ® 11.0
To select an ALIB Member from the Allocations Library panel:
1.Enter the ISPF library or PDS information for the member you want to edit.
2.Press Enter.
If you entered a complete member name, the application displays the Allocations Edit panel. If you entered a partial
member name, the application displays the ALIB Member Selection List.
Select an ALIB Member from the ALIB Member Selection List
If you did not specify a complete member name on the Allocations Library panel, the application displays the ALIB
Member Selection List panel. This panel lists all the allocations library members or those that match the pattern.
CA InterTest Batch  ALIB: USER01.INTBATCH.ALIB --------------------------------
Command ===>                                                   Scroll ==> PAGE
Cmd Name       Message  VV.MM Created  Modified______  Size  Init  Mods ID
    NEW                 01.02 14.060   14.077   12:47 00090 00090 00000 USER01
    PGM1                01.08 92.351   14.077   12:33 00001 00001 00000 USER01
    PGM2                01.01 14.077   14.077   14:09 00013 00013 00000 USER01
    PGM3                01.08 14.062   14.077   10:27 00002 00002 00000 USER01
    TEST1               01.01 14.077   14.077   14:10 00002 00002 00000 USER01


TEST2               01.02 14.078   14.078   10:11 00001 00021 00000 USER01
Enter the following line commands in the Cmd field before each member in the list:
AL To allocate all the data sets in the ALIB member.
B To browse the ALIB members. The Allocation List Browse panel
displays. From this panel you may view the allocation list in an
ALIB. You can scroll through the members and use the ISPF
Locate (L) command to locate specific members. The Allocation
List Browse panel is identical in format to the Allocations Edit
panel, but no edits may be made.
C To display the Convert to CLIST panel, which lets you convert the
selected ALIB member to CLIST format. For more information, see
Convert ALIB to CLIST (Export ALIB).
E/S To edit the ALIB member. Issuing this command displays the
Allocations Edit panel. For more information, see Edit ALIB
Allocations.
F To free all the ddnames in the ALIB member.
Edit ALIB Allocations
Display the Allocations Edit panel in any one of the following ways:
•From the Allocations Library panel by specifying a particular member
•From the ALIB Member Selection List panel by entering the line commands E or S next to a member
•From the JCL Allocations Step Selection List panel by selecting converted JCL steps for allocation
The Allocations Edit panel lets you create, modify, and manipulate lists of data set allocations. A list may be saved into the
ALIB, exported (converted) into a CLIST library, allocated, or freed. JCL may be imported (converted) into ALIB format.
A sample Allocations Edit Panel is shown next:


A sample Allocations Edit Panel is shown next:
CA InterTest Batch ALIB EDIT: PDS USER01.INTBATCH.ALIB(PGM1) -------------------
COMMAND ===>                                                    SCROLL==> PAGE
LINE COMMANDS - I(NNN), D(NNN), R(NNN), AL(LOCATE), F(REE), S(PACE)
 747


InterTest™ and SymDump ® 11.0
PRIMARY COMMANDS - ALLOCATE, SAVE, CREATE, RESET, CANCEL, IMPORT, EXPORT,
 REPLACE, FREE, OPTS, END.  FOR AN EXPLANATION, SEE THE USER GUIDE OR HIT HELP.
CMD  DDNAME   DATA SET NAME                                DISP VOLSER   DCB AL
MSG> Imported from USER01.JCL(PGM1)
MSG> USER01   //USER01R   JOB (42400000),'USER01',CLASS=A,M
MSG> RUN     //RUN      EXEC PGM=MAINCOB,REGION=4M,PARM='            RUN
MSG> ..  MAINCOB
.... @STEPLIB USER01.LOAD                                   SHR            N
.... SYSPRINT SYSOUT=X                                     NEW            N
.... SYSABOUT SYSOUT=X                                     NEW            N
.... SYSOUT   SYSOUT=X                                     NEW            N   A
.... SYSUDUMP SYSOUT=X                                     NEW            N
.... CARDIN   USER01.CARDIN.FILE                            NEW            Y
.... CARDOUT  USER01.SYSOUT                                 SHR            N
CMD Enter all line commands in this area.
DDName Data definition name. Enter a valid ddname in this field.
Data Set Name Data set name. Enter a valid data set name in this field. Data set
names must be fully qualified and without apostrophes. SYSOUT=
and TERMINAL are valid entries.
Disp The disposition of the data set. Enter the disposition of the data
set in this field. Valid dispositions are:
OLD
SHR
NEW
Default: SHR.
Volser The old volume serial, if any, of the data set. You may enter
another volume serial on which the data set is to reside.
DCB Yes DCB information is present


DCB Yes DCB information is present
No There is no DCB information for the data set
AL A The ddname is allocated
blank The ddname is not allocated
Primary Commands
The Allocations Edit Panel primary commands, which you enter on the COMMAND ===> line, are shown next.
ALLOCate Allocates all the allocations listed on the screen.
SAVE Saves any changes made to the list of allocations in the current
ALIB member.
CREate Writes the list of allocations to a new ALIB member. Issuing this
command displays the Copy to Allocation Library panel.
RESet Removes all non-relevant MSG lines created during JCL
conversion or during allocation.
CANcel Exits without saving any changes and redisplays the Member
Selection List panel from which you entered the editor. All changes
to the member that were not saved are discarded.
 748


InterTest™ and SymDump ® 11.0
IMPort Invokes the JCL Converter to convert raw JCL into ALIB format.
Import JCL from a PDS, Librarian , Panvalet , and current session
allocations libraries. The application displays the JCL Import
Specifications panel. For more information, see Converting JCL to
ALIB (Import JCL).
EXPort Converts the current ALIB member into CLIST format. For more
information, see Convert ALIB to CLIST (Export ALIB).
REPlace Replaces a member with the contents of the current member.
Issuing this command displays the Copy to Allocation Library
panel.
END Ends the current Edit session and displays the Member Selection
List panel from which you entered the editor. The member is
automatically saved if it was modified.
FREE Frees all ddnames in the current member.
OPTS Lets you change conversion and allocation options. Invoking this
command displays the JCL Conversion/Allocation Options panel.
For more information, see Option 4: JCL Conversion/Allocation
Options.
Line Commands
Enter line commands in the Cmd field next to the ddname:
Dataset Attributes Panel
Use the Dataset Attributes panel to review and change the data set attributes including DCB information, space
information, and extended (SMS) attributes. This panel displays when you select a ddname on the Allocations Edit panel.
Dataset Attributes Panel: Fields
The following table describes the Dataset Attributes Panel fields:
LRECL The logical record length of the data set.
BLKSIZE The block size of the data set.
RECFM The record format of the data set. Valid formats are:
F Fixed
FB Fixed blocked
FBA Fixed blocked with carriage control character
V Variable
VB Variable blocked
U Undefined
Default:  the current record format of the data set.


VB Variable blocked
U Undefined
Default:  the current record format of the data set.
DSORG The organization of the data set. Valid organizations are:
PO Partitioned Organization (PDS)
PS Sequential
SPACE UNIT The space unit used by the data set for primary and secondary storage. Valid space units
are:
BLK Blocks
TRK Tracks
CYL Cylinders
Default:  the current space unit of the data set.
PRIME SIZE The primary storage.
 749


InterTest™ and SymDump ® 11.0
SECONDARY The secondary storage.
DIRECTORY BLOCKS The number of directory blocks.
RELEASE Whether unused storage should be released. Valid values are:
Yes Release unused storage
No Do not release unused storage
Default:  No
UNIT NAME The unit name.
VOLUME SERIAL If you entered a VOLSER on the Allocations Edit panel, it is displayed here. If this field is
blank or you want to change the VOLSER, enter the new VOLSER.
OR ALLOCATE LIKE DDNAME OR
DSNAMEUse this field to obtain DCB information from another data set or ddname. Enter a valid
ddname in parentheses (for example,INT1LOAD), or a fully qualified data set name.
STORCLAS The SMS storage class.
DATACLAS The SMS data class.
MGMTCLAS The SMS management class.
DSNTYPE One of the following valid data set types:
LIBRARY
PDF
PIPE
HFS
RECORG One of the following valid record organizations:
KS Keyed sequential file
ES Entry-sequenced file
RR Relative record file
LS Linear space file
AVGREC Allocate space by records using one of these valid specifications:
U Unit is one record
T Unit is one thousand records
M Unit is one million records
KEYOFF Identifies the offset within the record where the key resides, for keyed files only.
KEYLEN Identifies the length of the key.
To change DCB information
1.Enter the DCB information in the appropriate fields.
2.Enter END  on the command line and press Enter, or press the End key.
Result: The application saves the DCB information and redisplays the
Allocations Edit panel.
NOTE
Enter CANCEL  to ignore the DCB information and to redisplay the Allocations Edit panel.
Copy to Allocation Library Panel


Copy to Allocation Library Panel
The application displays the Copy to Allocation Library panel whenever the ALIB editor needs the name of the ALIB data
set and member in order to write the allocations list. The application displays this panel if you issue a Replace or Create
command from the Allocations Edit panel.
To specify the ALIB data set name
 750


InterTest™ and SymDump ® 11.0
NOTE
The ALIB data set is optional. If your installation is not using an ALIB data set no entry is required on this panel.
Press PF3 several times until you return to the InterTest Batch PRIMARY OPTION MENU. For more information,
see the section Allocate ALIBs (Optional) in InterTest Batch Options.
1.If the data set to which you are writing is an ISPF library, complete the information for the ISPF Library fields (Project,
Group, Type, and Member). For more information on these fields, see Select an ALIB Member from the Allocations
Library Panel.
2.If the data set to which you are writing is not an ISPF library, complete the information for the Other partitioned data
set fields (Data set name, Volume serial). For more information on these fields, see Select an ALIB Member from the
Allocations Library Panel.
3.Enter Yes in the Replace like-named member field if you want the editor to overwrite members by the same name in
the library (the default is No).
4.Press Enter.
Result: The application creates or replaces the ALIB data set and
redisplays the Allocations Edit panel.
Convert ALIB to CLIST (Export ALIB)
Access the Convert to CLIST Options panel in one of these ways:
•From the ALIB Member Selection List panel by entering the line command C (Convert to CLIST) next to the member to
convert.
•From the Allocations Edit panel by entering the primary command EXP (Export) on the command line.
If your allocation situation is too complex for the limitations of the ALIB format (for instance, if you need conditional
allocations or need to use other TSO commands beyond simple free-and-allocate statements), you may find it useful to
translate your ALIB statements to CLIST.


translate your ALIB statements to CLIST.
The ISPF library and Other partitioned data set fields, in which you specify your destination ( TO) data set, are the same as
those on the Allocations Library panel.
The other fields are as follows:
Replace ? Determines if the target CLIST library is to be replaced.
Yes Replace the target CLIST library
No Do not overwrite the existing CLIST library.
After you press Enter, the cursor is placed
in the Data Set Name field and you can
specify a new name
Edit CLIST ? Determines if the ISPF editor will be invoked to edit the converted member.
Yes The ISPF editor will be invoked to edit the
converted member
No The ISPF editor will not be invoked
To convert from ALIB to CLIST
1.Specify the destination (TO) data set in either the ISPF library or the Other partitioned data set fields. Modify the
member name, if necessary.
2.Enter Yes or No in the Replace? and Edit CLIST? fields.
 751


InterTest™ and SymDump ® 11.0
3.Press Enter.
Result: The application performs the conversion.
If you entered Yes in the Edit CLIST field,
the application invokes the ISPF editor to
allow you to further modify the CLIST. If
you entered No in the Edit CLIST field, the
application redisplays the panel from which
the converter was invoked.
Convert JCL to ALIB (Import JCL)
The application displays the JCL Import Specifications panel when you use the Import command on the Allocations
Edit Panel. Use this panel to enter the name and type of the JCL library member from which you want to import JCL for
conversion.
The ISPF library and Other data set fields are the same as those on the Allocations Library panel. The other fields are as
follows.
Option The data set format of the data set you want to import for conversion.
Blank The member is in a PDS.
L The member is in a Librarian  library.
P The member is in a Panvalet  library.
S Import the currently allocated data set list
(current session allocations). No other fields
on this panel need to be completed if you
choose this option.
Librarian
index typeWhen converting Librarian  members, determines the amount of directory information
displayed.
Q Quick. Displays the member name only and
takes less time than the S (Short) option.
S Short. Displays more information on the
selected member than the Q (Quick) option.
To convert from JCL to ALIB
1.Enter the data set format of the JCL member you want to import for conversion.
2.In either the ISPF library or the other partitioned data set fields, specify the source  (FROM ) data set that contains the
JCL you want to import for conversion.
3.Press Enter.


JCL you want to import for conversion.
3.Press Enter.
Result: If you have requested the JCL Conversion/
Allocations Options Panel, it will be
displayed next. Otherwise, the JCL member
selection panel is displayed.
Option 2 The JCL Library/Allocations Functions
Option 2 (JCL) on the Allocations Main Menu panel lets you select existing JCL members for conversion to ALIB format.
PDS, Librarian , and Panvalet  libraries are supported. Use the resulting ALIB member on the Execution Control Panel to
allocate and free DDs.
 752


InterTest™ and SymDump ® 11.0
Specify the JCL to Convert
The application displays the JCL Library panel when you select the JCL option from the Allocations Main Menu. Use this
panel to specify the name and type of the JCL member you want to convert.
Complete the following input fields:
Option The format of the data set you want to import for conversion.
Blank The member is in a PDS.
L The member is in a Librarian  library.
P The member is in a Panvalet  library.
For ISPF Library members:
Project, Group, Type Required. Enter the three-level qualifier for standard data set names in ISPF
Member Optional. If you do not know the member name, leave this field blank or enter a member
name pattern. Valid ISPF wild card  member pattern characters are:
% Substitutes for any one character. May be
the first character.
* Substitutes for any number of characters.
May not be the first character
For PDS members:
Data set name Optional. If your member is not in an ISPF library, enter the actual, cataloged name of
the file. The name can be up to 44 characters long, with segments up to eight characters
long, separated by periods. You can specify any MVS data set name. You can use wild
card substitutions, as described for the Member field.
Volume serial Optional. This field identifies the VOLSER of the data set specified in the Data set name
field and is necessary only when a file is not cataloged.
Librarian
index typeUsed only when converting Librarian  files. Determines the amount of directory
information the application displays.
Q Quick. Displays the member name only and
takes less time than the S (Short) option.
S Short. Displays more information on the


takes less time than the S (Short) option.
S Short. Displays more information on the
selected member than the Q (Quick) option.
To specify a JCL member for conversion:
1.Enter the ISPF library or PDS information.
2.If you are converting a Librarian  member, enter the Librarian  index type you desire.
3.Press Enter.
4.The application displays the JCL Member Selection List panel.
Use the JCL Member Selection List
After specifying a partial or complete member name on the JCL Library panel, the application displays the JCL Member
Selection List panel.
CA InterTest Batch JCL: PDS USER01.INTBATCH.JCL----------------------------------
Command ===>                                                   Scroll ==> PAGE
    Enter  B to Browse member, S to select member for JCL conversion
 753


InterTest™ and SymDump ® 11.0
Cmd Name       Message  VV.MM Created  Modified______  Size  Init  Mods ID
    ABSDUMP             01.00 14.325   14.325   15:47 00006 00006 00000 USER01
    ASMHAL              01.00 14.154   14.154   11:40 00015 00015 00000 USER01
    TESTX               01.02 14.008   14.211   15:47 00043 00022 00027 USER01
    TEST2               01.03 14.188   14.062   09:13 00005 00005 00000 USER01
    TEST3               01.00 14.188   14.188   10:34 00007 00007 00000 USER01
This panel displays the JCL members that match the member name or wild card pattern specified in the Member field on
the JCL Library panel. If you made no entry in the Member field, the application displays all the members of the library.
Enter the following line commands in the Cmd field before each member in the list:
B To browse the JCL library member. the application displays the
JCL Browse panel.
S To select the JCL member for conversion to ALIB format. Once
the JCL conversion has ended, the application displays the JCL
Allocations Step Selection List panel. Note that if you have not set
the option to suppress the Conversion/Allocation Options panel,
it is displayed before converting the JCL and displaying the JCL
Allocations Step Selections Panel. For more information, see
Option 4: JCL Conversion/Allocation Options.
The JCL Browse Panel


Option 4: JCL Conversion/Allocation Options.
The JCL Browse Panel
The application displays the JCL Browse panel when you use the Browse command on the JCL Member Selection List
panel.
Use the JCL Browse panel to check the contents of a member selected for conversion and to determine the STEP names.
Scroll through the member to find the STEPs you want to use. Entering an END command or pressing the End key
redisplays the JCL Member Selection List panel.
CA InterTest Batch Browse JCL: PDS USER01.INTBATCH.JCL --------------------------
Command ===>                                                   Scroll ==> PAGE
Cmd __________________________________ JCLs __________________________________
    //USER01C  JOB (12300000,76),'RUN',CLASS=A,MSGCLASS=Z,
    //    NOTIFY=USER01
    //PROCLIB  DD  DISP=SHR,DSN=USER01.PROCLIB
    //QDD1     EXEC  COB,N=QDD
    //COB.SYSIN DD   DISP=SHR,DSN=USER01.QDD.COBOL
    //QEE2     EXEC  COB,N=UXX
    //COB.SYSIN DD   DISP=SHR,DSN=SYS2.ROSCOE56.DAILY.BKUP(-5)
Select Converted JCL Steps for Allocation
The application always displays the JCL Allocation Step Selection List panel after JCL conversion, if there were multiple
steps in the JCL. The panel lists all JCL EXEC cards in the member:
CA InterTest Batch JCL: PDS USER01.INTBATCH.JCL(TEST3) -------------------------
Command ===>                                                   Scroll ==> PAGE
    Enter S beside step to select, or press END key to select all
Cmd----------------------------------- Steps ------------------------------


Cmd----------------------------------- Steps ------------------------------
    DELETE    //DELETE  EXEC PGM=IEFBR14
    C         //C       EXEC PGM=IKFCBL00,REGION=4M,
    LKED      //LKED      EXEC PGM=IEWL,
    PRINTIT   //PRINTIT   EXEC PGM=IEBGENER,REGION=1024K
    DELETE    //DELETE  EXEC PGM=IEFBR14
 754


InterTest™ and SymDump ® 11.0
    C         //C       EXEC PGM=IKFCBL00,REGION=4M,
    LKED      //LKED      EXEC PGM=IEWL,
    PRINTIT   //PRINTIT   EXEC PGM=IEBGENER,REGION=1024K
NOTE
If you have not set the option to suppress the Conversion/Allocation Options panel, it displays before converting
the JCL and displaying the JCL Allocations Step Selections Panel. For more information, see Option4: JCL
Conversion/Allocation Options.
To select converted JCL steps for allocation
1.On the JCL Allocation Step Selection List panel, enter S next to the steps whose data set allocations you want to use
or enter the END command (or press the END key) to use all the steps. The steps you select form your allocation list.
2.Press Enter (unless you used an END key instead of entering the END command in step 1).
3.The application displays the Allocations Edit panel so you may edit the newly created Allocation List, saved in an
allocation library or converted to CLIST format.
For more information on working with allocation libraries, see Edit ALIB Allocations.
The Conversion Process
When you select JCL for conversion to ALIB format, the JCL converter checks the JCL for syntax. If the JCL executes
procedures and PROCLIBs were specified on the Conversion/Allocation Options panel, the JCL converter expands
the procedures found in the PROCLIBs, substitutes parameters, and performs step overrides. If the JCL executes a
procedure that is not found in a PROCLIB, a WARNING panel is displayed and JCLCheck message CAY6027E is
included in the ALIB member, indicating the name of the procedure that was not found.


included in the ALIB member, indicating the name of the procedure that was not found.
CA InterTest Batch ALIB EDIT: PDS CAI.CAVHJCL(DEMOJCL)                    ----
COMMAND ===>                                                    SCROLL==> PAGE
LINE COMMANDS - I(NNN), D(NNN), R(NNN), AL(LOCATE), F(REE), S(PACE)
PRIMARY COMMANDS - ALLOCATE, SAVE, CREATE, RESET, CANCEL, IMPORT, EXPORT,
 REPLACE, FREE, OPTS, END.  FOR AN EXPLANATION, SEE THE USER GUIDE OR HIT HELP.
CMD  DDNAME   DATA SET NAME                                DISP VOLSER   DCB AL
MSG> Imported from CAI.CAVHJCL(DEMOJCL)
MSG> DEMOJCL //DEMOJCL  JOB (124400000),'INTBAT10 DEMOJCL
MSG> STEP1   //STEP1    EXEC PGM=CAMRCOBB,REGION=4M                  STEP1
MSG> ..  .CA
.... @STEPLIB USER01.LOAD                                   SHR            N
.... SYSPRINT SYSOUT=X                                     NEW            N
.... SYSOUT   SYSOUT=X                                     NEW            N
.... REPORT   SYSOUT=X                                     NEW            N
******************************** BOTTOM OF DATA *******************************
To save the created Alib member
1.Place the cursor on the command line and type in 'SAVE' to save the ALIB version of the JCL.
The Copy to Allocation Library screen opens.
2.Fill in the library and member name where your ALIB member is to be saved and press Enter.
The ALIB member is saved.
Special Considerations
There are some special conversion considerations for certain types of DD statements. The application allocates DD


There are some special conversion considerations for certain types of DD statements. The application allocates DD
statements to a particular TSO session by using SVC 99, which performs dynamic allocation. SVC 99 does not allow the
following four DD statements to be dynamically allocated:
 755


InterTest™ and SymDump ® 11.0
•STEPLIB
•JOBLIB
•STEPCAT
•JOBCAT
The application changes STEPLIB to @STEPLIB and JOBLIB to @JOBLIB.
JCL Keywords Supported for Conversion
The JCL converter supports the following JCL keywords and positional operands. The degree of converter support is
noted.
JCL Keywords Description
DSN= Fully supported.
DISP= All operands except conditional dispositions are supported. If a DD
with a conditional disposition is passed, the third sub parameter is
ignored.
DCB= The DCB keywords supported are:
RECFM=
BLKSIZE=
LRECL=
DSORG=
HOLD= Ignored.
SYSOUT= Fully supported. Only the CLASS parameter is used.
UNIT= Fully supported.
VOL= Fully supported. Only the VOLSER parameter is used.
SUBSYS= Fully supported. Check with the vendor to make sure that a DD
can be allocated for this subsystem with SVC 99.
SPACE= Fully supported.
STORCLAS= Fully supported.
DATACLAS= Fully supported.
MGMTCLAS= Fully supported.
DSNTYPE= Fully supported.
RECORG= Fully supported.
AVGREC= Fully supported.
KEYOFF= Fully supported.
KEYLEN= Fully supported.
LIKE= Fully supported.
REFDD= Fully supported.
JCL Keywords Not Supported for Conversion
The JCL converter does not convert all JCL keywords because many parameters in batch JCL are not supported in TSO
CLISTs. The converter ignores backward references and keywords that it does not convert.
AMORG= FLASH=
BURST= FREE=
CHARS= LABEL=
 756


InterTest™ and SymDump ® 11.0
CHKPT= MODIFY=
CNTL= MSVGP=
COPIES= OUTLIM=
DDNAME= OUTPUT=
DEST= PROTECT=YES
DLM= QNAME=
DSID= UCS=
FCB=
Option 3 Current Allocations
The application displays the Current Allocations panel when you select option 3 (CURRENT) from the Allocations Main
Menu panel. The current allocations option displays current session allocations and lets you free, browse, or edit allocated
data sets.
The Current Allocations panel lists currently allocated data sets, which may have been previously allocated in TSO Logon
Procedures (such as STEPLIB), by a CLIST, or by the Allocation Facility. A sample Current Allocations List panel follows:
----------------- CA InterTest Batch Current Allocations List ------------------
Command ===>                                                   Scroll ==> PAGE
   Line commands: F - Free, B - Browse, E -Edit.
Cm DDName   Disp   Dataset Name                                         Volser
   ISP10155 SHR    USER01.INTBATCH.ISPMLIB                               OSI011
   ISPPROF  SHR    USER01.ISPF.ISPPROF                                   CAI801
   SYSPRINT        TERM
   SYSTERM         TERM
   SYSOUT          TERM
   SYSUDUMP        JES
   SYSIN           TERM
   SYS00001 SHR    SYS1.BRODCAST                                        MVSLIB
   ISPALIB  SHR    ISP.ISPALIB                                          MVXAD1
   ISRCFIL  SHR    ISR.ISPFLMF.CFIL                                     MVS003
   SYSHELP  SHR    SYS2.HELP                                            MVSLIB
            SHR    SYS1.HELP                                            MVXAD1


SHR    SYS1.HELP                                            MVXAD1
            SHR    USER.HELP                                            CAI800
   ISPTABL  SHR    USER01.ISPF.ISPPROF                                  CAI801
   ICQTABL  SHR    ICQ.ICQTLIB                                          MVXAD1
   SYSPROC  SHR    SYS2.CLIST                                           MVSLIB
            SHR    ICQ.ICQCCLIB                                         MVXAD1
            SHR    ICQ.ICQACLIB                                         MVXAD1
            SHR    ISR.ISRCLIB                                          MVXAD1
            SHR    SYS1.RMFCLS                                          MVXAD1
You may scroll through the list and enter the following line commands next to any data set in the list:
F/S Free the data set/ddname.
B Browse the data set. This is an ISPF function and operates only if
it is supported by your ISPF installation.
E Edit the data set. This is an ISPF function, and operates only if it is
supported by your ISPF installation.
 757


InterTest™ and SymDump ® 11.0
Option 4 JCL Conversion/Allocation Options
The application displays the JCL Conversion/Allocation Options panel when you select option 4 (OPTIONS) from the
Allocations Main Menu panel.
Use the Options option to specify JCL conversion and ALIB member export options and Proclibs (procedure libraries)
used for expanding JCL procedures found during JCL conversion.
The Current Allocations/Options fields are described next:
Proclib 1 -7 The procedure library names you want to use for expanding procedures found in
JCL during conversion. When your JCL job stream executes procedures, assign the
procedures a Proclib to be used during the conversion process. Enter up to seven
procedure library names. If you require more than seven Proclibs, use a pre-allocated
ddname instead.
Pre-allocated DD If you require more than seven Proclibs, or if your Proclibs are pre-allocated by other
means (for example, in the TSO logon procedures or custom CLISTs), enter the name of
a pre-allocated ddname here.
EasyProclib For EasyProclib users, this field specifies whether the JCL conversion facility uses
private JCL procedure libraries identified by the //PROCLIB ddname in the job stream.
Yes The JCL conversion facility uses private
JCL procedures using the //PROCLIB
ddname in the job stream.
No The JCL conversion facility will  not use
private JCL procedures using the //
PROCLIB ddname in the job stream.
Default: No
CLIST 'Control' Whatever you enter here appears in the CLIST control statement when you convert
from ALIB to CLIST (for example, NOMSG and NOLIST). For more information on valid


CLIST control statements, see the IBM publication TSO Command Language Reference
Manual .
DCB info on
(Attr, Alloc)Determines whether DCB information appears on the attribute statement or the allocate
statement in your CLIST when you convert from ALIB to CLIST. The choice is mainly
dictated by user-preference.
ALLOC Put DCB information on the generated
ALLOC statement.
ATTR Generate DCB information on a separate
ATTRIB statement.
Default: Attr
If allocated (Reuse, Free) Controls the allocation process during CLIST conversion. If the data set is already
allocated:
R The application tries to reuse the allocation.
The REUSE statement is generated on the
allocations card.
F The application frees the data set before
allocation. The FREE statement is
generated on the allocations card.
Default: Free
If exists (Delete, Use  - for new data sets
only)Used for allocating a new, non-temporary data set. Generates a DELETE statement in
the CLIST to prevent a Duplicate Data Set Name  error.
 758


InterTest™ and SymDump ® 11.0
DELETE Generates a DELETE statement in the
CLIST. This deletes any existing data set
allocated with the same name.
USE A Duplicate Data Set Name  error is
generated if there is an existing data set
allocated with the same name.
Default: USE
Suppress (Yes or No) Indicates whether or not this panel should be suppressed when converting JCL. Once
this option is set to Yes, this panel only displays when choosing option 4 from the
Allocations Main Menu.
JCL Conversion for Roscoe
This section describes how to use the JCL Conversion facility for Roscoe .
The JCL Conversion facility lets you convert JCL to Roscoe  RPF format so that Roscoe  can execute it. Use this facility to
convert the JCL that performs the allocations required by programs you are testing in foreground with your product.
Access the JCL Conversion Facility
To enter the JCL Conversion facility, enter the following command on the command line:
[xxx.]IBCONV
where xxx is the prefix of the library in which the product is installed. Omit this prefix if the application is installed in a
common execution library.
The application displays the JCL Converter panel.
Specify the JCL Member for Conversion
The JCL Converter panel lets you specify the JCL member for conversion:
----------------------- CA InterTest Batch JCL Converter ----------------------
 Option ===>
 Select an Option and press ENTER
             A - AWS....
             L - LIB....
             D - DSN.... USER01.LIB.CNTL(TEST*)
             J - JOB...:

             X    -  Exit

 JCL Conversion PROCLIBs:
             Proclib1... USER01.PROCLIB
             Proclib2... SYS2.PROCLIB


Proclib2... SYS2.PROCLIB
             Proclib3...
             Proclib4...
             Proclib5...
             Proclib6...
             Proclib7...
 759


InterTest™ and SymDump ® 11.0
Identify Where the JCL Member Is Stored
JCL members are stored in one of the following areas:
AWS Roscoe  active working storage
LIB Roscoe  user library
DSN Data set (PDS, sequential or Librarian )
JOB The currently attached job. You cannot change this jobname.
The information specified in these fields reflects your profile. If you change this information, for example if you change
the DSN, application updates your profile, which is stored in your library in member ZZIBOPTS. Follow standard Roscoe
conventions for specifying the AWS, Library or DSN.
Identify the PROCLIBs
In addition to specifying where the JCL member is stored, you must specify at least one PROCLIB. Each PROCLIB
identifies a library where JCL procedures are stored. Even if the JCL member does not use a procedure, one PROCLIB
must be specified on the JCL Conversion panel.
Display the JCL Member
Follow these steps:
1.Enter a letter (A,L,D,J) in the Option field to indicate where the JCL member is stored.
2.Complete the information for the option you selected:
–For A (AWS), enter the AWS name or leave this field blank.
–For L (library) or D (DSN), enter the library or DSN name or a partial name using the generic characters + or *, or
leave this field blank.
–For J (job), the name of the currently attached job already appears on the JCL Conversion panel and cannot be
changed.
3.Enter at least one PROCLIB name in the PROCLIB list.
4.Press Enter.
If you entered a complete AWS, library or DSN name, Roscoe  displays the JCL member you selected. If you entered


a partial name or left the name blank, Roscoe  prompts you for additional information. See Selecting the JCL Member
from a List, which follows, for instructions on specifying that information. If you selected J (job), Roscoe  displays file 2
(the JCL file) of the currently attached job.
Select the JCL Member from a List
If you do not specify a complete AWS, library or DSN name on the JCL Converter panel, Roscoe  prompts you for
additional information.
For AWS, Roscoe  displays a list of members. Enter a to the left of the desired AWS and press Enter to attach and display
the member.
For a library :
•If you left the library field blank on the JCL Converter panel, Roscoe  displays the Library Facility panel. Specify the
library information and, optionally, the member name, and attach the library.
–If you specify the member name, Roscoe  displays the member.
–If you omit the member name, Roscoe  displays the member list.
•If you specified a partial library name on the JCL Converter panel, Roscoe  displays a list of members that meet the
criteria.
 760


InterTest™ and SymDump ® 11.0
When Roscoe  displays the member list, enter a to the left of the library JCL member and press Enter to attach and display
a member.
For a DSN :
•If you left the DSN field blank on the JCL Converter panel, Roscoe  displays the Data Set Facility panel. Specify the
data set information and attach the data set to display a list of members.
•If you specified a partial data set name on the JCL Converter panel, Roscoe  displays a list of members that meet the
criteria.
When Roscoe  displays the member list, enter a to the left of the data set JCL member and press Enter to attach and
display a member.
Convert the JCL Member
When the application displays the JCL member you specified on the JCL Converter panel or selected from a list, you can
review the member to make sure it is the one you want to convert.
Follow these steps:
1.Enter GO on the command line.
2.Press Enter.
The application converts the JCL member to Roscoe  RPF format and displays the following message:
RPF generated in AWS xxxx
Where xxxx is the current AWS.
After the JCL member has been converted, enter a to attach and display the converted JCL member.
Review and Edit the Converted JCL
You can review and, if desired, edit the converted JCL to delete unnecessary steps. Note the following:
•The converted JCL is divided into steps.
•:: denotes a comment that identifies a STEP in the original JCL and displays the EXEC card.
•: denotes a message generated during conversion. These messages can be ignored.
•Each step contains:
–FREE statements to deallocate previously allocated data sets.


•Each step contains:
–FREE statements to deallocate previously allocated data sets.
–DELETE statements, if necessary, to delete non-temporary data sets that need to be created and may already exist.
–ALLOC statements to allocate and, if necessary, create the data sets.
Use standard Roscoe  editing commands to edit the converted JCL. When you finish editing the member, save it in your
own Roscoe  library.
Execute the Converted JCL
After the JCL member has been saved in your Roscoe  library, you can execute the converted JCL member at any time
to perform the allocations. Before executing a program that you want to test with the application, execute the appropriate
RPF member to allocate the files required by the program.
 761


InterTest™ and SymDump ® 11.0
Convert JCL to ALIB in Batch
A utility exists, CAMRAUTL, which takes a given JCL member of a PDS and creates an ALIB member from it. Review JCL
member CAMRAUTL in CAVHPROC. There are three required DDs, shown in the following table:
DDname Description
JCL DD pointing to the JCL member to be used in creating the ALIB.
ALIB DD pointing to the ALIB PDS.
SYSPROC DD pointing to the PROCLIB concatenation.
JCL example:
// JOB
//********************************************************************
//CRE8ALIB EXEC PGM=CAMRAUTL
//STEPLIB  DD  DISP=SHR,DSN=CAI.CAVHLOAD
//SYSPROC  DD  DISP=SHR,DSN=USER.JCL
//JCL      DD  DISP=SHR,DSN=USER.JCL(TESTJCL)
//ALIB     DD  DISP=SHR,DSN=USER.ALIB
//
Batch Link Facility
Batch link lets you debug applications from a terminal while they execute in batch.
The batch link facility offers the following advantages over standard foreground debugging:
•No foreground allocations
Executing an application in foreground requires that all data sets used by the application be first allocated in
foreground. While the application provides a JCL conversion and allocations facility for this purpose, the allocation and
de-allocation process can complicate the debugging process. Applications debugged using batch link are executing in
batch, so no foreground allocations are required.
•Execution of leading and trailing steps
Sometimes an application is executed as part of a multi-step job stream and one or more leading steps must be


executed before the application can run. Batch link allows debugging of any job step executing in batch, and therefore
permits the normal completion of leading steps prior to debugging. After debugging, any trailing steps can be
completed prior to job termination.
•Use of temporary files
Because batch link permits the execution of leading steps, applications can use temporary files created by a prior step.
The job stream can then delete these files when they are no longer needed.
•Multi-step debugging
Batch link supports the debugging of multiple steps within the same job stream. When debugging of any step
completes, the job continues as usual with the execution of the following step until end of job. Each batch link user
controls which steps will be debugged within a job stream before the job is submitted.
•Multi-user debugging
At any time during a batch link debugging session, you can suspend the session and disconnect the terminal from
the batch debugging session. This lets the debugging session be retrieved by another (or even the same) user
at a later time. This facilitates the transfer of the debugging session from one user to another without terminating and
restarting the application.
 762


InterTest™ and SymDump ® 11.0
InterTest Batch JCL Requirements
Before debugging a batch application using the batch link facility, modify the application JCL to enable the batch link
environment. Do this manually as described here, or automatically using the batch link JCL conversion facility.
Change the application JCL for each step to be debugged. These changes include the following steps:
1.Modify the PGM= field on the // EXEC statement to execute CAMRBL01.
2.Insert the application executable library at the end of the STEPLIB or JOBLIB concatenation if it does not exist in
LINKLIST.
NOTE
It is possible to use the dynamic symbolic support feature if you have multiple Endevor  C1DEFLTS and are
debugging as if you have a single C1DEFLTS.
To do so, insert a fully qualified data set name containing the C1DEFLTS with your site under the STEPLIB
concatenation ID.
3.Insert additional DD statements for the application data sets used by the debugging engine, including INT1PARM,
INT1PROF, INT1PNLL, and INT1MSGL.
NOTE
For more information about these additional DD statements, see The Batch Link DD Statements in Batch
Link JCL Edit Panel.
4.Insert an INT1OPTS DD containing in-stream debugging options, such as the original program name from the PGM=
field on the // EXEC statement.
NOTE
For more information about valid options, see Batch Link Options in Batch Link JCL Edit Panel. Different
requirements apply for DB2 applications.
The following code is a sample JCL stream for batch link:
 // JOB
 // EXEC PGM=CAMRBL01,PARM='application parms'
 //STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD


//STEPLIB  DD DISP=SHR,DSN=CAI.CAVHLOAD
 //         DD DISP=SHR,DSN=USER.LOADLIB
 //         DD DISP=SHR,DSN=USER.C1DEFLTS
 //INT1PARM DD DISP=SHR,DSN=CAI.CAVHSAMP
 //INT1PROF DD DISP=SHR,DSN=CAI.PROFLIB
 //INT1PNLL DD DISP=SHR,DSN=CAI.CAVHPNL1
 //INT1MSGL DD UNIT=SYSDA,SPACE=(TRK,(1,1))
 //INT1OPTS DD *
   EXEC=CAMRCOBB,PROFILE=USER01
 /*

Debug a Batch Application
When a job step that has been modified for batch link executes, the program CAMRBL01 starts the debugging engine in
batch. At this point the job step becomes available for debugging.
Batch link debugging sessions can only be connected to a terminal using the Batch Link Option Menu, described later
in this section. You choose a batch link job step for debugging from the selection list provided. Doing so connects the
terminal to the batch job, creating a batch link debugging session.
Debugging is exactly the same as it is for a standard foreground testing session, with the following exceptions:
 763


InterTest™ and SymDump ® 11.0
•The application and the debugging engine both execute in batch, not in foreground. The terminal acts only as a
window  for communicating with the batch link session.
•The batch link session begins with the Monitor Control panel, not an Execution Control panel.
•When the debugging session ends, the batch job continues normally with the next step, and the terminal returns to the
Batch Link Option Menu.
Use the Batch Link Menus
You can display the Batch Link menu by selecting option 5 from the Primary Option Menu:
The Batch Link Option menu consists of four options:
JCL
Use this option to convert and submit JCL for batch link. Conversion is only required once per JCL stream, unless
you alter your original JCL or decide to change which steps to debug. Alternatively, you can modify the JCL
manually.
Batch Link
Use this option to select a batch job for debugging. Batch link lists all jobs available for debugging. Select the job
that you want to debug to connect your terminal to the batch job, creating a batch link session.
Edit JCL
Use this option to edit and submit existing batch link JCL.
NOTE
This option is only supported under ISPF.
Scheduling
Use this option to use the DB2 SP and IMS/DC scheduling feature. This feature lets you specify which programs
in which regions you want the application to monitor, and lets all other programs run unmonitored. This feature
lets you use the same region for debugging and for running the normal IMS/DC and DB2SP workload.
Batch Link JCL Conversion Panel
Option 1 of the Batch Link Option Menu displays the Batch Link JCL Conversion panel. Use this panel to identify the
library name (and member if the library is partitioned) containing the JCL to be converted for batch link.
NOTE


NOTE
The batch link JCL conversion utility creates a new JCL member in the output destination of your choice.
The Batch Link Conversion panel fields are described next:
Field Name Description
Project The high-level qualifier for the library containing the JCL to be
converted.
Library The middle-level qualifier for the library containing the JCL to be
converted.
Type The lowest-level qualifier for the library containing the JCL to be
converted.
Member The name of the member to be converted when the library is
partitioned. Leave this field blank for sequential files or to produce
a member list for a PDS.
 764


InterTest™ and SymDump ® 11.0
Data Set Name If the JCL library name does not conform to
PROJECT.LIBRARY.TYPE, enter the name of the library in this
field. Use quotes for fully qualified names. If quotes are omitted,
your ISPF prefix is appended as the high-level qualifier.
Volume Serial If the JCL library is not catalogued, use this field to enter the
VOLSER of the DASD volume on which the library resides.
Dataset Password For password-protected libraries only, enter the password in this
field.
Once you have given values to all of the necessary fields on the panel, press Enter to advance to the next panel.
Select a JCL Member
If you have not provided a member name and your JCL library is partitioned, you are prompted to select a member for
conversion.
 ----------------- CA InterTest Batch MEMBER SELECTION -------------------------
  COMMAND INPUT ===>                                           SCROLL ===> HALF
       NAME
       **************************** TOP OF DATA ********************************
       ARMYCOMP
       ARMYRUN
       ARMY5STP
       ASM1
       COMPNGO
       DB2COMP
       DB2DEMO2
       DB2DEMO3
       DB2RUN
     s DEMOJCL
       IMSBUILD
       *************************** BOTTOM OF DATA ******************************

To select a member, place an s in the prefix area next to the member name and press Enter.
Batch Link Conversion Options Panel
After you identify the JCL library, use the Batch Link Conversion Options panel to specify options for the conversion.
The Batch Link Conversion Options panel fields are described next:
Field Name Description
Proclib 1-7 The data set names of any procedure libraries required for
converting the JCL.
Preallocated DD Identifies the ddname used to pre-allocate procedure libraries


Preallocated DD Identifies the ddname used to pre-allocate procedure libraries
required for converting the JCL.
Output JCL Lib The name of the JCL library where the converted JCL should be
written. If this field is left blank, a temporary output file is allocated.
When specifying an output JCL library, use quotes for fully
qualified data set names. If quotes are omitted, your ISPF prefix is
appended as the high-level qualifier.
 765


InterTest™ and SymDump ® 11.0
Output Member If a partitioned output JCL library is specified, enter the member
name into which the converted JCL is to be written.
Unit The unit field to be used if the converted JCL is being written to a
temporary file.
If using a temporary file for the converted JCL, VIO must not be
used.
Profile Library The name of the application profile library that should be used
by the batch debugging engine, excluding the profile member
name. Use quotes for fully qualified data set names. If quotes are
omitted, your ISPF prefix is appended as the high-level qualifier.
Profile Member The name of the member within the profile library that should be
used by the batch debugging engine.
Options Enter additional batch link options in this field. These options are
discussed in Batch Link JCL Edit Panel.
After you assign values to all of the necessary fields on the panel, press Enter to advance to the next panel.
Select Job Steps
If your JCL contains multiple steps, you are prompted to select job steps.
 ----------------- CA InterTest Batch Step Selection List ----------------------
  COMMAND INPUT ===>                                            SCROLL ===> PAGE
       Select one or more of the following Steps:
       **************************** TOP OF DATA ********************************
  s    1     //STEP1    EXEC PGM=CAMRCOBB,REGION=4M
       2     //STEP2    EXEC PGM=CAMRCOB,REGION=4M
       *************************** BOTTOM OF DATA ******************************

You can select any or all job steps in the selection list. To select a job step, place an s in the prefix area next to the entry.
To select multiple job steps, place an s in the prefix area next to each entry.
Press Enter to convert the JCL for batch link.
Convert and Submit the JCL


Press Enter to convert the JCL for batch link.
Convert and Submit the JCL
Once the JCL is converted, you are placed into EDIT, which lets you view or further modify the JCL prior to submitting it.
If you entered an output data set name, the JCL is written to that data set. If no output data set name is provided, a
temporary sequential file is used.
  EDIT       SYS00222.T093343.RA000.USER01.IBJCL.H01         Columns 00001 00072
  Command ===>                                                  Scroll ===> CSR
  ****** ***************************** Top of Data *****************************
  000001 //USER01A  JOB (42400000),'Demo JCL',CLASS=K,MSGCLASS=X,
  000002 // NOTIFY=USER01
  000003 //STEP1    EXEC PGM=CAMRBL01,REGION=4M
  000004 //STEPLIB  DD  DISP=SHR,DSN=CAI.CAVHLOAD
  000005 //         DD  DISP=SHR,DSN=USER01.LOADLIB
  000006 //SYSPRINT DD  SYSOUT=*
  000007 //SYSOUT   DD  SYSOUT=*
  000008 //INT1OPTS DD *
  000009   EXEC=CAMRCOBB, PROFILE=USER01
  000010 /*
 766


InterTest™ and SymDump ® 11.0
  000011 //INT1PARM  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHSAMP
  000012 //INT1LOAD  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHLOAD
  000013 //INT1PNLL  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHPNL1
  000014 //INT1MSGL  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHMSG0
  000015 //INT1PROF  DD  DISP=SHR,DSN=USER01.INTBATCH.PROFLIB
  000016 //INT1CLIB  DD  DISP=SHR,DSN=USER01.INTBATCH.CAVHSRC
  000017 //INT1CLOG  DD  SYSOUT=*
  000018 //INT1REPT  DD  SYSOUT=*
  ****** **************************** Bottom of Data ***************************

For each job step selected for debugging, the following modifications are made for batch link:
1.The PGM= field on the // EXEC statement is modified to execute CAMRBL01, the batch link driver program.
2.The application executable library is added to the STEPLIB or JOBLIB concatenation.
3.Additional DD statements are inserted for the application data sets used by the debugging engine, including
INT1PARM, INT1PROF, INT1PNLL, and INT1MSGL. These additional DD statements are described in detail later.
4.An INT1OPTS DD statement is added containing in-stream debugging options, such as the original program name
from the PGM= field on the // EXEC statement.


from the PGM= field on the // EXEC statement.
5.If you are using the dynamic symbolic support feature and you have multiple C1DEFLTS, you can concatenate to
the STEPLIB a fully qualified data set name containing the Endevor  site ID associated with the load module being
monitored. Alternatively, you can also let CAICCI discover the site id and populate the symbolic file for you.
NOTE
The requirements are slightly different for DB2 applications, as described.
When you are ready to submit the JCL, enter SUBMIT on the command line and press Enter. The job is submitted but you
remain in the EDIT session. Exit the EDIT session by entering END or CANCEL on the command line and then pressing
Enter.
The job begins execution and becomes available for debugging as soon as one of the selected steps begins to execute.
JCL Conversion Limitations
The following JCL constructs are not currently supported by the Batch Link JCL Conversion utility:
Partial DD overrides
Given the following JCL:
 //PROC1    PROC
 //S1       EXEC PGM=TESTPGM
 //TEST1    DD   DISP=(,CATLG,DELETE),DSN=USER01.TESTDSN,
 //         UNIT=DISK,SPACE=(1,(1,1))
 // PEND
 //MYPGM    EXEC PROC1
 //S1.TEST1 DD   UNIT=SYSDA

The DD TEST1 will not be generated correctly in the converted JCL.
JCL invokes a PROC that updates or adds JCL keywords to an EXEC statement.
Given the following JCL:
 //PROC1    PROC
 //S1       EXEC PGM=TESTPGM,PARM='ABC'
 //TEST1    DD   SYSOUT=*
 767


InterTest™ and SymDump ® 11.0
 // PEND
 //MYPGM    EXEC PROC1,PARM='DEF'

The PARM keyword on the EXEC card will not be updated.
NOTE
Any client hitting this limitation can still use the utility to do most of the conversion or you can edit the JCL and
make the necessary changes manually.
When the application converts JCL for batch link, all the called catalogued procedures are expanded and all expanded
steps from the procedures are given a stepname of just  procstepname.
When there are COND= parameters in the original JCL with stepname.procstepname  references, these are modified to
use the procstepname . As a result, the reference may no longer be unique.
IF statements and DD statements with stepname.procstepname  references are not modified and the
stepname.procstepname  reference is no longer valid. Therefore you must examine the converted JCL and modify these
instances as appropriate.
Batch Link Selection Panel
Option 2 of the Batch Link Option Menu displays the Batch Link Selection panel. Use this panel to select a batch job for
debugging.
NOTE
This panel is not accessible unless the batch link facility is initialized on your system and at least one batch link
job step is ready for debugging.
A batch link debugging session is functionally identical to a foreground test session.
NOTE
For a detailed description of the foreground test facility, see Debugging Commands.
 ----------------- CA InterTest Batch Batch Link Selection --------------------
 COMMAND INPUT ===>                                          SCROLL ===> PAGE
            *         *         *         *         *        *         *
      #     Jobname   Stepname  Program   Owner     User     Trans     SYSID
      **************************** TOP OF DATA *********************************


**************************** TOP OF DATA *********************************
      1     JOB01A    STEP1     TESTPGM   USER01                       TSO01
      2     JOB02A    STEP1     CAMRCOBB  USER02                       TSO02
      3     JOB03X    RUN       PAYROLL   USER03   LINKED BY USER03    TSO01
      ************************* BOTTOM OF DATA *********************************

Debugging a Job Step
To select a job step for debugging, type S next to the entry on the selection list, and press Enter. The Monitor Control
panel appears and the debugging session begins.
NOTE
Only one user at a time can select a batch link job step. If another user has selected a step, the entry is marked
as 'Linked by userid '.
Suspended Jobs
When you select a batch link job step that was suspended, the debugging session resumes at the point at which the
session was suspended.
 768


InterTest™ and SymDump ® 11.0
To suspend a session enter the SUSPEND command after the initial debugging intercept. A session is suspended if a
user ID is canceled during a debugging session.
Debugging on Foreign LPARs
You can debug a job that is executing within the SYSPLEX on a different LPAR than the one you are currently logged on
to. The SYSID column displays the LPAR the job is executing on.
After you select a job that is executing on a foreign LPAR, enter your user credentials to start debugging.
NOTE
For more information, see Configure Batch Link and Sysplex.
Batch Link JCL Edit Panel
Option 3 of the Batch Link Option Menu displays the Batch Link Edit JCL panel. Use this panel to identify the library
name (and member if the library is PDS) containing the JCL to be edited before submitting it for the batch link debugging
session.
The following table describes the Batch Link JCL Edit panel fields.
Field Name Description
Project The high-level qualifier for the library containing the JCL to be
edited.
Library The middle-level qualifier for the library containing the JCL to be
edited.
Type The lowest-level qualifier for the library containing the JCL to be
edited.
Member The name of the member to be edited when the library is
partitioned. Leave this field blank for sequential files or to produce
a member list for a PDS.
Data Set Name If the JCL library name does not conform to
PROJECT.LIBRARY.TYPE, enter the name of the library in this
field. Use quotes for fully qualified names. If quotes are omitted,
your ISPF prefix is appended as the high-level qualifier.
Volume Serial If the JCL library is not catalogued, use this field to enter the
VOLSER of the DASD volume on which the library resides.


VOLSER of the DASD volume on which the library resides.
Once you have given values to all of the necessary fields on the panel, press Enter to advance to the ISPF Edit panel.
After editing, you can save your changes and submit the changed JCL for batch link execution.
Select a JCL Member for Editing
If you have not provided a member name and your JCL library is partitioned, you are prompted to select a member for
editing.
 ----------------- CA InterTest Batch MEMBER SELECTION -------------------------
 COMMAND INPUT ===>                                           SCROLL ===> HALF
       NAME
       **************************** TOP OF DATA ********************************
       ARMYCOMP
       ARMYRUN
       ARMY5STP
       ASM1
 769


InterTest™ and SymDump ® 11.0
       COMPNGO
       DB2COMP
       DB2DEMO2
       DB2DEMO3
       DB2RUN
     s DEMOJCL
       IMSBUILD
       *************************** BOTTOM OF DATA ******************************

To select a member, place an s in the prefix area next to the member name and press Enter.
The Batch Link DD Statements
The following table describes the additional DD statements required for batch link. You must add these DD statements to
each job step selected for debugging:
DDNAME Data Set Name Description
INT1PARM CAI.CAVHSAMP Contains the parameter members used by
the batch debugger.
INT1LOAD CAI.CAVHLOAD Contains the product executables.
INT1PNLL CAI.CAVHPNL1 Contains panel skeletons.
INT1MSGL CAI.CAVHMSG0 Contains messages.
INT1PROF userid.PROFLIB Contains profile members used by the
debugger to store user preferences.
INT1OPTS n/a Contains batch link options and control
information.
(Optional DDNAMEs)
INT1CLIB CAI.CAVHSAMP Contains INCLUDE members.
INT1CLOG (SYSOUT) Log output from the debugger.
INT1REPT (SYSOUT) Report output from the HIST and XSUM
commands.
Batch Link Options
The following table describes the batch link options that you can specify in the INT1OPTS file for job steps selected for
debugging.
Keyword Description
AUTH Specifies the USERID that is authorized to debug this application.
BYPASS Use this option to prevent the batch link engine from stopping for
input at the Monitor Control panel, the Initial Intercept panel, or
both.
Specify BYPASS=MONITOR to prevent the batch link engine from


both.
Specify BYPASS=MONITOR to prevent the batch link engine from
stopping at the Monitor Control panel unless an error is detected.
The dynamic symbolic support feature is not supported when
BYAPSS=MONITOR is specified in conjunction with PGM and
PROTSYM options.
Specify BYPASS=INITIAL to prevent the batch link engine from
stopping at the initial Intercept panel.
 770


InterTest™ and SymDump ® 11.0
DB2SP Use this option to indicate that the application you are debugging
is a DB2 stored procedure.
EXEC* Specifies the name of the application's main program. For most
batch job steps, this is the name which is replaced by CAMRBL01
in the PGM= parameter of the // EXEC statement. For some
special environments such as DB2, see Batch Link Special
Considerations.
ICMDS Indicates the member in your INT1CLIB DD that includes
application commands to be executed at the initial intercept.
If this command is used in conjunction with BYPASS(INITIAL),
these commands are not executed until a breakpoint is reached.
If you would like to bypass the initial intercept and would also like
a set of commands to be executed at the initial intercept, do not
use BYPASS(INITIAL). Instead, have GO as the last command
executed at the initial intercept.
IDLE=nn Use the IDLE command force a debugging session to time out if
it is idle for a specified amount of time.  "nn" is the number of wall
clock minutes that the debugging session will be allowed to sit
idle before being timed out. When a time out occurs, WTOs will
be issued which indicate that the timer threshold was exceeded
and the debugging session will end.  If this is not an IMSDC or
a DB2SP debugging session, the jobstep will also abend with a
U0999 abend.
IMSDC Use this option to indicate that the application you are debugging
is an online IMS application.
LOOP Specifies the interval in seconds that a batch link job step is
permitted to execute between responses from a terminal. If this
interval is exceeded, the debugger cancels the batch link job step.


interval is exceeded, the debugger cancels the batch link job step.
PGM Use the PGM option to specify which programs are to be
debugged during the batch link session. Values specified for this
option are used to complete the PROGRAM fields on the Monitor
Control panel for the batch link session. You can specify only one
program as a value, but the PGM option can be repeated up to
30 times per job step. If there are no PGM values specified in
INT1OPTS, all of the symbolic information is retrieved from the
profile member identified by the PROFILE option.
However, if you specify PGM values in INT1OPTS, then no values
are retrieved from the profile.
If specified in conjunction with BYPASS=MONITOR and
PROTSYM option, dynamic symbolic support is not supported.
PROFILE Specifies the name of the profile member that should be used by
the debugging engine. You can use a unique profile member for
each batch link job or step if desired, or specify your own user ID
to use your personal profile member. If not specified, the default is
the user ID used to submit the job.
PROTSYM Use the PROTSYM option to specify the file that contains the
symbolic information for the programs you want to debug. You can
specify only one PROTSYM file as a value, but the PROTSYM
option can be repeated up to seven times.
If the PGM option has not been specified, the PROTSYM option is
ignored.
If specified in conjunction with BYPASS=MONITOR and PGM
option, dynamic symbolic support is not supported.
 771


InterTest™ and SymDump ® 11.0
NOTE
An asterisk (*) next to a keyword indicates that the option is required on each selected step.
Specify options using the syntax:
 keyword=value

You can specify more than one option per line if desired, separating the options by a space or a comma.
DB2 and IMS Schedule Menu
Option 4 of the Batch Link Option Menu displays the DB2 and IMS Schedule Menu panel.
DISPLAY
Displays a list of existing DB2 or IMS schedules. Specify DB2 or IMS in the Schedule Monitoring for field when
you use this option.
NOTE
You can also use these lists to The Batch Link Schedule Change Panel or delete entries from the
existing schedule.
ADD
Allows adding a DB2 SP or IMS/DC schedule. Specify DB2 or IMS in the Schedule Monitoring for field when you
use this option.
IMPORT
Enables importing a predefined set of schedules (DB2 SPS and IMS/DC) from an external data set.
EXPORT
Enables exporting all schedules (DB2 SPS and IMS/DC) to an external data set.
Sharing Schedules between LPARs in a SYSPLEX
Scheduling is not limited to the LPAR you are currently logged on to. You can:
•Add an IMS / DB2 schedule on one LPAR which is then available on all LPARs.
•Change an IMS / DB2 schedule on one LPAR, the change propagates to all LPARs.
•Delete an IMS / DB2 schedule from one LPAR which is then deleted on all LPARs.
•Trigger an IMS /DB2 schedule and select it for debugging from any LPAR.
•Use the IMPORT and EXPORT functions for all scheduled items available on the LPARs within the SYSPLEX.
NOTE
For more information, see Configure Batch Link and Sysplex.


NOTE
For more information, see Configure Batch Link and Sysplex.
Batch Link Schedule Display Panel
Based on the database type selected in the Schedule Options panel, the following active schedule entries are displayed:
--------------- CA InterTest Batch DB2 SPS Schedule Maintenance --------------
COMMAND ===>                                                  SCROLL ===> CUR
   COMMAND      : A - ADD a new entry to Schedule.
   LINE COMMANDS: D - DELETE selected entry. C - CHANGE selected entry
------------------------------------------------------------------------------
CMD    REGION/JOBNAME   PROGRAM       TYPE     ONE TIME   USER       TRANSACTION
     **************************** TOP OF DATA *********************************
       BIMNTH01         ASSET*        DB2      YES
       BIMNTH01         SALES*        DB2      YES
       WKLYPAY          TIMEATTN      DB2      YES
 772


InterTest™ and SymDump ® 11.0
       WKLYPAY          FCIA          DB2      YES
       WKLYPAY          FEDW2         DB2      YES
       WKLYPAY          STATEW2       DB2      YES
       WKLYPAY          CASHFLOW      DB2      YES
       QTRLY*           GL001         DB2      YES
       QTRYL*           ASSET001      DB2      YES
       QTRLY*           SALES001      DB2      YES
       QTRLY*           INVNTROY      DB2      YES
       QTRLY*           CHAININV      DB2      YES
       QTRLY*           WHAREHSE      DB2      YES
       QTRLY070         DSTRUTON      DB2      YES
     *************************** BOTTOM OF DATA *******************************
The Batch Link IMS/DC Schedule Display panel displays IMS/DC on the first line of the panel, and IMS under the TYPE
column. The rest of the display is similar to the DB2 SPS display.
--------------- CA InterTest™ IMS/DC  Schedule Maintenance --------------
COMMAND ===>                                                  SCROLL ===> CUR
   COMMAND      : A - ADD a new entry to Schedule.
   LINE COMMANDS: D - DELETE selected entry. C - CHANGE selected entry
------------------------------------------------------------------------------
CMD    REGION/JOBNAME   PROGRAM   TYPE   ONE TIME   USER       TRANSACTION
     **************************** TOP OF DATA *********************************
       BIMNTH01         ASSET*    IMS    YES        IMSUSER1   IMSTRANS
       BIMNTH01         SALES*    IMS    YES        USER2IMS   IMSTRX02
       WKLYPAY          TIMEATTN  IMS    YES        IMSU0003   IMST0003


WKLYPAY          FCIA      IMS    YES        MPPUSER4   MPPTRX04
       WKLYPAY          FEDW2     IMS    YES        USERIMS5   TESTTRAN
       WKLYPAY          STATEW2   IMS    YES        USERMPP6   TRANSMPP
     *************************** BOTTOM OF DATA *******************************
Batch Link Schedule Add Panel
Select option 2 from the Schedule Options panel or enter A on the Schedule Display panel. The Schedule Add panel
displays.
The Batch Link Schedule Add panel fields are described next:
Field Name Description
REGION/JOBNAME This is usually required for IMS/DC scheduling.
If program name selection is independent of region, job name, or
both, leave this field blank, otherwise specify a maximum of eight
character IMS region name or z/OS job name that is commonly
associated with the program name to be monitored. Use the entire
length of the field, including trailing blanks as selection criteria.
A trailing asterisk (*) denotes a generic name. Characters to the
left of the asterisk are used for selection. Thus ABC* matches any
name whose first three characters start with ABC.
An asterisk (*) as the first character of this field denotes that any
region/job name is considered a match.
 773


InterTest™ and SymDump ® 11.0
PROGRAM NAME This is a required field. Provide a maximum of eight-character
valid program name (DB2 SP name or IMS/DC name) you want
the application to monitor during your debugging session.
The entire length of the field, including trailing blanks is used as
selection criteria.
A trailing asterisk (*) denotes a generic name. Characters to the
left of the asterisk are used for selection. Thus ABC* matches any
name whose first three characters start with ABC.
An asterisk (*) as the first character of this field denotes that any
program name is considered a match.
ONE TIME SCHEDULE If this option is set to Y, yes, the entry is deleted from the schedule
upon selection for monitoring.
Change this to N, no, if you do not want the entry deleted after
selection.
Note that keeping the entry in the schedule means that the
product always monitors the named program in a debugging
session when all of the selection criteria are met.
DATABASE TYPE This field is automatically filled in based on the value you entered
in Schedule Monitoring for ==> of the Schedule Options panel.
USER ID This field is used for IMS/DC only. This is the user ID assigned
to the transaction submitted in the MPP region. If this value is
supplied, monitoring happens only if the specified user ID starts
the transaction.
TRANSACTION This field is the IMS transaction name used for IMS/DC only. A
trailing asterisk (*) denotes a generic name. Characters to the left
of the asterisk are used for selection. For example ABC* matches
any name whose first three characters start with ABC.
Batch Link Schedule Change Panel
To change displayed entries, enter C under the CMD column next to the entries you want to change:
--------------- CA InterTest Batch DB2 SPS Schedule Maintenance --------------


--------------- CA InterTest Batch DB2 SPS Schedule Maintenance --------------
COMMAND ===>                                                  SCROLL ===> CUR
   COMMAND      : A - ADD a new entry to Schedule.
   LINE COMMANDS: D - DELETE selected entry. C - CHANGE selected entry
------------------------------------------------------------------------------
CMD    REGION/JOBNAME   PROGRAM       TYPE     ONE TIME   USER       TRANSACTION
     **************************** TOP OF DATA *********************************
       BIMNTH01         ASSET*        DB2      YES
       BIMNTH01         SALES*        DB2      YES
C      WKLYPAY          TIMEATTN      DB2      YES
       WKLYPAY          FCIA          DB2      YES
       WKLYPAY          FEDW2         DB2      YES
       WKLYPAY          STATEW2       DB2      YES
       WKLYPAY          CASHFLOW      DB2      YES
C      QTRLY*           GL001         DB2      YES
C      QTRYL*           ASSET001      DB2      YES
       QTRLY*           SALES001      DB2      YES
       QTRLY*           INVNTROY      DB2      YES
       QTRLY*           CHAININV      DB2      YES
       QTRLY*           WHAREHSE      DB2      YES
       QTRLY070         DSTRUTON      DB2      YES
     *************************** BOTTOM OF DATA *******************************
 774


InterTest™ and SymDump ® 11.0
The Schedule Change panel displays once for each selection:
------------------ CA InterTest Batch DB2 SPS Schedule Change ----------------
                 CHANGE any field by overtyping the displayed value.
                 Press ENTER to accept the change, or END to cancel.
------------------------------------------------------------------------------
               REGION/JOBNAME     ====>  WKLYPAY
               PROGRAM NAME       ====>  TIMEATTN
               ONE TIME SCHEDULE  ====>  Y        (Y/N)
               DATABASE TYPE      ====>  DB2
               USER ID            ====>
               TRANSACTION        ====>
      PFkeys: HELP - Tutorial
               END  - Exit
After changing the schedule and pressing Enter, the Change panel for the next marked line, if any, is displayed. This
continues until all of the lines marked with C have been displayed for change.
After all the changes have been done, the system refreshes the Display panel to reflect the changes.
NOTE
Pressing the END key (PF3) only cancels the currently displayed change and any further Change panels
queued for display. For more information about the Change panel fields, see Batch Link Schedule Add Panel.
Batch Link Schedule Delete Action
To delete an entry, enter D under the CMD column next to the entry you want to delete and press Enter:
--------------- CA InterTest Batch DB2 SPS Schedule Maintenance --------------
COMMAND ===>                                                  SCROLL ===> CUR
   COMMAND      : A - ADD a new entry to Schedule.
   LINE COMMANDS: D - DELETE selected entry. C - CHANGE selected entry
------------------------------------------------------------------------------
CMD    REGION/JOBNAME   PROGRAM       TYPE     ONE TIME   USER       TRANSACTION
     **************************** TOP OF DATA *********************************
       BIMNTH01         ASSET*        DB2      YES


BIMNTH01         ASSET*        DB2      YES
       BIMNTH01         SALES*        DB2      YES
D      WKLYPAY          TIMEATTN      DB2      YES
       WKLYPAY          FCIA          DB2      YES
       WKLYPAY          FEDW2         DB2      YES
       WKLYPAY          STATEW2       DB2      YES
       WKLYPAY          CASHFLOW      DB2      YES
D      QTRLY*           GL001         DB2      YES
D      QTRYL*           ASSET001      DB2      YES
       QTRLY*           SALES001      DB2      YES
       QTRLY*           INVNTROY      DB2      YES
       QTRLY*           CHAININV      DB2      YES
       QTRLY*           WHAREHSE      DB2      YES
       QTRLY070         DSTRUTON      DB2      YES
     *************************** BOTTOM OF DATA *******************************
The system deletes all the marked entries and refreshes the display to reflect the deletion.
 775