So MLPA module can be loaded using SETPROG LPA ?
On Sat, 19 Sep, 2020, 4:32 pm Peter Relson, <[email protected]> wrote: > <snip> > 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 ? > </snip> > > If it is truly in "MLPA" then it was specified in your IEALPAxx parmlib > member which identifies the data set. > > If it is not truly in MLPA but is in dynamic LPA then there is no > programming interface available to provide that information. > Why don't you ask adabas what they specified to add it? The module is > almost certainly in some data set that is in the LNKLST or that you placed > into their joblib/steplib or otherwise identified to them. (DISPLAY > PROG,LNKLST,NAME=CURRENT,MOD=xxxx can be used to locate in which LNKLST > data set a module exists). If they did add it via dynamic LPA services > without using BYADDR=YES, then there is some information about the data > set from which it was fetched, but the format of that information is > intentionally not documented. That information can be retrieved by the > OUTDSKEY of the CSVQUERY macro or the MODI_DSKEY area for each module via > the CSVINFO macro. That information happens currently to consist of the > UCB address and the CCHH information of the data set on that volume. > > <snip> > MLPA is in CSA > </snip> > that is not correct. Dynamic LPA modules do come from (E)CSA. > > 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
