Database support configuration tasks — new installation
Do one of the following:
- If your site is not licensed for Abend-AID/Abend-AID for CICS support for Db2, IDMS, or IMS, go to Configure Workbench for Eclipse integration.
- If your site is not licensed for BMC AMI DevX Workbench for Eclipse go to Verify Abend-AID configuration.
The following Roles are involved for these tasks:
- Abend-AID installer
- Abend-AID for CICS installer
- Db2 database administrator
- IDMS database administrator
Perform the following tasks to configure database support:
Db2 database support configuration task — new installation
Task 1: Complete the Db2 database support screens
Perform the following steps to complete the Db2 database support screens:
- Access the Abend-AID Configuration and Customization Dialog again, or use the END (PF3) key to navigate to the products configuration menu.
Enter S (Select) to the left of the Configure Database Support option.
The screen shown in following figure is displayed.----------- Abend-AID Installation: Site-specific Database Support -----------
Command ===>
The Abend-AID installation requires site-specific information to complete
the installation for database options for which you are licensed.
Type an S next to the desired option and press ENTER.
DB2 Support
IDMS Support
No further action is required for Abend-AID IMS Support
For Abend-AID DB2 Support enter the following:
Abend-AID Load Lib ===> ‘SYS1.CPWR.MPAA170.SPAALOAD’
AA Customization Load Lib ===> 'SYS1.CPWR.MPAA170.CUST.LOAD'
For Abend-AID for CICS DB2 Support enter the following:
AA/CICS Load Lib ===> ‘SYS1.CPWR.MKFX171.SKFXLOAD’
NOTE: If you clear the values for either Abend-AID or Abend-AID for CICS,
DB2 IVP jobs will not be created for those products.- Verify that the displayed Abend-AID/Abend-AID for CICS load library names and the Abend-AID customization load library name are correct for your site.
Enter S to the left of the Db2 Support option.
The screen in following figure is displayed.---------------- Abend-AID Installation: Generated DB2 Support Row 1 to 2 of 2
Command ===>
Abend-AID DB2 Plan Name ===> CWDB2PLN
Line commands: 'e' = edit, 'i' = insert(add), 'r' = replicate, 'd' = delete
Line --- DB2 Information --- ------- DB2 Installation JCL --------
Cmd Subsystem Release Plan Generated? Date Time User
---- --------- ------- -------- ----------- -------- -------- --------
D121 12.1 CWDB2PLN NO
******************************* Bottom of data *********************************Enter the I (Insert) line command in the Line Cmd field to display the screen shown following figure.
-------------- Abend-AID Installation: Site-specific DB2 Support --------------
Command ===>
Abend-AID DB2 Plan Name ===> CWDB2PLN
DB2 Subsystem ID ===> D121 DB2 Release ===> 12.1
Collection ID ===> AAGENTST
Database ===> AADB
Tablespace ===>
AATS DB2 Load Library ===> 'DSN1210.SDSNLOAD'
DB2 Application Load Lib ===> 'DSN1210.D1201.RUNLIB.LOAD'
DB2 Exit Library ===> 'DSN1210.D1201.SDSNEXIT'
DB2 Stored Proc Load Lib ===> 'DSN1210.D1201SPS.LOAD'
WLM Environment Name ===> 'DSN1210.WLMLOAD'
NOTE FOR DB2 10 AND ABOVE USERS:
Does this site use the new function mode of DB2 10? or higher? ===> Y (Y/N)
Previously generated JCL ===>
Edit maintenance "bind plan" JCL? ===> N (Y/N)
Enter "generate" on command line to create the installation JCL.- Complete the fields with valid values for your site.
- Enter generate on the command line to generate the configuration jobs listed in the hlq.CTL member $$DB2LOG.
Task 2: Implement Db2 support
Depending on your site’s security requirements, your Db2 administrator may be required to run$21nxxx and $22nxxx.
Review, edit, and submit according to the comments in the JCL the following hlq.CTL library member $$DB2LOG jobs to bind the Abend-AID/Abend-AID for CICS DBRMs:
$21nxxx: Based on the information input during the generation of the JCL, this job installs, assembles, and links the hlq.CTL library module CWDB2OPT.
It also binds the Abend-AID/Abend-AID for CICS for Db2 DBRMs into PLAN/PACKAGES, where n represents the one-numeric character Db2 release identifier and xxxx is the four-alphanumeric character Db2 subsystem ID. The Abend-AID/Abend-AID for CICS DBRMs are hlq.SKAZSAMP library members ACDBnnn, where nnn represents the Db2 release.
hlq.CTL library module CWDB2OAS has been included in the event that CWDB2OPT needs to be assembled and linked outside of the $21nxxxx JCL job.- $22nxxx: This job binds Abend-AID/Abend-AID for CICS for Db2 maintenance using PLAN or PLAN PACKAGE support, where n represents the one-numeric character Db2 release identifier and xxxx is the four-alphanumeric character Db2 subsystem ID.
Task 3: Additional required tasks for Abend-AID for CICS Db2 support only
Do one of the following:
- If you are not licensed for Abend-AID Db2 support, but are licensed for other Abend-AID database support, go to IDMS Support Configuration Tasks and/or IMS Support Configuration Tasks.
- If your site is not licensed for any other Abend-AID database support, proceed to Configure Workbench for Eclipse Integration.
- If your site is not licensed for BMC AMI DevX Workbench for Eclipse, proceed to Verify Abend-AID Configuration.
Perform the following required tasks forAbend-AID Db2 support:
Grant Privileges for the Db2 Plan.
Abend-AID Granting Privileges for for Db2 Plan describes the choices you have for granting privileges for the Db2 plan. The AUTHID to which you grant privileges must match the AUTHTYPE parameter you specify on the RDO entry.
Abend-AID Granting Privileges for for Db2 PlanAUTHID
Privileges Granted
Binder of the plan
No privileges granted
Not specified
AADB or PUBLIC
SIGNID
AADB or PUBLIC
TXID/TX
AADB or PUBLIC
Specific User
Privileges granted to the user
- Add an RDO Entry.
- The Abend-AID Db2 option requires an entry in the CICS system definition data set (CSD). If you haven’t already done so, add the entry now.
Specify the Db2 Handle Routine (Optional).
The Abend-AID Db2 option generates output for non-zero SQL return codes. However, you must specify the action taken when an SQL code is returned. For non-zero SQL return codes, an EXEC CICS DUMP or EXEC CICS ABEND must be issued to generate the Abend-AID information. The following example produces an Abend-AID analysis and continues processing. You may want to distribute a copy of this example to your site’s application programmers.EXEC SQL WHENEVER SQLERROR
GOTO 9998-HANDLE-DB2-ERROR
END-EXEC.
.
.
.
9998-HANDLE-DB2-ERROR
.
.
.
EXEC CICS DUMP
DUMPCODE (’DB2E’)
END-EXEC.
.
.
.
EXEC CICS SYNCPOINT ROLLBACK
END-EXEC.
.
.
.
EXEC CICS RETURN
END-EXEC.The code EXEC CICS DUMP can be changed to EXEC CICS ABEND to stop processing. The programmer chooses the dump code to be used, and whether to issue an EXEC CICS RETURN. Always use EXEC CICS DUMP when SYNCPOINT rollback is a recovery requirement.
Keep the transaction dump global option SNAP set to ALL (the default) to ensure that the EXEC CICS DUMP command produces Abend-AID for CICS output. The transaction dump global options are described in the Abend-AID Advanced Configuration.
IDMS support configuration tasks — new installation
Do one of the following:
- If you are not licensed for Abend-AID for IDMS support, but are licensed for Abend-AID for IMS support, go to IMS Support Configuration Tasks.
- If your site is not licensed for Abend-AID for IMS support, go to Configure Workbench for Eclipse integration.
- If your site is not licensed for BMC AMI DevX Workbench for Eclipse, proceed to Verify Abend-AID configuration.
Perform the following steps to configure IDMS support tasks:
- Access the Abend-AID Configuration and Customization Dialog again, or use the END (PF3) key to navigate to the products configuration menu.
- Enter S (Select) to the left of the Configure Database Support option.
The screen shown in Abend-AID site-specific database support menu is displayed. Enter S to the left of the IDMS Support option.
The screen in following figure is displayed.-------------- Abend-AID Installation: Site-specific IDMS Support -------------
Command ===>
Enter parameters below specific to your site to complete the installation of Abend-AID support for IDMS.
Select applicable IDMS release for your site:
IDMS 18.50 ===> Y (Y/N)
IDMS 19.00 ===> N (Y/N)
IDMS Load Library ===> 'IDMS.LOADLIB'
Jobcard Info:
===> //XXXXXXXX JOB ('AAAAAA',BB),'AA SMP/E INSTALL',
===> // class="L",MSGCLASS=R,MSGLEVEL=(1,1),NOTIFY=&SYSUID
===> //* OPTIONAL JES PARAMETER CARD COULD GO HERE
===> //*
Enter "generate" on command line to create the installation JCL.- Complete the screen fields.
Specify the IDMS releases installed at your site, the IDMS load library data set name, and the job card information. - Enter generate on the command line to create the $31IDMS1 JCL listed in the hlq.CTL member $$IDMLOG.
Implement Abend-AID for IDMS support
Perform the following steps to implement CA-IDMS 18.50 or more current:
Review, edit according to the comments in the JCL, and submit hlq.CTL member $31IDMS1.
Member $31IDMS1 is generated to link the Abend-AID for IDMScode with the IDMS module IDMSIDMS.- Member JCLIDMST in the Abend-AID Common Components sample library hlq.SKAZSAMP should have been copied to your installation sample library hlq.CTL during SMP/E installation. If not, copy it now. Edit the JCLIDMST member to conform to your installation's requirements. Follow the instructions in that member for what needs to be changed. Submit the job, and verify that member #XAAIDTB has been created in your hlq.CUST.LOAD library.
- Relink COBOL programs that access a CA-IDMS 18.5 or more current database that are still linked with CA-IDMS 10.2 or less current subschemas.
- Because they need to use the new IDMSIDMS hook, relink any COBOL programs for which Abend-AID is unable to provide CA-IDMS database diagnostic information.
- Relink any non-COBOL programs.
IMS support configuration tasks — new installation
If your site is not licensed for Abend-AID for IMS support, proceed to Configure BMC AMI DevX Workbench for Eclipse integration.
If your site is licensed for Abend-AID for IMS support, all necessary modules were included on the product installation media. No special installation procedure is required for this optional database support facility. Abend-AID for IMS is automatically installed with Abend-AIDbasic support.
However, if your site is running programs in the IMS Transaction Manager (IMS/DC) and is experiencing performance issues, review the next section for BMC's recommendations. or ask your IMS database administrator to do so.
IMS online performance considerations
During Abend-AID processing, BMC AMI Common Shared Services (CSS) issues exclusive enqueues on the selected report database and its first data block during the following phases of the Abend-AID dump-capture process:
- Creation of a new member
- Allocation of another group (blocks in file) for a report member
- Close of a member
- Auto-deletion of a member.
For batch program abends, the overhead required for this processing is negligible. However, during times of unusually high abnormal terminations associated with programs running in the IMS Transaction Manager (IMS/DC), the overhead can be significant. For programs running in the IMS Transaction Manager (IMS/DC) consider doing the following measures to minimize the impact of enqueues on your IMS/DC environment:
- Attach at least five databases to your report shared directory. Doing so allows BMC AMI Common Shared Services (CSS) to assign a different database for the Abend-AID report in case one or more are busy with an enqueue.
- Change your global options to enable duplicate dump suppression. See “Task 9 Modify Batch Global Options” in the Accessing-the-dump-capture-options for more information.
- Determine the number of IMS/DC Abend-AID reports to retain in your report databases using the following steps:
- Decide the number of days your organization wants to retain reports.
- Determine the number of IMS/DC Abend-AID reports your organization typically experiences per day.
Apply the following formula to determine the number of reports to hold in your report databases.
Number of reports in all databases = Number of reports per day x Number of days + 20%
- Allocate the aggregate size of your report databases to be large enough to hold the number of reports determined in the previous step. You can use the DDIOCALC command for help with this number. Refer to the BMC AMI Common Shared Services (CSS) User/Reference Guide for details about DDIOCALC.
Set up a daily batch job that executes the BMC AMI Common Shared Services (CSS) utility CWDDALLU (formerly, CWAASDUT) to delete reports older than the number of days your organization wants to retain reports. Doing so has the effect of deferring AUTODELETE processing to a batch job, rather than performing it during Abend-AID processing. Refer to the BMC AMI Common Shared Services (CSS) user/reference guide for details about CWDDALLU.
You can accomplish the deferred AUTODELETE processing at the shared directory level by applying the same criteria to all databases attached to a shared directory, or at the database level by applying different criteria to different databases.
To operate at the shared directory level, use the DELETE command.
To operate at the database level, use the EXPORT command.