Activating Auditing for TP Monitors

#### Search Results

Search

# Activating Auditing for TP Monitors

The following sections describe how to activate auditing for TP monitors.

Note
If you wish Natural-related client information to be included in the auditing data, then you must ensure that the Natural Profile parameter `ADAPRM=ON` is set.

- Installing Adabas Auditing under Com-plete

- Installing Adabas Auditing under CICS

- Installing Adabas Auditing under Batch/TSO

- Installing Adabas Auditing under IMS/TM

- Adabas Auditing and Adabas Review

## Installing Adabas Auditing under Com-plete

To prepare the Adabas link routine:

1. Copy sample member LCOGBL (provided in the `ADAvrs.SRCE` library) to any appropriate user source library where it can be modified.

2. Modify the LGBLSET parameters in the copied LCOGBL member according to your site requirements ensuring the parameter `AUDIT=` is added and set to YES.

3. Modify sample job ASMGBLS provided in the `ADAvrs.JOBS` library as described at the top of the job. When fully modified, the SET statement in the job should reference the LCOGBL member you prepared in the previous step, and the NAME link edit control statement should reference the name specified by the GBLNAME parameter within that member.

4. Once modified, submit the ASMGBLS job to assemble and link-edit the link globals module. A new link globals module with the name specified by the GBLNAME parameter will be generated in the user load library identified in the ASMGBLS job.

5. Copy sample job LNKLCO8 provided in the `ADAvrs.JOBS` library to a user source library.

6. Modify the sample job LNKLCO8 to link the new link globals module you created along with the following INCLUDE statement:

       INCLUDE ALALIB(EABXCOM)

   where ALALIB references the `ALAvrs.LOAD` library.

   Note
   Instructions for modifying the sample job are described at the top of the job. Be sure to direct the output from the job to an appropriate user load library. The module resulting from this job is called ADALCO.

7. Place the newly linked ADALCO module in a load library available to the Com-plete job.

For general information regarding the installation of Adabas with Com-plete and an explanation of the associated LGBLSET parameters, refer to the Adabas for Mainframes documentation > Installing Adabas with TP Monitors.

## Installing Adabas Auditing under CICS

To prepare the Adabas link routine:

1. Copy sample member CICSGBL (provided in the `ACIvrs.SRCE` library) to any appropriate user source library where it can be modified.

2. Modify the LGBLSET parameters in the copied CICSGBL member according to your site requirements ensuring the parameter `AUDIT=` is added and set to YES.

3. Modify sample job ASMGBLS (provided in the `ADAvrs.JOBS` library) as described at the top of the job. When fully modified, the SET statement in the job should reference the CICSGBL member you prepared in the previous step, and the NAME link edit control statement should reference the name specified by the GBLNAME parameter within that member.

4. Once modified, submit the ASMGBLS job to assemble and link-edit the link globals module. A new link globals module with the name specified by the GBLNAME parameter will be generated in the user load library identified in the ASMGBLS job.

5. Copy sample job LNKGCICS (provided in the `ACIvrs.SRCE` library) to a user source library.

6. Modify the sample job LNKGCICS to link the new link globals module you created along with the following INCLUDE statement:

       INCLUDE ALALIB(EABXCIC)

   where ALALIB references the `ALAvrs.LOAD` library.

   Note
   Instructions for modifying the sample job are described at the top of the job. Be sure to direct the output from the job to an appropriate user load library that will be made available to CICS in the DFHRPL library concatenation.

For general information regarding the installation of Adabas with CICS and an explanation of the associated LGBLSET parameters, refer to the Adabas for Mainframes documentation > Installing Adabas with TP Monitors.

## Installing Adabas Auditing under Batch/TSO

To prepare the Adabas link routine:

1. Copy sample member LNKGBLS (provided in the `ADAvrs.SRCE` library) to any appropriate user source library where it can be modified.

2. Modify the LGBLSET parameters in the copied LNKGBLS member according to your site requirements ensuring the parameter `AUDIT=` is added and set to YES.

3. Modify sample job ASMGBLS (provided in the `ADAvrs.JOBS` library) as described at the top of the job. When fully modified, the SET statement in the job should reference the LNKGBLS member you prepared in the previous step and the NAME link edit control statement should reference the name specified by the GBLNAME parameter within that member.

4. Once modified, submit the ASMGBLS job to assemble and link-edit the link globals module. A new link globals module with the name specified by the GBLNAME parameter will be generated in the user load library identified in the ASMGBLS job.

5. Copy sample job LNKLNK8 (provided in the `ADAvrs.JOBS` library) to a user source library.

6. Modify the sample job LNKLNK8 to link the new link globals module you created along with the following INCLUDE statement:

       INCLUDE ALALIB(EABXMVS)

   where ALALIB references the `ALAvrs.LOAD` library.

   Note
   Instructions for modifying the sample job are described at the top of the job. Be sure to direct the output from the job to an appropriate user load library. The module resulting from this job is called ADALNK.

7. Place the newly linked ADALNK module in a load library available to the Batch/TSO job.

For general information regarding the installation of Adabas with Batch/TSO and an explanation of the associated LGBLSET parameters, refer to the Adabas for Mainframes documentation > Installing Adabas with TP Monitors.

## Installing Adabas Auditing under IMS/TM

To prepare the Adabas link routine:

1. Copy sample member LNIGBL (provided in the `AIIvrs.SRCE` library) to any appropriate user source library where it can be modified.

2. Modify the LGBLSET parameters in the copied LNIGBL member according to your site requirements ensuring the parameter `AUDIT=` is added and set to YES.

3. Modify and run sample job ASMGBLS (provided in the `ADAvrs.JOBS` library) as described at the top of the job. When fully modified, the SET statement in the job should reference the LNIGBL member you prepared in the previous step, and the NAME link edit control statement should reference the name specified by the GBLNAME parameter within that member.

4. Once modified, submit the ASMGBLS job to assemble and link-edit the link globals module. A new link globals module with the name specified by the GBLNAME parameter will be generated in the user load library identified in the ASMGBLS job.

5. Copy sample job LNKLNI8 (provided in the `AIIvrs.SRCE` library) to a user source library.

6. Modify the sample job LNKLNI8 to link the new link globals module you created along with the following INCLUDE statement:

       INCLUDE ALALIB(EABXIMS)

   where ALALIB references the `ALAvrs.LOAD` library.

   Note
   Instructions for modifying the sample job are described at the top of the job. Be sure to direct the output from the job to an appropriate user load library. The module resulting from this job is called ADALNI.

7. Place the newly linked ADALNI module in a load library available to the IMS MPP regions.

For general information regarding the installation of Adabas with IMS/TM and an explanation of the associated LGBLSET parameters, refer to the Adabas for Mainframes documentation > Installing Adabas with TP Monitors.

## Adabas Auditing and Adabas Review

If you wish to install Adabas Auditing under a TP monitor which currently has Adabas Review installed, please observe the following points:

1. Your existing LGBLSET Review-related parameters (`REVIEW=`, `REVHID=`, `RVCLNT=`) should be maintained. This is in addition to the `AUDIT=YES` parameter required to install Adabas Auditing.

   Note
   The parameter values `REVIEW=COR` and/or `RCVCLNT=COR` are not currently compatible with `AUDIT=YES` therefore replace these parameter values with `REVIEW=YES` and/or `RVCLNT=YES` accordingly.

2. In your TP monitor Adabas link job which link-edits the Adabas link globals module with the Adabas Review TP monitor component, replace the Adabas Review component with the corresponding Adabas Auditing component according to the following table:

   TP Monitor | Adabas Review Component | Adabas Auditing Component
   --- | --- | ---
   Com-plete | RDBLXCOM | EABXCOM
   CICS | RDBLXCIC | EABXCIC
   Batch/TSO | RDBLXMVS | EABXMVS
   IMS/TM | RDBLXIMS | EABXIMS

3. If you have installed REVUEX1 (Review User Field User Exit), then you will have previously linked your user exit to the appropriate Adabas Review TP monitor component using the sample member LREVUEX1 (provided in the `REVvrs.JOBS` library). Use this same sample member to link your user exit to the equivalent Adabas Auditing TP monitor component. Refer to the table above for the names of the corresponding components.

### On this page

- Installing Adabas Auditing under Com-plete
- Installing Adabas Auditing under CICS
- Installing Adabas Auditing under Batch/TSO
- Installing Adabas Auditing under IMS/TM
- Adabas Auditing and Adabas Review