Ah - I see you meant for this to be run against new DASD -- assuming the
copy had been done... I wasn't sure how/when the DASD would be copied to
the old...so it does depend... the script should be run before or
after depending on the method ;-)
Scott Rohling
On Thu, Aug 16, 2018 at
Good script -- I would use it 'after' the move though - not before..
backout is much easier that way... make changes on the new dasd - not the
old.
Use SAPL and change PDVOL= to correct address... 'then' run this script
once everything comes up and looks good. IMHO.
Scott Rohling
On Thu,
For that process to work you will have to load a new Standalone program Loader
using the new Device address for the PDR volume on the PDVOL =
Here is an example of an exec to load the IPL SALIPL file from the MAINT 190
"S" disk
MKSAIPL EXEC:
/* rexx exec */
true = (1=1)
false = \true
Q IPLPARMS should display what was set in the IPL SALIPL when it was loaded to
the RESVOL
When you move the VM Volumes as long as the VOLSER's don't change there should
be no issues unless you are setting the new devices OFFLINE AT IPL time in
Your SYSTEM CONFIG file.
For the most part Spool
Just a small warning: QUERY IPLPARMS shows you the parameters that will be
used on SHUTDOWN REIPL.
They will typically be the parameters that were in effect at IPL time, but
they can be changed by SET IPLPARMS.
I recommend updating AUTOLOG1 to stash away the output of QUERY IPLPARMS so
Yes - give it a parm of either SYSG (the integrated 3270 console on the
HMC) -- or your main operator console address. For example - if it is E00
... Then enter PARM of E00 at the load screen... then the SAPL screen
will come up there ..if on the normal console - just change PDVOL= ..
I know what SALIPL and SAPL are but not SAIPL.
Is SAIPL just a typo?
When we IPL we never see the SAPL screen where I can override the PDVOL=
The original install resulted in no SAPL screen being displayed.
Is there a way to make this appear when IPLing?
-Original Message-
From: Linux
I have moved/cloned z/VM 6.4 systems and the only thing related to the new
DASD addresses that I've had to do is run SALIPL against the new IPL volume
and specify the real address of the device with the parm disk as part of
the IPLPARMS text. For example, if F000 is the real address of the new
Thanks for the info. I get the following.
Current IPL parameters:
FN=SYSTEMFT=CONFIGPDNUM=1 PDVOL=A84C
CONS=0908
The PDVOL points to common volume which contains the SYSTEM CONFIG file.
I wonder if I can
Change PDVOL to the new address for the common volume.
Shutdown
CP Query IPL gives you the parms used...
You can use SAIPL to bring up z/VM the first time on new DASD (just specify
correct PDVOL=) .. then run SALIPL on the IPL volume to make the parms
stick and not need SAIPL next time..
Scott Rohling
On Thu, Aug 16, 2018 at 2:17 PM Davis, Jim
Last question Q IPLPARMS
On Thu, Aug 16, 2018 at 4:14 PM, Davis, Jim [PRI-1PP] <
jim.da...@primerica.com> wrote:
> I have been tasked with moving our z/VM and zlinux file system volume from
> an old DASD system to a New DASD system.
> All of my device numbers / unit addresses will change.
>
> I
I have been tasked with moving our z/VM and zlinux file system volume from an
old DASD system to a New DASD system.
All of my device numbers / unit addresses will change.
I have been successful in moving all of the z/linux volumes.
My problem is how to move the 6 VM volumes since the IPL text
Ahhh yes, I had to disable the epel repothanks!
Frank M. Ramaekers Jr.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Neale
Ferguson
Sent: Wednesday, August 15, 2018 3:37 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Advice on indexing PDFs
13 matches
Mail list logo
