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.

Two viewing servers and two TDCASs

This section provides a configuration example of two viewing servers and two TDCASs on a single MVS image. It describes the data sets used by the viewing servers and TDCASs. It does not provide a viewing access configuration example since the number of TDCASs does not affect viewing access configuration. See Viewing Access Configuration of Two Viewing Servers on a Single MVS Image for an illustration of viewing access configuration.

The information in this section is useful if you have only one MVS image but want to configure more than one Abend-AID viewing server, and you have a requirement for more than one TDCAS.

After you create your first viewing server, you can easily configure additional ones by repeating the steps described in the “Abend-AID viewer configuration” chapter of the Abend-AID Installation and Configuration Guide. Create a second TDCAS by repeating the steps described in Transaction-dump-capture-address-space-advanced-configuration.

The following figure  illustrates the data set usage of two viewing servers, SERVER1 and SERVER2, on a single MVS image. Two TDCASs are configured for the image.

Dataset Usage of Two Viewing Servers and two TDCASs on a Single MVS Image

image2021-1-8_17-13-28.png

Note

  1. SERVER1 and SERVER2 share the customization file and the system DSECT file. If your site is using the recommended MVS post-dump exit automatic region dump import facility, you can have only one customization file per MVS image, so the viewing servers must share this file. If you are not using this recommended facility, you can have multiple customization files on an MVS image.
  2. The system DSECT file is shared to save DASD. Alternatively, each viewing server can have its own copy of the system DSECT file. The user DSECT file and source listing files are not shown. If you are using these facilities, these files can be shared between viewing servers, or each viewing server can have a copy of these files.

  3. Each viewing server has its own set of the following viewing server-owned data sets:

    1. Dump information file
    2. IPCS directory (optional)
    3. PDSM file
    4. Viewing server work file
    5. Shared directory

    The viewing server data sets were allocated by executing the jobs generated into the Abend-AID installation sample library hlq.CTL member $$VWRLOG, as described in the “Abend-AID viewer configuration” section of the Abend-AID Installation and Configuration Guide. The viewing server parameters for each viewing server are specified on the EXEC statement of the S65SRVR job as the two- to four-character suffix of the AAVRxxxx member that you or your BMC AMI Common Mainframe Services Controller (CMSC) administrator makes available to the BMC CMSC PARMLIB.

    All other Abend-AID libraries — the Abend-AID authorized and non-authorized load libraries (SKFXAUTH, SKAZAUTH and SKFXLOAD, SKAZLOAD); the CICSLIB load library (SKFXCLIB); and the Common Shared Services authorized and non-authorized load libraries (SLCXAUTH and SLCXLOAD) — can be shared by all the viewing servers on the MVS image.

  4. SERVER1 is processing dumps for CICS region CICSPROD, and SERVER2 is processing dumps for CICS regions CICSTST1 and CICSTST2.Abend-AID continues to suppress duplicates until you delete the original dump, or it is automatically deleted by Abend-AID if the transaction database fills, or the expiration interval expires.
  5. The TDCAS is managing transaction dump capture for all CICS regions on the image. These dumps are written to the correct shared directory and transaction database based on the information specified on the CICS Region Configuration customization screen. This information is stored in the Abend-AID customization file. When Abend-AID initializes in the CICS region, it reads and retains information from the customization file. The TDCAS references this information when a transaction dump is invoked. See Configuring Regions for more information about the CICS Region Configuration screen.
    The TDCAS writes to only the shared directory and transaction databases. It does not read from or write to the other viewing server-owned data sets. One TDCAS can write to multiple shared directories. By contrast, a viewing server can read from only one shared directory.
    Only one transaction dump capture subsystem can be active on an MVS image. The transaction dump capture subsystem is started automatically by the first TDCAS started on the MVS image. When the second TDCAS is started, it verifies that the transaction dump capture subsystem is active, and then registers its name with the subsystem.

 

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