Re: USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Brent Litster
They are in separate lpar's.

 

Brent Litster

Zions Management Services Company

2185 South 3270 West

West Valley City  84119

(801) 844-5545

blits...@zionsbank.com



From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Ward, Mike S
Sent: Tuesday, January 06, 2009 3:19 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers

 

Are you running z/os under VM or are they LPARed separately? 

 

From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Brent Litster
Sent: Tuesday, January 06, 2009 2:43 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers

 

Thanks Bill. I got my directory rewritten with the correct volsers.  I
appreciate your help and all the good information I've gotten from this
list.  We are fairly new to VM as we are a zOS shop and there's lots to
learn.  Happy New Year to all.

Brent

 

Brent Litster

Zions Management Services Company

2185 South 3270 West

West Valley City  84119

(801) 844-5545

blits...@zionsbank.com



From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Bill Munson
Sent: Tuesday, January 06, 2009 9:56 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers

 


Brent, 

cool 

if you linked the 5.3 123 mdisk as 1123 then do not forget to change the
directory statement to DIRECTORY 1123 3390 530RES 
make sure you are running DIRECTXA against the USER DIRECT on the 12cc
mdisk I would rename it myself (530user direct) 
to answer your second question that is pretty much the way it is
normally done (a return code of 5 is ok) 

good luck 

Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/



Brent Litster  
Sent by: The IBM z/VM Operating System  

01/06/2009 11:44 AM 

Please respond to
The IBM z/VM Operating System 

To

IBMVM@LISTSERV.UARK.EDU 

cc

 

Subject

Re: USER DIRECT Rewritten with Wrong Volsers

 

 

 




I forgot to mention that I do have the 5.3 system 123 volume in the mix
and also I just ran DIRECTXA in (EDIT mode so I didn't update anything. 
Brent 
  
Brent Litster 
Zions Management Services Company 
2185 South 3270 West 
West Valley City  84119 
(801) 844-5545 
blits...@zionsbank.com 

 




From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Bill Munson
Sent: Tuesday, January 06, 2009 9:35 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers 
  

Brent, 

1) You got that message because DIRECTXA was run from the saved segment
on your 5.2 system not from the mdisk. 
2) I do not see where you linked to the 5.3 system 123 disk to write the
directory into the DRCT area. 
3) If you did not then you just wrote your 5.3 directory over your 5.2
directory and I hope you did not log off of MAINT 


Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/

Brent Litster  
Sent by: The IBM z/VM Operating System  

01/06/2009 11:19 AM 

 

Please respond to
The IBM z/VM Operating System 

 

To

IBMVM@LISTSERV.UARK.EDU 

cc

  

Subject

USER DIRECT Rewritten with Wrong Volsers


  

 

  

 





Good morning (not so good for me). Sometime ago I installed the VM:Suite
from CA, which included VM:Director which maintains user direct, on my
z/VM 5.2 system. I later installed z/VM 5.3 but didn't get back to
addressing the VM:Suite until recently.  I inadvertently ran VM:Director
on the 5.3 system before modifying its config files resulting in user
direct being rewritten  with all the USER entry MDISK statements
pointing to the 5.2 volsers.  As a result I can't log on to my 5.3
system.  To try and rewrite my 5.3 user direct I brought up my 5.2
system and attached the 5.3 versions of 2CC as 12CC which contains the
5.3 user direct, and 19E as 119E which contains the DIRECTXA utility. I
placed 12CC and 119E before 2CC and 19E in the access list and ran
DIRECTXA (EDIT pointing to the USER DIRECT on 12CC.  The message I got
was 
z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 2.0 
My question is twofold; 
1.Why is the 5.2 version of DIRECTXA being invoked if the 5.3
version is first in the access list,  and 
2.Is there an easier way to rewrite my 5.3 user direct 
Thanks, 
Brent 
 
Brent Litster 
Zions Management Services Company 
2185 South 3270 West 
West Valley City  84119 
(801) 844-5545 
blits...@zionsbank.com 
  

 



*** IMPORTANT NOTE *
The opinions expressed in this message and/or any attachments are those
of the author and not necessarily those of Brown Brothers Harriman &
Co., its subsidiaries and affiliates BBH. There is no guarantee that

Re: USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Ward, Mike S
Are you running z/os under VM or are they LPARed separately? 

 

From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Brent Litster
Sent: Tuesday, January 06, 2009 2:43 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers

 

Thanks Bill. I got my directory rewritten with the correct volsers.  I
appreciate your help and all the good information I've gotten from this
list.  We are fairly new to VM as we are a zOS shop and there's lots to
learn.  Happy New Year to all.

Brent

 

Brent Litster

Zions Management Services Company

2185 South 3270 West

West Valley City  84119

(801) 844-5545

blits...@zionsbank.com



From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Bill Munson
Sent: Tuesday, January 06, 2009 9:56 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers

 


Brent, 

cool 

if you linked the 5.3 123 mdisk as 1123 then do not forget to change the
directory statement to DIRECTORY 1123 3390 530RES 
make sure you are running DIRECTXA against the USER DIRECT on the 12cc
mdisk I would rename it myself (530user direct) 
to answer your second question that is pretty much the way it is
normally done (a return code of 5 is ok) 

good luck 

Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/




Brent Litster  
Sent by: The IBM z/VM Operating System  

01/06/2009 11:44 AM 

Please respond to
The IBM z/VM Operating System 

To

IBMVM@LISTSERV.UARK.EDU 

cc

 

Subject

Re: USER DIRECT Rewritten with Wrong Volsers

 

 

 




I forgot to mention that I do have the 5.3 system 123 volume in the mix
and also I just ran DIRECTXA in (EDIT mode so I didn't update anything. 
Brent 
  
Brent Litster 
Zions Management Services Company 
2185 South 3270 West 
West Valley City  84119 
(801) 844-5545 
blits...@zionsbank.com 

 




From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Bill Munson
Sent: Tuesday, January 06, 2009 9:35 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers 
  

Brent, 

1) You got that message because DIRECTXA was run from the saved segment
on your 5.2 system not from the mdisk. 
2) I do not see where you linked to the 5.3 system 123 disk to write the
directory into the DRCT area. 
3) If you did not then you just wrote your 5.3 directory over your 5.2
directory and I hope you did not log off of MAINT 


Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/

Brent Litster  
Sent by: The IBM z/VM Operating System  

01/06/2009 11:19 AM 

 

Please respond to
The IBM z/VM Operating System 

 

To

IBMVM@LISTSERV.UARK.EDU 

cc

  

Subject

USER DIRECT Rewritten with Wrong Volsers


  

 

  

 





Good morning (not so good for me). Sometime ago I installed the VM:Suite
from CA, which included VM:Director which maintains user direct, on my
z/VM 5.2 system. I later installed z/VM 5.3 but didn't get back to
addressing the VM:Suite until recently.  I inadvertently ran VM:Director
on the 5.3 system before modifying its config files resulting in user
direct being rewritten  with all the USER entry MDISK statements
pointing to the 5.2 volsers.  As a result I can't log on to my 5.3
system.  To try and rewrite my 5.3 user direct I brought up my 5.2
system and attached the 5.3 versions of 2CC as 12CC which contains the
5.3 user direct, and 19E as 119E which contains the DIRECTXA utility. I
placed 12CC and 119E before 2CC and 19E in the access list and ran
DIRECTXA (EDIT pointing to the USER DIRECT on 12CC.  The message I got
was 
z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 2.0 
My question is twofold; 
1.Why is the 5.2 version of DIRECTXA being invoked if the 5.3
version is first in the access list,  and 
2.Is there an easier way to rewrite my 5.3 user direct 
Thanks, 
Brent 
 
Brent Litster 
Zions Management Services Company 
2185 South 3270 West 
West Valley City  84119 
(801) 844-5545 
blits...@zionsbank.com 
  

 



*** IMPORTANT NOTE *
The opinions expressed in this message and/or any attachments are those
of the author and not necessarily those of Brown Brothers Harriman &
Co., its subsidiaries and affiliates BBH. There is no guarantee that
this message is either private or confidential, and it may have been
altered by unauthorized sources without your or our knowledge. Nothing
in the message is capable or intended to create any legally binding
obligations on either party and it is not intended to provide legal
advice. BBH accepts no responsibility for loss or damage from its use

Re: USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Brent Litster
Mike, thanks for the pointers. We are quite new to VM and can use all
the help we can get to strengthen our VM infrastructure.  Have a great
day.
Brent

Brent Litster
Zions Management Services Company
2185 South 3270 West
West Valley City  84119
(801) 844-5545
blits...@zionsbank.com
-Original Message-
From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Mike Walter
Sent: Tuesday, January 06, 2009 10:02 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers

Best bet... call the good folks on the VM product support line at CA to 
ask for support.  That's what you are paying them for - use it.  They
know 
by heart all the "special" VM:Director utilities that you *may* need.

After this is all fixed, prepare for the next crisis ahead of time:
- automate execution of VMXBKP01 and VMXBKP02 every night.
- automate and capture to disk (use a CMS PIPE command) output from 
"LISTFILE * * fm (ISO" of the VMSECURE 1B0 disk (or the VMXBKP02 output 
disk).  This will provide a list of what IDs were managed by which 
VM:Secure managers - something that's important, but not obvious until 
after a crisis.
- automate printing of the USER DIRECT at least weekly (you may want to 
mask the logon and mdisk link passwords, depending on the security of
your 
printing solutions).
- automate execution of VMX MDSKSCAN nightly, save to disk, and print at

least weekly.  We also "massage" that output of MDSKSCAN, including the 
volser before every MDISK record and sorting by userid/mdisk addr.
Having 
that hardcopy makes finding MAINT's and other critical MDISKs much
easier 
in a crisis.
- we do a little more each night, perhaps I should document that and
send 
it to CA as a "best practices" document.

Create a stand-alone 1-pack IPLable z/VM sysres.  With its own page and 
SPOOL space, not much is needed for a stand-alone "recovery" system, and

it does not need regular service (except for hardware changes).  Keep a 
copy of the CP DEFINE MDISK syntax handy when you are using that
recovery 
system.

Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.



"Brent Litster"  

Sent by: "The IBM z/VM Operating System" 
01/06/2009 10:19 AM
Please respond to
"The IBM z/VM Operating System" 



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
USER DIRECT Rewritten with Wrong Volsers






Good morning (not so good for me). Sometime ago I installed the VM:Suite

from CA, which included VM:Director which maintains user direct, on my 
z/VM 5.2 system. I later installed z/VM 5.3 but didn?t get back to 
addressing the VM:Suite until recently.  I inadvertently ran VM:Director

on the 5.3 system before modifying its config files resulting in user 
direct being rewritten  with all the USER entry MDISK statements
pointing 
to the 5.2 volsers.  As a result I can?t log on to my 5.3 system.  To
try 
and rewrite my 5.3 user direct I brought up my 5.2 system and attached
the 
5.3 versions of 2CC as 12CC which contains the 5.3 user direct, and 19E
as 
119E which contains the DIRECTXA utility. I placed 12CC and 119E before 
2CC and 19E in the access list and ran DIRECTXA (EDIT pointing to the
USER 
DIRECT on 12CC.  The message I got was 
z/VM USER DIRECTORY CREATION PROGRAM ? VERSION 5 RELEASE 2.0
My question is twofold;
1.  Why is the 5.2 version of DIRECTXA being invoked if the 5.3 
version is first in the access list,  and
2.  Is there an easier way to rewrite my 5.3 user direct
Thanks,
Brent
 
Brent Litster
Zions Management Services Company
2185 South 3270 West
West Valley City  84119
(801) 844-5545
blits...@zionsbank.com
 




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. 


Re: USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Brent Litster
Thanks Bill. I got my directory rewritten with the correct volsers.  I
appreciate your help and all the good information I've gotten from this
list.  We are fairly new to VM as we are a zOS shop and there's lots to
learn.  Happy New Year to all.

Brent

 

Brent Litster

Zions Management Services Company

2185 South 3270 West

West Valley City  84119

(801) 844-5545

blits...@zionsbank.com



From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Bill Munson
Sent: Tuesday, January 06, 2009 9:56 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers

 


Brent, 

cool 

if you linked the 5.3 123 mdisk as 1123 then do not forget to change the
directory statement to DIRECTORY 1123 3390 530RES 
make sure you are running DIRECTXA against the USER DIRECT on the 12cc
mdisk I would rename it myself (530user direct) 
to answer your second question that is pretty much the way it is
normally done (a return code of 5 is ok) 

good luck 

Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/





Brent Litster  
Sent by: The IBM z/VM Operating System  

01/06/2009 11:44 AM 

Please respond to
The IBM z/VM Operating System 

To

IBMVM@LISTSERV.UARK.EDU 

cc

 

Subject

Re: USER DIRECT Rewritten with Wrong Volsers

 

 

 




I forgot to mention that I do have the 5.3 system 123 volume in the mix
and also I just ran DIRECTXA in (EDIT mode so I didn't update anything. 
Brent 
  
Brent Litster 
Zions Management Services Company 
2185 South 3270 West 
West Valley City  84119 
(801) 844-5545 
blits...@zionsbank.com 

 




From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Bill Munson
Sent: Tuesday, January 06, 2009 9:35 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers 
  

Brent, 

1) You got that message because DIRECTXA was run from the saved segment
on your 5.2 system not from the mdisk. 
2) I do not see where you linked to the 5.3 system 123 disk to write the
directory into the DRCT area. 
3) If you did not then you just wrote your 5.3 directory over your 5.2
directory and I hope you did not log off of MAINT 


Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/



Brent Litster  
Sent by: The IBM z/VM Operating System  

01/06/2009 11:19 AM 

 

Please respond to
The IBM z/VM Operating System 

 

To

IBMVM@LISTSERV.UARK.EDU 

cc

  

Subject

USER DIRECT Rewritten with Wrong Volsers


  

 

  

 





Good morning (not so good for me). Sometime ago I installed the VM:Suite
from CA, which included VM:Director which maintains user direct, on my
z/VM 5.2 system. I later installed z/VM 5.3 but didn't get back to
addressing the VM:Suite until recently.  I inadvertently ran VM:Director
on the 5.3 system before modifying its config files resulting in user
direct being rewritten  with all the USER entry MDISK statements
pointing to the 5.2 volsers.  As a result I can't log on to my 5.3
system.  To try and rewrite my 5.3 user direct I brought up my 5.2
system and attached the 5.3 versions of 2CC as 12CC which contains the
5.3 user direct, and 19E as 119E which contains the DIRECTXA utility. I
placed 12CC and 119E before 2CC and 19E in the access list and ran
DIRECTXA (EDIT pointing to the USER DIRECT on 12CC.  The message I got
was 
z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 2.0 
My question is twofold; 
1.Why is the 5.2 version of DIRECTXA being invoked if the 5.3
version is first in the access list,  and 
2.Is there an easier way to rewrite my 5.3 user direct 
Thanks, 
Brent 
 
Brent Litster 
Zions Management Services Company 
2185 South 3270 West 
West Valley City  84119 
(801) 844-5545 
blits...@zionsbank.com 
  

 



*** IMPORTANT NOTE *
The opinions expressed in this message and/or any attachments are those
of the author and not necessarily those of Brown Brothers Harriman &
Co., its subsidiaries and affiliates BBH. There is no guarantee that
this message is either private or confidential, and it may have been
altered by unauthorized sources without your or our knowledge. Nothing
in the message is capable or intended to create any legally binding
obligations on either party and it is not intended to provide legal
advice. BBH accepts no responsibility for loss or damage from its use,
including damage from virus.
*** 



*** IMPORTANT NOTE *
The opinions expressed in this message and/or any attachments are those
of the author and not necessarily those of Brown Brothers Harriman &
Co., its subsidia

Re: USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Mike Walter
Best bet... call the good folks on the VM product support line at CA to 
ask for support.  That's what you are paying them for - use it.  They know 
by heart all the "special" VM:Director utilities that you *may* need.

After this is all fixed, prepare for the next crisis ahead of time:
- automate execution of VMXBKP01 and VMXBKP02 every night.
- automate and capture to disk (use a CMS PIPE command) output from 
"LISTFILE * * fm (ISO" of the VMSECURE 1B0 disk (or the VMXBKP02 output 
disk).  This will provide a list of what IDs were managed by which 
VM:Secure managers - something that's important, but not obvious until 
after a crisis.
- automate printing of the USER DIRECT at least weekly (you may want to 
mask the logon and mdisk link passwords, depending on the security of your 
printing solutions).
- automate execution of VMX MDSKSCAN nightly, save to disk, and print at 
least weekly.  We also "massage" that output of MDSKSCAN, including the 
volser before every MDISK record and sorting by userid/mdisk addr.  Having 
that hardcopy makes finding MAINT's and other critical MDISKs much easier 
in a crisis.
- we do a little more each night, perhaps I should document that and send 
it to CA as a "best practices" document.

Create a stand-alone 1-pack IPLable z/VM sysres.  With its own page and 
SPOOL space, not much is needed for a stand-alone "recovery" system, and 
it does not need regular service (except for hardware changes).  Keep a 
copy of the CP DEFINE MDISK syntax handy when you are using that recovery 
system.

Mike Walter 
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.



"Brent Litster"  

Sent by: "The IBM z/VM Operating System" 
01/06/2009 10:19 AM
Please respond to
"The IBM z/VM Operating System" 



To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
USER DIRECT Rewritten with Wrong Volsers






Good morning (not so good for me). Sometime ago I installed the VM:Suite 
from CA, which included VM:Director which maintains user direct, on my 
z/VM 5.2 system. I later installed z/VM 5.3 but didn?t get back to 
addressing the VM:Suite until recently.  I inadvertently ran VM:Director 
on the 5.3 system before modifying its config files resulting in user 
direct being rewritten  with all the USER entry MDISK statements pointing 
to the 5.2 volsers.  As a result I can?t log on to my 5.3 system.  To try 
and rewrite my 5.3 user direct I brought up my 5.2 system and attached the 
5.3 versions of 2CC as 12CC which contains the 5.3 user direct, and 19E as 
119E which contains the DIRECTXA utility. I placed 12CC and 119E before 
2CC and 19E in the access list and ran DIRECTXA (EDIT pointing to the USER 
DIRECT on 12CC.  The message I got was 
z/VM USER DIRECTORY CREATION PROGRAM ? VERSION 5 RELEASE 2.0
My question is twofold;
1.  Why is the 5.2 version of DIRECTXA being invoked if the 5.3 
version is first in the access list,  and
2.  Is there an easier way to rewrite my 5.3 user direct
Thanks,
Brent
 
Brent Litster
Zions Management Services Company
2185 South 3270 West
West Valley City  84119
(801) 844-5545
blits...@zionsbank.com
 




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. 


Re: USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Bill Munson
Brent,

cool

if you linked the 5.3 123 mdisk as 1123 then do not forget to change the 
directory statement to DIRECTORY 1123 3390 530RES
make sure you are running DIRECTXA against the USER DIRECT on the 12cc 
mdisk I would rename it myself (530user direct)
to answer your second question that is pretty much the way it is normally 
done (a return code of 5 is ok)

good luck 

Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/





Brent Litster  
Sent by: The IBM z/VM Operating System 
01/06/2009 11:44 AM
Please respond to
The IBM z/VM Operating System 


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
Re: USER DIRECT Rewritten with Wrong Volsers






I forgot to mention that I do have the 5.3 system 123 volume in the mix 
and also I just ran DIRECTXA in (EDIT mode so I didn?t update anything.
Brent
 
Brent Litster
Zions Management Services Company
2185 South 3270 West
West Valley City  84119
(801) 844-5545
blits...@zionsbank.com

From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On 
Behalf Of Bill Munson
Sent: Tuesday, January 06, 2009 9:35 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers
 

Brent, 

1) You got that message because DIRECTXA was run from the saved segment on 
your 5.2 system not from the mdisk. 
2) I do not see where you linked to the 5.3 system 123 disk to write the 
directory into the DRCT area. 
3) If you did not then you just wrote your 5.3 directory over your 5.2 
directory and I hope you did not log off of MAINT 


Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/




Brent Litster  
Sent by: The IBM z/VM Operating System  
01/06/2009 11:19 AM 


Please respond to
The IBM z/VM Operating System 



To
IBMVM@LISTSERV.UARK.EDU 
cc
 
Subject
USER DIRECT Rewritten with Wrong Volsers
 


 
 




Good morning (not so good for me). Sometime ago I installed the VM:Suite 
from CA, which included VM:Director which maintains user direct, on my 
z/VM 5.2 system. I later installed z/VM 5.3 but didn?t get back to 
addressing the VM:Suite until recently.  I inadvertently ran VM:Director 
on the 5.3 system before modifying its config files resulting in user 
direct being rewritten  with all the USER entry MDISK statements pointing 
to the 5.2 volsers.  As a result I can?t log on to my 5.3 system.  To try 
and rewrite my 5.3 user direct I brought up my 5.2 system and attached the 
5.3 versions of 2CC as 12CC which contains the 5.3 user direct, and 19E as 
119E which contains the DIRECTXA utility. I placed 12CC and 119E before 
2CC and 19E in the access list and ran DIRECTXA (EDIT pointing to the USER 
DIRECT on 12CC.  The message I got was 
z/VM USER DIRECTORY CREATION PROGRAM ? VERSION 5 RELEASE 2.0 
My question is twofold; 
1.Why is the 5.2 version of DIRECTXA being invoked if the 5.3 
version is first in the access list,  and 
2.Is there an easier way to rewrite my 5.3 user direct 
Thanks, 
Brent 
  
Brent Litster 
Zions Management Services Company 
2185 South 3270 West 
West Valley City  84119 
(801) 844-5545 
blits...@zionsbank.com 
 

*** IMPORTANT NOTE * 
The opinions expressed in this message and/or any attachments are those of 
the author and not necessarily those of Brown Brothers Harriman & Co., its 
subsidiaries and affiliates BBH. There is no guarantee that this message 
is either private or confidential, and it may have been altered by 
unauthorized sources without your or our knowledge. Nothing in the message 
is capable or intended to create any legally binding obligations on either 
party and it is not intended to provide legal advice. BBH accepts no 
responsibility for loss or damage from its use, including damage from 
virus. ***


*** IMPORTANT
NOTE* The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.


Re: USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Brent Litster
I forgot to mention that I do have the 5.3 system 123 volume in the mix
and also I just ran DIRECTXA in (EDIT mode so I didn't update anything.

Brent

 

Brent Litster

Zions Management Services Company

2185 South 3270 West

West Valley City  84119

(801) 844-5545

blits...@zionsbank.com



From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Bill Munson
Sent: Tuesday, January 06, 2009 9:35 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: USER DIRECT Rewritten with Wrong Volsers

 


Brent, 

1) You got that message because DIRECTXA was run from the saved segment
on your 5.2 system not from the mdisk. 
2) I do not see where you linked to the 5.3 system 123 disk to write the
directory into the DRCT area. 
3) If you did not then you just wrote your 5.3 directory over your 5.2
directory and I hope you did not log off of MAINT 


Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/





Brent Litster  
Sent by: The IBM z/VM Operating System  

01/06/2009 11:19 AM 

Please respond to
The IBM z/VM Operating System 

To

IBMVM@LISTSERV.UARK.EDU 

cc

 

Subject

USER DIRECT Rewritten with Wrong Volsers

 

 

 




Good morning (not so good for me). Sometime ago I installed the VM:Suite
from CA, which included VM:Director which maintains user direct, on my
z/VM 5.2 system. I later installed z/VM 5.3 but didn't get back to
addressing the VM:Suite until recently.  I inadvertently ran VM:Director
on the 5.3 system before modifying its config files resulting in user
direct being rewritten  with all the USER entry MDISK statements
pointing to the 5.2 volsers.  As a result I can't log on to my 5.3
system.  To try and rewrite my 5.3 user direct I brought up my 5.2
system and attached the 5.3 versions of 2CC as 12CC which contains the
5.3 user direct, and 19E as 119E which contains the DIRECTXA utility. I
placed 12CC and 119E before 2CC and 19E in the access list and ran
DIRECTXA (EDIT pointing to the USER DIRECT on 12CC.  The message I got
was 
z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 2.0 
My question is twofold; 
1.Why is the 5.2 version of DIRECTXA being invoked if the 5.3
version is first in the access list,  and 
2.Is there an easier way to rewrite my 5.3 user direct 
Thanks, 
Brent 
  
Brent Litster 
Zions Management Services Company 
2185 South 3270 West 
West Valley City  84119 
(801) 844-5545 
blits...@zionsbank.com 
  



*** IMPORTANT NOTE *
The opinions expressed in this message and/or any attachments are those
of the author and not necessarily those of Brown Brothers Harriman &
Co., its subsidiaries and affiliates BBH. There is no guarantee that
this message is either private or confidential, and it may have been
altered by unauthorized sources without your or our knowledge. Nothing
in the message is capable or intended to create any legally binding
obligations on either party and it is not intended to provide legal
advice. BBH accepts no responsibility for loss or damage from its use,
including damage from virus.
***



Re: USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Bill Munson
Brent,

1) You got that message because DIRECTXA was run from the saved segment on 
your 5.2 system not from the mdisk.
2) I do not see where you linked to the 5.3 system 123 disk to write the 
directory into the DRCT area. 
3) If you did not then you just wrote your 5.3 directory over your 5.2 
directory and I hope you did not log off of MAINT


Bill Munson
Brown Brothers Harriman
Sr. z/VM Systems Programmer
201-418-7588

President MVMUA
http://www2.marist.edu/~mvmua/





Brent Litster  
Sent by: The IBM z/VM Operating System 
01/06/2009 11:19 AM
Please respond to
The IBM z/VM Operating System 


To
IBMVM@LISTSERV.UARK.EDU
cc

Subject
USER DIRECT Rewritten with Wrong Volsers






Good morning (not so good for me). Sometime ago I installed the VM:Suite 
from CA, which included VM:Director which maintains user direct, on my 
z/VM 5.2 system. I later installed z/VM 5.3 but didn?t get back to 
addressing the VM:Suite until recently.  I inadvertently ran VM:Director 
on the 5.3 system before modifying its config files resulting in user 
direct being rewritten  with all the USER entry MDISK statements pointing 
to the 5.2 volsers.  As a result I can?t log on to my 5.3 system.  To try 
and rewrite my 5.3 user direct I brought up my 5.2 system and attached the 
5.3 versions of 2CC as 12CC which contains the 5.3 user direct, and 19E as 
119E which contains the DIRECTXA utility. I placed 12CC and 119E before 
2CC and 19E in the access list and ran DIRECTXA (EDIT pointing to the USER 
DIRECT on 12CC.  The message I got was 
z/VM USER DIRECTORY CREATION PROGRAM ? VERSION 5 RELEASE 2.0
My question is twofold;
1.  Why is the 5.2 version of DIRECTXA being invoked if the 5.3 
version is first in the access list,  and
2.  Is there an easier way to rewrite my 5.3 user direct
Thanks,
Brent
 
Brent Litster
Zions Management Services Company
2185 South 3270 West
West Valley City  84119
(801) 844-5545
blits...@zionsbank.com
 


*** IMPORTANT
NOTE* The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.


USER DIRECT Rewritten with Wrong Volsers

2009-01-06 Thread Brent Litster
Good morning (not so good for me). Sometime ago I installed the VM:Suite
from CA, which included VM:Director which maintains user direct, on my
z/VM 5.2 system. I later installed z/VM 5.3 but didn't get back to
addressing the VM:Suite until recently.  I inadvertently ran VM:Director
on the 5.3 system before modifying its config files resulting in user
direct being rewritten  with all the USER entry MDISK statements
pointing to the 5.2 volsers.  As a result I can't log on to my 5.3
system.  To try and rewrite my 5.3 user direct I brought up my 5.2
system and attached the 5.3 versions of 2CC as 12CC which contains the
5.3 user direct, and 19E as 119E which contains the DIRECTXA utility. I
placed 12CC and 119E before 2CC and 19E in the access list and ran
DIRECTXA (EDIT pointing to the USER DIRECT on 12CC.  The message I got
was 

z/VM USER DIRECTORY CREATION PROGRAM - VERSION 5 RELEASE 2.0

My question is twofold;

1.  Why is the 5.2 version of DIRECTXA being invoked if the 5.3
version is first in the access list,  and
2.  Is there an easier way to rewrite my 5.3 user direct

Thanks,

Brent

 

Brent Litster

Zions Management Services Company

2185 South 3270 West

West Valley City  84119

(801) 844-5545

blits...@zionsbank.com