Milestone 5: Configuring Code Debug TSO and Code Debug IMS — Upgrade
This section will guide you through configuration of an upgrade to Code Debug TSO and Code Debug IMS 17.02.
Roles Involved
The following people are required for this milestone:
- Code Debug TSO and Code Debug IMS Installer
- z/OS System Programmer.
Tasks
Complete the following tasks to configure an upgrade of Code Debug TSO and Code Debug IMS.
Task 5.1 Customize XTUPDATE Macro
Code Debug TSO and Code Debug IMS Installer is required for this task.
XTUPDATE is an ISPF edit macro that can be used to automate the entry of site-specific JCL parameters. Using this macro saves you from having to repeatedly type in the same information and ensures your JCL parameters are always entered correctly.
Task 5.1.1 Copy SLXTINST(XTUPDATE) into a Library in Your SYSPROC Concatenation
This CLIST library must be allocated to your ISPF session.
Task 5.1.2 Edit the XTUPDATE Macro
Instructions necessary to customize the macro are found in the member SLXTINST(XTUPDATE). All lines to be changed are marked with <==.
Task 5.2 Configure XPLIBDEF and XPCGDSN
Code Debug TSO and Code Debug IMS Installer is required for this task.
The CLIST XPLIBDEF is used to allocate the required Code Debug TSO environment and to invoke the product.
The CLIST library must be allocated to your ISPF session.
Task 5.2.1 Copy SLXTINST(XPLIBDEF) and (XPCGDSN)
Copy the two CLISTs into a data set that is either part of the SYSPROC concatenation or that is activated with an ALTLIB command.
Task 5.2.2 Edit the XPLIBDEF CLIST
By default, the XPLIBDEF CLIST will use the Simple Deploy method to allocate the data set names specified in the CSMC PARMLIB DDSNnnnn member (DDSN00 by default). If you are not using the default member, make sure to point to the DDSNnnnn member name by setting the DDSNSFX keyword to the one- to four-character PARMLIB member suffix.
For example, to point to PARMLIB member DDSNCPWR, use:
DDSNSFX(CPWR)In addition, the primary CMSC will be used by default. If you are not using the default CMSC, specify the CMSC to use by setting the CMSC keyword to the one- to four-character CMSC ID.
For example, to point to CMSC subsystem TEST, use:
CMSC(TEST)This CLIST can alternately use High-Level Qualifiers (HLQ) to allocate the various products it references. The following table identifies the product and its associated “node”.
Product Node Values
Product | Node | Initial Value |
|---|---|---|
Code Debug TSO | XTNODE | PARMLIB |
Common Shared Services | CSSNODE | PARMLIB |
Xchange | XGNODE | PARMLIB |
File-AID | FANODE | PARMLIB |
Code Coverage | CCNODE | PARMLIB |
Code Debug CICS | XDNODE | PARMLIB |
See the comments in the XPLIBDEF CLIST for further information.
Task 5.3 Configure the XOPTIONS File
Code Debug TSO and Code Debug IMS Installer is required for this task.
The XOPTIONS data set is used during COBOL enhanced FIND processing. The data set name will be used in the next task.
Task 5.3.1 Reuse Previous XOPTIONS File
You may use the same XOPTIONS file for multiple releases of Code Debug TSO and Code Debug TSO.
- The KEYWORD=value pair was created properly if you used SLXTINST(JCLCRPRM) as the foundation for the CMSC PARMLIB member.
- If not, to use the same file as the prior Code Debug TSO release, code this pair as follows:
OPTIONS_DATA_SET='XOPTIONS_dataset_name_noted_earlier'
Task 5.3.2 Create a New XOPTIONS File
- Use the XTUPDATE macro to configure SLXTINST(JCL015).
- Submit the JCL. It should end with return code 0.
Task 5.3.3 Code the XOPTIONS KEYWORD=Value Pair
In Implement the CMSC PARMLIB as follows, the XOPTIONS data set name should be specified by coding the following pair:
OPTIONS_DATA_SET='your_newly_created_XOPTIONS_file'
Task 5.4 Implement the CMSC PARMLIB
Code Debug TSO and Code Debug IMS Installer is required for this task.
Starting with release 17.02, BMC AMI mainframe products, including Code Debug TSO and Code Debug IMS, use parameter libraries (PARMLIBs) in conjunction with the BMC AMI Common Mainframe Services Controller (CMSC) to configure each product as well as common components. The CMSC was installed as part of the BMC AMI Enterprise Common Components installation.
In this task, you will implement the CMSC PARMLIB for Code Debug TSO and Code Debug IMS. This consists of creating default members and updating the CMSC with them. The default members are suffixed with 00 and should contain the values you want for all LPARs on which Code Debug TSO and Code Debug IMS and Code Coverage are installed.
Task 5.4.1 Migrate Your Code Debug TSO Defaults from a Prior Release
SLXTINST(JCLCRPRM) contains sample JCL as well as instructions for executing the utility.
This utility will extract Run-Time Parameter specifications from a prior release’s load module ADSRA093, and/or ISPF Installation Parameter specifications from a prior release’s Code Debug TSO ISPF table SLXTTABL.
- Use the XTUPDATE macro to configure SLXTINST(JCLCRPRM)
- Follow the instructions in the JCL to complete customization.
- Submit the JCL. It should end with return code 0.
Task 5.4.2 Create a PARMLIB Member
This task describes the Run-Time Parameters and ISPF Installation Parameters that are eligible to be configured based on the requirements at your site.
Any KEYWORD=value parameter specification omitted from a PARMLIB member will cause Code Debug TSO to use the Code Debug TSO-delivered default value for that parameter.
Copy the PARMOUT output from the JCLCRPRM job to CMSC PARMLIB member XTSO00
- Follow the instructions within the XTSO00 member to make all required changes.
Execute the CLIST XPLIBDEF with the INSTALL option (XPLIBDEF INSTALL). The screen shown in the following figure is displayed.
Installation Defaults Screen
COMPUWARE INSTALL --------- INSTALLATION DEFAULTS ---------------------------
COMMAND ===>
This process will commit the changes made to the CMSC PARMLIB member into
member XPTDFLTS in the Code Debug TSO Table Library. A CMSC "REFRESH" will be
attempted before the COMMIT action is performed. Member XPTBACK0 will be
used to save the previous values.
Enter the DSNAME of the Table Library to be updated:
Output ===> 'ACMJET0.XT170.TENU'
To copy existing installation defaults, enter the DSNAME of the old
Table Library (optional):
Input ===> 'ACMJET0.XT165.TENU'
Enter the suffix of PARMLIB member (XTSOssss) to be committed:
Suffix ===> (The default is used if no override is entered)
Action ===> COMMIT (Type COMMIT and press Enter to process)
Should Dataset Names in PARMLIB be validated? YES- Point to your new SLXTTABL data set.
- Point to the previous version’s SLXTTABL data set.
- Specify an ACTION of COMMIT.
- If you want the data set names specified in the XTSO00 PARMLIB member to be validated, specify YES to that question.
- Press Enter. The Roll Forward screen is displayed.
Type Y in the Continue and roll forward? field and press Enter.
- If there was no error message, a validation report will be displayed. Follow the instructions in the report.
Use SDSF, IOF, EJES or whatever JES viewer is used by your site to check the CMSC address space’s FDBDLOG (Figure CMSC Address Space FDBDLOG) to determine whether anything went wrong
CMSC Address Space FDBDLOG
SDSF JOB DATA SET DISPLAY - JOB CMSCAC01 (S0935052) DATA SET DISPLAYED
COMMAND INPUT ===> SCROLL ===> CSR
PREFIX=CMSCAC01 DEST=(ALL) OWNER=* SYSNAME=*
NP DDNAME StepName ProcStep DSID Owner C Dest Rec-Cnt Page-Cnt Byte-Cnt CC
JESJCLIN 1 CMSCCW01 A 2 127 1
JESMSGLG JES2 2 CMSCCW01 A 2 1 135 1
JESJCL JES2 3 CMSCCW01 A 34 1,760 1
JESYSMSG JES2 4 CMSCCW01 A 3,133 156,941 1
$INTTEXT JES2 5 CMSCCW01 A 14 821 1
EVENTLOG JES2 8 CMSCCW01 A 0 1
S FDBDLOG CMSCCW01 101 CMSCCW01 A 6,940 658,776 1
LMCPRINT CMSCCW01 102 CMSCCW01 A 6,464 108 649,659 1
LMZPRINT CMSCCW01 103 CMSCCW01 A 12,774 213 1M 1Return to the validation report and scroll to the bottom (Figure Validation Report with No Errors) to determine whether there were any errors. If there were no errors, NONE is indicated. If there were errors, fix them and start over.
Validation Report with No Errors
----------------------------------------------------------------------------------------------------------------------------
BROWSE SYS17158.T111305.RA000.ACMJET0.R0160298 Line 0000000654 Col 001 132
Command ===> Scroll ===> CSR
KEYWORD: DIRECT_JCL_PROC_EXPANSION_CLASS
VALUE: (I,PROC02)
KEYWORD: DIRECT_JCL_PROC_EXPANSION_CLASS
VALUE: (M,PROC02)
KEYWORD: DIRECT_JCL_PROC_EXPANSION_DSNAME
VALUE: (IATPLBST,'SYS1.PROCLIB')
------------------------------------------------------------------------------------------------------------------------
THE FOLLOWING DB2 PROC KEYWORDS WERE REPLACED
KEYWORD: DB2SP_SEARCH_PROC_DSNAME
VALUE: 'XT.SP.PROCLIB'
------------------------------------------------------------------------------------------------------------------------
NUMBER OF ERRORS THAT WERE DETECTED: NONE
INSTALLATION DEFAULTS CAN BE SAVED INTO 'ACMJET0.XT170.TENU'
NUMBER OF NEW VALUES TO BE COMMITTED TO THE TABLE: 116
************************************************** Bottom of Data ********************************************************- Press End, then press Enter (or press PF3).
- Press Enter to update the Installation Defaults. A message will be displayed saying that the Installation Defaults were saved.
Task 5.5 Configure Multi-Batch Support
The following people are required for this task:
- Code Debug TSO and Code Debug IMS
- Installer
- z/OS System Programmer.
Install the Code Debug TSO Multi-Batch Facility (MBF). MBF is required for Workbench for Eclipse.
Task 5.5.1 Create the Multi-Batch Staging File
Code Debug TSO and Code Debug IMS Installer is required for this task.
- Use the XTUPDATE macro to configure SLXTINST(JCLCREMB).
- Submit the JCL. It should end with return code 0.
Task 5.5.2 Activate Multi-Batch
Code Debug TSO and Code Debug IMS Installer is required for this task.
- Use the XTUPDATE macro to configure SLXTINST(JCLACTMB).
- Submit the JCL. It should end with return code 0.
Task 5.5.3 Configure z/OS to Start Multi-Batch After IPL
z/OS System Programmer is required for this task.
JCLACTMB must be run after each IPL to re-enable the Multi-Batch Facility. If you want JCLACTMB to run automatically during z/OS startup, perform the following:
1. Copy SLXTINST(JCLACTMB) into the appropriate library in your system PROCLIB concatenation.
2. Modify JCLACTMB to meet your site’s standards for a z/OS startup procedure, replacing the JOB statement with a PROC statement.
3. Configure your z/OS system to start JCLACTMB at IPL time by either:
- Updating your z/OS PARMLIB member COMMNDxx.
- Configuring your automated operations application.
An example of the START command is provided in SLXTINST(COMMNDxx).
Restrictions
When Code Debug TSO converts Db2 Batch JCL for use in Batch Connect testing, it moves the data set specified by the LIBRARY(dataset_name) keyword to the STEPLIB concatenation. Since Multi-Batch does not alter the JCL, the LIBRARY keyword of the DSN command (used in Db2 Batch programs that use IKJEFT01 to establish a connection to Db2) is not supported. If your program is in the library indicated by the LIB keyword, that library must be specified in the JCL’s STEPLIB or in the Code Debug SETUP load library list. In addition, the Db2 SDSNLOAD library must be specified in the JCL’s STEPLIB or in the Code Debug SETUP load library list.
Task 5.5.4 Configure the Multi-Batch Communication Task
Task 5.6 Perform Initial Verification
Code Debug TSO and Code Debug IMS Installer is required for this task:
Task 5.6.1 Verify Libraries
This initial verification lets you confirm that your Code Debug libraries are current before proceeding with other verifications.
- Execute the following TSO command:
EX 'dataset(XPLIBDEF)'
where data set is the fully qualified data set name chosen in Copy SLXTINST(XPLIBDEF) and (XPCGDSN). - From the Code Debug TSO Primary Menu, type XENV LEVELS in the OPTION field and press Enter. A screen similar to figure XENV Screen is displayed. Library versions should be those just installed.
XENV Screen
LIBRARY RELEASE LEVELS:
CODE DEBUG CLIST ................ 17.02
CODE DEBUG LOADLIB .............. 17.02.00
CODE DEBUG MSGS ................. 17.02
CODE DEBUG PANELS ............... 17.02
CODE DEBUG SKELS ................ 17.02
XCODE DEBUG TABLES / XPTDFLTS ....17.02 / 17.02
CSS LOADLIB ................... 17.02.00
CSS LOADLIB (LP COMPONENT) .... 17.02.00
CSS LOADLIB (DDIO COMPONENT) .. 17.02.00
******************************** Bottom of Data *******************************
Task 5.6.2 Verify Base Installation
Installation Verification Programs (IVPs)
The base product has four sets of IVP programs, one for each programming language supported by Code Debug TSO:
Base Code Debug TSO and Code Debug IMS IVPs
Language | IVPs |
|---|---|
COBOL | TRITST, TRIRPT, and TRIMAIN (TRIMAIN calls TRITST and TRIRPT) |
PL/I | TRITSTP, TRIRPTP, and TRIMAINP (TRIMAINP calls TRITSTP and TRIRPTP) |
Assembler | TRITSTA, TRIRPTA, and TRIMAINA (TRIMAINA calls TRITSTA and TRIRPTA) |
C | TRITSTC, TRIRPTC, and TRIMAINC (TRIMAINC calls TRITSTC and TRIRPTC) |
The programs are contained in the SLXTSAMP library. Use the specific Language Processor (LP) to compile or assemble the sample programs in the listed order (for example, TRITST*, then TRIRPT*, followed by TRIMAIN*). Some main routines statically link to subroutines higher in the list. See to the BMC AMI Common Shared Services User/Reference Guide for information on using the correct LP (COBOL, PL/I, Assembler, or C).
- The SYSLMOD output from these compiles should not be directed to the Code Debug TSO LOADLIB library. Instead direct the SYSLMOD output from your linkedit step to a test data set available to your application programmers for training sessions. For example, you could create a data set named hlq.TRAINLIB or hlq.SLXTIVP.
- To verify that the compile was successful and that a source listing member was created, check the listing under the DDNAME CWPERRM for a message similar to the following:
LISTINGS SUCCESSFULLY WRITTEN OUT TO DDIO
Run the IVPs to Initiate Verification Test Sessions
For each step, the program name or JCL referenced is specific to the language.
Verification Test Session IVPs
Language | Program | SAMPLIB JCL Member |
|---|---|---|
COBOL | TRIMAIN | TRIJCL |
PL/I | TRIMAINP | TRIJCLP |
Assembler | TRIMAINA | TRIJCLA |
C | TRIMAINC | TRIJCLC |
- Select 2 (TSO) from the Code Debug TSO Primary Menu.
Select 1 (STANDARD) from the Environments Menu.
- Enter SETUP from the Standard test screen.
- Select 1 (LOADLIBS) from the Setup Menu.
- On the Load Module Libraries screen, specify the application load library that contains the language-specific IVP load module. Also specify your Language Environment (LE) run-time library (usually CEE.SCEERUN). Press Enter.
- Enter END (or press PF3) to return to the Standard screen.
- Specify the language specific program from the table above on the Program ===> line.
- The SLXTSAMP library contains sample JCL that can be used to run the IVP. On the File List/JCL Member ===> line, enter the language specific data set/member name from the table above (for example, 'hlq.SLXTSAMP(TRIJCL)' for COBOL).
- Press Enter to begin the Code Debug TSO debugging session. The message area contains the lines Allocating User Datasets, then Allocating CODE DEBUG TSO Datasets. On a blank screen, the message Entering CODE DEBUG TSO Test Environment is displayed along with information about the test. Then the source for the applicable TRIMAIN program is displayed.
- Type GO 1 on the COMMAND line and press Enter.
The execution arrow will be on the next statement. The execution status message indicates that you are BEFORE program-name:line-number. - Press PF12 (GO). The Triangle Report is written to the screen.
- Press Enter until you return to the Source screen with a TEST COMPLETED message, indicating that your program executed successfully.
- Press PF4 (EXIT) to exit the test session.
Task 5.7 Additional Upgrade Configuration
Because you are upgrading from a prior release to a new release of Code Debug TSO and Code Debug IMS, only some of the Milestones and tasks necessary for a new installation need be examined.
Generally, a simple upgrade to a new release of Code Debug TSO and Code Debug IMS would not require any of these tasks. The conditions that could require you to perform a task are defined as follows.
To Support Workbench for Eclipse
Each release of Code Debug TSO creates an entry for Workbench for Eclipse in the CSPF (Common Shared Profile Facility). Even if you have configured a prior release of Code Debug TSO and Code Debug IMS to work with Workbench for Eclipse, you will need to perform Configure the CSS Shared Profile Facility (CSPF) data set.
To Use Code Debug TSO’s Batch Connect Feature
If the installer modified the value of PARMLIB keywords CT2VTPFX, CT2VTBEG, or CT2VTN2S, you will need to perform the tasks in Milestone 7: Configure Batch Connect Support.
To Use IMS/DB Support
If you have not previously configured this feature and want to use it, you will need to perform the tasks in Milestone 8: Configure IMS/DB Support.
Licensed for Code Debug IMS (IMS/DC Support)
If you have newly purchased this license, to configure it, you will need to perform the tasks in Milestone 9: Configure IMS/DC Support.
Licensed for Code Debug Db2 Stored Procedure Support
If you have newly purchased this license, to configure it, you will need to perform the tasks in Milestone 10: Configure Db2 Stored Procedure Support.
To Use Code Debug TSO with IBM’s BTS (Batch Terminal Simulator)
If you have not previously configured this feature and want to use it, you will need to perform the tasks in Milestone 11: Configure BTS Support.
To Use High-Performance Breakpoint Processing Methodology
If you have not previously configured this feature and want to use it, you will need to perform the tasks in Milestone 12: Enable High-Performance Breakpointing.
Licensed for the Code Debug for Db2 Extension
If you have newly purchased this license, see to the Code Debug TSO and Code Debug IMS Advanced Configuration Guide for more information.
To Utilize Code Debug TSO with CA-ROSCOE
If you have not previously configured this feature and want to use it, see to the Code Debug TSO and Code Debug IMS Advanced Configuration Guide for more information.