PTF LU04287 has a ++HOLD action statement to run the IDB2XAIX Job in order to create a VSAM alternate index for the exception definition file.
After the execution of the IDB2XAIX Job is it possible to continue to use the EXCPDEF file with an old name?.
The EXCPALT is only the alternate index related to that, is that correct?.
Release : 20.0
Component : SYSVIEW Performance Management Option for DB2 for z/OS
The IDB2XAIX Job is optional. Following PTF LU04287 all exception definitions contain a unique 8 byte name. This allows for the EXPORT and IMPORT of exception definitions to be run in batch. The purpose of the alternate index is to ensure that the name remains unique.
If there are no plans to utilize the EXPORT and IMPORT functions, and no action is taken to rename individual exceptions this step can be skipped.
If the IDB2XAIX Job is run, the original VSAM cluster name to name the file will continue to be used and no changes to the DC SYSPARMS or JCL are needed.
The name of the alternate index is never explicitly specified.
Note that the Data Collector must be brought up with the new maintenance (PTF LU04287) before running the IDB2XAIX Job, since the Data Collector will assign the names on the first Data Collector startup after the maintenance is applied, and the names must be present for the alternate index to be properly built.