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.

Batch Abend-AID configuration tasks — new installation


If your site is not licensed for batch Abend-AID, go to Abend-AID for CICS configuration tasks.

You must have already completed Abend-AID Viewer Configuration Tasks before configuring batch Abend-AID/Abend-AID for CICS.

Perform the following tasks to configure batch Abend-AID for a new installation of Abend-AID Release 17.02.

Task 1: Configure batch Abend-AID

This task utilizes the Abend-AID Configuration and Customization Dialog panels to configure batch Abend-AID.

Complete the batch Abend-AID screens

  1. Access the 

    Abend-AID

     Configuration and Customization Dialog again, or press the END (PF3) key to navigate to the products configuration menu (Abend-AID Configuration and Customization Dialog 17.2 Products Configuration Menu).

  2. Enter S (Select) to the left of the Configure Abend-AID option.
    The screen shown in following figure is displayed.

    --------------- Abend-AID Configuration (Screen 1 of 6) ----------------------
    Command ===>
                                                                            More: +
                                                                      PF8=NEXT PANEL
    Configuring Abend-AID consists of creating/migrating report routing
    information and batch Abend-AID global options, as well as creating
    the Installation Verification (IVP) jobs.

    Abend-AID Load Lib ===> 'SYS1.CPWR.MPAA170.SPAALOAD'
    AA Common High Level Qualifier ===> SYS1.CPWR.MKAZ170
    AA Customization File ===> 'SYS1.CPWR.MKAZ170.CUST.FILE'
    AA Customization Load Lib ===> 'SYS1.CPWR.MPAA170.CUST.LOAD'
    AA Source Report Shared Directory
                              ===> ‘SYS1.CPWR.MKAZ170.SHDRRPT’
    AA Source Listing Shared Directory
                              ===> 'SYS1.CPWR.MKAZ170.SHDRLST'
    Go to the next panel.
  3. Verify that the displayed 

    Abend-AID

     load library name, the 

    Abend-AID

     Common Components high-level qualifier name, the customization file name, the customization load library name, the report shared directory name, and the source listing shared directory name are correct for your site.

  4. If not, correct the names.
  5. Press the PF8 (NEXT) key to display the screen shown in following figure.

    ------- Abend-AID Configuration: Report Routing (Screen 2 of 6) --------------
    Command ===>
                                                                         More: - +
                                                     PF7=PREV PANEL PF8=NEXT PANEL
    This configuration dialog provides for the creation/migration of Report
    Routing information in the Abend-AID Customization file.

    If you already have Report and Listing Datasets and a Routing Criteria load
    module (CWROUTE) that you want to import from a previous release, enter
    the name of the load library where that information is currently located
    below. Otherwise, leave blank and the Customization file will be updated using
    settings where all Abend-AID reports will be written to the site default
    shared directory.

    Existing Load Library ===>

    Go to the next panel.
  6. Because you are configuring a first-time 

    Abend-AID

     installation, leave this line blank to create only the default routing option of routing all 

    Abend-AID

     reports to the site default report shared directory.

  7. Press the PF8 (NEXT) key to display the screen shown in following figure. 

    ---- Abend-AID Configuration Batch Global Options (Screen 3 of 6) ------------
    Command ===>
                                                                         More: - +
                                                     PF7=PREV PANEL PF8=NEXT PANEL
    This customization dialog provides for the creation/migration of Batch
    Abend-AID Global Options in the Abend-AID Customization file.

    If you already have a Global Options load module (CWGLOBAL) that you want
    to import from a previous release, enter the name of the load
    library where that load module is currently located below. Otherwise, leave
    blank and the Customization file will be updated using the default values for
    all Global Options.

    Existing Load Library ===>

    Go to the next panel.
  8. Leave this field blank to create batch 

    Abend-AID

     global options using the 

    Abend-AID

     installation default values.

  9. Press the PF8 (NEXT) key to display the screen shown in following figure.
    New, BMC-recommended JES2 support method one
    If your site is not using JES2, go to step 12.

    Depending on your site’s security requirements, your z/OS administrator may be required to provide the z/OS SMP/E Global CSI DSN and the z/OS SMP/E Target Zone name in hlq.SKAZSAMP library member PAAJES2.

    Note

    PTF ACF495Y provides an alternate, BMC-recommended method of making CWJESTAB available to Abend-AID by applying USERMOD PAAJES2 to JES2. Member PAAJES2 in the SKAZSAMP library contains a sample job to apply the USERMOD. Before running the job, customize it for your environment.

    Member PAAJES2 in the SKAZSAMP library contains a sample job to apply the USERMOD. Before running the job, customize it for your environment.

    1. If you have not already done so, copy member PAAJES2 from SKAZSAMP to your hlq.CTL library.
    2. Update the JOB card and JOBPARM to meet your installation standards.
    3. Specify the DSNAME of your MVS global CSI.
    4. Specify the target zone name where JES2 is applied.
    5. Specify ALIAS names to match the CWJTxxxx modules that you have in your hlq.CUST.LOAD sample library that will be used with the target IPL volume.

    When you apply the USERMOD, SMP/E will install the CWJESTAB module in the SYS1.LINKLIB data set on that target zone. When that IPL volume (or a copy of it) is IPLed, Abend-AID will find the CWJESTAB module in SYS1.LINKLIB that will match the JES2 on that volume.

    Once the USERMOD is applied, any JES2 maintenance that updates the macros used to assemble CWJESTAB will cause SMP/E to automatically reassemble CWJESTAB, keeping it updated along with JES2.

    We recommend this new method for making CWJESTAB available to Abend-AID. Using this method makes running the $09ASMJT, $10SMPU1, JCLSMPDD, or JCLSMPU2 jobs no longer necessary. go to step 12 below.

    -------- Abend-AID Configuration: JES2 Support (Screen 4 of 6) ---------------
    Command ===>
                                                                         More: - +
                                                     PF7=PREV Panel PF8=NEXT PANEL

    Enter parameters below specific to your site to create the Abend-AID CWJESTAB.

    z/OS SMP/E Global CSI DSN ==> 'ZOS.SMPE.GLOBAL.CSI'
    z/OS Target Zone Name     ==> OSTZONE
    SMP/E Usermod Name to Use ==> AAJESTA

    There is no USERMOD required for sites using JES3. If you are using
    JES3, please PF8 to bypass this step.

    Go to the next panel.

     Less current, alternative JES2 support method two

    Note

    BMC still supports the following less current, alternative method for implementing JES2 support.

    Depending on your site’s security requirements, your z/OS administrator may be required to provide the z/OS SMP/E Global CSI DSN and the z/OS SMP/E Target Zone name and to run the generated jobs.

  10. Specify your site's SMP/E Global CSI data set name and Target Zone name where JES2 was installed.
  11. Specify a maximum 8-character name for the SMP/E USERMOD name.
  12. Press the PF8 (NEXT) key to display the screen shown in following figure.

    ------------ Abend-AID Configuration: IVP (Screen 5 of 6) --------------------
    Command ===>
                                                                          More: - +
                                                      PF7=PREV PANEL PF8=NEXT PANEL
    Supply the appropriate parameters below in order to generate the jobs that
    will execute the IVPs to verify Abend-AID diagnostic support for COBOL.

    Select the supported COBOL compiler used at your site:
          COBOL Z/OS         ===> Y (Y/N)
    COBOL Compiler Library ===> 'IGY.SIGYCOMP'
    COBOL Runtime Library  ===> 'CEE.SCEERUN'
    COBOL LKED Library     ===> 'CEE.SCEELKED'

    SORTLIB Dataset Name   ===> 'SYS1.SORTLIB'

    Go to the next panel.
  13. Complete the fields on this screen with values appropriate for your site if your site requires Abend-AID support for Enterprise COBOL for z/OS.
  14. Press the PF8 (NEXT) key to display the next screen, shown in following figure.

    ------------ Abend-AID Configuration: IVP (Screen 6 of 6) --------------------
    Command ===>
                                                                           More: -
                                                                    PF7=PREV PANEL
    Supply the appropriate parameters below in order to generate the jobs that
    will execute the IVPs to verify Abend-AID diagnostic support for PL/I.

    Select the supported PL/I compiler used at your site:  
                PL/I Enterprise ===> Y (Y/N)

    PL/I Compiler Library ===> 'IBMZ.SIBMZCMP'
    PL/I Runtime Library  ===> 'CEE.SCEERUN'
    PL/I LKED Library     ===> 'CEE.SCEELKED'

    Enter parameters below specific to your site to create the Abend-AID CWJESTAB.

    Assembler Macro Library ==> 'SYS1.SHASMAC'

    Enter "generate" on command line to create the installation JCL.
  15. Complete the fields with PL/I values appropriate for your site if your site requires Abend-AID support for Enterprise PL/I for z/OS.
  16. If your site uses JES2, enter your site’s Assembler macro library name.
  17. Enter generate on the command line to create the batch 

    Abend-AID

     jobs to be listed into the $$IAALOG in the 

    Abend-AID

     hlq.CTL library.

Task 2: Implement JES2 USERMOD (for JES2 sites only)

If you used New, BMC-recommended JES2 Support Method One, skip this section and continue with Task 3: Register an Abnormal Termination Exit (ATE) for language environment support. Otherwise, continue with this section.

For sites using JES2, the file section of the Abend-AID report provides extensive information about JES2 (SYSOUT) files. This reporting requires the Abend-AID load module CWJESTAB that is based on the particular version and maintenance level of JES2 that you are running. Whenever a new level of JES2 is installed or any type of SMP/E JES2 maintenance is applied, hlq.CTL members $09ASMJT and $10SMPU1 must also be run. Refer to the  Abend-AID Advanced Configuration Guide for more information about the JES2 USERMOD.

Execute the following jobs only if you are using the Less Current, Alternative JES2 Support Method Two. Review, edit, and submit according to the comments in the JCL the following hlq.CTL library member $$IAALOG jobs:

  • $09ASMJT: Loads the JES2 DSECTS into the CWJESTAB module in the hlq.CUST.LOAD library. This job also generates another JES2 DSECT load module with the format of CWJTxxxx, where xxxx is the SYSID of the LPAR. You can then maintain multiple JES2 DSECT modules distinguished by the SYSID.
  • $10SMPU1: Performs an SMP/E UCLIN of the target zone to associate a USERMOD name with the JES2 macros used to assemble CWJESTAB.
  • JCLSMPDD: Not included in the $$IAALOG of generated jobs, but included in the hlq.CTL library performs an SMP/E LIST DDDEF to list the DDNAMEs and DSNAMEs in the SMP/E target zone. The SHASMAC DDNAME found in the output of this job corresponds to the DSNAME of the correct JES2 macros.
  • JCLSMPU2: Performs an SMP/E UCLIN of the target zone to remove the USERMOD name associated with the JES2 macros used in the assembly of CWJESTAB.

Task 3: Register an Abnormal Termination Exit for language environment support

IBM provides the capability to register an Abnormal Termination Exit (ATE). You must register LEAID as a Language Environment ATE. In addition to initially performing this step, repeat this step whenever a new release of Language Environment is installed. If LEAID is already registered as an LE ATE on your system, you do not need to perform this step. Otherwise, do the following steps:

  1. In member CEEEXTAN in the IBM Language Environment sample library (CEE.SCEESAMP), where CEEXART is specified: change the XXXXXXXX to LEAID, and change the * in column 1 to a blank.
  2. Follow the directions in member CEEWDEXT of the Language Environment sample library (CEE.SCEESAMP), and make the appropriate changes.
  3. When you have made all appropriate modifications to member CEEWDEXT, submit this JCL to assemble and link-edit CSECT CEEEXTAN. After this is done, LEAID is registered as a Language Environment ATE.

    The LEAID load module is included in the Abend-AID load library hlq.SPAALOAD.

    LEAID is not downward compatible. If a CALL to LEAID is contained within an application’s condition handler, it cannot be linked with the current Abend-AID release and executed with an earlier release.

Task 4: Register LEAID64 as a Language Environment 64-Bit Abnormal Termination Exit


Note

The LEAID64 load module is included in the Abend-AID load library hlq.SPAALODE.

IBM provides the capability to register an abnormal termination exit for 64-bit applications. Register LEAID64 as a Language Environment ATE. In addition to initially performing this step, repeat this step whenever a new release of Language Environment is installed. If LEAID64 is already registered as an LE ATE on your system, you do not need to perform this step. Otherwise, perform the following steps:

  1. Specify LEAID64 on the CEEXART macro statement in CSECT CELQXTAN. A copy of the source code for this CSECT is in member CELQXTAN in the IBM Language Environment sample library CEE.SCEESAMP.
  2. Copy the source code for CSECT CELQXTAN into member CEEWQEXT JCL stream where specified. Member CEEWQEXT is also contained in the IBM Language Environment sample library.
  3. After you have made all appropriate modifications to member CEEWQEXT, submit this JCL to assemble and link-edit CSECT CELQXTAN. Once this is done, LEAID64 is registered as a Language Environment 64-bit ATE.
  4. For 64-bit applications, the LEAID64 module in the PDSE object library must be available at abend time by a //STEPLIB or //JOBLIB DD statement or must be on the link list.

Task 5: Implement the Batch Dump Capture Address Space PARMLIB under CMSC

  1. Review the BDCAS core parameters located in the AABD00 member of the hlq.CTL library.
  2. Edit the AABD00 member to include valid values for your site.
    The last line in the new parameter member is $$$ V2 END $$$ -- DO NOT MODIFY OR REMOVE. This line marks the end of new format and must not be modified or removed.
  3. In order to use the CMSC component, copy the BDCAS parameter data set member AABD00 from the hlq.CTL library to a data set in the //CWPARM DD concatenation in the CMSC JCL, or ask your CMSC administrator to do so.
  4. Update CMSC with AABD00.
    Use the z/OS MODIFY (F) command to update the CMSC with the Abend-AID Viewer PARMLIB member you created or ask your CMSC administrator to do so.

    F cmscname,PARMLIB REFRESH member_name

    Whenever you modify an existing CMSC PARMLIB member or add a new member, you must execute the CMSC REFRESH command to update the contents of the CMSC cache.

Task 6: Activate the Batch Dump Capture Address Space

  1. Edit member $68BDCAS found in the hlq.CTL library according to the comments in the JCL. In the second step of the job, modify the following EXEC statement:

    //AABDCAS   EXEC PGM =FDBMMPLU,DYNAMIC=125,TIME-1440,
    //              PARM=’xxxxxxxx,BDCAS,yyyy’,
    //              REGION=8M

    xxxxxxxx is the 1- to 8-character name of this BDCAS. You must define a unique BDCAS name for each BDCAS configured on this MVS image.

    yyyy is the 1- to 4-character suffix of the BDCAS PARMLIB member configured for this BDCAS. The default suffix is 00, but you or the CMSC administrator can change the suffix and it must be specified here. The BDCAS PARMLIB member prefix must be AABD.

  2. Submit $68BDCAS.
  3. Ensure that the BDCAS is active by finding the following message in the JES message log:
    FDBRC1999I REGION INITIALIZATION COMPLETE FOR SERVER xxxxxxxx
    Where xxxxxxxx is the name of this BDCAS.

 

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