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 dump capture address space advanced configuration

Important

If your site does not plan to install Batch Abend-AID, see Transaction-dump-capture-address-space-advanced-configuration.

The following roles are involved for this section:

Batch Abend-AID administrator

z/OS system programmer

This section describes the various advanced configuration options available for the Abend-AID Batch Dump Capture Address Space (BDCAS). An Abend-AIDBDCAS is an MVS address space that manages batch dump capture processing. The BDCAS must be active whenever batch Abend-AID is active. No batch Abend-AID reports will be generated, even to SYSOUT, unless you configure and start the BDCAS. We recommend that you run the BDCAS as a started task that is always available. The BDCAS must be active before starting the Abend-AID SVC51 interface.

You should have already started the batch dump capture address space (BDCAS) as described in the Abend-AID Installation and Configuration Guide. Use the information in this section to make changes to better meet your site’s requirements.

Your site must have at least one Abend-AID batch dump capture address space per MVS image on which batch dumps are to be captured. You can run multiple BDCASs on a single MVS image, but doing so should not be necessary. You must repeat the steps in this section for each BDCAS you want to create.

Specifying the BDCAS configuration parameters (AABD00 and AABDALL)

Starting with Abend-AID 17.02, the //FDBDPARM DD statement is no longer used. Abend-AID configuration parameters are provided by the BMC AMI Common Mainframe Services Controller  (CMSC), which is a component of the Enterprise Common Components (ECC) Release 17.02 or more current single-image installation. The parameters that control the batch dump capture address space (BDCAS) configuration are specified in the Abend-AID installation sample library (hlq.CTL) members AABD00 and AABDALL. AABD00 includes the core BDCAS customization parameters, and ABDALL includes comprehensive BDCAS customization parameters as a reference for more advanced customization.

Once you have updated this member, depending on the security enforced at your site, add the edited AABD00 PARMLIB member to the //CWPARM concatenation in the CMSC BMC PARMLIB, or ask your CMSC administrator to do so. Use the z/OS MODIFY command to update the BMC PARMLIB with your changes to the PARMLIB member, or ask your CMSC administrator to do so. You can either provide the updated member or you can provide a PDS containing the member. If you provide a PDS, it must have the following attributes:

LRECL=80
BLKSIZE=any multiple of 80
RECFM=FB

See Configuration Parameters Controlled by the CMSC for the complete list of required/recommended configuration parameters included in the Abend-AID installation sample library hlq.CTL AABD00 and AABDALL sample members and instructions on how to implement changes. Review below the additional BDCAS configuration parameters that are available with this Abend-AID release.

Task 1: Specify the advanced BDCAS configuration parameters

Note

The required, recommended, and optional BDCAS configuration parameters are in the Abend-AID installation sample library hlq.CTL member AABDALL. See Configuration Parameters Controlled by the CMSC for the complete list of configuration parameters controlled by the BMC AMI Common Mainframe Services Controller (CMSC) and their descriptions.

Review the settings for the batch dump capture address space (BCDAS) configuration parameters to ensure that they are desired and relevant to your site in the AABDxxxx member that you or your CMSC administrator copy to the CMSC, as described in Configuration-parameters-controlled-by-the-CMSC.

Note

If you add or change a parameter while the BDCAS is active, you must stop and restart the BDCAS for the new/changed value to take effect.

Task 2: Modify the BDCAS JCL ($68BDCAS)

Installation sample library hlq.CTL member $68BDCAS contains sample startup JCL for the Abend-AID subsystem and batch dump capture address space. Review and modify the sample JCL according to the guidelines in this section.

The job has two steps. The first step starts the Abend-AID subsystem. The second step starts the batch dump capture address space. You need only one Abend-AID subsystem regardless of how many BDCASs you run on the MVS image. If the Abend-AID subsystem is already active when you submit this job, the step to start the subsystem is automatically skipped.

This section provides information about the following topics:

JOB or PROC statements

You can run the batch dump capture address spaces (BDCAS) as either a job or a started task. If you want to run the BDCAS as a started task, change the JOB statements to PROC statements, and modify the BDCAS JCL according to the instructions in the following sections. Then, copy the PROC to a library in your system PROCLIB concatenation.

Note

We recommend that you run the BDCAS as a started task and that you start it at IPL. The BDCAS must be active for batch Abend-AID to capture batch dumps. If the BDCAS is not active, no report will be generated, even to SYSOUT.


If you run the batch dump capture address space as a job, modify the BDCAS JCL according to the instructions in the following sections. Then, submit the BDCAS JCL when you want to start the  BDCAS.

Note

Note the following:

  1.  The BDCAS JCL is always generated with a TIME=1440 parameter on the execute statement to prevent the BDCAS from timing out, regardless of the amount of CPU time it uses. If necessary, modify this parameter to your site’s requirements.
  2.  The BDCAS region size defined on the execute statement is 8 megabytes. This is the minimum recommended region size for the BDCAS.
  3.  The BDCAS requires 64-bit storage during batch dump capture. You can do this using the MEMLIMIT=nnnnM parameter on the JOB or EXEC statements in your BDCAS JCL. Alternatively, your MVS systems programmer may have set an installation default MEMLIMIT through SMFPRMxx in PARMLIB or by using SMF exit IEFUSI. Check with your MVS systems programmer.
  4.  Whether you run the BDCAS as a started task or a batch job, assign the BDCAS to the SYSSTC Service Class. Doing so gives it a fixed high priority so that it can execute and finish quickly without impacting system performance. For more information, see Assigning-the-BDCAS-and-TDCAS-to-the-SYSSTC-service-class.
  5.  Do not specify REUSASID=YES if Db2 may be active in the jobs that Abend-AID will process. Because Db2 does not support REUSASID=YES, if it is specified, abend code S0D3 may occur.

Specifying the subsystem and BDCAS names

The BDCAS JCL has two execute statements: one for the Abend-AID subsystem and one for the batch dump capture address space:

  • The first execute statement contains a parameter value that specifies the name of the Abend-AID subsystem. This value is a four-character name. The default is CWAA. The parameter is specified PARM=’INIT,aasubsystemname’. The INIT must be included in the parameter. You can specify the same subsystem name for every BDCAS on a single MVS image.

The parameters on the second execute statement specify a unique batch dump address space name, a server type value, and optionally, a suffix value. The batch dump address space name is a one- to eight-character value that is used to identify the BDCAS to batch Abend-AID components. Therefore, you must specify a unique value for the parameter for each BDCAS you create on this MVS image. The server type value for the batch dump capture address space is BDCAS. No other value should be specified. The suffix value identifies the member containing the parameters. If a value is not specified, then the CMSC returns values from the default member. The team supporting the CMSC should provide you with the suffix value.

Note

The viewing subsystem is not the same as the Abend-AID subsystem. You cannot share the subsystem between a viewing server and a batch dump capture address space (BDCAS). See MVS_SUBSYSTEM_NAME=CWSS and MVS_SUBSYSTEM_TYPE=OWNER for information about specifying the viewing subsystem for TSO/ISPF or CICS viewing access.

Abend-AID data sets used in BDCAS

The following DD statements are generated with data set names that are created from the values specified in the installation dialog. Ensure they are correct:

//STEPLIB   DD DISP=SHR,DSN=compware.lcx170.SLCXAUTH
//   DD DISP=SHR,DSN=compware.paa170.SPAAAUTH
//FDBDRPL   DD DISP=SHR,DSN=compware.lcx170.SLCXLOAD
//   DD DISP=SHR,DSN=compware.paa170.SPAALOAD
//FDBDCUST DD DISP=SHR,DSN=aavwr.cust

The //STEPLIB DD points to the authorized step libraries for:

  • Enterprise Common Components
  • Batch Abend-AID

The //FDBDRPL DD points to the load libraries for:

  • Enterprise Common Components
  • Batch Abend-AID

The //FDBDCUST DD points to the Abend-AID Viewer customization file that is created/upgraded with the $62CUST generated job as described in the Abend-AID Installation and Configuration Guide.

BDCAS log destination

The //FDBDLOG DD statement specifies a SYSOUT class that is used to record BDCAS informational and error messages. We recommend that you check this output if you experience problems using batch Abend-AID, since many BDCAS-related messages are written there.

The default value is: 

SYSOUT=*, SPIN=UNALLOC

Note

SPIN=UNALLOC is required to prevent the loss of JES output with the ARM_ENABLED=YES parameter setting in the viewing server/BDCAS. However, this default setting is also valid for sites not using the ARM restart option.

ABNLIGNR DD statement

The BDCAS JCL contains an //ABNLIGNR DD DUMMY statement so that batch Abend-AID does not process BDCAS dumps. These statements should not be removed from the BDCAS JCL.

 

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