Good catch -- I stopped using 140A commands a long time ago .. and wish they would just drop them -- because every once in awhile, I run into something like this where a command will work for me but not someone else and it turns out to be a different cmdlevel and everyone confused until the 'aha' moment.
Glad you found you're way out of this one - good job -- Scott On Fri, Mar 20, 2009 at 4:12 PM, Stricklin, Raymond J < raymond.j.strick...@boeing.com> wrote: > Folks; > > Some joker put a DEFAULT_CMDLEVEL = 140A in CONFIGA DATADVH (probably > the same joker who didn't install the help files). > > I was able to run DIRM GLOBALV CMDLEVEL 150A on an authorized user and > get DIRM DIRECTORY ? to work, along with several other DIRM commands > (CHECK, QUERY, etc.) which had been failing in the same way. > > Unfortunately there were no references that I was able to find in the > DIRMAINT docs showing which commands were only valid at which command > levels. I just happened to get lucky finding the config setting and then > wondering, "what would happen if..." > > Thanks for helping us out. > > ok > r. > > > > > -----Original Message----- > > From: r.stricklin [mailto:b...@typewritten.org] > > Sent: Thursday, March 19, 2009 8:49 PM > > To: IBMVM@LISTSERV.UARK.EDU > > Subject: Re: DIRMAINT > > > > On Mar 19, 2009, at 7:46 PM, Scott Rohling wrote: > > > > > dirm directory ? > > > DVHXMT1191I Your DIRECTORY request has been sent for processing. > > > Ready; T=0.05/0.05 21:31:55 > > > > That's what we would've expected, but were unable to get. > > > > > What userid are you doing this from, and is it fully > > authorized to do > > > DIRMAINT admin things (very much like ADMIN users in VMSECURE IIRC)? > > > > We were trying it from several different user IDs, including > > MAINT. We checked the AUTHFOR CONTROL on DIRMAINT 1DF and it > > showed MAINT (and the others) having the whole string of > > auths (for both command levels 140 and 150), including S > > which is what the doc said was needed. > > > > ok > > bear > > >
