In <[email protected]>, on 03/10/2014
at 06:29 AM, Micheal Butz <[email protected]> said:
>There are but settings In the user area
>Mapped by ihapds macro indicating where the module came from I
>wonder what the setting would be For a LLA manages dataset
First, BLDL doesn't fetch the member[1]. Second, you have to know what
is in the active link list, in each tasklib and the private library
(if any) in order to know where BLDL found the member[1]; BLDL
returns:
K: Indicates the concatenation number of the data set. For the
first or
only data set, this value is zero.
Z: Indicates where the system found the directory entry:
Code Meaning
0 Private library
1 Link library
2 Job, task, or step library
3-16 Job, task, or step library of parent task n, where n = Z-2
Note that it doesn't matter whether the BLDL data are cached.
[1] It need not be a load module.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
