INTEROPERABILITY BY MIKE NELSON INSIGHTS The Transition to the P/390: A User’s Experience his article describes my company’s experience installing and using the IBM PC Server 500 System/390, or P/390 as it is called. The ordering and installation of both the T hardware and software was a very different process from that of the traditional MVS hardware and software. This article highlights the experiences of one We ordered the hardware and software system software was not delivered. After company that installed from IBM Direct through the S/390 Partners many phone calls to several 800 numbers, in Development organization (formerly known MVS arrived about two weeks later. the IBM PC Server as the S/390 Developers Association) based Preparing to install the P/390 is not unlike 500 System/390, on a list of features supplied by IBM. This any other system. You must take the time to allowed us to choose the type of hardware, read through the materials supplied. The first and presents some including optional components, as well as the thing you must do is install the PC hardware, operating systems we wanted. We chose if any, and any drivers needed for this hard- guidelines for other MVS/ESA 5.2 as our operating system, but ware. Our only additional hardware was 32 sites contemplating this VM and VSE could have been chosen also. MB of added OS/2 memory. Our P/390 has 64 MB memory for OS/2 The RAID controller diskette must be cre- type of implementation. and 128 MB for MVS. We have divided our ated to configure the disk array. You must use MVS memory into 96 MB for real storage the ServerGuide CD to create the diskettes and 32 MB for expanded storage to help keep needed. See the PC Server 500 User’s MVS paging down. The DASD layout con- Handbook for details on creating the diskettes sists of five 2.25 GB drives for a total of using the ServerGuide. Once the RAID con- 11.25 GB. We chose to use RAID 5 for our figuration diskettes are created, you must disk array subsystem based on a trade-off of decide what RAID configuration you want to data recovery and performance. Using RAID use. We chose the RAID 5 disk array because 5 left us with 9 GB of DASD available for the it has the best mix of performance, capacity, OS/2 and MVS operating systems. At our and recoverability of the RAID configura- site, we have a mixture of both Token-Ring tions. Keep in mind, that with RAID 5, you and Ethernet LANs. All of our “terminals” will lose the capacity of one installed drive. utilize Ethernet, and the Token-Ring is used For example, our disk configuration con- for connection to our 9221 mainframe tained five 2.25 GB disks for a total of 11.25 through a 3720 front-end processor. To allow GB; using the RAID 5 configuration we have us to connect the P/390 into the current system, a total or 9 GB of disk space. This provides us we chose the Auto LANStreamer card. We with automatic recovery in case of a disk opted not to get the optional S/370 channel drive failure. From an MVS/ESA standpoint, emulator. The S/370 channel emulator there is no difference in any of the RAID allows the connection of all S/370 devices via options, because MVS/ESA is not aware that bus/tag connection except for DASD RAID support is being used. (3380/3390). We also have the 4mm DAT Once you have created your RAID con- tape drive and a CD/ROM, which are standard troller diskette from the ServerGuide CD, devices with the P/390. insert this diskette into the primary drive on We placed the order for our P/390 in the P/390 and press Ctrl+Alt+Del to reboot. August 1995, and received it in October, The main menu will appear, and you may which was good response. We encountered proceed with the configuration. One option to one problem, however. The MVS operating keep in mind when configuring the RAID TECHNICAL SUPPORT MARCH 1996 INTEROPERABILITY INSIGHTS Figure 1: VTAM Definition Samples Figure 1: VTAM Definition Samples - continued ATCSTRxx vtamlst member for 9221: P390T005 LU LOCADDR=6 SSCPID=01,NOPROMPT,SSCPNAME=EMPSS,NETID=EMP, X . CONFIG=00,MAXSUBA=15,SUPP=NOSUP, X . NOTRACE,TYPE=VTAM, X TNSTAT,CNSL,TIME=60, X The NCP definitions added for the P/390 connection. This is assuming you already have CSA24=1024, X the NCP genned to support a current Token–Ring connection. IOINT=0, X CRPLBUF=(120,,2,,30,3), X *——— LOGICAL INN CONNECTION FOR P390 ————–––––————————- IOBUF=(88,384,3,F,28,33), X * LPBUF=(24,,2,,1,4), X LATRI102 LINE LOCALTO=2.5, (LN) LOCAL STATION T1 TIMER VALUE * LFBUF=(4,,,,1,1), X REMOTTO=2.5, (LN) REMOTE STATION T1 TIMER VALUE * SPBUF=(04,,,,1,1), X T2TIMER=(0.3,0.3,3), (LN) T2 TIMER VALUE * SFBUF=(100,,,,1,1), X UACB=X$L2A CRPLBUF=(120,,2,,20,3) * PATRI102 PU AD D R = 0 4 4 0 0 0 7 4 9 0 0 0 0 1 , (PN) SAP/LAA OF REMOTE TOKEN-RING * ATCSTRxx vtamlst member for P/390: NETID=EMP, (PN) LINK STATION NETWORK NAME * SSCPID=06,NOPROMPT, X PUTYPE=4, (PN) PHYSICAL UNIT TYPE * CONFIG=00,MAXSUBA=31,SUPP=NOSUP, X TGN=1 (PN) LINK STATIONS TGN * SSCPNAME=P390SS, X With the above definitions added, we needed the ability to move datasets, load libraries, NETID=EMP, X JCL libraries, etc., from our mainframes to the P/390. This is done using standard NJE HOSTSA=6, X definitions for both JES2 and VTAM. Attached are the changes needed for the NJE connection. CRPLBUF=(208,,15,,30,16), X Using the 3720 for the front–end processor requires us to use a 4 MB Token–Ring. This IOBUF=(100,384,19,,28,33), X connection is suprisingly fast when downloading datasets. LFBUF=(104,,0,,1,1), X LPBUF=(64,,0,,1,1), X VTAM definitions on the 9221. SFBUF=(163,,0,,1,1) EMPCDRMS VBUILD TYPE=CDRM Since the AWS3172 device driver emulates a 3172, you must have at least one UCB genned as a CTC EMPSS CDRM SUBAREA=1,CDRDYN=YES,CDRSC=OPT (3088). Once this is done, you can set up the VTAM definitions that define the 3172 connection. P390SS CDRM SUBAREA=6,CDRDYN=YES,CDRSC=OPT * * 3172 LAN CONNECTION N15CYADJ VBUILD TYPE=ADJSSCP * P390SS ADJCDRM LANTRXCA VBUILD TYPE=XCA XCA MAJOR NODE VTAMA ADJCDRM PORT1 PORT MEDIUM=RING, TOKEN RING LAN X SAPADDR=4, SERVICE ADDRESS POINT ADDRESS X ***************************************************************** ** ADAPNO=0, ADAPTER NUMBER X * PATH DEFINITIONS TO 3720 * CUADDR=E20 CHANNEL UNIT ADDRESS ***************************************************************** ** * PATH DESTSA=(15), C * XCA MAJOR NODE FOR TOKEN RING ER0=(15,1), C * ER1=(15,1), C GROUP1 GROUP ANSWER=ON, DIAL WILL ACCEPT CALLS X ER6=(15,1), C CALL=INOUT, DIAL ON AND OUT X VR0=0, C DIAL=YES, SWITCHED NODE (PERIPHIAL CONNECT) X VR1=1, C ISTATUS=ACTIVE ACTIVATE AT GEN VR6=6 LINE1TA LINE ***************************************************************** ** PU1TA PU * PATH DEFINITIONS TO P390 * GROUP2 GROUP DIAL=NO, NO SWITCED LINE (SUBAREA CONNECT) X ***************************************************************** ** ISTATUS=ACTIVE ACTIVATE AT GEN PATH DESTSA=(6), C LINE2TA LINE ER0=(15,1), C PU2TA PU MACADDR=400045210101, ADDR OF 3720 TOKEN RING X ER1=(15,1), C PUTYPE=4, X VR0=0, C SAPADDR=04, X VR1=1 SUBAREA=15, NCP SUBAREA ID X TGN=1 EMPNJE VBUILD TYPE=APPL EMPNJE1 APPL ACBNAME=EMPNJE1,EAS=4,AUTH=(PASS,ACQ,VPACE), X The VTAM Switched major node must be defined if one does not exist. VPACING=4,MODETAB=MODETEMP,DLOGMOD=JES2NJE * * SWITCHED MAJOR FOR TOKEN RING 3172 VTAM defintions on the P/390 * P390SWI VBUILD TYPE=SWNET,MAXGRP=32,MAXNO=32 EMPCDRMS VBUILD TYPE=CDRM * EMPSS CDRM SUBAREA=1,CDRDYN=YES,CDRSC=OPT P390SPU1 PU ADDR=01, X P390SS CDRM SUBAREA=6,CDRDYN=YES,CDRSC=OPT ANS=CONT, X CPNAME=P390SWT, X * DLOGMOD=EMC32792, X PATH DESTSA=(15), C IDBLK=05D, X ER0=(15,1), C IDNUM=00001, X ER1=(15,1), C IRETRY=YES, X ER6=(15,1), C ISTATUS=ACTIVE, X VR0=0, C MAXDATA=1024, VR1=1, C MAXOUT=7, X VR6=6 MAXPATH=4, X * MODETAB=MODETEMP, X PATH DESTSA=(1), C PASSLIM=5, X ER0=(15,1), C PUTYPE=2, X ER1=(15,1), C USSTAB=USSEMPS VR0=0, C P390PTH1 PATH DIALNO=0004400074900001, TIC(2)/SAP(2)/MACADDR X VR1=1 GRPNM=GROUP1 * NJEP390 VBUILD TYPE=APPL P390NJE APPL ACBNAME=P390NJE,EAS=4,AUTH=(PASS,ACQ,VPACE), X P390T001 LU LOCADDR=2 VPACING=4,MODETAB=MODETEMP,DLOGMOD=JES2NJE P390T002 LU LOCADDR=3 P390T003 LU LOCADDR=4 Also, you may need to create a Class of Service table on each machine (ISTSDCOS). P390T004 LU LOCADDR=5 INTEROPERABILITY INSIGHTS Figure 2: JES2 Definitions of the choices require some advanced planning. Make sure you use the CD-ROM version of OS/2 Warp shipped with the PC Server S/390 The JES2 definitions added to the 9221. and not the one shipped with the ServerGuide. During the OS/2 Warp APPL(P390NJE) NODE=x installation, we created a 200 MB FAT partition for OS/2 and other - - - - - - - - programs. The rest of the drives we configured as an HPFS partition CONNECT NODEA=1, for P/390 programs and emulated 3380s, etc. MEMBERA=1, NODEB=x, MVS/ESA also requires Communications Manager/2 (CM/2) to be MEMBERB=1, installed. CM/2 allows the PC Server System/390 to use the OS/2 PATHMGR=NO, video to emulate a local non-SNA 3270 device, which will be used as REST=2 the MVS master console.You need to use CM/2 Version 1.11 shipped - - - - - - - - LINE(x) UNIT=SNA with the P/390 rather than the ServerGuide.