   ==========================================================================
                              M I C R O   F O C U S

             S E R V E R   E X P R E S S   5.0   W R A P P A C K   4

                        for zSeries running SuSE Linux
   ==========================================================================

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

       INTRODUCTION
       NEW FEATURES
       DOCUMENTATION
       SUPPLEMENTARY INFORMATION
       BACKWARD COMPATIBILITY
       RESTRICTIONS


   INTRODUCTION
   ============
   This document provides information on new features, enhancements and
   certain restrictions of which you should be aware in this release.

   You should read this document in conjunction with your Introductory
   Letter and related documentation before using this product.

   For a list of the versions included in this release and the platforms 
   and operating systems to which they apply, see the document v5000.txt, 
   which is in the UNIX folder of the software CD.


   NEW FEATURES
   ============
   This version of Server Express contains the following new feature,
   which is described in the product Help:

   o  COBOL Support in Eclipse

      For information on Setting Up the Eclipse Environment, see the WrapPack
      Readme, which is available on the SupportLine Web site,
      http://supportline.microfocus.com.

      For information on COBOL Support in Eclipse, see the Eclipse Help. In 
      the Eclipse IDE, click Help > Help Contents > Micro Focus Help for UNIX.
      In the Start Here folder, click "Known Errors and Restrictions".

      Dynamic Help uses an embedded browser to display the Help, and requires 
      certain libraries. On Linux and Unix platforms, Eclipse requires a 
      compatible version of the Mozilla browser. Note that:
    
       *  Mozilla 1.4 GTK2 through to 1.7.12 GTK2 can be used with Eclipse.

       *  Mozilla Firefox can be used with Eclipse (Linux only), provided that 
          it has been compiled with linkable Gecko libraries. Note that Firefox 
          downloads from mozilla.org currently do not satisfy this criterion, 
          but Firefox installations that are included in major Linux 
          distributions often do. If you attempt to use a statically-linked 
          Firefox installation, the following error message is displayed "No 
          more handles [NS_InitEmbedding...error -2147221164]".

       *  Ensure that the environment variable MOZILLA_FIVE_HOME is set to 
          point to the folder containing your Firefox installation. For example:

             setenv MOZILLA_FIVE_HOME /usr/lib/firefox-1.0.4

       *  Ensure that MOZILLA_FIVE_HOME is added to the LD_LIBRARY_PATH 
          environment variable. For example: 

             setenv LD_LIBRARY_PATH %LD_LIBRARY_PATH%;MOZILLA_FIVE_HOME 

       *  Depending on your graphical environment, you press F1 or Ctrl F1 to 
          invoke COBOL Help from the Editor or Problems pane.



   DOCUMENTATION
   =============
   For information on the documentation provided with this product and 
   how to access it, see your CD Booklet.

   o  You can view the Enterprise Server Documentation in a separate 
      browser window while you are using the Enterprise Server 
      Administration Web interface, by clicking Contents in the menu 
      at the left-hand side of the page. For this link to work, you must 
      have the following in place: 
        o  An enterprise server that has a Web listener with
           the following entry in the [virtual paths] section: 
           docs=<ES>/docs/html
        o  The enterprise server must be started
      Note that the default enterprise server, ESDEMO, may not have
      the correct configuration information entry for its Web listener.
      If you encounter problems accessing this documentation while you 
      are using ESDEMO, you must correct the entry using the Edit 
      Listener page. 

      When you create a new enterprise server, a Web listener with the
      required configuration information entry is automatically created. 

   SUPPLEMENTARY INFORMATION
   =========================

   o  Animating Multi-threaded Programs

      You need to compile all programs in a application with "cob -t" when 
      animating a multi-threaded application, otherwise animation (in particular 
      dynamic attachment, cobrun +A, Just-In-Time and CBL_DEBUGBREAK/ 
      CBL_DEBUG_START animation) might not work.

   o  ACCT Demonstration Programs

      The charset of the ACCT demonstration programs has changed from
      EBCDIC to ASCII. As a consequence, these programs are not compatible
      with copies of the VSAM files, ACCTFIL and ACCTIX, created in an 
      earlier release. 

   o  C Calling COBOL to Get a License

      Executables containing linked-in C code can call from C to the license 
      entry point MFaslmf_getlic() to get a license. A returned value of 0 
      indicates success, otherwise a number indicating reason for failure (such 
      as no licenses exist, all licenses in use).  
      
      -526711

   o  Database Support

      The following database preprocessors are available with this release 
      of Server Express. See your Database Access Guide for further details 

      regarding their usage.

      DB2 ECM
      -------
      The DB2 ECM is intended for use with :

      - IBM DB2 Universal Database Version 5.0 or later
      - IBM DB2 Connect Version 5 or later

      To compile and execute applications that access DB2 database services, 
      you need to have installed either :

      - DB2 UDB Software Development Kit Version 6.1 or later, or

      - DB2 UDB Application Development Client Version 7.1 or later

        The DB2 ECM is supported in both 32-bit and 64-bit modes


        The Host Compatibility Option is supported in 32-bit mode.


      COBSQL
      ------

      COBSQL is intended for use with :

      - Sybase Open Client Embedded SQL/COBOL Version 11.1 or later
      - Oracle Pro*COBOL Version 1.8 or later
      - Oracle Pro*COBOL Version 8 or later
      - Informix ESQL/COBOL Version 7.3 or later

        The COBSQL preprocessor is supported in both 32-bit and 64-bit modes.


      A script is available that creates an executable run-time system or a
      callable shared object containing Oracle support. This script is 
      available in the Micro Focus Knowledge Base article #22062, located at 
      http://supportline.microfocus.com/mf_kb_display.asp?kbnumber=22062 
      For background information see the "Cobsql" chapter of the Database 
      Access Guide.

      A new COBSQL error message has been added: 

        CSQL-F-046: Command line is too large. Maximum length is 1140 characters
      -537959


      OpenESQL
      --------
      OpenESQL is intended for use with ODBC 3.0-compliant drivers.

      Refer to your driver vendors' documentation to determine whether 
      your driver is suitable for use with OpenESQL.

      OpenESQL is supported in 32-bit mode.

      SQL Option
      ----------
      The SQL Option is supported in 32-bit mode. Refer to the CD Booklet for 
      details on how to install this software.

      The SQL Option includes an ODBC 2.5-compliant ODBC driver. A template 

      odbc.ini file can be found under your SQL Option installation 
      directory, within the cfg subdirectory. This file includes documentation 
      on the various configuration options available for the driver.

      The SQL Option ODBC driver has been tested with the iODBC 3.51 ODBC 

      Driver Manager. You can obtain information on this driver manager, 
      including downloads, from http://www.iodbc.org/ .


   o  File Handler

      The default for NAMEOPTIONS has been changed to OFF in this release.

   o  Net Express 3.1 Publisher


      If you use Net Express Publisher to deploy applications built using 
      Net Express to Server Express, you need the Net Express 3.1 FixPacks:

 
      ide07n31.exe IDE component FixPack v3.1.007 (or later)
      unx05n31.exe Unix Option FixPack v3.1.005 (or later)
 
      These correct a problem with Net Express not copying certain files
      across to UNIX correctly. 

   o  Default Thread Stack Size

      The default thread stack size is 160KB in 32-bit mode and 320KB in 64-bit 
      mode. If you create a lot of  threads, you might run out of stack space. 
      You can increase the size of the threads stack by setting the 

      COBMAINSTACK environment variable.

      526716

   o  Remote Debugging with Net Express

      When you debug a program on your UNIX system from Net Express, you must 
      transfer the .idy files from Server Express to a local drive on the PC 
      where Net Express is running (or map a network drive to the UNIX 
      directory), and delete all idy files from the project debug directory. 
      Then in "Animate > Settings > Location of debug information files (.idy) 
      for local access" enter the path of the .idy files transferred from the 
      UNIX machine or on the mapped network drive. 

   o  Run-time Tunables

      A new tunable, no_mfredir, has been added. Its details are as follows:

          no_mfredir 

          Enables you to reduce the time the run-time system takes to 
          initialize if your project or application does not execute remote 
          programs.

          Syntax: 

          >>-----set no_mfredir=---.-TRUE-.-------------><
                                   +-FALSE+
          Parameters:

            TRUE    The run-time system initializes without searching for the 
                    optional module _MFREDIR. 
            FALSE   The run-time system searches for _MFREDIR when 
                    initializing.  

          Default: FALSE  


          Comments:

          The _MFREDIR module is only required to enable remote program 
          execution. As most applications do not require remote program 
          execution, _MFREDIR rarely exists resulting in many unnecessary 
          lookups being made in the folders on the application and system 

          search paths. 


   o  Use of Terminals

      There are a number of UNIX terminals that the IDE and License Management
      Facility will not function correctly with, e.g. true hpterm terminals. 
      The only terminals tested are those for which we supply terminfo files in 
      $COBDIR/terminfo.
      527502

   o  Enterprise Server


      Changing Timeouts
      -----------------
      There are two timeout options for COBOL clients of Enterprise Server 
      (including during deployment), one for establishing the connection and 
      another for other operations. The defaults can be overridden by setting 
      the following environment variables: 

      MFC_TIMEOUT
      MFC_CONNECT_TIMEOUT

      or editing the following section in the file mf-client.dat:

      [defaults]
      connect-timeout=<nn>
      timeout=<nn>

      where <nn> is the timeout period in seconds.

      These timeouts are set in seconds, but with a 5-second grain, so in 
      effect they are rounded up to the next multiple of 5 seconds. Timeouts
      are used as follows:

      If MFC_TIMEOUT or MFC_CONNECT_TIMEOUT (or both) is set in the 
      environment, its value will be used.

      Otherwise, if a "[defaults]" section exists in mf-client.dat and it 
      contains an entry for "connect-timeout" or "timeout", that value will 
      be used.

      Otherwise, the built-in defaults of 15 seconds for connect timeout and 
      30 seconds for other functions will be used.

      Controlling Debugging
      ---------------------

      Once you have entered a debuggable program (either because you inserted
      a call to CBL_DEBUGBREAK at the beginning of the procedural code or 
      because it is running in a server started with the command cassi /a), 
      if you hit Zoom, you cannot then break into the program using the 
      keyboard. So, if you want to use Zoom so that you can focus on a subset
      of your code, you will need to set breakpoints or insert "CALL 
      CBL_DEBUGBREAK" statements. If you wish to store breakpoints during a 
      debugging session, follow the procedure described in the section 
      "Debugging COBOL Services" in your Debugging Guide, and in addition, 
      before you run the client program:

      -  Set the COBAIF environment variable to point to a writeable 
         directory. (This is the directory in which Animator searches for 
         or creates the Animator session file (.aif) for the program being 
         animated.)

      -  Set the COBAIFNAME environment variable to a suitable name for the 
         Animator session file


      -  When you enter a debuggable program, set instruction breakpoints as 
         necessary in the current program, and set program breakpoints on 
         any programs that the current program calls. You can set a program 

         breakpoint on the current program as well, if necessary. When you 
         enter a called program, set instruction breakpoints as desired. 

      If you single-step through your code, when you step a GOBACK statement, 
      the Animator stops on the next debuggable instruction encountered.

      Terminating a Debug Service Execution Process
      ---------------------------------------------
      If you debug a COBOL service using the cassi /a command, use any of 
      the following methods to terminate the server:

      -  1. Enter ESMAC (Enterprise Server Monitor and Control) from the 
            Server Details page. 

         2. Select the SEP view and click Stop next to the debug SEP you 
            want to terminate.

      -  Press the quit key (default is Ctrl+\) at the UNIX machine where you 
         started the debug server. This closes the debug server down 
         immediately.

      -  1  Press ESCape at the Animator screen. Animator displays a popup 
            window.


         2  Press Y. This allows the current processes to terminate in a tidy 
            way. (do not press D (Detach) as this will leave the SEP active 
            with no debugger attached.)

      -  1  Press the interrupt key (default is Ctrl+C) at the UNIX machine
            where you started the debug server. Animator displays a popup 
            window.

         2  Press either ESCape or D (Detach). This allows the current 
            processes to terminate in a tidy way. You might need to press
            ESCape or D a second time 

      Viewing Enterprise Server Administration
      ----------------------------------------
      Enterprise Server Administration is best viewed with Internet Explorer. 
      You might find that pages are displayed slowly using the Netscape 
      browser.

      Java and JDK Support
      --------------------
      The Java Development Kit (JDK) is required for compiling Java. The 
      JDK is required for generating Java interfaces using the Deploy 
      tool in the Interface Mapping Toolkit or the imtkmake command.  

      The JDK required for generating Java beans depends on the JDK with 
      which your Java client is compiled, as follows:

         Java Client       Java Bean
         -----------       ---------
         JDK 1.4.2 (IBM)   JDK 1.4.2 (IBM)
         JDK 1.4.2 (Sun)   JDK 1.4.2 (Sun)
         JDK 1.5 (Sun)     JDK 1.4.2 (Sun)
         JDK 1.5 (Sun)     JDK 1.5 (Sun)

      After installing the JDK, you need to set up your Java environment. 
      See the section "Setting Up the Environment for Java and COBOL" in 
      your "Java and COBOL" book in the Help.

      J2EE 1.3 and 1.4 are supported for the deployment of EJBs. This 
      includes support for:
 
        - EJB 2.0 specification
        - EJB 2.1 specification
        - Java Connector Architecture 1.0 specification
        - Java Connector Architecture 1.5 specification

      The JDK is required for the generation of EJBs using the
      Interface Mapping Toolkit and their deployment. The JDK required
      depends on the J2EE application server being deployed to. The 
      following application servers and corresponding JDKs are supported:

          JBoss 3.2.8 - JDK 1.4.2 (Sun) for J2EE 1.3
          JBoss 4.0.2 - JDK 1.5 (Sun) for J2EE 1.4
          WebLogic 8.1 - JDK 1.4.2 (Sun) for J2EE 1.3
          WebSphere 5.1 - JDK 1.4.2 (IBM) for J2EE 1.3
          WebSphere 6.0 - JDK 1.4.2 (IBM) for J2EE 1.4

      Resource Managers

      -----------------
      Enterprise Server supports the execution of applications running 
      against any XA-compliant database.

      For the following databases, Micro Focus provides a switch module
      which provides Enterprise Server with access to the database's 
      XA switch structure.:

      - Oracle

        Applications precompiled using Pro*COBOL, or Cobsql, using

        * Oracle Pro*COBOL Version 1.8 or later
        * Oracle Pro*COBOL Version 8 or later

      - IBM DB2 Universal Database


        Applications precompiled using the IBM command-line precompiler
        or compiled using the Micro Focus DB2 Compiler directive. 


       For other databases, you should refer to the database vendors'
       documentation for details of their XA switch modules' requirements.

      If you are defining external XA resource managers for either Oracle or 
      IBM DB2, you need to have set up the database environment before starting 
      the Directory Server. Please refer to your database vendors' 
      documentation for further details.

      If you are defining external XA resource managers for both Oracle and 
      IBM DB2, you should ensure that the Oracle resource manager is defined 
      before the DB2 resource manager from within Enterprise Server 
      Administration.

      If you are defining external XA resource managers for Oracle, in order to 
      execute your user application, you must create a callable shared object
      containing Oracle DBMS support, rather than creating a new executable 
      run-time system including that support. For background information see 
      the COBSQL chapter in your Database Access Guide, and see also the 
      Micro Focus Knowledge Base article #22062, located at
      http://supportline.microfocus.com/mf_kb_display.asp?kbnumber=22062. 
      This article also provides a script that will create the callable shared 
      object for you.




   BACKWARD COMPATIBILITY
   ======================

   o  An error has been fixed in the checker, so that access permissions of a 
      file are now refreshed every time it is opened. Previously, the access 
      permissions used on the first open were used for all subsequent opens. If 
      you were relying on the existing behavior, you need to be aware of this 
      change.
      -1058301

   o  When you compile programs with EXEC SQL statements, you might now get
	External Compiler Module warnings, such as the following: 

        * 801-W***************************************
        **    External Compiler Module message
        **    DB1002 Statement is not in area B.

        * 801-W***************************************
        **    External Compiler Module message
        **    DB1000 Use of EXEC SQL INCLUDE SQLCA END-EXEC.

     You can usually ignore these warnings, which appear as a result of the
     Host Compatibility Option now being supported and enabled. 


   RESTRICTIONS
   ============

   Known Problems In This Release

   ==============================
   o  Animator
   
      Ending Path with a \
      --------------------
      When you set up remote animation, make sure that you do not end the 
      path in the 'location of debug information files (.idy) for local 
      access' with a backslash character (\). If you do end the path with a 
      \, when you try to debug the Animator will report that it cannot locate 
      the files.
      523153

 
      Query-Enter on Group Items
      --------------------------
      If you use Query-Enter to query a group item which contains a data item 
      with the same name as other data items in different groups, Animator does 
      not show the name of the group item.
      511230

      Reset in Generated Code
      -----------------------
      Using Reset Cursor/Start in optimized generated code programs can produce 
      unpredictable results.
 
      Animating an Error Procedure
      ----------------------------
      It is not possible to animate through an error procedure, that is, code 
      called by CBL_ERROR_PROC.
      526830

      Session Recorder
      ----------------
      A keystroke recording created on HP-UX cannot be replayed on another
      operating system. A keystroke recording created on any other operating 
      system but HP-UX cannot be replayed on HP-UX.

      Animating Through longjmp() Calls
      ---------------------------------
      You cannot step through longjmp() calls if your program is in .int code 
      and it has previously called setjmp(). This is due to a stack issue. The 
      result will be as if you had pressed (z)oom. To avoid this restriction, 
      we suggest you animate in .gnt code, or when animating the .int code, use 
      the directive 'mixedlangdebug'. This should allow you to step through the 
      longjmp() routine, and return to the saved location.
      523674




      Multi-threaded Animation Hangs
      ------------------------------
      Animating programs with multiple threads might hang.
      536075


   o  CCI   


      On 64-bit Linux, ccitcp2 might not communicate correctly with
      CCI programs running on other platforms. As a workaround,
      run ccitcp2 on another platform and direct your 64-bit Linux
      CCI programs to it by setting the CCITCP2 environment
      variable.
      540904


   o  Client-Server Binding

      When running mfserver in the background, you must use the -b option 
      to mfserver, and close or redirect standard input, or mfserver will 
      receive a SIGTTOU (terminal output) signal and stop when a client 
      connects to it. For example:


      cobrun mfserver -s filetran -b < /dev/null &

      532893

   o  Error Messages

      If run-time system error 249 occurs, the message displayed is "249 error 
      message text not found (Signal <signal-number>)". The message should be 
      "249 Process killed (Signal <signal-number>)". See the documentation 
      for more information on this error.

   o  COBOL Syntax Support

      The following pointer initializations are now rejected by the Compiler:


         01 cthandle usage pointer typedef.
         01 p1 cthandle value 0.

         01 cthandle usage pointer typedef.


        01 p1 cthandle value low-values.

       These are illegal and will produce illegal intermediate code.

       The proper syntax to use is

         01 cthandle usage pointer typedef.
         01 p1 cthandle value null.


       Previously the Compiler gave a syntax error for this. But now the
       Compiler allows the proper syntax to work.

       An alternative, which will compile with any compiler, is:

         01 cthandle usage pointer typedef value null.
         01 p1 cthandle. 

   o  Compiler Directives

      Support for HOSTNUMCOMPARE(1) and HOSTNUMMOVE(1) has been restored. 
      However the use of this form of these directives is deprecated and support
      for it will be removed in a future release.

   o  Dialog System Terminals

      Dialog System does not run correctly on a terminal that has more than 
      25 lines. To work around this set the LINES environment variable to 25.

   o  Eclipse COBOL Support

      For information on COBOL Support in Eclipse, see the Eclipse Help. In 
      the Eclipse IDE, click Help > Help Contents > Micro Focus Help for UNIX.
      In the Start Here folder, click "Known Errors and Restrictions".

      For information on Setting Up the Eclipse Environment, see the WrapPack
      Readme, which is available on the SupportLine Web site,
      http://supportline.microfocus.com.

      Dynamic Help uses an embedded browser to display the Help, and requires 
      certain libraries. On Windows platforms, the browser is usually Internet 
      Explorer and works with the default installation. On Linux and Unix 
      platforms, Eclipse requires a compatible version of the Mozilla browser. 
      Note that:
    
       *  Mozilla 1.4 GTK2 through to 1.7.12 GTK2 can be used with Eclipse.

       *  Mozilla Firefox can be used with Eclipse (Linux only), provided that 
          it has been compiled with linkable Gecko libraries. Note that Firefox 
          downloads from mozilla.org currently do not satisfy this criterion, 
          but Firefox installations that are included in major Linux 
          distributions often do. If you attempt to use a statically-linked 
          Firefox installation, the following error message is displayed "No 
          more handles [NS_InitEmbedding...error -2147221164]".

       *  Ensure that the environment variable MOZILLA_FIVE_HOME is set to 
          point to the folder containing your Firefox installation. For example:

             setenv MOZILLA_FIVE_HOME /usr/lib/firefox-1.0.4

       *  Ensure that MOZILLA_FIVE_HOME is added to the LD_LIBRARY_PATH 
          environment variable. For example: 

             setenv LD_LIBRARY_PATH %LD_LIBRARY_PATH%;MOZILLA_FIVE_HOME 

       *  Depending on your graphical environment, you press F1 or Ctrl F1 to 
          invoke COBOL Help from the Editor or Problems pane.



   o  Editor Backup Files

      The COBOL Editor's library option enables you to have multiple files
      open; each file is contained in its own sub-window. If you choose to
      back up a file in a window, you must close that file's window (using
      Esc), before attempting to load the backup. If you do not, you will 
      receive a file-locked error. For details on how to back up files in
      multiple windows, see the section "Saving a File" in the chapter
      "Editor" in your Utilities Guide.

   o  64-bit applications
      On Solaris x86_64, trying to run 32-bit .gnt code from a 64-bit 
      application, when no 64-bit .gnt version exists, will result in an 
      RTS 173 error and not an RTS 211 error as expected.        

   o  Fileshare on 64 bit systems

      Fileshare does not correctly set offsets in 64-bit bytestream I/O 
      operations.

   o  FSVIEW API and Command-line Interface

      The FSVIEW calls and commands that have to do with log files are not 
      currently implemented.

   o  J2EE Resource Adapters

      When you undeploy a resource adapter from WebLogic 8.1 and WebLogic 9.0,
      you receive a java.lang.NullPointer exception. This does not cause any 
      problems and will be investigated in future. 
      542611

   o  Length of Filenames

      The character-based tools in Server Express (Editor, Data File Editor, 
      Dialog System etc) cannot handle filenames longer than 65 characters. In 
      this context a filename includes the pathname.
      704814

   o  Naming of Interface Fields for Java Interfaces in IMTK

      Each group field (i.e. field containing subitems) in a Java interface
      must have a name that is unique across all operations of that
      interface. Where this is not the case, client generation may fail.

   o  Object-oriented COBOL

      When deploying a COBOL service program that uses Object-oriented COBOL
      to an enterprise server, you must specify that any container used to 
      run the service is not reused. To do this, configure the deployment 
      settings as follows: 

      If the Service Interfaces window is not open, start cobimtk.
      1. Click File > Open and navigate 
         to the directory containing the service interface you want to deploy. 
      2. Double-click the .si file containing your service interfaces. 
      3. In the Service Interfaces pane, right-click the service you want 
         to deploy. 
      4. Click Settings. 
      5. Make sure that the Deployment Server tab is selected. 
      6. Check Enable enterprise server run-time environment. 
      7. Click Configure enterprise server run-time environment. 
      8. Click the Deployment Characteristics tab. 
      9. Uncheck Reuse container after application termination. 
      10.Uncheck Reuse container after non-fatal run-time system error. 
      11.Click OK. 
      12.Click OK. 


      Enterprise Server does not support the use of Object-oriented COBOL in 
      CICS or JCL programs. 

   o  Run-Time System

      The run-time system error COBRT252 "Memory corruption detected (Fatal)”, 
      might occur when performing a SORT FIELDS=COPY on a file with a record 
      format of VB, under mainframe emulation of DFSORT.
      542609

      Threaded Programs - Return Code
      -------------------------------
      If you create a multi-threaded application that uses CBL_EXIT_PROC to 
      perform an exit procedure when the program terminates, and an error
      occurs during the exit procedure, the application does not terminate
      with a non-zero exit code to the operating system.

      Shared Object- C Module Load Failure
      ------------------------------------
      If you create a run-time system that includes a C module and you use the 
      run-time system to run a COBOL shared object that calls a function within 
      the C module, you will get an RTS 198 load error for that function when 
      "." (dot) is included as a directory to be searched on the load library 
      path (LD_LIBRARY_PATH).

   o  SORT/MERGE

      SORT/MERGE Using Old .int Files
      -------------------------------
      A program error might occur if you are executing intermediate code files 
      that were created using previous versions of COBOL for UNIX and which 
      include SORT/MERGE statements.

      Sorts Using the NLS Directive
      -----------------------------
      Programs compiled with the NLS directive that make use of COBOL SORT with 
      alphanumeric keys return records in the standard alphanumeric order, 
      rather than in the correct order for the NLS locale. This restriction 
      only applies to file sorts and not to table sorts.
      514543

   o  Unicode

      DISPLAY-OF Intrinsic Function
      -----------------------------
      When using the DISPLAY-OF intrinsic function to convert Unicode 
      characters to your current locale, any Unicode characters that have no 
      equivalent in the current locale might not be replaced by the optional 
      default replacement character on some UNIX platforms.
      532366

   o  Mainframe Sort Emulation

      In mainframe sort emulation, under certain circumstances when sorting 
      records using RECORD TYPE=VB, records are truncated by four characters.

   o  Documentation

      Fileshare Manager
      -----------------
      The section "Linking Fileshare Manager" in the "Advanced Operation" 
      chapter of the Fileshare Guide states that if your program calls the 
      Fileshare Manager, you need to link in the Fileshare manager object file 
      (fsmgr.o) when you create an executable file. In fact you do not need to 
      link in fsmgr.o. 

   o  Enterprise Server
   
      Application-Managed Services
      ----------------------------
      If you have configured Enterprise Server to support container-managed 
      services by defining external XA resource managers, any application-
      managed service that issues CONNECTs to, or DISCONNECTs from, one of 
      these defined resource managers might receive warning-level response 
      codes.

      Security Configuration
      ----------------------
      On some platforms the OpenLDAP client library is not supplied as 
      standard in the Server Express product. 
 
      As a consequence, if the Enterprise Server administrator adds a 
      new Security Manager that attempts to use the "mldap_esm" module 
      supplied by Micro Focus the following runtime errors may occur:
 
        - if a Security Manager using "mldap_esm" is added to the 
          Default ES Security Manager List (the default is not to use 
          an external Security Manager) the following error will appear 
          in the console when attempting to start an Enterprise Server 
          instance:
 
          "ESFMI0201C Unable to load ESM Module "[Security Manager name]"
          (mldap_esm)"
 
          Similarly, if such a Security Manager is added to the security
          configuration for a specific Enterprise Server instance, 
          over-riding the default ES security, the same error will occur.

        - if a Security Manager using "mldap_esm" is added to the 
          Directory Server Security Manager List (the default is 
          to use the "MFDS Internal Security" Manager), the 
          following error will be displayed:
 
          "SF0024E Error 16/4/0 SAFMGR initialization failed: Failure 
          loading ESM Module"
 
          The Security Manager will not be used by Directory 
          Server Security.
 
      If OpenLDAP client support is not present, MF Directory Server 
      repository location configuration will also display an 
      error if the MF Directory Server repository location is 
      changed to an LDAP server partition:
 
      "MDS1503E Schema check error: 501, OTHER. Previous schema 
      path restored."


      Simultaneous Client Requests (MTO only)
      ---------------------------------------
      If you have clients using the ECI interface with the CICS Transaction 
      Gateway to communicate with a CICS application running in Mainframe 
      Transaction Option (MTO), a client program might receive an 
      ECI_ERR_TRANSACTION_ABEND return code with an abend code of AZTY, 
      indicating that several clients tried to communicate with the system at 
      the same time but not all requests could be satisfied by MTO. The 
      workaround for this issue is to set the environment variable 
      TX_UNICLI_SESSIONS to the required number of sessions in the 
      Configuration Information for the enterprise server as follows:

      [ES-Environment]
      TX_UNICLI_SESSIONS=<required-number-of-sessions> 

      The default is 4.

      You should set "Maximum requests" in the Client Section of the CICS 
      Transaction Gateway configuration to the same value.

      If you do this you will also probably need to change the client program 
      to ignore the ECI-ERROR_MAX_SESSIONS return code and retry the call. 
      For example:

      do 
         {
             Rc = CICS_ExternalCall (&EciParms);
         } while (Rc == ECI_ERR_MAX_SESSIONS); 

      If you do not make this modification, the client program might still 
      receive the ECI_ERR_TRANSACTION_ABEND return code.



   Restrictions Due to Third-Party Software
   ========================================

   o  If you compile a program with dynamic SQL that uses more than one SQLDA, 
      the compilation fails with the error message

      "SQL4913N The host variable token ID has already been used."

      This is an issue with IBM UDB 8.1. To resolve this apply IBM's fixpack 
      8.1.2 or later  

   o  If using IBM UDB 8.1.4, if the User ID or Password is specified as a host 
      variable defined as a fixed-length character string (CHAR),unless the 
      length of the host variable used for the password matches the actual 
      length of the password, an SQLCODE of -30082 will be returned on the Type 
      1 CONNECT, with a error string of "24. USERNAME AND/OR PASSWORD INVALID".

      This is a known issue with IBM UDB 8.1.4. As a workaround, define the 
      host variable as a varying-length character string instead. For 
      information on how to define such a data item see the section 
      "Character Data Types" in the chapter "Data Types" in your Database 
      Access book.



   ==========================================================================

   Micro Focus, Animator and Net Express are registered trademarks, and 
   Object COBOL and Server Express are trademarks, of Micro Focus
   International Limited. All other trademarks are the property of their
   respective owners.
   ==========================================================================
   @(#)Vrn/readme.1/////05/13 Mar 2007/nrV 
   Copyright (C) 1992-2007 Micro Focus (IP) Limited. All rights reserved.
 
