User Exit(s) quit working after applying Repository Maintenance
Article ID: 39308
Updated On:
Products
Issue/Introduction
Issue:
Customized User Exit(s) quit working after applying Repository maintenance.
The User Exit(s) were working fine before application of the Repository
fixes via SMPe.
Cause:
If the Repository fix(s) that are being applied deliver new object module(s)
that result in a relink of DBEXCEL, then any customized user exit
programs previously linked into DBEXCEL will be wiped out.
Resolution:
Relink the Customized User Exit(s) into the DBEXCEL load module after applying
Repository maintenance. See below for an example.
Contact CA Support to determine if any specific
fixes will result in a relink of DBEXCEL and thus will require a relink of
any user exit(s).
ex.
//*In this example COBEXIT and DBXEXIT are the user exit programs that are
//*being relinked into DBEXCEL
//SYSLIN DD *
INCLUDE OBJLIB(COBEXIT)
INCLUDE OBJLIB(DBXEXIT)
INCLUDE SYSLIB(DBEXCEL)
INCLUDE DB2LIB(DSNALI)
ENTRY CEESTART
MODE AMODE(31)
MODE RMODE(ANY)
NAME DBEXCEL(R)
/*
Additional Information:
Refer to Chapter 20 ‘Working with User Exists’ in the CA Repository for z/OS r7.2 Admin Guide. As a best practice, it is recommend to Receive and Apply any user exit(s) to your CSI via SMP/E as documented in Chapter 20. By doing so, manual relinks of any user exit(s) will not be necessary. SMP/E will manage and relink as necessary. Failure to use SMP/E to manage user exit(s) will require manual relinks as documented above.
Environment
Component:
Feedback
