LOAD allows GLOBAL=YES,EOM=NO to put the module in CSA. Or you could use MVS commands to add the module to MLPA and activate it as an exit. .
Jon Perryman. >________________________________ > From: Peter Relson <rel...@us.ibm.com> > > > >>If I understand the processing for this exit, the exit >>routine must be in common storage (e.g., LPA or CSA) if >>you specify MODADDR on the CSVDYNEX ADD macro. So unless >>your LOAD is satisfied from LPA I doubt that this will >>work properly. > >Walt is correct, with the addition of "unless you use the STOKEN keyword >(or possibly the JOBNAME keyword if there is no duplication of the >specified jobname in the system) to specify the single address space in >which the exit routine is to get control". And even STOKEN would be wrong >if this were an initiator address space and the LOAD occurred within the >job step. > >Going beyond that, it makes no sense to do the LOAD and then use MODADDR >in just about any situation unless the specified module is present only in >a tasklib/steplib/joblib known to the LOAD and not in the LNKLST or LPA. >It makes no sense to add an exit routine of name CSVLLIX1 both because >that is the name owned by the customer not any individual application and >because z/OS will add that by default in the normal case. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
