Task 2.11: Configuring Code Debug Batch Connect under CA-ROSCOE

The following people are required:

• Code Debug TSO and Code Debug IMS Installer
• CA-ROSCOE Installer.

If you are installing Code Debug TSO’s Batch Connect Support under ROSCOE for this release, ensure that any prerequisite installation steps have been completed (BMC AMI Enterprise Common Components, Code Debug TSO Batch Connect, etc.).

If you have already installed this release of Code Debug TSO’s Batch Connect Support under ROSCOE and are going to apply maintenance, start here and go to Task 2.11.4: Maintenance Steps.

The following JCL is supplied in the Code Debug TSO SLXTINST library:

• ROS001 - contains the unload process for the initial installation of this release of Code Debug TSO's Batch Connect Support under ROSCOE.
• ROS002 - contains the link edit process.
• ROS003 - contains the unload process for the maintenance of this release of Code Debug TSO’s Batch Connect Support under ROSCOE.

Task 2.11.1: Create CA-ROSCOE Library Members

Edit the SLXTINST library member ROS001 as described here (and in the sample JCL). This job uses RPFLIBS as input to the unload process.

1. Add a JOB card.
2. Change the generic high-level qualifier to your site's high-level qualifier for the Code Debug TSO and Code Debug IMS SLXTLOAD and SLXTINST libraries.
3. Verify the validity of the UNIT=SYSDA value and correct if necessary.
4. Change the generic high-level qualifier of YOUR.ROSCOE to your site's high-level qualifier for the ROSCOE libraries.
5. Change the key segment XPEDITER.MAINT to the key segment (XTO650) used at your site.
6. Submit the job. It should complete with a return code of 0.

After the successful completion of the ROS001 job, a system library defaults module must be established. This is a normal ROSCOE library member that contains a date record as its first line, followed by a line for each library default. This member must be called XBATSLIB. A sample is provided in the ROSCOE library that was created by ROS001.

The formats are as follows:

• The date record consists of the constant DATETIME in columns 1-8 and the date in columns 60-72 in the format:
  yyyyjjjhhmmss
  where yyyy=year, jjj=julian day, hh=hours, mm=minutes, and ss=seconds.

• Each subsequent line is the library type in columns 1-4 and DSN in columns 5 and up. The valid four-character types are as follows:
  • SPRC = system PROCLIB, maximum of 3
  • SDIO = system DDIO libraries, maximum of 3
  • SSWS = system site-wide script library, maximum of 1
  • SINC = system INCLUDE libraries, maximum of 3
  • XLOD = system Code Debug loadlib @
  • XOPT = system XOPTIONS library @
  • HELP = system Code Debug help library, maximum of 3.

A sample XBATSLIB is shown as follows:

SSWS (Site-Wide Script Library)

Any data set name specified in XBATSLIB will be concatenated first in the XINCLUDE allocation. This file will not appear on the user’s Setup screen for possible removal from the concatenation. Although this library may contain global common scripts, its main purpose is to hold the Site-Wide initial script member @@SITE@@, which will always be included at the beginning of a test session. Any initial script specified by the user will execute after the @@SITE@@ member. This can be used by your support staff to apply changes to the environments of the entire user community without requiring individuals to modify Setup profiles.

Task 2.11.2: Modifying the ROSCOE Programming Facility XBATCFG Member

After completing changes to the XBATSLIB member, make the following changes listed to ROSCOE Programming Facility (RPF) member XBATCFG shown here:

1. Replace RP with the PREFIX used when you installed Code Debug TSO’s Batch Connect Support under ROSCOE.
2. Replace VIO with the default esoteric unit used for work data sets. If VIO is available as an esoteric unit at your site, it is recommended that you do not change this setting.
3. Replace N with a Y (Yes) if you have purchased Code Coverage. Otherwise, leave as N.

Task 2.11.3: Batch Connect Customization and Link

1. As installed, Code Debug TSO’s Batch Connect Support under ROSCOE uses the same Batch Connect security algorithm as it does under TSO. That is, the name of the batch job, minus the last character, must be the same as your ROSCOE ID (signon key). If this is not compatible with your site’s security system, you can either rewrite the Batch Connect security exit, or deactivate it by modifying the CMSC PARMLIB member (specifying a CTLSEC value of NO).
2. Edit SLXTINST library member ROS002 as described here (and in the sample JCL):
   1. Add a JOB card.
   2. Change the generic high-level qualifier to your site’s high-level qualifier for the Code Debug TSO and Code Debug IMS SLXTLOAD and ROSBAT.LOADLIB libraries.
   3. Verify the validity of the UNIT=SYSDA value and correct if necessary.
   4. If required, replace the VOL=SER=DDDDDD statement with a valid VOL=SER. Otherwise, remove the statement.
   5. Change the generic high-level qualifier of YOUR.ROSCOE to your site’s high-level qualifier for the ROSCOE libraries.
   6. Change the key segment XPEDITER.MAINT to the key segment (XTO650) used at your site.
   7. Submit the job. It should complete with a return code of 0.
3. The data set CPWR.XT.ROSBAT.LOADLIB is a separate LOADLIB containing the required Code Debug TSO modules. Since it makes use of the CA-ROSCOE-provided API service, it requires that the module ROETSAPI be included in the link-edit.
4. Concatenate this LOADLIB with DDname ETSOLIB in your ROSCOE startup JCL.
5. If you are currently using Xpediter/ROS 2.0, concatenate the ROSBAT.LOADLIB before the Xpediter/ROS LOADLIB. In addition, make the following change to line 1300 in RPF XPEDROS:
   LET P25 ='CPWR.XT.ROSBAT.LOADLIB'

6. Add the ADSIS086 and ADSIS300 programs to the ROSCOE ETSO EPL. This is usually saved as the member RO.ETSOPGMS. Ensure that the EPL remains in alphabetical order. Sample EPL entries for ROSCOE 6.0 and above are:

   VERSION2
   NAME MAX MAX.  MAX. MAX. MAX.   MAX.  D M C
        USR SLI-  TOT. VAR. TOT.   VAR.  U O P
            CES   GETM GETM GETM. GETM.  M D
                  AM24 AM24 AM31  AM31  P E
   *------- --- ---- ------ ------ ------ ------ - - -- ----------
   ADSIS086 999 9000 04096 000512 004096 000512 D N CP DIAGNOSTIC
   ADSIS300 999 9000 004096 000512 004096 000512 D N CP BATCH CONN
7. Verify that the following recommended minimum values are set in your ROSCOE SYSIN parms:
   AWSLIM=6 (or increase your current setting by 4)
   ARRAYMAX=255 (required)
8. Cycle the ROSCOE region to initialize the changes.

Task 2.11.4:Maintenance Steps

Previously, the RPFLIBS member of the SLXTINST library was used for the initial installation of Code Debug TSO’s Batch Connect Support under ROSCOE—and for any maintenance that was applied to the ROSCOE components. The process of applying maintenance would overlay the SLXTINST library members XBATSLIB and XBATCFG, forcing the product installer to take precautions to avoid overlaying those members.

Now, the RPFLIBS member of the SLXTINST library will consist of the initial installation components. The RPFMNT member of the SLXTINST library will have the most recent available maintenance applied to the ROSCOE components, minus the XBATSLIB and XBATCFG members, so no overlaying will occur.

1. Edit the SLXTINST library member ROS003 as described here (and in the sample JCL). This job uses RPFMNT as input to the unload process.
   1. Add a JOB card.
   2. Change the generic high-level qualifier to your site’s high-level qualifier for the Code Debug TSO SLXTLOAD and SLXTINST libraries.
   3. Verify the validity of the UNIT=SYSDA value and correct if necessary.
   4. Change the generic high-level qualifier of YOUR.ROSCOE to your site’s high-level qualifier for the ROSCOE libraries used at your site.
   5. Change the key segment XPEDITER.MAINT to the key segment (XTO650) used at your site.
   6. Submit the job. It should complete with a return code of 0.
2. Edit SLXTINST library member ROS002 as described here(and in the sample JCL):
   1. Add a JOB card.
   2. Change the generic high-level qualifier to your site’s high-level qualifier for the Code Debug TSO and Code Debug IMS SLXTLOAD and ROSBAT.LOADLIB libraries.
   3. Verify the validity of the UNIT=SYSDA value and correct if necessary.
   4. If required, replace the VOL=SER=DDDDDD statement with a valid VOL=SER. Otherwise, remove the statement.
   5. Change the generic high-level qualifier of YOUR.ROSCOE to your site’s high-level qualifier for the ROSCOE libraries.
   6. Change the key segment XPEDITER.MAINT to the key segment (XTO650) used at your site.
   7. Submit the job. It should complete with a return code of 0.