*------------------------------------------------------------------------------*
* IBM P/390, P/370, and S/390 Integrated Server                   6/25/99 v3.1 /
* Program Installation Instructions                                       v2.5.1
*
*  Only OS/2 WARP version 3.0 and version 4.0, and                John A. Hupcey
*  OS/2 WARP Server version 4 are supported.                    PKVMWFB1(HUPCEY)
*                                                            hupcey@vnet.ibm.com
*                                                            USIB2TWT at IBMMAIL
*            (P/390 questions or problems?  Call Marty Ziskind at (800) 633-7437
*                                                              or (914) 435-5280)
*-> S/390 Integrated Server questions or problems? Call your IBM Business Partner
*------------------------------------------------------------------------------*
Read ALL the instructions before doing anything! (including calling Marty)

 Note: P/390 = P/390, P/390E, or P/370 adapter cards or the 7437 Workstation box
|              and processor card in the S/390 Integrated Server 3006 Model B01
               (P/390 is also referred to as the "S/390 Microprocessor Complex")

*------------------------------------------------------------------------------*
*     OVERVIEW OF INSTALLATION STEPS
*------------------------------------------------------------------------------*
  These are BASIC installation instructions - enough to get your P/390 up and
  running with 3270 sessions. For detailed instructions about configuring any
  S/390 devices, see the appropriate "DOC" file.  There is a file for each P/390
  device manager (i.e. control unit). The files have an OS/2 file extention of
  .DOC and are located in the d:\P390 subdirectory. You can also view them from
  the F2 Update System Devices menu of the Configurator.

  Required Steps:

  A. Basic Installation Instructions
     1. Install OS/2 WARP Server
     2. Install "Communications Manager/2 v 1.1 or 1.11 for OS/2 WARP"
     OR "eNetwork Personal Communications" v 4.1 or higher for OS/2 Warp
     AND OS/2 LAN support - either NTS/2 or MPTS.
     3. Install P/390 Program and Licensed Internal Code diskettes
     4. Update CONFIG.SYS with P/390 pathnames and device drivers
     5. Reboot OS/2 to pick up CONFIG.SYS changes
     6. Install S/390 Operating System
     7. Run P/390 Configurator
     8. IPL the P/390 Processor

  Additional Steps:

  B. Activate local P/390 3270 sessions (and host TFA)
  C. Install host TFA (VM only)
  D. Activate P/390 LAN 3270 sessions
  E. Increase LAN parameters
  F. Change IBM Token-Ring Network Adapter/A (Microchannel) parameters
  G. Configuring SNA LAN clients for LAN3172 attachment
| H. S/390 Parallel & ESCON Channel Adapter (AWSICE) Installation notes
  I. S/370 Channel Emulator/A (Microchannel) Installation notes
  J. GDDM Installation notes
  K. PKZIPed packages: POSPOWER, AWSDEV, AWSDMEX

  Information:

  L. Additional Notes
     - P/390 Web page
     - Getting P/390 Fixes
     - P/390 Configurator
     - Tape Devices
     - RAID DASD Synchronization
  M. What's new in version 2.5 (2.4.1)

*----------------------------------------------------------------------*
* A. Basic Installation Instructions (P/390 only)
*----------------------------------------------------------------------*
| Note: For the S/390 Integrated Server, a complete OS/2 C: drive system
|       image is supplied.  This image must be restored from the supplied
|       S/390 IS CD-ROM.  It includes OS/2, eNetwork 3270 sessions, Artic
|       960 RIC code and all P/390 programs preinstalled. See the file
|       README.CDI on that CD for installation instructions.

  1. Install OS/2 WARP

  We support OS/2 WARP Server version 4.

    - If you have a PC Server 500 or 520, there is a separately available
      fix for the PC Server Cirrus SVGA adapter that should be installed.
      It is available from ftp://P390.IBM.COM/p390/os2/cirrus.zip
      See section L, below.

    - We require the C: partition be formatted as FAT.

    - When the OS/2 "System Configuration" menu appears, ALWAYS choose a
      printer even if you do not have an actual PC printer attached.
      In "Select System Default Printer" make sure something is assigned
      to port LPT1, for instance, "IBM 4201 Proprinter (IBM42XX.DRV)".

    - Do NOT activate the "Object REXX" feature. P/390 programs require
      the normal REXX that comes with OS/2 WARP ("Classic REXX").

    - We recommend installing OS/2 WARP fixpack 35. This is the only
      OS/2 fixpack that we have officially tested with P/390.

    o If you install fixpack 35, please note the following:
      a. Fixpack 35 has back-level versions of the device drivers for the
         IBM ServeRaid adapter and the Adaptec SCSI adapter (built-in to
         most newer IBM PC Servers). Before installing fixpack 35 you
         should either back up these files or make sure you have recent
         device driver diskettes containing: IPSRAID.ADD & AIC7870.ADD.
      b. After finishing fixpack 35 installation, copy back or reinstall
         the ServeRaid and Adaptec device drivers BEFORE rebooting OS/2.
     >>> The fixpack 35 IPSRAID.ADD is bad and will hang your system!

  2. Install 3270 Emulator support for local P/390 sessions
     and OS/2 LAN support: NTS/2 or MPTS (included with OS/2 WARP TCP/IP).

  NOTE: Only two 3270 Emulators are supported for local P/390 sessions:
        - Communications Manager/2 1.1 or 1.11 for WARP.
        - "eNetwork Personal Communications" v 4.1 or higher for OS/2 Warp
        (referred to here as CM/2, and PC/3270, respectively).
|    --> NOTE: Only PC/3270 is currently supported by IBM.

     o If you are using CM/2:
        - you must install the CM/2 Coaxial (DFT) 3270 Emulation even
          if you do not have a "3270 Connection Adapter" installed.
          This support is used to supply 3270 sessions for the P/390.
     o If you are using PC/3270:
        - you must use the PC LAN - TCP/IP - Telnet3270 emulation.

    --> You MUST configure the 3270 sessions now, unless you are using the
        AWS3215 console for your system operator (VM/ESA 370 feature only).
        Follow the instructions in Section B, below, then return here.

     o If this is a first time install, you must install CM/2 first, and
       then the P/390 programs.

  3. Install P/390 Program and Licensed Internal Code (seven diskettes):

  IMPORTANT: If you are reinstalling over an old level, read these points:

       > Make sure that none of the P/390 Programs nor the OS/2
         Communications Manager is running. Failure to insure this
         may result in some of the new programs not being copied.

       > The INSTALL program will back up your current P/390 subdirectory.
         If you have modified any files (such as IPL.CMD), or added any
         user files (such as AWSUSER.CMD or ISITAP1.SYS), you must migrate
         your changes into the new versions of those files, or copy the
         user files back to d:\P390.
         To go back to the previous, saved level of P/390 Program, type:
              d:\P390\REGRESS
         DON'T rename the \P390 subdirectory yourself - the icons will
         change to follow the rename and not point to the new version.

       > If you have a S/370 Channel Emulator/A then you will get an error
         in backing up or copying CHAN370.EXE because it is started (via a
         RUN= statement) from CONFIG.SYS and cannot be replaced without
         removing this statement and rebooting.  IGNORE these messages!
         CHAN370.EXE does not need updating.

       > If you have an Artic960 adapter then you may receive an error while
         copying RICIO32.DLL because of the active C:\RIC\BIN\RICIO16.SYS
         statement in CONFIG.SYS. You can either check to see if RICIO32.DLL
         has changed or unconditionally reinstall this diskette.
         o To decide whether you have to reinstall the Artic960 programs:
            a. Type DIR C:\RIC\BIN\RIO32.DLL and note the date & time.
            b. Insert P/390 Diskette 6 in drive a: and type
                 PKUNZIP2 A:\ARTIC960.ZIP RICIO32.DLL -v
               also noting the date & time.
            c. If the date in the ZIP file is newer, continue with the
               reinstall steps immediately below. Otherwise, you're done.
         o To reinstall, follow these steps:
            a. Edit CONFIG.SYS and comment out (place the characters "REM" in
               front of the line):
                   REM DEVICE=C:\RIC\BIN\RICIO16.SYS
            b. Save the file, then shutdown and reboot OS/2
            c. Insert P/390 Diskette 6 in drive a: and type
                   A:\INSTICE
            d. When this finishes, remove the diskette,
               then shutdown and reboot OS/2
            e. Watch the messages during boot to make sure the
               ARTIC OS/2 Device Driver loads successfully.

  INSTALL steps:
     - Insert the "PC Server S/390 Program diskette 1"
       (or "P/390" or "P/370" Program diskette 1)
       in drive A, open an OS/2 command prompt, maximize it, and type:

         A:INSTALL d:
       You may specify 'd:', the drive on which you want to install the
       programs (the default is C:).  The subdirectory is always \P390.
       (Unless this is a P/370 install - then it is \P370).
       Do NOT make the current drive A: while installing, i.e. your OS/2
       prompt should say [C:\] or [D:\].
     - You will be prompted for P/390 Program diskettes 2 - 6.
        You can skip diskettes 4, 5, or 6 by typing "S" instead of inserting them.
         - diskette 4 contains AWSPBS Portmaster Bisync/SDLC drivers
           and the online P/390 message help file (P390MSG.INF).
|  Note: AWSPBS is not supported anymore.
         - diskette 5 contains WAN3172 SDLC gateway support
         - diskette 6 contains ARTIC960 & S/390 Parallel Channel support
     - You will be prompted for the seventh diskette labeled:
       "IBM PC Server S/390 Advanced Diagnostics and Option" diskette
    or "IBM P/390E Advanced Diagnostics and LIC" diskette
        (or P/370 Advanced Diagnostics and Option diskette).

  4. Update CONFIG.SYS with P/390 pathnames and device drivers

  IMPORTANT: If you are reinstalling over an old level, you MUST update
             your P/390 CONFIG.SYS statements with anything that is new
|            in CONFIG.AWS. Also, ensure that there are NO lines in
|            CONFIG.SYS after the P/390 group of statements!!

   o If you answered "Yes" to:
      "Do you want the P/390 statements added to CONFIG.SYS?"
     then you can skip this step, UNLESS you have other P/390 related
     adapter cards (e.g. channel adapters or communications adapters).
     See NOTE below about configuring OTHER adapters.

   o If you answered "No", then you MUST manually edit CONFIG.SYS now!
      - Look at the sample addenda file CONFIG.AWS which was on the
        P/390 Program diskette 1 (now in the d:\P390 subdirectory).
      - Add the path d:\P390 at the front of the three statements
        as shown in the sample.  Your statements may differ.
        Be sure to substitute the correct drive letter for d:\.
        IMPORTANT: The d:\P390 path MUST be at the FRONT of each line
        (right after the "=" sign). Do NOT put it at the END!!
        If you have an ARTIC960 with the S/390 Parallel Channel AIB installed,
        you must also add the C:\RIC\BIN path to all three statements.
      - Add all the lines after the boxed comments "P/370 & P/390"
        to the end of the CONFIG.SYS file.
    +---------------------------------------------------------------------+
    | WARNING: The P/390 block of statements MUST ALWAYS be at the end    |
    |          of CONFIG.SYS. Certain OS/2 configuration utilities (such  |
    |          as LAPS or MPTS) put their statements at the end. ALWAYS   |
    |          check CONFIG.SYS, and move these new statements above the  |
    |          P/390 ones. If you are having weird problems this is the   |
    |          one of the first things you should check. Then reboot OS/2.|
    |                                                                     |
|   |          Also, MPTS tends to fool with the order of the PATH, DPATH,|
|   |          and LIBPATH statements. Always make sure the P/390 subdirs |
|   |          (d:\P390;C:\RIC\BIN;) are at the FRONT of each line!!      |
    +---------------------------------------------------------------------+
   o If you have a 7437 Personal/370 box:
      - Make sure the "DEVICE=" entry for DD3702.SYS is active and the
        one for AWS370DD.SYS is commented out ("REM " in front).
   o If you have a P/370 or P/390 adapter:
      - Make sure the "DEVICE=" entry for AWS370DD.SYS is active and the
        one for DD3702.SYS is commented out ("REM " in front).
   o If you have additional P/390 supported adapters, make sure the appropriate
        "DEVICE=" entries are active (remove any "REM " from each line).

  NOTE: Configuring OTHER P/390 supported adapters
        ------------------------------------------
        Whether you answered 'Y' or 'N', you should always compare the
        file d:\P390\CONFIG.AWS to your CONFIG.SYS, and either add lines
        to or uncomment lines (remove 'REM') from CONFIG.SYS to make active
        any device drivers you need to support additional P/390 functions.
        These include the following:
          - S/370 Channel Emulator (Huron) adapter
          - S/390 Parallel Channel AIB on ARTIC960 adapter
          - Multiprotocol adapter ICA support
          - Wide Area Connector (WAC) adapter ICA support
          - Portmaster adapter bisync/SDLC support
          - Portmaster or WAC SDLC WAN3172 support
          - LAN adapter LCS3172 support
          - SCSI tape drive support

        >>> Read the comments in CONFIG.AWS for a current list <<<

   NOTE:  Make sure you save the CONFIG.SYS file.

  5. Reboot OS/2 to pick up CONFIG.SYS changes

      - Bring up the OS/2 desktop menu by clicking the right-hand (second) mouse
        button on the background of the desktop.
      - Select "Shut down" of OS/2. Wait for shut down complete message.
      - Press and hold down Ctrl + Alt + Del keys to reboot the PC.
   NOTE:  If you have not yet installed the P/390 Adapter card, then
          power off the PC and do so now.

  6. Install S/390 Operating System

  There are three ways to do this:
    a. Install a PC Server S/390 CD-ROM.
       This is either a "Preconfigured" or "Application Development" CD
       VM/ESA, MVS/ESA, OS/390 or VSE/ESA S/390 operating systems.
    b. Restore an existing S/390 Operating System from your mainframe.
    c. Install the full S/390 product tapes.

  For b. and c. you must have either SCSI or Channel attached tape drive.
  For a. do the following:
     - Insert the CD into your CD-ROM drive (x:),
       open an OS/2 command prompt, and type:
         x:\INSTALL
     - You will be prompted for the source and destination drives.
     - Read the README file located in the root directory of the CD.

  7. Run P/390 Configurator.

      - From P/390 Folder select "P/390 Configuration"
      - Press ENTER to get to the "FUNCTIONS" main menu.
          (If you open the settings of this icon and change parameter
           S=1 to S=2, then it will go directly to the "FUNCTIONS" menu).
      - Select "F2 Update System Devices"
          (This displays a listing of DEVMAP, the S/390 I/O device mapping).
      - Check to see that all DASD devices have been found.
          (If the "size" column is blank, then the file has not been found).
        o If not, then either change the filename on the right to reflect
          the actual drive and path where the file is located, or allocate
          the devices.  For VM, you may have to allocate the PAGING,
          SPOOLS or TDISKS using F11 Allocate key. For MVS (OS/390) and VSE
          you may need to allocate "Full Pack" volumes.  Fullpack DASD may be
          allocated by specifying nD in the "Size" column, where 'n' is the
          column number in the table AWSCFULL.PAK. See header of that file for
          more information.  For example, 2D for 3380 = 1770 cyls.
      - Create other device entries or modify the parameters for existing
        devices. Print and read the *.DOC files in d:\P390 to find out more
        information on each device manager.
      - While still on the "Update System Devices" menu, press F12 to
        go to the "Start Device Manager Parameter Input/Display".
        Check that the parameter for LAN3274 is "/PORT=7490".
        Then press F10 to return to the "Update System Devices" menu.

      - Press F10 to return to main menu, then F6 to save.

  8. IPL the P/390 Processor.

    o If you have a P/390 or P/370 adapter:
      - Make sure the adapter card is plugged into your PC and properly
        configured.  For Microchannel bus machines, you must run the PC
        Reference diskette to configure the adapter with the P/370 or
        P/390 adapter description files (@8FC4.ADF and C8FC4.ADF, or
        @8F9E, respectively).  For PCI bus machines (such as the PC Server
        330) plug the P/390 PCI adapter into slots 4 or 5.
    o If you have a 7437 Personal/370 box:
      - Make sure your 7437 is powered-on and attached to the PS/2 with
        the black interface cable.
    o For either processor:
      - Start CM/2 or PC/3270 local 3270 sessions.
      - From P/390 Folder select "IPL P/390 Processor"
      - A "P/390 Info" screen is opened.  This tells you the
        status of the P/390 processor and various code levels.
        You may minimize this screen, but do not close it.  Closing
        it (or pressing Ctrl-Break) kills the P/390 processor support.
    o For VM/ESA 370 feature only:
      - The P/390 IPLs and displays the operator messages, e.g. (for VM)

            CHANGE TOD CLOCK? (Y/N)
        in the 3215 or first local 3270 "System Operator" session.
      - The TOD CLOCK and WARM | CKPT | FORCE | COLD messages are
        automatically answered for the Operator if on a 3215 session
        unless you passed the parameter "NOAUTO" to IPL.CMD.
    o For VM/ESA only:
      - The system will IPL and autolog the OPERATOR onto the primary
        3270 display (usually device 200).
      - The OPERATOR's PROFILE will run and display the message:
          "P/390 VM Initialization Complete"

| **> If you have not yet activated local P/390 3270 sessions using the
|     instructions in Section B (below), you will get a Disabled Wait PSW.
|
|     If you are using PC/3270 TCP/IP support for the local P/390 sessions
|     and the TCP/IP loopback address (127.0.0.1) is either not configured
|     or not started, then you will receive this message:
|
|       AWSTCP006S Failure when BINDing Port 7490 to TCP/IP Socket (RC=10049)
|
|     Go to an OS/2 window and type "netstat -a". If you do not see:
|
|       Addr 127.0.0.1 Interface 9 mask 0xff000000 broadcast 127.0.0.1
|
|     or something like it, then the loopback is not configured. Go to
|     Section B2, "Additional 3270 Notes", below.  If NOTHING is typed
|     on your screen after entering netstat -a, then the TCP/IP SETUP.CMD
|     has failed to run due to an error. One possibility is if you are
|     running TCP/IP 4.1 and you have more LAN adapters configured in
|     MPTS than you actually have plugged into the PC. The solution is
|     go into the MPTS configuration program and delete out the extra
|     LAN adapter instances.

*----------------------------------------------------------------------*
* B. Activate local P/390 3270 sessions and host TFA (P/390 only)
*----------------------------------------------------------------------*
  Follow ONE set of instructions, below, for either:
   B1 - Communications Manager/2 1.1 or 1.11
   B2 - Personal Communications/3270 version 4.1 or higher for OS/2
| Note: Only PC/3270 is currently supported by IBM.


*-------------------------------------------*
*  B1. Communications Manager/2 1.1 or 1.11 *
*-------------------------------------------*
  The following instructions will set up the P/390 3270 DFT sessions, some of
  which will be allocated to "host" 3270 sessions IF you have a 3270 Connection
  adapter for coaxial attachment to your mainframe. If you use a Token Ring or
  other LAN attachment to your mainframe, you MUST still configure these DFT
  sessions for use by the P/390. You ALSO must configure LAN 3270 sessions to
  get to your host. A good time to configure host LAN sessions is between steps
  11 and 12.

  1. Double click on "Communications Manager Setup" icon from the CM/2 folder.
  2. Click on "Setup".
  3. Open either a new or existing configuration file.
  4. Select "Coaxial (DFT)" on the left and "3270 emulation" on the right.
      (the picture on the bottom should change to a terminal attached to a host)
  5. Click on "Configure".
  6. Type a "5" for the Number of terminal sessions and a "0" for the Number of
     printer sessions (unless you want 3287 emulation). Then click on "Advanced".
  7. Double click on "Required  3270 emulation" line.
  8. Double click on the "A" space under "Long Session/LU Names".
     - Change "Presentation space size" to 33 x 80 (3279 mod 3).
     - Turn off "Activate presentation space print".
     - Click on "Change" for "Alarm" option. Turn off "Screen update alarm".
  9. Click on "Save".
  10. Repeat steps 8 & 9 for the remaining four sessions (B, C, D, E).
  11. Double click on the upper left corner box (next to title "3270 Emulation")
       (This will bring you back to the Comm Mgr Profile List).

  For VM only (otherwise skip steps 12 - 14):
  o If you are going to activate TFA on these coaxial sessions,
    then complete steps 12 - 14.  Otherwise, skip to step 15.
   (If you are running VM on both the P/390 and the mainframe then activate TFA)

  o If you are going to activate TFA on LAN sessions to your mainframe,
    then complete steps 12 - 14 using the "Advanced" configuration menu for
    Workstation Connection Type = "Token Ring or other LAN types".
    (Note: LAN 3270 sessions over VTAM must change a parameter on each 3270
     Emulation session menu: "Data transfer buffer size override" = "Specific 4").

  12. Double click on "Optional  3270 SRPI" line.
      - Click on "File", then "New"
      - For Server name enter "AWSHOST" then press ENTER.
      - For SRPI server alias enter "AWSHOST1" then press ENTER.
      - Back on main screen, click once on "AWSHOST1" to get it highlighted.
      - Click on the little down arrow at the end of the line to get selection
        menu for "3270 Long Session Name". Click on "A" (or whatever the letter
        is for your host LAN session, e.g. "F").
      - Click ONCE on "AWSHOST1" to get it highlighted, again.
  13. Repeat step 12, with an alias of "AWSHOST2" and session "B" (if you have
      a second host session)
  14. Double click on the upper left corner box (next to title "Server Requester
      Programming..."  This will bring you back to the Comm Mgr Profile List).

  15. Click on "Close". Click on "Close" again.
      - Follow directions on the screen to exit or load more CM/2 diskettes.
      - Continue with step 16, below.
  16. You must tell the Communications Manager how many 3270 logical
      terminals (LTs) you want to allocate for Host coax sessions versus
      Local P/390 sessions.
      - From "P/390 Folder" click on "P/390 Configuration" icon.
      - From the "FUNCTIONS" screen press "F7 Update 3270 LT Sessions".
      - You get a selection menu.  In general, the first one or two LTs
        are allocated to the Host and the rest as Local.
         o If you do not have a 3270 Connection Adapter (DFT coax connection
           to a mainframe then do NOT allocate any host sessions on this menu!
        Don't worry about "LAN" type for now or the other fields to the right.
        (You can also get to this menu from any OS/2 session by typing AWSCMLT).

  17. Identify TFA devices (only necessary if you are running VM).
     - Select "F2 Update System Devices"
     - Scroll to device 450
     - Make sure "Mgr" code corresponds to MGR Code=AWSTFA
       (If not, delete the device and add it again with the correct mgr number).
     - In the "Filename/Parameters" field on the right for device 450,
       put "AWSHOST1".  Press ENTER.
     - If you have a second host session and wish to do TFA to that
       session, add a TFA device at address 451 with the parameter "AWSHOST2".
       Press ENTER.
     - Press F10 or ESC to return to "FUNCTIONS" menu
     - Press F6 to save the configuration.

  18. Shutdown and restart the system.
      - For VM, type "SHUTDOWN" on the Operator screen and press ENTER.
        Wait for the "Shutdown Complete" message.
      > For other operating systems, use normal shutdown procedures.
      - Select "Stop P/390 Processor" from P/390 Folder.
      - Bring up the OS/2 desktop menu by clicking the right-hand (second) mouse
        button on the background of the desktop.
      - Select "Shut down" of OS/2.
      - Press and hold down Ctrl + Alt + Del keys to reboot the PC.
      After OS/2 has come up again:
      - Start the Communications Manager
        After the Comm Mgr is fully up, make sure that there are
        5 (host + local) session windows (or icons) active.
        The local sessions have a MACH690 in them until
        you IPL and ENABLE the 3270 devices from the OPERATOR.
      - Select "IPL P/390 Processor" from P/390 Folder.
        o If you are running VM/ESA (370 feature):
          The OPERATOR will come up on 3215 device 009.
        o If you are running VM/ESA (ESA feature), MVS/ESA, or VSE/ESA:
          The System Console will come up on the first local 3270 device.
        VM only:
        The Operator's PROFILE EXEC will run which enables the other
        local 3270 sessions (the logon/logo screen will appear).


*-------------------------------------------*
*  B2. Personal Communications/3270 ver 4.1 *
*-------------------------------------------*
  The following instructions will set up the P/390 3270 "Telnet" sessions.
  that will be used as the local 3270 system and user consoles.

  First, you must install PC/3270 ver 4.1 or higher from its CD-ROM.

  Here are some quick tips for installing version 4.2, which is the
  current level at this time:
  1. Load eNetwork CD-ROM into drive x:
  2. Open an OS/2 window and type x:\INSTALL
  3. On the "eNetwork Personal Communications" screen, make sure
     "OS/2 Warp" is checked. Click on "Installation" icon.
  4. Under "Select Products" only select "Personal Communications".
     Click on "Begin".
  5. When asked, "Choose the way to install...", choose "Run P. C.
     from my workstation". Click on "OK".Click on "Next".
  6. When asked, "Select a package", choose "3270 Emulator". Click on "Next".
  7. "Specify Personal Communications drive and directory", take the
     default of C:\PCOMOS2.
  8. "Specify Access Feature drive", choose C: UNLESS you are installing
     over a previous install of CM/2 AND want to keep using both CM/2
     and PC/3270. On first time P/390 installs, just choose C:
  9. Click on "Next". "Select type of installation", choose "Full Installation"
     Click on "Next".
  10. Click on "Finish".


  After the PC/3270 is installed and OS/2 is rebooted then:
  11. Open the "Personal Communications" folder and
      double click on "Start/Configure Session" icon.
  12. A blank 3270 screen will open, overlayed by a "Welcome" message.
      Click on "OK" to clear the welcome message.
  13. The "Customize Communications" menu is displayed.
  14. Select "Interface" = "LAN"
      Select "Attachment" = "TCP/IP" (Telnet3270)
  15. Click on "Configure".
      This brings up the "Customize Communications - 3270 Host" menu.
  16. Set:
        - Screen Size = whatever you desire
        - Session Type = "Display"
        - Enable Host Graphics = "Yes"
  17. Click on "Configure Link"
      The "Telnet3270" menu is displayed.
  18. In "Host Name or IP Address" put "127.0.0.1"
      (This is the local TCP/IP Loopback address, which must be enabled
       in the TCP/IP configuration settings notebook. See Additional
       3270 Notes, below, for instructions on how to enable this).
  19. Click on "Advanced"
      A different "Telnet3270" menu is displayed.
  20. Change "Port Number" = "7490"
      Check the box "Auto-reconnect".
      Click on "OK"
  21. Back to previous menu. Click on "OK"
  22. Back to previous menu. Click on "OK"
  23. Back to top-level menu. Click on "OK"
      The blank 3270 screen is left.
  24. Click on "File" on the line below the title bar.
  25. Click on "Save".
      The "Save Workstation Profile as" menu appears.
      Change the file name to P390.WS
      Click on "OK"
  26. A pop-up message asks, "Do you want to add an icon for this
      session to the Desktop?"
      Click on "Yes".
      NOTE: It will create an icon in the "Personal Communications"
            folder, NOT on the OS/2 Desktop.
  27. Make a shadow of this new icon on the OS/2 desktop:
      - Point to new icon
      - Click once with RIGHT mouse button
      - Select "Create Shadow" from submenu
      - Click on "Desktop" selection, and then click on "Create".
  28. Use this new icon to start your P/390 Local 3270 console
      before IPL P/390 is done.

     If you want to start multiple P/390 local 3270 sessions at the
     same time (most of the P/390 preconfigured CDs have three local
     AWS3274 3278 sessions in DEVMAP) then use the "Multiple Sessions"
     icon in the "Personal Communications" folder to set them up.

 Additional 3270 Notes:
   - Any S/390 operating system running VTAM requires the
     following manual configuration step:
      a. Edit d:\PCOMOS2\PRIVATE\P390.WS
         (or whatever you called the .WS file created in step 15, above)
      b. Add the following two lines at the bottom, if not already there:
           [LT]
           IgnoreWCCStartPrint=y

    - To configure TCP/IP Loopback for local P/390 3270 Telnet sessions:
|      a. From an OS/2 command prompt, type: TCPCFG (or for 4.1, TCPCFG2)
       b. On the first menu, "Configure Network Interface Parameters"
          click on "loopback interface" in the left window.
       c. Check the "Enable interface" box on the right.
       d. Make sure the "IP address" field contains "127.0.0.1".
       e. Double click on the upper left corner to close the menu.
       f. Click on "Save".
       g. Run P/390 Configurator.
          - From P/390 Folder select "P/390 Configuration"
          - Press ENTER to get to the "FUNCTIONS" main menu.
          - Select "F2 Update System Devices"
          - Press F12 to go the "Start Device Manager Parameter
            Input/Display".
          - Check that the parameter for LAN3274 is  >/PORT=7490
            o If you previously had CM/2 installed, add this parameter
              to AWS3274:  >/NOCM
          - Press F10 to return to the "Update System Devices" menu.
          - Press F10 to return to main menu, then F6 to save.
       h. Reboot OS/2 for the changes to take effect
         (If you came here from Step 8, above, don't reboot yet!!)

    - If you are running VM on both the P/390 and the mainframe and wish
      to use Transparent File Access (TFA) then do the following:
       a. Click on "File" on the line below the 3270 session title bar.
       b. Click on "API Settings"
       c. Check the "SRPI" box. Click on "OK".
       d. Click on "Yes"
       e. Start the P/390 Configurator and get to the "Functions" main menu.
       f. Press F2 to display the "Update System Devices" menu
       g. Scroll down to device 450 (AWSTFA managed 3088).
       h. Change the "FN/P" field to say "AWSHOST"  (take off the 1)
       i. Do the same for any other AWSTFA devices (like 451).
       j. F10 to return to main menu. F6 to Exit and Save.

      PC/3270 TFA is restricted to one host session at a time.

*----------------------------------------------------------------------*
* C. Install Host TFA (for VM only)
*----------------------------------------------------------------------*
 1. You should have received the AWSHOST programs with the VM Starter System.
    o If you received these programs via RSCS, then you already have them
      on your host.
    o Otherwise the programs can be uploaded from either MAINT's 370 disk
      or the OS/2 d:\vm\ subdirectory.
      - Logon to host VM system (for instance, first LT session a:)
      - Go to an OS/2 prompt and type the following to upload these four
        files to your host userid: (substitute the short session ID for a:)
         send d:\vm\awshost.mod a:awshost pmodule a (lrecl 1024 recfm f
         send d:\vm\awshost.exc a:awshost exec a2 (ascii crlf
         send d:\vm\awshost.srp a:awshost srpi a2 (ascii crlf
         send d:\vm\awshost.map a:awshost map a2 (ascii crlf
      - Enter this commands on your host userid:
         copy awshost pmodule a = module a2 (oldd unpack

 2. Put "AWSHOST EXEC", "AWSHOST SRPI", and "AWSHOST MODULE" on the host,
    accessible to any host userids that will be running TFA.
    Check the date of DMSDFT MODULE (part of CMS). It should be 1989
    or newer in order to communicate with OS/2.

 3. From the first host session (e.g. A):
   - Logon to your VM userid.
   - You must IPL CMS VM/SP Release 5.08 or higher (or VM/ESA or VM/XA)  .
   - Type "AWSHOST".  You will get the CMSSERV fullscreen panel.
     o If there is an immediate error message displayed on the CMSSERV panel,
       then report it to your host system support personnel.  A SRPI connection
       was not established with the OS/2 workstation.

  4. On the P/390, go to the MAINT session and type "TFA START".
    - You can now link host minidisks with the "HLINK" command.
    - The syntax is the same as the CP LINK command, except you can HLINK
      to minidisks (or Temp Disks) that the host userid already has linked
      by specifying "*" for the userid and leaving the link mode blank, e.g.
         HLINK * 191 111
         ACCESS 111 C
         FILELIST * * C
      will allow you to read and write your host userid's 191 A-disk from
      the P/390 VM userid.

 5. When you are finished using TFA, issue a "TFA STOP" on the P/390.

 6. On the host, press PF3. All your minidisks are reaccessed as they
    were before running TFA.  They are released when the first "HLINK"
    command is detected, and reaccessed when either:
      o TFA STOP is issued
      o PF3 is pressed to exit CMSSERV
      o AWSHOST is NUCXDROPed

*------------------------------------------------------------------------------*
* D. Activate P/390 LAN 3270 sessions (optional)
*------------------------------------------------------------------------------*
  There are three ways to allow LAN-attached client PCs or workstations to access
  logon sessions on your P/390:

   Covered in LAN3274.DOC:
     - TCP/IP connection without running an S/390 TCP/IP on the P/390
   Covered in section G., below, and LAN3172.DOC:
     - S/390 SNA connection using VTAM on the P/390
   Covered in LCS3172.DOC:
     - S/390 TCP/IP connection using TCP/IP on the P/390
|  *** Note: You cannot use the same LAN adapter for both S/390 TC/IP and
|            OS/2 TCP/IP. If your system is an S/390 Integrated Server, then
|            note that the built-in Ethernet comes configured to OS/2 TCP/IP.
|            If you want to use it for LCS3172, then you must disable the
|            OS/2 TCP/IP support on that adapter (LAN0) from the TCPCFG2 menu.

 You MUST do steps E. and F. below on each client and the P/390 host.

*------------------------------------------------------------------------------*
* E. Increase LAN parameters
*------------------------------------------------------------------------------*
  Complete section E if you are using any of the P/390 LAN device managers:
  LAN3088, LAN3274, LAN3172, or LCS3172.

  1. Start Lan Adapter and Protocol Support (LAPS or MPTN) configuration
     - At an OS/2 prompt type
        c:\IBMCOM\LAPS
     OR
        c:\IBMCOM\MPTS
     - Click on "Configure".
     - Select "Configure LAN transports" and then click on "Continue".
       This displays your current LAN configuration and allow you to
       add or modify LAN adapters and their protocols.

  2. If your Network Adapter card is not listed in the "Current Configuration"
     box, then first add the appropriate adapter (e.g. IBM Token-Ring Network
     Adapter, IBM Token-Ring Busmaster Server Adapter, or LANStreamer MC 32)
     and then add the IBM IEEE 802.2 and OS/2 NETBIOS protocols to this adapter.

  3. Edit the driver parameters for the Token-Ring / IBM OS/2 NETBIOS.

  4. Increase the following entries to AT LEAST these numbers:
     - Maximum sessions         64
     - Maximum commands         95
     - Maximum names            30
     These numbers are just guidelines and may have to be bigger if you
     are running additional NETBIOS programs.

  5. Select "OK" to save the changes.

  6. Edit the driver parameters for the Token-Ring / IBM IEEE 802.2

  7. Increase the following entries to AT LEAST these numbers:
      - Maximum link stations    63
      - Maximum SAPs              7
      - Maximum number of users   7

  8. Select "OK" to save the changes.

  9. Exit LAPS
      - Click on "Exit".
      - Click on "Continue".
      - Follow the instructions on the screen to exit LAPS.

  10. Shutdown OS/2.

  11. Press Ctrl-Alt-Del to re-BOOT OS/2!! (but see step F, below first) .

*------------------------------------------------------------------------------*
* F. Change IBM Token-Ring Network Adapter/A (Microchannel ONLY) parameters
*------------------------------------------------------------------------------*
  Complete section F if you are using any of the P/390 LAN device managers:
  LAN3088, LAN3274, LAN3172, or LCS3172, AND you are using a Micro Channel
  Token-Ring Network Adapter/A.

  1. Boot the PC Reference diskette

  2. Select "Set Configuration" from the Main Menu

  3. Select "Change Configuration"

  4. Use PageDown and PageUp to search all Micro Channel slots for the
     IBM Token-Ring Network (16/4) Adapter/A.
  (If you do not have the 16/4 adapter, then skip steps 5 & 6)

  5. Move the highlighted bar down to "RAM Size and Address Range".

  6. Use F5 (Previous) and F6 (Next) to select a non-conflicting address range
     corresponding to a RAM size of "16 KB".
 *** This is also a good time to check that the "Adapter Data Rate" is properly
     set.  If you are using a Token-Ring 16/4 adapter, and all the other PCs
     on your ring are set to 16 Mbps, then you must also be set to 16 Mbps.
  >> Don't use "AUTO" speed setting. Always explicitly set the ring speed


  7. Move the highlighted bar down to "Interrupt Level".

  8. Use F5 (Previous) and F6 (Next) to set the interrupt level to "Interrupt 3"
     Do NOT use "Interrupt 2".
 *** Other PC adapters may need their parameters reset at this time ***

  9. Press F10 (Save) to save your configuration changes.

 10. Press ESC (or F3) to return to the Main Menu.

 11. Press ESC (or F3) to exit from the Main Menu. Follow the instruction
     displayed to RESTART your computer and boot OS/2.

 Note: Anytime you run "Auto-Configuration" you should redo this procedure
       to check the configuration values.

*------------------------------------------------------------------------------*
* G. Configuring SNA LAN clients for LAN3172 VTAM attachment (optional)
*------------------------------------------------------------------------------*
  Complete section G. if you want to allow client workstations on a LAN to
  access (via VTAM) 3270 SNA logon sessions on your P/390.

  These instructions are for the IBM PC/3270 product. If you are using another
  emulator product, read through the steps and then use the summary information
  that follows to customize your emulator parameters.

  1. On the P/390 PC (acting as host system):
     - From "P/390 Folder" start "P/390 Configuration".
     - From the "FUNCTIONS" screen press "F2 Update System Devices"
     - Use PGDN key to scroll through the list of devices. Make sure there is
       a 3088 device that is assigned to the MGR code of LAN3172. The P/390
       VM Starter System has an LAN3172 device at address 448.
     o If you do not find this device, then add one. Make sure you type in
       the correct MGR code for LAN3172 - do NOT take the default code.
     o If there is already an LAN3172 managed device, but it is in DARK BLUE,
       this signifies that it is "turned off". To reactivate it:
       - Position the cursor under the device address and press Alt-F5.
     - Press F10 to return to "Functions" screen.
     - Press F6 to END and SAVE ALL UPDATES.

  Here are the instructions for configuring a DOS client, as an example.
  The concepts and parameters are similar for non-DOS clients

 On each DOS client PC:
  1. Install the IBM LAN Support Program. You MUST install the 802.2 support.
     This will place two statements in your CONFIG.SYS similar to this:
          DEVICE=C:\LSP\DXMA0MOD.SYS
          DEVICE=C:\LSP\DXMC0MOD.SYS
  2. Install PC/3270. Here are abbreviated instruction steps:
     - Insert PC/3270 DOS diskette 1 and type A:INSTALL
     - Choose "Quick Installation"
     - For "Attachment type" choose "LAN via 802.2 protocol"
     - For "Number of host sessions" select how many you want (1 to 8).
     - On menu screen "LAN via 802.2 Protocol" fill in:

       >   Destination Address:  400074900001 <--- e.g. for P/390 SYS1

       Use the Network Adapter address of the P/390 you want to connect to
       via the LAN. You can set this via LAPS "Configure Workstation" menu,
       or you can use the "burned-in" adapter address that appears in
       c:\IBMCOM\LANTRAN.LOG. The Network Adapter address is also used by
       other systems to connect via VTAM to your P/390 (see the MACADDR
       parameter in the appropriate VTAMLST).

       >   Physical Unit ID: nnnnn

       This number uniquely identifies your PC workstation. It can be any five
       digit hexadecimal number that is unique across the entire LAN.

       >   Block ID: 05D

       The block ID is used to preface the Physical Unit ID to form an exchange
       identification. Use the default value of 05D.  If you change it, then
       it must match the IDBLK parameter in the SLAN VTAMLST.

       >  PIU Size: 0265

       PIU specifies the maximum number of receive data bytes. KEEP THE DEFAULT
       OF 0265 FOR NOW. We will change this later manually! The desired value
       that will match the P/390 Starter System VTAM cannot be entered on this
       menu. It is equal to the MAXDATA parameter in SLAN VTAMLST plus 36 bytes
       (1460 + 36 = 1496). The total MUST be under 1500.

     - Follow the directions on screen to save the PC/3270 configuration, and
       exit the install program. DO NOT REBOOT the PC yet!
     - Edit the file c:\PC3270\PC3270.BAT.
     - Locate the line that starts "PCSTKR LU= ..."
     - Change "RS=265" to "RS=1496" <-- MAXDATA + 36
     - Change "DS=04"  to "DS=08"   <-- SAPADDR value in SLAN VTAMLST
     - Save the file.
     - Reboot your PC and type $PC3270 to start the emulator
       (or c:\PC3270\PC3270 to skip the setup program each time).

 SUMMARY OF EMULATOR PARAMETERS:

   Using the P/390 VM Starter System, for node ID "SYS1", set up the
   following parameters in each client's 3270 emulator:

       Destination Address (TIC):  400074900001
       ID Number: 05Dnnnnn
       Receive Buffer Size: 1496

*------------------------------------------------------------------------------*
* H. S/390 Parallel & ESCON Channel Adapter (AWSICE) Installation notes  )
*------------------------------------------------------------------------------*

| AWSICE supports the Artic960 PCI adapter with the S/390 Parallel or
| ESCON Channel AIB (daughter board) that replaces the S/370 Channel
  Emulator/A (Huron) in PCI-based PCs.  It provides a hardware channel
| for "bus and tag" or ESCON  attached or control units.

  The P/390 INSTALL.CMD will install the support in the d:/P390 subdirectory
  (programs with the characters "ICE" in them); it will also create a
  C:\RIC\BIN for the Artic960 OS/2 device driver programs.

  1. If you have installed the S/390 channel card, you must edit CONFIG.SYS
     and make sure the following lines for the Artic960 device drivers are
     active.  For new P/390 installs they will be in the block of P/390
     statements at the bottom, but will be commented out.  Remove the "rem"
     from the front of each line, if present:

        DEVICE=C:\RIC\BIN\RICIO16.SYS
        SET RICPATH=C:\RIC

  2. Read the d:\P390\AWSICE.DOC file for instructions on how to configure
     and use channel attached devices.

*------------------------------------------------------------------------------*
* I. S/370 Channel Emulator/A (Microchannel ONLY) Installation notes (opt.)    *
*------------------------------------------------------------------------------*
  This section only applies to the Micro Channel adapter.

Before installing the S/370 Channel Emulator/A (Huron card) in your PC:

  1. Boot the PC Reference diskette

  2. Select "Copy an option diskette" from the Main Menu

  3. When you are prompted to insert a diskette with the "new" files,
     insert the "P/390 Program diskette 1" into the drive.
     - This will copy the newer versions of the S/370 Channel Emulator/A
       Adapter Description Files (@E014.ADF and CE014.ADF) to your PC
       Reference diskette.
     Note: NEVER use the diskettes that come with the Channel Emulator card!

  4. Power down the PC and install the S/370 Channel Emulator/A card.

  5. Power on the PC, and get a 165 error, "Configuration has changed,
     Auto-Configure (Y | N)?".  ALWAYS answer "Y".

   o If you have already configured the S/370 Channel Emulator/A in this PC,
     with the wrong ADF files, you will have to do this in order to properly
     configure the adapter card with the new ADF files:
     - Power down the PC and REMOVE the card.
     - Power on the PC, and get a 165 error, "Configuration has changed,
       Auto-Configure (Y | N)?"
     - Answer "Y".
     - Power down the PC and INSTALL the card.
     - Power on the PC, and get a 165 error, "Configuration has changed,
       Auto-Configure (Y | N)?
     - Answer "Y".

 6. After running PC autoconfiguration, ALWAYS follow the procedure given
    above in section F. to check the parameters on other PC adapters.
    Be sure to check the Channel Emulator's configuration to ensure there
    are no conflicts (conflicts are flagged with a '*' after the choice).
    o If there is an '*', then you must autoconfigure the PC
      as detailed in step 5.
    The Channel Emulator's "I/O Buffer Location" MUST say "PROGRAMMED 64K > 1M".
    o If it doesn't, then you have the wrong ADF files. Go back to step 1.

 7. Also make sure you have:
     - copied the necessary lines from CONFIG.AWS into your CONFIG.SYS file
     - removed the "rem" from in front of the "DEVICE=" and "RUN=" lines
       for "CHAN370"
     - updated all the "C:" drive letters to correspond to the drive on
       which you have installed the P390 subdirectory
     - re-booted the PC after making changes to CONFIG.SYS.
     - READ the CHAN370.DOC file!! (located in the d:\P390 subdirectory).

*------------------------------------------------------------------------------*
* J. GDDM OS/2 LINK Installation Notes (optional)
*------------------------------------------------------------------------------*
  If you attempt to run a GDDM application and get the message:
              CANNOT DISPLAY GRAPHICS
  then you must perform the following steps.

  NOTE: There are three sets of instructions below. Follow:
    J1 - For Communications Manager/2 1.1
    J2 - For Communications Manager/2 1.11 (WARP)
    J3 - For Personal Communications/3270 4.1 or above

 *--------------------------------------------*
 * J1. Communications Manager/2 1.1           *
 *--------------------------------------------*
  1. Before running HGINST, you MUST have a OS/2 printer defined.

  2. Log on to the desired host or local 3270 session.

  3. Get access to the GDDM programs on that 3270 session.
     - For host sessions, contact your system support personnel. You
       may have to link a disk and issue a CMS command such as:
          GLOBAL TXTLIB ADMPLIB ADMGLIB
     - For local P/390 sessions, it is assumed that you have installed the
       GDDM program product minidisk(s) on the PC disks. Link and access
       these minidisks and issue the GLOBAL TXTLIB command, as above.

  4. From an OS/2 window issue the OS/2 command:

          HGINST
     and follow the directions. You should see files being copied,
     and a successful completion message.

 Note: If HGINST fails for any reason (e.g. the corresponding host VM program
       is not found, or the GDDM programs are not found) then you must:
       - Make sure you have solved the problem.
       - Stop the Communication Manager 3270 session.
       - Restart the Communications Manager 3270 session.
       - Close the OS/2 window.
       - Open a new OS/2 window.
       - Issue "HGINST" again.

 *--------------------------------------------*
 * J2. Communications Manager/2 1.11 (WARP)   *
 *--------------------------------------------*
  1. Double click on "Communications Manager Setup" icon from the CM/2 folder.

  2. On the "Communications Manager Setup" menu, click on "Options" at the top.
     This will display a pull-down menu of several selections.

  3. Choose "Install additional functions" from this menu by clicking once on it.

  4. Find "Host Graphics (GDDM-OS/2 Link)" in the Function List. If it is not
     installed, click on the selection to highlight it, them click on "OK".

  5. Follow the instructions to install the necessary programs from the CM/2
     1.11 CD-ROM or diskettes (You must use the same media that you originally
     used to install CM/2, at the same OS/2 drive letter!)

 *---------------------------------------------------*
 * J3 - For Personal Communications/3270 4.1 or above
 *---------------------------------------------------*
  - Make sure the item "Enable Host Graphics" says "Yes" on the
    "Customize Communications - 3270 Host" menu. This is the same
    PC/3270 menu where you set the screen size.

*------------------------------------------------------------------------------*
* K. PKZIPed packages: POSPOWER, AWSDEV, AWSDMEX (optional)
*------------------------------------------------------------------------------*
  Complete section K. if you wish to use any of these additional features:

     1. POSPOWER - Dynamic POS for Async/SDLC V.32 Modem/A or 7855 and
                   IBM PS/2 9595 Pentium auto on/off power features

     2. AWSDMEX  - Ring 3 Device Manager example code

     3. AWSDEV   - Sample Ring 0 P/390 Device driver and supporting control unit

  For each of the above, there is a name.PAC and name.ZIP in \P390 subdirectory.
  The name.PAC file lists and describes the programs that are packed together in
  the name.ZIP file. If you wish to unpack any of these into separate files then
  follow these instructions.

  - From an OS/2 prompt, enter:
       CD \P390
       PKUNZIP2 name.ZIP

  - Repeat for each package desired, substituting POSPOWER, AWSDMEX, or AWSDEV
    for "name".

  - Other options are available. Type PKUNZIP2 without any parameters for a list.

*------------------------------------------------------------------------------*
* L. Additional Notes
*------------------------------------------------------------------------------*

  P/390 Web Page
  --------------
  Additional Hints and Tips (FAQ) are available at:
     ftp://p390.ibm.com/doc/index.htm
  or
     http://www.s390.ibm.com/products/p390/p390hp.html

  Getting P/390 Fixes
  -------------------
  P/390 fixes are distributed in two forms:

   1) "Temporary fixes" are distributed to fix individual or related
      problems before a fixpack becomes available. Generally, you would
      apply these fixes only if you were experiencing that problem.

   2) "Fixpacks" are collections of fixes that have been tested together,
      and should generally be applied to all systems.

  P/390 fixpacks are available on each of the following on-line sites:

  Via WorldWideWeb:    http://www.pcco.ibm.com/files.html
                           Select OS/2 Device Drivers
                           and search for P390
                    OR
                       ftp://P390.IBM.COM/readme.htm
                           The file readme.htm identifies all available fixes.

| Via the IBM Intranet:
|                      ftp://S390IS.POK.IBM.COM/readme.htm
|                          The file readme.htm identifies all available fixes.

  Via Anonymous FTP:   ftp.pc.ibm.com
                           login as user anonymous, password=your_id.
                           cd /pub/pccbbs/os2_drivers
                           binary
                           get p390nnnn.zip
                    OR
                       P390.IBM.COM
                           The file readme.txt identifies all available fixes.

  Via Modem:           Call the OS/2 BBS at 919-517-0001. Set Modem to N 8 1.
                            Log in with your name.
                            Go to the File section.
                            Select the OS/2 Device Driver area.
                            Search for P390

  Temporary fixes are made available on the following FTP site. This is
  also where you should upload error traces if you are working with IBM
  service personnel.

| Customer Internet access:     P390.IBM.COM
| IBM Internal Intranet access: S390IS.POK.IBM.COM

       Login as user anonymous, password=your_email_address
       The file readme.txt or readme.htm identifies all available fixes.

  Netscape users should login this way:
     ftp://anonymous:your_e-mail_address@P390.IBM.COM
     Click on README.HTM

  If you cannot access these on-line sites, call the 800 number at the top of
  this file.


  P/390 Configurator
  ------------------
  There is a limit of 256 devices in DEVMAP. You can see all the Devmap
  devices on the "F2 Update System Devices" menu.

  - VM users who are approaching the 256 device limit may want to package
    multiple minidisks in a single OS/2 file, just like it would be on a
    mainframe.  A good candidate for this would be minidisks that are
    logically grouped together, such as the pieces of a program product.
    Be aware that:
     a) The P/390 Configurator F3 menus have minimal support for multiple-
        minidisk volumes. You must use the F2 menu to allocate the overall
        OS/2 file, then exit the Configurator and, using an OS/2 editor,
        edit the USER.DIR file and manually add the MDISK cards for the
        each minidisk. You MUST be knowledgeable about VM user directories
        to perform this procedure!
     b) It will be harder to increase the size of any individual minidisk
        within the volume.

  Tape Devices
  ------------
  1. The P/390 I/O subsystem does not support the READ BACKWARDS CCW unless
     the SKIP bit is on.  This may affect certain tape utility programs.
     It applies to all tapes, whether emulated, SCSI-attached, or Bus &
     Tag Channel-attached via the S/370 Channel Emulator/A adapter.
     This restriction does NOT apply to the S/390 Parallel Channel Adapter.

  2. When you are purchasing a SCSI-attached 3420 or 3480 tape drive,
     make sure the drive has been tested by the dealer with the P/390
     SCSI tape device drivers. There are different levels of hardware and
     firmware, usually found in older or refurbished drives, that will
     not operate correctly or at all with the P/390.

  3. SCSI-attached 3420 and 3480 tapes drives (including the 4mm DAT cartridge)
     are only supported when attached to these cards:

     PC Server 500 or 520
     --------------------
         Name in Reference Diskette Configuration  Adapter ID  Ordering P/N
         ----------------------------------------  ---------- -------------
         IBM PS/2 SCSI-2 Fast/Wide Adapter/A             8EFC   70G8498

     PC Server 520
     -------------
         Only the built-in (system board) SCSI port is supported.

     PC Server 330:
     -------------
         Product Name                              Feature Code  P/N
         ----------------------------------------- ------------ ---------
         IBM PC ServeRAID Adapter                   1930         70G8489
         IBM PC Server Ultra Wide SCSI PCI Adapter  8260         76H5407
         IBM PC ServeRAID II Ultra SCSI Adapter                  76H3584
         Adaptec Differential SCSI Adapter (IBM 3490-F01 only)   AHA2944UW
|        (See Warning, below)

|    S/390 Integrated Server
|    -----------------------
|        Product Name                                            FRU P/N
|        ------------------------------------------------------ ---------
|        Adaptec Differential SCSI Adapter (IBM 3490-F01 only)   31L7462

    Warning: Be careful in systems having both differential and regular
             (single-ended) SCSI. The interfaces are electrically different,
             so that attaching the wrong device to the wrong adapter may
             damage the device and/or the SCSI adapter.
|            Do not confuse this older "high voltage" differential interface
|            with the newer "Low Voltage Differential" (LVD) one.


| 4. Using the IBM 3490-F01 tape drive with SCSI3480 or AWS3480
|
|    Rule Number 1.
|    -------------
|    Both SCSI3480 and AWS3480 will respond strictly as a 3480
|    device -- either without IDRC (3480) or with IDRC (3490).
|
|    The 3490-F01 tape unit supports IDRC which MUST be turned on
|    by the S/390 operating system:
|      o For OS/390, define a 3480 device with the COMPACT option
|      o For VM/ESA, define a 3480 device and use the "XF" parameter
|        on the TAPE and VMFPLC2 commands, and the "MODE XF" option
|        on the DDR command. Do NOT specify both MODE XF (hardware
|        compression and COMPACT (software compression) at the same time!
|
|    Note that in this configuration, the 3490-F01 will ONLY write
|    in 18-track mode.  It will read both 18-track AND 36-track tapes
|    even though it is only defined as an 18-track device to S/390.
|    The tape drive automatically does the format adjustment transparent
|    to the software.
|
|    Rule Number 2.
|    -------------
|    If you want to use the 3490-F01 to WRITE in 36-track mode, you
|    MUST still define the device as set forth in Rule Number 1 AND
|    use the "/TRK=36" parameter in the P/390 Configurator definition
|    for the device.
|
|    Note that with this combination, S/390 still thinks it is an
|    18-track device with IDRC. HOWEVER, IT WILL WRITE IN 36-TRACK
|    FORMAT.  It will continue to automatically adjust to read both
|    18-track and 36-track formats.
|
|    Rule Number 3.
|    -------------
|    For proper support of multi-tape operations, the following 3490-F01
|    option settings are REQUIRED:
|
|    L490E Option Settings
|    ---------------------
|
|    Option  Value                   Comments
|    ______  _____________________   _________________________________
|    31      Disp WRT Format
|    44      Sync 2 FMK              Write synchronization
|    46      32                      Number of read retries
|    47      16                      Number of write retries
|    48    + Host/Panel Unlkd        Host and front panel active
|    49      Variable                Blocksize
|    50      ID 5                    SCSI ID (may vary)
|    51      OPT 51 Yes              Interface parity enabled
|    52      Dflt Dev (80h)          Device Type (Overland 3480/3490E)
|    53    * OPT 53 No               Ready signaled during rewind
|    54      OPT 54 No               Scnchronous Data Transfer
|    55      Std                     EOT Mode Reporting
|    57      OPT 57 No               Enable 2's complement residue
|    59      Default S/N             -- not used --
|    60    * Overland                Vendor ID
|    61    * L490E                   Product ID
| |  62    + 3490E                   Format selection (ISITAPE only)
| |  62    # 3480                    Format selection (SCSI3480 & AWS3480)
|    63      SCSI-2                  Interface Option
|    65      18trk Wrt Unlkd         18-track write enabled
|    66    * Status on Unload        Status signalled on Unload
|    67      Retry MTW errs          -- not used --
|    68      Sync 5Mb/Sec            Default SCSI Transfer Rate
| |  69    + 3490E COMP              Power-up default (ISITAPE only)
| |  69    # 3480                    Power-up default (SCSI3480 & AWS3480)
|    72    * BUSY                    SCSI response during Rewind
|    74      Read to EOD
|    75      Auto Clean Off
|    76      Pack After RTYS
|    77      18 trk Write Off
|    78      NO Medium Type
|    79    * Standard Mode           ACL sequential stacker mode
|    88      0
|
|     * = Note:  REQUIRED for proper operation of the
|                auto-cartridge loader with multi-volume
|                tape datasets.
|
|     + = Note:  REQUIRED for ISITAPE (v2.04 or later) software
|                select of 18/36-track write by unit address in
|                conjunction with 3480/3490 device type settings
|                in the P/390 Configurator.
|
|     # = Note:  SCSI3480/AWS3480.SYS on the other hand MUST always
|                specify 3480 here and in DEVMAP. To turn on 3490E
|                36-track format, use the "/TRK=36" parameter on each
|                device address in DEVMAP with the P/390 Configurator.
|
|
|         Note:  Option 72 is only available with firmware level
|                FLASH 15 or later.
|


  5. Make sure that the SCSI bus is properly terminated. For instance,
     a wide SCSI adapter requires WIDE termination, even if the tape
     drive you are attaching is narrow SCSI.

     A cable is available from Interprocess Systems, Inc., which provides
     termination for narrow external devices attached to wide SCSI.
     For ISI's phone number see the bottom of file d:\P390\XTAPELO.DOC.


  RAID DASD Synchronization
  -------------------------
| IBM recommends that you synchronize your RAID DASD once a week, if your adapter
| doesn't automatically perform background data scrubbing.  This is required
  to find bad sectors on your SCSI disks while you still have RAID parity.

  There are three ways to run synchronize:
    1. From the RAID Administration icon
    2. Boot the RAID Configuration diskette
    3. ServeRAID II at newer firmware levels performs background scrubbing.

*------------------------------------------------------------------------------*
* M. What's new in version 3.1 (2.5.1), 3.0.1, 2.5 (2.4.1) & 2.4 (2.3.3)
*------------------------------------------------------------------------------*

 New supported adapters (3.0.1):
 ------------------------------
  - P/390E Adapter
  - Multiport Model 2 ISA adapter (replaces Portmaster Microchannel adapter)
  - Artic960 with S/390 Parallel Channel AIB (see AWSICE.DOC)
    or S/390 ESCON Channel AIB (S/390 Integrated Server only).
  - SSA DASD adapter (S/390 Integrated Server only).
  - RS-422 OCA monitor (S/390 Integrated Server only).

  New in 3.1 (2.5.1)
  ------------------
  - Fixes for Integrated Server 3.0.1 CD-ROM install
  - See "New in 3.0.1" if you are a P/390 2.5 diskette install

  New in 3.0.1:
  ------------------
  - S/390 Integrated Server support
  - TN3270E support
  - 4 digit device addresses
  - Long filename support
  - ESCON channel for S/390 IS only
  - Wrap test for Parallel channel
  - Capture traces if a device manager abends
  - AWSSNAP / AWSSRAM2 / SENDLOG for sending traces to IBM
  - Improved Trace spooling options
  - PCI and BIOS query tools
  - Customer configuration save/restore
  - LCS3172: Supports IP Multicast
  - OS/2 LanServer, HPFS386, and Netfinity are NOT supported

  New in 2.5 (2.4.1):
  ------------------
  - P/390E Adapter support

  - S/390 extended storage using PC memory
    (for both P/390E & P/390 PCI adapters only: see AWS370DD.DOC)

  - P/390 local 3270 sessions can now be TCP/IP connected using eNetwork
    Personal Communications (PC/3270).

  - PLO, BSA, and immediate-and-relative Ops added to ESA/390 LIC

  - Performance improvements for S/390 Parallel Channel Adapter (AWSICE)

  - Trace spooling (AWSTRCSP) is now autostarted by IPL.CMD if I/O trace
    is activated in CHAN.TRC. It is stopped by AWSEND.CMD.

  - WAN3172 supported for VM/ESA and VSE/ESA; Multiport Model 2 support

  - OS/2 Warp Server Advanced v4 Fixpack 35 supported (and recommended)


  New in 2.4 (2.3.3):
  ------------------
  - P/390 PCI adapter support for PC Server 325/330 (AWS370DD.SYS)
    For more information see the file d:\P390\AWS370DD.DOC.

  - Online error message help (P390MSG.INF)

  - Device manager parameter submenu (F12) beneath F2 menu (AWSCNF.EXE)

  - AWSICA support of ISA WAC adapter for SDLC or BSC

  - AWSFBA multithreading support
    For more information see the file d:\P390\AWSFBA.DOC.

  - System Activity Display (AWSSAD) now has yellow SIO I/O activity bar
    For more information see the file d:\P390\AWSSAD.DOC.

  - XTAPELO - "Load Only" version of XTAPE  utility for simple backup/restore
    of files (e.g. P/390 DASD volumes) from OS/2 (e.g. to 4mm DAT tape).
    For more information see the file d:\P390\XTAPELO.DOC.

  - Year 2000 testing parameters for IPL.CMD /NOCLKGET, SET, CLR

  - New calls to user exit AWSUSER.CMD from IPL P/390 and END P/390.
  **** Note: If you have already written a user exit it must be updated *****
    For more information see the file d:\P390\IPL.CMD, comments at top.


 Problems fixed in version 3.1 (2.5.1)
 ---------------------------------------

  ID      Component    Description
  ------  ---------    ----------------------------------------------
  N4558   LAN3274      Illegally reused queue element (IFCC/Trap 4)
  N3310   AWS2821      Emulated printer couldn't handle long HPFS names
  N4472   AWSCHAN/CKD  AWSCHN017W Invalid CCW count
  N6698   LCS3172      Trap D on WATCH$ when tracing 3172
  N4834   AIC7870      Set device timeout feature
  N5636   AIC7870      Tape Unit Ready times out
  N5633   AIC7870      Shared hardware IRQs - hang of external SCSI tape
  N5633   ISSAPCI/DSK  Shared hardware IRQs
  M1722   AIC7870      Shared hardware IRQs - slow tape performance
  N5894   AWSCART/STAT Overflow of Cart Mgr table
  N3794   AWSINTF      Overflow Int queue (PCI) abend
  N3129   ICECAP       Establish logical path, invalid addr in CCW
  N3950   ICEMAP       Escon LPAR/Logical CU number
  N4996   AWSICE       Escon LPAR/Logical CU number
  N3862   AWSICE       Early (ESCON) printer interrupt, CC3 fix
          AWSATTN      Pink hang (critsec->semaphore)
          ICEDEV       Unsolicited status, deferred CC2, ports 14, 34
  PMR3036 AWSCKD       3330 fixes; Sync_Sort fix; Record not found on locate record
  N3522   AWSADPUP     Fault is displayed if temporary communication timeouts occur.
          OP0008.HXX   Voltage level-5 after Turn On delay I and V sensor unmasking for 0.7-S
          XTAPELO      SSA performance for LOAD improved


 Problems fixed in version 3.0.1
 -------------------------------

  ID        Component   Description
  --------  ----------  -------------------------------------------------------
  N2237     ICECAP      Fixes AWSICE004T error code 442 when AWSCFG run
  N3177     ICEINIT     Set ESCON director sequence number and tag fields
  N2973     ICEDEV      Support for 9032-5 switch, port addrs<C0, >1024 devices
  H164101   AWSCKD      Fixes Record Not Found condition when VTOC is on last cylinder
  H164102   AWSICE      Fixes line drop problems with 3745 CUs.
  H164004   AWSLANIP    Fixes third party client connection problems
  H164005   AWSLANIP    Resolves TN3270 problems with extended attributes
  H163864   AWSCHAN     IFI005 Abend in VM/ESA V1R2.2 and V2R1
            AWSINTF     IFI005 Abend in VM/ESA V1r2.2 and V2R1
  H164438   AWS3900     Microcode Fix to OC4 Abend
  000059PA  AWS2821     Fixes 3211 FCB Print Problem
  000093PA  AWS2540     Fixes 1Q35A UNEXPECTED EOF when reader is empty (VSE)
  000098PA  SCSI34X0    OS/390 "READ BLOCK ID" Return Count


 Problems fixed in version 2.5 (2.4.1)
 -------------------------------------

    ID     Component   Description
 --------  ----------  ---------------------------------------------------------
 000056PA  LAN3274     SYS317x abends in AWSLANIP.DLL or AWS3274.EXE
 000001PA  AWS2821     Documentation fix; new Lines/page feature in control file
 000042PA  AWS2821     Extra blank lines at top of each page; FCB fixes
 000067PA  AWSDEV      Documentation fix - tape DD error message explanations
 000049PA  SCSI34x0    Reinstate default 9/18 track table entries; OS/2 memory problem
 000016PF  AWSCKD      EOV seeking, 3330 seek fix, priority fix
 000043PA  AWS370DD    Added message AWSDDX008E to online message file
 000065PA  AWSINTF     Fixed TOD clock setting bugs
 000020PA  AWSCHAN     SYS317x abends in AWSCHAN.EXE or AWSICE.EXE


 Problems fixed in version 2.4 (2.3.3)
 -------------------------------------

    ID     Component   Description
  -------  ----------  ---------------------------------------------------------
  PJ23579  AWS2821     Sets printer default to '0F' regard-less of options set
                       in control file.
  PJ23727  AWSCHAN     Fixes IOS error messages during tape write operation.
  PJ23728  AWSINTF     GMT offset problem has been fixed.
  PJ23733  AWSCHAN     Same as PJ23727.
  PJ23851  AWS2821     Fixes SYS3175 access violation when end of file character
                       did not exist in printer control file.
  PJ23883  CHAN370     Fixes IFCCs when sharing tape drives with other mainframe
                       systems.
  PJ24013  CHAN370     Fixes missing channel device end when aligning or
                       installing paper on channel attached printer.
  PJ24032  AWS2703     Fixes SYS3175 with AWS2703.
  PJ24036  AWSTAPE     Tape positioning error when using AWSTAPE.
  PJ24059  AWSNTCA     Abend in AWSNTCA when P390 shuts down.
  PJ24237  AWSIPL      System Load Parm did not reflect change.
  PJ24307  AWSCHAN     Resolves pink hang and OS/2 hang by modifying AWSCHAN to
                       use a semaphore instead of a critical section.
  PJ24353  AWSCKD      AWSCKD wasn't correctly translating CCWs when running
                       DFDSS jobs on an MVS guest under VM.
  PJ24400  AWSLANIP    AWSLANIP.DLL abend.
  PJ24401  AWSCNF      Problem when using 'V' in the password resulted in PCOPY
                       thinking the file was empty.
  PJ24413  AWSSAD      Resolved SYS3171 when starting AWSSAD on Voicetype was
                       installed.
  PJ24564  (info)      Identifies correct IBM2SCSI.ADD and OS2SCSI.DMD file with
                       SCSI34X0.SYS file.
  PJ24794  AWSCHAN     Resolves incorrect CCW being displayed if system is VSE
                       in 370 mode.
  PJ24798  AWSINTF     Resolves problem with loss of AWSPBS sessions when PC
                       Server 500 was under heavy load.
  PJ24822  AWSCKD      Resolves problem with permanenet UNIT CHECK when
                       formatting a minidisk on 370 version of VM.



 Problems fixed in version 2.3:
 -----------------------------

    ID     Component   Description
  -------  ----------  ---------------------------------------------------------
  PJ22867  AWSICA      MSGIST446I and sense 8011 with AWSICA and VSE/ESA
  PJ23187  AWSPBS      BiSync problems with new portmaster cards.
  PJ23300  AWSICA      Line drop in secondary mode SDLC AWSICA after soft error
  PJ23233  AWSCKD      Info APAR only.  Instructions to remedy AWSCKD002.
  PJ23344  AWS2821     When using a printer config file.  Receiving IOS
                       MSGIOS551I NO PHYSICAL PATH AVAILABLE (P390 only).
  PJ23369  AWSCHAN     Getting tape error MSG IEC210I attempting LCT to
                       DFP near EOV on 3480 drives.
  PJ23422  AWSCHAN     SYS3173 error from AWSCHAN.EXE (INT3 in LIMITCHK)
  PJ23446  AWSDM       VSE on PC Server 500 system 390 experiences system
                       hangs an unpredictable outcomes.
  PJ23469  AWSICA      Trap 000D in AWSMPADD (MPADD$) at offset 13B9



 Problems fixed in version 2.2:
 -----------------------------

    ID     Component   Description
  -------  ----------  --------------------------------------------------------
  PJ22122  Channel     Abend in AWSCHAN/AWSINTF at FC4D or 44AF
  PJ22652  Channel     IFI004 in VM/ESA
  PJ21799  AWSDM       Abend in IPLing with deck in "card reader".
  PJ22257  AWS39X0.MCD Incorrect condition code.
  PJ22564  AWSCKD      Failure in VM appl using very high cylinder number
  PJ25570  AWSCKD      Did not support datachained read of record 0.
  PJ22671  AWSCHAN     CLRCH could cause system to hang all (SAD all PINK)
  PJ22830  AWSCHAN     MVS/VTAM could not activate 3725
  PJ22931  AWSDM       AWSTAPE abended with exactly 15 devices
  PJ23102  AWSMAIN     AWSCKD CODE=5 pop up on IPL.
  P390A000 AWSPCSRV    LTRENAME CMS command fails
  P390A001 LAN3274     Sessions slow to start
  P390A002             Dup of PJ22257
  P390A003             Dup of PJ22671
  P390A004             Dup of PJ22122
  P390A005 AWSCFG      Abend when creating new devmap
  P390A006 AWSCFG      Volume named wrong in allocating 3380-K
  P390A007 AWSICA      Line drops on slow (e.g. 2400 baud) bisync on WAC
  P390A008 SCSI34x0    Error reading multi-volume tapes. "early" EOT was
                        sensed when reading a tape; it is now ignored.
  P390A009 SCSI34x0    Perform Subsystem Function now treated as a
                        no-op instead of giving a command reject.
  P390A010 SCSI34x0    Made traces when it shouldn't have.
  P390A011 INST3172    ZIP source filenames were reversed; if run it would
                        have unzipped the files onto the wrong drives.
  P390A012 AWS2821     Blank lines when there shouldn't be
                       New TR code point translate function.
  P390A014 CHAN370.SYS Intermittant Mouse/Keyboard hang or bad performance
