Configuring CSS for a new install

This topic will assist you to configure CSS for use with BMC AMI products that utilize the CSS functions.

Skip this step if you do not have BMC AMI products that require CSS on this LPAR and continue. 

Task 1: Making CSS load modules accessible to BMC AMI products

Ensure that the CSS load modules can be accessed by BMC AMI products by placing the ECC load library in the STEPLIB or ISPLLIB for individual TSO logon PROCs, and in the STEPLIB or JOBLIB for batch jobs. The ECC load library (SLCXLOAD or a copy of it) should be concatenated in front of any BMC AMI product libraries.

Task 2: Creat the compile information table

This task will create the compile information table, which is stored in SLCXTABL and used by the CSS Utilities. This table contains information about your compilers, compiler libraries, DB2 pre-compile libraries, CICS translator libraries and other miscellaneous items. A series of ISPF dialog box panels will take you through the table creation process. When you have finished creating the table, you will have to make it available to the CSS Utilities in Task 3: To activate ISPF dialogs.

1. Edit member CXUECIN2 in the SLCXCNTL library. To avoid having your modifications overlaid by future maintenance, you should copy this member to a non-SMP/E controlled library that is in your SYSPROC concatenation. Follow the instructions that are in the member. You will need the name of your ECC panel library, SLCXPENU, and your ECC REXX EXEC/CLIST library, SLCXEXEC.

2. If you placed the member CXUECIN2 in a library that is in your SYSPROC concatenation, then you might have invoked the REXX EXEC as follows:

   TSO %CXUECIN2

   Otherwise, you may invoke it as follows:

   TSO EXEC ‘your.dataset.library(CXUECIN2)’

   The first panel displayed is the Install Menu:

   CSS Utilities --------- Install Menu --------------------------------
   COMMAND ===>
   Enter the name of the library, which is used to store the compile information
   that you supply from the options below. If the library does not exist, it
   will be allocated.
   ===>
   
   If you have already supplied the compile information in a prior installation
   and you want to copy that information to a new library, then enter the
   'old' library name below. Use the 'C' option to copy from the library named
   below to the library named above.
   ===>
   
   Enter an option on the command line.
   1.) Select compilers
   2.) Enter compiler libraries
   3.) Enter DB2 IDs and precompile libraries (optional)
   4.) Enter CICS IDs and translator libraries (optional)
   5.) Enter miscellaneous information
   A.) Process options 1 through 5
   C.) Copy a prior installation's information to a new library
   
   Press ENTER to process or enter END command to terminate

   The first field is the name of the compile information table. All the information entered will be saved in this table. If the file does not exist it will be allocated for you. The second field is used during the COPY command. See Option B. Copy a prior installation's information to a new library. 
   

Option 1. Select compilers

This option displays the available compilers that the Compile Facility supports. In the following Select Compilers figures (Compile Information Table - Select Compilers (1 of 2) and Compile Information Table - Select Compilers (2 of 2)), specify Y next to each compiler that will to be used with the Compile Facility.

This option must be specified first, with at least one compiler selected. 

Compile Information Table - Select Compilers (1 of 2)

Compile Information Table - Select Compilers (2 of 2)

Option 2. Enter compile libraries

This option allows you to supply the library names for the compiler you selected in Option 1. Select Compilers. The compilers that you selected will have their corresponding arrow indicators highlighted and the field names will be modifiable.

Compile Information Table - Enter Compiler Libraries (1 of 5)

Compile Information Table - Enter Compiler Libraries (2 of 5)

Compile Information Table - Enter Compiler Libraries (3 of 5)

Compile Information Table - Enter Compiler Libraries (4 of 5)

Compiler Libraries – screen 5 of 5

Libraries entered on these screens depend on the compile processors used at your site. The following types of libraries can be entered on this figure:

• Compiler libraries
• SYSLIB libraries
• Compiler dependent libraries

Compiler libraries describe the data sets that contain the compile processor load modules. These libraries are required only if the processor libraries are not already included in the concatenation lists for LPA or LINKLIST. When these libraries are supplied, they will appear in the STEPLIB DD of the compile JCL.

The SYSLIB libraries describe the data sets to be used for the primary resolution of external references by the linkage editor or binder. For example, the L/E library, SCEELKED. When these libraries are supplied, they will appear in the SYSLIB DD of the Linkedit step.

Compiler dependent libraries are for those compilers that have additional library requirements. For example, the C language SYSMSGS library or the L/E library, SCEERUN.

Option 3. Enter DB2 IDs and Pre-compile libraries

If your site has DB2, this option will allow you to define DB2 identifiers and associate the identifiers with DB2 libraries. When an identifier is selected, the associated data sets will appear in the STEPLIB DD of the pre-compile step and in the SYSLIB DD of the Linkedit step. The DB2 IDs will appear on the Compile Menu.

In the column on the left, type in a DB2 identifier. It can be from one to six characters in length. You may have up to two identifiers with the same name. In addition, you may have up to eight unique DB2 identifiers.

In the column on the right in Compile Information Table - Enter DB2 IDs and Pre-compile Libraries type in the DB2 data set names that are required to perform the DB2 pre-compile step.

Compile Information Table - Enter DB2 IDs and Pre-compile Libraries

There are two D910S1 identifiers. That is the maximum for a single identifier. Also, there are three unique identifiers: D910S1, DA10S1, and DB10S1. You may have up to eight of these.

Option 4. Enter CICS IDs and translator libraries

If your site has CICS, this option will allow you to define CICS identifiers and associate the identifiers with CICS libraries. When an identifier is selected, the associated data sets will appear in the STEPLIB DD of the translator step and in the SYSLIB DD of the Linkedit step. The CICS IDs will appear on the Compile Menu.

In the column on the left, type in a CICS identifier. It can be from one to six characters in length. You may have up to two identifiers with the same name. In addition, you may have up to eight unique CICS identifiers.

In the column on the right, type in the CICS data set names that are required to perform the CICS translator step.

There are two CTS530 identifiers. That is the maximum for a single identifier. Also, there are three unique identifiers: CTS530, CTS520, and CTS510. You may have up to eight of these.

Option 5. Enter miscellaneous information

Information that did not fall within the previous option categories (1 through 4) are found on the Miscellaneous Settings panel.

Miscellaneous Settings

Foreground Compile: Some sites do not want their staff doing foreground compiles. If you do not want your users doing foreground compiles, then set this field to N. The foreground literal will not be displayed as one of the preparation options.

Job Statement Exit: This is an exit point in which the JOB card is passed to the stated entity before job submission for the Batch option. The invocation of the exit is also done before the JCL is displayed with the Editjcl option.

The invocation of the exit uses the ISPF SELECT service syntax. The following are examples:

or

Option A. Process options 1 through 5

Entering this option on the command line will cause options 1 through 5 to be displayed sequentially.

Option B. Copy a prior installation’s information to a new library

The Copy process will take an existing compile information table with member AAUTCTBL and copy the member to a new compile information table. If the new table already has member AAUTCTBL, a message window appears asking if you want to overwrite the existing member or bypass the update.

This process may be used to create a back-up of your completed compile information table. Also, it may be used to carry existing compile information forward to a new release—thus, avoiding having to retype the compile information.

1. Specify C on the command line.
2. In the first field, enter the data set name that you want to contain the compile information.
3. In the second field, enter the data set name of an existing compile information table.
4. Press Enter to copy the information. The Compile Menu is displayed in the figure Compile Menu – Compile Facility with the values that you supply during this installation.

Compile Menu – Compile Facility

If you set the Foreground Compile value to Y in the figure Miscellaneous Settings, then the Foreground literal appears in the parenthetical list to the right of the Preparation field. If you set the Foreground Compile value to N, then the literal does not appear.

If you selected all the compilers, the parenthetical list under the Language field is generated. The user will select the language they want to use for their compile by placing one of the names from the list in the Language field. The name entered tells the compile facility which libraries to use during the compile.

If you used eight unique DB2 identifiers, the list under the DB2 Precompile field would be similar. If you supplied less than eight unique identifiers, then any supplied would appear in a left to right, top to bottom sequence.

If you used eight unique CICS identifiers, the list under the CICS Translator field would be similar. If you supplied less than eight unique identifiers, then any supplied would appear in a left to right, top to bottom sequence.

Task 3: Activating BMC ISPF dialogs

This task discusses two different ways to activate the CSS Utilities libraries, included with the BMC ISPF Dialogs—dynamically, or at TSO startup.

If you do not want to use the CSS Utilities, continue to Task 5: To link CSS utilities tutorials to your main tutorial panel.

To dynamically allocate the CSS Utilities libraries when CSS Utilities are executed, you must determine how to make the REXX EXECs and CLISTs accessible.

CSS provides sample REXX EXECs and CLISTs for invoking CSS Utilities in library SLCXCNTL. You can allocate this library at TSO logon time, or make the CLIST or REXX EXEC accessible in a user-defined library allocated at TSO logon.

1. Determine whether to use REXX EXECs or CLISTs. We recommend using REXX EXECs; you may find them easier to customize and maintain.
2. Determine whether Japanese and English language support is required, or just English language support.

3. If using REXX EXECs, choose the appropriate REXX EXEC for CSS Utilities using the following table as a guide. If using CLISTs, select one CLIST for CSS Utilities.

   Use this REXX EXEC:	Or this CLIST:	For:
   CWUTREXE	CWUTCLSE	CSS utilities, English-only language support, set up or run Code Debug utilities.
   CWUTREXJ	CWUTCLSJ	CSS utilities, English and Japanese language support, set up or run Code Debug utilities.

4.  Change the library names in the REXX EXECs or CLISTs selected in previous step to match your site standards.

   Important

   An optional ISPSLIB can be used with On-the-Fly processing invoked in the Abend-AID Viewer. See On-the-fly-Language-Processing-Support for detailed information about support for On-the-Fly processing CLISTS. You may use an existing skeleton library allocated at TSO logon time or allocate one at viewer startup by updating the REXX EXECs or CLISTs selected.
   
   The CSS Utilities require the SLCXSLIB and SLCXTABL data sets to be concatenated to ISPSLIB and ISPTLIB respectively.

5. Allocate the ECC SLCXCNTL library at TSO logon time, or copy the edited REXX EXECs/CLISTs to a library allocated at TSO logon:
   
   
   • To allocate the ECC SLCXCNTL library at TSO logon:
     Add the library to the SYSPROC concatenation in the TSO logon PROC.
   • To make specific REXX EXECs/CLISTs accessible in a library allocated at TSO logon:
     Copy the REXX EXECs or CLISTs to an existing SYSPROC library allocated at TSO logon.

6. Users can invoke the CSS Utilities by selecting an option from an ISPF panel (recommended), or by executing a REXX EXEC or CLIST.

   • To enable users to select an ISPF menu option:
     Add one or more of the following lines to an ISPF panel. Note that ‘o’ represents the option to be entered at the menu command prompt.

   o ‘CMD (%CSS Utilities CLIST name or REXX EXEC name)

   • To invoke CSS Utilities by executing a REXX EXEC or CLIST:
     Enter the appropriate command at the TSO command prompt.

   TSO %CSS Utilities CLIST name or REXX EXEC name

Option 2. Allocate the libraries at TSO startup

Allocating the load, panel, and message libraries at TSO  logon simplifies maintenance. All TSO users have access to CSS Utilities after logging on to TSO, and upgrades that affect all TSO users can be made in one central location. However, allocating these libraries at TSO logon may be inappropriate. In that case, dynamically allocating the libraries may be a better solution.

Steps to provide access to the load, panel, and message modules at TSO logon time:

1. Concatenate each library as shown:
   ECC Libraries

   Load Library SLCXLOAD	Place a DD statement for the load library in the concatenation for STEPLIB or ISPLLIB in your TSO logon PROC OR Execute a CLIST or REXX EXEC at logon time that will concatenate the load library to the appropriate DD statement before starting ISPF Important BMC AMI DevX Abend-AID for CICS users must place a DD statement for the load library in the concatenation for FDBDRPL in your server startup JCL.
   Message Library SLCXMENU	Concatenate the library to ISPMLIB in the TSO logon PROC OR Concatenate the library to ISPMLIB in a CLIST or REXX EXEC before starting ISPF
   Panel Library SLCXPENU	Concatenate the library to ISPPLIB in the TSO logon PROC OR Concatenate the library to ISPPLIB in a CLIST or REXX EXEC before starting ISPF
   EXEC Library SLCXEXEC	Concatenate the library to SYSPROC in the TSO logon PROC OR Concatenate the library to SYSPROC in a CLIST or REXX EXEC before starting ISPF
   Skeleton Library SLCXSENU	Due to the Compile Facility’s requirement for this library this DD is required. Concatenate the library to ISPSLIB in the TSO logon PROC OR Concatenate the library to ISPSLIB in a CLIST or REXX EXEC before starting ISPF
   Table Library SLCXTABL	Concatenate the library to ISPTLIB in the TSO logon PROC OR Concatenate the library to ISPTLIB in a CLIST or REXX EXEC before starting ISPF

   Important

   • Replace any existing CSS libraries in these concatenations.
   • When testing a new install of BMC AMI DevX Abend-AID, if the new BMC AMI DevX Abend-AID load and customization libraries have not yet been placed in the link list, they must be added as explained in the instructions for the SLCXLOAD library. Doing this will prevent text merge error messages when viewing an BMC AMI DevX Abend-AID reports.
   • When testing a new install of BMC AMI DevX Abend-AID for CICS, if the new BMC AMI DevX Abend-AID for CICS load library has not yet been placed in the link list, it must be added as explained in the instructions for the SLCXLOAD library. Doing this will prevent error messages when using the CSS Utilities with BMC AMI DevX Abend-AID for CICS DDIO files.

2. Add one or more of the following lines to an ISPF panel. Note that ‘o’ represents the option to be entered at the ISPF menu command prompt:

   /
   o ‘PGM(CWDDIUFE) NEWAPPL(AAUT)’

Task 4: Customizing CSS parameters

BMC provides a CSS PARMLIB member (CSSALL), which contains a single, non-core parameter, ESS. As a non-core parameter, it is not required.

The ESS parameter, Embedded Source Support, controls whether the source is embedded in the program object or not. NO specifies the source listing to not be embedded in the program object.ESS=NO

YES specifies the source listing to be embedded in the program object. The default is NO.

Task 5: Linking CSS utilities tutorials to your main tutorial panel

To link the CSS utilities tutorial panels to your tutorial main menu panel (TTUTOR or ISR00003), use the applicable member (either CXTUTOR or CXR00003) located in the SLCXCNTL library as an example.

Where to go from here?

For additional CSS configuration items, see Additional-configuration. To integrate ECC with Workbench for Eclipse, proceed to Configuring-BMC-AMI-DevX-Workbench-for-Eclipse.