At 21:46 -0800 on 01/25/2006, Keith E. Moe wrote about Identify Macro:
The problem is that programs "created" via IDENTIFY cannot be
deleted or otherwise made to disappear until task (I think)
termination. Even
if the module that it is identified against is deleted, the IDENTIFY
Entry Point remains.
I had somewhat the same problem in that I had a Job Step program
that I used IDENTIFY against to create an alternate entry point for a
subtask attach. Because there was the possibility of attaching the
subtask multiple times, I wanted to IDENTIFY, ATTACH, DETACH, and
DELETE, making the subtask processing independent of the first
versus subsequent times. But you can't DELETE an IDENTIFY entry
point.
I assume that when your main program starts up it does some one time
housekeeping (setting up a Save Area or saving to the Linkage Stack,
etc) before it gets into the main processing code. Why not do the
LOAD there and save the entry address there and in the main loop just
load the entry address and use it for the ATTACH? That way all the
ATTACHs are the same since the LOAD is not in the processing loop.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
