On 2014-09-30, at 08:47, Pommier, Rex wrote: > > I don't think ISRDDN gives a rip about these edit rules - other than the one > about mixing legacy and Unix. > And that's treacherous in that ISRDDN will report only a member in a Legacy data set while BLDL will find a similarly named member in an earlier UNIX catenand. I went to ETR on this a few years ago; got WAD. Shameful; BAD.
> In my ISRDDN concatenation that I was editing I have 18 datasets > concatenated, and I can select a member from any of the first 16 (which is > all ISRDDN will show me). These datasets have anywhere from 2-4 qualifiers > and they are all over the board as far as DSN is concerned from system > libraries to production to development/test libraries. > Does LMINIT have a catenation limit? > As far as checking SAF upon entry, the answer is no it doesn't. I just > verified that RACF didn't fail an edit of the first library until the user > tried to save when she just has read access to the library. > Of course, that could be changed dynamically, unexpectedly while Edit is in progress. Nonetheless, an early warning would be a courtesy. The motive for saving into the first catenand may be that earlier catenands tend to be development libraries; later system libraries. It's simple source code control -- after testing you can move the member to a more stable level. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
