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 one TDCAS for a single MVS image


This section provides a configuration example of two viewing servers, but only one TDCAS, on a single MVS image. It first describes the data sets used by the viewing servers and TDCAS, and then provides a viewing access configuration example. The information in this section is useful in the following situations:

  • If you have only one MVS image but want to configure more than one Abend-AID viewing server, and you do not have a requirement for more than one TDCAS.
  • If you have multiple MVS images, but want to use one customization file per image. If you want to share a common customization file across MVS images, see Multiple-viewing-servers-sharing-files-across-MVS-images.

After you create your first viewing server, you can easily configure additional ones by repeating the steps described in the “Abend-AID viewer configuration tasks” section of the Abend-AID Installation and Configuration Guide.

The following figure illustrates the data set usage of two viewing servers, SERVER1 and SERVER2, on a single MVS image. Only one TDCAS is configured for the image.

Dataset Usage of Two Viewing Servers and One TDCAS on a Single MVS Image

image2021-3-17_11-27-12.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 tasks” 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 BMC AMI 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. 


The following figure shows an example of how the two viewing servers can be configured for viewing access.

Viewing Access Configuration of Two Viewing Servers on a Single MVS Image

image2021-3-17_11-28-18.png

Note

  1. The TDCAS is not referenced in Viewing Access Configuration of Two Viewing Servers on a Single MVS Image because it is not involved in dump viewing.
  2. SERVER1 is configured for only VTAM viewing access. The LU2_APPLID=LU2APPL1 viewing server configuration parameter is specified in this viewing server’s PARMLIB, and the LU 2 APPLID LU2APPL1 is defined in SYS1.VTAMLST.
  3. When a user logs onto SERVER1 through VTAM, only dumps for region CICSPROD are available because SERVER1 is processing dumps for only that region. See Data set Usage of Two Viewing Servers and One TDCAS on a Single MVS Image.
  4. CICS region CICSPROD is not shown in Viewing Access Configuration of Two Viewing Servers on a Single MVS Image because it is not involved in viewing access.
  5. SERVER2 is configured for VTAM, TSO/ISPF, and CICS local and remote viewing access. The viewing server configuration PARMLIB for this viewing server contains the following specifications:

    LU2_APPLID=LU2APPL2
    LU62_APPLID=LU62APPL
    LOGMODE=FXLOGM
    MVS_SUBSYSTEM=(ACSS,OWNER)

    VTAM APPLIDs LU2APPL2 and LU62APPL are defined in SYS1.VTAMLST, and the assembled and link-edited logon mode table entry FXLOGM is contained in SYS1.VTAMLIB.

    The viewing server subsystem name (ACSS) must be unique on this MVS image. Because the Abend-AID viewing server dynamically starts the viewing server subsystem, no further configuration for the subsystem is required.

    Users logging onto SERVER2 from CICS can view dumps only for the CICS region from which they entered the AADF transaction. Users logging onto SERVER2 through either VTAM or TSO/ISPF can see dumps from both CICSTST1 and CICSTST2.

VTAM APPLIDs LU2APPL2 and LU62APPL are defined in SYS1.VTAMLST, and the assembled and link-edited logon mode table entry FXLOGM is contained in SYS1.VTAMLIB.

The viewing server subsystem name (ACSS) must be unique on this MVS image. Because the Abend-AID viewing server dynamically starts the viewing server subsystem, no further configuration for the subsystem is required.

Users logging onto SERVER2 from CICS can view dumps only for the CICS region from which they entered the AADF transaction. Users logging onto SERVER2 through either VTAM or TSO/ISPF can see dumps from both CICSTST1 and CICSTST2.

 

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