=========================================================================
                 G C O S - 8  C O B O L  W O R K B E N C H

                                 v1.2.83

                              16bit RELEASE
   =========================================================================

                              UPDATE NOTES
                              ============

   TABLE OF CONTENTS
   =================

       INTRODUCTION
       MIGRATION
       ERRORS FIXED IN THIS UPDATE
       IMPROVEMENTS IN THIS UPDATE
       DOCUMENTATION CHANGES
       TIPS & HINTS
       KNOWN ERRORS
       KNOWN LIMITATIONS
       MANUAL INSTALLATION
       PROBLEM REPORTING

   INTRODUCTION
   ============

   This update diskette contains fixes to all problems and all new features
   since release v1.2.68. Previously provided update diskettes are obsolete
   and no longer required.

   MIGRATION
   =========

   You must always run G8WB-MFWB Integration after applying an update.

   ===> V1.2.83

   n/a

   ===> V1.2.82

   n/a

   ===> V1.2.81

   n/a

   ===> V1.2.80

   n/a

   ===> V1.2.79

   n/a

   ===> V1.2.78

   n/a

   ===> V1.2.77

   n/a

   ===> V1.2.76

   n/a

   ===> V1.2.75

   n/a

   ===> V1.2.74

   n/a

   ===> V1.2.73

   n/a

   ===> V1.2.72

   n/a

   ===> V1.2.71

   n/a

   ===> V1.2.70

   The structure of $G8WBFDIR\FMS has changed. During G8WB-MFWB integration
   the current FMS structure will be migrated to $G8WBFDIR\FORMS, and the
   current FMS structure will no longer be used.

   Note: The current FMS structure is NOT deleted after migration. You need
   to do this manually, once your G8WB environment is operational.

   Note: The migration is triggered by the absence of $G8WBFDIR\FORMS
   directory. If you need to re-do the migration, you should delete the
   $G8WBFDIR\FORMS directory, and re-run G8WB-MFWB integration.

   ===> V1.2.69

   n/a

   ===> V1.2.68

   o   New Release base for 16-bit environment.

   ==============
   UPDATE V1.2.83
   ==============

   Errors fixed in this update
   ---------------------------

   o   DB Load: Database load could fail with 'Record-type invalid' if
       a CRLF sequence on a UFT format file, was split when reading the
       input file (unlikely to happen).

   o   PSM: Error messages when PSM source format is wrong, i.e. use
       incorrect columns, tabulation, have been made more clear.

   o   PSM: The message '-> BLKSZ ignored' was treated as an error,
       but it is only an information message.

   o   HD8: Communication from 16-bit is restricted/changed as follows:

       HDCCIMODULE=TCP/IP|DDE|IPX|NETBIOS
           Default = NETBIOS for DOS-XM. HD8 Server MUST be running
                     NETBIOS also.
           Default = TCP/IP for Windows.
           Note: DDE is for test only - HD8 on same PC as G8WB.

       For TCP/IP a CCI.INI configuration file must be placed in the
       Windows directory, ex. C:\WINDOWS. The content of the file is
       as follows:

       [ccitcp-base]
       CCITCP2=<servername>
       NAME=<clientname>

       where <servername> designate the network name of the PC running
       CCITCP2 Registration Server.

       where <clientname> designate the network name of the PC running
       G8WB.

   Improvements in this update
   ---------------------------

   o   Verify Log: A new command may be used to verify the execution
       of G8WB commands, and log failures into an error-log file.

       Example of use:

           A command file contains a series of SCIN commands. After
           execution, it may be difficult to verify whether all SCIN
           executed correctly.

       The Verify Log command must be included in the command file -
       similar to UELOG, after each command you want to verify.

       Ex. CBT

           SCIN p1 $tpr
           VULOG $g8wbldir\w8scin.wrk
           SCIN p2 $tpr
           VULOG $g8wbldir\w8scin.wrk

       G8WB utilities will be default write a log into $g8wbldir\w8xxxx,
       where xxxx is the name of the G8WB command. Alternatively you
       may direct the log to another file via =log-file argument.

       The Verify Log command will examine the given log file and determine
       whether the command was executed without errors, and write an
       exception message to an error log file. The content of the log
       file will also be included in the error log file. The default
       error log ile is $g8wbldir\LERROR.LOG, however error log file may
       be specified in the VULOG command.

       Ex. CBT

           SCIN p1 $tpr
           VULOG $g8wbldir\w8scin.wrk $tpr\my.log

       The error log file may be cleared as follows:

           VULOG CLEAR
           VULOG CLEAR $tpr\my.log

   o   Source Import: Import of a single source - where import file
       contains only source (no APPEND and *END* directives), is now
       possible from command line, ex.

           XM WB W8 p1. $tpr umc/source/p1 [...]

       The presence of a GCOS cata-file-string trigger import of
       single source.

   o   Source Import: _Classify <type> now support following source
       types:

           TPR
           PROGRAM
           COBOL-74
           COBOL-85
           COBOL-SQL
           TPR-74
           TPR-85
           TPR-SQL
           PROGRAM-74
           PROGRAM-85
           PROGRAM-SQL

       The source type is documented in the program source as follows:

           *set>g8wb COPY P1.CPM
           *set>g8wb TPR COBOL-74

       and will not be removed during export.

       Although the source type cannot be used directly to control
       checking (CHAR or GUI), it makes it visible. The TPR and PROGRAM
       source types are used by G8WB Preprocessor to restrict some
       syntax depending on source type.

   o   BCF: A mask using file extension C74, C85 and CSQ will now
       be processed as follows:

       - CBL used instead of C74, C85 or CSQ to scan for files
       - consult classify information within CBL for COBOL dialect

       Ex.

           XM WB W8 BCF *.C85 check

           build CHECK.CBT from CHECK.SCB for all CBL files in current
           directory with classify type COBOL-85

   o   Source Checkin: The '_Compile [type]' argument may now
       be specified without type. The source type is then picked up
       from classify information in the source. If no classify information
       is present, CBL74 is used as default.

   o   Source Import: The '.. Imported G8WB ...' comment line will now
       include '... by userid ...' if USERID is set in environment.

   o   Copy Import: The '.. Imported G8WB ...' comment line will now
       include '... by userid ...' if USERID is set in environment.

   o   Create Source: The '.. Created G8WB ...' comment line will now
       include '... by userid ...' if USERID is set in environment.

   o   Create Copy: The '.. Created G8WB ...' comment line will now
       include '... by userid ...' if USERID is set in environment.

   o   Source Checkin: The '... Imported/Created G8WB ...' comment line
       is now changed to '... Updated G8WB ...' during checkin. Also
       comment line will now include '... by userid ...' if USERID is
       set in environment.

   o   Copy Checkin: The '... Imported/Created G8WB ...' comment line
       is now changed to '... Updated G8WB ...' during checkin. Also
       comment line will now include '... by userid ...' if USERID is
       set in environment.

   o   Source Checkout: The lock information will now include '... by
       userid' if USERID is set in environment.

   o   Copy Checkout: The lock information will now include '... by
       userid' if USERID is set in environment.

   ==============
   UPDATE V1.2.82
   ==============

   Errors fixed in this update
   ---------------------------

   o   IDS-II: A 'Connect <record> TO <set>', where no <set> currency
       had been established, would cause IDS-II to fail (Database
       Corrupt abort), instead of giving an exception.

   o   DIMS8: Copy Form function did not work (locked), if the form was
       checked out.

   o   DIMS8: Save and Generate function did not work for a Storage
       Definition (SD), when it was checked out.

   o   COBOL: When using COMP-REDEFINE-ANALYZER, the first 01-structure
       in Working-Storage would be considered a redefine of the last FD.
       This could cause incorrect flagging.

   o   COBOL: When first Procedure Division paragraph (no Declaratives)
       was in a COPY, the following Section would incorrectly be flagged
       (8073-Missing section header at beginning of procedure division).        ure division

   o   Source Create: When registrering a new program, and the source
       file is not in the reference directory, G8WB will now copy the
       source file to the reference directory, register the new program
       and delete the "input" source file.

   o   DIMS8: The command for deletion of SD(s) was missing. The command
       may be invoked as follows:

           XM WB W8 FSDDEL storage-name|storage-mask [-force]

       Note: For storage-mask a confirmation prompt is given, unless
       the -Force argument is present.

   o   DIMS8: The command for deletion of TD(s) was missing. The command
       may be invoked as follows:

           XM WB W8 FTDDEL transaction-name|transaction-mask [-force]

       Note: For transaction-mask a confirmation prompt is given, unless
       the -Force argument is present.

   o   DIMS8: When migrating from V1.2.69 or prior, the migration
       of SD's to the new forms structure would not be correct.

   Improvements in this update
   ---------------------------

   o   Source Import: An Index file will now be created during import.
       The Index file is placed with the Import file with the extension
       XSI (same name as Import file). The Index file contains a list
       of all source files imported - one entry per line. The Index file
       may be used as input to Build Command File utility.

   o   Create Source: The '_Compile <type>' argument may now be specified
       for create source - like Source Checkin. When specified, the
       program will be checked and generated to GNT format, and if the
       source file is not in the reference directory, all 'work' files
       will be deleted also. Ex. command syntax

           XM WB W8 SCRE P1 $batch _C CBL74

   o   Copy Create: A new copy may registered from an existing - like
       create source, provided no mapping is required (max. 8 chars).
       If the copy file is not in the reference directory, G8WB will
       now copy the file to the reference directory, register the
       new copy and delete the "input" copy file.

   ==============
   UPDATE V1.2.81
   ==============

   o   Tips & Hints has been updated, ref. below.

   Errors fixed in this update
   ---------------------------

   o   Source Checkin: G8WB will now verify the reference directory for
       presence of LCK file during checkin. If it fails to find the LCK
       file, ex. if the reference directory is wrong or non existing,
       and error message is given.

   o   Source Create: When specifying a reference directory (source
       not in current directory), G8WB would incorrectly create a dummy
       source in current directory, even if a program file was present
       in the reference directory.

   o   Create/Import Copy: New copies could require an update of the
       COPYMAP.CFG. If the COPYMAP.CFG was locked, the function would fail.
       Utilities will now retry (3-5 minutes max) until COPYMAP.CFG becomes
       available for update.

       Note: When viewing COPYMAP.CFG in the Editor, the file is locked
       for update. Care should be taken when browsing/changing the
       COPYMAP.CFG file for an extended period.

   o   DS Generate: Some 'large' subschemas could cause the DS Generate to
       fail during import of the generated Dialog System screen sets. As
       a result, Record Panels could not be used for the subschema.

   o   COBOL: "NAME" has been removed as a reserved word for COBOL-74 and
       COBOL-85 source types.

   o   COBOL: An invalid value in column 7 could pass undetected - not
       flagged as incorrect, if the verb just in from was preprocessed
       by G8WB.

   o   Forms: When exporting forms, the Confirm = Yes setting was ignored.

   o   FORMAT: G8WB will update the text-length of output CD for each send
       operation. When sending multiple Format forms this could lead to a
       send failure - status 50 text-length > send-argument. Text-length is
       new reset to 1 after each Format send operation.

   o   TPFF: Screen-painter would incorrectly allow an Array with an
       Array. This would cause a loop when generating the form.

   o   COBOL: Non-paragraph coding in section A - column 8-11, could be
       flagged with warning or error (8521-Period missing at the verb).

   o   COBOL: A literal continuation line in Procedure Division was
       incorrectly flagged (8521-Period missing at the verb).

   o   COBOL: When first Procedure Division paragraph (excluding Declaratives)
       was in a COPY, the following Section would incorrectly be flagged
       (8073-Missing section header at beginning of procedure division).        ure division

   o   Q2UT: The Print function did not work. It is now equivalent to the
       Dump function.

   o   FORMAT: Multiple receives would fail, because the input buffer
       was emptied (like a standard TP8 receive). Input buffer is now
       kept and each receive will be processed with original input
       buffer.

   o   FORMAT: The command was incorrectly stripped from the receive
       buffer and incorrect results would occur if the command field
       was defined on the form (starting TX in forms mode).

   o   TP8: When using a fixed command size - MAX_COMMAND_NAME_SIZE:n,
       system commands ($term etc.) could fail.

   o   COBOL: A section name < 3 characters would cause an incorrect
       warning to be given (8521-Period missing at the verb).

   o   COBOL: A literal continuation line followed by a new verb on the
       same line would cause incorrect flagging (first character of verb
       was lost).

   Improvements in this update
   ---------------------------

   o   COBOL-85: The use of NULL with DBK data items conflict with use of
       NULL with pointer data items, and G8WB will by default assume NULL
       is related to a pointer data item for COBOL-85 (COBOL-74 does not
       have this conflict). In order to handle NULL with DBK data items,
       G8WB directives are required in the source, ex.

       01  ws-pointer pointer.
       01  ws-dbk     dbk.

           set ws-pointer to null
      *w8prep alt
           set ws-dbk to null
      *w8prep on

      A new preprocessor directive (PREP.CFG) may be used to change the
      default behavior.

           DBK-NULL : ON ; OFF(default)/ON

      When DBK-NULL setting is ON, use of NULL with pointer data items
      needs G8WB directives insetad, ex.


       01  ws-pointer pointer.
       01  ws-dbk     dbk.

      *w8prep alt
           set ws-pointer to null
      *w8prep on
           set ws-dbk to null

   o   Forms: When FORMS-CHECKOUT-REQ:ON is set, following functions are
       disabled:

       Import
       Export
       Checkout using a mask

   o   Forms: When FORMS-CHECKOUT-REQ:OFF is set, you are able to Cancel
       a checkout (done via Checkin), even if the form cannot be found
       in current USERDIR structure.

       Note: This may be used to clean-up a locked form, when the USERDIR
       structure is somehow lost.

   ==============
   UPDATE V1.2.80
   ==============

   Errors fixed in this update
   ---------------------------

   o   MFWB Integration: The location of COBOL\LBR and \COBOL\EXEDLL was
       determined by scanning $COBDIR for certain files. This scanning
       could fail if the COBDIR setting was very long (>114 chars).
       G8WBMFWB has been changed so you are prompted for a path, if
       searching via $COBDIR should fail.

   o   IIDS: Use of REPEAT within a command file would cause return to
       interactive input mode, and the remainder of the command file to
       be ignored. An abort would occur also, when IIDS was launched
       as a command.

   o   IDS-II: 'Initialize $$LOCAL Server' did not work correctly.

   o   GUI Batching: 'Run' within 'Batching' did not work correctly.

   o   TP8: A call ".FREER" followed by a call to ".FREE" or ".SLEEP" or
       equivalent VMPS service calls, should cancel ".FREER". G8WB has
       been changed to be compatible with GCOS 8.

   o   TP8: Implicit send with a text length greater > 2400 would fail
       with status = "01", possibly followed by an X15 abort. Implicit
       send will now, like explicit send, use the OUTPUT_MSG-SIZE setting
       in TP8.CFG to determine maximum text length (maximum 6144).

   Improvements in this update
   ---------------------------

   o   IIDS: Output from Interactive IDS-II is now written to
       $g8wbldir\BATCH.LOG. For command processing, output may be
       redirected, ex.

           WB W8 IIDS <subschema> FILE <script> =<outputfile>

   o   IIDS: Output from Dynamic Debugger is now written to TP or
       Batch Journal.

   o   HD8: Host Distribution 8 is now supported. HD8 is a primarily a
       replacement/enhancement for DISPATCH8 and TELEX8. HD8 is enabled
       through a new setting for PRINT-SOFTWARE in Defaults Configuration.

       [G8WB-DEFAULTS]
       PRINT-SOFTWARE        : HD8     ; DISPATCH8
                                       ; HD8
                                       ; SAFE
                                       ; NONE
                                       ; Other = Name of own Program

       The DISPATCH8 API's D8D8I and D8D8BI will route print to HD8 when
       enabled, and TELEX8 API's will route messages to HD8 when enabled.

       G8WB will interface with a test or production version of HD8
       dependent on your setup. The following environment setting may
       be used to control the HD8 interface used by G8WB.

       HDPUB=HDCli|<name>
           Default = HDCli. <name> of the HD8 Distribution Server.
       HDSYSTEM=<systemname>
           Default = DK. Used for collection of mail.
       HDDEBUG=OFF|ON
           Default = OFF. ON trigger write of HD8 interface information
           on the TP or Batch Journal.
       HDCCIDEBUG=OFF|ON
           Default = OFF. ON trigger write of detailed CCI information
           on seperate CCI.LOG file.
       HDCCIMODULE=TCP/IP|DDE|IPX|NETBIOS
           Default = TCP/IP. Communication protocol for HD8 interface.
           Note: DDE is for test only - HD8 on same PC as G8WB.
       CCITPC2=<computer>
           No Default. <computer> designate where CCITCP2 Registration
           Server is running. Only required for TCP/IP.

   o   Installation: Uninstall procedure has been changed as follows:

       a) G8WB product is now installed under either Server, Workstation
          or Single-User label, allowing partial uninstallation.
       b) Registry (and environment) settings are left unchanged by
          uninstaller.

   o   MFWB Integration: Migrate files - used during migration to v1.2.68
       from a previous version, are now available as separate files.
       Previously these files were overridden by the latest update. The
       migrate files are relevant if you need to integrate G8WB again,
       after installing a fresh MFWB. Refer. 'MANUAL INSTALLATION' for
       details.

   ==============
   UPDATE V1.2.79
   ==============

   Errors fixed in this update
   ---------------------------

   o   TP8: Linkage argument check for LID-Storage would fail (abort
       reason LDSSiz) for COBOL-85 TPR's, if no LID-storage argument was
       present and DEFAULTBYTE setting other than 000 was configured.

   o   Interactive IDS-II: For a large subschema ( more than 500 fields )
       IIDS could abort while accessing a record panel (generated with
       DS-Generate). If you experience this problem, you need to run
       DS-Generate again to remove this problem.

   o   DBWFL: The generated nnWDBU (unload) and nnWDBL (load) programs
       did not work if SIGN-EBCDIC:ON was specified in Database Confi-
       guration (DBMS.CFG).

   o   DBWFLM: Migrate generation would lead to errors in nnWDBL load
       program, if records with Location-mode DIRECT was present.

   Improvements in this update
   ---------------------------

   o   Preprocessor: GNT-DELETE will now look for GNT file to delete in
       both source directory (CBL) and COBIDY directory (when COBIDY
       directive is used>.

   o   DIMS8: New TX-storage verify feature has been implemented.

       New service calls:

           *> Set TX-storage identifier in last 8 bytes of tx-storage
           CALL ".STXID" using status-size
                               dims-tx-storage

              *> Status-size = size of TX-storage in bytes (COMP-6)

           *> Verify TX-storage identifier
           CALL ".VTXID" using status-size
                               dims-tx-storage
           if status-size = 0
              *> Identifier lost from TX-storage
           else
              *> Identifier found OK

           Note: Identifier consist of a constant (DIMS) plus TX
           Serial number, and verify will fail if either constant is
           missing or TX Serial number has changed.

       New site option (in DIMS8.CFG):

           [CONFIGURATION]
           SITE-OPTION-45 : 1 ; 1=Setup TX-storage identifier

           Note: Automatic call of .STXID at start of a new TX.

   o   DIMS8: Password change calculation routine has been changed for
       Year 2000 compatibility.

   ==============
   UPDATE V1.2.78
   ==============

   Errors fixed in this update
   ---------------------------

   o   COBOL: When using REDEFINES for an 01-level within a 'BLOCK n IS
       identifier-1 THRU identifier-2', a syntax error was given.

   o   COBOL: ALTER verb was not allowed as default for GCOS-8 compile
       types within GUI environment.

   Improvements in this update
   ---------------------------

   o   G8WFL: Progress indication (%) is now given.

   o   New Database Migration feature - ONLY relevant if you need to
       exchange databases between v1.1.xx and v1.2.xx.

       Generate Migration
       ------------------

       This new activity must be performed for the database you need
       to exchange. The activity may be launched either with ALT-F5
       Generate migrate in the Schema menu (CHAR mode), or through
       a new WB command:


           WB W8 DBWFLM subschema

       The subschema must be the same as you use for unload/load under
       v1.1.xx.

       You need to specify the location of V1.1.xx, since Generate Migrate
       will read the V1.1.xx subschema file. Include an environment setting
       as follows:

           SET G8WBGV11=<path>

       Generate Migrate will create three copy files under $G8WBDDIR\SCHEMA

           nnRECORD.000 (record descriptions)
           nnMOVEUL.000 (unload logic)
           nnMOVELN.000 (load logic)

           where nn = schema number (implied through subschema)

       Re-generate Unload/Load programs
       --------------------------------

       Next the Unload/Load programs must be re-generated. The Migrate
       copies (ref. above) will be recognized, and Unload/Load programs
       with capability to handle V1.1.xx format files will be generated.

       Unload database V1.1.xx
       -----------------------

       Use the nnHDBU.cbl program to unload the whole or parts of the
       database.

       Load database V1.2.xx
       ---------------------

       Use Load Database function to load with the unload file from
       V1.1.xx.

       Unload database V1.2.xx
       -----------------------

       Use Unload Database function to unload the whole or parts of the
       database. A new option 'Migrate' may be used to obtain an
       unload file in V1.1.xx format. The new option may be specified
       in the WB command also, ex:

           WB W8 DBUNLOAD class ufile _M

       Load database V1.1.xx
       ---------------------

       Use nnWDBL.CBL program to load with the unload file from V1.2.xx.

       Note: GCOS8-DBK-ALLOCATION:OFF must be specified in DBMS.CFG, if
       you exchange databases with V1.1.xx.

   ==============
   UPDATE V1.2.77
   ==============

   Errors fixed in this update
   ---------------------------

   o   DIMS8: Checkout did not work correctly for forms with a
       language-code (default language was checked out instead).

   o   Forms: Create of a new form (TPFF, FORMAT, DIMS8) did not
       work correctly.

   o   COBOL: 'IF identifier' syntax, where identifier needed pre-
       processing (switch-name, underscore etc.), was not handled
       correctly if NO sub-schema section was present.

   o   COBOL: Preprocessing of COPY syntax could lead to confusing
       flagging (Period missing), if the path for the copy file
       exceeded 57 characters. A G8WB preprocessor error message
       is now given:

           E-8074 COPY File-path too long

       Recovery: Change directory for COPY library so the full
       (expanded) path does not exceed 57 characters.

   o   SOLD+ Barmenia: Refer to SOLD+ Notes for details.

   o   SOLD+ Debeka: Refer to SOLD+ Notes for details.

   Improvements in this update
   ---------------------------

   o   PSM: Parametic Sort/Merge execution is now supported through
       'Run PSM' function in Batch Support (CHAR and GUI).

       The PSM source - with or without JCL, is read, syntax checked
       and execution of Sort or Merge operation is performed accordingly.
       The default file-extension for the PSM-file is PSM.

       File mapping is using standard and/or configured file-codes for
       input and output, however, the name of the PSM-file is used as
       prefix for the file-code to qualify the file.

       Ex. PSM-file is named TEST.PSM

           TESTSA is input file
           TESTSZ is output file

       Note: Generic file mapping (no program-name) syntax must be used.

       Limitation: Extract directive is not implemented.

       WB Command-line
       ---------------

          PSME PSM-file [_List-source]

   ==============
   UPDATE V1.2.76
   ==============

   Errors fixed in this update
   ---------------------------

   o   IDS-II: The DB exception 05200 (content of data item invalid)
       would occur during a GET, when a CHAR field was defined longer
       in schema than in subschema (remainder of schema field was not
       initialized to spaces during STORE/MODIFY).

   Improvements in this update
   ---------------------------

   o   SOLD+ Barmenia: Refer to SOLD+ Notes for details.

   ==============
   UPDATE V1.2.75
   ==============

   o   Known Limitations has been updated, ref. below.

   o   Known Errors has been updated, ref. below.

   Errors fixed in this update
   ---------------------------

   o   IDS-II: When processing set selection (CALC) and the owner
       record is not within same area as the target member, retrieval
       of the owner would fail and cause the db-exception 1502400.

   o   COBOL-85: CALL syntax with 'USING LENGTH OF identifier' was
       not handled correctly.

   o   COBOL-74/TP8: Standard TP copies from DMIV-TP were used, even
       when TP8 was configured as TP-MONITOR.

   o   COBOL: Missing period handling was not correct when:
              - a paragraph label was followed by a COPY
              - the first non-comment line within the copy was
                a paragrah label

   o   COBOL-85: Missing period handling for 'end of verb' would flag
       any word starting in column 8-11, if the preceeding line
       was not terminated with a period. This has been changed, so a
       word = verb-keyword (ex. MOVE) will be flagged with a warning
       only.

   Improvements in this update
   ---------------------------

   o   COBOL: When a COBOL-85 reserved word is used in a COBOL-74
       program (or an MF-COBOL reserved word), you need to 'remove'
       the reserved word to avoid error flagging. This can either
       be done with an in-source directive:

           *set>MFWB remove"function"

       or by placing 'remove"function"' in one of the site DIR files
       under $G8WBDIR\MFI.

       If, however, the reserved word is defined in a G8WB preprocessor
       table file, then you may still experience error flagging, ex.
       function would be flagged a 'COBOL-85 syntax'.

       Following new directive may be used to trigger 'remove' both
       towards G8WB preprocessor and MF-COBOL.

           *set>G8WB remove:function

       The new directive(s) may either be placed in-source, or in the
       DEFAULT-SECTION of Preprocessor configuration (PREP.CFG).

           REMOVE  : function
           REMOVE  : "evaluate"

   ==============
   UPDATE V1.2.74
   ==============

   Errors fixed in this update
   ---------------------------

   o   SOLD+ Debeka: Refer to SOLD+ Notes for details.

   o   COBOL: 'IF ALL "-" = ...' was treated as IDS-II DML, and
       incorrectly flagged.

   o   COBOL: 'ACCEPT ... FROM DAY-OF-WEEK' was treated as IDS-II DML,
       and incorrectly flagged.

   o   Schema: If a new Area was added to an existing schema, IDS-II
       run-time tables would have an incorrect Area counter. When a
       generic READY was issued, a 1309300 execption would occur.
       Recovery: Re-validate (no translate) the schema.

   o   DBWFL: Generation of database unload/load programs would loop,
       if a record was member of more than 10 sets. This limit has been
       removed, and record tables will now dynamically adjust to the
       largest membership count within the schema.

   o   DBWFL: Database load program will now apply character-set-adjust
       for UFT unload files (for non-UFT files this is done in G8WFL).

   o   DBWFL: Database load program will now accept both LF, CR and CRLF
       as record delimiter for UFT unload files.

   o   DKU71XXE: Field with Transmittable and Protect attribute would
       not be updated, if the application use HT in forms mode to
       position in the fields.

   o   DKU71XXE: Field with Transmittable and Protect attribute would
       not be returned to the application.

   Improvements in this update
   ---------------------------

   o   SOLD+ Debeka: Refer to SOLD+ Notes for details.

   ==============
   UPDATE V1.2.73
   ==============

   o   Known Limitations has been updated, ref. below.

   Errors fixed in this update
   ---------------------------

   o   G8WBMFWB: If G8WBUPD.ODF was imported and the file was empty,
       GUI Organisor would loop. The file is now checked for empty and
       import suppressed if so.

   o   GUI IDS-II Tools: After exit from schema and subschema validation,
       an error message occurred (no effect on validation).

   o   COBOL-85: Missing period is now flagged as an error for COBOL-85
       to be GCOS compatible.

           8503-S Missing period end of section
           8504-S Missing period end of level
           8521-S Missing period end of verb

   o   Export: When exporting Copy or Source an abort could occur after
       the result window had been presented (GUI only).

   o   TP/IIDS: When launching IIDS from TP Escape menu, the system
       would abort and lock the TP journal (GUI only).

   o   TSS/DAC: The DAC screen is now saved and re-shown after each
       operation. This technique is used to protect the DAC screen
       against other output, i.e. Dynamic Debugger.

   o   TSS/DAC: 'DISPLAY SPACES' syntax was flagged.

   o   TSS/DAC: Literal value for a DISPLAY would be changed to upper-
       case.

   o   TSS/DAC: After each DISPLAY, a CR-LF sequence is now sent.

   o   TSS/DAC: The last typed character was truncated for ACCEPT.

   o   VIP77XXE: Blink and Blank characters are now shown (previously
       not shown) on screen, and passed to application.

   o   DKU71XXE: Blink and Blank character are now shown and passed to
       application in VIP mode.

   o   DKU71XXE: No Space Suppresion is now done.

   o   TPFF: When DKU71XXE is configured for TERMINAL-EMULATION, TPFF
       will now change to VIP78XXE automatically (DKU71XXE not supported
       for TPFF).

   Improvements in this update
   ---------------------------

   o   TP: Command configuration is now documented in the TP journal.

   ==============
   UPDATE V1.2.72
   ==============

   Errors fixed in this update
   ---------------------------

   o   SOLD+: The 3965 Master record unload was incomplete and date
       time stamp on SOLD forms would be missing (or partially missing).

       Note: Please refer to migration procedures for details on
       fixing the problem.

   o   Schema: Validation of schema would fail due to a missing file
       (W8VSCH.G02) from G8WB software library.

   o   IIDS: Update of Numeric Display fields via Record Panels did
       not work correctly.

   o   G8WFL: When using a mask the record length would be truncated
       to 3 digits.

   o   G8WFL: Conversion of UFAS Relative files did not work correctly.

   o   Schema: The syntax 'RECORD ... LOCATION DIRECT field' would lead
       to duplicate fields in the UWA - a parameter with the same name
       was incorrectly generated.

   o   Schema: Calculation of MINK/MAXK for areas was based on the
       sequence of area definition in the DDL, and could thus lead
       to difference in DBK allocation, if the sequence in DMCL was
       different. This has been changed so sequence in DMCL is used
       for MINK/MAXK calculation.

       Note: If DMCL is not given, then a default allocation for each
       area is assigned, and MINK/MAXK is calculated in ascending
       area name seuqence.

   o   G8WFL: Conversion of GFRC files did not work correctly.

   o   G8WFL: G8M and G8P file extension were not default for mask and
       profile files (saved without extension).

   o   Batch Support: SYSOUT buttom was not enabled, even if a SYSOUT
       file was present.

   o   TPFF: Generated copies now support a form name of up to seven
       characters (previously six).

   o   GUI Batch Support: 'Convert Native' did not launch MF File Converter.

   o   GUI: The 'Save As' function in browse result window did not
       work.

   Improvements in this update
   ---------------------------

   o   Overpunch Sign: G8WB by default use the Micro Focus standard
       SIGN"ASCII". This standard is not compatible with GCOS, and
       GCOS files with overpunch would have to be converted with a
       mask to adapt fields with overpunch sign.

       Micro Focus also support the standard SIGN"EBCDIC" and this
       standard is compatible with GCOS, however G8WB does use this
       as standard for historical reasons.

       SIGN"EBCDIC" may now be made default for G8WB, so overpunch
       sign fields need not be adapted via G8WFL (and a mask). If
       default is changed, this will impact all fields with overpunch
       sign (files, subschema uwa and other fields), and it is impor-
       tant that you ensure all components use the same default.

       A new option in Preprocessor Configuration (PREP.CFG) under
       DEFAULT-SECTION may be used to change the default overpunch
       sign:

       [DEFAULT-SECTION]
       SIGN-EBCDIC           : ON        ; OFF/ON

       This setting will ensure programs are checked with SIGN"EBCDIC"
       as default.

       A new option in Database Configuration (DBMS.CFG) under
       DEFAULT-SECTION may be used to change the default overpunch
       sign:

       [DEFAULT-SECTION]
       SIGN-EBCDIC           : ON        ; OFF/ON

       This setting is used by IDS-II to determine how overpunch
       sign fields should be setup/handled from the application
       program.

       This setting is also used by G8WFL conversion utility to
       determine how overpunch sign fields should be converted
       (when handled through a mask).

   o   SOLD+: New feature for Import/Checkin of SOLD+ Form and PDA
       entities. Refer to SOLD+ documentation for further details.

   o   TSS/DAC: G8WB now support GCOS 'Terminal Support Subroutine', a
       facility to interact with a terminal from a TSS or DAC program.
       This support is available to 'Batch' programs within G8WB.

       Subroutine support
       ------------------

       TSACC   -   Accept input message
       TSDSP   -   Buffered output
       TSDSPI  -   Immediate send of output
       TSDSPN  -   Output followed by input
       .TSDED  -   Count message line feed (ignored)
       .TSDNE  -   Do not count message line feed (ignored)

       Note: Output to terminal is presented ASIS - no scroll control.

       ACCEPT/DISPLAY support
       ----------------------

       GCOS will allow ACCEPT/DISPLAY to be redirected to DAC terminal
       I/O through the ON3 run-time switch. This technique represents
       an alternative to TSACC/TSDSP subroutines, or as a suplement to
       these (both techniques allowed simultaniously).

       G8WB provides a similar functionality for ACCEPT/DISPLAY, however
       the redirect must be specified at time of Check instead of run-
       time. A new directive under DEFAULT-SECTION in G8WB Preprocessor
       Configuration file may be used to trigger redirection:

           [DEFAULT-SECTION]
           DAC-ON3            : ON   ; Redirect ACCEPT/DISPLAY (OFF/ON)

       Note: Since redirection will apply only to some programs, inline
       directives in the program source is flexible, ex.

           *set>g8wb dac-on3:on
            identification division.

       Limitation: For ACCEPT only one identifier is allowed. For DISPLAY
       only identifier(s) with usage display will work correctly. For
       DISPLAY literals are supported, however following limitations
       apply: 1) Ascii-literal cannot be mixed with a normal literal, ex.
       ""033"N"" is not allowed, ""33"" "N" is allowed. 2) Literal
       length is limited to 28 characters and line continuation is not
       allowed.

       Terminal support
       ----------------

       Terminal emulation is controlled through TERMINAL-EMULATION
       setting under G8WB-DEFAULTS in the G8WB Defaults Configuration
       file (G8WB.CFG) - like TP8.

       Trace
       -----

       A new configuration option under G8WB-TRACE in the G8WB Defaults
       Configuration file (G8WB.CFG), may be used to enable a trace of
       terminal activity (similar to TP8 BIBO format).

         [G8WB-TRACE]
         DAC-COMM-DETAIL        : ON             ; Trace DAC details

       Note: The trace is written to $g8wbldir\DAC.LOG.

   ==============
   UPDATE V1.2.71
   ==============

   Errors fixed in this update
   ---------------------------

   o   IDS-II: A missing copy would cause checking errors for 'FIND db-key'
       syntax.

   o   Forms: The program W8FCLEAR (special for clear of forms library)
       was not updated in v1.2.70.

   o   COBOL: "EOS" has been removed as a reserved word for COBOL-74 and
       COBOL-85 source types.

   ==============
   UPDATE V1.2.70
   ==============

   Errors fixed in this update
   ---------------------------

   o   COPY: GCOS allow partial word replace when the replacing argument
       is a literal, ex.

           COPY something REPLACING "YYY" BY PRG1A.

           01    "YYY"-MAIN.
             05  "YYY"-field-1 PIC 9.

       G8WB has been changed to allow similar partial replacement, however
       this replacement is NOT limited to prefix only.

   o   IDS-II: FIND PRIOR ... WITHIN <realm> did work correctly when
       DBK's were not linear (GCOS DBK allocation mode or non-allocated
       DBK's prior to current DBK).

   o   IDS-II: Re-sorting within a set after a MODIFY <record>|<field>
       INCLUDING did not work correctly (sorting based on old and not
       new values).

   o   IDS-II: Sorting of DUPLICATES FIRST within a set would be
       incorrect if the current record at time of STORE was a
       duplicate (inserted prior to current record and not first).

   o   IDS-II: FIND number <record> WITHIN <set> did not work correctly
       if multiple members were present (number used without regard to
       record type).

   o   IDS-II: FIND number|identifier ... WITHIN <set>|<realm> did not
       work correctly for negative values.

   o   Interactive IDS-II: The DML aid did not handle a negative integer
       correctly.

   o   IDS-II Schema: Delete of schema from CHAR menu did not ask for
       confirmation (Yes/No), and a schema could not be deleted.

   o   IDS-II Subschema: Delete of subschema from CHAR menu did not work
       correctly.

   o   IDS-II Schema: The syntax 'BY CALC_KEY EQUAL TO field_1 ...' in
       set selection clause for schema DDL, was not handled correctly if
       more than one field was specified (E-0071 error).

   o   TPFF: Processing of Image or Vector could result in an A7 status
       (bad format), if either were crossing a segment boundary (STAR
       T30036).

   Improvements in this update
   ---------------------------

   o   Forms: A new Check-in/out feature - like Source/Copy, is now
       available for Forms entities.

       General
       -------

       Forms Check-in/out feature is using $USERDIR setting similar to
       Source/Copy, and $USERDIR (personal or project) setting thus
       define where checked out entities are kept.

       A new $USERID setting may be used to document WHO did various
       Forms operations, ex.

           - create
           - change
           - import
           - export
           - checkout

       'Unknown' is used if no $USERID setting is current.

       Checkout
       --------

       Forms entities are checked out to $USERDIR\UFORMS and locked in
       the $G8WBFDIR\FORMS directory. Checked out forms entities are
       used during checking (TPFF etc.) or execution (DIMS8).

       Note: Parallel checkout is NOT allowed - locked until checkin or
       cancelled.

       Checkin
       -------

       Forms entities are checked in from $USERDIR\UFORMS to $G8WBFDIR\
       FORMS directory, unlocked and removed from $USERDIR\UFORMS.

       Import
       ------

       Forms entities are imported into $G8WBFDIR\FORMS and registered
       for automatic export. Override check is applied - changed since
       import/export or checked out.

       Export
       ------

       'Changed' forms entities are exported from $G8WBFDIR\FORMS.

       Administration
       --------------

       Check-in/Out feature may be configured as optional(default) or
       mandatory. In mandatory mode, the developer cannot change forms
       entities directly under $G8WBFDIR\FORMS, but has to checkout
       forms entities before changing these. Similarly, the developer
       is not allowed to import/export forms entities.

       A new setting in Defaults Configuration (G8WB.CFG) may be used
       to set mandatory mode, as follows:

         [G8WB-DEFAULTS]
         FORMS-CHECKOUT-REQ   :  OFF(default)/ON

       Screen-Painter
       --------------

       New Checkout function: May be used to checkout one or more forms
       entities.

       New Checkin function: May be used to checkin one or more forms
       entities.

       Changed Import function: By default, import will not override any
       forms entity which has been changed since last import/export, or
       has been checked out. Instead you are prompted for each instance.
       A new 'Force' option may be used to force override of any forms
       entity during import.

       Changed Export function: You now the option to export 'changed'
       forms entities, or (like before) one or more forms entities
       regardless of their 'change' status. A new 'Confirm' option may be
       used to make the export permanent - 'change' status updated. By
       default export operations are not-confirmed (like a trial export).

       Commands
       --------

       New check-in/out commands are available as follows:

       TPFF:       FFCIN  name|namemask
                   FFCOUT name|namemask
       Format:     FACIN  name|namemask
                   FACOUT name|namemask
       Pilspr†k:   FPCIN  name|namemask
                   FPCOUT name|namemask
       SOLD:       FSCIN  name|namemask
                   FSCOUT name|namemask
       DIMS8:      FDCIN  name|namemask   (DD)
                   FDCOUT name|namemask   (DD)
                   FSDCIN name|namemask   (SD)
                   FSDCOUT name|namemask  (SD)
                   FTDCIN name|namemask   (TD)
                   FTDCOUT name|namemask  (TD)

       Existing Import commands have now recognize a force override
       argument as follows:

           command import-file ... [-Force]

       Existing Export commands have now recognize '*CHANGED*' as an
       alternative to a name or namemask (meaning export only changed
       forms entities), and a confirm export argument as follows:

           command name|namemask|*CHANGED* export-file ... [-Confirm]

   o   PVCS: G8WB and PVCS integration may now be requested during
       setup. The integration is done as follows:

       CHAR Mode: CTRL-F7 in Batch or TP menu may be used to gain
       access to a PVCS menu with following options: Check out(GET),
       Check in(PUT), Administration(VCS), Differences(VDIFF), History
       (VLOG) and Information(VSQL).

       GUI Mode: PVCS Workbench may be launched from new Tool.

       Note: For CHAR mode, PVCS function are executed under DOS. If
       you experience problems with memory, you should change/include
       an XM setting to limit XM's use of Extended Memory, ex.

           SET XM=/Z8192 (limit XM to 8MB)

       XM will by default use all Extended Memory (up to 16MB).

   ==============
   UPDATE V1.2.69
   ==============

   Errors fixed in this update
   ---------------------------

   o   SOLD+ Debeka: Entity Import Utility failed to find W8SOLDP when
       generating run-time form files.

   o   TPFF: FILL attribute was not recognized by the G8WB import utility.

   o   COBOL: Some variants of literal continuation in combination with
       ascii-literal syntax was not handled correctly.

   Improvements in this update
   ---------------------------

   o   Screen-painter TPFF: Fill attribute for NFIELD is now supported.

   o   TPFF: FLC"x" and FLX"nn" syntax is now supported by host
       import/export utilities, and G8WB import/export utilities.
       FLX is ONLY relevant if the FILL attribute has non-disable value.
       FLC is equivalent to FILL.

       Note: New versions of TPFFEX.CBL and TPFFIM.CBL are available
       under $G8WBGDIR\HOST.

   ==============
   UPDATE V1.2.68
   ==============

   o   New Release base for 16-bit environment.


   =====================
   DOCUMENTATION CHANGES
   =====================

   o   Please refer to Release Notes.


   ============
   TIPS & HINTS
   ============

   o   EURO sign: The Euro sign may be used in COBOL source, however
       neither CHAR Editor nor GUI Editor will show the euro sign
       character correctly.
       You can enter the euro sign character, either with 'Alt-gr E',
       'Alt(hold down) 0128', or copy the character from another
       Euro enabled application, ex. WORD 97.

   o   Forms Table Overflow

       If you receive either of following error messages during import
       or modification of a form (TPFF etc.)

          *-> Form Table field overflow
          *-> Form Table extension overflow

       then you should check settings in Default configuration (G8WB.CFG).

       PAINTER-MAX-FIELDS    : 300            ; Maximum 500
       PAINTER-MAX-EXTENSIONS: 450            ; Maximum 750 (>max fields)

       Increase the values up to maximum as required.

   o   Please refer to Release Notes for futher details.

   ============
   KNOWN ERRORS
   ============

   o   COBOL: 'subscript missing' error flagging does not take place
       when the source line is preprocessed by G8WB, ex.

           IF data-item = ""123""

           should have been

           IF data-item (1) = ""123"

           but is not flagged due to adaption of BULL syntax ""123""

   o   COBOL: When a numeric data-item has some form of COMP usage, and
       the data-item is being used in 'OCCURS .. DEPENDING ON data-item',
       error flagging occur.
       Avoidance: Change source line so usage does not appears on the
       same source line a data-item name, ex.

           Before: 01  PIC-LENGTH COMP-6.
           After:  01  PIC-LENGTH
                                  COMP-6.

   o   G8WFL: Due to problems with GUI interface and creation of a mask,
       the GUI version is disabled (default to CHAR version).

   o   Please refer to Release Notes for further details.


   =================
   KNOWN LIMITATIONS
   =================

   o   COBOL: The syntax 'IF NOT item = ( "A" or "B )' is not flagged by
       G8WB. GCOS accept either 'IF item NOT = ( "A" or "B )' or
       'IF NOT ( item = "A" or "B" )'.

   o   COBOL: G8WB will create a data-item for each file-code, ex.
       'SELECT ... ASSIGN TO F1' will create a date-item named F1.
       This could conflict with a data-item, paragraph or section name
       declared within the program (allowed on GCOS).

       Avoidance: Change data-item, paragraph or section name.

   o   COBOL: G8WB does not accept double value declaration, ex.

       01    ZPCB VALUE SPACES.
             ...
         05  COPTVAL    PIC X(01) VALUE "*".

   o   COBOL: G8WB does not flag a paragraph label in area B.

   o   COBOL-85: Reference modifier validation is not as restrictive as
       GCOS, and some syntax accepted by G8WB will be flagged by GCOS
       COBOL-85 compiler. Be aware of following differences:

       1) The starting position, whether numeric literal or content of
       indentifier, may exceed the length of the field
       2) The length, whether numeric literal or content of identifier,
       may exceed the length of the field

       For G8WB a reference modifier exceeding the field will access
       characters in the relative postions in the following field(s).
       This behavior would normally lead to incorrect results, however,
       it could pass unnoticed, and thus make G8WB testing incomplete.

   o   COBOL: An ascii-literal terminated in column 72 will be flagged
       unless the literal is continued (column 7) on the next source line.

   o   G8WFL: G8WB does not support conversion of GCOS files with an
       OCCURS DEPENDING clause (either abort or produce incorrect
       results).

   o   COBOL: G8WB does not flag use of operator in a WHEN clause, ex.

           EVALUATE field
              WHEN > 0
                 PERFORM ...
              WHEN OTHER
                 PERFORM ...
           END-EVALUATE

       GCOS will flag '> 0' as an error, and you would have to an
       alternate syntax, ex.

           EVALUATE TRUE
              WHEN field > 0
                 PERFORM ...
              WHEN OTHER
                 PERFORM ...
           END-EVALUATE

   o   COBOL: G8WB is triggered whenever multiple verbs occur on the
       same source line, however, all verbs are treated as one during
       animation, ex.

           EVALUATE field
              WHEN 1 DISPLAY "Is 1"
              WHEN 2 DISPLAY "Is 1"
           END-EVALUATE

       During animation 'WHEN 1 DISPLAY "Is 1"' is treated as one step
       only.

   o   COBOL: G8WB does not flag 'NEXT SENTENCE', when preceeded by
       another COBOL statement, ex.

           IF something
              MOVE SPACES to a-field
              NEXT SENTENCE

       GCOS will flag 'NEXT' as a non-alterable identifier.

   o   Sub-schema: G8WB will only support 'SUB-SCHEMA SECTION' when
       placed first in Data Division. GCOS will allow 'SUB-SCHEMA
       SECTION' to be placed anywhere in Data Division, even though
       some GCOS 8 documentation says otherwise.

   o   Please refer to Release Notes for further details.


   ===================
   MANUAL INSTALLATION
   ===================

   G8WB-MFWB Integration utility has been changed to make customization
   of CHAR menus and GUI Organisor easier.

   For initial and update installation, the G8WBMFWB utility will customize
   CHAR menus and GUI Organisor import files, however copying of CHAR menus
   and import of GUI Organisor files will only take place if certain
   trigger files are present. These trigger files are:

   For initial installation:

       $g8wbldir\g8wb.mnc - trigger copying of CHAR menus
       $g8wbldir\g8wb.odc - trigger import in GUI Organisor

   For migrate installation:

       $g8wbldir\g8wbup18.odc - trigger import in GUI Organisor

   For update installation:

       $g8wbldir\g8wbupd.mnc - trigger copying of CHAR menus
       $g8wbldir\g8wbupd.odc - trigger import in GUI Organisor

   If you need to customize CHAR menus and/or GUI Organisor, you should
   delete these files before running G8WBMFWB integration.

   CHAR menus are prepared by G8WBMFWB integration in the following
   files:

       $g8wbdir\MFI\G8WB.MNU  -> $COBDIR\LBR\CLI.MNU
       $g8wbdir\MFI\W8.MNU    -> $COBDIR\LBR\W8.MNU
       $g8wbdir\MFI\W8T.MNU   -> $COBDIR\LBR\W8T.MNU

   After you have customized these files, copy these to $COBDIR as
   indicated and delete the corresponding MNT files.

   GUI Organisor content  are prepared by G8WBMFWB integration in the
   following files:

       $g8wbdir\SYSWIN\G8WB.ODF
       $g8wbdir\SYSWIN\G8WBUP68.ODF
       $g8wbdir\SYSWIN\G8WBUPD.ODF

   After you have customized these files, import these into GUI Organisor.

   Note: Migrate files (G8WBUP68) are ONLY relevant if you have migrated
   to v1.2.68 from a previous release.

   Note: For OS/2, SYSPM is used instead of SYSWIN.

   =================
   PROBLEM REPORTING
   =================

   Please use the enclosed Software Problem Reporting (SPR) forms for
   problem reporting. Describe your problem in as much detail as possible,
   providing example(s) and/or other supporting material if possible, and
   send this to

       B & C Solution
       P.O. Box 54
       Ole Piisvej 4
       DK-3100 Hornbaek
       Denmark

   or fax to +45 49.70.47.80

   or send through COMPUSERVE 100115,1127

   or send through INTERNET support@bc-solution.dk

   Note: If you send supporting material through INTERNET, please use
   CrossePAC to build an F=T B=140 archive with the file(s), or standard
   encoding.

   If you have any questions, suggestions for changes and/or improvements,
   please do not hesitate to let us know.

   More recent updates are available through INTERNET for download or
   verification of update content.

   Via WWW
   -------

   Connect to our web-site 'http://www.bc-solution.dk', go to the
   Support section and select 'GCOS-8 COBOL Workbench 16-bit Update'
   under Download Software Update.

   Note: Only available for Windows 3.x, 95, 98 and NT.

   Via FTP
   -------

   Connect to our web-site 'http://www.bc-solution.dk', go to the
   Support section and select 'Access FTP Download site'
   under Download Software Update, or connect directly to
   'ftp://ftp.bc-solution.dk'.

   Example of an update on FTP-site under G8WB\V12XX:

       wu1269.txt              - Update Notes
       WIN\wu1269.exe          - Complete update for Windows 3.x, 95 and NT
       OS2\wu1269.exe          - Complete update for OS/2

   The Update file is a self extracting ZIP file. Download the wu1269.exe
   file to a temporary directory, and execute each of this. Next run
   SETUP to apply the update.

   If you have problems with download of large files, you may use an
   alternate technique for Windows 95 and NT.

       WIN\wu1269D1.exe        - Partial update for Windows 3.x, 95 and NT
       WIN\wu1269D2.exe        - Partial update for Windows 3.x, 95 and NT
       WIN\wu1269D3.exe        - Partial update for Windows 3.x, 95 and NT
       WIN\wu1269D4.exe        - Partial update for Windows 3.x, 95 and NT
       WIN\wu1269D5.exe        - Partial update for Windows 3.x, 95 and NT

   Update files are self extracting ZIP files. Download all the partial
   update files to a temporary directory, and execute each of these.
   Next run SETUP to apply the update.

   =========================================================================
   GCOS-8 COBOL Workbench is a trademark of B & C Solution Sarl. All other
   trademarks and trade names belong to their respective companies.
   =========================================================================
   Copyright (C) 1991-1999 B & C Solution Sarl. All Rights Reserved.