Adding new disk devices to existing Mainframe configuration
CONTENTS:
An easy way to add new formatted LCU and newly created Device addresses to existing Mainframe configuration (if a ESS800 shark storage is available) is described below. The first step is to update and create IODF work configuration with the added LCU and newly created Devices followed by IODF building (using HCD or JCL technology). The next step is to build the new IOCDS configuration (by HCD or HMC technology) using the updated IODF work configuration followed by IPL prepare before starting the modified system configuration. The new IOCDS is used at POR (Power Off Reset) time before IPL to make the new configuration data known to z/OS .
1. Update and build IODF
For HCD technology follow the link ZOS production IODF configuration display/ create/ change using ISPF and create a new work IODF based on the current production IODF (copied under a new name “sys1.iodf39.work” selecting ISPF – HC– 6(Maintain I/O definition files) – 2(Copy I/O definition file) . Add the new control units (if =3A00/3B00) in the HC – 1 – 4 menu selections using F11. Add the new devices (if =500,256/600,256) in the HC – 1 – 5 menu selections using F11 and select the action Add like. To build IODF select HC-2-1 (Build production I/O definition file) as shown in Case3 of the upper link. The new IODF is saved on BC2MCC (IODF device with address 644) as sys1.iodf39.
For JCL technology follow the link ZOS test IODF configuration display/ create/ change-consoles/ add- disks using JCL source library to create new JCL executable library member IODEF42 copying source member MVSIO42 with added New disk volume addresses (500 and 600) to New control units (3A00 and 3B00) as follows:
CNTLUNIT CUNUMBR=3A00,PATH=(25,27), X
UNITADD=((00,256)),UNIT=2105,CUADD=4
IODEVICE UNIT=3390,ADDRESS=(0500,256),CUNUMBR=(3A00), X
UNITADD=00,STADET=Y,OFFLINE=YES
CNTLUNIT CUNUMBR=3B00,PATH=(25,27), X
UNITADD=((00,256)),UNIT=2105,CUADD=5
IODEVICE UNIT=3390,ADDRESS=(0600,256),CUNUMBR=(3B00), X
UNITADD=00,STADET=Y,OFFLINE=YES
After execution of the submitted member IODEF42, the IODF file Sys1.iodf42 is created on IODF deviceBC2MCC.
2. Update and build IOCDS
For the HCD technology follow the link ZOS IOCDS build or change using HCD of ISPF and enter – HC – 2(Activate or process configuration data) – 2(Build IOCDS) specifying the name of the new created IODF file ‘SYS1.IODF39′ to be used and continue with Build IOCDS function. Then you have to perform some Actions on selected IOCDS configuration(A0, A1, A2..) – Update IOCDS and writing/rename the title and date of the changed configuration. A job is generated “CRIOCDS JOB07466 “ that is submitted, but not started. On syslog (sd.log) you have to answer/ REPLY ‘YES’ for the job “CRIOCDS” to WRITE TO LEVEL A0 IOCDS or A1 IOCDS which is choosen to be replaced (“Disable write protection” for this IOCDS must be activated from HMC/Hardware Management Console/).
For the HMC technology go to link ZOS IOCDS data set creation using Hardware Management Console and add to the existing configuration file the following statements with the new CUNUMBR=(3A00/3B00) and IODEVICE ADDRESS=(500,256)/(600,256) as follows:
IODEVICE ADDRESS=(500,256),CUNUMBR=(3A00),UNIT=3390,STADET=Y
IODEVICE ADDRESS=(600,256),CUNUMBR=(3B00),UNIT=3390,STADET=Y
Different function options exist for the choosen I/O configuration (IOCDS). To view or edit the active A0 configuration you have to “Disable write protection”, to “Disassemble data set”, then “Open source file” and save it. Enter “Build data” function to create IOCDS as A0 and exit to finish operations. You may write a new A0 configuration generated by HMC only if “Disable write protection“ function option for the selected configuration is activated.
After the new IOCDS is made active it is necessary from HMC to start task list – CPC Recovery – POR (Power Off Reset) to make the new configuration data ready for IPL.
3. Prepare and start IPL
3.1. IPL preparation
Before IPL it is necessary to prepare a special LOAD39 member in library sys1.iplparm as shown in case 4.1 following the link ZOS production IODF configuration display/ create/ change using ISPF where it is pointed IODF39 to be used during IPL.
In sys1.parmlib(commnd00) library member should be added “‘comm=’v 500-5ff,online’/ comm=’v 600-6ff,online” if IODF is created with parameter “offline YES’ for addresses 500 and 600.
3.2. Start IPL
To start IPL follow the HMC /Hardware Management Console/ IPL Operations described below:
START SYSTEM ACTIVITIES – IPL for LPAR=BC2A, go to – task list – CPC Recovery – Load:
Load address: 0640 – (from /d iplinfo: “IPL DEVICE 0640 VOLUME BC2RIC”)
Load parameter: 064439 – (from /d iplinfo: “IODF DEVICE 0644” of VOLUME BC2MCC, “USED LOAD39 IN SYS1.IPLPARM ON 0644” for sys1.iodf39 on VOLUME BC2MCC)
After IPL is finished the new added disk devices could be verified (Find) with their volume names and physical addresses using the following ISPF menu selections – p.6 – rmf – 2 – 2 – 3. The next actions should be to distribute the new added disk space among the LPARS and the applications.
Comments
No comments yet, be the first to add one!