In a recent note, Wade Curry said:

> Date:         Sat, 20 May 2006 18:31:04 -0700
> 
> Paul Gilmartin([EMAIL PROTECTED])@Sat, May 20, 2006 at 09:42:58AM -0600:
> > In ISPF DSLIST, I enter as "Dsname Level" the pattern,
> > "USER.**.CSI", and deselect "Include Additional Qualifiers".
> > The display presented shows such as:
> >
> >  USER.XYZ.GLOBAL.CSI                      *VSAM*
> >  USER.XYZ.GLOBAL.CSI.DATA                 VOL999
> >  USER.XYZ.GLOBAL.CSI.INDEX                VOL999
> > Does this make sense?  Why is it showing me additional qualifiers
> > when I excluded them?
> 
> I'll address the sticky 'confirm on delete' issue first, since it
> has been addressed by others already.  I can't say that I know how
> to make it stick, but I happen to agree with you that if _I_ decide
> I want _my_ 'confirm on delete' setting to stick, then there ought
> to be an option to make it persist.  Others can go ahead and cringe
> thinking about it if that makes them feel better, I suppose.
> 
Indeed.  They should recognize that it's not their dog.  I'm trying
to recall the history.  Did "Confirm ..." appear ab ovo with DSLIST,
or later?  ISTR that I and many operated happily for years with no
Confirm.  Even if I'm wrong there, I know that when I first used
ISPF there was no Confirm on CANCEL from edit session.  That one is
plain stupid; there's no plausible conjecture that typing CANCEL
could be inadvertent.  And there's no way to turn that off, is
there?  I was dismayed when that interaction changed.

Is it a lawyer thing?

> As for the additional qualifiers, I have noticed a couple things
> about that.  One is that the setting *does* stick.  The second is

Ironically, that's one I'd prefer to be not sticky -- I could operate
alwas with no Confirm Delete, but turning off Additional Qualifiers
is something I do only temporarily.

> that it only seems to stick in "new" started screens.  What I mean
> is that, when ISPF starts up, the first screen will not respect
> that setting when I use the DSLIST command. This is also true of
> any other screens that I may start via a command in my logon CLIST.
> Any other screens that are started after that *will* respect that
> setting.
> 
Does it affect only VSAM data sets?  That's how it seems to me.

-- gil
-- 
StorageTek
INFORMATION made POWERFUL

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to