Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Milestone 7: Configuring Batch Connect support

This milestone contains details regarding configuration of the Code Debug TSO and Code Debug IMS Batch Connect facility to suit your site’s needs.

Warning

If Batch Connect was installed with a previous Code Debug release, you do not need to perform this milestone unless you are making modifications to the PARMLIB keywords CT2VTPFX, CT2VTBEG, or CT2VTN2S. These keywords specify the VTAM ACB Prefix (CT2VTPFX), the beginning VTAM ACB number (CT2VTBEG), and the number of “pairs” of VTAM ACB nodes (CT2VTN2S). (For example, CT2VTN2S=7 indicates seven pairs of nodes).

If your site:

  • Is not using—and does not plan to use—the Batch Connect facility, or
  • Installed Batch Connect with a previous Code Debug release and did not modify PARMLIB keywords CT2VTPFX, CT2VTBEG, or CT2VTN2S for this release,

go ahead to Milestone-8-Configuring-IMS-DB-support.

Roles Involved

The following people are required for this milestone:

Important

VTAM Administrator

Code Debug TSO and Code Debug IMS Installer.


Tasks

Complete the following tasks to configure Batch Connect support.

Task 7.1 Define VTAM APPLIDS

The following person is required for this task:

Important

VTAM Administrator

If you intend to use the Code Debug TSO Batch Connect facility or Workbench for Eclipseyou must define a pool of VTAM APPLIDs for use by Code Debug TSO. There must be one APPLID for each batch job using the Batch Connect facility, and there must also be an APPLID for each TSO session that is connected to a Batch Connect job. Therefore, there will be two APPLIDs for each expected active and running Code Debug batch job. Terminals that are connected directly to the batch job do not require an additional APPLID

Code Debug TSO requires that the VTAM APPLID pool adhere to the following naming conventions:

  • Each ACBNAME must be a valid VTAM ACBNAME.
  • Each ACBNAME must be eight characters.
    • The first five characters are treated as a prefix for a range.
    • The last three characters are the range. These characters must be numeric (0 through 9) and occur in sequential order.

The default prefix is XPDTR. The default range for the VTAM ACBNAME pool is XPDTR000 through XPDTR011.

Important

If you must use a different VTAM ACBNAME prefix or range due to local naming conventions, you must also change PARMLIB to tailor the site defaults. PARMLIB keyword CT2VTPFX specifies the ACBNAME prefix (default XPDTR), keyword CT2VTBEG (default 000) specifies the value at the end of the first ACBNAME, and keyword CT2VTN2S (default 6) specifies the high-pair number the last ACBNAME must end with.

The following example illustrates how to define the pool of VTAM APPLIDs to VTAM. This example can be found in SLXTSAMP(XPDTR). These entries can be added to an existing member in VTAMLST or a new member can be created. Be sure that the member is activated either by manual operator commands or by adding the member name in VTAMLST(ATCCONxx).

Defining VTAM APPLIDs for Batch Connect

H01AXPD VBUILD TYPE=APPL
*
A01CS000 APPL ACBNAME=XPDTR000,                                        X
PRTCT=XPED,                                                            X
MODETAB=ISTINCLM,                                                      X
DLOGMOD=NSX32702,                                                      X
EAS=1
*
A01CS001 APPL ACBNAME=XPDTR001,                                        X
PRTCT=XPED,                                                            X
MODETAB=ISTINCLM,                                                      X
DLOGMOD=NSX32702,                                                      X
EAS=1
   .
   .
   .
*
A01CS011 APPL ACBNAME=XPDTR011,                                        X
PRTCT=XPED,                                                            X
MODETAB=ISTINCLM,                                                      X
DLOGMOD=NSX32702,                                                      X
EAS=1

Each active Batch Connect region requires a pair of VTAM APPLIDs. XPDTR000 through XPDTR011 allows for six (6) active regions at one time. The entries are as follows:

ACBNAME

The APPLID. The names must start with the value specified in the CT2VTPFX keyword in PARMLIB. The first ACBNAME must end with the value specified in the CT2VTBEG keyword in PARMLIB. The last ACBNAME must end with the high-pair number derived from the CT2VTN2S keyword in PARMLIB. (For example: CT2VTPFX=XPDTR, CT2VTBEG=001, CT2VT2NS=7 would result in a “low” ACB name of XPDTR001 and a “high” ACB name of XPDTR014).

PRTCT

The password. Code Debug TSO sets the password to XPED.

MODETAB

The VTAMLIB member that defines the logmodes that can be used by the application. Member ISTINCLM is a default mode table shipped by IBM.

Warning

Do not modify the NSX32702 logmode used for DLOGMOD. Code Debug has dependencies on certain NSX32702 parameters, such as an RUSIZE value of 0.

DLOGMOD

The default logmode for this application. This must be a NON-SNA logmode. NSX32702 is a valid logmode entry in member ISTINCLM

EAS

The estimated application sessions. Coding the number 1 instead of using the default reduces storage allocation.

Task 7.2 Batch Connect Security

The following person is required for this task:

Important

Code Debug TSO and Code Debug IMS Installer

The Batch Connect security module (automatically included when the facility is installed) enforces a standard that requires that the job name to which you are connecting be the same as your TSO ID plus one character.

Important

If this is not compatible with your site’s security system, you can either rewrite the Batch Connect security exit or deactivate it by changing PARMLIB keyword to CTLSEC=NO.

To use any other security checks, modify SLXTINST(ADSRAUSR) to whatever your site standard is for the job name. SLXTINST(JCLRAUSR) contains the JCL needed to receive and apply the USERMOD.

If your site does not enforce a standard that requires the job name to be the same as your TSO ID plus one character, then you may need to customize the TSO OUTPUT exit, IKJEFF53.

Task 7.3 Perform Initial Verification

The following person is required for this task:

Important

Code Debug TSO and Code Debug IMS Installer

Task 7.3.1 Verify Batch Connect Installation

Run the Installation Verification Programs (IVPs) to Initiate Verification Test Sessions

To verify that the Batch Connect process is properly customized, use the same IVP you used to verify the base product install.

The following sample JCL members provided in SLXTSAMP are language-specific. Make sure any you use have a valid JOBCARD (matching your TSO UserID, plus one character).

Batch Connect IVPs

Language

SAMPLIB JCL Member

COBOL

TRIJCL

PL/I

TRIJCLP

Assembler

TRIJCLA

C

TRIJCLC

  1. Select 3 (BATCH) from the Code Debug TSO Primary Menu.
  2. Select 1 (Batch) from the Batch Menu.
  3. Type the SLXTSAMP data set name in the Data set Name field and press Enter.

  4. Select the appropriate language-specific TRIJCL* member

    Tip

    The Load Module libraries in the “setup” should already have been populated when you ran the IVP for the base product.

  5. Type I next to the program name.

  6. Type RUN on the COMMAND line and press Enter. The status Processing Request for Code Debug Batch Region may be displayed. Eventually, source should be displayed.

    The interaction between the Batch Job and the TSO session verifies that the VTAM nodes were properly configured.

  7. Type EXIT on the COMMAND line and press Enter.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*