I agree with Roy Hewitt and Mark Zeldon.
Way back when, I was a user of the STK UIMs so that I could gen the 9490s
as device type 9490. But, after some z/OS (or perhaps OS/390, it was some
time ago) change came along, and the STK UIMs didn't work correctly
anymore, I changed to using the standard IBM UIMs - and have not looked
back since.
If you do decide to go down the path of installing the STK 9490 UIMs into
z/OS (the modules must go into SYS1.NUCLEUS, by the way), please post
back your results as I'd be curious to hear if STK ever fixed their UIMs for
the
problem we hit several years ago.
There is one side effect to using the IBM 3490 UIM for the 9490 device. The
IBM UIM for 3490 expects the Control unit to have 16 devices behind it. The
STK UIM 9490 allows for what the STK device actually does - one control
unit / one device. As a result, when you generate the production IODF using
the IBM 3490 UIM, HCD issues a warning message.
CBDG448I Following 8 control units of type 3490 have less devices
attached than the minimum number of 16 unit addresses:
0230, 0231, 0232, 0233, 0234, 0235, 0236, 0237
This message appears, and the job I run to create a production IODF ends
RC=4. Everything works correctly - I believe this is how nearly every STK
9490 user does this.
Here's definitions for eight 9490 devices, with device numbers 230-237:
CNTLUNIT CUNUMBR=0230,PATH=(1C,29),UNITADD=((00,016)), *
LINK=(B6,B6),UNIT=3490
CNTLUNIT CUNUMBR=0231,PATH=(1C,29),UNITADD=((00,016)), *
LINK=(BA,BA),UNIT=3490
CNTLUNIT CUNUMBR=0232,PATH=(1C,29),UNITADD=((00,016)), *
LINK=(BD,BD),UNIT=3490
CNTLUNIT CUNUMBR=0233,PATH=(1C,29),UNITADD=((00,016)), *
LINK=(C1,C1),UNIT=3490
CNTLUNIT CUNUMBR=0234,PATH=(36,43),UNITADD=((00,016)), *
LINK=(B8,B8),UNIT=3490
CNTLUNIT CUNUMBR=0235,PATH=(36,43),UNITADD=((00,016)), *
LINK=(BE,BE),UNIT=3490
CNTLUNIT CUNUMBR=0236,PATH=(36,43),UNITADD=((00,016)), *
LINK=(C1,C1),UNIT=3490
CNTLUNIT CUNUMBR=0237,PATH=(36,43),UNITADD=((00,016)), *
LINK=(C4,C4),UNIT=3490
IODEVICE ADDRESS=230,UNITADD=00,CUNUMBR=(0230),STADET=Y, *
UNIT=3490
IODEVICE ADDRESS=231,UNITADD=00,CUNUMBR=(0231),STADET=Y, *
UNIT=3490
IODEVICE ADDRESS=232,UNITADD=00,CUNUMBR=(0232),STADET=Y, *
UNIT=3490
IODEVICE ADDRESS=233,UNITADD=00,CUNUMBR=(0233),STADET=Y, *
UNIT=3490
IODEVICE ADDRESS=234,UNITADD=00,CUNUMBR=(0234),STADET=Y, *
UNIT=3490
IODEVICE ADDRESS=235,UNITADD=00,CUNUMBR=(0235),STADET=Y, *
UNIT=3490
IODEVICE ADDRESS=236,UNITADD=00,CUNUMBR=(0236),STADET=Y, *
UNIT=3490
IODEVICE ADDRESS=237,UNITADD=00,CUNUMBR=(0237),STADET=Y, *
UNIT=3490
Brian
On Fri, 16 Nov 2007 17:43:12 +0000, Roy Hewitt wrote:
>George,
>
>Yes you could define them as 9490, and as you have discovered you will
>need to install various modules to install the HCD UIMs, as HCD does not
>understand '9490'
>
>However, there is little point in doing this as you can just as easily
>define them with Control Unit 3490 and Device Type 3490. I have been
>doing it this way evey since 9490s became available - never had a problem.
>
>Regards
>
>Roy
>
>George Rodriguez wrote:
>> I'm trying to do a z/OS v1.7 HCD IODF, but I'm coming back with the
>> following SEV E error:
>>
>>
>>
>> CBDA268I No Control Unit Information Table found for 9490.
>>
>>
>>
>> According to STK support there's a USERMOD that I need, but I can't seem
>> to explain to support that I need 4 object modules to apply the USERMOD.
>> The 4 object modules are:
>>
>> CBDUC094
>> SODDEFN
>> CBDEC094
>> SODPN01
>>
>> Is there anyone on the list that can help me out?
>>
>> TIA,
>>
>> George Rodriguez :-)
----------------------------------------------------------------------
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
