Two questions 1) can BLDL or DESERV differentiate between TASK STEP or JOBLIB
2) is there any way to get DSN name given a DCB I seem to recall RDJFCB doing that but that was with EXLST pram on the DCB -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Scott Ford Sent: Sunday, December 01, 2013 2:37 PM To: [email protected] Subject: Re: DESERV function get DCB address Sorry a 'bit' more Scott ford www.identityforge.com from my IPAD 'Infinite wisdom through infinite means' > On Dec 1, 2013, at 2:35 PM, Scott Ford <[email protected]> wrote: > > Michel, > > Can you impart a big more information on what your trying to accomplish ? > > Scott ford > www.identityforge.com > from my IPAD > > 'Infinite wisdom through infinite means' > > >> On Dec 1, 2013, at 2:03 PM, MichealButz <[email protected]> wrote: >> >> Thanks for your help >> >> Two questions >> >> Does BLDL or DESERV have anyway of differentiating between >> TASKLIB/STEPLIB/JOBLIB I think not. TCBJLIB represents the first >> library looked at be it TASK STEP or JOB Second is there anyway of >> getting the associated DSN name >> >> Thanks >> >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] >> On Behalf Of Peter Relson >> Sent: Sunday, December 01, 2013 1:36 PM >> To: [email protected] >> Subject: Re: DESERV function get DCB address >> >>> unfortunately DESERV >>> FUNC=GET needs a real DCB address as opposed to the zero used >>> invoking >> BLDL >> >> You need to supply a DCB address that represents a concatenation in >> which the member for which you are seeking the directory entry exists. >> >> BLDL happens to support 0 as asking to search >> tasklib(s) >> steplib/joblib >> lnklst >> DESERV does not. >> >> TCBJLB of the jobstep program task is either joblib or steplib. >> TCBJLB of subtasks of that task, when different, is a tasklib. >> >> So where is the member? If it's in the lnklst, then use the DCB >> pointed to by CVTLINK. >> If you don't know where it is, then you may need to do what the >> system does to locate a module: >> search every tasklib up to/through the ASCBXTCB TCB using its DCB >> search the LNKLST using its DCB And if that's not where your member >> is, then you need to search where it is. In some situations, for >> example, ISPLLIB is used not as a tasklib. >> Of course it was not even stated why BLDL was being used. >> >> In some scenarios, it is necessary first to eliminate the possibility >> that the module is in LPA and not the LNKLST (perhaps by CSVQUERY). >> >> 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
