When you say "source of the old CP directory"  are you referring to the
whole USER DIRECT?  

I tried to ATT rdev * and I added a MDISK statement in my 5.3 user
directory, but I couldn't acc the mdisk.  

It kept saying the volume wasn't mounted.  (It was the 510W01 volume
that I needed.. so no worry about duplicate volume names)

 

________________________________

From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, September 06, 2007 8:08 AM
To: [email protected]
Subject: Re: no xautolog

 

But, there is no real need to IPL the 5.1 system to grab things you
forgot.  The only thing you need is a copy of the source of the old CP
directory, and your current VM LPAR needs access to the DASDs of the old
system (and the old dasds need other labels than the current VM). 
Then you can ATTACH an old disk to SYSTEM and issue DEFINE MDISK, or you
can copy the the MDISK record from the old CP directory in your current
directory.  
To facilitate the use of DEFINE MDISK, I've got an MDSK EXEC.  Suppose
the source of the old VM directory is named OLDVM DIRECT, you could
simply issue 
   MDSK OLDVM.DISKACNT 191 (FILELIST DETACH
and the MDSK EXEC finds the MDISK in OLDVM DIRECT, ATTACHes the volume
to SYSTEM, issue DEFINE MDISK, ACCESS it, start FILELIST; when FILELIST
ends, everything gets DETACHEed again.  I'll send Anne my EXEC. 

2007/9/6, Anne D. Crabtree <[EMAIL PROTECTED]>:

We always use the SAPL screen, so I should be safe there...  I converted
to z/vm 5.3 last night, but my diskacnt routines were wrong so I didn't
get the accounting this morning!  I think I have it fixed so I won't
need to ipl the 5.1 system (at least not today).  However, if something
else needs to be looked at, I'm glad I have a way to get to it!  Thanks
for the help.

 

________________________________

From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Kris Buelens
Sent: Thursday, September 06, 2007 7:28 AM


To: [email protected]
Subject: Re: no xautolog

 

Beware though: depending on the definitions in SYSTEM CONFIG, the IPL
prompt can be bypassed.  The safest way is then to IPL with a SAPL
screen, fill in the address of a 3270 screen, or SYSG if you use an
"integrated 3270 console", at the SAPL screen, enter PROMPT in the IPL
options input field. 


-- 
Kris Buelens,
IBM Belgium, VM customer support 

Reply via email to