Hi
We are looking at using 2074s to replace a number of 3174s we have
supporting our consoles on our mainframes. We have installed a 2074
model 2 with two channel adapters connected to two 9032 Model 3 Escon
directors as a test box. We have two LPARs on a 2064-215 connected to
the Escon directors. These LPARs will be used for testing z/OS 1.7 as we
upgrade from z/OS 1.4. We have two channels from each LPAR attached to
each 9032. One channel for the master console and one channel for the
alternate console. There are other consoles and VTAM devices defined on
each channel. We are starting our testing with the TSTM LPAR with
channel 31 connected to port 80 in director #1 for it's master console
and channel 81 connected to port 80 in director #2. LPAR XXXX has
channel 3D connected to port 81 in director #1 and channel 8D connected
to port 81 in director #2. The out port to the 2074 is A0 on both Escon
directors. The LEDs on the channel adapters in the 2074s are both green
when the CAs in the 2074 are IMLed. The 9032s both see the 2074.
However, we can only get TSTM IPLed using the HMC and the 3174 addresses
defined on the channels won't come online. The 3174 is defined with 32
addresses starting at 380 with 398 being our master console. When Chpid
31 is configured online it says addresses 380 to 39F are available but a
display matrix of address 398 says path operational N. If you vary the
path for 398 offline then online, it says IOS552I PATH NOT PHYSICALLY
AVAILABLE. A display matrix on the channel shows device 398 as
*(physically online) and the other addresses are $@ path not operational
and not validated.
We have looked at the 2074 Configuration Guide, 2074 Installation and
Maintenance Information, the 2074 Red Book and the Washington System
Center Planning and Installation Guide for the 2074-003 and can't seem
to find our error. Here are our IOCDS definitions for TSTM:
RESOURCE PART=((ROSE,1),(TSTM,2),(XXXX,3))
CHPID31 CHPID PATH=31,PART=(TSTM),TYPE=CNC,SWITCH=07
CHPID81 CHPID PATH=81,PART=(TSTM),TYPE=CNC,SWITCH=08
CUD380 CNTLUNIT CUNUMBR=D381,PATH=(31),UNIT=3174,UNITADD=((80,32)),
LINK=(A0)
TUBE380 IODEVICE UNIT=3278,ADDRESS=(380,25),MODEL=2,
CUNUMBR=(D381)
TUBE399 IODEVICE UNIT=3278,ADDRESS=(399,2),MODEL=4,
CUNUMBR=(D381)
TUBE39B IODEVICE UNIT=3278,ADDRESS=(39B,2),MODEL=2,
CUNUMBR=(D381)
TUBE39D IODEVICE UNIT=3278,ADDRESS=(39D,2),MODEL=4,
CUNUMBR=(D381)
TUBE39F IODEVICE UNIT=3278,ADDRESS=(39F),MODEL=2,
CUNUMBR=(D381)
CUDD80 CNTLUNIT CUNUMBR=DD81,PATH=(81),UNIT=3174,UNITADD=((80,32)),
LINK=(A0)
TUBED80 IODEVICE UNIT=3278,ADDRESS=(D80,25),MODEL=2,
CUNUMBR=(DD81)
TUBED99 IODEVICE UNIT=3278,ADDRESS=(D99,2),MODEL=4,
CUNUMBR=(DD81)
TUBED9B IODEVICE UNIT=3278,ADDRESS=(D9B,2),MODEL=2,
CUNUMBR=(DD81)
TUBED9D IODEVICE UNIT=3278,ADDRESS=(D9D,2),MODEL=4,
CUNUMBR=(DD81)
TUBED9F IODEVICE UNIT=3278,ADDRESS=(D9F),MODEL=2,
CUNUMBR=(DD81)
The IODF looks like this:
TUBE380 IODEVICE UNIT=3278,ADDRESS=(380,8),MODEL=4,STADET=N,
FEATURE=(DOCHAR,EBKY3277,KB78KEY),CUNUMBR=(0380)
TUBE388 IODEVICE UNIT=3270,ADDRESS=(388,19),MODEL=X,STADET=N,
FEATURE=(DOCHAR,EBKY3277,KB78KEY),CUNUMBR=(0380)
TUBE39B IODEVICE UNIT=3278,ADDRESS=(39B,2),MODEL=4,STADET=N,
FEATURE=(DOCHAR,EBKY3277,KB78KEY),CUNUMBR=(0380)
TUBE39D IODEVICE UNIT=3270,ADDRESS=(39D,2),MODEL=X,STADET=N,
FEATURE=(DOCHAR,EBKY3277,KB78KEY),CUNUMBR=(0380)
TUBE39F IODEVICE UNIT=3278,ADDRESS=(39F),MODEL=2,STADET=N,
FEATURE=(DOCHAR,EBKY3277,KB78KEY),CUNUMBR=(0380)
TUBED80 IODEVICE UNIT=3278,ADDRESS=(D80,8),MODEL=4,STADET=N,
FEATURE=(DOCHAR,EBKY3277,KB78KEY),CUNUMBR=0D80
TUBED88 IODEVICE UNIT=3270,ADDRESS=(D88,23),MODEL=X,STADET=N,
FEATURE=(DOCHAR,EBKY3277,KB78KEY),CUNUMBR=0D80
TUBED9F IODEVICE UNIT=3278,ADDRESS=(D9F),MODEL=2,STADET=N,
FEATURE=(DOCHAR,EBKY3277,KB78KEY),CUNUMBR=0D80
The IOCDS and IODF definitions for XXXX are similar to the above for
TSTM
.
The 2074 devices were configured like this for CA0:
Index Dev LPAR Port CU UA MGR Parameters
01 3278 2 80 0 80 2 /R=TSTMOC
02 3278 2 80 0 88 2 /R=TSTMVT
03 3278 2 80 0 8B 2 /R=TSTMVT
04 3278 2 80 0 98 2 /R=TSTMMC
05 3278 2 81 0 80 2 /R=XXXXOC
06 3278 2 81 0 88 2 /R=XXXXVT
07 3278 2 81 0 8B 2 /R=XXXXVT
08 3278 2 81 0 98 2 /R=XXXXMC
The devices for CA1 are configured the same, We also tried a UA offset
of 00, 08, 0B and 18. We also tried PORT definitions of 00 and 01
instead of 80 and 81.The BTITOOL Show Neighbor Info command for each CA
shows that each CA is connected to the correct 9032. Any help you can
give us in getting this 2074 working would be appreciated since we are
looking at replacing over 40 3174s used as console controllers with 4
2074s in our two sites.
John Parsons
Lead Systems Engineer
Thomson Legal and Regulatory
610 Opperman Dr. E1-N357
Eagan, MN 55123
651-687-8049
----------------------------------------------------------------------
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
