IMPORTANT WARNING: Please note that the release notes below are divided into 
two sections.  The first section describes fixes specific to Gentran:Server 
for Windows product, whereas the second describes fixes associated with the 
Common Component Translator shared with other Gentran products.

To ensure you understand all the changes affecting your product version for 
a given patch number, you need to review both sections.


=========================================================================
                         PATCH RELEASE NOTES
        IBM® Sterling Gentran:Server® for Microsoft Windows 5.3.1
        		       Patch 2
=========================================================================


**************************************************************************
                                 PATCH 1
**************************************************************************
_______________________________________________________________________________

RTC DEFECT: 	351228
APAR:		IC87515  		
DATE:		10/26/2012
MODULE:		Commpost.exe      

PROBLEM DESCRIPTION:  When Commpost attempts to process bad data it attempts to retry processing that data 5 times.
This can cause Commpost to continue attempting to process the bad data for an inordinate amount of time and consume large amounts of memory.

FIX DESCRIPTION:  Have the default remain at 5 however have an override set in the registry so the customer can set it to a number they would like to have.  
This registry setting is named CommPostMaxRetryCount and is a DWORD entry and defaults to 5.  
It is stored under the following registry key:
32-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\<VERSION NUM>\Systems\<SYSTEM NAME>
64-bit OS: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sterling Commerce\GENTRAN\Server\<VERSION NUM>\Systems\<SYSTEM NAME>
When Commpost runs it attempts to read this value in and use it as the Max retry count, if it does not find it, it creates the value and sets it to 5.


_______________________________________________________________________________

RTC DEFECT: RTC 343543
APAR:   IC87657
DATE:       10/30/12    
MODULE:     gntstart.exe 

PROBLEM DESCRIPTION:  Some commands are unable to execute in 64-bit OS through GNTStart and Unattend from command line



FIX DESCRIPTION:  Added code to fix the physical GSW login portion for when the silent signon fails.  This was not previously working so even
when the user was prompted to login on Win7 or Server 2008, the DSN information was not being set correctly and genstart could not access it.
Also added code to allow for gntstart to exit correctly if it can not access the DB.  This was causing gntstart to crash.




_______________________________________________________________________________

RTC DEFECT:	354271
APAR:   	IC87651
DATE:      	10/30/12   
MODULE:    	Partnred.exe   	

PROBLEM DESCRIPTION:  In the Partner Editor's Outbound Interchange dialog, when you uncheck the "Use the default Mailbox and
E-mail Address" checkbox, the "Set Max Number of Documents per Interchange" checkbox unchecks also.

FIX DESCRIPTION:  An UpdateData command to retrieve the current values of the dialog controls was missing in the if-else 
clause.  Moved it to the start of the function.


_______________________________________________________________________________

RTC DEFECT: 353247
APAR: IC87818
DATE: 10/31/12       
MODULE: tx32.exe (GNTXBASE.lib)

PROBLEM DESCRIPTION: Outbound document has duplicate Document Name checking turned on but no warning message is received in the audit log. 



FIX DESCRIPTION:  Updated duplicate document checking on outbound documents to   
write to the same error message to the Audit Log that we'd get 
when recieving duplicate inbound docs.                         
                                                               



_______________________________________________________________________________

RTC DEFECT:	352952
APAR:   	IC87997
DATE: 		11/7/2012
MODULE:       	Commpost.exe

PROBLEM DESCRIPTION:  In CommPost, When data comes in with unprintable terminators it causes compost to hang.


FIX DESCRIPTION:  In CommPost, when a UNB segment is detected and the segment terminator defined in the Splitter table is not found in the data,
we now flag the interchange as bad, write an Audit message and continue processing the file.



_______________________________________________________________________________

RTC DEFECT: 348251
APAR: IC88106 
DATE: 11/9/2012      
MODULE: GNTXBase.lib      

PROBLEM DESCRIPTION: Pad character outputs as space instead of "0" for empty numeric fields in Export maps


FIX DESCRIPTION:  Added check condition in export translation to look for new "PadFillEmptyNum" DWORD value in registry.  
If it does not exist, we create it and set it to "0".  If it exists and is "0", we pad empty numeric map segments 
using the default setting which is spaces.  Otherwise, if it's set to "1", we pad with the pad character the customer has specified.
This registry key cannot be changed through the UI and must be manually changed in the registry.  This key is located in:
32 bit OS: HKLM \ SOFTWARE \ Sterling Commerce \ Gentran \ Server \ <Version Num Folder> 
64 bit OS: HKLM \ SOFTWARE \ Wow6432Node \ Sterling Commerce \ Gentran \ Server \ <Version Num Folder> 



_______________________________________________________________________________

RTC DEFECT:   360899
APAR:         IC89935
DATE:         12/21/12
MODULE:       ANServer.exe

PROBLEM DESCRIPTION:  5.3.1 Audit service crashes during service startup sequence.  It was fine after a fresh install, but 
it suddenly started crashing after several days of processing.

FIX DESCRIPTION:  Symptom only occurred whenever DataAuditLog_tb database table had invalid 10-digit event IDs.  Fixed
ANServer so that it could accomodate valid 10-digit event IDs.


_______________________________________________________________________________

RTC DEFECT:     362804
APAR:   	IC89518
DATE:         	1/14/2013
MODULE:         BRK997 Map

PROBLEM DESCRIPTION: ERROR - 0121 Too Many Elements when processing inbound 997 005010 for the AK1 segment. 


FIX DESCRIPTION:  Brk997 map was missing the AK103 element which is an option element that was added in standard version 004041.  This was added to
the brk997.map which can be found in the support folder of the patch install under:  
     Maps > Special > Source > Brk997_AK103.map.  

The tpl file can be found in the support folder under: 
     Maps > Special > Compiled > brk997_AK103.tpl.  

Support also changed the min field value on the output side of the map for fields 10 & 12 from 1 to 0.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: THESE SYSTEM MAPS WILL NOT BE INSTALLED BY THE PATCH INSTALL.  
YOU MUST GO THE SUPPORT FOLDER AND REGISTER THE TPL FILES MANUALLY
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Please Note: brk997_AK103.tpl and Brk997_AK103.map were removed from the corresponding Special subfolders due to later RTC defect 372073. 
The AK103 functionality can be found in the most recent brk997.tpl and brk997.map.


_______________________________________________________________________________

RTC DEFECT:	363982
APAR:   	IC89748
DATE:         	1/22/2013
MODULE: 	Aleserver      

PROBLEM DESCRIPTION:  During ALEServer We are reporting: Check_TID: Update the TID-Management failed, instead of a Check_TID: Lock the TID-Management
failed, when the aleserver.lck retry attempts exceed 60.



FIX DESCRIPTION:  Changed error reporting for Check_TID to report TID_ERROR_LOCK instead of TID_ERROR_UPDATE when the AleServer can not attain a lock
on the TID file.




_______________________________________________________________________________

RTC DEFECT:   362017
APAR:   
DATE:         1/31/13
MODULE:       tx32.exe (gntxbase.lib)

PROBLEM DESCRIPTION:  The Export to Mailbox process is generating 10-digit event IDs in DataAuditLog_tb which was causing the 
5.3.1 Audit service to crash on startup.

FIX DESCRIPTION:  Passed in event ID to Mailbox API calls.  Without it, the event ID in the Mailbox interface was uninitialized 
resulting in the 10-digit values.


_______________________________________________________________________________

RTC DEFECT:  364201
APAR:   
DATE:  	     02/01/2013       
MODULE:      BLD997.map      

PROBLEM DESCRIPTION:  BLD997.MAP does not have the AK103 element (0480) to populate the GS08 version


FIX DESCRIPTION:  BLD997 map was missing the AK103 element which is an option element that was added in standard version 004041.  This was added to
the BLD997.map which can be found in the support folder of the patch install under:  
     Maps > Special > Source > BLD997_AK103.map.  

The tpl file can be found in the support folder under: 
     Maps > Special > Compiled > BLD997_AK103.tpl.  


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: THESE SYSTEM MAPS WILL NOT BE INSTALLED BY THE PATCH INSTALL.  
YOU MUST GO THE SUPPORT FOLDER AND REGISTER THE TPL FILES MANUALLY
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



_______________________________________________________________________________

RTC DEFECT:   366092
APAR:         IC90423
DATE:         2/25/13
MODULE:       Edimgr.exe

PROBLEM DESCRIPTION:  The 5.3.1 Interchange Browser and External Data Browser are not displaying external data correctly for
outbound interchanges.  Only 1 or 2 bytes of garbage is displayed instead of the actual contents of the .int file.

FIX DESCRIPTION:  When the contents of the .int file was being read into a temp buffer, the data type conversion wasn't being
done properly.  Fixed.


_______________________________________________________________________________

RTC DEFECT:   368383
APAR:         IC90579
DATE:         2/28/13
MODULE:       Commmpost.exe, AuditMsgFile.xml

PROBLEM DESCRIPTION:  5.3.1 commpost crashing when EDI splitter entries had NULL values in the RepeatingElementDelimPosn 
database column.

FIX DESCRIPTION:  Added check to EDI splitter to validate the RepeatingElementDelimPosn value retrieved from the database.  
If the variable is less than 0 or greater than 200, it gets reset to 0 and a new warning audit is written to the Audit Log 
(1-6-1683: "Splitter - the RepeatingElementDelimPosn value for the [start tag] splitter entry is invalid. The Splitter 
value Rep Elem has been temporarily set to 0 (not used) for this transaction. Please update the Splitter configuration to 
prevent further warnings.")


_______________________________________________________________________________

RTC DEFECT:   357241
APAR:         IC88643
DATE:         3/14/13
MODULE:       Commpost.exe

PROBLEM DESCRIPTION:  When an inbound file with multiple interchanges comes in with unprintable terminators (0x0D as segment 
terminator) for some interchanges, commmpost is unable to split the interchanges properly and it causes translator to hang.

FIX DESCRIPTION:  Issue was due to a previous fix for Vantive SR#1343740 that did not anticipate 0x0D would be used in the
data as segment terminators.  Rolled back that fix.


_______________________________________________________________________________

RTC DEFECT:	371623
APAR:   
DATE:    	3/25/13     
MODULE:       	BRK999.MAP, BRK997.MAP, BRK997_AK103.map, Bld997t.map

PROBLEM DESCRIPTION:  The following break maps were not adjusted correctly to correspond with the PartnerKey expansion of GSW 5.3.1.  The BLD997_AK103 map was corrupted and would not open in the 
map editor.


FIX DESCRIPTION:  Expanded all partnerKey fields in the maps to the new length of 25 chars. The 
BLD997_A103 was also replaced and the .tpl file rebuilt to keep the file date consistant.  These 
maps can be found in the support folder of the patch install under:
	Maps > INSTALL> Source > BRK999.map
	Maps > INSTALL> Source > BRK997.map
	Maps > INSTALL> Source > BLD997t.map
	Maps > Special > Source > BRK997_AK103.map 
	Maps > Special > Source > BLD997_AK103.map

The tpl file can be found in the support folder under:
	Maps > INSTALL> compiled> BRK999.tpl
	Maps > INSTALL> compiled> BRK997.tpl 
	Maps > INSTALL> compiled> BLD997t.map
     	Maps > Special > Compiled > BRK997_AK103.tpl 
	Maps > Special > Compiled > BLD997_AK103.tpl


!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: THESE SYSTEM MAPS WILL NOT BE INSTALLED BY THE PATCH INSTALL.  
YOU MUST GO THE SUPPORT FOLDER AND REGISTER THE TPL FILES MANUALLY
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!




**************************************************************************
                                 PATCH 2
**************************************************************************

RTC DEFECT:   370537
APAR:         IC91066
DATE:         3/21/13   
MODULE:       SCEMailGateway.dll   

PROBLEM DESCRIPTION:  When using the new 5.3.1 Email Gateway 'Send as attachment' feature, the email that is sent has "This is 
the body of the message" in the message body and cannot be changed.

FIX DESCRIPTION:  Added new edit field control to Email Gateway mailbox properties dialog that allows users to specify the 
contents of the message body when sending messages with "Send as attachment" selected.


_______________________________________________________________________________

RTC DEFECT:   372089
APAR:         IC91356
DATE:         4/4/13   
MODULE:       Unattend.exe

PROBLEM DESCRIPTION:  5.3.1 Unattend.exe crashes when GDW_Document_Rpt (or any other Process Control command) uses the 
Date/Age parameter.  

FIX DESCRIPTION:  Newer Microsoft classes used in 5.3.1 now throw exceptions when trying to create a time object with the hours 
parameter to set 24. Fixed so that the time object is created first then incremented by one day.


_______________________________________________________________________________

RTC DEFECT:   371636
APAR:         IC91433
DATE:         4/10/13   
MODULE:       Commpost.exe   

PROBLEM DESCRIPTION:  When processing a custom file layout that contains a single line item, will get a 'No valid interchanges 
Processed' error but it works fine if there are two or more lines.  This problem only occurs with the Variable Position formats.

FIX DESCRIPTION:  The customer's variable position splitter entry had a 'max length of start segment' value that was greater than
the total size of the data file (minus the CR/LFs).  That splitter value was not a typo since it matches what's indicated in their
maps.  Added code to check for the end of the file when it reads in the max length amount of data.


_______________________________________________________________________________

RTC DEFECT: 369668  
APAR: IC91537
DATE: 4/16/2013        
MODULE: aleserver.exe      

PROBLEM DESCRIPTION:  SAP IDoc Control Record could be partially overwritten with aleserver trace file "Established connection" message, when running 
aleserver with the "-interval" command line argument, or with the "Set timer for checking the connection" in the SAP configuration configuration UI.  
The probability of the symptom frequency increased as the duration between connection checks decreased.  

FIX DESCRIPTION:  Removed buffer overwrite potential between threads, when communication thread reestablishes connection with SAP while transaction thread 
receives an IDoc.  


char array for error log messages and Idoc buffering between IDoc writes.  Issue was reported when connection was checked every ten seconds.
_______________________________________________________________________________

RTC DEFECT:   373109
APAR:         IC91946
DATE:         4/29/13
MODULE:       _Gsbrk2DivSR.map, _Isabrk2DivSR.map, _Stbrk2.map, GNTXEng.exe (gntxbrk.lib)

PROBLEM DESCRIPTION: (1) Bad ISA data processes for 2 hours and creates 120,000+ 0 byte .doc files.  (2) Side issue: 3-1-1740 
audit message is not displaying the partner name at the interchange level: "Translator: 1 compliance errors detected for 
interchange 000050409 from ".

FIX DESCRIPTION:  (1) The _2 ISA break maps didn’t account for bad data between envelopes.  Modified the break maps by adding a 
record to catch bad data.  (2) Audit message was written before partner lookup was done.  Moved partner lookup before the audit
call.


_______________________________________________________________________________

RTC DEFECT:   373127
APAR:         IC91778
DATE:         4/29/13
MODULE:       sapint

PROBLEM DESCRIPTION: The program sapint.exe with -POSTPROC argument did not populate either of the EDI_DC* record fields SNDPOR or RCVPOR.

FIX DESCRIPTION:  Populate the fields SNDPOR and RCVPOR in the EDI_DC* header record from the sapconfig_tb when executing sapint with the -POSTPROC argument.


_______________________________________________________________________________

RTC DEFECT:  RTC 374460
APAR: 	     IC91937  
DATE:        5/6/2013        
MODULE:      EDIMGR.exe      

PROBLEM DESCRIPTION: Closing Document browser window causes Edimgr.exe to crash 



FIX DESCRIPTION: Our temp file cleanup routine would mistakely try to delete a temp file again after it had already been deleted.  We have adjusted our 
cleanup routine and now correctly move from one file in the list to the next in our list.




_______________________________________________________________________________
RTC DEFECT:     374003 
APAR:   	IC92537
DATE:         	5/17/2013
MODULE:         TxAckGen.dll

PROBLEM DESCRIPTION:  Inbound file processing with acknowledgment generation causes error in txackgen.dll and crashes Gentran.  



FIX DESCRIPTION:  TxAckGen.dll would fail if the ack type was NULL in the ack generation process.  As part of a previous fix for AK5 / IK5 error reporting in 999s & 997s, 
we check our ack type for specific error reporting.  If our ack type is NULL, this check fails.  Added code to skip this check if our ack type is null since it's only 
needed for 997s & 999s.  




_______________________________________________________________________________
RTC DEFECT:	373868
APAR:           IC93737
DATE:   	5/17/2013      
MODULE:       	TX32.exe

PROBLEM DESCRIPTION:  Importing outbound documents into GSW causes TX32.exe to crash.  



FIX DESCRIPTION:  TX32.exe was crashing when trying to import outbound documents into the workspace causing GNTXEngine to enter a retry loop reprocessing the inbound file.  This crash was a result of Microsoft changing their CTime class to use a new _maketime64 function in the newer compilers (VS2005 and up).  The import process uses CTime to set a number of time variables, one of those being a check value of Jan 1, 1970 @ 00:00.  This new MFC _maketime64 gets the sytem's time zone, then either adds or subtracts time from this value because it now assumes the value being provided is 00:00 GMT.  If your time zone is UCT 01:00+ to UCT 13:00+, this will subtract time from this value invalidating it causing a runtime exception. To resolve this we adjusted our check value to Jan 2, 1970 @ 00:00.  Customers in these time zones trying to import docs into their workspace will experience this issue as well.




_______________________________________________________________________________

RTC DEFECT:	375138
APAR:   	IC92265
DATE:         	5/10/2013
MODULE:       	BLD997Partial&Rejectcodes.map

PROBLEM DESCRIPTION:  BLD997Partial&Rejectcodes.tpl printing 000 at the end of the AK109 segment



FIX DESCRIPTION:  Rebuilt and compiled Bld997Partial&RejectCodes.map & .tpl which resolved this issues.  These new break maps and tpls will be found in the support folder of the patch install under: 

Maps > Special > Source:  BLD997PARTIAL&REJECTCODES.MAP

Maps > Special > Compiled:  BLD997PARTIAL&REJECTCODES.TPL

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: THESE SYSTEM MAPS WILL NOT BE INSTALLED BY THE PATCH INSTALL.  
YOU MUST GO THE SUPPORT FOLDER AND REGISTER THE TPL FILES MANUALLY
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



_______________________________________________________________________________

RTC DEFECT:	372073
APAR:   
DATE:           5/19/2013
MODULE:         997 Build / Break maps

PROBLEM DESCRIPTION:  All Brk997.maps & Brk997.tpls need to be updated with AK103 element just like BLD997_AK103.map (RTC#364201).



FIX DESCRIPTION:  Updated all BRK & BLD 997's with AK103 element.  New build maps and tpls labled _AK103 will be found in the support folder of the patch install under:

Maps > Special > Source:  BLD997PARTIAL&REJECTCODES_AK103.MAP, Bld997t_AK103.MAP, Bld997_UE_AK103.MAP

Maps > Special > Compiled:  BLD997PARTIAL&REJECTCODES_AK103.TPL, Bld997t_AK103.TPL, Bld997_UE_AK103.TPL


The BRK maps & tpls have all been modified to include this as a conditional element and won't affect translation of
data if the element is not present.  Because of this, there are no special BRK maps or tpls labeled as _AK103. (The Brk997_AK103.map and .tpl from RTC#362804 have been removed.)
These new break maps and tpls will be found in the support folder of the patch install under: 

Maps > Install > Source:  Brk997u.map, brk997.map, brk997t.map

Maps > Install > Compiled: Brk997u.tpl, brk997.tpl, brk997t.tpl

Maps > Special > Source: Brk997_2.map, Brk997_3.map, Brk997u_2.map, Brk997u_3.map

Maps > Special > Compiled: Brk997_2.tpl, Brk997_3.tpl, Brk997u_2.tpl, Brk997u_3.tpl

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: THESE SYSTEM MAPS WILL NOT BE INSTALLED BY THE PATCH INSTALL.  
YOU MUST GO THE SUPPORT FOLDER AND REGISTER THE TPL FILES MANUALLY
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


_______________________________________________________________________________

RTC DEFECT: 	377817
APAR:           IC92525
DATE:       	5/22/2013        
MODULE: 	AuditLog.exe

PROBLEM DESCRIPTION:  The Audit Log Date/Time column could display corrupted dates.  This would occur if
the Regional Settings in the Contol Panel differred from the Regional Setting of the DB server and the 
Date Time Format of the DB was not the same as the system running GSW.  



FIX DESCRIPTION:  If the attempt to format the date/time fails, as described above, display the date/time 
string provided by the DB without formating or adjusting for the current locale or user format preferences.




_______________________________________________________________________________

RTC DEFECT:   348235
APAR:   
DATE:         5/30/13
MODULE:       RpcSrv.exe, Mercury.exe, Unattend.exe, Proccntl.exe, Config.exe, InstallDll, patch install

PROBLEM DESCRIPTION:  A new enhancement has been done that extends the Inbound/Outbound Recovery process that normally runs every
time the Gentran Executive service starts up.  

FIX DESCRIPTION:  (1) Added a new Process Control system event (System-MBRecovery) that executes the recovery process daily.  
(2) Added the option to set an upper limit to the number of mailbox messages that can be recovered in a session or at service 
startup.  (3) Added the option to disable recovery at service startup.  The new recovery unattend event can also be disabled too.
(4) Added a new tab (Recovery) to the System Configuration app that has these new settings for recovery at service startup.  
The settings for the recovery unattend event are configured in Process Control.

If you want to revert back to the previous default behavior for recovery, you'll need to (1) disable the recovery unattend event 
and (2) go to the Recovery tab in Config and select the 'recover all messages' options for both inbound and outbound.


_______________________________________________________________________________
RTC DEFECT:	380707
APAR:   	IC92999 
DATE:         	6/12/2013
MODULE:       	MClient.exe

PROBLEM DESCRIPTION:  The default Mailbox message attachment viewer is hardcoded to be c:\Windows\Notepad.exe.
Notepad.exe does not exist in this location on Windows 2008 OS.  



FIX DESCRIPTION:  The absolute path was removed the default Mailbox message attachment viewer.  Notepad.exe is 
now called directly, relying on the Windows Path to locate the Notepad.exe in the Windows Path.  This will be in
either C:\Windows, C:\Windows\System32, or C:\Windows\SysWOW64




_______________________________________________________________________________

RTC DEFECT:   376817
APAR:         IC93689
DATE:         6/24/13
MODULE:       Edimgr.exe, ArchiveManager.exe, Commpost.exe, ProcCtrl.exe, tx32.exe

PROBLEM DESCRIPTION:  Customer's client users are not allowed to be Administrators or have an admin account to run Gentran under.
If the Windows user is not an administrator for that machine, UAC pops-up a notification box and prompts for an Administrator ID and
password when launching GSW apps. So customer is requesting that the "Run as Administrator" requirement be removed from some of the
GSW modules.  Customer thinks they should not need "Run As Administrator" authority to run GSW on a client system despite the fact
that Microsoft has changed user configurations and added User Account Control settings to newer operating systems.

FIX DESCRIPTION:  Added new project build modes that use the "AsInvoked" UAC setting to the following modules so that non-admin binaries could be created without the "Run as Administrator" requirement:  Edigmr.exe, ArchiveManager.exe, Commpost.exe,
ProcCtrl.exe, tx32.exe.  These non-Admin binaries can be found in the Support\NonAdmin folder of the patch install image.

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
NOTE: THESE SPECIAL BINARIES WILL NOT BE INSTALLED BY THE PATCH INSTALL.  
IF YOU WANT THEM, YOU MUST GO THE SUPPORT\NONADMIN FOLDER AND COPY THEM TO THE BIN FOLDER MANUALLY
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


_______________________________________________________________________________
RTC DEFECT:
APAR:   
DATE:         
MODULE:       

PROBLEM DESCRIPTION:  



FIX DESCRIPTION:  




_______________________________________________________________________________
===================>> End Patch Release Notes GSW 5.3.1 <<=====================

                          PATCH RELEASE NOTES
                      Common Component Translator


**************************************************************************
                              PATCH 1
**************************************************************************

RTC DEFECT:     355497 
APAR:           IC88735
DATE:           11/29/2012       
MODULE:         Mapper.exe

PROBLEM DESCRIPTION:  Compilation error reported for valid trim command in extended rule mapping.  rule #xxx = right(left($VAR,y),z);
Reported error: Error 8003, Line 1 : ActiveX properties could not be used because the length is unknown.

FIX DESCRIPTION:  Resolved internal allocation of temporary string in compiler to hold the result of the first expression. 
The length is derived from the length of the previous command.


_______________________________________________________________________________ 

RTC DEFECT:   366280
APAR:         IC90131
DATE:         2/13/13
MODULE:       tx32.exe (txengine.lib)

PROBLEM DESCRIPTION:  5.3.1 ODBC mapping issues: (1) When importing a document (ODBC to positional), a NULL value from an ODBC date 
field resulted in 19691231 in the document.  (2) When doing inbound processing (EDI to ODBC), if the interchange has multiple datetime
values to store in a single ODBC row, the last datetime value is used for any datetime column.

FIX DESCRIPTION:  (1) When retrieving values from ODBC database (datetimes, strings or numbers) added checks to see if the value is NULL.
If so, the field do not retrieve a value.  (2) Instead of re-using a single datetime variable, added a datetime array to use for ODBC
inserts.


_______________________________________________________________________________ 

RTC DEFECT: 363084
APAR:       IC90804
DATE:       03/12/13      
MODULE:     txengine.lib     

PROBLEM DESCRIPTION: 999 & 997 Segment count off when _isabrk2 _gsbrk2 _stbrk2 maps are used on incoming document 

FIX DESCRIPTION: Added a check at the document level of the translator to see if the customer is using maps that include passing 
through the enveloping data with the document data.  If so, we need to ignore the enveloping data as this is not part of the document
and is not needed for error reporting in the 997's and 999's.    



**************************************************************************
                              PATCH 2
**************************************************************************

RTC DEFECT:  371770  
APAR:        IC91493
DATE:        4/11/2013     
MODULE:      Mapper.exe

PROBLEM DESCRIPTION: Map Release Version getting set to negative number in DB if no association is entered in map Details dialog

FIX DESCRIPTION: Set EDI Associations Release Versions in Details window to a default value of zero.  Changed the Edi Associations Release field to a numeric only field and added validation checking to ensure that the integer value is between 0 & 32767. Added two new warning messages for the validation check of the Edi Associations Release value to inform the user of which value is out of range.


_______________________________________________________________________________

RTC DEFECT:     379967
APAR:           IC92985
DATE:           6/10/2013        
MODULE:         Mapper.exe

PROBLEM DESCRIPTION:  When compiling maps from the command line with the "Mapper.exe -c Map_Name_Pattern" 
invocation, errors found during the compliation of a map generate a dialog box that must be closed before the 
mapper will compile the next map.  Additionally, the failed map is not reported in the map compilation report.



FIX DESCRIPTION:  Added the -q option for the The Mapper.exe command line invocation.  The options are now
Mapper.exe [-q] [ -c Map_Name_Pattern].  The -q (quiet) option represses the Mapper errror dialog box from 
displaying, if a compilation error is reported.  The failed compilation is now reported in the map compilation 
report, with or without the -q option.




_______________________________________________________________________________

RTC DEFECT: 378775
APAR:       IC93076
DATE:       6/13/13 
MODULE:     TX32.exe 

PROBLEM DESCRIPTION:  Importing a file creates an exception in tx32 Exception Code: c0000417



FIX DESCRIPTION:  GSW 5.1 - 5.3 translators had a bug that allowed date syntax of %Y%m%d to have an extra % after the d.  In the 
5.3.1 translator microsoft updated the function GSW uses to get the date and it now throws an exception and crashes the translator
if %Y%m%d% is encountered.  We have updated the translator to check for an invalid syntax of %Y%m%d% and change it to %Y%m%d. This 
fix will not work for other syntaxes that may also have an extra % immediately following the last date parameter.  % signs not 
immediately followed by a parameter will still throw exceptions in the translator.




_____________________________________________________________

RTC DEFECT:   
APAR:
DATE:         
MODULE:       

PROBLEM DESCRIPTION:  

FIX DESCRIPTION:  


_____________________________________________________________