Ideally, the appropriate resolution to this problem scenario would have been for the customer to RESTORE their CADDSPLx LDS environment in it's entirety, from a backup that was taken just prior to the attempted APPEND. CA always recommends taking backups of the CADDSPLx and CA Dispatch environments prior to attempting to make any changes of this nature, especially in a PRODUCTION environment.
However, given the problem scenario and taking into account that the "APPEND12" LDS file had not actually had any report data written to it, the customer was able to resolve the problem(s) by executing the following process:
1. Delete any "APPEND12" files that currently remain out on DASD.
2. Run IDCAMS JCL job (NOT CADDUTIL utilty) outside of CA Dispatch to reallocate the "APPEND12" file with the EXACT SAME SIZE and attributes as the "original" APPEND12 file from item (A) of the problem scenario.
Note - DO NOT specify the size from item (B) of the problem scenario. The INTERNAL ROOT LDS TABLE entry for "APPEND12" believes the size for this file to be the size resulting from the original successful execution of the CADDUTIL utilities INIT function.
3. Run the CA Dispatch provided CADDUTIL utilty with the INIT function to allocate and initialize a new "APPEND13" file with the EXACT SAME SIZE and attributes as the original APPEND12 file from item (A) of the problem scenario.
4. Then, using standard IDCAMS, either setup and run a job or manually "REPRO" the initialized "APPEND13" file into the un-initialized APPEND12 file from item 2 above. This will add the required initialization seed record into the "APPEND12" LDS file. The initialization seed record is not specific to the NAME of an LDS file.
After performing the above process, the CADDSPLx environment will restart successfully, and will now recognize BOTH the new APPEND12 and APPEND13 LDS files.