I'm apolitical.. and not sure how politics came into it for you.. anyway:
Here's what I get: dirm directory ? DVHXMT1191I Your DIRECTORY request has been sent for processing. Ready; T=0.05/0.05 21:31:55 DVHREQ2288I Your DIRECTORY request for ROHLING at * has been accepted. DVHDRY3386I The following are your DIRECTORY control statements. Note DVHDRY3386I that the first field is the ordinal associated with each DVHDRY3386I statement. DVHDRY3386I 1 : DIRECTORY 0123 3390 540RES DVHREQ2289I Your DIRECTORY request for ROHLING at * has completed; DVHREQ2289I with RC = 0. 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)? The contents of AUTHFOR CONTROL (VMLINK DIRMAINT 1DF and look for it) should show you who can do what.. I know DIRMAINT doesn't work just like VMSECURE - so it takes some adjusting. Scott On Thu, Mar 19, 2009 at 8:18 PM, Stricklin, Raymond J < raymond.j.strick...@boeing.com> wrote: > We know VMSECURE and the rest is big-company politics. DIRMAINT doesn't > need defending. We just need to know how to work with an existing DIRMAINT > installation until we can get the politics straightened out. > > I was able to change the directory by putting a USER INPUT file on DIRMAINT > 1DF and erasing a lot of files, which apparently forced some sort of > rebuild. It did the job, but who knows what else I may have affected, > inadvertently? > > It seems clear from reading all the documentation that the DIRM DIRECTORY > command is intended to do the job we needed. When we try it, DIRM claims > DIRECTORY is not a valid keyword, and nobody here knows enough about > DIRMAINT to understand why this should be. I was just looking for a little > enlightenment, in case there's something else related to this issue, waiting > to bite us later. > > ok > r. > > ------------------------------ > *From:* Scott Rohling [mailto:scott.rohl...@gmail.com] > *Sent:* Thursday, March 19, 2009 6:24 PM > > *To:* IBMVM@LISTSERV.UARK.EDU > *Subject:* Re: DIRMAINT > > I just gave the procedure to do just that a few posts ago... > > Rather than me defend DIRMAINT, maybe you could explain what you don't > understand first...? > > Scott > > On Thu, Mar 19, 2009 at 6:58 PM, Doug Shupe <dsh...@bellsouth.net> wrote: > >> I never understood why anyone would use dirmaint to begin with. >> >> Can you make dirmaint produce a standard directory and start over? >> >> >> ----- Original Message ----- >> *From:* Stricklin, Raymond J <raymond.j.strick...@boeing.com> >> *To:* IBMVM@LISTSERV.UARK.EDU >> *Sent:* Thursday, March 19, 2009 18:58 >> *Subject:* Re: DIRMAINT >> >> We've been trying that all day, it doesn't work. Why? >> >> >> dirm directory ? >> >> DVHADZ1252E An invalid keyword or value has been encountered. Please >> >> DVHADZ1252E check the command syntax. >> >> DVHADZ1270E DIRMaint >>> directory <<< ? >> >> Ready(01252); T=0.08/0.09 17:56:06 >> >> >> Some joker did not install the help files. >> >> ok >> r. >> >> ------------------------------ >> *From:* Scott Rohling [mailto:scott.rohl...@gmail.com] >> *Sent:* Thursday, March 19, 2009 3:16 PM >> *To:* IBMVM@LISTSERV.UARK.EDU >> *Subject:* Re: DIRMAINT >> >> DIRM HELP DIRECTORY .. >> >> DIRM DIRECTORY CHANGE 0123 etc etc should do ya.. >> >> Scott >> >> On Thu, Mar 19, 2009 at 4:10 PM, Stricklin, Raymond J < >> raymond.j.strick...@boeing.com> wrote: >> >>> Lance means --- using DIRMAINT, how do we do this? >>> >>> thanks, guys. (@: >>> >>> ok >>> r. >>> >>> > -----Original Message----- >>> > From: Preuett, Lance M >>> > Sent: Thursday, March 19, 2009 3:09 PM >>> > To: IBMVM@LISTSERV.UARK.EDU >>> > Subject: DIRMAINT >>> > >>> > >>> > need help >>> > > How do you change the direct record in the directory >>> > > >>> > > DIRECT 0123 3390 VFARES 223 *A59FF-2086 >>> > > >>> > > I need to change it to >>> > > >>> > > DIRECT 0123 3390 VFARES 223 *A59FF-2066 >>> > > >>> > > >>> > > Lance Preuett >>> > > Enterprise Storage and Servers Delivery Systems M/S 7M-RE >>> > PO Box 3707 >>> > > Seattle, WA 98124-2207 >>> > > 425-865-1525 >>> > > lance.m.preu...@boeing.com >>> > > >>> > > >>> > >>> >> >> >
