DIRMAINT comes up by default in TESTING mode, but it sure doesn't like testing mode. Instructions were changed back in z/VM 4.4 (I know, it was my ETR) to tell the installer to manually switch the config to production early on. You are likely picking up testing because you are not picking up your override CONFIG50. I think fixing that will fix the TESTING error. And the OFFLINE setting is probably due to that too, although you can fix that, as indicated, by entering DIRM ONLINE.
On 10/24/07, RPN01 <[EMAIL PROTECTED]> wrote: > Some additional info... I'm seeing this on the DirMaint console: > > DIRMAINT VMTESTP. - 2007/10/24; T=0.01/0.01 13:29:19 > dvhbegin > DVHITI3531W An OFFLINE CONTROL exists. Updates to the object > DVHITI3531W directory are currently disabled. Use the DIRM ONLINE > DVHITI3531W command to enable object directory updates. > DIRMAINT VMTESTP. - 2007/10/24; T=0.10/0.12 13:30:09 > DVHWAI2140I Waiting for work on 07/10/24 at 13:30:09. > DVHWAI2143I Wakeup caused by timer file entry on 07/10/24 at 13:30:09. > DVHWAI2143I Processing event number 00004 scheduled for ==/==/== at > DVHWAI2143I 00:03:00. > DVHMEO3526W DirMaint is in TESTING mode. > DVHWAI2119T Error in CMS command; RC= 3526 > DVHWAI2119T from: EXEC DVHMERO DIRMAINT DATADVH A = > DVHWAI2119T = * > DVHWAI2119T at line 210. > *** Query Time > TIME IS 13:30:09 CDT WEDNESDAY 10/24/07 > CONNECT= 00:24:32 VIRTCPU= 000:00.42 TOTCPU= 000:00.52 > *** Identify > DIRMAINT AT VMTESTP VIA * 10/24/07 13:30:09 CDT WEDNESDAY > > DVHMERO is compiled, so I can't look at line 210, and I'm not sure what the > RC=3526 would relate to. > > -- > .~. Robert P. Nix Mayo Foundation > /V\ RO-OE-5-55 200 First Street SW > / ( ) \ 507-284-0844 Rochester, MN 55905 > ^^-^^ ----- > "In theory, theory and practice are the same, but "Join the story... > Ride Ural." > in practice, theory and practice are different." > >
