You're not wrong. IODF changes affecting underlying hardware configuration absolutely require hardware (full) ACTIVATE. Software-only change is OK as a first step, but until the new IODF hits HSA, efforts to access new/changed hardware components will fail.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: "Ambros, Thomas" <[email protected]> To: [email protected], Date: 06/12/2014 08:06 AM Subject: Re: IODF/HCD query reg DASD Sent by: IBM Mainframe Discussion List <[email protected]> I might be wrong, but if you added CUs you changed the hardware configuration and activating only the software portion isn't going to do you any good. Thomas Ambros zEnterprise Operating Systems zEnterprise Systems Management 518-436-6433 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pabitra Mukhopadhyay Sent: Thursday, June 12, 2014 10:56 AM To: [email protected] Subject: Re: IODF/HCD query reg DASD Hi, z9 LPARs are on z/OS V2.1 and z10 LPARs are at V1.13. I have done a test activate followed by soft activate on one of the LPARs on z9. I have not IPL-ed that LPAR. D M=CHP(xx) shows the following (i am showing output for one CHPID only, other CHPID output are similar) IEE174I 20.10.13 DISPLAY M 741 CHPID 01: TYPE=1A, DESC=FICON POINT TO POINT, ONLINE DEVICE STATUS FOR CHANNEL PATH 01 0 1 2 3 4 5 6 7 8 9 A B C D E F D90 + + + + + + + + + + + + + + + + D91 + + + + $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D92 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D93 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D94 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D95 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D96 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D97 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D98 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D99 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D9A $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D9B $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D9C $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D9D $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D9E $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ D9F $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ . DA0 + + + + + + + + + + + + + + + + DA1 + + + + + + + + + + + + + + + + DA2 + + + + + + + + + + + + + + + + DA3 + + + + + + + + + + + + + + + + DA4 + + + + + + + + + + + + + + + + and goes until E8F $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ . E90 + + + + + + + + + + + + $@ $@ $@ $@ E91 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E92 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E93 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E94 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E95 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E96 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E97 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E98 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E99 $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E9A $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E9B $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E9C $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E9D $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E9E $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ E9F $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ $@ . SWITCH DEVICE NUMBER = NONE SWITCH DEVICE NUMBER = NONE ATTACHED ND = 002107.931.IBM.75.0000000DYXD1 PHYSICAL CHANNEL ID = 0100 ************************ SYMBOL EXPLANATIONS ************************ + ONLINE @ PATH NOT VALIDATED - OFFLINE . DOES NOT EXIST * PHYSICALLY ONLINE $ PATH NOT OPERATIONAL It does not show the range that I have added (D100 onwards) Here is the output of D M=DEV(xxxx) D M=DEV(D100) IEE174I 20.13.32 DISPLAY M 774 DEVICE 0D100 STATUS=DEVICE NOT AVAILABLE Below is the output of devserv command ds p,d100 IEE459I 20.15.03 DEVSERV PATHS 784 UNIT DTYPE M CNT VOLSER CHPID=PATH STATUS RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU-TYPE 0D100,3390 ,F,000, ,UCB NOT CONNECTED, PATH STATUS UNAVAILABLE ************************ SYMBOL DEFINITIONS ************************ F = OFFLINE Thanks, P.Mukhopadhyay On Thu, Jun 12, 2014 at 8:12 PM, Lizette Koehler <[email protected]> wrote: > I forgot to add, show the output. Don't tell us what the output has. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List > > [mailto:[email protected]] On Behalf Of Lizette Koehler > > Sent: Thursday, June 12, 2014 7:39 AM > > To: [email protected] > > Subject: Re: IODF/HCD query reg DASD > > > > What version of z/OS? > > > > > > What do you get with > > > > D M=CHP(xx) > > D M=DEV(xxxx) > > > > Did you IPL or do a soft activate? > > > > Have you done a TEST Activate? > > > > > > > > Lizette > > > > > > > -----Original Message----- > > > From: IBM Mainframe Discussion List > > > [mailto:[email protected]] On Behalf Of P. Mukhopadhyay > > > Sent: Thursday, June 12, 2014 7:25 AM > > > To: [email protected] > > > Subject: IODF/HCD query reg DASD > > > > > > Hello, > > > > > > Need help regarding IODF configuration using HCD. > > > > > > There are two system z hardware in our data center (z9 EC and z10 EC). > > > Both of them are connected to same DS8100 storage. The CHPIDs from > > > z9 and z10 connect to different storage LCUs in same DS8100. > > > > > > With the existing z9 CHPIDs (which are already in use) I would > > > like to make z10 LCU number 02 DASD devices (already online on > > > z10), visible to z9 LPARs. For this, I have added a control unit > > > (type 2107) in the > > > z9 IODF with the LCU number 02 and added 256 DASD devices (type 3390). > > > > > > I have activated (software only) the production IODF on z9, > successfully. > > > > > > However, when I try to vary the devices online on z9, I get an > > > error > message: > > > IEE025I UNIT XXXX HAS NO LOGICAL PATHS > > > > > > I have executed /d m=chp(nn) commands with all the CHPIDs in use > > > on z9, but the output does not show the DASD device range that I > > > have > added > > through the IODF. > > > > > > Next, I have executed DEVSERV PATH command as follows: > > > /DS P,XXXX where XXXX is the device number > > > > > > > > > The command output shows UCB NOT CONNECTED, PATH STATUS > > UNAVAILABLE > > > > > > IEE459I 18.05.40 DEVSERV PATHS 220 UNIT DTYPE M CNT VOLSER > > > CHPID=PATH STATUS > > > RTYPE SSID CFW TC DFW PIN DC-STATE CCA DDC CYL CU- > > TYPE > > > 0XXXX,3390 ,F,000, ,UCB NOT CONNECTED, PATH STATUS > > > UNAVAILABLE > > > ************************ SYMBOL DEFINITIONS > > > ************************ F = OFFLINE > > > > > > > > > > > > I have tried this in two different ways by: > > > > > > 1. using same CU and device names on z9 as well as z10. e.g. the > > > CU is called > > > D100 on both z9 and z10 and the devices are called D100 to D1FF > > > > > > 2. using different CU/device names. e.g. on z10 CU is called B100 > > > and devices are called B100 to B1FF whereas on z9 the CU was named > > > A100 and devices A100 to A1FF. > > > > > > Neither of these worked :( > > > > > > > > > I am not sure if I am missing anything here. Any > > > pointer/suggestion to make the device visible will be highly appreciated. > > > > > > Thanks, > > > P. Mukhopadhyay > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
