Again, delayed to digest daily...
Radoslaw: no, I just didn't type the entire name since his examples only
differed by LLQ. To be specific, <quote> {any, some} catalogue changes to
HLQ.BAR.COMMON will lose all the aliases.</quote> For example, HLQ.BAR.A,
HLQ.BAR.B, & HLQ.BAR.C from Charles' example. However, it appears this is a
defunct subject now that he's opted to use SET variables in JCL.
--------> signature = 6 lines follows <--------
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585 fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
"How *do* you plan for something like that?" Guardian Bob, Reboot
"For every action, there is an equal and opposite criticism."
"Systems Programming: Guilty, until proven innocent" John Norgauer 2004
-----Original Message-----
From: R.S. [mailto:[email protected]]
Sent: December 11, 2014 16:56
Subject: Re: Dataset alias advice
W dniu 2014-12-11 o 22:12, Neil Duffee pisze:
> Charles: in addition to gil's notes [1], be advised that {any, some}
> catalogue changes to .COMMON will lose all the aliases. [snip] In the past,
> when FDR archived the base dataset, the alias(es) disappeared and were not
> re-constructed on recall. (not surprising) I'll gamble that similar stuff
> might occur with HSM. So, any process you have that creates .COMMON should
> also have the Define Alias commands imbedded with it ie. batch IDCAms.
> [...]
Do you mean that low level qualifier .COMMON is processed in special way by
catalogs?
Is it documented anywhere?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
