On Thu, 28 Jan 2016 15:36:46 -0500, Tony Harminc wrote:
>On 28 January 2016 at 15:16, Paul Gilmartin wrote:
>> Description
>> The IDENTIFY macro is used to add an entry name to a copy of a load
>> module
>> currently in virtual storage. The copy must be one of the following:
>>
>> A copy that satisfied the requirements of a LOAD macro issued during the
>> execution of the current task.
>>
>> The last load module given control, if control was passed to the load
>> module
>> using a LINK, LINKX, ATTACH, ATTACHX, XCTL, or XCTLX macro.
>
>Surely that's describing limitations on what you can add an entry
>point *to*. I don't believe it puts any restrictions on the address
>for the entry name you are adding, except perhaps that the new address
>may have to be compatible with the current RMODE and/or AMODE. And of
>course you can't add an entry name that duplicates one in LPA, etc.
>etc. But surely it is not a requirement that your new EP be within the
>bounds of the added-to module.
>
Looking further at:
z/OS 2.1.0>z/OS MVS>z/OS MVS Programming: Assembler Services Reference
IAR-XCT>IDENTIFY - Add an entry name
There's no parameter that identifies "what you ... add [the] entry point *to*"
I assume the function can identify this only by examining Content Supervision
control blocks to determine which module contains the new EP.
I suspect they're trying to protect against sequences such as:
GETMAIN; IDENTIFY; FREEMAIN; ATTACH.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
