To answer specifically:
-- A module added to LPA is never automatically deleted.
-- A module added by LOAD with GLOBAL=YES always has a defined
circumstance at which point it is deleted (it could be task termination,
it could be address space termination).
So we highly recommend using dynamic LP
On Wed, Nov 29, 2017 at 3:28 PM, Jim Mulder wrote:
> 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 IEFS
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
On Wed, Nov 29, 2017 at 12:37 PM, Jim Mulder 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
IEFSSVT was created in MVS/ESA SP5.2.0, before the existence of
CSVDYLPA, which was created in OS/390 2.4.
Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp.
Poughkeepsie NY
John McKown wrote on 11/29/2017 11:50:46
AM:
> I'm guessing that LOADTOGLOBAL literally means "LOAD
Behalf
Of John McKown
Sent: Wednesday, November 29, 2017 8:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: CSVDYLPA ADD question.
I'm looking at example #1 here:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa100/iea3a1_Description18.htm#dylpaxm
What I'm t
I'm looking at example #1 here:
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa100/iea3a1_Description18.htm#dylpaxm
What I'm thinking of is in regards to a subsystem (SSI) initialization
which occurs after IPL (i.e. not via the IEFSSNnn member of PARMLIB). The
ab