


                         IBM HIGH PERFORMANCE
                         OPTICAL FILE SYSTEM
                         INSTALLATION GUIDE
































































  +--- NOTE -----------------------------------------------------------+
  |                                                                    |
  | Before using this information and the product it supports, be sure |
  | to read the general information under -- Heading 'NOTICES' unknown |
  | --.                                                                |
  |                                                                    |
  +--------------------------------------------------------------------+

  THE FOLLOWING PARAGRAPH DOES NOT APPLY TO THE UNITED KINGDOM OR ANY
  COUNTRY WHERE SUCH PROVISIONS ARE INCONSISTENT WITH LOCAL LAW:
  INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
  AND PROGRAM(S) "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
  INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
  MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.  Some states do
  not allow disclaimer of express or implied warranties in certain
  transactions, therefore, this statement may not apply to you.

  This publication could include technical inaccuracies or typographical
  errors.  Changes are periodically made to the information herein;
  these changes will be incorporated in new editions of the publication.
  IBM may make improvements and/or changes in the programs(s) described in
  this publication at any time.

  It is possible that this publication may contain reference to, or
  information about, IBM products (machines and programs), programming,
  or services that are not announced in your country.  Such references
  or information must not be construed to mean that IBM intends to
  announce such IBM products, programming, or services in your country.

  Requests for technical information about IBM products should be made
  to your IBM Authorized Dealer or your IBM Marketing Representative.






















  ii  HPOFS Installation Guide









  CONTENTS





  CHAPTER 1.  INTRODUCING HPOFS  . . . . . . . . . . . . . . . . . . . . . .  1
  Hardware Requirements  . . . . . . . . . . . . . . . . . . . . . . . . . .  2
  Software Requirements  . . . . . . . . . . . . . . . . . . . . . . . . . .  2

  CHAPTER 2.  INSTALLING HPOFS WITH OS/2 2.0 OR LATER  . . . . . . . . . . .  5
  Installing HPOFS with DDINSTAL   . . . . . . . . . . . . . . . . . . . . .  5
  Installing HPOFS without DDINSTAL  . . . . . . . . . . . . . . . . . . . .  7

  CHAPTER 3.  USING UTILITIES AND PROTOCOLS FOR HPOFS  . . . . . . . . . . .  9
  Utilities  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
    CERTIFYF   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .  9
    FORMAT   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   10
      Return Codes:  . . . . . . . . . . . . . . . . . . . . . . . . . . .   12
    CHKDSK   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   13
      Return codes   . . . . . . . . . . . . . . . . . . . . . . . . . . .   13
      Parameters   . . . . . . . . . . . . . . . . . . . . . . . . . . . .   14
  Protocols  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   14
    Name Space Rules   . . . . . . . . . . . . . . . . . . . . . . . . . .   14
    Directory Entry  . . . . . . . . . . . . . . . . . . . . . . . . . . .   15
    Volume Rule  . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   16
    Extented Attribute Support   . . . . . . . . . . . . . . . . . . . . .   16
    OS/2 and DOS Command Supported Differently   . . . . . . . . . . . . .   16
    Unsupported OS/2 and DOS Commands  . . . . . . . . . . . . . . . . . .   16

  CHAPTER 4.  LOCAL AREA NETWORK ACCESS  . . . . . . . . . . . . . . . . .   19
  IBM 3431 LAN-Attached Token Ring and Ethernet Setup for AS/400   . . . .   20
  AS/400 Line Description Configuration  . . . . . . . . . . . . . . . . .   26
    AS/400 Controller Description  . . . . . . . . . . . . . . . . . . . .   26
    AS/400 Device Description  . . . . . . . . . . . . . . . . . . . . . .   27

  APPENDIX.  OBTAINING CORRECTIVE SERVICE DISKS  . . . . . . . . . . . . .   29

  GLOSSARY   . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   31

  INDEX  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .   35















  (C) Copyright IBM Corp. 1995                                              iii

































































  iv  HPOFS Installation Guide







  CHAPTER 1.  INTRODUCING HPOFS





  The IBM* High Performance Optical File System (HPOFS) is a removable media
  file system for optical storage devices.  HPOFS can be used along with or
  instead of the OS/2* 2.0,2.1, 3.0(WARP) file allocation table (FAT) file
  system.

  HPOFS uses the unique features of optical media, and features include:

  o   Long name file support (254 characters maximum length)
  o   Mixed case file name support
  o   Full extended attribute support
  o   Multiple code page support for world-wide use
      -   Code page 437 U.S. ENGLISH
      -   Code page 500 EBCDIC
      -   Code page 850 INTERNATIONAL ASCII
      -   Code page 942 JAPANESE
      -   Code page 944 KOREAN
      -   Code page 948 CHINESE

  Use HPOFS in the following circumstances:

  o   Copying files from hard disk drives formatted by using the High
      Performance File System (HPFS).

      When copying files from HPFS-formatted hard disk drives onto HPOFS
      formatted optical cartridges, mixed case and long-file names, in addition
      to extended attribute files, are preserved.

  o   Migrating 5.25-inch cartridges into the 3995 optical library.

      Because HPOFS is used in the 3995 libraries, cartridges can be loaded
      directly into the library without having to be copied.

  o   Ability to read cartridges formatted and written on a 3995 optical
      library.

  o   High performance requirements.

      HPOFS provides superior performance in many situations, especially when
      many files are present on a cartridge.

  Use the standard FAT file system when exchanging optical media with another
  station that does not have HPOFS.   Do not use HPOFS in this circumstance.

  NOTE:  Refer to IBM 3995 Optical Library Dataserver:  Optical Disk Format for
  more specific information.






  (C) Copyright IBM Corp. 1995                                                5







  HARDWARE REQUIREMENTS

  The following SCSI cards are supported:

  o   The following list is of tested SCSI cards--other cards
      may support optical drives but to be reasonably sure
      of support we reccommend you use one of the following:

      For PS2 microchannel machines--
        IBM PS/2 MC adapter/A & IBM PS/2 MC adapter/A w/cache
         Device Driver required-IBM2SCSI.ADD

      For AT bus machines--
        IBM AT FAST SCSI adapter 16bit
        Future Domain TMC 1680 high performance 16 bit ISA
         Device Driver required-FD16-700.ADD

      For PCI bus machines--
        Adaptec AHA2940
         Device Driver required-AIC7870.ADD

      For Local Bus machines--
         NONE TESTED

  The following drives are supported:

  o   IBM 5.25-inch Rewritable Optical Disk Drive 3431 Model 001

  o   IBM 5.25-inch Rewritable Optical Disk Drive 3431 Model 705

  o   IBM 3.5 Rewritable Optical Disk Drive(128M and 230M)

  o   IBM 3.5 Rewritable Optical Disk Drive 3432  Mod 705

  o   IBM 3.5 Rewritable Optical Disk Drive 3432  Mod 715

  o   IBM 5.25-inch 1/2 High 1.3 GB Rewritable Optical Disk Drive

  SOFTWARE REQUIREMENTS

  o   OS/2 2.0/2.1/3.0(WARP) installed as current operating system

  o   CONFIG.SYS will require the following two lines, which are device drivers
      supplied with OS/2 2.0/2.1/3.0(WARP). The .ADD specified will be specific
      to your SCSI adapter--therefore name_add.ADD is specified.

      NOTE:  The IBM2SCSI.ADD is only used with an IBM PS/2* computer.  Refer
      to your SCSI adapter manual to load your specific adapter device driver
      for your particular SCSI adapter card.

  +---------------------------------------------------------------------------+
  |                                                                           |
  |    BASEDEV = name_add.ADD                                                 |
  |    BASEDEV = OS2SCSI.DMD                                                  |
  |                                                                           |
  +---------------------------------------------------------------------------+



  6  HPOFS Introduction





  o   IBM High Performance Optical File System (HPOFS) diskette, which contains
      the following files:

      1.  MO.SYS -- device driver

      2.  CERTIFYF.EXE -- utility to certify a disk prior to formatting FAT

      3.  MO001.MSG -- message file for MO.SYS

      4.  UHPOFS.DLL -- contains FORMAT and CHKDSK utilities

      5.  DBCS3995.DLL -- required even if DBCS is not used

      6.  FMT001.MSG -- message file supplied for for UHPOFS.DLL.  It is a copy
          of the messages file FMTENV.MSG for national language support.

          -   FMTENU.MSG is the message file in English.
          -   FMTDEU.MSG is the message file in German.
          -   FMTFRA.MSG is the message file in French.
          -   FMTESP.MSG is the message file in Spanish.
          -   FMTITA.MSG is the message file in Italian.
          -   FMTJPN.MSG is the message file in Japanese.

          NOTE:  To install a language other than English, copy the appropriate
          message file to FMT001.MSG.  This will overwrite the FMT001.MSG file
          with the appropriate language file.

      7.  HPOFS20.IFS -- installable file system for both rewritable and
          write-once media.

      8.  README.DOC provides the latest information Mo.DDP and HPOFS.DDP are
          files required by OS2/2.x and later DDINSTAL programs.


  o   FORMAT.COM supplied with OS/2 2.1 must be replaced with the latest format
      utility.  If the date on the format.com utility is April, 1993 please
      replace with the format.com supplied on the installation disk.  If the
      date is later that April, 1993 please use the format.com supplied with
      OS/2 version you are using.





















  7  HPOFS Introduction





  CHAPTER 2.  INSTALLING HPOFS WITH OS/2 2.x OR LATER

  This section covers the installation procedure for HPOFS.  Follow the
  checklist before beginning work:

  __ 1.  Read the README.DOC file on the installation disk for the latest
         changes not contained in this document.

  __ 2.  Ensure that IBM OS/2 2.0 or later is installed.

  __ 3.  Use one of the following options:

         o   Installing HPOFS with DDINSTALL
         o   Installing HPOFS without DDINSTALL


  INSTALLING HPOFS WITH DDINSTAL

  This section covers the installation procedure for HPOFS if you use the
  DDINSTAL program:

  __ 1.  Turn the computer on and wait for the operating system to start.

  __ 2.  Make a backup copy of your installation diskette before proceeding.

  __ 3.  Insert the backup HPOFS diskette you created into drive A.

  __ 4.  Select either OS/2 WINDOW or OS/2 FULL SCREEN.

  __ 5.  On the drive on which OS/2 is currently installed, make a directory
         FILESYS.

  __ 6.  For example:

  +---------------------------------------------------------------------------+
  |                                                                           |
  |            [C:>] MD FILESYS                                               |
  |                                                                           |
  +---------------------------------------------------------------------------+

  __ 7.  At the command prompt of the drive with OS/2 installed and with the
         FILESYS directory, type DDINSTAL and press Enter.

  __ 8.  An OS/2 Device Driver Installation screen will appear on your console
         The source directory should be the diskette drive letter where your
         HPOFS diskette currently resides (if you are following the above
         instructions this should be drive A.  If this is not the correct drive
         letter, change if necessary using the CHANGE and SET buttons from the
         screens.  Your destination directory should be the drive with OS/2
         currently installed and the destination path will be FILESYS,  Use the
         CHANGE and SET buttons from the screens to make this your destination
         directory.  You should now have both source and destination
         directories correct.






  (C) Copyright IBM Corp. 1995                                                8




  __ 9.  Click on the INSTALL button.  A screen to select Device Drivers should
         now appear.  Select the HPOFS device driver and the IBM OS/2 MAGNETO
         OPTICAL DEVICE DRIVER by highlighting them, and then, click on the OK
         button. This will install HPOFS (the installable file system), MO.SYS,
         all message files, and will update your CONFIG.SYS file.

  __ 10. When the Device Driver Installation screen returns you may choose EXIT
         A screen will appear to tell you that the configuration changes have
         been made, and that you need to restart your system.  Before
         restarting, edit your CONFIG.SYS file with a suitable text editor.  At
         the end of the config.sys file, 2 lines should have been added.

  +---------------------------------------------------------------------------+
  |                                                                           |
  |          DEVICE=[DRIVE LETTER]:\FILESYS\MO.SYS                            |
  |          IFS=\FILESYS\HPOFS20.IFS                                         |
  | note-- if you will use 1024 byte per sector media it is strongly advised  |
  |  that you use the following line in your config.sys instead of line above |
  |          DEVICE=[DRIVE LETTER]:\FILESYS\MO.SYS /1                         |
  +---------------------------------------------------------------------------+

         You will need to attach the proper disk drive letter and colon to the
         IFS statement before restarting your system.  After editing, your
         lines should be as follows:

  +---------------------------------------------------------------------------+
  |                                                                           |
  |          DEVICE=[DRIVE LETTER]:\FILESYS\MO.SYS                            |
  |          IFS=[DRIVE LETTER]:\FILESYS\HPOFS20.IFS                          |
  |                                                                           |
  +---------------------------------------------------------------------------+

  __ 11. If an IBM 3995 library is attached, make sure that the IBM 3995
         library device driver is installed before MO.SYS in config.sys.

  __ 12. If you have previously installed an IBM 3.5-inch optical disk drive,
         you will have a OPTICAL.SYS statement in the CONFIG.SYS file and this
         must either be removed (MO.SYS will support the IBM 3.5 inch optical
         disk drive) or must follow both the IBM 3995 library device driver(if
         installed) and the mo.sys device driver. You will need to use a text
         editor and modify your CONFIG.SYS file so that the MO.SYS device
         driver precedes the OPTICAL.SYS device driver.

         NOTES:

         a.  If all three devices are installed the order in which the device
             drivers appear in config.sys is as follows:
  +---------------------------------------------------------------------------+
  |                                                                           |
  |          DEVICE=DRIVE\PATH\IBM3995.SYS                                    |
  |          DEVICE=DRIVE\PATH\MO.SYS                                         |
  |          DEVICE=DRIVE\PATH\OPTICAL.SYS                                    |
  |                                                                           |
  +---------------------------------------------------------------------------+

         b.  Add only the above drivers to CONFIG.SYS file that are necessary
             to support your specific hardware configuration.  If you are using
             more than one of the above devices, it is absolutely essential
             that the device statements appear in the correct order.

  __ 13. Remove the diskette from drive A and restart the computer.

  9  HPOFS Installation Guide






  INSTALLING HPOFS WITHOUT DDINSTAL

  This section covers the installation procedure for HPOFS if you do not use
  the DDINSTAL program.  The following files are required:

  __     MO.SYS

  __     CERTIFYF.EXE

  __     MO001.MSG

  __     UHPOFS.DLL

  __     DBCS3995.DLL

  __     FMT001.MSG

         NOTE:  Remember to use appropriate language message file for
         FMT001.MSG.

  __     HPOFS20.IFS

  __ 1.  Make a backup of your CONFIG.SYS file by using copy:

  +---------------------------------------------------------------------------+
  |                                                                           |
  |     COPY C:\CONFIG.SYS C:\CONFIG.BAK                                      |
  |                                                                           |
  +---------------------------------------------------------------------------+

  __ 2.  Copy the files listed above into a directory of your choice.

  __ 3.  Edit CONFIG.SYS using the OS/2 system editor or editor of your choice.

  __ 4.  Make sure the BASEDEV = statements shown in "Software Requirements" on
         page 2 appear in the CONFIG.SYS file.

  __ 5.  Make sure that the directory where you copied UHPOFS.DLL and
         DBCS3995.DLL is in your LIBPATH statement in CONFIG.SYS.

  __ 6.  Make sure the directory(s) you copied message files FMT001.MSG and
         MO001.MSG is in your DPATH statement in CONFIG.SYS.

  __ 7.  Add the line DEVICE=DRIVE LETTER\PATH\MO.SYS /N4 (N is followed by
         number SCSI DEVICES).

  __ 8.  Add the line IFS=DRIVE LETTER\PATH\HPOFS20.IFS

  __ 9.  Save your new CONFIG.SYS file.

  __ 10. Reboot your system.

  If you are currently using the FAT file system with the optical drive, MO.SYS
  will continue to support disks formatted with FAT.  New disks can now be
  formatted either using FAT or HPOFS. To format a disk using HPOFS instead of
  FAT use the format command passing the parameter to denote the file system
  desired.  If you wish to format a disk back to FAT format you must run
  CERTIFY.EXE /ALL prior to running format.

                         Chapter 2.  Installing HPOFS with OS/2 2.x or Later 10




  For example, for HPOFS:

  +---------------------------------------------------------------------------+
  |                                                                           |
  |     FORMAT E: /FS:HPOFS                                                   |
  |                                                                           |
  +---------------------------------------------------------------------------+

  Or for example, for FAT:

  +---------------------------------------------------------------------------+
  |                                                                           |
  |    FORMAT E: /FS:FAT                                                      |
  |                                                                           |
  +---------------------------------------------------------------------------+

  The message file required by UHPOFS.DLL is FMT001.MSG.  The default
  FMT001.MSG file is the USA English version.  If you are using one of the
  other languages, such as Spanish, then copy FMTESP.MSG to FMT001.MSG.  You
  may then erase the unused FMTXXX.MSG files from your hard disk.

  Refer to IBM High Performance Optical File System Reference, for information
  about commands, device driver interface, and return codes.





































 11  HPOFS Installation Guide









  CHAPTER 3.  USING UTILITIES AND PROTOCOLS FOR HPOFS





  The utilities and protocols used by HPOFS are described in this section.


  UTILITIES

  The HPOFS utilities are described in this section and are:

  o   CERTIFYF

  o   FORMAT

  o   CHKDSK


  CERTIFYF

  This utility prepares the optical disk for the file allocation table (FAT)
  file system.  CERTIFYF is not needed for disks that are to be formatted to
  HPOFS.  It is used for disks that need to be formatted for the FAT file
  system that are currently formatted HPOFS.

  If you have media that was formatted for the HPOFS File System and you want
  to re-format it for the FAT file system, you must first run the CERTIFYF
  utility by using the /ALL parameter.  Be certain to use the /ALL parameter in
  this case, or the performance of CERTIFYF will be very slow.

  The syntax of the CERTIFYF utility is:

  CERTIFYF d: [/ALL]

  where

  D:    is the drive letter of the optical drive containing the media to be
        certified.
  /ALL  is an optional parameter that tells CERTIFYF to unconditionally write
        to every sector on the media.  All data on media will be destroyed.
        However, it will significantly reduce execution time, if the media
        contains many erased sectors (for example if reformatting media that
        was previously formatted for the HPOFS file system).

        NOTE:  The /ALL parameter WILL DESTROY ALL DATA on the media, so it
        should be used only when you are sure that the data on the media is not
        needed.

        You should not run CERTIFY on media that is formatted for the HPOFS
        File System, unless you are reformatting that media for the FAT file
        system.



  (C) Copyright IBM Corp. 1995                                               12







  FORMAT

  This utility formats disks in a specified drive to accept files either for
  the FAT file system or the HPOFS file system.  The file system format is a
  matter of user preference--however if you wish to import the formatted disks
  into a IBM 3995 optical library at any future time the disk must be formatted
  HPOFS.  In addition HPOFS has other advantages such as speed, and added
  protection for power outage situations.

  For HPOFS the basic format command is:

  +---------------------------------------------------------------------------+
  |                                                                           |
  |      FORMAT E: /FS:HPOFS                                                  |
  |                                                                           |
  +---------------------------------------------------------------------------+

  For FAT the basic format command is:

  +---------------------------------------------------------------------------+
  |                                                                           |
  |      FORMAT E: /FS:FAT                                                    |
  |                                                                           |
  +---------------------------------------------------------------------------+

  Parameters for HPOFS format include the following:

  /FS:      File System Name  /FS:HPOFS  or /FS:FAT

            NOTE:  The file system name (HPOFS) must be selected or the system
            defaults to file allocation table (FAT).

  /B:       Override rewritable file system (MO) and format the disk using
            write-once file system (WORM).

  /F:@      Filename This is a text file that you may use to include all the
            parameters which you will use in format--this is somewhat easier
            that typing a long list of command line parameters each time you
            wish to format a disk.  The file name must be in the 8.3 character
            format (no drive or path should be specified).

  /R:#      RPS ID (write-once = 1 or 257) (rewritable =2,10 or 266).  The
            default /R for MO is 10 and for WORM is 1.  Version support for MO
            media is RPS 2 but is not supported in the non-library version of
            HPOFS. All WORM formatted disks support versioning.  RPS 257 and
            RPS 266 are for mixed case support.

  /OV:@     Old volume label (not required on non-library HPOFS)

  /NV:@     New volume label (not required but may be specified by the user
            wishing to attach a volume name to disk).





  13  HPOFS Installation Guide







  /CP:#     Code Page 850, 500, 942, 944, 948.  850=ASCII(default),
            500=EBCIDIC, 942=JAPAN, 944=KOREA, 948=CHINA

  /CI:#     CI size is the control interval used on rewritable media only, that
            affects performance. The default 2048 should obtain satisfactory
            performance. If user will have large number of small files this
            number should be increased to 4096. CI sizes may be 1024, 2048,
            4096, 8192, 16348, 32768 (default is 2048).

  /?:       Displays above quick help parms.

  +---------------------------------------------------------------------------+
  |                                                                           |
  |        # = NUMBER                                                         |
  |        @ = TEXT                                                           |
  |                                                                           |
  +---------------------------------------------------------------------------+

  In general, for stand alone drives the defaults are satisfactory if you are
  using the FAT file system on OS/2.  Format Drive: /FS:HPOFS /NV:VOLLABEL.

   If you are planning on using the OS/2 HPFS file system with mixed case
  support and you are wish to use the MO portion of the file system, then an
  /R:266 is the one to choose.  This will allow copying files from the OS/2's
  HPFS file system to the HPOFS file system and preserve mixed case.

  NOTE:  HPOFS is a true case-sensitive (AIX-like) and does not support HPFS
  type case sensitivity.

  The format command senses which type of media is in the drive and formats the
  media appropriately.  There is an override option in the format program /B:
  which will format a rewritable device using the write-once file system.
  There is a valid purpose for using the write-once file system on an
  rewritable drive.  The write-once file system assures that no file is ever
  physically overwritten.  All versions of a file are maintained, however these
  versions cannot be retrieved in the stand alone mode.  The media must be
  transported to an IBM 3995 optical library for retreival of any version other
  than the latest version on the cartridge (and only if the latest version is
  not logically deleted). When using the write-once file system on rewritable
  (MO) media and you erase a file it is logically deleted.  The space on the
  disk will remain the same. Once the disk is full it will need to be
  reformatted.

  NOTE:  The HPOFS file system supports diskette drives using 1.44 media.  This
  allows you to experiment with different options for evaluation.  Do not use
  720K media because it will format it 1.44 and may be unreliable. You must use
  a 1.44 M diskette drive --this is not supported by the 2.88 diskette drive.

  The format command can accept a text file name as input.









                        Chapter 3.  Using Utilities and Protocols for HPOFS  14









  +---------------------------------------------------------------------------+
  |                                                                           |
  |       FORMAT DRIVE: /FS:HPOFS /F:MYPARMS.TXT                              |
  |                                                                           |
  +---------------------------------------------------------------------------+

  Inside the text file MYPARMS.TXT you can put any one of FORMAT's parameters
  with the exception of the ?:

  1.  Parameters in a file are text and are 1 parameter per line starting in
      the first column.

  2.  Blank lines are not allowed.

  3.  Parameters are treated as last meaningful.  If you have a parameter on
      the command line or in file more than once, the last one is used.


  Return Codes:

  o   0 - Normal completion

  o   Non Zero - FORMAT was unable to complete format.


































  15  HPOFS Installation Guide









  CHKDSK


     Checks a disk in the specified drive as to integrity of pointer chains.

    ľľľľ CHKDSK  drive >
          drive      path                           /F 
                                                            /V 
                                                            /E 
                                                            /%F
                                                            /? 
                                                            /BEEP 


  +---------------------------------------------------------------------------+
  |                                                                           |
  | WARNING: DO NOT RUN CHKDSK WHILE PERFORMING OTHER                         |
  | OPERATIONS TO THE OPTICAL DRIVE.                                          |
  |                                                                           |
  +---------------------------------------------------------------------------+

  Return codes

  o   0 - Normal completion
  o   Non Zero - CHKDSK found an error in testing of structures.


  +---------------------------------------------------------------------------+
  |                                                                           |
  | IMPORTANT:  If there is a possibility the volume                          |
  | you are using will be imported either to a system with a                  |
  | previous version of HPOFS or 3995 LAN Optical Library                     |
  | Dataserver Models 122, 121, 022, or 021, you must run                     |
  | CHKDSK after your last write operation to the cartridge.                  |
  |                                                                           |
  +---------------------------------------------------------------------------+
  +---------------------------------------------------------------------------+
  | Note: /F /E of chkdsk is implemented currently for mo portion of the file |                                                                          |
  |  system--it will not work on oblative worm cartridges, CCW worm cartridges|
  |  or on mo cartridges formatted as worm ( the /B option of format )        |
  +---------------------------------------------------------------------------+
















                        Chapter 3.  Using Utilities and Protocols for HPOFS  16









  Parameters

  o   /F - Fixes errors found on disk.

  o   /V - Verbose listing.

  o   /E - Erase, unused, unerased sectors.

  o   /%F - Allows user to reset percent full for disk.  The default value is
      95% and this option allows the user to set up to 99%.

  o   /? - Displays options.

  o   /BEEP - Test CHKDSK error tone.

      A low, short tone indicates an error.  If the error is a logical error on
      the disk, then the /F option may or may not fix the error.



  PROTOCOLS

  The HPOFS protocols are described in this section include:

  o   Name space rules
  o   Directory entry
  o   Volume rules
  o   Extented attribute support


  NAME SPACE RULES

  o   There are 254 total characters permitted in the name.

  o   The media may be formatted in either ASCII or EBCDIC.  Either ASCII or
      EBCDIC must be specified and it governs all discussion of character set
      used for volume names, file names, and others.  The actual user data is
      left as written.  and no conversion or interpretation is performed.  The
      ASCII/EBCDIC identifier may only be changed by reformatting the disk and
      a new code page identifier specified.

  o   The slash is defined as a separator character.

  o   All alpha characters will be written on the media in both uppercase and
      lowercase.

  o   The invalid file name characters are:

      -   All characters from binary 0 - 0x1F
      -   Forward slash
      -   Backward slash
      -   Left bracket  (only used to pass version information)
      -   Right bracket (only used to pass version information)
      -   <    (cont next page)


  17  HPOFS Installation Guide









      -   >
      -   "

  o   Blanks immediately preceding a dot ARE significant.

      This means that "FILE.TXT" and "FILE       .TXT" refer to different
      files.

  o   Trailing blanks are not allowed and will be truncated by the
      Dataservers's file system.

      This means that "FILE.TXT        " is the same as "FILE.TXT".

  o   Blanks elsewhere in the file are significant.

      This means that "F I L E.TXT" is not the same as "FILE.TXT".

  o   Trailing dots on component names are not valid, and the library's file
      system will discard them.

      For example, "/FOO.BAR...BLETCH.../A..B..C." becomes
      "/FOO.BAR...BLETCH/A..B..C".

  o   The component separator in a file name or subdirectory name must be a dot
      (.).  There are no restrictions on the number of components in a file
      name or path specifier.

  o   There can be no more than 254 characters between separators.  (This
      character field is informally called a "name".)

  o   Subdirectories are supported. All directory structures are hierarchical
      (all parents will exist and be defined on the media).

  o   There is an implied limit of 127 total "Subdirectories".


  DIRECTORY ENTRY

  The create time stamp will be set to a value which represents the time at
  some point of the create process.

  The modify time stamp is set to a new value when:

  o   Data is changed or added in the file.

  o   Any part of the directory, extent list, or name is changed.

      NOTE:  Access date and time stamps are not maintained by HPOFS.
      Therefore, a read-only operation will not cause a new directory entry to
      be created.






                        Chapter 3.  Using Utilities and Protocols for HPOFS  18









  VOLUME RULE

  In addition to the file-naming conventions there are additional restrictions
  on the volume name.  Characters must be uppercase letters, numbers, space, or
  the hyphen.  Volume labels may be up to 32 characters in length. This length
  may be truncated if the workstation operating system cannot handle all 32
  characters.

  If operating on rewritable media, all unused data areas will be erased during
  the format process.

  All preallocated space on rewritable media will be written with all binary
  zeros (0x0).


  EXTENTED ATTRIBUTE SUPPORT

  HPOFS has full Extended Attribute (EA) support for files.


  OS/2 AND DOS COMMAND SUPPORTED DIFFERENTLY

  Table 1 shows the commands that are supported, but the response with the
  optical library is different from other OS/2 or DOS environments.  The
  difference may be some command options, additional support (new/additional
  options) is not supported, or some option commands may return different
  information.

  +---------------------------------------------------------------------------+
  | Table 1. Restore Command                                                  |
  +---------------------+-----------------------------------------------------+
  |       COMMAND       |                         TASK                        |
  +---------------------+-----------------------------------------------------+
  |       RESTORE       | Restore from a floppy to the optical library is not |
  |                     | supported.  Restore from the optical library is     |
  |                     | supported as described in the OS/2 and DOS manuals. |
  +---------------------+-----------------------------------------------------+
  |        RENAME       | Rename is not supported for renaming of             |
  |                     | directories, but is supported for renaming of       |
  |                     | files.                                              |
  +---------------------+-----------------------------------------------------+


  UNSUPPORTED OS/2 AND DOS COMMANDS

  Table 2 on page 17 shows the five command processors from OS/2 and DOS
  workstations that are not supported.









  19  HPOFS Installation Guide









  +---------------------------------------------------------------------------+
  | Table 2. Unsupported Commands                                             |
  +---------------------+-----------------------------------------------------+
  |       COMMAND       |                         TASK                        |
  +---------------------+-----------------------------------------------------+
  |       DISKCOPY      | This command is not supported.                      |
  +---------------------+-----------------------------------------------------+
  |       DISKCOMP      | This commmand is not supported.                     |
  +---------------------+-----------------------------------------------------+
  |         SYS         | This command is not supported.                      |
  +---------------------+-----------------------------------------------------+
  |       RECOVER       | This command cannot be used on files residing on    |
  |                     | optical media.                                      |
  +---------------------+-----------------------------------------------------+










































                        Chapter 3.  Using Utilities and Protocols for HPOFS  20









  CHAPTER 4.  LOCAL AREA NETWORK ACCESS





  The IBM 3431 may be accessed over a token-ring or Ethernet local area network
  (LAN). Support is provided for LAN Server/LAN Requester and Communications
  Manager/2 (CM/2).  Refer to your Lan Server/Requester(Netbios) and/or CM/2
  (APPC) documentation for installation and access information.

  This chapter discusses installation and configuration details for
  communication between an AS/400 and IBM 3431. The Advanced Program-to-Program
  Communications (APPC) protocol allows access by applications, such as
  Workfolder Application Facility/400 (WAF/400) and Report/Data Archival and
  Retrieval System/400 (R/DARS/400) to the IBM 3431 optical drive by means of a
  token-ring or Ethernet LAN.  The APPC and APPC/HFS support described in this
  section requires that Communication Manager/2 (CM/2) be installed and that
  the IBM 3431 controller be attached to a LAN.  Instructions are provided to:

  o   Configure CM/2 for the LAN-attached controller of the drive
  o   Create a controller description on the AS/400
  o   Create a device description on the AS/400

  The APPC or APPC/HFS support for the LAN-attached IBM 3431 optical disk drive
  is provided through the OPTSRV2.EXE or HFSSRV.EXE transaction programs, which
  are invoked by the Communication Manager/2 upon request from a partner
  connection.

  Prior to configuring CM/2, follow the instructions in Chapter 2, "Installing
  HPOFS with OS/2 2.0 or Later" on page 5 to install HPOFS20.IFS and MO.SYS.
  Then, copy OPTSRV2.EXE and/or HFSSRV.EXE into the subdirectory where HPOFS is
  loaded and follow the instructions in this section to configure the IBM 3431
  with CM/2 for either a token-ring or Ethernet LAN.

  Before configuring the IBM 3431 optical drive, obtain the following system
  and network parameters:

  o   Token-ring or Ethernet Network ID

  Before configuring the AS/400, obtain the following system and network
  parameters:

  o   AS/400 local location name
  o   IBM 3431 local node name
  o   Token-ring or Ethernet network ID
  o   Token-ring or Ethernet physical LAN name
  o   IBM 3431 token-ring/Ethernet adapter address

      NOTE:  To obtain the IBM 3431 token-ring/Ethernet adapter address, enter
      the following command at a full screen prompt:





  (C) Copyright IBM Corp. 1995                                               21









  +---------------------------------------------------------------------------+
  |                                                                           |
  |        C:>TYPE C:\IBMCOM\LANTRAN.LOG                                      |
  |                                                                           |
  +---------------------------------------------------------------------------+

      The address is identified in the sentence "Adapter X is using node
      address YYYYYYYYYYYY", where X represents the adapter number connected to
      the network and YYYYYYYYYYY corresponds to the adapter address.

  The adapter address may be changed to either the universally administered or
  locally administered address with the LAN Adapter and Protocol Support (LAPS)
  program:

  __     Enter the following command at a full screen prompt:

  +---------------------------------------------------------------------------+
  |                                                                           |
  |        C:>CD IBMCOM                                                       |
  |        C:\IBMCOM> LAPS                                                    |
  |                                                                           |
  +---------------------------------------------------------------------------+

  __     Configure the appropriate adapter protocol (NETBIOS and IEEE 802.2) to
         use the universally administered or locally administered address.

         NOTE:  For optimal LAN performance, select the installed adapter and
         edit its "Receive Buffer Size" to use a buffer size of 1536 for
         Ethernet LANs, or a size of 2040 for Token-ring LANs.


  IBM 3431 LAN-ATTACHED TOKEN RING AND ETHERNET SETUP FOR AS/400

  The CM/2 Setup screen is invoked by selecting the CM/2 Setup Icon from the
  OS/2 Desktop, or by typing CMSETUP at an OS/2 prompt.

  NOTE:  The following description is based on Communications Manager/2,
  version 1.0.

  From the CMSETUP screen:

  __ 1.  Select the OK pushbutton and press Enter to display the Communication
         Manager Setup screen.

  From the Communication Manager Setup screen:

  __ 2.  Select the SETUP pushbutton and press Enter.

  From the Open Configuration screen:

  __ 3.  Select the appropriate configuration file from the Configurations menu
         or type the configuration file name in the Configuration entry field,
         if the configuration file does not exist:



  22  HPOFS Installation Guide









         __ a.  WAF3431 for a Token-Ring APPC connection

         __ b.  WAF3431E for an Ethernet APPC connection

         __ c.  HFS3431 for a Token-Ring APPC/HFS connection

         __ d.  HFS3431E for an Ethernet APPC/HFS connection

  __ 4.  Select the OK pushbutton and press Enter.

  From the OS/2 Communication Manager screen:

  __ 5.  Select the YES pushbutton and press Enter when asked whether this
         configuration file will be used for this workstation.

  From the Communication Manager Configuration Definition screen:

  __ 6.  Select the TOKEN-RING OR OTHER LAN TYPES or ETHERNET (ETHERAND)
         NETWORK from the Workstation Connection Type menu.

  __ 7.  Select APPC APIS from the Feature or Application menu.

  __ 8.  Select the CONFIGURE... pushbutton and press Enter.

  From the Communication Manager Profile List Sheet screen:

  __ 9.  Select DLC-TOKEN-RING OR OTHER LAN TYPES DLC-ETHERNET (ETHERAND)
         NETWORK from the Profile Name menu.

  __ 10. Select the CONFIGURE... pushbutton and press Enter.

  From the "Token Ring or Other LAN Types DLC Adapter Parameters" or "Ethernet
  (ETHERAND) Network DLC Adapter Parameters" screen:

  __ 11. Accept the default adapter parameters and change the following
         parameters:

         o   Send window count = 8
         o   Receive window count = 8
         o   C&SM LAN ID = network id

  __ 12. Select the OK pushbutton and press Enter.

  From the Communication Manager Profile List Sheet screen:

  __ 13. Select SNA LOCAL NODE CHARACTERISTICS from the Profile Name menu.

  __ 14. Select the CONFIGURE... pushbutton and press Enter.

  From the Local Node Characteristics screen:

  __ 15. Enter the LAN network id in the Network ID entry field.

  __ 16. Enter LU3431X in the Local node name entry field.


                                      Chapter 4.  Local Area Network Access  23









  __ 17. Select END NODE - NO NETWORK NODE SERVER in the Node type field.

  __ 18. Enter 05D 10001 in the Local node ID entry field.

         If several IBM 3431 controllers are defined to the network, the local
         node name LU3431X may already be defined and needs to be changed to
         another unique node name identifier.  The local node ID also needs to
         be changed to a unique ID, such as 05D 10002 for the second node, 05D
         10003 for the third, and so on.

  __ 19. Select the OPTIONS... pushbutton and press Enter.

  From the Local Node Options screen:

  __ 20. Enter LU3431X in the Local node alias name entry field.

         This name should match the local node name entered in the previous
         Local Node Characteristics menu.

  __ 21. Enter an optional comment.

  __ 22. Select and check ACTIVATE ATTACH MANAGER AT STARTUP.

  __ 23. Select the OK pushbutton and press Enter.

  From the Local Node Characteristics screen:

  __ 24. Select the OK pushbutton and press Enter.

  From the Communication Manager Profile List Sheet screen:

  __ 25. Select SNA CONNECTIONS from the Profile Name menu.

  __ 26. Select the CONFIGURE... pushbutton and press Enter.

  From the Connections List screen:

  __ 27. Select TO PEER NODE from the Partner type menu.

             For each IBM 3431 controller, define all partner connections.
                 Select the CREATE... pushbutton and press Enter.

                 NOTE:  If a partner does not exist, define a default partner
                 connection with a partner adapter address of 000000000000.

             From the Adapter List screen:
                 Select TOKEN-RING OR OTHER LAN TYPES or ETHERNET (ETHERAND)
                 NETWORK from the Adapter type menu.
                 Select the CONTINUE... pushbutton and press Enter.

             From the Change a Connection to a Peer Node screen:
                 Enter a link name (LINK0001, LINK0002, etc.) in the Link name
                 entry field.



  24  HPOFS Installation Guide









                 Enter the partner's Token-Ring/Ethernet address in the LAN
                 destination address entry field.
                 Enter the partner's network identifier in the Partner network
                 ID entry field.
                 Enter the partner's node name in the Partner node name entry
                 field.
                 Enter an optional comment for this partner connection in the
                 comment field.
                 Select the OK pushbutton and press Enter.

             Select the CLOSE pushbutton and press Enter.

  From the Communication Manager Profile List Sheet screen:

  __ 28. Select SNA FEATURES from the Profile Name menu.

  __ 29. Select the CONFIGURE... pushbutton and press Enter.

  From the SNA Features List screen:

  __ 30. Select MODES from the Features menu.

  __ 31. Select BLANK from the Definition menu.

  __ 32. Select the CHANGE... pushbutton and press Enter.

  From the Change a Mode Definition screen:

  __ 33. Accept the default mode parameters and change the following parameter:

         o   Check the MAXIMUM RU SIZE button.
         o   Enter a RU size of 7168.

  __ 34. Select the OK pushbutton and press Enter.

  From the SNA Features List screen:

  __ 35. Select TRANSACTION PROGRAM DEFINITIONS from the Features menu.

  __ 36. For APPC support:

             If the SAHS transaction program definition exists:
                 Select SAHS from the Definition menu.
                 Select the CHANGE... pushbutton and press Enter.
             If the SAHS transaction program definition does not exist:
                 Select the CREATE... pushbutton and press Enter.
             From the Change a Transaction Program Definition screen:
                 Enter SAHS in the Transaction Program (TP) name entry field.
                 Enter the complete path and file name where the OPTSRV2.EXE
                 transaction program is loaded in the OS/2 program path and
                 file name entry field.
                 Enter the optical drive letter, a space, and a "D" to indicate
                 that support is for an IBM 3431 optical disk drive in the
                 Program parameters string entry field.


                                      Chapter 4.  Local Area Network Access  25









  __ 37. For APPC/HFS support:

             If the HFSSRV transaction program definition exists:
                 Select HFSSRV from the Definition menu.
                 Select the CHANGE... pushbutton and press Enter.
             If the HFSSRV transaction program definition does not exist:
                 Select the CREATE... pushbutton and press Enter.
             From the Change a Transaction Program Definition screen:
                 Enter HFSSRV in the Transaction Program (TP) name entry field.
                 Enter the complete path and file name where the HFSSRV.EXE
                 transaction program is loaded in the OS/2 program path and
                 file name entry field.
                 Enter the optical drive letter, a space, and a "D" to indicate
                 that support is for an IBM 3431 optical drive in the Program
                 parameter string entry field.

  __ 38. Select the CONTINUE... pushbutton and press Enter.

  From the Change Additional TP Parameters screen:

  __ 39. Select BACKGROUND from the Presentation type field.

  __ 40. Select NON-QUEUED, ATTACH MANAGER STARTED from the Operation type
         field.

  __ 41. Select the OK pushbutton and press Enter.

  From the SNA Features List screen:

  __ 42. Select the CLOSE pushbutton and press Enter.

  From the Communication Manager Profile List Sheet screen:

  __ 43. Select the CLOSE pushbutton and press Enter.

  From the Communication Manager Configuration Definition screen:

  __ 44. Select the CLOSE pushbutton and press Enter.

  From the OS/2 Communication Manager screen:

  __ 45. If verification warnings and verification errors were found, you may
         be asked whether you want to see the messages:

         __     Select the NO pushbutton and press Enter if verification
                warnings were found.

                NOTE:  The warnings usually refer to definitions that are
                defined but not referenced and do not prohibit the use of the
                configuration.

         __     Select the YES pushbutton and press Enter if verification
                errors were found.



  26  HPOFS Installation Guide









                NOTE:  View the error messages and correct the problem.  The
                configuration file is unusable with its current settings.

  From the OS/2 Communication Manager screen:

  __ 46. When asked if you would like to return to the Communication Manager
         Configuration to change the settings:

         __     Select the NO pushbutton and press Enter if verification
                warnings were found.  Parameter settings need not be changed.

         __     Select the YES pushbutton and press Enter if verification
                errors were found.  Parameter settings need to be changed.

  From the Communication Manager Configuration screen:

  __ 47. Select the OK pushbutton to acknowledge the installation complete
         message, and press Enter.

         NOTE:  A window may pop up to ask whether the SNA resources need to be
         updated dynamically. If so, select the YES pushbutton and press Enter.

  From the Communication Manager Setup screen:

  __ 48. Select the CLOSE pushbutton and press Enter to complete the
         configuration.

  __ 49. Restart CM/2.




























                                      Chapter 4.  Local Area Network Access  27









  AS/400 LINE DESCRIPTION CONFIGURATION


  AS/400 CONTROLLER DESCRIPTION

  Sign on as a system administrator and use the CRTCTLAPPC command to create
  the controller description and press F4 to display the CREATE CTL DESC panel.
  Provide the following values and leave the remaining parameters as defaults:

  +---------------------------------------------------------------------------+
  | Table 3. CREATE CTL Panel                                                 |
  +----------------------+-----------------+----------------------------------+
  |         FIELD        |    PARAMETER    |            DESCRIPTION           |
  +----------------------+-----------------+----------------------------------+
  | CTLD:                |     LU3431X     | Controller description should    |
  |                      |                 | match the LOCAL NODE NAME of the |
  |                      |                 | IBM 3431 configuration.          |
  +----------------------+-----------------+----------------------------------+
  | RMTNETID:            |       APPN      | Remote network id should match   |
  |                      |                 | the NETWORK ID of the IBM 3431   |
  |                      |                 | configuration.                   |
  +----------------------+-----------------+----------------------------------+
  | LINKTYPE:            |       *LAN      | Link type information.           |
  +----------------------+-----------------+----------------------------------+
  | INLCNN:              |      *DIAL      | Initial connection information.  |
  +----------------------+-----------------+----------------------------------+
  | LINE:                |                 | Line information should be       |
  |                      |                 | blank.                           |
  +----------------------+-----------------+----------------------------------+
  | SWITCHED:            |       *YES      | Switch line information.         |
  +----------------------+-----------------+----------------------------------+
  | SWTLINLST:           |       APPN      | Switch line list information     |
  |                      |                 | should equal the physical name   |
  |                      |                 | of the Token-Ring/Ethernet line  |
  |                      |                 | to which the IBM 3431 and AS/400 |
  |                      |                 | are connected.                   |
  +----------------------+-----------------+----------------------------------+
  | RMTCPNAME:           |     LU3431X     | Remote control point information |
  |                      |                 | should match the above value     |
  |                      |                 | under Controller Description     |
  |                      |                 | (CTLD).                          |
  +----------------------+-----------------+----------------------------------+
  | EXCHID:              |    05D 10001    | The exchange identifier          |
  |                      |                 | information should match the     |
  |                      |                 | LOCAL NODE ID of the IBM 3431    |
  |                      |                 | configuration.                   |
  +----------------------+-----------------+----------------------------------+
  | ADPTADR:             |                 | IBM3431 Token-Ring adapter       |
  |                      |                 | address.                         |
  +----------------------+-----------------+----------------------------------+

  The following table describes those parameters that need to match when
  configuring the AS/400 and IBM 3431 for the Token-Ring/Ethernet LAN. All



  28  HPOFS Installation Guide









  values are suggestions and may not apply to the specific setup shown in
  Table 4 on page 27.

  +---------------------------------------------------------------------------+
  | Table 4. AS/400 and IBM 3431 Controller Parameters                        |
  +---------------------+---------------+---------------------+---------------+
  |        AS/400       |     AS/400    |       IBM 3431      |    IBM 3431   |
  |      PARAMETER      |     VALUE     |      PARAMETER      |     VALUE     |
  +---------------------+---------------+---------------------+---------------+
  |       RMTNETID      |      APPN     | Local Node          |      APPN     |
  |                     |               | Characteristics     |               |
  |                     |               | /Network Id         |               |
  +---------------------+---------------+---------------------+---------------+
  |      RMTCPNAME      |    LU3431X    | Local Node          |    LU3431X    |
  |                     |               | Characteristics     |               |
  |                     |               | /Local Node Name    |               |
  +---------------------+---------------+---------------------+---------------+
  |        EXCHID       |   05D 10001   | Local Node          |   05D 10001   |
  |                     |               | Characteristics     |               |
  |                     |               | /Local Node ID (in  |               |
  |                     |               | hex)                |               |
  +---------------------+---------------+---------------------+---------------+


  AS/400 DEVICE DESCRIPTION

  Use the CRTDEVAPPC command to create the device description. Press F4 to
  display the CREATE DEV DESC panel. Provide the following values and leave the
  remaining parameters as defaults:

  +---------------------------------------------------------------------------+
  | Table 5 (Page 1 of 2). CREATE DEV Panel                                   |
  +----------------------+-----------------+----------------------------------+
  |         FIELD        |    PARAMETER    |            DESCRIPTION           |
  +----------------------+-----------------+----------------------------------+
  | DEVD:                |     LU3431X     | Device description information   |
  |                      |                 | should match the LOCAL NODE NAME |
  |                      |                 | of the IBM 3431 configuration.   |
  +----------------------+-----------------+----------------------------------+
  | RMTLOCNAME:          |     LU3431X     | Remote location information      |
  |                      |                 | should match the LOCAL NODE NAME |
  |                      |                 | of the IBM 3431 configuration.   |
  +----------------------+-----------------+----------------------------------+
  | LCLOCNAME:           |      AS400X     | Location information should be   |
  |                      |                 | equal to the AS/400 name defined |
  |                      |                 | to the network.                  |
  +----------------------+-----------------+----------------------------------+
  | RMTNETID:            |       APPN      | Remote network identifier        |
  |                      |                 | information should match the     |
  |                      |                 | Network ID of the IBM 3431       |
  |                      |                 | configuration.                   |
  +----------------------+-----------------+----------------------------------+




                                      Chapter 4.  Local Area Network Access  29









  +---------------------------------------------------------------------------+
  | Table 5 (Page 2 of 2). CREATE DEV Panel                                   |
  +----------------------+-----------------+----------------------------------+
  |         FIELD        |    PARAMETER    |            DESCRIPTION           |
  +----------------------+-----------------+----------------------------------+
  | CTL:                 |     LU3431X     | Attached controller information  |
  |                      |                 | should match the name used for   |
  |                      |                 | the Controller Description       |
  |                      |                 | (CTLD).                          |
  +----------------------+-----------------+----------------------------------+
  | MODE:                |      BLANK      | Mode field should match the IBM  |
  |                      |                 | 3431 mode.                       |
  +----------------------+-----------------+----------------------------------+

  The following table describes those parameters that need to match when
  configuring the AS/400 and IBM 3431 for the Token-Ring/Ethernet LAN.  All
  values are suggestions and may not apply to the specific setup shown in
  Table 6.

  +---------------------------------------------------------------------------+
  | Table 6. AS/400 and IBM 3431 Device Parameters                            |
  +---------------------+---------------+---------------------+---------------+
  |        AS/400       |     AS/400    |       IBM 3431      |    IBM 3431   |
  |      PARAMETER      |     VALUE     |      PARAMETER      |     VALUE     |
  +---------------------+---------------+---------------------+---------------+
  |      RMTLOCNAME     |    LU3431X    | Local Node          |    LU3431X    |
  |                     |               | Characteristics     |               |
  |                     |               | /Local Node Name    |               |
  +---------------------+---------------+---------------------+---------------+
  |       RMTNETID      |      APPN     | Local Node          |      APPN     |
  |                     |               | Characteristics     |               |
  |                     |               | /Network ID         |               |
  +---------------------+---------------+---------------------+---------------+
  |         CTL         |    LU3431X    | Local Node          |    LU3431X    |
  |                     |               | Characteristics     |               |
  |                     |               | /Local Node Name    |               |
  +---------------------+---------------+---------------------+---------------+
  |         MODE        |     BLANK     | SNA Features        |     BLANK     |
  |                     |               | List/Mode           |               |
  +---------------------+---------------+---------------------+---------------+
















  30  HPOFS Installation Guide









  APPENDIX.  OBTAINING CORRECTIVE SERVICE DISKS





  The latest HPOFS corrective service disks (CSD) can be obtained by contacting
  Pamela Glenn at 1-602-799-3143.  After receiving your phone call a diskette
  with current level HPOFS and MO.SYS will be mailed to you. If you have
  questions or problems with HPOFS you may also call the above number for
  information.  I am currently working on getting a location on compuserve
  bulletin board / and pc bulletin board however this will probably be in the
  January 96 time frame.











































  (C) Copyright IBM Corp. 1995                                               31

































































  32  HPOFS Installation Guide









  GLOSSARY





  This glossary defines terms unique to this book.  If you do not find the term
  here, consult Dictionary of Computing, New York:  McGraw Hill, 1994.
     +---+                                  of devices and programs that make a
     | A |                                  data-processing system.
     +---+
                                            CPU.  Computer processing unit.
  ACCESS.  (1) To obtain the use of a
  computer resource.  (2) The use of
  an access method.  (3) The manner in         +---+
  which files or data sets are                 | D |
  referred to by the computer.                 +---+

  ALGORITHM.  An order set of               DEFAULT.  Pertaining to an
  well-defined rules for the solution       attribute, value, or option that is
  of a problem in a finite number of        assumed when none is explicitly
  steps.                                    specified.

  ALLOCATE.  To assign a resource,          DESCRIPTOR.  A word or phrase used
  such as a disk or a diskette file,        to categorize or index information.
  to perform a task.
                                            DEVICE.  A mechanical, electrical,
  AUTHORITY.  The right to access           or electronic contrivance with a
  objects, resources, or functions.         specific purpose.

                                            DIAGNOSTIC.  Pertaining to the
     +---+                                  detection and isolation of errors in
     | B |                                  programs and faults in equipment.
     +---+
                                            DISK.  Disk and media are used
  BUFFER.  A routine or storage used        interchangeably.
  to compensate for a difference in
  rate, or time of occurrence of            DISK DEFINITION STRUCTURE (DDS).
  events, when transferring data from       The DDS contains information on the
  one device to another.                    structure of the disk and is located
                                            in the DMA.

     +---+
     | C |                                     +---+
     +---+                                     | E |
                                               +---+
  COMPLY.  To complete and perform
  what is due.                              ERROR CODE.  Any type of code that
                                            defines an error, for example,
  CONFIGURATION.  (1) The manner in         symptom codes, diagnostic isolation
  which the hardware and software of        codes, and reference codes.
  an information-processing system are
  organized and interconnected.  (2)        ERROR RECOVERY PROCEDURES (ERP).
  The physical and logical arrangement      Procedures designed to aid in


  (C) Copyright IBM Corp. 1995                                               33









  isolating and, where possible, to            +---+
  recover from errors in equipment.            | K |
                                               +---+
  EXECUTE.  To perform the actions
  specified by a program or a portion       KB.  Kilobit; 1024 bits.
  of a program.
                                            KB.  Kilobyte; 1024 bytes.

     +---+                                  KG.  Kilogram; 1000 grams.
     | F |
     +---+
                                               +---+
  FAT.  File allocation table                  | L |
                                               +---+

     +---+                                  LOGICAL UNIT NUMBER (LUN).  The LUN
     | H |                                  field contains the logical address
     +---+                                  of the unit on the bus that is being
                                            addressed by this command.
  HPFS.  High Performance File System
                                            LSB.  Least significant byte.
  HPOFS.  High Performance Optical
  File System                               LUN.  See logical unit number.


                                               +---+
                                               | M |
                                               +---+

                                            MB.  Megabit; 1 048 576 bits.

                                            MB.  Megabyte; 1 048 576 bytes.

                                            MEDIA.  Media and disk are used
     +---+                                  interchangeably.
     | I |
     +---+                                  MICROCODE.  (1) One or more
                                            microinstructions.  (2) A code,
  ID.  See Identifier.                      representing the instructions of an
                                            instruction set, that is implemented
  IDENTIFIER.  A sequence of bits or        in a part of storage that is not
  characters that identifies a              program-addressable.
  program, device, controller, or
  system.                                   MO DISK.  Magneto-optic disk.

  INTERFACE.  A shared boundary             MODE.  A method of operation.
  between two functional units,
  defined by functional                     MPU.  Microprocessor unit.
  characteristics, signal
  characteristics, or other                 MS.  Milliseconds; one thousandth of
  characteristics, as appropriate.          a second.





  34  HPOFS Installation Guide









     +---+                                  by the user except under special
     | O |                                  conditions.
     +---+
                                            RETRIEVE.  To locate data in storage
  OBLIGATE.  Restricted to one              and read it so that it can be
  particularly characteristic mode of       processed, printed, or displayed.
  operation.
                                            RETRY.  The act of doing something
  ODC.  Optical disk controller.            again.

  OVERWRITE.  To write into an area of      REWRITABLE.  Pertaining to an
  storage, thereby destroying the data      optical disk that, once written to,
  previously stored in the same area.       can be rewritten.  Present
                                            technology allows only one side to
                                            be read at a time; to access the
     +---+                                  other side, the disk must be flipped
     | P |                                  over.
     +---+
                                            ROM.  See read-only memory.
  PARAMETER.  A variable that is given
  a constant value for a specified
  application and that may denote the          +---+
  application.                                 | S |
                                               +---+
  POWER ON.  To turn the power on and
  begin an orderly system operation.        SCSI.  Small-computer system
                                            interface.
  POWER-ON SELF-TEST (POST).  A series
  of diagnostic tests that are run          SECTOR.  On disk storage, an
  automatically by a device when the        addressable subdivision of a track
  power is turned on.                       used to record one block of a
                                            program or data.

     +---+
     | R |                                     +---+
     +---+                                     | U |
                                               +---+
  R/W.  Read/write.
                                            UPLOAD.  (1) To transfer programs or
  READABILITY.  Able to read easily.        data from a connected device,
                                            typically a personal computer, to a
  READ-ONLY MEMORY (ROM).  Memory in        computer with greater resources.
  which stored data cannot be modified      (2) To transfer data from a device,
                                            such as a workstation or a
                                            microcomputer, to a computer.











                                                                   Glossary  35

































































  36  HPOFS Installation Guide









  INDEX





     +---+                                     +---+
     | F |                                     | O |
     +---+                                     +---+

  features, HPOFS  1                        OS/2 2.1, installation of HPOFS  5
  file system, HPFS  1
  file system, HPOFS  1
                                               +---+
                                               | R |
     +---+                                     +---+
     | G |
     +---+                                  requirements, hardware  2
                                            requirements, software  2
  glossary  31

                                               +---+
     +---+                                     | S |
     | H |                                     +---+
     +---+
                                            software requirements  2
  hardware requirements  2
  High Performance File System  1
  High Performance Optical File
   System  1
  HPFS  1
  HPOFS  1
  HPOFS features  1


     +---+
     | I |
     +---+

  installing HPOFS  5


     +---+
     | N |
     +---+

  national language support  2









  (C) Copyright IBM Corp. 1995                                               37








                         IBM





                         Printed in U.S.A.










