A small follow-up to my earlier reply. The PMAR structure is also laid out by the IGWSMDE macro, which invokes IEWPMAR internally. If you are already mapping the SMDE for DESERV return data you already have all of the PMAR structures.
Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Farley, Peter x23353 Sent: Saturday, December 1, 2018 3:45 AM To: [email protected] Subject: Re: Where is the EPA offset of a program in the Binder API data? Thank you Peter! I missed that even though I called myself doing a very careful RTFM. Makes sense now that I think about it. DESERV returns the PMAR data following the SMDE entry and likely gets the same data from the same place (though I realize it is not necessarily getting the data via the GUPI interface). Thanks again for the on-target answer. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Peter Morrison Sent: Saturday, December 1, 2018 2:16 AM To: [email protected] Subject: Re: Where is the EPA offset of a program in the Binder API data? Peter, You can read the PMAR using the binder API. I had a similar problem trying to find out where information that is in the PDS(E) directory is for a program object in a unix file. It turns out that the information is embedded in the program object, but, of course, the internal format for a program object has not been decoded (yet?) If you look at the binder API description, you will see that you can rear the information by using the GETD Call, using a class name of B_PMAR - the returned data must be described by a buffer that uses the TYPE=PMAR option. Note that the actual PMAR data in the buffer must be mapped using the IEWPMAR macro. Be aware of the program object level - according to the documentation the PMAR is a different length for some. Peter Morrison -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
