While there are also other advantages to CSVDYLPA (like creating a CDE,
so that SLIP and IPCS can find the module by name), we likely would 
consider it incompatible to change the documented meaning of the 
LOADTOGLOBAL option on the IEFSSIVT macro.   Adding a new 
IEFSSIVT option to use CSVDYLPA would be more palatable.
Unfortunately, the code for the dynamic SSI functions in 
MVS/ESA SP5,2.0 was written in a prototype internal Object Oriented
language, which is now an effectively dead language (no longer 
supported, and very few developers who speak it).  So that adds to
the degree of difficulty for doing SSI enhancements. 

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. 
Poughkeepsie NY

John McKown <john.archie.mck...@gmail.com> wrote on 11/29/2017 01:53:00 
PM:
 12:37 PM, Jim Mulder <d10j...@us.ibm.com> wrote:
> 
> >   IEFSSVT was created in MVS/ESA SP5.2.0, before the existence of
> > CSVDYLPA,  which was created in OS/390 2.4.
> >
> 
> That makes sense. And, since it works well, there's never been any real
> need to update the internals. Hum, I wonder if someone could argue that
> continuing to use the LOAD instead of CVSDYLPA is some sort of 
"exposure",
> even though it is documented.
> 



----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to