PC Server S/390 Pre-configured System for VSE/ESA - Version 2.3.0 (12/97) ------------------------------------------------------------------------ Thank you for using this Pre-configured System for VSE/ESA. The system is designed to help you get a VSE system up and running quickly, so you can concentrate on getting your work done. You should be aware that the VSE/ESA system on this CD may not be at the most current service level. Reminder: make sure you have installed Communications Manager/2 and that as many as 4 (or at least 2) DFT sessions are configured to LOCAL in the P/390 Configurator. Also, you must start Communications Manager/2 prior to IPLing the VSE system. The first DFT session configured as LOCAL will become the operator's console. This pre-configured VSE/ESA system was built on emulated 9336 FBA DASD. It is a two pack system (DOSRES & SYSWK1) built following the installation process defined in the VSE/ESA Version 2 Installation Manual (SC33-6604). The following replies have been given to the VSE/ESA installation process: Addr DOSRES = 140 Addr SYSWK1 = 141 Environment = B Security = NO Access Method = VTAM Local CU SNA = NO Local 3270 Addr = 200 Local 3270 Addr = 201 Local 3270 Addr = 202 FCB/UCB = default IMPORTANT NOTE: the number of blocks defined in DEVMAP.VSE for the emulated 9336 FBA DASD does not match the number of blocks found on a real 9336 device (920,115). The number of blocks has been rounded up to the nearest 4K increment (921,600). This will enable VM mini disk caching of DOSRES and SYSWK1 for those VM/VSE users who choose to do so. This also means that the volumes are slightly larger than the ones on the Pre-configured System CD for VSE/ESA 2.1.0. The system uses the predefined environment B which includes: VSIZE = 180M # of Address Spaces = 12 # of Static Partitions = 12 # of Dynamic Partition Classes = 4 Supervisor Mode = ESA ($$A$SUPX) Default IPL Proc = $IPLESA Default JCL Proc = $$JCL There are 4 terminal sessions defined (01F, 200, 201 and 202). The operator console (01F) will come up on the first DFT Session in CM/2 that is de- fined as LOCAL in the P/390 Configurator. For P/390: The operator console (01F) will come up on the first DFT Session in Communications Manager/2 that is defined as LOCAL in the P/390 Configurator. For R/390: The operator console will come up on the first 3270 Emulation session which is opened during IPL of R/390 Note that there are two 3422 tape devices, 500 and 501 that are configured as harddisk files. Also the 4mm DAT drive has been configured as a 3480 tape drive at address 590 and is included in the $IPLESA.PROC. Even if you are planning on installing VSE from tape, you may wish to install this pre-configured system initially for two reasons: 1) It is the quickest way to get an initial system to gain experience with the PC Server System/390. 2) You can install from 4mm tape over the pre-configured system to get to the most current level of VSE/ESA. This install will actually be faster than basic tape install because you do not have to wait for the 9336 DASD volumes to format. However it will delete some pre-definitions done in the starter system. See PREDEFINITIONS later in this file. Installation on P/390: (for installation on R/390 see /cdrom/aix/readme.aix) --------------------- The install process is started by opening an OS/2 window and typing: x:\install Where x is the drive letter assigned to the CD-ROM drive. You will be prompted for the destination drive where you want VSE/ESA installed. The install process unpacks and copies the DOSRES.140 and SYSWK1.141 and sets d:\VSE\DEVMAP.VSE as the current DEVMAP. If you have installed VM/ESA from a pre-configured CD before and you do this VSE/ESA installation as second step to run VSE/ESA under control of VM/ESA, you have to set the current DEVMAP back to the VM/ESA DEVMAP This can be done by: 1. opening an OS/2 Window 2. typing AWSPROF x:\VMESA\DEVMAP.1VM where x: is the drive letter where VM/ESA has been installed before A current Preventative Service Planning (PSP) tape has also been applied to the system (if available) using the VSE Interactive Interface (II) and the procedures outlined in the VSE/ESA Version 2 System Upgrade and Service Manual (SC33-6602). As with all Operating Systems, it is recom- mended that you maintain corrective service currency. This system contains the following program products: PRODUCT NUMBER VERSION ======================= ======== ======= VSE/ESA Version 2.3 5690-VSE VSE Central Functions 5686-066 VSE/SP UNIQUE CODE 5686-066 6.3.0 VSE/POWER VSE/POWER MACROS VSE/VSAM VSE/VSAM MACROS VSE/AF OC/MC VSE/AF SVR & BAM & GDS VSE/AF MACROS VSE/AF GENERATION FEATURE VSE/AF MSHP VSE/AF INFO/ANA VSE/AF IOCP VSE/AF ICCF VSE/AF FASTCOPY REXX/VSE LIBRARY REXX/VSE KERNEL & INTERFACE VSE/OLTEP VSE/WORKDESK ACF/VTAM 5686-065 4.2.0 HLASM 5696-234 1.2.0 CICS/VSE 5686-026 2.3.0 GENERATION RCF EREP 5656-260 3.5.0 DITTO/ESA 5648-099 1.2.0 BTAM-ES 5746-RC5 1.1.0 ICKDSF 5747-DS2 1.16.0 LE/VSE Comp-RTE 5686-094 1.4.0 TCP/IP 5686-A04 1.3.0 VSE Extended Base 5686-066 6.3.0 LANRES/VSE LANRES WS NOVELL LANRES WS OS/2 VSE/DIST WS Feature VisualLift RTE 1.1.2 VisualLift WS WINDOWS VisualLift WS OS/2 VSE/CF/OSA 2.2.0 PREDEFINITIONS: --------------- Two ICCF Administrator ID's have been created in addition to the SYSA userid. They are SIE1 and P390. All three userids have system priv- ledges and their password is the same as the userid. It is recommended that you change these passwords immediately after initial installation. All three userids have ICCF library 10 as their primary library. This was the library used for system customization. You will find sample VTAM B-books (w/JCL) and some other helpful tools in this library: TMOUNT - JCL and source for the TMOUNT PHASE which has been cataloged in IJSYSRS.SYSLIB and is callable from a VSE batch job. Copy of source contained in ICCF library 59. IESZNEP - JCL and source for a NODE ERROR PROGRAM which has been cat- aloged in PRD2.CONFIG and is used to facilitate terminal recovery. Copy of source contained in ICCF library 59. SKIWSTF - IDCAMS job to define the VSAM file used for PC FILE TRANSFER. This file has been defined for you and the PC file transfer program has been implemented in the PPT, PCT and FCT for DBDCCICS. Copy of source contained in ICCF library 59. In addition there is a sample source program for PCOPY and associated Job control members in VSE/ESA ICCF Library 59 (PCOP*). This sample is provided on an "as is" basis. For details refer to the description in the program header. This sample program has not been tested on a R/390. "Pop-Up" message during IPL P/390 --------------------------------- If you receive the following "pop-up" message: +-------------------------------------------+ | P/390 Error | +-------------------------------------------+ | AWSDEV908E CU=SCSI348: RC=006E | | opening device driver, DD=SCSI3480 | +-------------------------------------------+ this means that you need to activate the SCSI3480.SYS device driver in CONFIG.SYS. This device entry is in the default DEVMAP: - 590 SCSI3480: 3480 tape on 4mm DAT cartridge If this entry is active but the device driver is not, then you get the error message. Since every PC Server S/390 has a 4mm DAT tape drive, you should edit CONFIG.SYS and make sure the "rem" characters are deleted from this line: rem DEVICE=d:\P390\SCSI3480.SYS 00,00 Reboot OS/2 and look for the SCSI3480 message during boot. SCSI Tapes during IPL R/390: --------------------------- When you do an IPL on the R/390, you have to have a tape (can be a scratch tape) mounted in your 4MM DAT drive (rmt0). After VSE/ESA startup you can do an OFFLINE for this tape (if not needed) to make it available for AIX. A ONLINE will give it back to VSE/ESA when required, but only when it was ready at IPL time. If not ready at IPL, the device manager SCSI34XX will not start. Messages during VSE IPL ----------------------- If you change the P/390's CPUID (on the Configurator F4 menu) from the default of 000001, or you install a P/390 daughter memory card, or you run VSE under VM, then VSE will detect a change in the processor serial number and display several messages that require replies on the VSE system console. They are all of the form: 0I37D . . . Overlap on unexpired file. Reply by typing: 0 delete for each message. Activating DEVMAP LAN devices ----------------------------- Certain devices are "excluded" in DEVMAP.VSE because they require a LAN adapter to be installed and configured in OS/2 LAPS (P/390) or to AIX (R/390). If you have a LAN adapter installed, then you may want to activate the device entries that are LAN-related. Excluded devices are shown on the P/390 Configurator F2 Update System Devices menu in DARK BLUE, with a device manager number of "0". The LAN devices contained in this DEVMAP are: 300 LAN3172: VTAM 3172 emulation - e.g. for DOS 3270 clients. To activate excluded devices, position the cursor on the first device and press ALT+F5 (P/390) or CTRL+F5 (R/390). See the documentation or online help (F1) for additional details. Local Time Offset from GMT -------------------------- Be sure to set the GMT offset in both the P/390 Configurator F4 Update System Environment menu and where appropriate in your VSE/ESA operating system. Stand-alone ICKDSF ------------------ We have provided a stand-alone version of ICKDSF version 16.0C on the CD-ROM in AWSTAPE format as ICKDSF.IPL. Instructions for IPLing ICKDSF.IPL on P/390: 1. Bring up the P/390 Configurator. Go to F2 Update System Devices menu. 2. Put d:\VSE\ICKDSF.IPL in the "FN/P" field for device 500. Press ENTER. (d: = your hard drive). 3. Save and exit the Configurator. 4. At an OS/2 prompt: D: CD D:\P390 IPL 500 CLEAR 5. To give the initial 3270 console interrupt, go to the first local CM/2 session, make it active, and then press the right-hand mouse button. Select "ATTN" from the pop-up menu. Instructions for IPLing ICKDSF.IPL on R/390: 1. Bring up the R/390 Configurator. Go to F2 Update System Devices menu. 2. Put /vse/vseesa/ickdsf.ipl in the "FN/P" field for device 500. Press ENTER. 3. Save and exit the Configurator. 4. At an AIX window: cd /usr/bin/r390 ipl 500 clear 5. To give the initial 3270 console interrupt, press ENTER at the first HCON session which gets initiated LANRES & VisualLift Diskette Images ----------------------------------- Diskette images of the LANRES Server Code and VisualLift Workstation Code have been included on this CD. The host code for these products has already been installed however, additional configuration tasks will need to be completed prior to their use. See the specific product documentation for customization details. The following diskette images can be found in the DISKIMGS sub-directory of this CD-ROM: LANRES VisualLift ------------ ------------ LANNOVD1.DSK - Novell disk 1 of 2 LFTWIND1.DSK - Windows disk 1 of 1 LANNOVD2.DSK - Novell disk 2 of 2 LFTOS2D1.DSK - OS/2 disk 1 of 3 LANOS2D1.DSK - OS/2 disk 1 of 2 LFTOS2D2.DSK - OS/2 disk 2 of 3 LANOS2D2.DSK - OS/2 disk 2 of 2 LFTOS2D3.DSK - OS/2 disk 3 of 3 To create a diskette from these files, open a DOS or OS/2 window and change to the DISKIMGS sub-directory of this CD-ROM. Place a formatted 1.44 diskette in your A: drive and enter the following command: LOADDSKF filename.DSK A: Where filename is one of the diskette images listed above. The complete diskette image contained in the filename will be written to the floppy in your A: drive.