What is giving you the indication that they're ALIASes?  Can you show a 
snapshot of your ISRDDN screen?  When I browse the SYSPROC concatenation in 
ISRDDN I get the list of members along with which library they're in.  I see 
the BLS* members and ISRDDN indicates they're in "library 8" which on my system 
is SYS1.SBLSCLI0, but they're not aliases, they're the actual members.

What I did find interesting is that if I "E"dit the SYSPROC concatenation, and 
then select a member that is in one of the libraries, ISPF copies that library 
into the first DSN in my concatenation and edits the copy that it placed there. 
 I guess I would have thought that ISRDDN would have put the modified member 
back into the library it found the original in.

Rex

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf 
Of Ruegsegger, Jeff
Sent: Monday, September 29, 2014 5:59 PM
To: [email protected]
Subject: ISRDDN SHOWS MEMBER ALIAS

I've run across something strange.  I was  modifying an IPCS clist in our in 
house CLIST library.  Whilst using ISRDDN to locate the correct version I 
noticed that library contained quite a few BLSxxxx members.  When I select 
browse from ISRDDN SYSPROC concatenantion I'm actually browsing the 
SYS1.SBLSCLI0 library.  How is it that I only see the alias name when using 
ISRDDN and not in TSO BROWSE?   How can I determine when these ALIAS's were 
created?

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

The information contained in this message is confidential, protected from 
disclosure and may be legally privileged.  If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful.  If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format.  Thank you.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to