Mike Directory entries and list below... Thanks.
Directory Entries:
01264 USER 5VMDIR30 xxxxxxxx 16M 64M EG
01265 ACCOUNT 1 SYSPROG
01266 IPL CMS
01267 MACHINE ESA
01268 CONSOLE 009 3215 T
01269 SPOOL 00C 2540 READER *
01270 SPOOL 00D 2540 PUNCH A
01271 SPOOL 00E 1403 A
01272 LINK MAINT 190 190 RR * CMS system disk
01273 LINK MAINT 19D 19D RR * help disk
01274 LINK MAINT 19E 19E RR * Product code disk
01275 LINK MAINT 51D 51D MR * VMSES/E software inventory disk
01276 LINK MAINT 5E5 5E5 RR * VMSES/E code
01277 LINK DIRMAINT 1DF 1DF MR * DIRMAINT server disk
01278 MDISK 2C4 3390 3337 001 530W01 MR
01279 MDISK 191 3390 0229 009 530W02 MR
01280 MDISK 2A2 3390 0238 004 530W02 MR
01281 MDISK 2A6 3390 0242 004 530W02 MR
01282 MDISK 2B2 3390 0246 013 530W02 MR
01283 MDISK 2C2 3390 0259 002 530W02 MR
01284 MDISK 2D2 3390 0261 050 530W02 MR
01285 MDISK 29D 3390 0311 009 530W02 MR
01286 MDISK 29E 3390 1795 001 VPWK02 MR READ
01287 MDISK 2B1 3390 0321 010 530W02 MR
01288 MDISK 502 3390 0331 009 530W02 MR
01289 MDISK 491 3390 0340 015 530W02 MR
01290 MDISK 492 3390 0355 015 530W02 MR
01291 MDISK 41F 3390 0370 008 530W02 MR ALL
01292 MDISK 11F 3390 0378 008 530W02 MR ALL
01293 *
01294 USER DIRMAINT NOLOG 32M 64M BDG
01295 IPL CMS PARM AUTOCR
01296 MACHINE ESA
01297 ACCOUNT SYSTEM SYSPROG
01298 D8ONECMD FAIL LOCK
01299 OPTION CONCEAL DIAG88 D84NOPAS IGNMAXU
01300 IUCV ANY PRIORITY MSGLIMIT 100
01301 CONSOLE 009 3215 T
01302 SPOOL 00C 2540 READER A
01303 SPOOL 00D 2540 PUNCH A
01304 SPOOL 00E 1403 A
01305 LINK 5VMDIR30 491 191 MR
01306 LINK 5VMDIR30 492 192 MR
01307 LINK 5VMDIR30 11F 11F MR
01308 LINK 5VMDIR30 41F 21F MR
01309 LINK MAINT 190 190 RR * CMS system disk
01310 LINK MAINT 19D 19D RR * help disk
01311 LINK MAINT 19E 19E RR * Product code disk
01312 LINK MAINT 123 123 MW
01313 MDISK 1AA 3390 0458 009 530W02 MR
01314 MDISK 1FA 3390 0467 009 530W02 MR
01315 MDISK 1DE 3390 0476 020 530W02 MR
01316 MDISK 2AA 3390 0496 009 530W02 MR
01317 MDISK 155 3390 0505 009 530W02 MR
01318 MDISK 1DF 3390 0514 009 530W02 MR
01319 MDISK 1DB 3390 0523 009 530W02 MR
01320 MDISK 2DF 3390 0532 009 530W02 MR
01321 MDISK 2DB 3390 0541 009 530W02 MR
Screen Print of startup:
LOGON DIRMAINT
HCPLNM107E MAINT 019D not linked; not in CP directory
z/VM Version 5 Release 3.0, Service Level 0703 (64-bit),
built on IBM Virtualization Technology
There is no logmsg data
FILES: 0014 RDR, 0016 PRT, NO PUN
LOGON AT 14:32:26 EDT WEDNESDAY 06/18/08
DMSACC724I 19E replaces Y (19E)
DMSACP723I Y (19E) R/O
z/VM V5.3.0 2008-01-10 14:57
DMSWSP100W Shared Y-STAT not available
........................................................................
PRODUCT:
IBM Directory Maintenance Facility for z/VM (DirMaint)
5741-A05 (C) Copyright IBM Corporation 1979, 2007.
Function Level 530 Service Level 0000.
DMSACC724I 155 replaces A (191)
DMSACC723I X (01DE) R/W - OS
DVHPRO2008I ROLE = DIRMAINT
DVHPRO2010I TESTING USE OF MSGNOH ...
DASD 0192 DETACHED
DASD 021F DETACHED
DVHPRO2002A Manual start is required for DIRMAINT. Enter "DVHBEGIN"
DVHPRO2002A when ready to start.
........................................................................
DIRMAINT VMTESTEB - 2008/06/18; T=0.03/0.04 14:32:44
dvhbegin
DVHRLC2102E File not found: DVHUPDIR MODULE; RC=
DVHRLC2102E 28. File not found: DVHUPDIR MODULE;
DVHRLC2102E RC= 28.
DVHBEG2119T Error in CMS command; RC= 2102
DVHBEG2119T from: EXEC DVHRLDC
DVHBEG2119T at line 37.
DIRMAINT VMTESTEB - 2008/06/18(02119); T=0.08/0.10 14:32:48
*** Query Time
TIME IS 14:32:48 EDT WEDNESDAY 06/18/08
CONNECT= 00:00:22 VIRTCPU= 000:00.11 TOTCPU= 000:00.14
*** Identify
DIRMAINT AT VMTESTEB VIA * 06/18/08 14:32:48 EDT WEDNESDAY
*** Query FILES *
FILES: 0014 RDR, 0017 PRT, NO PUN
*** Query User
DIRMAINT - 0021
*** Query Secuser
SECONDARY USER IS UNDEFINED
*** Query CPLEVEL
z/VM Version 5 Release 3.0, service level 0703 (64-bit)
SELECTED TABLE IS: DVH15
DVHSHU2194T Automatic shutdown/restart
DVHSHU2194T initiated. Machine= DIRMAINT,
DVHSHU2194T caller= DVHBEGIN, reason= 2119
DVHSHU2195I The failing command has been purged.
DVHSHU2197I The DIRMAINT machine is attempting to
DVHSHU2197I re-IPL and restart.
.
DMSACC724I 19E replaces Y (19E)
DMSACP723I Y (19E) R/O
z/VM V5.3.0 2008-01-10 14:57
DMSWSP100W Shared Y-STAT not available
PRT FILE 0032 SENT FROM DIRMAINT CON WAS 0032 RECS 0499 CPY 001 0 HOLD NOKEEP
........................................................................
>>> Mike Walter <[EMAIL PROTECTED]> 6/18/2008 12:20 PM >>>
> Any ideas how to resolve this issue would be appreciated.
Well, for starters: pasting the messages you see on DIRMAINT when you logon and
the PROFILE EXEC runs would be a good place to start.
As I tell some end users: "No message, no problem. Be happy!".
> being detached by something in the system.
Without the messages, it's hard to say what and why it might be detached. But
the LINK not being authorized might be a good place to start looking.
Mike Walter
Hewitt Associates
Any opinions expressed herein are mine alone and do not necessarily represent
the opinions or policies of Hewitt Associates.
"Howard Rifkind" <[EMAIL PROTECTED]>
Sent by: "The IBM z/VM Operating System" <[email protected]>
06/18/2008 11:10 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>
To
[email protected] cc
Subject
Dirmaint Start Up Problem.
When I log on to the Dirmaint user id and the system executes profiles and what
not, I'm getting the following error.
It seems that the 192 disk (with is a link to 5vmdir30's 492 disk) is being
detached by something in the system.
When I issue the 'DVHBEGIN' command the system is telling me that the DVHUPDIR
module can't be found.
That's because this module exists on the 192 disk which should be linked but is
becoming detached.
This is sort of a new installation. I'm doing my testing second level and I
did DDR's on tape from the first level system then back to the second level
system.
I DDR'ed the following users minidisks:
5VMDIR30
DIRMAINT
DATAMOVE
DATASAT
The DDR's didn't have any errors and I believe I did copy over all the
minidisks involved. The DIRMAINT system came packaged on first level.
The directory entries for these users are the same in both the first and second
level system and contain all the same link statements.
Any ideas how to resolve this issue would be appreciated.
Thanks
_____________
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient is strictly prohibited. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal policies
and to protect our business. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, lost or destroyed, or
contain viruses. You are deemed to have accepted these risks if you communicate
with us by e-mail.
_____________
LEGAL NOTICE
Unless expressly stated otherwise, this message is confidential
and may be privileged. It is intended for the addressee(s) only.
Access to this E-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the
contents of this E-mail or any action taken (or not taken) in
reliance on it is unauthorized and may be unlawful. If you are not an
addressee, please inform the sender immediately, then delete this
message and empty from your trash.
