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.

Multiple viewing servers sharing files across MVS images

This section provides a configuration example of two viewing servers on each of two MVS images. It first describes the data sets used by the viewing servers, and then provides an example of viewing access configuration. The information in this section is useful for sites that have multiple MVS images, and want to share a single customization file between images. If you have multiple MVS images but want to define one customization file per MVS image, see the example provided in Two Viewing Servers and One TDCAS for a Single MVS Image  or Two Viewing Servers and Two TDCASs .

After you create your first viewing server, you can easily configure additional viewing servers by repeating the steps described in Abend-AID-viewing-server-advanced-configuration.

The following figure illustrates the data set usage of an Abend-AID configuration for SERVER1 running on MVS1, and SERVER2 running on MVS2.

Dataset Usage of Two Viewing Servers on Two MVS Image

image2021-1-8_17-11-19.png

Note

  1. The customization file and system DSECT file are allocated on shared DASD, and are used by both SERVER1 and SERVER2.
    Ensure that these files are part of a GRS ring to protect their integrity. See GRS-considerations for more information.
    The user DSECT file and source listing files are not shown. If you are using these facilities, these files can be shared by both viewing servers (if they are allocated on shared DASD), or each viewing server can have its own copy of the files.
  2. 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

    6. Transaction database. We recommend that you allocate at least two transaction databases per viewing server.
      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.

  3. SERVER1 is processing dumps for CICS region CICSPROD, and SERVER2 is processing dumps for CICS regions CICSTST1 and CICSTST2. These CICS regions are running on the same MVS image as the viewing servers that are processing their dumps.

  4.  A TDCAS is running on each MVS image. You cannot share a TDCAS across MVS images. If you want to run more than one TDCAS per image, see Two-viewing-servers-and-two-TDCASs.

    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.

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 Two MVS Images

 image2021-1-8_17-11-34.png

Note

  1. The TDCASs are not referenced in Viewing Access Configuration of Two Viewing Servers on Two MVS Image because they are not involved in dump viewing.
  2. SERVER1 is configured for only VTAM viewing access. The LU2_APPLID=LU2APPL1 server configuration parameter is specified in this viewing server’s PARMLIB, and the LU 2 APPLID LU2APPL1 is defined in SYS1.VTAMLST.
    When a user logs onto SERVER1 through VTAM, only dumps for region CICSPROD are available because SERVER1 is processing dumps only for that region. See Data set Usage of One Viewing Server Supporting Two MVS Images.
  3. Users attached to MVS2 can access SERVER1 as a VTAM application, if APPLID LU2APPL1 is defined as a cross-domain resource.
  4. CICS region CICSPROD is not shown in Viewing Access Configuration of Two Viewing Servers on Two 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 subsystem name (ACSS) must be unique on this MVS image. Because the Abend-AID viewing server dynamically starts the viewing subsystem, no further configuration for the viewing 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.

  6. Users attached to MVS1 can access SERVER2 as a VTAM application if APPLID LU2APPL2 is defined as a cross-domain resource.

 

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