Coding for UNIT=3590

[Mohammed Imam]

Hello,

I need to replace 3490 ESCON with 3590 FICON tape units.
I would appreciate if someone could share their IOCP codes for tape
3590.

Thanks,
Mohammed A. Imam
County of Cumberland, NC.
(910) 678-7680.

[Mike Moore]

Here is what we have:

* -------------------------------------------------------------

* 3590 TAPES

* -------------------------------------------------------------

CHPID PATH=1F,TYPE=FC,PCHID=120,PARTITION=(AJDCPRD)

CHPID PATH=21,TYPE=FC,PCHID=121,PARTITION=(AJDCPRD)

CNTLUNIT CUNUMBR=0800,PATH=(1F,21),UNIT=3590,UNITADD=((00,04))

IODEVICE ADDRESS=(0800,04),CUNUMBR=(0800),UNIT=3590

* -------------------------------------------------------------

Mike Moore
IT Manager
Alabama Judicial Datacenter
300 Dexter Ave
Montgomery, AL 36104
334-954-5025

[indust...@winwholesale.com]

owner...@Lehigh.EDU wrote on 07/03/2008 11:07:37 AM:
> I need to replace 3490 ESCON with 3590 FICON tape units.
> I would appreciate if someone could share their IOCP codes
> for tape 3590.

Ours are dual-pathed and shared across LPARs:

CHPID PCHID=160,PATH=60,TYPE=FC,SHARED .ESCON 3590 Tape
CHPID PCHID=170,PATH=70,TYPE=FC,SHARED .ESCON 3590 Dual-Path
CNTLUNIT CUNUMBR=0C04,UNIT=3591,UNITADD=((00,04)),PATH=(60,70)
IODEVICE CUNUMBR=0C04,UNIT=3590,ADDRESS=(200,04),STADET=Y

Sincerely,

Dave Clark

WinWholesale Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331

[Mohammed Imam]

Thanks Mike,

Question:
What are advantages and/or disadvantages of using devices from 2
different paths as opposed to single path with RECONFIGURABLE option to
be shared among LPARs.

Thanks,
Mohammed A. Imam

[Mike Moore]

The system can choose whichever path gets the data to and from there the
fastest. It also gives us a failover if something should happen to one
of the paths.

[indust...@winwholesale.com]

owner...@Lehigh.EDU wrote on 07/03/2008 11:22:12 AM:
> Ours are dual-pathed and shared across LPARs:

> CHPID PCHID=160,PATH=60,TYPE=FC,SHARED .ESCON 3590 Tape
> CHPID PCHID=170,PATH=70,TYPE=FC,SHARED .ESCON 3590 Dual-Path
> CNTLUNIT CUNUMBR=0C04,UNIT=3591,UNITADD=((00,04)),PATH=(60,70)
> IODEVICE CUNUMBR=0C04,UNIT=3590,ADDRESS=(200,04),STADET=Y

Sorry, the comments in what I posted previously did not match the
definitions. The following are both kinds of definitions -- with matching
comments this time.

CHPID PCHID=160,PATH=60,TYPE=CNC,SHARED .ESCON 3590 Tape
CHPID PCHID=170,PATH=70,TYPE=CNC,SHARED .ESCON 3590 Dual-Path

CHPID PCHID=160,PATH=60,TYPE=FC,SHARED .FICON 3590 Tape
CHPID PCHID=170,PATH=70,TYPE=FC,SHARED .FICON 3590 Dual-Path

[Mark Pace]

With ESCON & FICON you don't need reconfigurable.  Just define it as shared to each partition.  Vary on and off as required.

--
Mark Pace
Mainline Information Systems

[Mohammed Imam]

Mike,

Would there be any conflict when requests are made to use the same
device (same address) from multiple LPARs simultaneously in a normal
working situation.

How the system allocates the device to satisfy each requests. Would it
be based upon first come first serve basis or the job priority or what.

[Mike Moore]

I'm not really sure how the sequence is determined--I would think FCFS
would make sense. We don't run multiple LPARs here so I've never chased
it. FICON is so much faster than ESCON my guess is it would be a moot
point.

[Mohammed Imam]

Dave,

Is it possible to have multiple TYPEs (CNC and FC in your case) defined
on the same PATH.

Mohammed A. Imam

-----Original Message-----
From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf
Of indust...@winwholesale.com
Sent: Thursday, July 03, 2008 11:44 AM
To: VSE Discussion List

[indust...@winwholesale.com]

owner...@Lehigh.EDU wrote on 07/03/2008 11:46:24 AM:
> Would there be any conflict when requests are made to use the same
> device (same address) from multiple LPARs simultaneously in a normal
> working situation.

> How the system allocates the device to satisfy each requests. Would it
> be based upon first come first serve basis or the job priority or what.

We are native VSE (no stinkin' VM, as Bob would say). We don't do
any reconfiguring or varying anything on or off. The first LPAR to request
the device gets it. The second LPAR gets a non-blocking DEV IN USE error
message, the job step fails, but the job may continue trying to execute
subsequent job steps depending on what failed, whether you could set any
return codes, and how you're handling conditional JCL.

[indust...@winwholesale.com]

owner...@Lehigh.EDU wrote on 07/03/2008 11:52:12 AM:
> Is it possible to have multiple TYPEs (CNC and FC in your case)
> defined on the same PATH.

No, since the path indicates to controller card connection and, thus,
would be limited to the type of controller card where FC=FICON. ESCON has
different types (see below) for different types of device connections but I
haven't seen anything for FICON that wasn't FC. Maybe someone else has
seen that -- don't know.

CHPID PCHID=160,PATH=60,TYPE=CNC,SHARED .ESCON 3590 Tape

CHPID PCHID=161,PATH=61,TYPE=CTC,SHARED .ESCON LPAR-to-LPAR
CHPID PCHID=162,PATH=62,TYPE=CVC,PART=(PROD) .ESCON Conv 4245 Prt.
CHPID PCHID=163,PATH=63,TYPE=CNC,SHARED .ESCON
*

CHPID PCHID=170,PATH=70,TYPE=CNC,SHARED .ESCON 3590 Dual-Path

CHPID PCHID=171,PATH=71,TYPE=CNC,SHARED .ESCON LPAR-to-LPAR
CHPID PCHID=172,PATH=72,TYPE=CNC,SHARED .ESCON
CHPID PCHID=173,PATH=73,TYPE=CNC,SHARED .ESCON

[indust...@winwholesale.com]

owner...@Lehigh.EDU wrote on 07/03/2008 11:57:26 AM:
> No, since the path indicates to controller card connection and, thus,
> would be limited to the type of controller card where FC=FICON.

Corrections:

...indicates the interface controller card connection...
...type of interface controller card...