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

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

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

I've done this on two different processor models - and when look at thehardware channel problem determination screens on the 2003/204 serviceprocessor, it tells me that there's a "Link configuration problem - initfailure - 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 havesomething wrong in the IOCDS. Various people have mentioned theLIBRARY-ID statement, but VM's IOCP doesn't recognise that.

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

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

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

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

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

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

Roy Harrop

**********************************************************************This email and any files transmitted with it are confidential. If youare 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 purposenor disclose their contents to any other person.

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

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

Sure, there are all sorts of config setup you have to do with DFSMS/RMSonce 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 notmatch that you have in the IOCP.

I cannot be certain but I am almost certain that we were still running 2.4when 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'veread, this should be possible - support for 3494 was in VM/ESA version1.2 I believe.

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

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

I've done this on two different processor models - and when look at thehardware channel problem determination screens on the 2003/204 serviceprocessor, it tells me that there's a "Link configuration problem - initfailure - 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 havesomething wrong in the IOCDS. Various people have mentioned theLIBRARY-ID statement, but VM's IOCP doesn't recognise that.

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

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

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

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

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

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. Iassume it's something I'm doing wrong ( - always assume you're doing somethingwrong, never blame the machines... :-) ?!? ).

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

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

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

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

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

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

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

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

IODEVICEADDRESS=(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 notthe intended recipient, please notify our Help Desk. Email ***@nats.co.ukimmediately. You should not copy or use this email or attachment(s) for anypurpose nor disclose their contents to any other person.

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