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 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 , 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), * 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. More about VTAM ter------minal support is covered later in this article. NODE(4) NAME=P390NJE, LAN adapter and protocol support (LAPS) must also be installed PATHMGR=NO on the P/390 if you plan to use other terminals or on a The JES2 parms added on the P/390. LAN.You can use the client feature to access the MVS/ESA system from OS/2, Windows, or DOS client workstations. OS/2 workstations APPL(EMPNJE1) NODE=x on the LAN can appear to the P/390 as local non-SNA terminals. ------OS/2, DOS, and Windows workstations can be attached as switched CONNECT NODEA=1, MEMBERA=1, definitions. We currently have all of our PCs attached to an Ethernet NODEB=x, LAN running Novell NetWare. We use the IRMA Windows client MEMBERB=1, for 3270 terminal emulation, and the IRMALAN Gateway as the PATHMGR=NO, connection point to both the Ethernet and Token-Ring LANs. LAPS REST=2 ------is supplied as part of CM/2, and is contained on the CM/2 CD-ROM. LINE(x) UNIT=SNA This installation is very important because it sets up the P/390 so it LINE(x) UNIT=SNA can communicate to other LANs within your complex. The IBM ------Token-Ring Network Adapter address, a very important parameter, is LOGON(x) APPLID=P390NJE ------the old 400074900001 address which will be used later in your NJEDEF DELAY=120, VTAM definitions. JRNUM=3, Once OS/2, CM / 2 , and LAPS have been installed, you are rea d y to SRNUM=3, install the P/390 programs and MVS/ESA. The r e are some OS/2 tuning JTNUM=3, STNUM=3, options you may want to be awar e of: LINENUM=2, OS/2 CONFIG.SYS Parameters: NODENUM=3, OWNNODE=1, ■ MAXWAIT - Defines the number of seconds that an OS/2 thread PATH=1, RESTMAX=7992000, waits before being assigned a higher dispatching priority. I/O- RESTTOL=0, intensive applications could be n e f it from setting this to 1. RESTNODE=100 The default is 3. MAXWAIT=1. ------NODE(x) NAME=P390NJE, PATHMGR=NO ■ DISKCACHE - If you defined no FAT partitions this can be commented out. It could save OS/2 memory. NODE(x) NAME=EMPNJE1, PATHMGR=NO ■ PRIORITY_DISK_IO -This parameter controls whether or not an app l i c a tion running in the OS/2 for eground rec e i ves prio r ity for disk-array is the Write Policy. Automatically, this is set to write- disk I/O over background tasks. MVS drivers for the P/390 are through (WT) mode, where the completion status is sent after the data co n s i d e r ed backg rou n d . OS/2 command-line windows, among is written to hard disk drive. You can change this write policy to write- others, are considered foreground.The suggestion here is NO, back (WB) mode, where completion status is sent after the data is but the default is YES.This ensures background functions (i.e., copied to cache, but before the data is actually written to the di s k . MVS disk requests) are processed at the same priority as OS/2 Ho wever , this increases the risk of data loss due to a power fai l u r e. foreground functions. Another important RAID setting is the stripe unit size, which is the amount of data written to a disk before writing on the next disk. The Also look into the following HPFS driver parameters: default stripe unit size is 8 KB data bytes. Sizes larger than 8 KB can provide better MVS performance, but if the PC Server 500 is to ■ HP F S .IFS de vice driver CAC H E : nnnn - The default value both MVS and OS/2 workloads, you must take this into consideration depends upon the RAM available at installation. The when setting this val u e . Once the stripe unit size is cho s e n , and data is rec o m m e n d a tion is /CACH E : 2 0 4 8 , assuming the HPFS file written on the disks, you will have to back up and restore all your data system is being used. in order to change the stripe unit size. If not, you will lose all data in the array! For our purposes, the P/390 is strictly an MVS processor, ■ /CRECL - Specifies the largest record (in a single write) that is so we chose to use the 64 KB stripe size. Performance has been good eligible for the ca ch e . The default is 4 KB. Increasing this val u e so far, and we have seen no ill effects using this stripe size value. ma y improve MVS I/O perform a n c e .

INSTALLING OS/2 ■ LAZY writ e s - I/O completion is signaled complete when the data OS/2 must be installed on the PC Server System/390 before is placed in HPFS cache . This can improve perfor mance; however , MVS/ESA can be used.This is a standard OS/2 installation, but some keep in mind the exposure if power is lost. INTEROPERABILITY INSIGHTS

INSTALLING THE S/390 PROGRAMS we have not figured out why the file size is initialize the DASD.You will also need to The PC Server 500 S/390 programs can be larger, but IBM is investigating a problem update ‘SYS1.PARMLIB’ as necessitated by installed any time after OS/2 has been we’ve had with the file size calculation. your site. installed.This consists of three diskettes plus You can emul a te all 3380 devices; however , We have a 9221 processor used for devel- an A dvanced Diagnostics and Options we did not define any 3380 greater than the E opment at our location, and a 9021 and 9672 diskette.The installation is straightforward; model. Following is a breakdown of the 3380 CMOS processor at our California data cen- simply follow the prompts used during the device sizes: ter.We wanted the P/390 accessible in our install process. The P/390 support will auto- V TAM netwo rk so all deve l o p e rs could matically update the CONFIG.SYS file.The ■ Single Density - 885 cylinders, 15 tracks/ access it from their current terminals. P/390 softwar e will be placed in a subdirec t o r y cyl i n d e r , 47476 byt e s / t ra ck , about 630 MB The P/390 has several device drivers that named x:/P390, and a P/390 icon will appear ■ Double Density - 1770 cylinders, will allow for connectivity using SNA. We on the OS/2 desktop. The P/390 installation 15 tracks/cylinder, 47476 bytes/track, chose to use the AWS3172 driver which will add the necessary programs and about 1260 MB allows us to connect our Ethernet LAN ter- device/emulator drivers needed to run MVS ■ Triple Density - 2665 cylinders, minals to the To ke n - R i n g - at t a ched 3720 on the P390. The device drivers are centered 15 tracks/cylinder, 47476 bytes/track, front-end processor. around the configuration program. about 1890 MB The AWS3172 device manager emulates The confi g u ration program defines the an IBM 3172 (Model 1, and some Model 3 mapping of MVS devices to the device man- The number of 3380s you can use depends functions) using the Token-Ring adapter. It agers and files used under OS/2 to emulate upon the size 3380 you define.We created a can be used for workstations using SNA 3270 the devices. This configuration program is total of 16 3380 volumes of various sizes: emulation, as well as NJE and CICS ISC essentially the IOCP. Since the P/390 has no links from the P/390 MVS system to another IOCP, all devices and their characteristics are ■ four double-density volumes for the mainframe MVS system. d e fined here. The MVS Hardwa re preconfigured MVS packs; You may recall, we installed and defined Configuration Definition (HCD) is still used, ■ one single-density volume; LAPS early in the installation of the P/390. but this will define the hardware layout for ■ nine 400-cylinder volumes; and For To ken-Ring adapter we specified a OS/2. For a list of device drivers and what ■ two 200-cylinder volumes. Network Adapter Address (400074900010). they emulate, refer to the documentation you This will be used as the remote VTA M received with your P/390. The smaller volumes are form a tted by MVS MACADDR address. We defined both the When MVS is installed using the precon- ICKDSF as minidisks and are crea ted as odd- node for 3270 sessions as well as fi g u red system, a device map si z ed volumes the same way VM wou l d . We the subarea node for the NJE connection (DEVMAP.MVS) is unloaded.This device de f ined many smaller volumes for the testing between our other MVS mainframes. The map matches the MVS system installed from and development of our storage prod u c t s . P/390 could not be defined as an SNI con- the CD-ROM. If you are not using the pre- The aforementioned DASD configuration nection, so we made the VTAM NETID c o n fi g u red system, you must cre ate a can be done after the preconfigured MVS match our existing 9221 NETID. DEVMAP.MVS file to define the MVS hard- is installed. Howeve r, you must have a I have included samples of our VTAM and ware configuration. This is done using the ge n e ral idea of wh at is needed befo re JES2 definitions because there are no clear AWSCFG program. proceeding. I would also suggest obtaining samples of this included with the P/390 doc- This completes the installation of all OS/2 the IBM Redbook, MVS and the IBM PC umentation. See Figures 1 and 2. software needed to support MVS.You will Server 500 System/390 (GG24-2538), which The parameters in Figures 1 and 2 will need to reboot OS/2 to pick up all the new is a great help. need to be modified based on your current P/390 devices drivers added into the CON- Installation of the preconfigured system NJE configuration. These parameters were FIG.SYS file. copies files from the CD-ROM to the P/390 added as guidelines. With these definitions in hard disk drive is easy.These files are images place, the developers are able to logon to any INSTALLING MVS of the MVS/ESA operating system. To start MVS systems in the network and send data to MVS/ESA can be installed using any of the install, place the MVS CD in the CD- and from these systems. the following methods: ROM drive and type: x:install. Follow the prompts through the install. This process took BACKING UP ■ using a preconfigured system on several hours, but it was very simple. Once Backing up your data is just as important a CD-ROM; the files are copied, you are ready to IPL on the P/390 as on any mainframe.With the ■ copying it from another PC Server S/390; MVS.To IPL MVS, CM/2 must be active. 4mm DAT tape drive we have used ■ co p ying it from another S/390 hardwar e; or You can doubl e - cl i ck in the IPL 390 DFSMSdss as we would on our mainframe to ■ installing the initial products from other Processor icon to begin IPL. Once this is do volume level backups. The 4mm DAT uses media. started, MVS will use one of the CM/2 termi- an OS/2 device driver, which makes it look nals as the master console.There is an alter- like a 3480 cartridge tape to MVS. B e fo re installing MVS/ESA, s o m e nate console and three other terminals avail- We are currently using SYTOS Premium ad vanced planning is needed; DASD planning able for using TSO.You will need to review to back up the OS/2 files. The only problem is probably the most important. Both CKD the file x:\\readme.mvs, which contains we have encountered is that you can not have and FBA devices can be emulated by the i n fo rm ation needed about MVS vo l u m e s the SYTOS 4mm DAT driver and the S/390 P/390. For this discussion, I will examine the (SYSRES, DLIB, etc) and TSO logon IDs. 3480 device driver in the same CKD devices, since these are the ones we MVS/ESA is now available for further CONFIG.SYS.To get around this problem, chose to use. One OS/2 file will be created c u s t o m i z at i o n , s o f t wa re installat i o n , and we created two different CONFIG.xxx files: for every 3380 device you define, and the production use. C O N F I G. O S 2 , wh i ch contains only the OS/2 file will be slightly larger than the actual When you add new 3380 devices to the device drivers needed for OS/2 and SYTOS; size of the defined 3380 DASD. At this point, device, you must use the ICKDSF program to and CONFIG. M V S, wh i ch contains the INTEROPERABILITY INSIGHTS device drivers needed for OS/2 and MVS. We rename the correct CONFIG.xxx file to CONFIG.SYS depending on what we plan to do with the P/390, and reboot. You must also plan for disaster recovery situations. We had this type of problem when we copied some files we did not need, but failed to change the JES2 proc.This caused JES2 to have a JCL error, and we had to restore the packs that contained the deleted datasets. As the P/390 is delivered, only the standalone version of ICKDSF was supplied. We needed the standalone ve rsion of DFSMSdss to restore our backup tapes. This created a problem because we had no real 3480 to used the standalone DFSMSdss. The solution was to logon to the 9221 mainframe and copy from SYS1.SAMPLIB member ADRDMPRS to a floppy diskette. On the P/390 we copied the diskette to a fi l e D:\MVS\DFDSS.IPL. In the P/390 configu- rator, we used the AWS2540 device driver to e mu l ate a card reader pointing to the DFDSS.IPL file, and used the standalone ver- sion of DFSMSdss this way. Keep in mind, when you perform a standalone function, use the configurator to set up the 3215 terminal d evice driver so it emu l ates a dedicat e d standalone restore console.

PERFORMANCE AND USABILITY OUTWEIGH THE DRAWBACKS This arti c le has highlighted sever al feat u re s of the P/390. As you use the P/390, I am sure you will discover many more. This machine has been in production for several months, and performance results are good. Generally, we have five or fewer TSO users, but we have had as many as 15 users without any notice- able performance degradation. The only problem we have found is that running batch jobs, such as SMP/E, takes a heavy toll on CPU utilization. Any process that is very I/O-intensive can also prove to be a performance bottleneck. Considering the size, cost, and overall topology of the P/390, the performance and usability outweigh the drawbacks. ts

Mike Nelson is an advisory for Boole & Babbage Storage Division, Conyers, Ga. He has 15 years experience in MVS sys - tems programming.

©1996 Technical Enterprises, Inc. Reprinted with permission of Technical Support mag- azine. For subscription information, email [email protected] or call 414-768-8000, Ext. 116.

TECHNICAL SUPPORT MARCH 1996