You can display the Batch Link menu by selecting option 5 from the Primary Option Menu:
----------- CA InterTest™ Batch PRIMARY OPTION MENU ------------------ OPTION ===> Release - r8.5 1 Foreground - Test a Program in Foreground Level - SP00 2 Core - Display and Alter Virtual Storage Userid - USER01 3 Allocation - Allocations and JCL Conversion Time - 15:38:23 4 Map - Address Space Map Date(G) - 07/14/09 5 Batch - Batch Link Facility Date(J) - 05.195 U Utilities - Symbolic Utilities and Preferences X EXIT - Terminate the Session PFkeys: HELP - Tutorial END - Exit Copyright (C) 2009 CA. All rights reserved.
The Batch Link Option menu consists of four options:
------------- CA InterTest™ Batch BATCH LINK OPTION MENU ----------------------- OPTION ===> 1 JCL - Prepare/Submit JCL for Batch Link 2 Batch Link - Select an active batch job for testing 3 Edit JCL - Edit existing Batch Link JCL 4 Scheduling - DB2 SP, IMS/DC Scheduling Functions Batch Link Status ENABLED on SYS1 X EXIT - Return to CA InterTest™ Batch Primary Option Menu PFkeys: HELP - Tutorial END - Exit
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.
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.
Use this option to edit and submit existing batch link JCL.
Note: This option is only supported under ISPF.
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.
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: The batch link JCL conversion utility creates a new JCL member in the output destination of your choice.
---------------------- Batch Link JCL Conversion PANEL ------------------------ COMMAND ===> Enter JCL Library: Project ===> Library ===> Type ===> Member ===> Other Partitioned Data Set: Data Set Name ===> 'cai.caisrc' Volume Serial ===> (If Not Cataloged) Dataset Password ===> (If Password Protected) Enter L for Librarian, P for Panvalet or blank for PDS: ===>
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. |
|
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.
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.
After you identify the JCL library, use the Batch Link Conversion Options panel to specify options for the conversion.
---------------------- Batch Link Conversion Options -------------------------- COMMAND ===> JCL Conversion Proclibs: Proclib 1 ===> Proclib 2 ===> Proclib 3 ===> Proclib 4 ===> Proclib 5 ===> Proclib 6 ===> Proclib 7 ===> Preallocaed DD ===> Converted JCL: Output JCL Lib ===> Output Member ===> UNIT/CLASS Name ===> SYSDA (for temp JCL) Type ===> U (U, S, M or D) Batch Link Variables: Profile Library ===> 'CAI.PROFLIB' Profile Member ===> USER01 Enter additional Batch Link options for INT1OPTS: ===>
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 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. |
|
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. Note: If using a temporary file for the converted JCL, VIO must not be used. |
|
Type |
Indicates the class type for the converted JCL member. Specify one of the following types:
|
|
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 the Batch Link Options section. |
After you assign values to all of the necessary fields on the panel, press Enter to advance to the next panel.
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.
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.CAILIB 000005 // DD DISP=SHR,DSN=USER01.LOADLIB 000006 //SYSPRINT DD SYSOUT=* 000007 //SYSOUT DD SYSOUT=* 000008 //INT1OPTS DD * 000009 EXEC=CAMRCOBB, PROFILE=USER01 000010 /* 000011 //INT1PARM DD DISP=SHR,DSN=USER01.INTBATCH.CAISRC 000012 //INT1LOAD DD DISP=SHR,DSN=USER01.INTBATCH.CAILIB 000013 //INT1PNLL DD DISP=SHR,DSN=USER01.INTBATCH.CAIPNL1 000014 //INT1MSGL DD DISP=SHR,DSN=USER01.INTBATCH.CAIISPM 000015 //INT1PROF DD DISP=SHR,DSN=USER01.INTBATCH.PROFLIB 000016 //INT1CLIB DD DISP=SHR,DSN=USER01.INTBATCH.CAISRC 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:
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.
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=USER1.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=* // 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.
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 the chapter Debugging Commands.
----------------- CA InterTest™ Batch Batch Link Selection -------------------- COMMAND INPUT ===> SCROLL ===> PAGE * * * * * * * # Jobname Stepname Program Owner User Trans SYSID **************************** 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.
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 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:
-------------------- CA InterTest™ Batch SYSPLEX Sign on ----------------------- # Jobname Stepname Program Owner User Trans SYSID 5 JOB01A STEP1 TESTPGM USER01 TS001 ----------------------------------------------------------------- SIGN ON TO: ===> TS001 USERID: ===> USER01 PASSWORD: ===> -----------------------------------------------------------------
The following prerequisites apply to debugging a job on a foreign LPAR:
Note: For more information, see the Enable the SYSPLEX (Cross-LPAR) Debugging Feature section in the CA InterTest Batch Installation Guide.
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.
----------------------- Edit Batch Link JCL Panel ----------------------------- COMMAND ===> Enter JCL Library: Project ===> Library ===> Type ===> Member ===> Other Partitioned Data Set: Data Set Name ===> CNTL Volume Serial ===> (If Not Cataloged)
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. |
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.
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 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 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.CAISRC |
Contains the parameter members used by the batch debugger. |
|
INT1LOAD |
CAI.CAILIB |
Contains the product executables. |
|
INT1PNLL |
CAI.CAIPNL1 |
Contains panel skeletons. |
|
INT1MSGL |
CAI.CAIISPM |
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.CAISRC |
Contains INCLUDE members. |
|
INT1CLOG |
(SYSOUT) |
Log output from the debugger. |
|
INT1REPT |
(SYSOUT) |
Report output from the HIST and XSUM commands. |
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 stopping at the Monitor Control panel unless an error is detected. Note: 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. |
|
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 Special Considerations later. |
|
ICMDS |
Indicates the member in your INT1CLIB DD that includes application commands to be executed at the initial intercept. Note: 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. |
|
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. |
|
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. Note: 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. Note: If specified in conjunction with BYPASS=MONITOR and PGM option, dynamic symbolic support is not supported. |
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.
Option 4 of the Batch Link Option Menu displays the DB2 and IMS Schedule Menu panel:
--------------- CA InterTest™ Batch DB2 and IMS Schedule Menu ---------------- OPTION ===> Schedule Monitoring for ==> (DB2 or IMS) - Required for options 1 and 2. Available Options: 1 DISPLAY - Display DB2 or IMS Schedules 2 ADD - Add a DB2 SP or IMS/DC to the Schedule 3 IMPORT - Import DB2 or IMS Schedules from External Dataset 4 EXPORT - Export DB2 or IMS Schedules to External Dataset PFkeys: HELP - Tutorial END - Exit
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 change or delete entries from the existing schedule.
Allows adding a DB2 SP or IMS/DC schedule. Specify DB2 or IMS in the Schedule Monitoring for field when you use this option.
Enables importing a predefined set of schedules (DB2 SPS and IMS/DC) from an external data set.
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:
To use this functionality, ensure that:
Note: For more information, see the Enable the SYSPLEX (Cross-LPAR) Debugging Feature section in the CA InterTest Batch Installation Guide.
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 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 *******************************
Select option 2 from the Schedule Options panel or enter A on the Schedule Display panel. The following Schedule Add panel displays:
------------------ CA InterTest™ Batch DB2 SPS Schedule Add ------------------- To ADD a new schedule entry, fill in the blank fields. Press ENTER to accept the new entry, or END to cancel ------------------------------------------------------------------------------ REGION/JOBNAME ====> PROGRAM NAME ====> ONE TIME SCHEDULE ====> Y (Y/N) DATABASE TYPE ====> DB2 USER ID ====> TRANSACTION ====> PFkeys: HELP - Tutorial END - Exit
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. |
|
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. |
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 -------------- 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 *******************************
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 The Batch Link Schedule Add Panel section.
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 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.
When you select option 3 from the Schedule Options panel, the following Batch Link Schedule Import panel displays:
------------ CA InterTest™ Batch Link SCHEDULE IMPORT ------------------------- OPTION ===> Enter Dataset Name: Project ===> Library ===> Type ===> Member ===> Other Partitioned or Sequential Data Set: Data Set Name ===> Volume Serial ===> (If Not Cataloged) PFkeys: HELP - Tutorial END - Exit
The Batch Link Schedule Import panel fields are described next:
|
Field Name |
Description |
|---|---|
|
Project |
The high-level qualifier for the data set containing the schedule to be imported. |
|
Library |
The middle-level qualifier for the data set containing the schedule to be imported |
|
Type |
The lowest-level qualifier for the data set containing the schedule to be imported. |
|
Member |
The name of the member to be imported when the data set is partitioned. Leave this field blank for sequential files or to produce a member selection list for a PDS. |
|
Data Set Name |
If the import data set name does not conform to PROJECT.LIBRARY.TYPE, enter the name of the data set in this field. Use quotes for fully qualified names. If quotes are omitted, your ISPF prefix is used to form the high-level qualifier. |
|
Volume Serial |
If the data set is not catalogued, use this field to enter the VOLSER of the DASD volume on which the data set resides. |
Note that the DCB attributes of the IMPORT data set are RECFM=FB, LRECL=80, DSORG=PS or PO.
Alternatively you can run the schedule import function as a batch job. Use the following sample JCL to accomplish the task:
// JOB /*JOBPARM SYSAFF=xxxx //IMPORT EXEC PGM=CAMR40IP //STEPLIB DD DISP=SHR,DSN=CAI.CAILIB //INT1SKUT DD DISP=SHR,DSN=CAI.SCHEDULE.DATA(MEMBER)
Instead of doing a complete replacement of the schedule table, import can also perform an additive import when you code an execution parameter:
// JOB /*JOBPARM SYSAFF=xxxx //IMPORT EXEC PGM=CAMR40IP,PARM='ADD' //STEPLIB DD DISP=SHR,DSN=CAI.CAILIB //INT1SKUT DD DISP=SHR,DSN=CAI.SCHEDULE.DATA(MEMBER)
Entries are added based on slot availability and using the same first available rules.
The following code is return code from import operations:
RC = 0 successfully imported
RC = 4 schedule table does not exist
RC = 8 INT1SKUT DD statement missing.
When you select option 4 from the Schedule Options panel, the following Batch Link Schedule Export panel displays:
------------ CA InterTest™ Batch Link SCHEDULE EXPORT -------------------------- OPTION ===> Enter Dataset Name: Project ===> Library ===> Type ===> Member ===> Other Partitioned or Sequential Data Set: Data Set Name ===> Volume Serial ===> (If Not Cataloged) PFkeys: HELP - Tutorial END - Exit
See the Batch Link Schedule Import panel fields for a discussion of the various similarly named fields.
Note: Export creates a new PDS member if member name provided does not exist. If one does exist, it is overwritten.
Alternatively, you can run the schedule export function as a batch job. Use the following sample JCL to accomplish the task:
// JOB /*JOBPARM SYSAFF=xxxx //EXPORT EXEC PGM=CAMR40XP //STEPLIB DD DISP=SHR,DSN=CAI.CAILIB //INT1SKUT DD DISP=SHR,DSN=CAI.SCHEDULE.DATA(MEMBER)
The following code is return code from export operations:
RC = 0 successfully imported
RC = 4 schedule table does not exist
RC = 8 INT1SKUT DD statement missing.
|
Copyright © 2013 CA.
All rights reserved.
|
|