Display the Dump Capture and Processing Menu, shown in Dump Capture and Processing Menu for Abend-AID only and Dump Capture and Processing Menu for Abend-AID and Abend-AID for CICS figures , using one of two methods:

• Tab to the Modify Dump Capture and Processing Options option on the Customization Options menu, and then press Enter. Accessing the Customization Options Menu describes accessing the Customization Options menu.
• Type CAPTURE or =2 in the COMMAND (or OPTION) field on any customization screen and press Enter. You cannot use these fast-path commands unless you have accessed the customization facility.

If your site has Abend-AID only installed, Dump Capture and Processing Menu (see the following figure) for Abend-AID only figure is displayed. If your site has both Abend-AID and Abend-AID for CICS or Abend-AID for CICS only installed, Dump Capture and Processing Menu (see the following figure) for Abend-AID only figure is displayed.

Dump Capture and Processing Menu for Abend-AID only

Dump Capture and Processing Menu for Abend-AID and Abend-AID for CICS

Configuring regions 

On the Summary Configuration screen (batch Abend-AID only installed) or the Region Configuration screen (batch Abend-AID  and Abend-AID for CICS or Abend-AID for CICS only installed), you assign Abend-AID  Viewer servers to process dumps for specific regions. A combination of job name and MVS SYSID is used to identify each region. By default, all dumps are processed by the very first viewing server ever started at your site. 

You can also indicate which region dump profile member you want each region to use. By default, all regions (qualified by job name and MVS SYSID) use the $DEFAULT members for region dump profiles. If you want any regions to use values other than these defaults, you must use the summary configuration function. From the above menus, option 6 is for batch Abend-AID  only, and options 3 through 5 are for Abend-AID for CICS only.

A single asterisk (*) is a wildcard character for the Job Name and MVS SYSID fields. For example, you can specify AAVWR* in the Job Name field to indicate that all jobs beginning with AAVWR are to use the region profile members and viewing server listed in their corresponding fields. This can remove the need to enter the job name of each region at your site.

Task 1: Modify summary configurations

To modify summary configurations, complete the following procedure:

1. Display the Summary Configuration screen, shown in Summary Configuration for Batch Abend-AID figure using one of two methods:

   • Tab to the Summary Configuration option on the Dump Capture and Processing Menu, shown in Dump Capture and Processing Menu for Abend-AID  only figure and then press Enter.

   • Type SUMMARY or =2;1 in the COMMAND (or OPTION) field on any customization screen and press Enter. You cannot use these fast-path commands unless you have accessed the customization facility.
     Summary Configuration for Batch Abend-AID

     Customization ---------- Summary Configuration ----------------- Row 000001 of 000001
     COMMAND ===>                                                          SCROLL ===> CSR
                                                                                                                                    
     Enter your values in the appropriate fields.  This list is processed in a top-down  
     order. Abend-AID can capture both CICS and non-CICS dumps. Press HELP (PF1) for more  
     information.                                                                         
     _____________________________________________________________________________________
                                                                                                                                    
      I Insert     R Replicate      D Delete
                                                                                                                                    
                MVS    Rgn Dump  Viewing   Region Description  (Categorizes                                                         
      Job Name  SYSID  Profile   Server    Dumps on the Summary Display)                                                            
      ********  ****   ********  ********  ********************
     _ PFHRHH*   *      $DEFAULT  AASRV110  My dumps  
     _ AA*       *      $DEFAULT  AASRV110  Batch dumps
     _ IMS*      *      $DEFAULT  AASRV110  IMS dumps
     _ PFHEAB*   *      $DEFAULT  AASRV110  IDMS batch dumps
     _ DFHBJS0*  *      $DEFAULT  AASRV110  Batch Dumps
     _ HL*       *      $DEFAULT  AASRV110  Batch Dumps
     _ HST*      *      $DEFAULT  AASRV110  Batch Dumps
     _ HQ*       *      $DEFAULT  AASRV110  HQ Batch Dumps
     _ FF*       *      $DEFAULT  AASRV110  Batch Dumps
     _ H01AC098  *      $DEFAULT  AASRV110  Batch Dumps                                                                                         
      ************************ BOTTOM OF DATA *****************************************

   The Summary Configuration screen initially displays the asterisk (*) wildcard character in the Job Name and MVS SYSID fields, and $DEFAULT in the Rgn Dump Profile field. This is the default entry, and means that all regions — regardless of job name or SYSID — are processed using the $DEFAULT members by the first viewing server you ever start at your site.

2.  Use the I (Insert) line command to insert a new line or the R (Replicate) line command to replicate an existing line to use as a starting point for each new entry.

   Note

   • The summary configuration list is processed in a top-down order. Region dumps are processed according to the first configuration entry matched in the list. Keep this in mind when you are inserting or replicating statements, or if you are using the asterisk (*) wildcard character.
   • There is no line command to move an entry, so if you put an entry in the wrong place, you must delete it and then insert it in the correct place. Use the D (Delete) line command to delete an entry.
   • The Abend-AID Viewer warns you if you attempt to save the summary configuration list and the default is not the last entry. Because all job name/APPLID/SYSID combinations will match the default entry, any entries you make that are after the default in the list are ignored.
   • If you install the Abend-AID Viewer MVS post-dump exit and you leave the default entry on the Summary Configuration screen, Abend-AID also processes system dumps. To prevent this, remove the default entry, and then ensure that your other definition statements are specific enough to cover all of your regions. Alternatively, you can leave the default entry if the region dump profile associated with the entry specifies Dump Type=SYS1 and Copy SYS1.DUMP=N, which are the defaults.
   • You cannot save duplicate entries. The Abend-AID Viewer highlights duplicate entries when you attempt to save the list. You must delete or modify one of the entries.
   • Use the ? (question mark) line command to display the viewing server name and the shared directory data set name for an entry.
   • You can enter up to a maximum of 65,535 entries.

3. Enter your configuration values in the appropriate columns. A single asterisk (*) can be used as a wildcard character to partially qualify any job name or MVS SYSID. An asterisk entered as a full qualifier means that all job names or SYSIDs are processed using the profile members and viewing server assigned to the entry.

   Note

   The asterisk (*) can be used anywhere at the beginning, middle, or the end of a partial field value. Or, it can be used in place of the value to indicate that all values qualify for the condition set.

   The Summary Configuration screen displays the following input fields:

   Job Name

   Specifies the name of the MVS address space. You can use the asterisk (*) wildcard character to create a generic job name for multiple regions.

   Customizing SVC Dump Processing contains information on the choices that are available to you for processing region dumps.

   MVS SYSID

   Specifies the MVS SYSID of the executing region. You can use the asterisk (*) wildcard character to create a generic SYSID.

   Rgn Dump Profile

   Specifies the region dump capture profile for this entry. This profile indicates automatic processing choices for region dumps. See Customizing SVC Dump Processing for more information. Modify Region Dump Profiles describes creating your own profile members. $DEFAULT indicates the BMC-supplied defaults are used.

   Viewing Server

   Specifies the name of the viewing server that processes dumps matching this entry. By default, the name of the first viewing server ever started at your site is displayed in this field. To use a different viewing server, type over the displayed name with the new viewing server name. To identify the viewing server names, defined for your site, see Viewing-server-name.

   Region Description

   Specifies a description for the region. This description is used to categorize entries on the Fault Summary screen. Enter an identical region description for all regions you want to group under the same name.

   The Fault Summary summarizes the type and number of region and batch dumps available for each region or region group to which you have assigned a name. Refer to the  Abend-AID User or Reference guides for a description of the Fault Summary.

   Note

   Entering a region description is optional. Regions are grouped on the Fault Summary display by job name, unless you enter a region description here.

4. Press the END (PF3) key to save your changes or enter CANCEL to erase them.

Example

The summary configuration shown in Summary Configuration figure (see the following figure) displays four configuration statements. The first statement specifies that any region whose job name begins with AAVWR3, regardless of the MVS SYSID of the region, is processed using member PROD for the region dump profile options. SERVER2 on the MVS images where regions meeting the specified criteria are running process dumps for this configuration.

The second statement specifies that any region whose job name begins with AAVWRT1, regardless of the MVS SYSID of the region, is processed using member TEST1 for the region dump profile options. SERVER1 on the MVS images where regions meeting the specified criteria are running process dumps for this configuration.

The third statement specifies that any CICS region whose job name begins with AAVWRT2, regardless of the MVS SYSID of the region, is also processed using member TEST1 for the region dump profile options. SERVER1 on the MVS images where regions meeting the specified criteria are running process dumps for this configuration.

The fourth statement specifies that all other regions are processed by SERVER1 on the MVS images where regions meeting the specified criteria are running according to the defaults contained in the $DEFAULT member. The first two fields of the statement contain asterisks, indicating that all regions are affected.

Summary Configuration

The Region Description field shows the descriptive name used for displaying summarized dump activity for regions on the Fault Summary. Because the job name AAVWRT1* and AAVWRT2* entries both have Test Region as their region description, dumps from regions matching these job names are grouped together on the Fault Summary under a common entry called Test Region. All job names beginning with AAVWRT3* are grouped together under the entry title Production Region. Any other job names not matching any criteria specifically listed here are listed by job name on the Fault Summary. Refer to the Abend-AID User/Reference Guide for more information about the Fault Summary.

Task 2: Configure Regions with Abend-AID for CICS Installed

5.  If your site has installed Abend-AID for CICS (with or without batch Abend-AID ) on this viewing server, instead of the Summary Configuration screen, the Region Configuration is displayed, as shown in Region Configuration, Left Screen figure. On the Region Configuration screen, you assign Abend-AID viewing servers and, optionally, transaction dump capture address spaces (TDCASs) to process dumps for specific CICS regions. A combination of job name, CICS APPLID, and MVS SYSID is used to identify each region. By default, all dumps are processed by the very first viewing server ever started at your site and the first TDCAS on the MVS image where a given CICS region is running. If you have multiple TDCASs and want to assign specific CICS regions to them, use this screen. If you have only one TDCAS per image, you do not have to assign a TDCAS name here. The Region Configuration screen (see the following figure) supports a maximum of 8,322 entries.

6.  You can also indicate which region dump profile, transaction dump profile, and transaction dump global options member you want each CICS region to use. By default, all CICS regions (qualified by job name, CICS APPLID, and MVS SYSID) use the $DEFAULT members for transaction dump profiles, region dump profiles, and transaction global options. If you want any CICS regions to use values other than these defaults, you must use the CICS region configuration function.

A single asterisk (*) is a wildcard character for the Job Name, CICS APPLID, and MVS SYSID fields. For example, you can specify CICSP* in the Job Name field to indicate that all jobs beginning with CICSP are to use the transaction dump global options member, region and transaction profile members, viewing server, and transaction dump capture address space listed in their corresponding fields. This can remove the need to enter the job name of each CICS region at your site.

To specify CICS region configurations, complete the following procedure:Optionally, you can also use the Region Configuration screen to assign transaction databases to CICS regions. By default, a CICS region can write to all transaction databases assigned to the viewing server that is processing dumps for the CICS region. You can restrict which transaction databases a CICS region can write to using the function described in Assign CICS Transaction Databases to CICS Regions (see Task 14.3).

1. Display the Region Configuration screen, shown in Region Configuration, Left Screen figure using one of two methods:

•  Tab to the Region Configuration option on the Dump Capture and Processing Menu, shown in Dump Capture and Processing Menu for Abend-AID  and Abend-AID for CICS  figure, and then press Enter.
•  Type REGIONS or =2;1 in the COMMAND (or OPTION) field on any customization screen and press Enter. You cannot use these fast-path commands unless you have accessed the customization facility.

Region Configuration, Left Screen

The Region Configuration screen, as shown in Region Configuration, Left Screen figure, initially displays the asterisk (*) wildcard character in the Job Name, CICS APPLID, and MVS SYSID fields, and $DEFAULT in the Region Dump Profile, Tran Dump Profile, and Tran Dump Globals and Tran Dump Handlers fields. This is the default entry, and means that all CICS regions — regardless of job name, APPLID, or SYSID — are processed using the $DEFAULT members by the first viewing server you ever start at your site and the first TDCAS started on the MVS image where the CICS region is running.

2.  Use the I (Insert) line command to insert a new line or the R (Replicate) line command to replicate an existing line to use as a starting point for each new entry.

 3.  Enter your configuration values in the appropriate columns. A single asterisk (*) can be used anywhere at the beginning, middle, or the end of a string as a wildcard character to partially qualify any job name, CICS APPLID, or MVS SYSID. An asterisk entered as a full qualifier means that all job names, APPLIDs, or SYSIDs are processed using the profile members and viewing server assigned to the entry.

The Region Configuration screen displays the following input fields:

Job Name

Specifies the name of the MVS address space. You can use the asterisk (*) wildcard character to create a generic job name for multiple regions.

If you specify anything other than asterisk (*) in this field, then you must install the MVS post-dump exit.

Customizing SVC Dump Processing contains information about the choices that are available to you for processing region dumps.

CICS APPLID

Specifies the CICS APPLID for this region. You can use the asterisk (*) wildcard character to create a generic APPLID.

In a non-XRF environment, CICS APPLID is the generic APPLID for both region and transaction dumps. In an XRF environment, for transaction dumps, the APPLID is the generic CICS APPLID. For region dumps, it is the specific CICS APPLID.

MVS SYSID

Specifies the MVS SYSID of the executing CICS region. You can use the asterisk (*) wildcard character to create a generic SYSID.

Rgn Dump Profile

Specifies the region dump capture profile for this entry. This profile indicates automatic processing choices for region dumps. See Customizing SVC Dump Processing for more information. Modify Region Dump Profiles describes creating your own profile members. $DEFAULT indicates the BMC-supplied defaults are used.

Tran Dump Profile

For Abend-AID for CICS only. Specifies the transaction dump capture profile for this entry. This profile indicates automatic processing choices for transaction dumps. See Modifying Permanent CICS Transaction Dump Profiles for more information. This section describes creating your own profile members. $DEFAULT indicates the BMC-supplied defaults are used.

Tran Dump Globals

For Abend-AID for CICS only. Specifies the transaction dump global options member for this entry. This profile indicates global processing choices for transaction dumps. See Modify CICS Transaction Dump Global Options  for more information. $DEFAULT indicates the BMC-supplied defaults are used.

Tran Dump Handlers

For Abend-AID for CICS only. Specifies the transaction dump handlers profile for this entry. This profile lists programs that routinely handle abends/conditions and that will not be identified as the abending program. Instead, the program calling these handlers is identified. $DEFAULT indicates the BMC-supplied defaults are used. You can also create your own site-defined abend handler profiles. See Modify CICS Transaction Dump Handler Profiles (see Task 14.8) for more information. If this field is left blank, Abend-AID for CICS makes no attempt to identify and ignore any abend- handling programs.

Viewing Server

Specifies the name of the viewing server that processes dumps matching this entry. By default, the name of the first viewing server ever started at your site is displayed in this field. To use a different viewing server, type over the displayed name with the new viewing server name. To identify the viewing server names defined for your site, see Viewing Server Name (see Modifying-the-viewing-server-JCL-65SRVR).

Tran Dump Capture AS

For Abend-AID for CICS only. Specifies the name of the transaction dump capture address space (TDCAS) that processes dumps matching this entry. If you have only one TDCAS per MVS image, you can leave this field blank, and Abend-AID automatically uses the TDCAS on the image where this region is running. You need to complete this field only if you have multiple TDCASs on an image and want to assign a CICS region to a specific TDCAS. To identify the TDCAS names defined for your site, see Specifying the Subsystem and TDCAS Names (see Modify the TDCAS JCL ($67TDCAS)).

Region Description

Specifies a description for the region. This description is used to categorize entries on the Fault Summary screen.

If you want to assign a region to a description (name) for grouping on the Fault Summary screen, scroll right. The right side of the Region Configuration screen, shown in Region Configuration, Right Screen figure (see the following figures), is displayed. Enter an identical region description for all regions you want to group under the same name.

The Fault Summary summarizes the type and number of transaction and region dumps available for each region or region group to which you have assigned a name. Refer to the Abend-AID for CICS User Guide for a description of the Fault Summary.

4. Press the END (PF3) key to save your changes or enter CANCEL to erase them.

Example

The CICS region configuration shown in Region Configuration, Left Screen figure (see the following figure) displays four configuration statements. The first statement specifies that any CICS region whose job name begins with CICSP, regardless of the APPLID or MVS SYSID of the region, is processed using members called PROD for the region dump profile, transaction dump profile, and transaction dump global options. SERVER2, and the first transaction dump capture address space (TDCAS) on the MVS images where regions meeting the specified criteria are running, process dumps for this configuration.

The second statement specifies that any CICS region whose job name begins with CICST1, regardless of the APPLID or MVS SYSID of the region, is processed using members called TEST1 for the region dump profile, transaction dump profile, and transaction dump global options. SERVER1, and the first TDCAS on the MVS images where regions meeting the specified criteria are running process dumps for this configuration.

The third statement specifies that any CICS region whose job name begins with CICST2, regardless of the APPLID or MVS SYSID of the region, is processed using members called TEST2 for the region dump profile, transaction dump profile, and transaction dump global options. SERVER1, and the first TDCAS on the MVS images where regions meeting the specified criteria are running process dumps for this configuration.

The fourth statement specifies that all other CICS regions are processed by SERVER1 and the first TDCAS started on the MVS images where regions meeting the specified criteria are running according to the defaults contained in the $DEFAULT members. The first three fields of the statement contain asterisks, indicating that all CICS regions are affected.

Region Configuration, Left Screen

The figure below shows the second page of the Region Configuration screen that is displayed by scrolling right. The Region Description field shows the descriptive name used for displaying summarized dump activity for regions on the Fault Summary.

Region Configuration, Right Screen

Because the job name CICST1* and CICST2* entries both have Test CICS Region as their region description, dumps from regions matching these job names are grouped together on the Fault Summary under a common entry called Test CICS Region. All job names beginning with CICSP are grouped together under the entry title Prodctn CICS Region. Any other job names not matching any criteria specifically listed here are listed by job name on the Fault Summary. Refer to the Abend-AID for CICS User Guide for more information about the Fault Summary.

Task 3: Assign CICS transaction databases to CICS regions

To assign specific transaction databases to a CICS region, complete the following procedure:By default, a CICS region can write to all transaction databases attached to the shared directory for the viewing server that is processing dumps for the CICS region. You can restrict which transaction databases a CICS region can write to by assigning transaction databases to the region.

1. Display the Region Configuration screen, shown in Region Configuration, Left Screen figure (see the previous figure) using one of two methods:

•   Tab to the Region Configuration option on the Dump Capture and Processing Menu, and then press Enter.
•   Type REGIONS or =2;1 in the COMMAND (or OPTION) field on any customization screen and press Enter. You cannot use these fast-path commands unless you have accessed the customization facility.

2. Enter the A line command next to the CICS region configuration statement for which you are assigning files. The Assign Database Files to Regions screen displays, as shown in Assign Database Files to Regions Screen figure ((see the following figure)).

Assign Database Files to Regions Screen

The Assign Database Files to Regions screen lists all transaction databases that are attached to the shared directory/viewing server that is processing dumps for the selected CICS region (that is, all candidate transaction database files).

Transaction databases are allocated and attached to a shared directory when you allocate them during the Abend-AID  Viewer Configuration portion of the installation dialog, as described in the “ Abend-AID-viewer-configuration-tasks-new-installation ” section of the Abend-AID Installation and Configuration Guide . If after completing the Abend-AID for CICS installation you want to add additional transaction databases to a shared directory, see Adding Databases to a Report Shared Directory.

3. To assign only a subset of the available transaction database files to this CICS job name/CICS APPLID/MVS SYSID, position your cursor on the UNASSIGN selection and press Enter. Then, enter A next to each transaction database file that the selected CICS region can use.

To unassign a transaction database, enter U next to the file name.

When you have made your file assignments, press the END (PF3 ) key to save your changes, or enter CANCEL to erase them.

Task 4: Modifying Dump Capture Profiles

On the Summary Configuration ( Abend-AID  only installed) or Region Configuration ( Abend-AID  and Abend-AID for CICS  or Abend-AID for CICS only installed) screen (option 1 on the Dump Capture and Processing Menu), you assign regions (using job name, APPLID, and MVS SYSID as qualifiers) to use the dump capture profiles you create. Multiple regions can use the same profile and, if you don’t specify a profile, the default profile is used. You can update the BMC-supplied default profiles, but you cannot delete them.The region dump capture profiles contain the actions that Abend-AID is to take when a region dump is about to be taken. BMC provides a default region dump capture profile.

To modify a dump capture profile, complete the following procedure:

1. Display the Dump Capture Profiles screen, shown in Dump Capture Profile Screen figure (see the following figure), using one of two methods:

  Tab to the Region Dump Capture Profiles option on the Dump Capture and Processing Menu (See Dump Capture and Processing Menu for Abend-AID  and Abend-AID for CICS  figure) and then press Enter.

  Type REGPROF or =2;2 in the COMMAND (or OPTION) field on any customization screen and press Enter. You cannot use these fast-path commands unless you have accessed the customization facility.

Dump Capture Profiles Screen

The Dump Capture Profiles screen lists the region dump profiles. When you initially access the screen, the $DEFAULT region profile is displayed. This member contain the default profile values supplied by BMC, and can be used as a template for profiles you create. If the BMC defaults are acceptable, you don’t have to do anything, and the Abend-AID Viewer uses the default region dump capture profile. The Dump Capture Profiles screen supports a maximum of 65,535 entries.

2. The profile names are displayed in alphabetical order. Select a profile member to create, modify, or delete, as follows:

• If you want to create a new profile member, enter R next to an existing member. This replicates the definitions of the existing member to use as a starting point for the new member. Then, complete the profile definition, as described in Modify Region Dump Profiles.
• If you want to modify an existing profile member, enter S next to the member. Then, complete the profile definition, as described in Modify Region Dump Profiles.
•  If you want to delete a profile member, enter D next to the member.

Modify region dump profiles

The Region Dump Profile screen supports a maximum of 65,535 entries. Region dump profiles specify the following information:

• Whether to automatically import the dump.
  For dumps taken to SYS1.DUMPxx data sets, this option is available only if Abend-AID first copies the dump from the SYS1.DUMPxx data set to another data set.
  For dumps taken to an automatically allocated dump data set, this option is available only if you install the MVS post-dump exit, as described in Automatically Importing Dumps.
• Whether to automatically analyze the dump.
• Whether dumps taken to SYS1.DUMPxx data sets are to be automatically copied to another SDUMP data set, and the naming convention and attributes of the data set.
• Automatically copying SYS1.DUMPxx data sets is supported only if you install the MVS post-dump exit, as described in MVS-post-dump-exit-installation.

Display the Region Dump Profile screen, shown in Region Dump Profile Screen figure (see the following figure) by  selecting or replicating a region profile member name on the Dump Capture Profiles screen (See Dump Capture Profiles Screen figure).To modify a region dump profile member, complete the following procedure:

Region Dump Profile Screen

If you displayed the Region Dump Profile screen by replicating a member on the Dump Profile Selection screen, enter a unique name in the Profile Name field and overtype the Description field with a unique name and description.

Enter I to insert a new statement in the profile or R to replicate an existing statement to use as a starting point for the new statement, and then press Enter. (Or, proceed to the next step if you are simply modifying an existing statement.) The Region Dump Profile screen is refreshed and displays the inserted or replicated line.

The Region Dump Profile screen displays the following input fields:2. Overtype the inserted or replicated line with the new values. Press the HELP (PF1) key on any field for specific information.

Abend Code

Specifies the abend code for this dump capture entry. You can use the asterisk (*) wildcard character at the end of a partial abend code. An asterisk (*) can be used in place of an abend code, to indicate ALL abend codes qualify for the condition to be set. The default is *.

Auto Import

Specifies whether to automatically import dumps that match this entry into the Abend-AID  Viewer and whether to automatically run dump analysis at the time the dumps are imported. See Automatically Importing Dumps for additional requirements for implementing the auto import function. Valid values are:

Copy SYS1.DUMP

Specifies whether to automatically copy dumps that match this entry from a SYS1.DUMPxx data set to another data set because the Abend-AID Viewer cannot automatically import dumps directly from SYS1.DUMPxx data sets. You must specify a data set naming pattern for the copy data set. See Specifying a Data set Naming Pattern (see Customizing the Abend-AID viewer dump capture) for more information. Valid values are:

3. Press the END (PF3) key on the Region Dump Profile screen to save your changes, or enter CANCEL to erase them.

4. If you added or changed a profile name, update the CICS region configurations for any CICS region that uses the profile. See Configuring Regions for more information.

5. If you need to specify a data set naming pattern because of your specific requirements, continue with Specifying a data set Naming Pattern.

Task 5: Specifying a data set naming pattern

You may have to modify the Region Dump Data set Information screen. This screen is used to specify a data set naming pattern for region dump data sets allocated by the Abend-AID  Viewer. You need to specify a pattern if:

• You entered USER (SDUMP to a user-defined data set) in the Dump Type field for any of your region dump profile statements. The data set naming pattern you specify is used when the Abend-AID Viewer allocates user SDUMP data sets.
• You entered Y in the Copy SYS1.DUMP field. The Abend-AID  Viewer allocates a data set name using this pattern when it copies dumps from a SYS1.DUMPxx data set.

 6.  To specify a naming pattern for these data sets, place the cursor on the tab-selectable data set field on the Region Dump Profile screen (See Region Dump Profile Screen), and press Enter. The Region Dump data set Information screen, shown in Region Dump data set InformationScreen, is displayed.Task 14.5  Specify a data set Naming Pattern

Region Dump data set Information Screen

7. On the Region Dump data set Information screen, specify the naming pattern and attributes for the region dump data sets. Press the HELP (PF1) key on any field for specific information.

The Region Dump data set Information screen displays the following input fields:

Data set Name

Specifies the data set naming pattern. You have three choices in the type of data set name you specify. Valid types of data set names include:

• A GDG (Generation Data Group). Make sure that a GDG index is created and that you specify (+1) after the data set name.
• A partially qualified data set name, using the Abend-AID Viewer symbolic qualifiers. The symbolic qualifiers available are:

If you use any of the symbolic qualifiers, the slash (/) is required. Separate them by using a period (.). For example:

    SYS2.MVS./JOBNAME./DATE./TIME

You can combine symbolic qualifiers with hard-coded qualifiers. In the above example, there are two hard-coded qualifiers — SYS2 and MVS. The actual job name, date, and time values are substituted for the symbolic qualifiers when the data set is allocated. For example, the data set above can be allocated as follows:

    SYS2.MVS.AAVWPROD.D94188.T094207

A fully qualified data set name. This type is not recommended because dumps copied or written to this single data set can be easily overlaid.

Space Units

Specify the unit of space allocation to be used for this data set. Valid values are:

Unit

Specifies the one- to eight-character esoteric DASD unit name on which to allocate the dump data set. This field is required for non-SMS data sets.

Primary Space

Specifies the primary space allocation for this data set.

For dumps taken to a user-defined data set, the space allocation must be contiguous. Only the primary allocation is used.

VOLSER

Specifies the volume serial number on which to allocate the dump data set. If you do not specify a volume serial number, the data set is allocated based only on the unit you specify.

Secondary Space

Specifies the secondary space allocation for this data set. This field is not valid for dumps taken to user-defined data sets.

Storage Class (SMS Only)

Specifies the SMS storage class for this data set allocation.

Management Class (SMS Only)

Specifies the SMS management class for this data set allocation.

8. When you have made your changes, press the END (PF3) key to save your changes and return to the Region Dump Profile screen, or enter CANCEL to erase them.

Task 6: Modifying Permanent CICS Transaction Dump Profiles

Both CICS transaction dump profiles and transaction dump global options, described in Modify CICS Transaction Dump Global Options (see Customizing the Abend-AID viewer dump capture) control the actions that Abend-AID for CICS takes when transaction abends occur. Transaction dump global options specify actions that are taken for all transaction abends in the CICS region. Transaction dump profiles can override certain transaction dump global option specifications for individual abend codes, transactions, programs, terminals, network names, operator IDs, user IDs, APPLIDs, or MVS SYSIDs, so that you have more control over exception conditions in your CICS regions.

There are two types of transaction dump profiles — permanent and temporary. Permanent transaction dump profiles are loaded by the CICS regions to which they are assigned when Abend-AID for CICS is initiated in the CICS region. Permanent transaction dump profiles are created and maintained using the online customization procedure, and are described below.

Temporary transaction dump profiles override any specifications made in permanent transaction dump profiles. They are created and maintained from CICS using a CICS transaction, and are active only for the life of the CICS region in which they are created, or until you stop Abend-AID for CICS. Temporary transaction dump profiles are described in the Abend-AID for CICS User Guide.

Specifications made in the transaction dump profiles (both temporary and permanent) control:

• Suppressing duplicate dumps.
• Capturing an IBM dump in addition to, or instead of, an Abend-AID dump. You can also choose to just write a directory entry for the dump, but not capture it.
• Capturing the last 3270 screen image associated with the abend.
• The extent of the CICS trace captured (complete, abending task only, or none).

These specifications can be made using a variety of criteria, including abend code, program name, transaction, terminal, NETNAME, operator ID, user ID, APPLID, MVS SYSID, or a combination of criteria.

Permanent Tran Dump Profile Screen

A sample Permanent Tran Dump Profile screen is shown in Permanent Tran Dump Profile Screen figure (see the following figure). The default transaction dump profile entry that you will see when you initially access the screen is blank. This means that, by default, nothing is considered an exception condition, and transaction dumps are processed for all abends according to the options specified in the transaction dump global options member assigned to each CICS region.

A distinction is made between a profile condition statement and a profile entry. A profile condition statement is a single line in the scrollable area of the Permanent Tran Dump Profile screen. A profile entry is one or more condition statements that comprise a single action (entry). Profile entries are delimited by a dashed line.

When multiple condition statements are grouped together in a single entry, include a comparison operator (AND or OR) on the first statement in the entry. The comparison operator is propagated to all statements in the entry, so you cannot mix AND and OR comparisons within an entry. AND is the default comparison operator.

Further, the Supp(ress) Dups, AA/CICS Dump, IBM Dump, Entry Only, L3270 Image, and CICS Trace options apply to all condition statements within a single profile entry, but are specified only on the first condition statement in the entry. The Permanent Tran Dump Profile screen supports a combined total of 175 profile entries and condition statements.

Modify Permanent Transaction Dump Profiles

To modify a permanent transaction dump profile member, complete the following procedure:

1.  Display the Dump Capture Profiles screen, shown in Dump Capture Profiles Screen figure (see the following figure), using one of two methods:
   • Tab to the CICS Transaction Dump Capture Profiles option on the Dump Capture and Processing Menu (See Dump Capture and Processing Menu for Abend-AID and Abend-AID for CICS ) and then press Enter.

   • Type TRANPROF or =2;3 in the COMMAND (or OPTION) field on any customization screen and press Enter. You cannot use these fast-path commands unless you have accessed the customization facility.
     Dump Capture Profiles Screen

     Customization ------------- Dump Capture Profiles -------------- Row 000001 of 000001
     COMMAND ===>                                                          SCROLL ===> CSR  
                                                                                                                                      
        S Select     R Replicate      D Delete                                                                                         
                                                                                                                                      
        Profile   Type    Description                                                                                                  
       ********  ******  ********************************                                                                             
     _  $DEFAULT  TRAN    DEFAULT TRANSACTION DUMP PROFILE                                                                             
       *********************** BOTTOM OF DATA ***********************************
2.  Display the Permanent Tran Dump Profile screen, shown in Region Dump data set Information Screen figure (see Dump Capture and Processing Menu for Abend-AID and Abend-AID for CICS) by selecting or replicating a transaction profile member name on the Dump Capture Profiles screen.
3.  If you displayed the Permanent Tran Dump Profile screen by replicating a member on the Dump Capture Profiles screen, enter a unique name in the Profile Name field and overtype the Description field with a unique name and description.
4. Press the HELP (PF1) key on any field for specific information.
5.  Create or modify condition statements or entries, as follows:

• 
  
  •      To modify existing information, simply type over the information with the new values, and then press Enter. The screen is refreshed with your new values.
  •      To create a new profile condition statement: 
  •      Enter I next to the statement after which the new statement is to be inserted, and then press Enter. The Permanent Tran Dump Profile screen is refreshed and displays the inserted line.

1.  Enter A next to the line after which you want the new entry inserted, and then press Enter. The Permanent Tran Dump Profile screen is refreshed and displays the inserted line, showing the BMC default value.  

   •  To create a new profile entry:

     Note

     Make sure that you are inserting the entry into an appropriate place, taking into consideration that the entries are processed in a top-down order from the table. There is no line command to move an entry, so if you put an entry in the wrong place, you must delete it and then add it in the correct place.

2. Overtype the inserted line with the new values.  
3. Repeat this process to add additional condition statements to the entry. Remember that the AND or OR comparison operator and the dump processing options (Supp(ress) Dups, AA/CICS Dump, and so forth) are specified only on the first condition statement of a multiple-condition statement entry.

The Permanent Tran Dump Profile screen displays the following input fields:

Resource

Specifies the item to be tested to determine whether these dump options apply. The item specified is tested against the literal each time an abend occurs, and if the condition is met, then the options specified are taken. Valid values are:

ABCODE: CICS transaction abend code (ASRA, AEIM, etc.).

APPLID: APPLID of the system on which the transaction executed.

NETNAME: Logical unit name of the terminal in the VTAM network.

OPID: Three-character OPID from the TCTTE.

PROGRAM: Program ID in control at abend.

SYSID: Name of the local CICS on which the transaction executed.

TERM: Terminal ID at abend.

TRAN: CICS transaction code at abend.

USERID: User ID signed onto the terminal.

Operator

Specifies the Boolean operator to be used to evaluate the resource for this dump entry. Valid values are:

EQ: Resource equal to literal.

NE: Resource not equal to literal.

LT: Resource less than literal.

GT: Resource greater than literal.

LE: Resource less than or equal to literal.

GE: Resource greater than or equal to literal.

Literal

Specifies the alphanumeric field to be used in the comparison to the resource to determine whether to apply these options. The string is automatically padded to the right with blanks to achieve the comparison length implied by the resource parameter. You can specify a generic value by using a single asterisk (*) as the last character, in which case the length of the comparison will be the string length without the asterisk.

The asterisk can be used only at the end of a partial field value, and not at the beginning or in the middle. Or, it can be used in place of the resource value, to indicate that all values qualify for the condition set. For example, ASR* could be used with ABCODE to mean any ASRx abend code.

AND/OR

Specifies the conditional operator for this dump entry. Valid values are:

AND: Default. All comparisons must match.

OR: Any comparison can match.

Supp Dups

Specifies whether to suppress duplicate dumps (or directory entries when Entry Only is set to Y) for reports which meet the criteria. The original dump is kept on the transaction database, but all subsequent duplicate dumps are suppressed until the duplicate dump expiration interval expires. History information for the 100 most recent duplicates is kept when this field is set to Y, A, or S. Valid values are:

Y: Default. Suppress all duplicate dumps.

N: Do not suppress duplicate dumps.

A: Suppress only duplicate ABEND dumps.

S: Suppress only duplicate SNAP dumps issued by EXEC CICS DUMP commands.

Specifies whether to take an Abend-AID dump. Valid values are: AA/CICS Dump

Y: Default. Abend-AID dumps are taken.

N: Abend-AID dumps are not taken.

IBM Dump

Specifies whether to take an IBM dump. Valid values are:

Y: IBM transaction dumps are taken.

N: IBM transaction dumps are not taken.

Entry Only

Specifies whether to bypass the Abend-AID for CICS dump and only make an entry for the dump on the Abend-AID Directory. Valid values are:

Y: Abend-AID for CICS makes an entry for this abend in the directory, but an Abend-AID for CICS dump is not taken. This option implies that N is also specified for the AA/CICS and L3270 Image options, and NONE for the CICS Trace option.

N: Default. Do not write only a directory entry for this abend. This value is ignored if the AA/CICS option is set to Y, which is the default.

L3270 Image

Specifies whether to capture the last 3270 screen displayed to the user. Valid values are:

Y: The last 3270 screen is captured if available.

N: The last 3270 screen is not captured.

Specifies the extent of CICS trace entries to capture when processing an abend. Valid values are: CICS Trace

NONE: No CICS trace entries are captured.

TASK: Only CICS trace entries for the abending task are captured.

FULL: All CICS trace entries are captured.

6. Press the END (PF3) key on the Permanent Tran Dump Profile screen to save your changes, or enter CANCEL to erase them.

7.  If you added or changed a profile name, update the region configurations for any CICS region that uses the profile. See Configuring Regions for more information.

Example

The sample Permanent Tran Dump Profile screen in Permanent Tran Dump Profile Screen figure here shows three profile entries: the first with two condition statements, and the second and third with one condition statement each.

Permanent Tran Dump Profile Screen

The first entry in the profile is:

This entry means that if CICS is about to take an ASRA dump for any program except one called MYPGM, (because the condition specifies PROGRAM is not equal to MYPGM), then Abend-AID is to do the following:

• Suppress the dump if it is a duplicate of one that has already been processed by Abend-AID.

• Capture dump information and perform Abend-AID analysis.
• Do not take an IBM dump.
• Do not write only a directory entry to the Abend-AID Directory (without capturing the dump information).Abend-AID

• Capture the last 3270 screen image.
• Do not capture any trace table entries.

The other two condition statements indicate what actions are taken IF a program called MYPGM is going to take any kind of a dump, and IF any abend code that begins with AEI is about to be taken.

Task 7:  Modify CICS Transaction Dump Global Options

For Abend-AID for CICS installations only, the transaction dump global options function controls Abend-AID functionality in a CICS region on a global basis. The transaction dump global options are maintained in named members that you assign to CICS regions on the Region Configuration screen.

A default CICS transaction dump global options member is supplied that provides recommended settings for the global options. The default settings should be sufficient for most sites.

To specify the CICS transaction dump global options, complete the following procedure:

1. Display the Transaction Dump Global List screen, shown in Transaction Dump Global List Screen figure (see the following figure)using one of two methods:

    - Tab to the Transaction Dump Global Options option on the Dump Capture and Processing Menu, and then press Enter.

    - Type TRANGBL or =2;4 in the COMMAND (or OPTION) field on any customization screen and press Enter. You cannot use these fast-path commands unless you have accessed the customization facility.

Transaction Dump Global List Screen

The Transaction Dump Global List screen displays all transaction dump global options members. When you initially access the screen, a $DEFAULT member is displayed. This member contains the default global option values supplied by BMC, and can be used as a template for the members you create. If the BMC defaults are acceptable to you, you do not have to do anything, and Abend-AID uses the default global options member.

2. If you want to create a new global options member, enter R next to an existing member. This replicates the definition of the existing member to use as a template for the new member. If you want to modify an existing profile member, enter S next to the member. For either selection, the Transaction Dump Global Options screen, shown in Transaction Dump Global Options Screen, Page 1 and Transaction Dump Global Options Screen, Page 2 figures is displayed as shown here.

To delete a global options member, enter D next to the member.

Transaction Dump Global Options Screen, Page 1

Press PF8 to scroll to the second screen.

Transaction Dump Global Options Screen, Page 2

3. Overtype any values you want to change with the new values. If you accessed the Transaction Dump Global Options screen by replicating a member on the Transaction Dump Global List screen, enter a unique name in the Global Name field and overtype the Description field.

The Transaction Dump Global Options screen displays the following options. For more information about any option, including the valid values for the option, press the HELP (PF1) key on the option field.

AAMSG

Controls automatic online access to Abend-AID information by displaying a message at the user’s terminal when an abend occurs. Valid values are:

N: Default. Do not display the message.

Y: Display the message.

Controls the number of abends that can be concurrently processed by Abend-AID. Five hundred bytes above the 16 megabyte line and 400 bytes below the 16 megabyte line are allocated during Abend-AID initialization in the CICS address space for each abend indicated by this parameter. This storage is freed when the Abend-AID is turned off. Additionally, for each abend, 6K is allocated above the line to capture the last 3270 screen. The last 3270 screen buffer is allocated and freed at the time the transaction dump is captured. ABLIMIT

Valid entries are 1 through 100. The default is 5.

ABQDUP

Specifies whether you want Abend-AID to suppress duplicate dumps in the CICS region when the region exceeds the limit of dumps to be processed concurrently. This limit is set in the ABLIMIT global option. Duplicate dump suppression is reset back to the original value when the ABLIMIT is no longer exceeded. This form of duplicate dump suppression is different than suppression that is controlled by the DUPABLIMT and DUPDUMPS global options. Suppression that is controlled by the ABQDUP global option is done entirely in the CICS region and is based on the following three criteria: transaction ID, program (load module), and abend code passed in the XDUREQ parameter list. Valid values are:

Y: Default. Abend-AID suppresses duplicate dumps in the CICS region when the ABLIMIT is reached. No IBM transaction dump is produced.

N: Abend-AID does not suppress duplicate dumps in the CICS region.

I: Abend-AID suppresses duplicate dumps in the CICS region when the ABLIMIT is reached. The IBM transaction dump is produced.

Specifies the time limit in wall clock seconds for data capture required for the Abend-AID transaction dump, excluding Db2 information. If this time limit is reached before data capture finishes, the Abend-AID report may be incomplete. If a Db2 abend is being processed, the DBTIME value is added to this value, and the sum is used as the total time limit for report data capture. Valid values are 10 through 300. The default is 120. ABTIME

APPLID

Specifies whether the CICS APPLID is used as a criterion in duplicate dump suppression. Valid values are:

Y: APPLID is used as a criterion.

N: Default. APPLID is not used as a criterion.

The criteria in effect are saved with the dump. Therefore, changing the APPLID value may result in another dump being taken because that dump would not be considered a duplicate. Subsequent dumps matching the criteria are suppressed.

BLLMAX

Specifies a limit on the number of BLL cells, per program, that are to be written to the transaction database. If you enter zero, the limit of 9999 is assumed.

Valid entries are 0 to 9999. The default is 0.

CICSACCESS

Specifies the type of access made to the viewing server from CICS when Abend-AID viewing is invoked using the AADF transaction. Valid values are:

LOCAL: Default. Cross-memory services are used to provide viewing access from the CICS region only if the CICS region and the viewing server region are running on the same MVS image.

REMOTE: LU 6.2 communication is used to provide viewing access from the CICS region. The CICS region and the viewing server region may be running on the same or on different MVS images.

If you select LOCAL viewing and the viewing server is not on the same MVS image as the CICS region, a message is issued and REMOTE viewing is attempted if it has been configured. Earlier versions of Abend-AID provided only remote viewing. Local viewing is now recommended if the CICS region and the viewing server region run on the same MVS image because the configuration is much easier.

CONNECTION

Specifies the CICS APPC connection name used to communicate with the Abend-AID viewing server for CICS remote viewing. You must also define the connection ID to each CICS region from which you are using CICS remote viewing access, as described in Review CICS Transaction Dump Global Option. Valid values are any one- to four-character name that is defined to CICS. The default is CCFX.

DBTIME

Specifies the time limit in wall clock seconds for capturing Db2 information. Elapsed time is measured. This parameter imposes restrictions on the amount of time Abend-AID spends reading Db2 catalog tables. When this parameter is used, dump capture is terminated prematurely if the time limit is reached and dump capture (including Db2) is not complete. Valid values are 1 through 1200. The default is 240.

DB2ENABLE

Specifies whether Db2 dump processing is enabled. Valid values are:

Y: Default. Db2 dump processing is enabled.

N: Db2 dump processing is not enabled.

DCFAILMSG

Specifies whether the message that states that dump capture has failed (TC4233) is displayed only in the FDBDLOG, or is displayed both in the FDBDLOG and on the system console. Valid values are:

N: Default. Display message TC4233 in the FDBDLOG only.

Y: Display message TC4233 in the FDBDLOG and also on the system console.

DMPITRACE

Specifies whether the internal trace buffers are written to the transaction database after the dump is processed. Valid values are:

N: Default. Do not dump the internal trace.

Y: Dump the internal trace.

DUPABLIMT

Specifies whether Abend-AID will force duplicate dump suppression when the CICS region exceeds the limit of concurrently processed dumps. This limit is set in the ABLIMIT global option. Duplicate dump suppression is reset to its original value when the number of concurrently processed dumps falls below 50 percent of the ABLIMIT value. Valid values are:

N: Default. Do not allow Abend-AID to force duplicate dump suppression when the ABLIMIT is reached.

Y: Allow Abend-AID to force duplicate dump suppression when the ABLIMIT is reached.

See DUPDUMPS below for more information about specifying duplicate dump suppression.

DUPDUMPS

Indicates whether dumps having the same abend code, program name, program offset, and transaction ID are suppressed. The original dump is kept on the transaction database, but all subsequent duplicate dumps are suppressed until the duplicate dump expiration interval expires. History information for the 100 most recent duplicates is kept when this field is set to Y, A, or S. Valid values are:

Y: Suppress all duplicate dumps.

N: Default. Do not suppress duplicate dumps.

A: Suppress only duplicate ABEND dumps caused by transaction abends.

S: Suppress only duplicate SNAP dumps issued by EXEC CICS DUMP commands.

DUPEXPIR

Specifies the expiration period for duplicate dumps in the units set by the DUPUNITS global option (see below). This parameter controls how many units are to elapse before a new dump is taken for a duplicate abend when duplicate dump suppression is active. If this value is set to 0, duplicate dumps never expire.

This option makes it easier to identify recurring abends while still suppressing most duplicates. For example, if this value is set to 7 and DUPUNITS is set to DAYS, duplicates are suppressed for 7 days (or 168 hours) from the original abend time. If a duplicate abend occurs after that time, one new dump is taken, and then suppression resumes for another 7 days. History information for subsequent duplicates is reported with this new dump. Valid values are 0 through 65,535. The default is 0.

DUPUNITS

Specifies the units used to determine the expiration of duplicate dump suppression. The number of units is determined by the value of DUPEXPIR.  Valid values are:

CALENDAR: Duplicate dump suppression is based on the number of changes in the calendar date occurring from the date the original dump occurred.

DAYS: Default. Duplicate dump suppression is based on a number of 24 hour periods elapsing from the time the original dump occurred.

MINUTES: Duplicate dump suppression is based on a number of minutes elapsing from the time the original dump occurred.

IBMDUMP

Specifies whether an IBM is to be taken. Valid values are:

Y: Default. IBM dump is taken.

N: IBM dump is not taken.

JOBNAME

Specifies whether the CICS job name is used as a criterion in duplicate dump suppression. Valid values are:

Y: Job name is used as a criterion.

N: Default. Job name is not used as a criterion.

The criteria in effect are saved with the dump. Therefore, changing the JOBNAME value may result in another dump being taken because that dump would not be considered a duplicate. Subsequent dumps matching the criteria are suppressed.

LESUPPORT

Specifies whether Abend-AID for CICS provides optional features for CICS transaction abends executing under Language Environment (LE).

N: Default. Do not provide optional LE support.

Y: Optional LE support is provided.

This option controls the LE optional support for the entire CICS region. See LE Support Considerations for information to help you determine when to set this option to Y.

Optional LE support provides the following features for a CICS transaction abend when executing under Language Environment:

• Discard duplicate dumps: When you code the LE option TERMTHDACT(UAONLY) or use an LE abnormal termination exit to force a CICS transaction dump for software-raised conditions, duplicate dumps normally occur for the same instance of an abend for common CICS abends such as ASRA and AEIx. The LESUPPORT global option eliminates these duplicate reports even if you do not use the DUPDUMPS global option or the Supp Dups transaction dump profile option to enable duplicate dump suppression. When these abends are discarded, no history information is maintained, and duplicate abend counts are not increased.

• Discard subsequent dumps: Discards subsequent abends that are identical to a previous one with the same abend code, program, and offset for the same task number. These abends are normally caused by LE, although they can be caused by application errors or by issuing the EXEC CICS DUMP command more than once from the same point in a program.

• Discard CESE trace entries: When you code the LE option, TERMTHDACT(UAONLY), to force a CICS transaction dump for software-raised conditions, LE dumps are normally written to the CESE transient data queue. These dumps create a large number of trace table entries that use a lot of space on the transaction databases, but are not needed by users. If you set the TRACE global option to TASK, the LESUPPORT option eliminates from the report many of the trace table entries related to writing the CESE entries.

L3270

Specifies whether Abend-AID for CICS captures the last 3270 screen image when a transaction abends at a terminal.

Y: Default. Capture the last 3270 screen image.

N: Do not capture the last 3270 screen image.

This option controls the last 3270 processing for the entire CICS region, but you can override it for individual conditions using permanent or temporary transaction dump profiles.

Specifies the time limit in seconds that Abend-AID for CICS is to wait for an outstanding terminal wait before capturing the last 3270 screen image when a transaction abends at a terminal. Abend-AID for CICS checks once every second until either the write is complete or the time limit is reached. Valid entries are 0 to 120. The default is 0. L3270WAIT

NBRSLS

Specifies the maximum number of source listing files to search for a program listing. Valid values are 1 through 88. The default is 8.

PLTCAPTURE

Optional. Specifies whether an Abend-AID for CICS dump is wanted for abends that occur during FIRSTQUIESCE of Shutdown PLT processing. CTCCJSTR should be placed just before DFHDELIM in the PLTSD table in order to capture abends from any other programs listed before it. Since no new tasks can be started, Last 3270 Screen and Db2 Information will not be available. Valid values are:

Y: An Abend-AID for CICS dump is wanted.

N: Default. An Abend-AID for CICS dump is not wanted.

SEGLEN

Specifies the maximum length in kilobytes of user storage segments to be dumped. Valid values are 0 through 9999. The default is 64.

Entering 9999 results in the dumping of all available storage. Overriding the default may create very large transaction entries in the transaction database. The dump may take longer to process, and DDIO file usage will increase. In particular, natural program abends dump large amounts of storage resulting in increased DASD usage. See BMC AMI Common Shared Services User/Reference Guide for DDIO file allocation size recommendations.

SLSDDN

Specifies a seven-character file ID (or an eight-character file ID to maintain compatibility with previous users of Abend-AID for CICS) for the first Abend-AID for CICS source listing file to substitute for SLSF001 (the default source listing file ID). Abend-AID for CICS determines additional source file DDnames by adding 1 to this DDname.

The last two characters must be numeric so that when searching for files at turn-on time these characters can be incremented by one until the maximum number of files specified in the NBRSLS option is reached. if the last character is not numeric, it will be forced to zero.

By default, the first file is SLSF001; the second file is SLSF002; the third file is SLSF003; and so on until the maximum number of files specified in NBRSLS is reached.

Each source listing file must have either a separate DD statement in the startup JCL or an RDO file entry. Start the numbering from 01, and ensure not to leave any gaps in the numbering.

SNAP

Specifies whether Abend-AID for CICS intercepts embedded DUMP requests. Optionally, Abend-AID for CICS can also intercept any dump requests made by the command-level EXEC CICS DUMP or the macro-level DFHDC call. Valid values are:

AB: Generates a report only for dump requests made from a SETXIT or HANDLE ABEND routine. All other requests are bypassed by Abend-AID for CICS and passed on to IBM dump control. To issue an ABEND request from the EXIT program, an EXEC CICS DUMP or DFHDC macro must be issued before the ABEND request in order to obtain the correct information about the original abend.

ALL: Default. Generates an Abend-AID for CICS report for all dump requests.

NO: Passes all embedded dump requests to IBM dump control with no intervention and no Abend-AID for CICS output.

Abend-AID for CICS Db2 users should specify SNAP=ALL so that Abend-AID for CICS output is produced for all non-zero SQL codes and DSNC transaction dumps.

TERMDEF

Specifies the method used to determine whether a terminal supports extended data streams when Abend-AID for CICS captures the last 3270 screen image. If the terminal supports extended data streams, the last 3270 image is captured in extended data stream mode. Valid values are:

QUERY: Default. The 3270 device query function is used to determine whether the terminal supports extended data streams.

ASSIGN: The EXEC CICS ASSIGN command is used to determine whether the terminal supports extended data streams. Correct terminal characteristics must be coded in the TCTTE.

NONE: Abend-AID for CICS assumes the terminal does not support extended data streams.

TERMID

Specifies whether the CICS terminal ID is used as a criterion in duplicate dump suppression. Valid values are:

Y: CICS terminal ID is used as a criterion.

N: Default. CICS terminal ID is not used as a criterion.

The criteria in effect are saved with the dump. Therefore, changing the TERMID value may result in another dump being taken because that dump would not be considered a duplicate. Subsequent dumps matching the criteria are suppressed.

TRACE

Specifies the scope of trace table entries captured by Abend-AID for CICS. Valid values are:

TASK: Default. Capture only the abending task’s trace entries.

FULL: Capture trace entries for all tasks in the region.

NONE: Do not capture any trace entries.

FAST: Capture only the abending task's trace entries.

Notes:

1. 
   
   1. The FULL option is not recommended because of the substantial DASD overhead to store the entries, and CPU cycles to process the entries.
      If you specify FULL, review the information in Dump Information File Reorganization.
   2. If you specify TRACE=FULL and DATASPACE=NO, trace entries are written last during dump capture. During the intervening time between abend and Abend-AID for CICS transaction dump capture completion, the trace table is still being updated by CICS, and important entries may be overwritten by the time Abend-AID for CICS captures the trace table. If you specify TRACE=TASK and DATASPACE=PARTIAL or ALL, trace entries are captured first during Abend-AID for CICS processing, avoiding this problem.
   3. The FAST option captures trace entries prior to identifying a transaction as a duplicate. Sites suppressing duplicates need to weigh the need for trace against additional processing being expended on duplicates.

   4. Contact BMC Support if you need further assistance.

   5. For performance reasons, except for AICA abends, options TASK and FAST capture trace entries for only the last 45 seconds of the transaction.

USERID

Specifies whether the CICS user ID is used as a criterion in duplicate dump suppression. Valid values are:

Y: CICS user ID is used as a criterion.

N: Default. CICS user ID is not used as a criterion.

The criteria in effect are saved with the dump. Therefore, changing the USERID value may result in another dump being taken because that dump would not be considered a duplicate. Subsequent dumps matching the criteria are suppressed.

4. Press the END (PF3) key on the Transaction Dump Global Options screen to save your changes, or enter CANCEL to erase them.

5. If you added or changed a member name, update the CICS region configurations for any CICS region that uses the global options member. See Configuring Regions (see Customizing the Abend-AID viewer dump capture) for more information.

6. You must stop and restart Abend-AID for CICS in each CICS region that uses this global options member for changes to take effect. See Using Supplied Abend-AID for CICS Transactions for more information.

Task 8: Modify CICS Transaction Dump Handler Profiles

To modify a dump handler profile, complete the following procedure:If you have Abend-AID for CICS installed, on the Region Configuration screen (option 1 on the Dump Capture and Processing Menu), you can assign regions (using job name, APPLID, and MVS SYSID as qualifiers) to use the $DEFAULT transaction dump handler profile or profiles you create. Multiple regions can use the same profile but if you don’t specify a profile, none is used. You can update the BMC-supplied default profile, but you cannot delete it.

1. Display the Dump Capture Profiles screen, shown in Dump Capture Profiles Screen for Transaction Handlers figure (see the following figure) using one of two methods:

   - Tab to the Transaction Dump Handler Profiles option on the Dump Capture and Processing Menu (see the following figure) and then press Enter.

    - Type HNDPROF or =2;5 in the COMMAND (or OPTION) field on any customization screen and press Enter. You cannot use these fast-path commands unless you have accessed the customization facility.

Dump Capture Profiles Screen for Transaction Handlers

The Dump Capture Profiles screen for transaction handlers lists the transaction dump handler profiles. When you initially access the screen, the $DEFAULT handler profile is displayed. This member contains the default profile values supplied by BMC and can be used as a template for profiles you create. If the BMC defaults are acceptable, you don’t have to do anything, and Abend-AID for CICS uses the default dump handler profile for region configuration entries that specify $DEFAULT in the Tran Dump Handlers field on the Region Configuration screen. The Dump Capture Profiles screen for transaction dump handlers supports a maximum of 2,031 entries.

2. The profile names are displayed in alphabetical order. Select a profile member to create, modify, or delete, as follows:

    - If you want to create a new profile member, enter R next to an existing member. This line command replicates the definitions of the existing member to use as a starting point for the new member.

The Transaction Dump Profile Handler screen is displayed. Then, complete the profile definition, specifying the following information:

• 
  
  • The profile name
  • A description of the profile
  • The program name
  • A description of the program.

     -  If you want to modify an existing profile member, enter S next to the member.

The Transaction Dump Profile Handler screen is displayed. Enter I next to a program name to add new entries, or overtype the data in any of the following fields for non-default entries:

• 
  
  • The program name
  • A description of the program.

     -  If you want to delete a non-default profile member, enter D next to the member.

     -  If you want to delete a non-default program entry from a profile member, enter D next to the program name on the Transaction Dump Profile Handler screen (See Transaction Dump Handler Profile Screen figure).

Press the END (PF3) key on the Transaction Dump Profile Handler screen to save your changes, or enter CANCEL to erase them.

Transaction Dump Handler Profile Screen

Duplicate Dump Suppression Processing

When a transaction abend occurs, Abend-AID for CICS makes a request to BMC AMI Common Shared Services (CSS) to determine whether the dump should be suppressed, using the criteria described below. CSS does the following:

• Determines if duplicate dump suppression is enabled through the SUPP DUPS transaction dump profile option and/or the DUPDUMPS transaction dump global option. If duplicate dump suppression is not enabled, a new dump is always taken.
• Determines if the abend is indeed a duplicate of an existing abend. If the entry does not already exist, CSS returns a dump number assigned to this new entry. If the entry is not a duplicate, a dump is taken.
• Determines if the abend is in the group of transaction database associated with the CICS region taking the abend. Abend-AID for CICS sites can assign specific transaction databases to be used by a CICS region. The set of transaction databases can be unique to the CICS region or can be shared by other CICS region. By default, a CICS region uses the entire set of transaction databases attached to the shared directory associated with the CICS region.
  When the request is made to create a new dump entry and CSS has determined that the abend is a duplicate, CSS then determines if the existing entry exists in a transaction database that has been associated with the region experiencing the abend. If the existing abend is in a transaction database that is not in the set of transaction databases associated with the CICS region, then the abend is not suppressed and a new dump is taken. When this situation occurs, duplicate entries can exist in the same shared directory.

• Determines if the duplicate entry is complete. When a new entry is created, the entry is initially marked incomplete. During the request, if duplicate dump suppression is enabled and a duplicate entry exists that is already in the set of transaction databases configured for the CICS region experiencing the abend, CSS suppresses any duplicates and gathers history that they are occurring simultaneously to the first dump. Within a BMC-specified time interval, a call is made to CSS to mark the abend entry complete. If it is, CSS continues to suppress duplicates. However, if after that time interval the first abend is not complete, CSS displays it as incomplete on the Abend-AID Directory, and an IBM dump is produced. The next occurrence of the abend is not suppressed, and a new dump is taken and processed.
• Determines if the existing abend has expired. If Abend-AID for CICS specified an expiration date on the dump creation request, CSS determines if the already existing abend entry has expired. If the elapsed time exceeds the expiration interval, then the abend is not suppressed and a new dump is taken.
• Suppresses the abend. At this point, CSS has determined to suppress the duplicate abend and update the existing abend history information. CSS then returns to Abend-AID for CICS a code indicating that the abend is a duplicate and that it should not be processed.

Accessing the Batch Customization Options

Display the Batch Customization menu, shown in Batch Customization Menu figure, using one of two methods:

• Tab to the Batch Customization option on the Dump Capture and Processing Menu, (See Dump Capture and Processing Menu for Abend-AID only figure) and then press Enter. Accessing the Customization Options Menu describes accessing the Customization Options menu.
• Type BATCUST or 6 in the COMMAND field on the Dump Capture and Processing Menu, (See Dump Capture and Processing Menu for Abend-AID only figure) and then press Enter.

Batch Customization Menu

Task 9:  Modify Batch Global Options

Access the Batch Global Option Groups screen, shown in the Batch Global Option Groups Screen figure by tabbing to the Batch Global Options option or by entering 1 on the Batch Customization menu.

The Batch Global Option Groups screen is used to specify global options for batch Abend-AID and associate each set with a group name. The group name references a set of criteria that is used to select the global options that will be in effect at the time an Abend-AID report is captured.

The $DEFAULT group contains the default global option values supplied by BMC, and can be used as a template for creating additional groups. The list of defined Batch Global Groups is shown on this screen along with a brief description of the group. From this screen, you can define, view, update, and delete the details of individual global option definitions.

The following line commands are available on this screen:

• S (Select): View and update a group's global option settings.
• D (Delete): Remove a group definition. You cannot delete the $DEFAULT group.  
• R (Replicate): Copy an existing set of global options, allowing you to update them and save them under a different name. Once a group has been created, the name cannot be changed.

Batch Global Option Groups Screen

To view the $DEFAULT global options and their values, enter S next to the default Group Name. The screen shown in the following figure is displayed. Use the PF7 (UP) and PF8 (DOWN) keys to scroll through the options.

Batch Dump Global Options Screen - Default Options

The Batch Dump Global Options screen displays the following default options. For more information about any option, including the valid values for the option, press the HELP (PF1) key on the input field.

AB400 Message (TAILOR THIS TO MATCH YOUR INSTALLATION):

HotKey WTO 1, HotKey WTO 2, HotKey WTO 3, HotKey WTO 4

The HotKey WTO fields are used to specify up to 55 characters of the first site-customized message line that will be displayed with every Abend-AID AB400 message.

A possible usage could be to describe the availability of the Abend-AID HotKey and how to use it to access the Abend-AID report using the HotKey.

You may also add a viewing server URL such as http://prod:1234/aaview.html. If your 3270 emulator recognizes the URL, users will be able to jump directly into the Abend-AID Web Browser Interface from where they can view the Abend-AID report.

Duplicate Dump Suppression:

Enable duplicate dump suppression (Y/N)

Specifies whether dump suppression is used. The following items are used to determine if a dump is a duplicate of an existing dump:

• 
  
  • Program name
  • Error offset with the program
  • Completion code
  • LE condition

This parameter can be used in conjunction with SYSID and/or JOBNAME to further limit duplicate dump suppression.

Valid entries are:

Expiration Time Unit

Specifies the units to be used to determine the expiration of duplicate dump suppression.

Valid entries are:

Expiration Time

Specifies the expiration interval of duplicate dumps.  This parameter controls how much time is to elapse before a new dump is taken for a duplicate abend when duplicate dump suppression is active.  If this value is set to 0, duplicate dumps never expire.  The value entered is dependent on the Expiration Time Unit value (see above).

This option makes it easier to identify abends that are recurring while still suppressing most duplicates.  For example, if this value is set to 7 and the Expiration Time Unit is set to C for calendar days, duplicates are suppressed for 7 days from today, resetting at midnight on the 7th day. If a duplicate abend occurs after that time, one new dump is taken, and then suppression resumes for another 7 calendar day changes. History information for subsequent duplicates is reported with this new dump.

Valid entries are:

Enable for SYSID

Specifies whether duplicate dump suppression is to be limited by system ID. Specifying a value for this field requires setting the Enable duplicate dump suppression (Y/N) option to YES.

This option can be used in conjunction with the Enable for JOBNAME option to further limit duplicate dump suppression.

Enable for JOBNAME

Specifies whether duplicate dump suppression is to be limited by job name. Specifying a value for this field requires setting the Enable duplicate dump suppression (Y/N) option to YES.

This option can be used in conjunction with the Enable for SYSID option to further limit duplicate dump suppression.

Site Specific Error Handler Programs (by CSECT name):

Use this list to specify the names of the general error routine programs that are called by several different application programs at your site in the event an application encounters an error.

Abend-AID will identify as the program-in-error the program calling one of these general error routine programs when, for example, it has been called, using standard save area linkage to issue an abend on behalf of its caller. Programs named in this list will not be identified by Abend-AID as a program-in-error.

Show the entire current record File Information:

Specifies the current record size display option. Valid entries are:

Show data management control blocks

Specifies the data management control block print option. Valid entries are:

Use JES2 formatting

Specifies a format for the File section. Valid entries are:

Provide IAM file Support

Provides Abend-AID support for Innovation Access Method (IAM) files. Valid entries are:

Show non-VSAM control blocks

Determines whether the control block information for non-VSAM files will be displayed.

Show both VSAM current records

When the I/O buffers differ, display the current record from both the system and application buffers.

The option is used to specify how Abend-AID will handle the display of the current records for VSAM files. It was implemented because multiple VSAM files can use the same buffer for I/O. The option applies only when the current record that is found in the application buffer (RPLAREA) is different than the current record found in the VSAM system buffer (PLHRECP).

With the default setting being NO, when the two current records differ, Abend-AID displays only the one found in the VSAM system buffer (PLHRECP) below the text heading, CURRENT RECORD IN SYSTEM BUFFER:. Users that want Abend-AID to display both of the current records should set this Global Option to YES.

Show QSAM IOBs and UCBs

Defines whether information on IOBs (Input Output Blocks) and UCBs (Unit Control Blocks) will be provided and written to the Abend-AID report file for open files.

Max number of JCL lines to display

Specifies how many submitted JCL lines to display in a report. Valid entries are:

SYSOUT Parameters:

Lines per page for Abend-AID report

Specifies the number of lines per page for the Abend-AID report. This option does not affect the output from the Abend-AID utility programs such as CWVERIFY or reports written to the Abend-AID report data sets. Valid entries are:

Use narrow column width format

Defines the width of the Abend-AID report written to //ABENDAID DD statements.

Product Information:

Free Abend-AID for IDMS work areas

Abend-AID for IDMS only. Determines whether the work areas that are acquired by Abend-AID for IDMS for each IDMS bind run unit are freed when a finish is issued. This option is intended to prevent potential S106 (out of memory) situations when an IDMS application program issues an excessive number of bind run units. Valid entries are:

IMS driver name

Abend-AID for IMS only. Specifies for Abend-AID the IMS driver name. Change this only if you have renamed DFSRRC00. Maximum eight characters. The first character must exist in the national character set. Remaining characters must be national character set or the numbers 0 to 9.

CA-1 TMS SVC value

Specifies the CA-1 (TMS) SVC number. Valid entry is:

Two-digit hexadecimal number corresponding to your site’s CA-1 (TMS) SVC number. F5 is the default.

Abend-AID supports system abends and associated return codes issued by CA-1 (TMS). Abend-AID uses this value to know if a system abend is a CA-1 (TMS) abend or an operating system abend.

Provide dump with SYSCHK DD

Allows you to request a dump if a program checkpoint, SYSCHK DD, is present. Valid entries are:

General:

Language type for report text

Specifies the Abend-AID report text language type. This option applies only to Abend-AID reports that are written to a SYSOUT destination.

The Abend-AID report text in an Abend-AID Viewer/Abend-AID Web Browser Interface report database is not affected by this option. The language type for an Abend-AID Viewer/Abend-AID Web Browser Interface report database can be specified in the user profile options panel at view time. Valid entries are:

Directory programmer name field option

Determines what will be displayed in the Description field on the Abend-AID Viewer/Abend-AID Web Browser Interface directory screens.

Note:   If the option selected is not relevant to a particular job, the default (P) programmer information will be displayed in the Description field.

Provide IBM dump, if application run minutes exceed

Specifies the number of minutes that a job is allowed to run before Abend-AID requests a dump. This option requests a dump for the abending steps that have run for the time limit specified. Valid entries are:

Display help text in Abend-AID report

Specifies the Help output option. Valid entries are:

Disable Abend-AID processing

Specifies the system disable option. Valid entries are:

Note:   If the Disable Abend-AID Processing CWGLOBAL option is set to Yes, and the //ABNLENAB DD statement is not used, include the following Abend-AID modules in the link list to avoid generating error message AB5A2:

Display diagnostic specific information

Display specific information in the Error Analysis section of the Abend-AID report for COBOL S0C7 and S0CB abends. Valid entries are:

Display Abend-AID memory utilization

Specifies whether to display Abend-AID’s memory utilization statistics.

Display additional data with Code Debug

Determines the amount of information that will be displayed when Abend-AID is invoked from Code Debug.

WTO with LE U4039 and no ABEND-AID

When using IBM's Language Environment (LE), a dump may be requested by Abend-AID to provide additional information for debugging. WTO messages can be written to the job log of the abending job to show that the dump was requested by Abend-AID issuing a 4039-8 abend.

Suppress second Abend-AID report in LE

Determines if Abend-AID should suppress duplicate in the Language Environment (LE).

WTO with non-zero dump and no Abend-AID

Determines if WTO messages will be displayed when a dump is produced with a non-zero ID and there is no Abend-AID report .

Suppress Abend-AID for Started Tasks

Determines if Abend-AID will be suppressed for Started Tasks.

Maximum element display for LE storage

This option limits the number of LE heap elements analyzed by Abend-AID.

Maximum SAS/C CSA length displayed

This option sets the length in bytes to use to format a SAS/C C program save area in the event that Abend-AID cannot determine the length by usual means.

Maximum DSAs displayed for LE U4083

This option limits the number of LE Dynamic Save Areas (DSAs) formatted by Abend-AID during the analysis and diagnosis of an LE U4083 abend.

Program Storage:

Display program storage section

Display the Program Storage section of the Abend-AID report. Valid entries are:

Use field wrapping in program storage

Applies to COBOL and PL/I Extended Language Support (XLS). Controls field wrapping when displaying program storage. This option takes effect at the time of the abend. Valid entries are:

COBOL external data display format

Specifies, for COBOL external data, the display format in the Program Storage section of the Abend-AID report. Valid entries are:

BL cell number display format

Specifies, for COBOL working storage, the display format of BL cell numbers in the Program Storage section of the Abend-AID report. Valid entries are:

Display BLL cells in program storage

Specifies, for COBOL linkage (BLL cells), whether to display the data in the Program Storage section of the Abend-AID report. Valid entries are:

COBOL programs to have source displayed

Applies to COBOL Extended Language Support (XLS). Specifies the display of program storage in the Program Storage section of the Abend-AID report and whether it will contain source support.

PL/I programs to have source displayed

Applies to PL/I Extended Language Support (XLS). Specifies the display of program storage in the Program Storage section of the Abend-AID report and whether it will contain source support.

Maximum NORENT CSECT display amount (K)

Specifies the maximum size of an Assembler/unknown-type non-reentrant CSECT, module, or program object that will be shown in the Program Storage section of the Abend-AID report. If the size exceeds this value, the amount shown will default to the size specified in Program Storage Display Limit (k).

Maximum RENT CSECT display amount (K)

Specifies the maximum size of an Assembler/unknown-type reentrant CSECT, module, or program object that will be shown in the Program Storage section of the Abend-AID report. If the size exceeds this value, the amount shown will default to the size specified in Program storage display limit (K).

Program storage display limit (K)

Specifies the amount of non-reentrant or reentrant source information that will be shown in the Program Storage section when the Maximum NORENT CSECT display amount (k) or Maximum RENT CSECT display amount (k) value is exceeded.

Program storage display around PSW (K)

Specifies the amount of program storage to be shown in the Program Storage section before and after a program PSW. This additional storage is only displayed if the maximum CSECT display amount has been met and the storage at the abending PSW was not previously dumped

Valid entries are:

Display COBOL storage no longer active

Validates and automatically includes TGT storage for COBOL modules no longer present on the active calling chain but which remain as a result of previous activity. Valid entries are:

Program Listing:

Active program listing display amount

Applies to COBOL and PL/I Extended Language Support (XLS). Specifies which part of the program source listing is displayed in the Program Listing section of the Abend-AID report for the active COBOL program or PL/I procedure. Valid entries are:

Inactive program listing display amount

Applies to COBOL and PL/I Extended Language Support (XLS). Specifies which part of the program source listing is displayed in the Program Listing section of the Abend-AID report for the inactive COBOL programs or PL/I procedures. Valid entries are:

Abend-AID DD Dynamic Allocation Parameters:

Use a DD as a model

Specifies whether to refer to CEEDUMP, SYSUDUMP, PLIDUMP, or the one that is specified under USEDDNM, as a model for the statement to be allocated, unless the model was dynamically allocated. See Model DD can be dynamically allocated below.

Model DD can be dynamically allocated

Specifies whether a model is used if the statement was dynamically allocated.

Model DD name to be used

Specifies a DD name to use as a model instead of CEEDUMP, SYSUDUMP, PLIDUMP, or PL1DUMP. Maximum eight characters. The Default is blank.

Hold the output class

Specifies whether to hold the SYSOUT data set.

Force free = close

Specifies whether the dynamically allocated DD is to use the free option from the allocation model or whether the FREE=CLOSE is forced.

Set free = close

Specifies whether the dynamically allocated DD will be freed when a close is done.

Dynamically allocated DD output class

Specifies the output class. The default is CLASS=*, which implies usage of the MSGCLASS value. Valid values are a digit from 0 to 9, an uppercase alphabetic character, or an asterisk (*), which implies usage of the MSGCLASS value.

Dynamically allocated DD user form

Specifies a user form to associate with the SYSOUT data set. Four alphanumeric or national characters maximum. This option is inactive unless specified. Two single quotes without a space (‘’) indicate that this option is set to blanks.

Dynamically allocated DD destination

Specifies a node to which the SYSOUT data set may be routed. Eight alphanumeric or national characters maximum. Use values applicable to your system’s output options. The default is LOCAL.

User ID for routing output

Specifies a user ID or remote at the destination node to which the SYSOUT data set may be routed. Use values applicable to your site’s user IDs, from one to eight alphanumeric or national characters. This option is inactive unless specified. Two single quotes without a space (‘’) indicate that this option is set to blanks.

Output writer for routing output

Specifies an output writer to process the output. Use values applicable to your site’s output writers, from one to eight alphanumeric or national characters. This option is inactive unless specified. If both User ID for routing output and Output writer for routing output are specified, only the user ID specified will be used.

Debug Options:

Note:   Contact BMC Support before using the following options.

Turn on #XAAMKDD debugging WTOs

Specifies whether write-to-operator (WTO) messages are to be issued to the job log of abending jobs. The WTO messages provide information about the dynamic allocation of the //ABENDAID DD.

Force an Abend-AID trace

Specifies whether to force an Abend-AID internal trace to be produced for abending jobs. The //ABNLTRAC DD is dynamically allocated. This option creates additional output and may impact Abend-AID performance..

Provide general WTO messages

Specifies whether to issue write-to-operator (WTO) messages to the job log of the abending job. The WTO messages provide general diagnostic information. This option creates additional output.

Use IEWBIND binder interface

Specifies whether Abend-AID is to use the IEWBFDAT Fast Data Access API instead of the IEWBIND Binder interface (default) to obtain module data.

Maximum size of DMPVH data(K)

Specifies the maximum amount of data to be available in the Abend-AID report. Changing this number affects the size of the Abend-AID reports. Valid values are:.

Linkage section format

Specifies which programs are to have a formatted linkage section when the Abend-AID report is viewed. Valid values are:.

Dump additional storage

Specifies whether additional application storage is to be written to the Abend-AID report data set.

Task 10:  Modify Global Criteria Entries

Access the Batch Global Criteria Update screen, shown in the following figure using one of the following methods:

• Tab to the Batch Global Criteria Table option on the Batch Customization menu and press Enter.
• Enter 2 on the Batch Customization menu.
• Tab to the CRITERIA field on the Batch Global Option Groups screen and press Enter.

Batch Global Criteria Update Screen

Use the Batch Global Criteria Update screen to create and maintain criteria information entries that specify which batch global options are associated to which batch dumps. The criteria entries are evaluated in the order displayed on the screen, from first to last. When an abending job matches all defined criteria fields, the global options for that group are used to process the Abend-AID report. The remaining criteria entries are not tested for a match.

BMC provides a default entry. When you initially access the screen, the $DEFAULT entry is displayed. This entry contains the default values supplied by BMC, and it can be used as a template for the entries you create.  

You can do the following actions on this screen:

• To update or view an existing entry, enter the S (Select) line command next to it.
• To insert a new entry before an existing one, enter the I (Insert Before) line command next to it. You will be presented with a blank screen where the data may be entered.
• To copy an existing entry, enter the R (Replicate) line command next to it. This command replicates the existing entry to use as a template for the new one.
• To delete an entry, enter the D (Delete) line command next to it. You cannot delete the $DEFAULT entry.
• To rearrange the entries, enter the M (Move Row), A (After This Row), or B (Before This Row) line command next to an entry.

If you enter the S, I, or R line command next to an existing entry, the Batch Global Criteria Options screen, shown in the following figure is displayed

The Batch Global Criteria Options screen is used to define, view, and update the details of a specific global criteria definition. You can update all of the criteria options from this screen. If a field is left blank, it will not be used in the criteria matching.

You can specify Wild card characters in any of the fields. A percent character (%) can be used to specify one, and only one, positional character. An asterisk (*) can be used to specify zero to many characters.  

For example:

*AB in the Job Name field would match if the characters AB were in any position of the job name.

%AB in the Job Name field would match if the second character was A and the third character was B.

Press the END (PF3) key to save your changes, or type CANCEL to ignore them.

Batch Global Criteria Options Screen

Task 11: Modify Report Database Groups

Access the Batch Report DB Groups screen, shown in  the following figure  by using one of the following methods:

• Tab to Batch Report Database Options on the Batch Customization Menu and press Enter.
• Enter 3 on the Batch Customization Menu.

Batch Report DB Groups Screen

The Batch Report DB Groups screen is used to specify the report routing option for Abend-AID and to associate each set with a group name. The group name references a set of criteria that is used to select the routing options that will be in effect at the time an Abend-AID report is captured.

The $DEFAULT group contains the default report and listing shared directories and can be used as a template for creating additional groups.

The list of defined Batch Report DB Groups is shown on this screen along with a brief description of the group. From this screen, you can define, view, update, and delete the details of individual routing option definitions.

You can do the following actions on this screen:

• Enter the S (Select) line command to view and update a group's routing option settings.
• Enter the R (Replicate) line command to copy an existing set of routing options, allowing you to update them and save them under a different name. Once a group has been created, the name cannot be changed.
• Enter the D (Delete) line command to remove a group definition. You cannot delete the $DEFAULT group.

If you enter the S or R line command next to an existing entry, the Batch Report DB Options screen, shown in the following figure is displayed.

Batch Report DB Options Screen

Use the Batch Report DB Options screen to specify options for controlling where Abend-AID report output is routed for the selected group. The group name is used to associate these routing options with a specific set of batch report routing criteria. You can specify an optional 32-byte description to help identify the options.                                                                     

You must specify a single report shared directory data set name. All Abend-AID reports will be written to a report database attached to this report shared directory.                                                            

In addition to writing the Abend-AID report to a report database, you can also route a 72-column formatted report to SYSOUT.

You can optionally specify that report databases restrict the output to be written to specific report databases. All included report database data sets must be attached to the specified report shared directory. The listed order of the report databases data sets is unimportant. If no database files are defined, any report database attached to the report shared directory is eligible to be written to.

You can do the following actions on this screen:

• To insert a report database entry after an existing entry, enter the I (Insert) line command next to the existing entry.
• To delete an existing report database entry, enter the D (Delete) line command next to the desired entry.
• Enter the END command or press the END (PF3) key to save all updates and return to the previous screen.
• Enter the SAVE command to save all updates and redisplay the same screen.
• Enter the CANCEL command to return to the previous screen ignoring prior updates.

Task 12: Modify Routing Criteria Entries

Access the Batch Routing Criteria Update screen, shown in the following figure by using one of the following methods:

• Tab to the Batch Routing Criteria Table option on the Batch Customization menu and press Enter.
• Enter 4 on the Batch Customization menu.
• Tab to the CRITERIA field on the Batch Report DB Groups screen and press Enter.

Batch Routing Criteria Update Screen

The Batch Routing Criteria Update screen is used to create and maintain criteria information entries that specify which batch report groups are associated to which batch dumps. The criteria entries are evaluated in the order displayed on the screen, from first to last. When an abending job matches all defined criteria fields, the report options for that group are used to process the Abend-AID report. The remaining criteria entries are not tested for a match.

BMC provides a default entry. When you initially access the screen, the $DEFAULT entry is displayed. This entry contains the default values supplied by BMC, and it can be used as a template for the entries you create.

You can do the following actions on this screen:

• To update or view an existing entry, enter the S (Select) line command next to it.
• To insert a new entry before an existing one, enter the I (Insert Before) line command next to it. You will be presented with a blank screen where the data may be entered.
• To copy an existing entry, enter the R (Replicate) line command next to it. This command replicates the existing entry to use as a template for the new one.
• To delete an entry, enter the D (Delete) line command next to it. You cannot delete the $DEFAULT entry.
• To rearrange the entries, enter the M (Move Row), A (After This Row), or B (Before This Row) line command next to an entry.

If you enter the S, I, or R line command next to an existing entry, the Batch Routing Criteria Options screen, shown in the following figure is displayed.

Batch Routing Criteria Options Screen

The Batch Routing Criteria Options screen is used to define, view, and update the details of a specific report database criteria definition. You can update all of the criteria options from this screen. If a field is left blank, it will not be used in the criteria matching.

You can specify Wild card characters in any of the fields. A percent character (%) can be used to specify one, and only one, positional character. An asterisk (*) can be used to specify zero to many characters.  

For example:

*AB in the Job Name field would match if the characters AB were in any position of the job name.

%AB in the Job Name field would match if the second character was A and the third character was B.

Press the END (PF3) key to save your changes, or type CANCEL to ignore them.

Task 13: Modify Batch Dump Capture Profiles

Batch Abend-AID global options control the actions that Abend-AID takes when batch job abends occur. Batch dump global options specify actions that are taken for all batch abends.

The batch dump profile can override certain batch dump global option specifications for individual abend codes, job names, programs, user IDs, or MVS SYSIDs, so that you have more control over exception conditions in your batch regions. The batch dump profile is maintained using the online customization procedure described below. Once the profile is updated, the new option takes effect immediately.

You can make specifications in the batch dump profile to control what kind of action is taken when a duplicate dump occurs. These specifications can be made using a variety of criteria, including abend code, job name, program name, user ID, MVS SYSID, or a combination of criteria.

A sample Batch Dump Profile screen is shown in in the following figure. The default batch dump profile entry that you will see when you initially access the screen is blank. This means that, by default, nothing is considered an exception condition, and batch dumps are processed for all abends according to the options specified in the batch dump global options.

A distinction is made between a profile condition statement and a profile entry. A profile condition statement is a single line in the scrollable area of the Batch Dump Profile screen. A profile entry is one or more condition statements that comprise a single action (entry). Profile entries are delimited by a dashed line.

Batch Dump Profile Screen

When multiple condition statements are grouped together in a single entry, include a comparison operator (AND or OR) on the first statement in the entry. The comparison operator is propagated to all statements in the entry, so you cannot mix AND and OR comparisons within an entry. AND is the default comparison operator.

Further, the Suppr(ess) Dups option applies to all condition statements within a single profile entry, but is specified only on the first condition statement in the entry. The Batch Dump Profile screen supports a combined total of 175 profile entries and condition statements.

To modify a batch dump profile member, complete the following procedure:

1. Display the Dump Capture Profiles screen, shown in following figure using one of two methods:
   1. Tab to the Batch Dump Capture Profiles option on the Batch Customization menu, and then press Enter.
   2. Type 5 in the OPTION field on the Batch Customization menu and then press Enter.

Dump Capture Profiles Screen for Batch Dumps

2. Display the Batch Dump Profile screen, by selecting a batch profile member name on the Dump Capture Profiles screen.

3. Press the HELP (PF1) key on any field for specific information.

Batch Dump Profile Screen

4. Create or modify condition statements or entries, as follows:

a. To modify existing information, simply type over the information with the new values, then press Enter. The screen is refreshed with your new values.

b. To create a new profile condition statement:

     Enter I next to the statement after which the new statement is to be inserted, and then press Enter. The Batch Dump Profile screen is refreshed and displays the inserted line.

c. Overtype the inserted line with the new values.

d. Repeat this process to add additional condition statements to the entry. Remember that the AND or OR comparison operator and the Suppr(ess) Dups dump processing option are specified only on the first condition statement of a multiple-condition statement entry.

–To create a new profile entry:

a. Enter A next to the line after which you want the new statement inserted, and then press Enter. The Batch Dump Profile screen is refreshed and displays the inserted line with the BMC default values.

b. Overtype the added line with the new values.

c. To add additional condition statements to an entry, enter the I line command next to the condition statement after which the new statement is to be added. Overtype the values displayed with the new values. Remember that the AND or OR comparison operator and the Suppr(ess) Dups dump processing option are specified only on the first condition statement of a multiple-condition statement entry.

The Batch Dump Profile screen displays the following input fields:

Resource

Specifies the item to be tested to determine whether these dump options apply. The item specified is tested against the literal each time an abend occurs, and if the condition is met, then the options specified are taken. Valid values are:

ABCODE: Batch abend code (S0C1, S0C4, SNAP, etc.).

JOBNAME: Name of the abending job.

PROGRAM: Program ID in control at abend.

SYSID: System ID name where the abending job was executed.

USERID: User ID for the submitted job.

Operator

Specifies the Boolean operator to be used to evaluate the resource for this dump entry. Valid values are:

EQ: Default. Resource equal to literal.

NE: Resource not equal to literal.

LT: Resource less than literal.

GT: Resource greater than literal.

LE: Resource less than or equal to literal.

GE: Resource greater than or equal to literal.

Literal

Specifies the alphanumeric field to be used in the comparison to the resource to determine whether to apply these options. The string is automatically padded to the right with blanks to achieve the comparison length implied by the resource parameter. You can specify a generic value by using a single asterisk (*) as the last character, in which case the length of the comparison will be the string length without the asterisk.

The asterisk can be used only at the end of a partial field value, and not at the beginning or in the middle. Or, it can be used in place of the resource value, to indicate that all values qualify for the condition set. For example, S0C* could be used with ABCODE to mean any S0Cx abend code.

AND/OR

Specifies the conditional operator for this dump entry. Valid values are:

AND: Default. All comparisons must match.

OR: Any comparison can match.

Ignore Abend

Specifies whether Abend-AID is to ignore abends that meet the specified criteria. Valid values are:

N: Default. Abend-AID processes this abend.

Y: Abend-AID ignores this abend.

Suppr Dups

Specifies whether to suppress duplicate dumps that meet the criteria. History information for the 100 most recent duplicates is kept. Valid values are:

N: Default. Do not suppress duplicate dumps.

Y: Suppress all duplicate dumps.

Example

The sample Batch Dump Profile screen in the following figure shows three profile entries: the first with two condition statements, and the second and third with one condition statement each.

Sample Batch Dump Profile Screen

The first entry in the profile is:

   (Implied IF)  ABCODE  EQ S0C*   AND
                PROGRAM NE MYPGM

This entry means that if the system is about to take a SNAP dump for any program except one called MYPGM, (because the condition specifies PROGRAM is not equal to MYPGM), then Abend-AID is to process the dump and suppress any dump if it is a duplicate of one that has already been processed by Abend-AID.

The other two condition statements indicate what action is taken IF a program executed by user ID TSOUSER3 abends, and IF a program with JOBNAME TEST abends.

Task 14: Define a Default Remote Server

The Remote Server Definition screen, shown in  the following figure, lets you enter one remote server name to be used a default when the IDR source file name is not found on the local system. Display this screen using one of two methods:

• Tab to the Remote Server Definition option on the Dump Capture and Processing Menu and then press Enter.
• Type REMSRVR or 7 in the COMMAND field on the Dump Capture and Processing Menu and then press Enter.

Remote Server Information Screen

This screen displays the current viewing server name. You can specify a remote server name to be used as the default for IDR source files names that are not resident on the current viewing server.

Task 15: Define Remote Source Listings to Remote Servers

The Remote Source Information screen, shown in the figure below lets you define remote source data sets to remote servers. Display this screen using one of two methods:

• Tab to the Remote Source Information option on the Dump Capture and Processing Menu and then press Enter.
• Type REMSRC or 8 in the COMMAND field on the Dump Capture and Processing Menu and then press Enter.

Remote Source Information Screen

You can enter up to a maximum 200 entries. You can do the following actions on this screen:

• To insert a new entry before an existing one, enter the I (Insert) line command next to it.
• To copy an existing entry, enter the R (Replicate) line command next to it. .
• To delete an entry, enter the D (Delete) line command next to it.
• Enter the END command or press the END (PF3) key to save all updates and return to the previous screen.
• Enter the SAVE command to save all updates and redisplay the same screen.
• Enter the CANCEL command to return to the previous screen ignoring prior updates.