At 14:29 -0600 on 01/06/2012, Staller, Allan wrote about Re: Error apply ZAP:
First the IDR (forget what the acronym stands for) is an optional list of zaps applied to this module (load module?). Due to the structure of the directory, IIRC, you are limited to 19 IDR entries per module (load module?). The IDR data is set by an AMASPZAP control statement. IDENTIFY. The message AMA120I message below may be safely ignored. It is indicated that there is no space left to record additional IDR information. The only impact of this is that it will make it difficult to determine which zaps have already been applied.
If you relink as the AMA120I suggests/instructs the Binder adds another (empty) IDR record so you can use the IDENTIFY statement (think this is automatic although it may be triggered by supplying a Binder command to add more IDR Space). As you note, this allows you to track what ZAPs have been installed. If I remember IDR is ID Record. There are IDR records for each CSECT in the Load Module (they come from the Assembler) so you can see what the assembly date of the CSECT is (there is only one for the last linkedit).
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
