Sorry, I tried to type "PDS(E)" but the "(E)" became a Euro symbol in my mail client. PDS/E was a substitute name, not a product. I should have switched the format to plain text.
But the question still remains -- Where (if anywhere) is an EPA indicator in the returned Binder API data? I know the EPA Is in the directory entry, but where is it in the Binder data? If it matters, I am using INTENT=ACCESS for the BINDER session. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Greg Price Sent: Friday, November 30, 2018 11:31 AM To: [email protected] Subject: Re: Where is the EPA offset of a program in the Binder API data? On 2018-11-30 4:01 AM, Farley, Peter x23353 wrote: > The PDS/E directory entry for a program contains, among other information, > the EPA offset within the program. > > The EPA offset is also contained in the SMDE/PMAR information returned by > DESERV. > > After much RTFM however, I cannot seem to find anywhere in the Binder API > data areas an indication of which section/label is the entry point for the > program. > > In particular, I would have expected that an LD entry in the ESD table would > contain such an indicator, but I do not see one anywhere. Wasn't PDS/E the first commercial version of free PDS command? PDS/E was later renamed PDSTOOLS and then StarTool, IIRC. Both a PDS and a PDSE program member directory entry contain the EPA offset. Typically the EPA is chosen from label and section ESDs because it matches a real or alias member name, or was explicitly named on a Binder ENTRY statement, or was some sort of default. I think that no change is made to the relevant external symbol's recorded details as a result of being selected to be the entry point. Often a tool will report one of several symbols with matching offsets as the entry point simply because it was the first symbol found which had the correct offset, even if the reason the entry point was chosen was because of another symbol at the same offset address. I'll propose that it's a bit like a NOTE list TTR stored in the directory entry. Such a TTR may record the location of an "important" block within the member, but the block itself is not changed simply because something recorded its location. Cheers, Greg P. -- 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
