MQSeries Workflow 3.1.2 - Service Pack #2
-----------------------------------------

INDEX
------------------------------------------
	1. Installation of Service Pack #2
	   1.1 Installation on IBM OS/2
	   1.1 Installation on Microsoft Windows
	   1.2 Installation on IBM AIX
	2. Important Notices
	3. Changes
	   3.1 Changes in Hotfix #8
	   3.2 Changes in Hotfix #7
	   3.3 Changes in Hotfix #6
	   3.4 Changes in Hotfix #5
	   3.5 Changes in Hotfix #4
	   3.6 Changes in Hotfix #3
	   3.7 Changes in Hotfix #2
	   3.8 Changes in Hotfix #1
------------------------------------------


1. Installation of Service Pack #2
===========================================

1.1 Installation on IBM OS/2
-------------------------------------------

1.1.1 Which file must be downloaded?

         The Service Pack consists of several self-extracting executables.
         One for each National Language version of IBM MQSeries Workflow.
         Following the list of the self-extracting executables:

         O312ENU2.EXE   -  U.S. English language version including the common
                           files of MQSeries Workflow

         O312CHS2.EXE   -  Simplified Chinese language version
         O312CHT2.EXE   -  Traditional Chinese language version
         O312DAN2.EXE   -  Danish language version
         O312DEU2.EXE   -  German language version
         O312ESP2.EXE   -  Spanish language version
         O312FIN2.EXE   -  Finnish language version
         O312FRA2.EXE   -  French language version
         O312HEB2.EXE   -  Hebrew language version
         O312HUN2.EXE   -  Hungarian language version
         O312ITA2.EXE   -  Italian language version
         O312JPN2.EXE   -  Japanese language version
         O312KOR2.EXE   -  Korean language version
         O312NLD2.EXE   -  Dutch language version
         O312NOR2.EXE   -  Norwegian language version
         O312PLK2.EXE   -  Polish language version
         O312PTB2.EXE   -  Brazilian Portuguese language version
         O312PTG2.EXE   -  Portuguese language version
         O312SVE2.EXE   -  Swedish language version
         O312TRK2.EXE   -  Turkish language version

1.1.2 Unpack the file

        Copy the O312ENU2.EXE to a temporary directory and execute it
        using the command:

        O312ENU2 /D .

        This command unpacks the common files and the U.S. English files.

        If you need to update another language than U.S. English ("ENU"), you
        must copy the downloaded file to the temporary directory and execute
        it by the command:

        O312xxx2 /D .

        where 'xxx' is the language abbreviation.

1.1.3 Update your existing MQSeries Workflow installation

        To install this Service Pack, use the Install & Maintain icon
        in your MQSeries Workflow folder.

        1. Double-click on the MQSeries Workflow Install & Maintain icon
        2. Select FILE from the menu bar.
        3. From FILE select OPEN CATALOG.
        4. Select DRIVE.
        5. From the Drive list box, select the drive which contains the
           Service Pack.
        6. Use the SEARCH button to search for the catalog file
           FMCZIxxx.ICF of the Service Pack. It is located in the
           subdirectory 'xxx' where you have unpack the downloaded executable.
           Note: 'xxx' is the language used also with the downloaded
                 executable.
        7. Press OPEN.
        8. Select ACTION from the menu bar.
        9. From ACTION, select UPDATE.
       10. Select the UPDATE button.
       11. Reboot the system to activate the changes.


1.2 Installing the Service Pack on Windows NT and Windows 95
------------------------------------------------------------

1.2.1 Which file must be downloaded?

         The Service Pack consists of several self-extracting executables.
         One for each National Language version of IBM MQSeries Workflow.
         Following the list of the self-extracting executables:

         W312ENU2.EXE   -  U.S. English language version including the common
                           files of MQSeries Workflow

         W312CHS2.EXE   -  Simplified Chinese language version
         W312CHT2.EXE   -  Traditional Chinese language version
         W312DAN2.EXE   -  Danish language version
         W312DEU2.EXE   -  German language version
         W312ESP2.EXE   -  Spanish language version
         W312FIN2.EXE   -  Finnish
         W312FRA2.EXE   -  French language version
         W312HEB2.EXE   -  Hebrew language version
         W312HUN2.EXE   -  Hungarian language version
         W312ITA2.EXE   -  Italian language version
         W312JPN2.EXE   -  Japanese language version
         W312KOR2.EXE   -  Korean language version
         W312NLD2.EXE   -  Dutch language version
         W312NOR2.EXE   -  Norwegian language version
         W312PLK2.EXE   -  Polish language version
         W312PTB2.EXE   -  Brazilian Portuguese language version
         W312PTG2.EXE   -  Portuguese language version
         W312SVE2.EXE   -  Swedish language version
         W312TRK2.EXE   -  Turkish language version


1.2.2 Unpack the file

        Copy the W312ENU2.EXE to a temporary directory and execute it
        using the command:

        W312ENU2 /D .

        This command unpacks the common files and the U.S. English files.

        If you need to update another language than U.S. English ("ENU"), you
        must copy the downloaded file to the temporary directory and execute
        it by the command:

        W312xxx2 /D .

        where 'xxx' is the language abbreviation.

1.2.3 Update your existing MQSeries Workflow installation

        To install this Service Pack, switch to the subdirectory xxx which
        is located in the directory where you have unpacked the downloaded
        file.

        To start the installation of the Service Pack, run SETUP.EXE.


1.2 Installation on IBM AIX
------------------------------
        1) First stop all running MQSeries Workflow processes

        2) As root, perform the command 'slibclean'.

        3) Update your MQSeries Workflow 3.1.2.0 installation (with or without 
           having hotfixes applied) using smit - "update to latest level" to level 3.1.2.200.
           Note: Your configuration (profile "fmcrc", /home/fmc/..., /var/fmc/...) 
                 will not be modified by the update.

        4) Note for users which have a special installation setup ("security fix") applied:
           The access modification changes have to be re-applied now!

        5) As updated DB2 bind files are included in this package, the following 
           step has to be performed now:
                fmczdcdb -o:b
          Use the userid 'fmc' or any other userid with DB owner rights.

        Optionally you can perform the following step:

        6. Replace the existing MQSeries queue definitions by running the following commands:
           a. fmczqdef -o:d
              This rebuilds the customized queue definition files: fmczques.mqs and fmczcltc.mqs
           b. runmqsc <fmczques.mqs >csd2q.log
              This creates the new queue definition for the trigger monitor using the updated file fmccques.mqs
           c. runmqsc <fmczcltc.mqs >csd2c.log
              Create the channel definitions using the hotfix file fmcccltc.mqs file
           d. Start the trigger monitor using the command:
              runmqtrm -m FMCQM -q FMCTRIGGER

        and then start again the MQWorkflow servers.


2. Important Notices
===========================================
 o If the fmcemain fails to start, then we recommend to shutdown MQSeries Workflow. 
   Then you need to run the following commands as user fmc:
     - endmqm -i <queue manager name>, e.g. endmqm -i FMCQM
     - dltmqm <queue manager name>, e.g. dltmqm FMCQM
     - fmczqdef -o:i
   From now on you can start your MQSeries Workflow system as user fmc:
   strmqm <queue manager name>, e.g. strmqm FMCQM
   runmqtrm -m FMCQM -q FMCTRIGGER &, assuming FMC is the qualifier being used
   fmcamain &

 o Hotfix #4 is required for MQSeries Workflow/390

 o Starting with hotfix #3 the following MQSeries Workflow definitions have been changed:

   a.) Alias queue definition for the trigger monitor input queue does no longer refer to the
       SYSTEM.DEFAULT.INITIATION.QUEUE, but to the FMCTRIGGER queue which has been introduced.

   If this new resource definition has been applied, the MQSeries trigger monitor has to be
   started for MQSeries Workflow to use this dedicated trigger monitor input queue.
   (e.g. runmqtrm -m FMCQM -q FMCTRIGGER).

   The new MQ resource definition will become active as soon as you perform one of the
   following steps:

   a.) Create a new queue manager using FMCZQDEF utility with option -o:i
   b.) Whenever you run FMCZQDEF with -o:d option and running RUNMQSC manually to replace the
       resources
   c.) Whenever you run FMCZQDEF with -o:d option and later on with the -o:x option





3. Changes
===========================================
This Service Pack contains the fixes of hotfix package #1, #2, #3, #4, #5, 
#6, #7 and Hotfix #8. Hotfix package #7 and #8 are not available as a separat 
download. They are only available from this Service Pack.

The following APARs are fixed with this package: IX87658, IX88220, IY00484


3.1 Changes for Hotfix #8
------------------------------
1. PEA: consumes too much CPU on AIX ( PMR 20130 )

   PEA consumes too much CPU on AIX.
   The symptom is that 10 PEAs on midrange AIX system 
   cause the system to virtually hang.
   The problem was reported by Takahashi-san from IBMJP,
   as well as by Tower in Australia.

   Platform: AIX


2. Execution Server: trap in condition evaluation ( PMR15558 )

   Execution server trap in condition evaluation
   There is a bug in condition evalution which causes an internal 
   exception in the Runtime Server. The problem is that condition
   evaluation did not recover correctly when accessing the container
   of a dead-path eliminated activity resulted a 'container not found'
   code.

   Platform: independent of platform


3. Filter: TS should be local time ( PMR 02094 )

   Timestamps in filter strings should be interpreted as local
   time and converted to UTC for the use on server side.

   Platform: independent of platform


4. Database: Deadlock /w SQL Code -924 ( PMR 46044 )

   Platform: independent of platform


5. Execution Server: Filter Assertion in Execution Server ( PMR 23465 )

   *** Assertion failed in FMC.PT310SHP.INL#(FMCDSDF)(25543):
   *_parametersAsSql.PreDB2LOBWrite() == *rhs._parametersAsSql.P
   reDB2LOBWrite()
   Aborting ...
   CEE3204S The system detected a protection exception.
            From entry point fmckAssert(const char*,const char*,unsigned int) at
   compile unit offset +000002DC at address
             1F15E834.

   Platform: independent of platform


6. Import/Export: Format of exported FDL (record length)

   The export facility shoud not produce lines longer than 254
   characters. E.g. the user ids related to a role should not
   exported in a single row. The standard visible area on /390
   is up to 72 characters. 

   Platform: independent of platform



3.2 Changes for Hotfix #7
------------------------------
1. ActiveX: Endless loop when terminating process instances
  
   When the user terminated a process instance, the user interface hangs
   due to an endless loop. This is fixed now.

   Platform: WinNT, Win95


2. Buildtime: Cleanup_time is set to 0 when System settings are saved to DB 

   When making any changes in System and System Group but leaves the Cleanup Server
   settings unchanged (everything is inherited) for CLEANUP_TIME and CLEANUP_DELAY_TIME
   a 0 is written into the database and for DIST_RECEIVE_TIME the value ANYTIME is 
   written into the database.
   These three values should all be NULL when inherited is checked for Cleanup Server settings.  
   Although there are values in the database the GUI still shows the inherited flag!

   Platform: WinNT, Win95


3. ActiveX: Filters cannot be set

   If you create a new worklist and set the following filter:
          OWNER = QXGC3GC and STATE NOT IN Disabled
   and click OK to create the worklist, the worklist gets created correctly.

   If you then want to change the filter, you select Settings... from the
   worklist context menu.  This displays the Worklist properties dialog, where you 
   click on the Filter tab.  After doing so, you click on the Add button to 
   add another criteria and select NAME = MY ACTIVITY.  You click on OK and 
   then when you click OK on the Worklist properties dialog, the following 
   message appears:  fmcn6lpd (in the title bar), Invalid filter string, 
   expected 'FE 0; FE 1; FE 2' and found 'STATE'.  The only option is to 
   click OK and when you do that, you lose all filter criteria.

   Platform: WinNT, Win95


4. ActiveX: Cannot set substitute in GUI
   It was not possible to set the substitute in the RTC GUI. Now the
   read-only field was changed to an entryfield and the user can update
   (or remove) his substitute.

   Platform: WinNT, Win95


5. ActiveX: Terminate workitem not implemented

   You have to terminate a running workitem to be able to transfer ist.

   Platform: WinNT, Win95


6. V3 to V3.1 Migration: Wrong isolation level used during setup of runtime database.

   The database configuration tool FMCZDCDB didn't bind four of the packages with
   isolation level UR (Uncommitted Read). This resulted in a performance degradation.

   Platform: independent of platform


7. Staff Resolution: Apply staff resolution fixes of 3.2.0 to 3.1.2

   Platform: independent of platform


8. Buildtime: Buildtime fatal error after Hotfix #6

   Trying to open the diagram for an existing process a message box (title IBM
   MQSeries Workflow Version 3.1. Buildtime) came up with "FMC259699E:
      "Unknown error occured, more information:"
   After clicking OK second message box (title IBM MQSeries Workflow Version 3.1.
   Buildtime) having the message:
     "FMC259685E: For the object '<Template Name>' the connection to an FMC OCX
   returned an error. The error itself is so far unknown."
   After Ok button an empty Process Diagram was displayed.
   After closing the empty diagram, I got some other errors and a Runtime Error.

   Platform: WinNT, Win95


9. API: V312 CSD1, Client gets "1500: FMC_METHOD_EXCEPTION ...

   V312 CSD1, Client gets 
      "1500: FMC_METHOD_EXCEPTION ... ContainerElementArray::add "
   when starting a process instance requiring data entry at process start.
   Driver was installed from \\FMCNBLD\V312\INSTALL\NTFULL\ENU\...

   Platform: independent of platform


10. Samples: Cannot import sample FDL "fmclife.fdl"

   Sample FDL "fmclife.fdl" import results with two errors:
      FMC20315E fmclife.fdl(708): Syntax error; incorrect value in DataStructureMemberName: '_RC'.
      FMC20315E fmclife.fdl(713): Syntax error; incorrect value in DataStructureMemberName: '_RC'.

   Platform: independent of platform


11. Cleanup omission of NotesDB-update on CheckIn/Out

   CheckIn and CheckOut behave slightly differently now from the remaining
   Exmn... calls: if the NotesDBName is omitted for these two calls, the 
   "best" RC that can occur is "...ERROR_REPLICATION_INTERNAL" because 
   container data could not be mapped to/from the NotesDB.
   If an application for these calls really wants to ignore this RC, it 
   should explicitly do so. However, it should no longer unintentionally
   occur that mapping is omitted due to a missing NotesDB name.

   Platform: independent of platform


12. Execution Server: Restart of block which contains block activity does not work

   1) The audit trail writes out duplicate records (activity complete, block complete, 
       activity complete, block complete), and then rolls them back.
   2) The MQSWF Server Crashes.
   3) There's nothing in the fmc*.err logs.  However, in the db2diag, we see that the 
      FMCDB is getting a -803 (writing duplicate rows with the same key).

   Lines (1) and (3) seem to imply that something in MQSWF is looping wrong.

   Platform: independent of platform


13. Container Datastructures: Support () in addition to [] for array member referencing

   As there is no common Codepoint for brackets in EBCDIC-Codepages we can not use these
   brackets to scan in dooted container names on S/390. We will therefor have to
   allow parenthesis as well. This will have the following impact on out external behaviour:
      o In BuidTime you can use the both brackets and parenthesis to describe
        dotted names.
      o During checks of a process both brackets and parenthesis are allowed; 
        they will translate into the same semantikal meaning.
      o During upload to S/390 and the following conversation brackets will always
        be translatet into parenthesis. If you export an FDL from S/390 it will
        only have parenthesis.
      o In Container-API on the LAN-Plattforms we will accept brackets as well as
        parenthesis - during access, mapping and during evaluation of initial values.
        On S/390 we will only accept parenthesis.
      o While creating Container-API by Member-Names, these will will optain brackets
        on the LAN-Plattform and parenthesis on S/390.

   The following things will have to be changed in our components:
      o The Syntax-Checker will have to accept both brackets and parenthesis. They
        should appear paired, but do not have to.
      o The Container-Classes must be extended to the amount that it does understand
        brackets and parenthesis on LAN-Plattform and parenthesis only on S/390.
        While generating it should produce brackets on LAN and parenthesis on S/390
        Plattform.
      o The changes in the Syntax-Checker should enable all other components to 
        automatically accept the new syntax.

   Platform: independent of platform


3.3 Changes for Hotfix #6
------------------------------

1. Buildtime: Cannot draw a connector if part of the target activity is off paper

   The name or the exit condition of an activity may be off paper. In this case any connector
   cannot be attached to this activity.

   Platform: WinNT, Win95


2. Execution server: The _ACTIVITY field of a container does not contain the fully qualified name

   The data container member _ACTIVITY did not contain the fully qualified
   activity name (i.e. <block name>.<activity name>) but only the activity name itself.
   In FlowMark V2.3 the fully qualified activity name was contained in member _ACTIVITY.

   Platform: independent of platform

3. Buildtime: Insert datastructure member error

   If you deleted a member of a datastructure, it was not possible in some cases to
   insert a new member.

   Platform: WinNT, Win95

4. Buildtime: MQWF Data default connector problems

   Data mappings and setting default values do not work correctly for activities
   which have both a data loop connector and a data default connector. The mappings
   from and to other activities work ok, but not the mappings or defaults for the
   data loop connector and for the data default connector.

   Platform: WinNT, Win95

5. Execution server: 'Resume Process' for a certain process leads to exception.

   The problem occurs when during the resumption of a process instance a block is
   restarted since the block activity's exit condition evaluates to false.
   Execution Server shuts down with an assertion.

   Related message = FMC31050E An error has occurred which has terminated processing.
   Error location  = File=/home/fmcbld/lbld/v31_561/src/fmckdbg.cxx, Line=99,
   Function=fmckAssert(const  char*,const char*,unsigned int)
   Error data      = FmcAssertionException, Condition=*** Assertion failed in
   /home/fmcbld/lbld/v31_561/src/fmcdtgen.hxx(477): iterator != dict.end()

   or

   Related message = FMC31050E An error has occurred which has terminated processing.
   Error location  = File=/home/fmcbld/lbld/v31_561/src/fmckdbg.cxx, Line=113,
   Function=fmckInvariant(const char*,const char*,unsigned int)
   Error data      = FmcAssertionException, Condition=*** Invariant failed in
   /home/fmcbld/lbld/v31_561/src/fmcenabl.inl(166): _noFinishedEndActs <= _noEndActs


   Sample scenario for the problem:
   Have a running process instance with a running block that contains a running or
   checked-out program activity. Now process suspend is called. The process instance
   will become suspending, the block also, since the program activity is still executing.
   Now the execution server receives the program finish or checkin message from the client,
   i.e. the program activity becomes finished but no further navigation is performed since
   the process was in state supending, now in state suspended.
   When this process instance is resumed, the navigation must continue at the finished
   program activity by completing the block and evaluating the exit condition of the block
   activity. If the exit condition evaluates to false, the block activity will be restarted
   and the problem occurs.
   If the exit condition evaluates to true, the block activity will finish and control
   connectors leaving this activity will be followed.
   The problem would also not occur if the block becomes immediately suspended upon suspend
   request, i.e. skips the intermediate state suspending. The intermediate state suspendingis
   only reached when there are still running or checked-out  activities contained in the block.


   Platform: independent of platform

6. Buildtime: Data mapping in sub block shows datastructures of parent block

   It is not possible to map data from sources or to sinks in blocks which are
   nested more than one level deep. That is, data mappings in Process.Block work
   ok, but data mappings in Process.Block.SubBlock do not.

   Platform: WinNT, Win95

7. ActiveX: CheckOut Workitem implementation is in error

   CheckOut of Workitem was not correctly implemented. The local ProgramData object was
   destructed at the end of the CheckOut method. This lead to unpredictable results.

   Platform: WinNT, Win95

8. ActiveX: Problems with Passthrough and CreateList in ExecuteService

   A Runtime error message was displayed after execution of Passthrough method

   Platform: WinNT, Win95

9. Intermittent PEA crashes

   The PEA intermittently crashes if the Operating System environment contains
   unexpected entries (i.e. not in the form keyword=value). This is now fixed.

   Platform: independend of platform

10.Execution Server: Assertion failure in fmcenwid.cxx line 731

   During termination of a process instance the contained block activities are also terminated.
   During termination of a block activity the execution server (fmcemain) might fail with an assertion
   exception in file fmcenwid.cxx, line 731 (reported in error data of error FMC31050E
   in file fmcerr.log).

   Platform: independent of platform



3.4 Changes for Hotfix #5 
------------------------------

1. Execution server terminates with internal error FmcStream::ExcTruncated

   In special situations (depending on the process model and related runtime data) the
   execution server terminates with the internal error FmcStream::ExcTruncated. This
   internal error is logged in the error log (log accessible via administration utility or
   file fmcerr.log).

   Platform: independent of platform

2. Loop data connector in connection with a default data connector abends with an error

   Drawing a loop data connector and a default data connector for the same activity in the
   buildtime ends with an ODBC error.

   Platform: WinNT, Win95

3. Program Command Line Argument Problem with embedded spaces

   The program execution agent did not correctly reflect the quotes in the commandline.

   Platform: independent of platform

4. Problem with exporting deep

   The buildtime went in a loop if "export deep" was selected for exporting a FDL.

   Platform: WinNT, Win95

5. Wrong isolation level used during setup of runtime database.

   The database configuration tool FMCZDCDB didn't bind four of the packages with
   isolation level UR (Uncommitted Read). This resulted in a performance degradation.

   Platform: independent of platform


3.5 Changes for Hotfix #4 
------------------------------

1. Export deep doesn't export nested datastructures


   If "export deep" was selected in buildtime, nested datastructures have not
   been exported. This problem is solved with this hotfix.

   Platform: WinNT, Win95

2. Error in MQ listener when closing RTC

   When RTC is closed, the MQ TCP/IP-listener window reports the following error:

   12/10/98  14:13:16 AMQ9208: Error on receive from host 'et (9.164.7.233)'.
   12/10/98  14:13:16 AMQ9999: Channel program ended abnormally.

   This problem has been solved with this hotfix.

   Platform: WinNT, Win95


3.6 Changes for Hotfix #3
------------------------------

 1. ForceFinish/Finish of an activity contained in a block might fail under certain conditions

    If the ForceFinish or Finish work item request results in a block restart scenario of the
    surrounding block (i.e. the exit condition of the corresponding block activity is not met
    and therefore the block is started anew), the excecution server might fail with an assertion
    (Finish: fmcecosa.cxx, line 1916, ForceFinish: fmcecosa.cxx, line 2173).

    Platform: independent of platform

 2. Restart of block which contains block activity does not work

    If a block which contains other block activities is restarted, it fails with FmcTOMNotUniqueException.
    This unrecoverable exception leads to the server shutdown. (Error location: fmcdbact.sqx, Line=11855)
    In addition this defect caused database records to be not deleted. It is therefore strongly
    recommended to apply this hotfix package.

    Platform: independent of platform

 3. AIX: Profile directory must not be hard-coded to /home/fmc

    A profile search algorithm has been added for AIX that searches for the machine profile fmcrc in
    /var/fmc/<system qualifier> if /home/fmc contains no profile or does not exist.

    Platform: AIX

 4. Select random user for automatic program activities.

    If a set of users is resolved to execute an automatic program, the user that receives the
    activity should be selected randomly. Currently there is a bug, that selects always the
    same user.

    Platform: independent of platform


3.7 Changes for #2
------------------------------

1. Data mapping to Sink not saved, if there are several connectors

   If a sink had more than one incoming data connector the mapping of the data
   members was not saved. This problem is solved with this hotfix

   Platform: WinNT, Win95

2. Mapping from input to output container not implemented

   Mapping from input to output container of the same activity (default data mapping)
   was not supported in the Runtime, but could be specified in Buildtime and FDL. This
   now supported with this hotfix.

   Platform: independent of platform

3. Exception in methods 'NewWorkitem' and 'PersistentObject' of Workitem.

   When you use the ActiveX APIs 'NewWorkitem' and 'PersistentObject' of the
   object 'Workitem', you will get an exception without this hotfix.

   Platform: WinNT, Win95

4. Unable to map _PROCESS_INFO from source to activity

   Using of _PROCESS_INFO members in data container mappings resulted in error
   "26530: Translate of process '...' failed. See file 'XLATE.LOG' for details."
   This file contained the message
   "Mapping error: source member _PROCESS_INFO (...) do not match"

   This problem is fixed with this hotfix.

   Platform: independent of platform

5. CHECKED_OUT SQL filter value not correctly handled.

   Creating a worklist with STATE = CHECKED_OUT filter or using
   this filter in a query led to a wrong result (mostly empty results).
   This was due to the fact that the generated SQL statement queries for workitems
   were generated with state = 0 (undefined) instead of state = 64 (checked_out).
   With this hotfix the correct results are now returned.

   Platform: independent of platform

6. Notification from input container not exported to FDL.

   When the 'Notification from predefined members' checkbox on the Notification
   page of the Program Activity property sheet was checked in buildtime this was
   not exported to FDL.

   Platform: WinNT, Win95

7. FMCIBIE does not accept full OS2 PATH_AND_FILENAME

   PATH_AND_FILENAME for a OS/2 program object could only be specified using
   a simple name. A fully qualified path was rejected with a syntax error. With
   this hotfix the full path can be used.

   Platform: FDL definition independent of platform on which it is imported

8. Scoped data structure members not accepted in exit conditions

   Data members other than of the current activity or immediate preceeding activities
   were not accepted in exit conditions.

   Platform: WinNT, Win95

9. Enable trusted flag in buildtime

   A "Trusted" check-box is added to the Domain, System Group, System and Program property
   sheet in the Buildtime.

   Platform: WinNT, Win95

10.Block restart does not work in specific cases

   When an end activity which triggered the block restart was also a start activity of
   this block (e.g. scenario with only one activity in a block), the block restart would
   fail.

   Platform: independent of platform

11.In runtime client you cannot delete automomous subprocesses

   Automomous subprocesses could be deleted in the client, only the top level process
   could be deleted. When you apply this fix, the 'Delete' and 'Terminate' menu entries
   are also enabled for subprocesses.

   Platform: WinNT, Win95


3.8 Changes for Hotfix #1
------------------------------

If you encounter one of the three problems listed below you can get an early fix if you install
the provided hot fix. It is recommended to apply the hotfix only if you urgently need the solution
for one of these problems:

Note: The hotfix applies ONLY to MQSeries Workflow Version 3.1.2


1.   DLLs as activity implementation cannot be loaded by the PEA on OS/2

Description:  If you have defined an activity implementation as DLL (e.g. mydll.dll) the program execution
              agent cannot load this DLL. The hotfix solves this problem.
Workaround:   none
Platform:     OS/2
Component:    Program execution agent
Evaluation:   Apply the hotfix if you intend to run OS/2 activity implentation DLLs.
              The hotfix must be applied to all workstations on which the PEA runs.


2.  API calls ExmcGetSessionID() (FlowMark 2.3 compatibility API) and FmcjProgramID()
    return no sessionID/programID

Description:  These API calls do not return a sessionID/programID. This leads to
              problems when an activity implementation tries to access its container.
Workaround:   none
Platform:     All
Component:    PEA and API
Evaluation:   With MQSeries Workflow Version 3.1.2 an activity implementation
              gets a sessionID/programID from the PEA only if the program
              registration has set the TRUSTED attribute. Currently you cannot
              modify the TRUSTED attribute of a program in the Buildtime. You need
              to modify the FDL before importing it into the runtime database.
              You can define a default value for the TRUSTED attribute of all programs
              in the PROGRAM part of the reference FDL. For each program you can also
              specify an individual value (TRUSTED or NOT TRUSTED) in its
              program definition part.
              In addition to this configuration work the hotfix must be applied to all
              workstations on which the PEA runs.


3. Audit Trail writes starter of process instead of starter of activity for events 21007, 21011, 21032, 21041

Description:  The userid in these audit events is not set correctly for automatic activities.
              It contains the ID of the user, who started (or created and started) the related process,
              and not the starter of the activity. The event affected are:
                        21007 ActivityStarted
                        21011 ActivityEndedNormally
                        21032 ActivityImplCompleted
                        21041 ActivityRestarted
Workaround:   none
Platform:     All
Component:    Execution server
Evaluation:   Apply the hotfix if you need the correct userIDs e.g. for your accounting.
              The hotfix must be applied to the workstation on which the execution server runs.



4. Data members which are not set are no more considered during data mapping

If a data mapping is specified from one container to another, data members that
are not set are no more mapped to the target container.
E.g. if multiple containers are mapped to one target container only data
members where a value is set are mapped in order to avoid that data members
that are not set override valid values from other source containers.