Trouble installing the LDXEVX01 Driver Security Exit on the mainframe where ZAP job fails

  • 7017363
  • 14-Mar-2016
  • 14-Mar-2016

Environment

NetIQ Identity Manager 4.5
NetIQ Identity Manager Driver - Mainframe RACF Bi-directional

Situation

Having trouble installing the LDXEVX01 Driver Security Exit on the mainframe. Cannot locate the source.  Attempted to run the supplied Zap job, SAMPLIB(ZAPEVX01), applying the zap against the supplied load module in LOAD(LDXEVX01). The job fails.

The Mainframe system in question is "RELEASE z/OS 01.13.00", the product appears to be "V3.6". Attached is the abend output from the JCL(see below) from the Samplib.

//*

//* THIS SAMPLE JOB CHANGES THE SPECIFIED NUMBER OF LDX ENTRIES THAT

//* WILL BE ALLOWED TO ACCUMULATE IN THE CSA QUEUE (WHEN THE IRREVX01

//* EXIT IS QUEUING ENTRIES TO THE LDX QUEUE BUT LDXLOGR IS NOT LOGGING

//* THEM) BEFORE THE WARNING MESSAGE, LDX9998E IS ISSUED. IT ALSO

//* CHANGES THE SPECIFIED NUMBER OF LDX ENTRIES THAT WILL BE ALLOWED TO

//* ACCUMULATE IN THE CSA QUEUE BEFORE 'CUTOFF' MESSAGE LDX9999E IS

//* ISSUED, AND QUEUING OF LDX ENTRIES IS SUSPENDED.

//*

//* SUPERZAP OF LDXEVX01 LOAD MODULE TO CHANGE THE WARNING

//* AND CUTOFF THRESHOLDS FOR MESSAGES LDX9998E AND LDX9999E.

//*

//PLEASE EXEC PGM=OMASPZAP,REGION=2M,PARM=IGNIDRFULL

//SYSPRINT DD SYSOUT=*

//SYSLIB DD DSN=SYS2.LDXRAC.V4540821.LOAD.ZAP,DISP=SHR

//SYSIN DD *

*

* THIS SAMPLE JOB CHANGES THE SPECIFIED NUMBER OF LDX ENTRIES THAT WILL

* BE ALLOWED TO ACCUMULATE IN THE CSA QUEUE (WHEN THE IRREVX01 EXIT IS

* QUEUING ENTRIES TO THE LDX QUEUE BUT LDXLOGR IS NOT LOGGING THEM) BE-

* FORE THE WARNING MESSAGE, LDX9998E IS ISSUED. IT ALSO CHANGES THE

* SPECIFIED NUMBER OF LDX ENTRIES THAT WILL BE ALLOWED TO ACCUMULATE IN

* THE CSA QUEUE BEFORE 'CUTOFF' MESSAGE LDX9999E IS ISSUED, AND QUEUING

* OF LDX ENTRIES IS SUSPENDED.

*

NAME LDXEVX01 LDXEVX01

VER 07BC 4040F16BF0F0F000 /* VERIFY WARNING VALUE TO BE 1,000 */

REP 07BC 40404040F5F0F000 /* REPLACE WARNING VALUE WITH 500 */

VER 07C4 40F1F06BF0F0F000 /* VERIFY CUTOFF VALUE TO BE 10,000 */

REP 07C4 4040F26BF0F0F000 /* REPLACE CUTOFF VALUE WITH 2,000 */

//*

Resolution

Use the following command:

  NAME LDXEVX01 LDXEVX01                                             

  VER  07B4 4040F16BF0F0F000  /* VERIFY WARNING VALUE TO BE   1,000 */

  REP  07B4 40404040F5F0F000  /* REPLACE WARNING VALUE WITH     500 */

  VER  07BC 40F1F06BF0F0F000  /* VERIFY CUTOFF  VALUE TO BE  10,000 */

  REP  07BC 4040F26BF0F0F000  /* REPLACE CUTOFF  VALUE WITH   2,000 */

//*

Cause

The 4.5 code had different displacements than the 4.0.x branch and the new offsets were not put in the ZAP modules.