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 4:35 PM Scott Rohling <[email protected]> wrote: > 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, Aug 16, 2018 at 4:16 PM Davis, Larry (National VM Capability) < > [email protected]> wrote: > >> 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 =xxxx >> >> 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 >> debug = TRUE >> >> /* **************************************************************** */ >> /* */ >> /* Setup Procedures: */ >> /* 1 NEED ACCESS TO THE Z/VM 6.4 IPL SALIPL TEXT DECK */ >> /* 2 If this is SSI Environment set to TRUE otherwise FALSE */ >> /* 3 Is the virtual address the address the RESVOL is linked as? */ >> /* 4 Is the volid of the RESVOL? */ >> /* 5 Is the real address of the PDR VOLUME? */ >> /* */ >> /* **************************************************************** */ >> >> ssi = FALSE /* Set to TRUE when using SSI */ >> DEV_ADDR = 'xxxx' /* RESVOL Virtual Address */ >> VOL_ID = 'vvvvvv' /* RESVOL Volume Serial Number */ >> PD_VOL = 'xxxx' /* PDR VOLUME Real Address */ >> >> /* *************************************************** */ >> /* PDNUM is the offset extent for the CF0 PARM disk */ >> /* PDVOL is the Real address for the PDR Volume */ >> /* *************************************************** */ >> >> if ssi Then do >> Say >> Say 'Loading SALIPL text deck for SSI on RESVOL' vol_id 'on' dev_addr >> Say >> IPL_PARM = 'FN=SYSTEM FT=CONFIG PDNUM=1 PDVOL=' pd_vol end Else do >> Say >> Say 'Loading SALIPL text deck on RESVOL' vol_id 'on' dev_addr >> Say >> IPL_PARM = 'FN=SYSTEM FT=CONFIG' >> end >> >> if debug then do >> salp_opt = 'EXTENT 1 VOLID' vol_id , >> 'IPLPARMS' ipl_parm >> say ' ADDRESS COMMAND SALIPL' dev_addr >> say ' (' salp_opt >> end >> else do >> salp_opt = 'EXTENT 1 VOLID' vol_id , >> 'COMMENTS ? IPLPARMS' ipl_parm >> >> queue 'IPL Parameters Options are: ' >> queue ' CONS=xxxx FN=fn FT=ft CLEARPDR REPAIR NOEXITS NOHCD PROMPT' >> queue ' PDNUM=n PDOFF=offset PDVOL=addr STORE=nnnnM/G/T/P/E ' >> queue >> >> ADDRESS COMMAND 'SALIPL' dev_addr '(' salp_opt end >> >> Exit >> >> >> >> Larry Davis >> >> >> -----Original Message----- >> From: Linux on 390 Port [mailto:[email protected]] On Behalf Of >> Davis, Jim [PRI-1PP] >> Sent: Thursday, August 16, 2018 17:54 >> To: [email protected] >> Subject: Re: Moving z/vm and zlinux volumes from old dasd to new dasd >> >> Thanks for the info. I get the following. >> >> Current IPL parameters: >> FN=SYSTEM FT=CONFIG PDNUM=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 >> Move all six volumes to their new addresses. >> IPL from new res volume address. >> >> >> -----Original Message----- >> From: Linux on 390 Port <[email protected]> On Behalf Of Tom Huegel >> Sent: Thursday, August 16, 2018 5:36 PM >> To: [email protected] >> Subject: Re: Moving z/vm and zlinux volumes from old dasd to new dasd >> >> Last question Q IPLPARMS >> >> >> On Thu, Aug 16, 2018 at 4:14 PM, Davis, Jim [PRI-1PP] < >> [email protected]> 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 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 has unit >> > addresses in it. >> > >> > In z/vm 5.x I just zapped the 2 addresses in ipl text. >> > >> > In z/VM 6.4 the ipl text has all of 6 volume address in text and some >> > in hex. >> > >> > Can I use SALIPL to change these addresses? >> > >> > SALIPL was run under the covers when I installed VM6.4; Is there a way >> > to find out what was passed as parms to SALIPL. >> > >> > >> > >> > James Davis >> > [email protected] >> > 470-564-5061 >> > "quando omni flunkus moritati" >> > >> > ---------------------------------------------------------------------- >> > For LINUX-390 subscribe / signoff / archive access instructions, send >> > email to [email protected] with the message: INFO LINUX-390 or >> > visit >> > http://www.marist.edu/htbin/wlvindex?LINUX-390 >> > ---------------------------------------------------------------------- >> > For more information on Linux on System z, visit >> > http://wiki.linuxvm.org/ >> > >> >> ---------------------------------------------------------------------- >> For LINUX-390 subscribe / signoff / archive access instructions, send >> email to [email protected] with the message: INFO LINUX-390 or visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> ---------------------------------------------------------------------- >> For more information on Linux on System z, visit http://wiki.linuxvm.org/ >> >> ---------------------------------------------------------------------- >> For LINUX-390 subscribe / signoff / archive access instructions, send >> email to [email protected] with the message: INFO LINUX-390 or visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> ---------------------------------------------------------------------- >> For more information on Linux on System z, visit http://wiki.linuxvm.org/ >> >> >> DXC - This is a PRIVATE message - If you are not the intended recipient, >> please delete without copying and kindly advise us by e-mail of the mistake >> in delivery. NOTE: Regardless of content, this e-mail shall not operate to >> bind the Company to any order or other contract unless pursuant to explicit >> written agreement or government initiative expressly permitting the use of >> e-mail for such purpose. >> >> ---------------------------------------------------------------------- >> For LINUX-390 subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO LINUX-390 or >> visit >> http://www.marist.edu/htbin/wlvindex?LINUX-390 >> ---------------------------------------------------------------------- >> For more information on Linux on System z, visit >> http://wiki.linuxvm.org/ >> > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
