The MLPA is key zero and it's bad form to put nonrefreshable code there, but it is not always read only. Unlike PLPA, it is subject to page out.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Joe Monk <[email protected]> Sent: Friday, September 18, 2020 12:55 PM To: [email protected] Subject: Re: Searching MLPA module Thats incorrect. MLPA is read only. Joe On Fri, Sep 18, 2020 at 9:42 AM Itschak Mugzach < [email protected]> wrote: > MLPA is in CSA and is modifiable while lpa is read only. > > בתאריך יום ו׳, 18 בספט׳ 2020, 17:17, מאת Peter <[email protected]>: > > > Apology for being ingorant .. if LPA and MLPA are same then why are they > > being placed in a different parmlibs ? Aren't any difference between MLPA > > and LPA ? > > > > On Fri, 18 Sep, 2020, 5:56 pm Peter, <[email protected]> wrote: > > > > > We have a MLPA module from adabas which got loaded But we aren't able > to > > > trace from which dataset it was loaded. > > > > > > Is there a way to know the dataset name from which or where it is > saved ? > > > > > > On Fri, 18 Sep, 2020, 4:16 pm Itschak Mugzach, < > > > [email protected]> wrote: > > > > > >> Peter, > > >> > > >> There are some 3rd party products that load modules to modified LPA > (CSA > > >> or > > >> ECSA) as they start. They do it dynamically so if they don't start, > you > > >> save the storage. > > >> > > >> ITschak > > >> > > >> *| **Itschak Mugzach | Director | SecuriTeam Software **|** IronSphere > > >> Platform* *|* *Information Security Continuous Monitoring for Z/OS, > > zLinux > > >> and IBM I **| * > > >> > > >> *|* *Email**: [email protected] **|* *Mob**: +972 522 986404 > > >> **|* > > >> *Skype**: ItschakMugzach **|* *Web**: > > >> http://secure-web.cisco.com/1uYnAuN5Ol9abEOzh6GC-P1tZbk86urrVNMwVjYQIOlgTTKT4QSFQUFWraW13edzSO87wcJpA_vlV83vjhQ6pNhwF_TPNNPinlw5-2OILY5iiPF6DCNEZf4V-snl77CC0ryDjJKX1IXqCSzVhmJyKDOHkeEPJVg5n3quERi5iKXNa8lPNRGG-nmnINU7l5ZqjQng3vMroYdM7NK9E6v8PUHuVZI_x-Os9BGacDvzUahCMk5zMagXS8ROJaZQrz6y5-pGJViFEhcRs27I7fmMZLvNqMg6NpG-7hBpElMxKW6HcMnUxUawEKd8vBATe_5Yk6i8ofPMrlUQJgXqbkyA_tdm5NN2iHk0LTeqaqQLvNDvmGIHfZWuID3FID6Syv2zm4lihXQEkcf_AZEnOmVCu2hkzgEziOHKxVOokp5hlF5Gs2Y3jvSeTxRhvRxd67TM9/http%3A%2F%2Fwww.Securiteam.co.il > > >> **|* > > >> > > >> > > >> > > >> > > >> > > >> On Fri, Sep 18, 2020 at 3:06 PM Peter Relson <[email protected]> > wrote: > > >> > > >> > <snip> > > >> > Is there any utility which can help to search the loaded MLPA > module ? > > >> > </snip> > > >> > What do you mean by "search the loaded MLPA module"? > > >> > > > >> > A program can use CSVQUERY to locate the address of a module in LPA > > >> > (whether PLPA, MLPA, FLPA, or dynamic LPA), just as it can use LOAD > > and > > >> > then DELETE (CSVQUERY typically has less overhead than that pair of > > >> > operations). > > >> > > > >> > <snip> > > >> > We have a product which loads via MLPA and we just trying to > > understand > > >> if > > >> > it's possible to load it dynamically without the need of IPL > > >> > </snip> > > >> > I do not understand this sentence either. Nothing loads "via MLPA". > > Some > > >> > things might require that their parts be in LPA. Is that what you > > meant? > > >> > If a program wants to put module(s) into LPA it can use the CSVDYLPA > > >> > macro. If a customer wants to put module(s) in LPA it can use the > LPA > > >> > statement of the PROGxx parmlib member or the SETPROG LPA command. > > >> > > > >> > > > >> > Peter Relson > > >> > z/OS Core Technology Design > > >> > > > >> > > > >> > > ---------------------------------------------------------------------- > > >> > For IBM-MAIN subscribe / signoff / archive access instructions, > > >> > send email to [email protected] with the message: INFO > > IBM-MAIN > > >> > > > >> > > >> ---------------------------------------------------------------------- > > >> For IBM-MAIN subscribe / signoff / archive access instructions, > > >> send email to [email protected] with the message: INFO > IBM-MAIN > > >> > > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
