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

                      S E R V E R   5.0   W R A P P A C K   4
                                       
                             for PA-RISC running HP-UX
   ==========================================================================

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

       INTRODUCTION
       DOCUMENTATION
       SUPPLEMENTARY INFORMATION
       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 these products.

   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 root of the software CD. 


   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 FOR APPLICATION SERVER
   ================================================

   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  Path for Shared Libraries
      -------------------------
      On HP-UX 32/64-bit, to access shared libraries you need to include 
      $COBDIR/lib on both SHLIB_PATH and LD_LIBRARY_PATH.

      On HP-UX, in order to execute an application precompiled using
      Pro*COBOL (or COBSQL) after you have created a callable shared 
      object of Oracle DBMS routines, you need set an environment variable,
      LD_PRELOAD, to point to the Oracle client callable shared object, for
      example:

      LD_PRELOAD=$ORACLE_HOME/libdir/libclntsh.sl  
      export LD_PRELOAD  
  
      where libdir is:  
  
      lib32 for 32-bit environments, and  
      lib for 64-bit environments.  
  
      You should then be able to execute your application.  
   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


   SUPPLEMENTARY INFORMATION FOR ENTERPRISE SERVER
   ===============================================

   o  Changing Timeouts

      There are two timeout options for Enterprise Server, 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.

   o  J2EE Application Server Support
      
      J2EE 1.3 and 1.4 are supported for the deployment of EJBs generated using
      the Interface Mapping Toolkit. 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 following J2EE application servers, using the following JDKs:

          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
          Oracle 10.1.2 - JDK 1.4.2 (Sun) for J2EE 1.3
          Oracle 10.1.3 - JDK 1.5 (Sun) for J2EE 1.4
          WebLogic 8.1 - JDK 1.4.2 (Sun) for J2EE 1.3
          WebLogic 9.0 - JDK 1.5 (Sun) for J2EE 1.4
          WebSphere 5.1 - JDK 1.4.2 (IBM) for J2EE 1.3
          WebSphere 6.0 - JDK 1.4.2 (IBM) for J2EE 1.4

   o  J2EE Applications

      If you run J2EE applications on Enterprise Server, if you stop and 
      restart the enterprise server you must also stop and restart the J2EE 
      application server, such as WebSphere.
      533207

   o  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.

      If you are defining an external XA resource manager for Oracle, you need 
      to perform an additional step before starting the Directory Server.

      Having installed the patch, you need to set an environment variable,
      LD_PRELOAD, to point to the Oracle client callable shared object, for
      example:

      LD_PRELOAD=$ORACLE_HOME/libdir/libclntsh.sl  
      export LD_PRELOAD  
  
      where libdir is :  
  
      lib32 for 32-bit environments, and  
      lib for 64-bit environments.  
  
      You should then be able to execute your application.  

   o  Viewing Enterprise Server Administration

      Enterprise Server Administration is best viewed with a modern browser,
      such as Internet Explorer 6 or later, Mozilla, or Firefox.


   RESTRICTIONS FOR APPLICATION SERVER
   ===================================

   o  64-bit Unsupported Features
      
      HyHelp is not supported on 64-bit platforms.


   Known Problems In This Release
   ==============================

   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  Dialog System

      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  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  Run-Time System

      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.

      Deleting Files
      --------------
      On HP-UX, if a program attempts to delete a file that is already open 
      to another user, the file status returned is 0/065 (File locked), 
      instead of the more usual 9/029 (Attempt to delete open file). This 
      applies to 32-bit files only: 64-bit files return the usual file 
      status. 

   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


   RESTRICTIONS DUE TO THIRD-PARTY SOFTWARE
   ========================================

   Known Problems In This Release
   ==============================
   o  BEA WebLogic 8.1 fails to throw an exception on a failure of the
      commit verb in the local transaction resource adapter. The Micro Focus 
      resource adapter throws an exception indicating the commit failure, but 
      WebLogic ignores this and continues the processing and throws an 
      exception in the user code at a later point. 
      -540412

   o  In IBM WebSphere 5.0, when a stateful session gets passivated, there 
      is a problem with activation. This causes an error
      org.omg.CORBA.OBJECT_NOT_EXIST: null:java.rmi.NoSuchObjectException: at
      com.ibm.ejs.container.passivator.StatefulPassivator.activate 
      (StatefulPassivator.java:156)
      at com.ibm.ejs.container.StatefulBeanO.activate(StatefulBeanO.java:382) 

      The alternatives are to use stateless beans or to tune WebSphere
      to prevent passivation of stateful beans. To do the latter, change the 
      timeout value under IBM Extensions. Click the EJB in the Application 
      Assembly Tool (AAT), then in the bottom right pane click the IBM
      Extensions tab. The default is set to 600 seconds. Change this to 0
      seconds to ensure that the stateful bean does not get passivated. 
      -530027
 
   o  With IBM WebSphere 5.1 on IBM xSeries running SuSE Linux, you get
      the message 'connection refused’ when running an EJB that calls enterprise
      server. Check that the port is correct and that enterprise server is 
      started (before starting WebSphere). 

      If you still get the same message, set the ServerHost configuration 
      property to the machine name instead of localhost. You can do this 
      using the WebSphere administration console. You need to restart 
      WebSphere server after setting the property.

      Alternatively you can set this property in the deployment descriptor, 
      ra.xml in the resource adapter's archive file: mfcobol*.rar. For the 
      location of the resource adapters see the section "Resource Adapters"
      in the chapter "Deploying Interfaces" in the "Configuration and 
      Administration Guide" for Micro Focus Server. Again, you need to restart 
      WebSphere server after setting the property. 
      -540148

   o  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  On Solaris using Oracle 10.1.2, a NullPointerException is sometimes 
      thrown at the end of a session. You can avoid this by catching the 
      exception and moving on to the next operation. The result of executing 
      the COBOL program is available in your output.
      542639


   RESTRICTIONS FOR ENTERPRISE SERVER
   ==================================

   o  64-bit 

      Enterprise Server is not supported on 64-bit platforms. Some features 
      might compile correctly, but won't run.

   o  License Reports

      If you have a CPU license for MTO or Micro Focus Server, you have
      unlimited use of the product. With this CPU license, if you use the 
      license manager command eslmfgetpv t to produce a license report, 
      DEVMTO (or DEVES) usage is not reported and 0 is shown against the 
      appropriate license totals. 
      536449

   o  Under HP-UX PA-RISC, because of an issue with the operating system, when 
      a debuggable SEP is removed from the ES pool, it is not always removed 
      cleanly. This debuggable SEP might be 'terminated' and will show up in 
      console.log as 'terminating due to run-time error'. This should not 
      affect your ES system.
      536360
 

   o  Enterprise Server 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."


   Known Problems In This Release
   ==============================
  
   o  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.

   o  CICS Unsupported Transactions

      The reference help for Mainframe Transaction Option includes topics on 
      some CICS transactions that are not supported and are not included in the 
      software. These are:

      CGWY
      CPOP
      CRTE
      CSSF

   o  Clients from Server Express 4.0

      If you have COBOL Web Service clients that you generated using Server
      Express 4.0, you need to regenerate them in order for them to work 
      correctly with Server Express 4.0 Service Pack 1. This restriction
      will be removed in the first Fixpack for this release.
      535434
      535435

   o  Transactional Client Requests

      When a COBOL service that is processing a transactional J2EE client 
      request using the local connector (mfcobol-localtx.rar) fails by ending 
      with a fail return-code, Enterprise Server displays the message 
      "Cannot end/commit/rollback/recover a transaction that doesn't exist". 
      This message is incorrect, as in this case rollback has succeeded and 
      your data is in a stable state.
      533220

   o  Databases supported in Enterprise Server

      A list of databases supported is missing from the section "Container-
      managed Services" in the chapter "Introduction" of your Enterprise Server
      Configuration and Administration Guide. The list should follow the second 
      paragraph and should read:

        IBM DB2
        Oracle

   o  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 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. 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.

      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); 

   ==========================================================================
   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/////04/13 March 2007/nrV 
   Copyright (C) 1992-2007 Micro Focus (IP) Limited. All rights reserved.
 
