3494 VTS on VM/ESA

[HARROP, Roy]

We are trying to put a VTS on a VM/ESA 2.4 system.

Yes, I know it's an old system... However, according to everything I've
read, this should be possible - support for 3494 was in VM/ESA version
1.2 I believe.

Has anyone out there done this? If so, can you help me get this lot
going. I assume it's something I'm doing wrong ( - always assume you're
doing something wrong, never blame the machines... :-) ?!? ).

When I try to bring any of the addresses online, I receive a "... no
channel path is available... " message, HCPCPN6283I.

I've done this on two different processor models - and when look at the
hardware channel problem determination screens on the 2003/204 service
processor, it tells me that there's a "Link configuration problem - init
failure - Channel/CU mismatch".

The processor can 'see' the VTS because its serial number shows up and,
on the VTS console service frames, the processor serial number shows up.
However, there's no system generated Link Address, so I assume I have
something wrong in the IOCDS. Various people have mentioned the
LIBRARY-ID statement, but VM's IOCP doesn't recognise that.

To begin with, the four CNTLUNIT/IODEVICE pairs in my IOCP source used
to be coded thus:

CNTLUNIT
CUNUMBR=0700,PATH=4F,UNIT=3490, CUADD=0,UNITADD=((00,16))

IODEVICE
ADDRESS=(700,16),CUNUMBR=0700,UNIT=3490,UNITADD=00

I made a couple of changes in a vain attempt to get it working - but to
no avail:

CNTLUNIT
CUNUMBR=0700,PATH=4F,UNIT=3490, CUADD=0,UNITADD=((00,2))

IODEVICE
ADDRESS=(700,2),CUNUMBR=0700,UNIT=3490,STADET=Y,UNITADD=00


Roy Harrop




**********************************************************************
This email and any files transmitted with it are confidential. If you
are not the intended recipient, please notify our Help Desk. Email
***@nats.co.uk immediately.
You should not copy or use this email or attachment(s) for any purpose
nor disclose their contents to any other person.

NATS computer systems may be monitored and communications
carried on them recorded, to secure the effective operation of the
system and for other lawful purposes.
********************************************************************************************************************************************

[Colin Allinson]

Hi Roy,

Nice to see you are still around on VM!

I cannot see anything wrong with your definitions. Ours are a lot more
complicated (multiple channels) but here is a sample:-

* --------------------------------------------------------
CU3A2 CNTLUNIT CUNUMBR=3A2,UNIT=3490,UNITADD=((00,16)),
PATH=(B0,B6,CB,EC,64,68,B3,B4),
LINK=(73,77,7A,A9,D4,CC,BC,C4),CUADD=2
*IOCP
VTS3A2 IODEVICE UNIT=3490,CUNUMBR=(3A2),ADDRESS=(3C0,16),
UNITADD=00

Note: We do not use the first 2 blocks of 16 drives on VM and we are going
via an ESCON director (Hence the LINK statement).

Sure, there are all sorts of config setup you have to do with DFSMS/RMS
once you get these online but that should not stop you getting that far.

The only thing I can think of is the CU setup in the VTS box does not
match that you have in the IOCP.

I cannot be certain but I am almost certain that we were still running 2.4
when we put VTS in here.

Regards

Colin Allinson

"HARROP, Roy" <***@nats.co.uk> wrote:
We are trying to put a VTS on a VM/ESA 2.4 system.

Yes, I know it's an old system... However, according to everything I've
read, this should be possible - support for 3494 was in VM/ESA version
1.2 I believe.

Has anyone out there done this? If so, can you help me get this lot
going. I assume it's something I'm doing wrong ( - always assume you're
doing something wrong, never blame the machines... :-) ?!? ).

When I try to bring any of the addresses online, I receive a "... no
channel path is available... " message, HCPCPN6283I.

I've done this on two different processor models - and when look at the
hardware channel problem determination screens on the 2003/204 service
processor, it tells me that there's a "Link configuration problem - init
failure - Channel/CU mismatch".

The processor can 'see' the VTS because its serial number shows up and,
on the VTS console service frames, the processor serial number shows up.
However, there's no system generated Link Address, so I assume I have
something wrong in the IOCDS. Various people have mentioned the
LIBRARY-ID statement, but VM's IOCP doesn't recognise that.

To begin with, the four CNTLUNIT/IODEVICE pairs in my IOCP source used
to be coded thus:

CNTLUNIT
CUNUMBR=0700,PATH=4F,UNIT=3490, CUADD=0,UNITADD=((00,16))

IODEVICE
ADDRESS=(700,16),CUNUMBR=0700,UNIT=3490,UNITADD=00

I made a couple of changes in a vain attempt to get it working - but to
no avail:

CNTLUNIT
CUNUMBR=0700,PATH=4F,UNIT=3490, CUADD=0,UNITADD=((00,2))

IODEVICE
ADDRESS=(700,2),CUNUMBR=0700,UNIT=3490,STADET=Y,UNITADD=00


Roy Harrop

[Michael Coffin]

Hi Roy,

I vaguely recall having some initial problems with our 3494-L14 on VM/ESA 2.4.0
running on a 7060-H30. I can't recall exactly what the problem was, but 3494's
are tempermental. You might try powering down the 3494, and use the CP DELETE
command to manually delete all of the RCTLUNIT and RDEV blocks and manually
redefine them correctly, then power up your 3494. Again, I can't recall the
specifics but I seem to recall if you powered your 3494 up/down more than a
couple of times while connected to a running VM/ESA 2.4.0 system somehow the
RDEV/CU blocks got messed up - it happened to us several times actually. Make
sure the microcode on the 3494 is current as well.

Michael Coffin, President
MC Consulting Company, Inc.
57 Tamarack Drive
Stoughton, Massachusetts 02072

Voice: [phone] FAX: [phone]

***@mccci.com
www.mccci.com

We employ aggressive SPAM filters. If you cannot reply or send email to
mccci.com go to www.mccci.com/spamblockremove.php





-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU] On Behalf
Of HARROP, Roy
Sent: Wednesday, March 08, 2006 7:46 AM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: 3494 VTS on VM/ESA


We are trying to put a VTS on a VM/ESA 2.4 system.

Yes, I know it's an old system... However, according to everything I've read,
this should be possible - support for 3494 was in VM/ESA version 1.2 I believe.

Has anyone out there done this? If so, can you help me get this lot going. I
assume it's something I'm doing wrong ( - always assume you're doing something
wrong, never blame the machines... :-) ?!? ).

When I try to bring any of the addresses online, I receive a "... no channel
path is available... " message, HCPCPN6283I.

I've done this on two different processor models - and when look at the hardware
channel problem determination screens on the 2003/204 service processor, it
tells me that there's a "Link configuration problem - init failure - Channel/CU
mismatch".

The processor can 'see' the VTS because its serial number shows up and, on the
VTS console service frames, the processor serial number shows up. However,
there's no system generated Link Address, so I assume I have something wrong in
the IOCDS. Various people have mentioned the LIBRARY-ID statement, but VM's IOCP
doesn't recognise that.

To begin with, the four CNTLUNIT/IODEVICE pairs in my IOCP source used to be
coded thus:

CNTLUNIT
CUNUMBR=0700,PATH=4F,UNIT=3490, CUADD=0,UNITADD=((00,16))

IODEVICE
ADDRESS=(700,16),CUNUMBR=0700,UNIT=3490,UNITADD=00

I made a couple of changes in a vain attempt to get it working - but to no
avail:

CNTLUNIT
CUNUMBR=0700,PATH=4F,UNIT=3490, CUADD=0,UNITADD=((00,2))

IODEVICE
ADDRESS=(700,2),CUNUMBR=0700,UNIT=3490,STADET=Y,UNITADD=00


Roy Harrop




**********************************************************************
This email and any files transmitted with it are confidential. If you are not
the intended recipient, please notify our Help Desk. Email ***@nats.co.uk
immediately. You should not copy or use this email or attachment(s) for any
purpose nor disclose their contents to any other person.

NATS computer systems may be monitored and communications
carried on them recorded, to secure the effective operation of the
system and for other lawful purposes.
********************************************************************************
************************************************************