Hi,
Thanks for replying , Scott and Paolo. I am starting to understand the issue.
My IOCDS looks like :
CNTLUNIT CUNUMBR=1000,PATH=((CSS(0),20,22,23,30)), *
UNITADD=((00,256)),CUADD=0,UNIT=1750
IODEVICE ADDRESS=(300,196),CUNUMBR=(1000),STADET=Y,UNIT=3390B
And
CNTLUNIT CUNUMBR=1100,PATH=((CSS(0),20,22,23,30)), *
UNITADD=((00,256)),CUADD=1,UNIT=1750
IODEVICE ADDRESS=(1100,196),CUNUMBR=(1100),STADET=Y,UNIT=3390B
I have asked for the csv reports from the DS8K for further analysis.
Regards,
Srinivas G
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of
Scott Rowe
Sent: Friday, December 03, 2010 8:29 PM
To: [email protected]
Subject: Re: Z10 BC DS8700 Storage issue
To explain further:
The CUADD in the CNTLUNIT statement in the IOCDS corresponds to the DS8K LCU
under which the device was defined, and the UNITADD corresponds to the
relative unit number within that LCU.
If your storage guy says he created a volume at 2100, then that most likely
means LCU 21, unit 00. Unless your IOCDS looks like this:
CNTLUNIT
CUNUMBR=xxxx,PATH=((CSS(0),yy,zz)),UNITADD=((00,nnn)),CUADD=21,UNIT=2107
IODEVICE ADDRESS=(1100,nnn),CUNUMBR=(xxxx),STADET=Y,UNIT=3390
Then you are not going to get to that unit from device number 1100.
If your IOCDS looks more like this:
CNTLUNIT
CUNUMBR=xxxx,PATH=((CSS(0),yy,zz)),UNITADD=((00,nnn)),CUADD=11,UNIT=2107
IODEVICE ADDRESS=(1100,nnn),CUNUMBR=(xxxx),STADET=Y,UNIT=3390
Then you need your storage guy to create a device on LCU 11, unit 00.
On Fri, Dec 3, 2010 at 9:38 AM, Scott Rowe <[email protected]> wrote:
> The actual device numbers you assign in the IOCDS is irrelevant, what
> matters is the CUADD and UNITADD keywords, how are they set?
>
CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains
confidential and privileged information intended only for the addressee.
If you are not the intended recipient, please be advised that you have
received this material in error and that any forwarding, copying, printing,
distribution, use or disclosure of the material is strictly prohibited.
If you have received this material in error, please (i) do not read it,
(ii) reply to the sender that you received the message in error, and
(iii) erase or destroy the material. Emails are not secure and can be
intercepted, amended, lost or destroyed, or contain viruses. You are deemed
to have accepted these risks if you communicate with us by email. Thank you.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are
not
to copy, disclose, or distribute this e-mail or its contents to any other
person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has
taken
every reasonable precaution to minimize this risk, but is not liable for any
damage
you may sustain as a result of any virus in this e-mail. You should carry out
your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this
e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
