Description:
Product Name    : TIBCO iProcess Engine (SQL)
Release Version : 10.6.2-Hotfix01
Release Date     : May 2008

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

This hotfix applies to the TIBCO iProcess Engine, version 10.6.2
running on the following platforms and databases:

  Sun SPARC; Solaris 8-10; Oracle 10g
  Sun SPARC; Solaris 8-10; Oracle 9i
  Intel Pentium x86; Linux; Oracle 10g
  Windows 2000/2003; Oracle 9i (32 bit)
  Windows 2000/2003; Oracle 10g (32 bit)
  Windows 2000/2003; SQL Server 2000/2005

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

Closed Issues in 10.6.2-Hotfix01

Defect Id: MR 35054 (Parent MR 34142)

   Jumpto with a specific sub-procedure step is not working. Also,
   dynamic sub-procedure is not started when EVENT updates the data
   (and sub procedure does not exist).

Defect Id: MR 35049 (Parent MR 32462)

   If a field is set to SW_NA by a script, the field is blanked but
   not set to SW_NA.
  
Defect Id: MR 35036 (Parent MR 34451)

   An invalid year (prior to 1900) in a script causes the BG process
   to hang.

Defect Id: MR 34440

   A new configuration flag is needed in the staffcfg file to define
   how predicted step duration is to be calculated.
      
   Implemented.  A new flag has been added to the staffcfg file as
   follows:
  
   Flag: DYNDEADPRED
   Section: STAFF
   Default Value: 1
   Unit: n/a
   Range: 0 or 1
   Description: Defines how the predicted step duration is to be
   calculated.
   Tuning:
   If the value is 1, then if the ‘Use Deadline for Step Duration’
   flag is set then use the deadline as the predicted duration,
   otherwise, use either the configured duration or the deadline
   depending on which would elapse first.
  
   For example, if the deadline was set to expire in one hour and
   the duration was set to three hours then the deadline would be
   used for the predicted duration.
   Conversely if the deadline was set to expire in three hours and
   the duration was set to one hour then the duration would be used
   for the predicted duration.

   If the value is 0, then if the ‘Use Deadline for Step Duration’
   flag is set then use the deadline as the predicted duration,
   otherwise use the configured duration for the predicted duration.

Defect Id: MR 34431 (Parent MR 33126)
  
   Cannot login to iProcess Engine if non default (non DES) encryption
   is set in OS.
  
Defect Id: MR 34430 (Parent MR 33838)

   iProcess Objects can crash with a memory allocation error.
  
Defect Id: MR 34234

   LDAP not working with Windows Active Directory 2003.

Defect Id: MR 33834 (Parent MR 33387)

   Cannot call TIBCO Rendezvous from iProcess Java Plug-in steps.

Defect Id: MR 33833 (Parent MR 33175)

   SAL refresh one queue optimisation only works for own queue
   (sal_queue_getqueue_info32() with negative index).
  
Defect Id: MR 33832 (Parent MR 32638)

   ioctl call from get_myaddress can fail on HP - causing RPC
   processes to crash.
  
Defect Id: MR 33808

   LDAP Search with referral to domain name returns fatal error
   MACHINE_DOWN in 10.6.0. Earlier versions would return
   PARTIAL_RESULTS.
  
Defect Id: MR 33791

   If you attempt to withdraw an EAIORCH type step, then the BG will
   fail to process the transaction.

Defect Id: MR 33389

   There is a problem in the setting up of a connection to IAP from
   the BG process.

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

Known Issue

  This issue only applies to some installation scenarios.
  
  The default installation path for TIBCO Rendezvous has changed and
  the path of /opt/tibco/tibrv as described in the TIBCO iProcess
  Administration guide should now have /8.1 appended to it so that it
  becomes:

    /opt/tibco/tibrv/8.1

  You will also need to edit the smserv.bat (for Windows) and
  $SWDIR/bin/smstart and $SWDIR/bin/smstop scripts (for UNIX) in order
  to start the iProcess Web Server.    

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

Restrictions

Defect Id: MR 34352

   Summary: A limitation exists whereby even though iProcess Engine
   now works with Active Directory 2003, referral points cannot be
   specified. This is due to Active Directory 2003 having (by default)
   objects which iProcess Engine tries to use as referrals.
  
   Workaround: None.  

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

NOTE: See attached readme document for installation instructions.

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

The TIBCO iProcess Engine (SQL) 10.6.2 HotFix 01 can be downloaded from our support-ftp.tibco.com. You will be able to download by clicking on the link below after you provide your TIBCO Support Web username and password in the url:

                     ftp://username:password@support-ftp.tibco.com

Directory path:
available_downloads/StaffwareProcessSuite/iProcess/engine/10.6.2/hotfix-01

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

TIBCO iProcess Engine (SQL) 10.6.2 HotFix 01 is available.

Product: TIBCO iProcess Engine (SQL) Version: 10.6.2 OS: --------------------