Memorandum To:

V3R1 OS/400 Support for Novell NetWare Users 
Subject:
Getting Started 
NetWare - Getting Started!

Table of Contents

  • Introduction 
  • FSIOP Hardware Requirements/Restrictions 
  • OS/400 Installation
  • Installation Checklist 
  • Determining Your OS/400 V3R1 Level 
  • Installing OS/400 PTFs 
  • Installing OS/400 Features 
  • Where to Go Next 
  • General Information
  • Novell Patches 
  • Displaying Installed Software Features 
  • Accessing the Sockets API for IPX 
  • Functional Limitations and Special Considerations 
  • FSIOP limitations 
  • Internetwork Packet Exchange (IPX) communications 
  • TCP/IP 
  • General 
  • New and Changed CL Commands 
  • Moving from V3R1 (IMPI) to V3R6 (PowerPC) 
  • Appendix A. Workstation Installation - Tested Devices/Cards

    Appendix B. PTF Special Instructions

  • MF09567 Special Instructions 
  • SF25805 Special Instructions 
  • Appendix C. Trademarks and Service Marks

    Introduction

    You have ordered OS/400 feature #1643 IBM* Network Extensions for OS/400* (5733SA1). This document contains information regarding this feature, and two related OS/400 features #1644 Integration Services for FSIOP (5733SA2) and #1645 Integration for Novell NetWare (5733SA3). Combined with PTFs to provide additional function to OS/400, these features provide OS/400 V3R1 Support for Novell** NetWare**. 

    In this document, the OS/400 features are referred to by their licensed product numbers: 5733SA1, 5733SA2 and 5733SA3. 

    At the time of printing the books for the features listed in Figure 1, some information was incomplete or unavailable. This document provides both updated information and an overall guide to planning, installing and getting started with OS/400 V3R1 Support for Novell NetWare. 

    As of March 1996, there will be a two levels of V3R1 OS/400: 

    1. V3R1 03/08/96 Level 

    2. This level has many of its OS/400 PTFs already permanently applied, saving you time during install. This new level will be shipped to customers ordering V3R1 after 03/08/96. 

    3. V3R1 Original Level 

    4. This is the original level of V3R1 that still can be used, but more time is needed for installation of PTFs. 

    This document shows you how to determine the level of V3R1 OS/400 you have installed and appropriate actions to install NetWare Integration support based on that level. 

    You are also referred to Informational APAR II09022. An informational APAR is a short document that you can obtain using the same command that you order PTFs. We will update this document regularly so that you can check for the latest information on these features and required PTFs before you proceed with the installation. 

    Note: IBM* Network Extensions for OS/400* (5733SA1), integrates much of its function directly into OS/400. Therefore, if you have IBM* Network Extensions for OS/400* installed on your AS/400 and do a slip install of V3R1 OS/400, you will need to also reinstall IBM* Network Extensions for OS/400*. A slip install involves reinstalling V3R1 OS/400 without first deleting it. PTFs for IBM* Network Extensions for OS/400* (5733SA1) listed in Informational APAR II09022 must also be reapplied. This note is true for both the OS/400 V3R1 Original Level and the OS/400 V3R1 03/08/96 Level.

    Figure 1. IBM OS/400 Support for Novell NetWare Features.
     
    Product ID/ PTFs  Product Size (See note)  Product Install Time  Contains  More Information 
    V3R1 system cumulative PTF package C5304310 (or later)  n/a  4-8 hours to load and apply PTFs  PTFs required to install and available for features 5733SA1, 5733SA2 and 5733SA3.  Informational APAR II09022. 
    5733SA1 (#1643)  8 MB  10-30 minutes  IPX** communications support and enablement for 5733SA2 and 5733SA3.  Internetwork Packet Exchange** Support (SC41-3400) 
    5733SA2 (#1644)  96 MB  10-30 minutes  Support for *BASE network server descriptions (NWSDs) and enablement for 5733SA3  Integration Services for File Server I/O Processor (SC41-3123) 
    5733SA3 (#1645)  2 MB  10-30 minutes  Support for installing and running NetWare on File Server Input/Output Processor (FSIOP).  OS/400 Integration for Novell NetWare (SC41-3124) 
    Note: The product size values may differ from those printed in the books for each feature; the size values listed here are current. 


    FSIOP Hardware Requirements/Restrictions

    A minimum of 32MB of memory is required to run Novell NetWare 4.1 on the FSIOP. A 1 or 2-port FSIOP card can be used. 

    Notes:

    1. If you want NetWare for SAA* to connect to the same AS/400 in which the FSIOP is installed, you must have either a second port on the FSIOP or a separate token-ring or Ethernet card. 
    2. If you want NetWare TCP/IP to communicate with OS/400 TCP/IP on the same AS/400 system, you must have either a second port on the FSIOP or a separate token-ring or Ethernet card. 
    Of the available memory, approximately 11MB (when configuring a 1-port adapter) and 14MB (when configuring a 2-port adapter) is not available for NetWare 4.1 to use. 

    You can use an existing FSIOP card (that had been used for LAN Server/400, for example) if it meets the minimum memory requirements for running Novell NetWare 4.1. However, you cannot run both LAN Server/400 and Novell NetWare 4.1 on the same FSIOP card. 

    When ordering your FSIOP, you must specify a feature number, as listed in Figure 2, which defines the memory and number of ports. For example, to order a FSIOP with 32MB of memory and two ports, specify feature #6527.

    Figure 2. FSIOP Feature Order Numbers
     
    Memory  One-Port Adapter  Two-Port Adapter 
    32MB  #6517  #6527 
    48MB  #6518  #6528 
    64MB  #6519  #6529 

    The FSIOP is supported on the following AS/400* system models: 
    • D Models D04, D06, D10, D20, D25, D35, D80 
    • E Models E04, E06, E10, E20, E25. E25, E90, E95 
    • F Models F04, F06, F25, F95, F97 
    • Server Models 100, 135 and 140 
    • Advanced Server Models 20S and 30S 
    • Advanced System Models 200, 300, 310 and 320 

    OS/400 Installation


    Installation Checklist

    Before you begin the installation, check that you have: 

    1. Received tapes containing the following: 
      1. The OS/400 V3R1 cumulative PTF package C5304310 (or a later cumulative PTF package). 
      2. An OS/400 feature tape containing one or more of the following features: 
        • 5733SA1 - IBM Network Extensions for OS/400 (#1643) 
        • 5733SA2 - IBM Integration Services for FSIOP (#1644) 
        • 5733SA3 - IBM OS/400 Integration for Novell NetWare (#1645) 
        This tape may be labeled AS/400 System Programs V3, or with the first feature that is loaded on the tape. One or more features may actually be on the tape. The tape comes with a media description report that describes which features are on the tape. 
    2. Received a 3.5" diskette labeled OS/400 Integration for Novell NetWare if you ordered OS/400 Integration for Novell NetWare 5733SA3. This diskette is used in the workstation installation procedure. 
    3. Obtained informational APAR II09022 containing details regarding the latest PTFs that are required for this installation process. This includes PTFs that are available on cumulative PTF tape C5304310 and any subsequent PTFs that are necessary or recommended. Issue the Send PTF Order (SNDPTFORD) command to obtain informational APAR II09022. 
    4. Referred to Appendix B. "PTF Special Instructions" to determine if these conditions apply to your installation. 
    5. Installed your AS/400 system with OS/400 V3R1. 
    6. Obtained PTF SF26838 to enable use of the automated procedure to permanently apply the PTFs as described in step 3 in the following section. 

    Determining Your OS/400 V3R1 Level

    1. First you need to determine whether you have installed the V3R1 Original Level or the V3R1 03/08/96 Level. 

    2. Use the Display PTF command to see if the following PTFs are applied. 

         DSPPTF LICPGM(5763999) SELECT(RE96010)
          DSPPTF LICPGM(5763SS1) SELECT(AP96010)
      
      
    3. If both PTF RE96010 for LP 5763999 and AP96010 for LP 5763SS1 are applied on the AS/400, you have the V3R1 03/08/96 Level. If you have this level, proceed to the "Installing OS/400 Features" section, ignoring the "Installing OS/400 PTFs" section. 
    4. If both PTF RE96010 for LP 5763999 and AP96010 for LP 5763SS1 are not applied on the AS/400, you have the V3R1 Original Level. If you have this level, proceed to the "Installing OS/400 PTFs" section, before proceeding to the "Installing OS/400 Features" section. 

    Installing OS/400 PTFs

    Follow the steps in this section ONLY if you have the V3R1 Original Level. If you have the V3R1 03/08/96 Level, proceed to the "Installing OS/400 Features" section. 

    Note that the PTFs you are installing provide added function to OS/400 V3R1. Normally, IBM delivers added function with a new operating system release. In this case, we are delivering you new OS/400 features that you can add to OS/400 V3R1. This means that we must ask you to ensure that the required PTFs are installed and permanently applied to your system. 

    The cumulative PTF tape contains all of the PTFs that are required for the installation of 5733SA1 in addition to other system fixes. If the required PTFs are not applied, the installation of 5733SA1 will fail. In addition, 5733SA2 and 5733SA3, if installed, will not function properly. 

    To permanently apply the required PTFs you must use the automated procedure that is available with PTF SF26838. This PTF provides a program that performs the required Apply PTF (APYPTF) commands.

    1. First, install the cumulative PTF tape C5304310 (or later) which contains PTFs for 5763999 and 5763SS1 and IPL the system. 

    2. You should refer to the shipping letter provided with the cumulative PTF package for installation instructions. 

    3. Now load and temporarily apply PTF SF26838. 

    4. This PTF contains the program to apply permanently those PTFs required for the installation of the 5733SA1 product. 

    5. Call the program QFPAPYPTF using the following command:
    6.    CALL PGM(QSYS/QFPAPYPTF)
      
      
      This program issues requests to apply permanently each of the PTFs required to install the IBM OS/400 Network Extensions (5733SA1) product. The PTFs are applied permanently as delayed PTFs. The program takes approximately five minutes. 

      If the PTFs are applied successfully the following message will be sent when the program ends: 

         CPC1215 -- Applying of PTFs completed.
      
      
      When you receive the completed message, you can go on to the next step. 

      If any failures occur, the following message will be sent when the program ends: 

         CPI35AD -- Applying PTFs failed.
      
      
      The job log is printed with job's spooled output for reference in the event of failures. If a failure occurs, see the job log for messages describing the errors. After correcting the errors, call QFPAPYPTF again to apply any remaining PTFs. 

      An error could occur if one of the required PTFs has been superseded. In this case the following messages will be sent for each superseded PTF: 

         CPF3635 -- PTF xxxxx superseded.
                  -- PTF xxxxx SUPERSEDED BY yyyyy
      
      
      If a PTF has been superseded, you should use the the Display Program Temporary Fix (DSPPTF) command, option 5 (Display PTF details), to display information about the superseding PTF. Permanently apply the superseding PTF and its prerequisites using the following command as an example: 
         APYPTF LICPGM(5763SS1) SELECT(SFyyyyy) APY(*PERM) DELAYED(*YES)
      
      
    7. Use the following command to place the system in restricted state:
    8.    ENDSBS SBS(*ALL) OPTION(*IMMED)
      
      
      Check the system operator's message queue using the command DSPMSG QSYSOPR and check that you have received the following message: 
         System ended to restricted condition
      
      
    9. Now issue the following command to IPL the system. This will permanently apply any PTFs that have been identified for this action.
    10.    PWRDWNSYS OPTION(*IMMED) RESTART(*YES) IPLSRC(B).
      
      
    11. You have now completed the installation of the required PTFs and you can go to the next section. 

    Installing OS/400 Features

    This section is required for both the V3R1 Original Level and the V3R1 03/08/96 Level. 

    This section describes how to install the OS/400 features required to provide OS/400 support for Novell NetWare. 

    1. Signon to the system again as QSECOFR. Use the following command to place the system in restricted state:
    2.    ENDSBS SBS(*ALL) OPTION(*IMMED)
      
      
      Check the system operator's message queue using the command DSPMSG QSYSOPR and check that you have received the following message: 
         System ended to restricted condition
      
      
    3. Place the OS/400 features tape in the drive and enter:
    4.    RSTLICPGM LICPGM(5733SA1) DEV(TAPnn)
      
      
      Note: Installing the Network Extensions for OS/400 feature (5733SA1) performs a permanent update to OS/400. Although you can use the Delete Licensed Program (DLTLICPGM) command to delete the feature, the updates to OS/400 cannot be removed. 
    5. Now use the following commands to install the additional OS/400 features. Both features are required to provide OS/400 support for Novell NetWare.
    6.    RSTLICPGM LICPGM(5733SA2) DEV(TAPnn)
          RSTLICPGM LICPGM(5733SA3) DEV(TAPnn)
      
      
    7. Now change the usage limit for the 5733SA2 feature with the following command:
    8.    CHGLICINF PRDID(5733SA2) FEATURE(5050) USGLMT(1) THRESHOLD(1)
      
      
    9. Now you need to install some PTFs for the OS/400 features 5733SA1, 5733SA2 and 5733SA3. 
      • Place the cumulative PTF tape in the drive again. 
      • Enter GO PTF. Select option 8. 
      • Enter the Device name and specify Automatic IPL(*NO). Accept the remaining command defaults. Press Enter. The PTFs on the cumulative PTF tape for for 5733SA1, 5733SA2 and 5733SA3 will be loaded. 
    10. At the time of writing the following hiper PTFs are available and necessary for the correct functioning of the NetWare Integration for OS/400 product. 
      • 5733SA2 - SF28383 
      • 5733SA2 - SF28430 
      • 5733SA3 - SF28620 
      Refer to information APAR II09022 for PTF information including cumulative PTF tape, latest hiper, required, and highly recommended PTFs. This information APAR pertains to PTFs available since the cumulative PTF tape C5304310. Obtain these PTFs and load them now using the Load PTF (LODPTF) command. Apply the PTFs that were loaded using the Apply PTF (APYPTF) command. 
    11. If your system has not already done an IPL as a result of the prior step, then IPL your system now:
    12.    PWRDWNSYS OPTION(*IMMED) RESTART(*YES) IPLSRC(B)
      
      
    13. Sign on to the system again. Now all the OS/400 features and their PTFs have been applied. 

    Where to Go Next

    You are now ready to install a NetWare server on your AS/400. This involves running the install NetWare server command on the AS/400 and then a second stage of the installation that is performed on a workstation running Windows** 3.1. 

    Refer to Appendix A. "Workstation Installation - Tested Devices/Cards" for a list of the hardware that has been tested for the workstation installation of NetWare 4.1. 

    Full installation and configuration instructions can be found in Chapter 2 of OS/400 Integration for Novell NetWare (SC41-3124). 


    General Information


    Novell Patches

    There are NetWare 4.1 OS patches and updated Novell NetWare Loadable Modules (NLMs)** modules that are shipped along with Integration Services for FSIOP (5733SA2). Refer to OS/400 Integration for Novell NetWare (SC41-3124) for more information on which patches have been included. Hereafter, it will be the customer's responsibility to obtain any other NetWare patches that are necessary. 


    Displaying Installed Software Features

    The 5733SA1, 5733SA2 and 5733SA3 features will not be displayed using GO LICPGM option 10. However, they will be displayed if you enter the Display Software Resource (DSPSFWRSC) command. 


    Accessing the Sockets API for IPX

    To access the Sockets API for IPX communications you must ensure that the following have been installed: 

    • System Openness Includes (5763SS1 - Option 13) 
    • ILE C/400* (5763CX2) 
    • Network Extensions for OS/400 (5733SA1) 
    • Sockets PTFs 
      • SF23612 - OSP-SYSINC-INCORROUT MUST HANDLE BLANK FOR NEW MEMBER 
      • SF25558 - ADD HEADER FILES FOR AF_NS SUPPORT 
      • SF25543 - ADD SOURCE PHYSICAL FILE NETNS FOR AF_NS SOCKETS SUPPORT 
      • SF25959 - OSP ADD SOCKET IPX COMMANDS TO SYS/IOCTL.H HEADER FILE 

    Functional Limitations and Special Considerations

    FSIOP limitations

    • You cannot run IPX over a *LANSERVER File Server I/O Processor (FSIOP). You can run IPX over a *BASE or *NETWARE FSIOP. 
    Internetwork Packet Exchange (IPX) communications
    • If you use Anynet/400 and its IP over IPX support and use the Work with TCP Status (WRKTCPSTS) command to view details of an IP over IPX interface, the command will fail and an FFDC error will be logged. There are no current plans to provide a PTF for this problem in V3R1. 
    TCP/IP
    • Verify TCP/IP Connection (PING) may fail if an internet address is specified that corresponds to a line associated with a local *NETWARE network server description (NWSD). 
    • The Change TCP/IP Attributes option to enable datagram forwarding does not apply to lines associated with a *NETWARE network server description (NWSD). TCP/IP packets entering the AS/400 via a line associated with a *NETWARE network server description (NWSD) will not be forwarded to other TCP/IP interfaces by OS/400. 
    General
    • Verify Communications (VFYCMN) Link Test may fail for a line associated with a *NETWARE network server description (NWSD) if 1) the controller to be tested specified that line's adapter address, or 2) the controller to be tested is *NONE and the LAN remote adapter address is *SELF (the default). Possible workarounds: Use a *BASE network server description (NWSD) or use a remote adapter address (either with or without a controller). 
    • If you are experiencing Ethernet communication failures with AS/400, the problem may be caused by the Multiport Transceiver/Hub. Some Multiport Transceiver/Hubs do not conform with Ethernet Standards. The applicable Ethernet Standards are ISO/IEC 8802-3 (ANSI/IEEE 802.3). The AS/400 information PTFs identified below describe potential customer circumventions. 

    • The following AS/400 feature codes may be affected. 

      • All FSIOPs configured for Ethernet connections. See informational APAR II08464. 
      • Feature Code 9174 (Ethernet) on Advanced Series Model 200 or Advanced Portable Models. See informational APAR II08473. 

    New and Changed CL Commands

    New CL commands will be available and some existing CL commands will be changed as a result of installing the required PTFs and the OS/400 features (5733SA1 and 5733SA3). 

    The Install NetWare Server (INSNTWSVR) command is new as part of OS/400 Integration for Novell NetWare (5733SA3). This command can be found in OS/400 Integration for Novell NetWare (SC41-3124). In addition, there are new IPX commands that are available with Network Extensions for OS/400 (5733SA1). The IPX CL commands can be found in Appendix F of Internetwork Packet Exchange Support (SC41-3400). 

    The CL commands listed in Figure 3 are changed as a result of installing the required PTFs and Network Extensions for OS/400 (5733SA1).

    Figure 3. Changed CL Commands
     
    CL Command  Command name  Changes 
    CRTNWSSTG  Create NWS Storage Space  Added FORMAT keyword. 
    WRKNWSSTS  Work with NWS Status  Added SVRTYPE with values *LANSERVER, *BASE and *NETWARE. 
    SBMNWSCMD  Submit Network Server Command  Added SVRTYPE with values *LANSERVER, *BASE and *NETWARE and CMDTYPE with values *SVRTYPE, *OS2 and *NETWARE. 
    CRTNWSD  Create Network Server Description  Added TYPE, LCLIPXCNN, MSGQ, CFGFILE and IPX keywords. 
    CHGNWSD  Change Network Server Description  Added LCLIPXCNN, MSGQ, CFGFILE and IPX keywords 
    ADDNWSSTGL  Add Server Storage Link  Added TYPE and ACCESS keywords 
    VRYCFG  Vary Configuration  Added RESETCFGF keyword 


    Moving from V3R1 (IMPI) to V3R6 (PowerPC)

    If you have installed any of the OS/400 Support for Novell NetWare features on your V3R1 system, you must be aware that these functions are NOT available on V3R6. If you have installed this support and plan to move from V3R1 to V3R6, you will not retain this function. Furthermore, you should refer to informational APAR II08907 for more details and the steps that are necessary should you choose to move from V3R1 to V3R6.


    Appendix A. Workstation Installation - Tested Devices/Cards

    Figure 4. Tested Devices for NetWare Installation
     
    Name  Description  Company 
    Sound Blaster** 16 Value** Addition  Sound Board/Multi-Media Package  Creative Labs** 
    Sound Blaster Discovery CD**  Sound Board/Multi-Media Package  Creative Labs 
    CDQ300  Sound Board/Multi-Media Package  REVEAL** 
    MV-3100 Super Deluxe  Sound Board/Multi-Media Package  Media Vision** 
    MC579BP  IDE CD-ROM  Panasonic** 
    FX400  IDE CD-ROM  Mitsumi** 
    SuperQuad** 4X  IDE CD-ROM  Teac** 
    CDU76S  SCSI** CD-ROM  SONY** 
    Backpack** External CD-ROM  Parallel Printer Port CD-ROM  MicroSolutions** 
    Portable PCMCIA 2X CD-ROM  PCMCIA-Connect CD-ROM  Panasonic 
    Ethernet Adapter  Ethernet ISA LAN Card  IBM 
    Etherlink** III Combo (3C509BCOMBO)  Ethernet ISA LAN Card  3COM** 
    EtherExpress** FlashC  Ethernet ISA LAN Card  Intel** 
    Elite** Ultra 16C BNC/AUI/10BaseT  Ethernet ISA LAN Card  SMC** 
    ProNET/E** P1370-XX  Ethernet ISA LAN Card  PROTEON** 
    EP2000 Plus Combo  Ethernet ISA LAN Card  Eagle Technology 
    Etherstreamer**  Ethernet Microchannel LAN Card  IBM 
    EtherExpress MCA TP  Ethernet Microchannel LAN Card  Intel 
    Series 1720 Plus MCA (AT-1720BT)  Ethernet Microchannel LAN Card  Allied Telesis
    International** 
    Etherlink III PCI Combo  Ethernet PCI LAN Card  3COM 
    ProNET/E 10BT/10B2 PCMCIA  Ethernet PCMCIA LAN Card  PROTEON 
    Token-Ring Auto 16/4 Credit Card  Token-Ring PCMCIA LAN Card  IBM 
    16/4 Token Ring ISA LAN Adapter  Token-Ring ISA LAN Card  IBM 
    Token-Card Elite  Token-Ring ISA LAN Card  SMC 
    ProNET-4/16 Plus Token-Ring ISA  Token-Ring ISA LAN Card  PROTEON 
    Token-Ring Network PC Adapter II  Token-Ring ISA LAN Card  IBM 
    Token-Ring Network 16/4 Adapter  Token-Ring ISA LAN Card  IBM 
    Olicom** TokenRing ISA 16/4 Adapter  Token-Ring ISA LAN Card  OLICOM** 
    16/4 Token-Ring Card  Token-Ring Microchannel LAN Card  IBM 
    LANStreamer* Adapter  Token-Ring Microchannel LAN Card  IBM 


    Appendix B. PTF Special Instructions


    MF09567 Special Instructions

    ..          5763999 5050 0000 MF09567 2924 R01M00    0003 
    .
     ., OSP-COMM ALLOW ENABLEMENT OF SNA OVER IPX ANYNET SUPPORT
    
     PTF/FIX #: MF09567 - OPERATING SYSTEM/400
     LICENSED PROGRAM: 5763999
    
    -------------------------------------------------------------------------
     SYSTEM : MODELS  : RELEASE : RECOMPILE : LIBRARY  :  MRI   :  APAR     :
            :         :         :           :          : FEATURE:  FIXED    :
            :         :         :           :          :        :           :
     AS/400 :  *ALL   : V3R1M0  :     N     :   QSYS   :  NONE  :  MA10867  :
            :         :         :           :          :        :  MA10996  :
    -------------------------------------------------------------------------
    
     PRE/CO-REQUISITE PTF/FIX LIST
     -----------------------------
       REQ   LICENSED  PTF/FIX
       TYPE  PROGRAM   NUMBER   LICENSED PROGRAM DESCRIPTION
       ----  --------  -------  ---------------------------------------------
       CO    5763SS1   SF21042  OPERATING SYSTEM/400
    
     DESCRIPTION OF PROBLEM FIXED FOR APAR MA10867 :
     -----------------------------------------------
    
       Update APPC over TCP/IP support to allow the addition of APPC
       over IPX support.
    
     CORRECTION FOR APAR MA10867 :
     ----------------------------
    
       Update APPC over TCP/IP support to allow the addition of APPC
       over IPX support.
    
     CIRCUMVENTION FOR APAR MA10867 :
     --------------------------------
       None.
    
     DESCRIPTION OF PROBLEM FIXED FOR APAR MA10996 :
     -----------------------------------------------
           NS/Win uses fixed pacing.  The BIND sent to AnyNet* contains
       primary and secondary receive and send pacing windows as
       configured locally.  AnyNet/Win strips the TH as architected,
       and sends the BIND on an MPTN_Connect flow to the partner, an
       AS/400.  AnyNet/400* receives the BIND, and decides to do
       adaptive pacing (locally) between the SNA stack and the syntax
       mapper.  By the time the BIND Rsp is returned to AnyNet/Win, the
       pacing window sizes have been made 0.
    
     CORRECTION FOR APAR MA10996 :
     -----------------------------
       ANYNET has been updated to correctly reflect back pacing
       information has been sent as a result of a BIND.
    
     CIRCUMVENTION FOR APAR MA10996 :
     --------------------------------
       None.
    
     ACTIVATION INSTRUCTIONS :
     -------------------------
       None.
    
     SPECIAL INSTRUCTIONS :
     ----------------------
    
       If you have not experienced this problem, nothing needs to be done.
       If you have experienced this problem, you need to do the following
       after you apply the PTF:
    
       You must end the TCP/IP protocol stack, vary off all
       controller description objects of LINKTYPE(*ANYNW), then
       vary on the controller description objects and start TCP/IP.
       The procedure to do this is the following:
    
       1) Issue the ENDTCP CL command.  Wait for completion of this
          command.
    
       2) Issue the VRYCFG CL command to vary off all controller
          descriptions of LINKTYPE(*ANYNW).
    
       3) Issue the VRYCFG CL command to vary on all controller
          descriptions of LINKTYPE(*ANYNW).
    
       4) Issue the STRTCP CL command to restart the TCP/IP protocol
          stack.
    
     DEFAULT INSTRUCTIONS :
     ----------------------
       THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
    
     SUPERSEDES
     PTF/FIX NO(S).  APAR TITLE LINE
     -------------  --------------------------------------------------------
       MF08868      OSP-COMM-APPCTCP-INCORROUT CONNECTIONS IN FIN-WAIT-2 STATE
       MF09018      OSP-COMM-APPCTCP-INCORROUT CANNOT CONNECT TO SYSTEM
       MF08777      OSP-COMM-APPCTCP-INCORROUT DATA QUEUE APPLICATION HANGS
       MF08777      OSP-COMM-APPCTCP-INCORROUT QAPPCTCP JOB FAILS
       MF08352      OSP-COMM-APPCTCP USER CAN NOT DEFINE DOMAIN SUFFIX
       MF07911      OSP-COMM-APPCTCP-INCORROUT APPC APPLICATION HANGS
    
    

    SF25805 Special Instructions

    ..          5733SA2 5050 0000 SF25805 2924 R01M00    0003 
    .
     ., OSP INTSVC RCONSOLE DOES NOT DISPLAY NETWARE SERVER
    
     PTF/FIX #: SF25805 - IBM INTEGRATION SERVICES FOR FSIOP
     LICENSED PROGRAM: 5733SA2
    
    -------------------------------------------------------------------------
     SYSTEM : MODELS  : RELEASE : RECOMPILE : LIBRARY  :  MRI   :  APAR     :
            :         :         :           :          : FEATURE:  FIXED   
            :         :         :           :          :        :           :
     AS/400 :  *ALL   : V3R1M0  :     N     :  QFPINT  :  NONE  :  SA46373  :
    -------------------------------------------------------------------------
    
     PRE/CO-REQUISITE PTF/FIX LIST
     -----------------------------
       REQ   LICENSED  PTF/FIX
       TYPE  PROGRAM   NUMBER   LICENSED PROGRAM DESCRIPTION
       ----  --------  -------  ---------------------------------------------
       PRE   5763SS1   SF25519  OPERATING SYSTEM/400
       CO    5733SA3   SF25793  OPERATING SYSTEM/400
       CO    5733SA2   SF26026  OPERATING SYSTEM/400
       CO    5733SA2   SF25974  OPERATING SYSTEM/400
       CO    5733SA1   SF25973  OPERATING SYSTEM/400
    
     DESCRIPTION OF PROBLEM FIXED FOR APAR SA46373 :
     -----------------------------------------------
    
       1) When running a NetWare server, some line errors are not
       detected. For example, LAN cables
       that are disconnected or fail after the network server description
       (NWSD) is varied on are not detected.
    
       2) If AS/400 IPX has been started, a NetWare server can not be
       accessed by remote console until a license is installed.
    
     CORRECTION FOR APAR SA46373 :
     -----------------------------
    
       1) Line errors are now detected.
    
       2) NetWare configuration has been changed so that if AS/400 IPX has
       been started, remote console access is possible.
    
     CIRCUMVENTION FOR APAR SA46373 :
     --------------------------------
    
       None.
    
     ACTIVATION INSTRUCTIONS :
     -------------------------
    
       When this PTF is applied, the changes are not automatically activated.
       To activate the changes, you must:
    
       1. Vary off (VRYCFG) all *NETWARE network server descriptions at your
          convenience.
    
       2. Then, as you vary on the first network server description
          for each national language installed, the changes will be
          activated.
    
    
     SPECIAL INSTRUCTIONS :
     ----------------------
       Make sure all co-requisite PTFs are applied before preceding.  This
       PTF will not work without the co-requisite PTFs applied.
    
       When to apply this PTF:
    
       -  This PTF should be applied before creating any *NETWARE
          network server descriptions (NWSDs).
    
       -  If you have already created any *NETWARE NWSDs then you must
          delete and recreate them. The following procedure can be used:
          1. Enter the WRKNWSD command to list all of the NWSDs.
          2. Use the option 5=Display to find all NWSDs with a network
             server type of *NETWARE.
          3. For each *NETWARE NWSD found, the following steps can be used
             from the "Work with Network Server Descriptions" panel:
            a. Make sure that you save a copy of the current *NETWARE NWSD
               configuration before deleting the NWSD.  This can be done by
               using option 6=Print or option 9=Retrieve Source.
            b. Use option 4=Delete to delete the *NETWARE NWSD.
            c. Recreate the deleted *NETWARE NWSD. If you used option
               9=Retrieve Source in step 3a, you can use the retrieved CL
               source to recreate a *NETWARE NWSD with the same values as
               the deleted NWSD.
    
               Otherwise, use option 1=Create to recreate a *NETWARE
               NWSD with the same values as the one
               that was deleted in step 3b. Note that if any line
               descriptions were attached to the deleted NWSD, make sure
               that they are specified on the CRTNWSD command in the
               PORTS parameter.  After creating the new NWSD,
               link the NWSD to the appropriate network server storage
               spaces (these were removed when you deleted the original NWSD)
               using the ADDNWSSTGL command.
    
       If this PTF is removed and not to be reapplied:
    
       1. All co-requisite PTFs must all so be removed.
       2. All NWSDs must be deleted and recreated (see above for details).
    
     DEFAULT INSTRUCTIONS :
     ----------------------
       THIS PTF CAN BE APPLIED IMMEDIATE OR DELAYED.
    
     SUPERSEDES
     PTF/FIX NO(S).  APAR TITLE LINE
     -------------  --------------------------------------------------------
         NONE
    
    

    Appendix C. Trademarks and Service Marks

    The following terms, denoted by an asterisk(*) in this publication, are trademarks of the IBM Corporation in the United States or other countries or both. 

      AS/400               OS/400
      IBM                  Etherstreamer
      SAA                  400
      C/400                AnyNet
      AnyNet/400
    The following terms, denoted by a double asterisk(**) in this publication, are trademarks or registered trademarks of their respective companies. 
    Allied Telesys International   Allied Telesys Intnal
    Creative Labs                  Creative Labs
    Discovery CD                   Creative Labs
    Eagle Technology               Eagle Technology Inc.
    Elite                          SMC Inc.
    EtherExpress                   Intel Inc.
    Etherlink                      3COM Inc.
    Intel                          Intel Inc.
    Internetwork Packet Exchange   Novell, Inc
    IPX                            Novell, Inc
    Media Vision                   Media Vision Inc.
    Mitsumi                        Mitsumi Inc.
    NetWare                        Novell, Inc.
    Novell                         Novell, Inc.
    Panasonic                      Panasonic Inc.
    PCMCIA                         Personal Comp Mem Card
                                   Intal Association
    ProNET                         PROTEON Inc.
    ProNET/E                       PROTEON Inc.