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 12
=========================================================================


**************************************************************************
                                 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 Commpost 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.

New audit message 1-6-1682: "Splitter - no matching segment terminator found in splitter table for %1 interchange".


_______________________________________________________________________________

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:       Commpost.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, commpost 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
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!



**************************************************************************
                                 PATCH 3
**************************************************************************

RTC DEFECT:   384560
APAR:         IC94340
DATE:         7/23/13      
MODULE:       GenCom97.exe      

PROBLEM DESCRIPTION:  Duplicate File errors during OFTP/CAPI comms SEND sessions due to identical timestamp in OFTP Virtual FileName
when sending more than one file within the same second.

FIX DESCRIPTION:  Added code to sleep for one second before getting the current datetime stamp.


_______________________________________________________________________________

RTC DEFECT:   390506
APAR:   
DATE:         8/1/13
MODULE:       ArchiveEngine.exe

PROBLEM DESCRIPTION:  In 5.3.1 only, at the end of archive mailbox with delete, the 7-1-4 audit message that is written has the wrong number for
messages deleted.  "Archive Engine completed processing of definition file (Test.ard). Archived (563) message(s) and deleted (158766) message(s)."

FIX DESCRIPTION:  During the VS2008 conversion, a code change was made that resulted in multiple attempts to delete the mailbox messages as the 
message ID array was being loaded.  The mailbox message delete function was smart enough to ignore any messages that no longer existed and did not 
attempt to delete them again.  However, the total deleted counter was tied to attempts made (not actual deleted) and grew exponentially. Fixed.
Undid aforementioned code change and declared loop counter outside of the loop.


_______________________________________________________________________________

RTC DEFECT:	390679
APAR:   	IC94815
DATE:           8/12/13
MODULE:         999 Build P&R map

PROBLEM DESCRIPTION:  BLD999.MAP does not create acknowledgements with P (Partial accepted) status



FIX DESCRIPTION:  Added new BLD999_DETAILEDPARTIAL&REJECTCODES map and tpl to GSW.  These files can be found
at:

Maps > Special > Source: BLD999_DETAILEDPARTIAL&REJECTCODES.MAP

Maps > Special > Compiled: BLD999_DETAILEDPARTIAL&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:	391572
APAR:   	IC94911
DATE:           8/13/13
MODULE:         Special maps - Break 2 and 3

PROBLEM DESCRIPTION:  Translation can hang if using Group and Set pass through maps and the Interchange
defines the same character as the segment terminator and repeating element separator.



FIX DESCRIPTION:  Updated pass through maps to fail translation, rather than passing the invalid 
interchange to through to the GS and ST break maps.  These files can be found at:

Maps > Special > Source: _gsbrk2.MAP, _gsbrk3.MAP, _stbrk3.MAP

Maps > Special > Compiled: _gsbrk2.TPL, _gsbrk3.TPL, _stbrk3.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:	391048
APAR:   	IC95687
DATE:           8/19/2013
MODULE:         Partner.exe / BRK999_DETAILED.MAP & .TPL

PROBLEM DESCRIPTION:  Need inbound 999 process for X12



FIX DESCRIPTION:  Modified partner editor to allow 999 inbound and outbound relationships to be built for partners using X-12 standard.  Also added 
BRK999_DETAILED.map and .TPL to specials folder.  They are located at:

Maps > Special > Source: BRK999_DETAILED.MAP

Maps > Special > Compiled: BRK999_DETAILED.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:	393211
APAR:   	IC95117
DATE:           8/23/13
MODULE:         tx32.exe 

PROBLEM DESCRIPTION:  Zero byte files left in Gentran temp folder after translation, with no errors
reported in audit log.


FIX DESCRIPTION:  Write new audit message to audit log when translator fails to unlink temp report
or temp translation output file, following import.  New audit messages report file-access errors of
unlink command.


______________________________________________________________________________

RTC DEFECT:   394552
APAR:   
DATE:         8/27/13
MODULE:       Patch install

PROBLEM DESCRIPTION:  Customer could not install any patch since the setup was aborting without indicating why.  Need to add debug 
popups at every step during installation to help track down where the setup runs into a problem.

FIX DESCRIPTION:  Added debug popups to the patch install.  The popups only appear if a "debug.txt" file exists in the root of the
install image.


______________________________________________________________________________

RTC DEFECT:   398210
APAR:         IC96722
DATE:         10/8/13
MODULE:       SCCertMgr.exe

PROBLEM DESCRIPTION:  RosettaNet Security Profile Manager is creating certificates with a 2010 expiration date ("Valid from 9/24/2013
to 9/24/2010").

FIX DESCRIPTION:  The "To" year was hard-coded to be 2010.  Fixed it to be 3 years from the current date.


_______________________________________________________________________________

RTC DEFECT:   396017
APAR:         IC96331
DATE:         10/11/13
MODULE:       GenCom97.exe, GenComUI.dll, GenSec.dll

PROBLEM DESCRIPTION: (1) 5.3.1 comm does not properly load any third-party comm DLLs (such as Capi2032.dll and FtpPro32.dll). 
This prevents CAPI, WSFTP, etc from working.  (2) The TAPI version is initialized to 2.0 which is too high for some comm devices 
and generated an INCOMPATIBLEAPIVERSION error in the comm system log.

FIX DESCRIPTION: (1) Needed to modify the 5.3.1 DLL load function to retry loading the DLL from multiple locations in case of failure.
(2) Needed to add code to negotiate the API version to use with the comm device.


_______________________________________________________________________________

RTC DEFECT:   400377
APAR:   
DATE:         10/14/13   
MODULE:       Commpost.exe, AuditMsgFile.xml   

PROBLEM DESCRIPTION:  Commpost is reporting critical errors using the 1-6-50400 info audits.  These should be reported as errors.

FIX DESCRIPTION:  Added new error audit message 1-6-4000 for Commpost to use in those error scenarios.


_______________________________________________________________________________

RTC DEFECT:   398950 
APAR:         IC96843
DATE:         10/15/13   
MODULE:       tx32.exe 

PROBLEM DESCRIPTION:  Translation could fail to open an existing Template file, when a system was under load.  If Template file 
was an Import header map, the result was that two tdo*.TMP files were left in the Gentran temp folder after translation.  If 
the Template file was a document level Import map, the result was that file could be imported and exist in the ExtData folder, 
but the file would not be translated, due to the failure to open the Template, causing a zero byte document to be created in 
the Document folder, but no Translation report would be created.

FIX DESCRIPTION:  Implemented retry logic into the opening of translation templates, with a sleep period between each attempt.
If retry attempts are exceeded, the Translation report is opened, and the Template open error is recorded and translation fails.


_______________________________________________________________________________

RTC DEFECT:   400251
APAR:         IC96846 
DATE:         10/16/13   
MODULE:       tx32.exe, tx32audits.xml

PROBLEM DESCRIPTION:  Retry attempts and sleep durations values, for APAR IC96843, need to be configurable for processing 
optimization, and a new audit message is required to record retry attempts.

FIX DESCRIPTION:  Added registry entry lookup for Translation Object open retry attempts.  Default values are 1000 milliseconds
and 5 retry attempts.  Updates to these default values require the creation and assignment of the registry keys below.  The 
TranslatorTemplateSleep value should be the number of milliseconds to sleep between retry attemps.

CC_BASE_KEY = "SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1\TranslatorFileSleep"
CC_BASE_KEY = "SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1\TranslatorFileRetry"

Added new error audit message 3-1-1805 for Template open retry warnings.


_______________________________________________________________________________

RTC DEFECT:	397871
APAR:   	IC97320  
DATE:         	10/30/2013
MODULE:       	GentranAdministrator.exe

PROBLEM DESCRIPTION:  The report line that should report the verision of the GentranAdministrator.exe binary reports 
the patch version.  The binary version should be reported instead.


FIX DESCRIPTION:  Changed GentranAdministrator.exe to extract the program's version information.  This had been changed
when the previous function failed to retrieve the correct information on a Windows 7 or 2008 OS.




_______________________________________________________________________________

RTC DEFECT:	401315 and 401322
APAR:   	IC97493
DATE:         	11/6/2013
MODULE:       	Gntxeng.exe

PROBLEM DESCRIPTION:  Acknowledgements generated with Error Detail could contain incorrect error codes in the AK304 
and AK403, or IK304 and IK403 elements.  A defect in the formatting of compliance errors in the translator report 
caused an error in the formatting of the 997 and 999 detail segments formatting to use the code 004 in these elements.


FIX DESCRIPTION:  Fixed translator reporting parsing logic to correctly format compliance error codes.



_______________________________________________________________________________

RTC DEFECT:	384495
APAR:   	
DATE:         	11/11/2013
MODULE:       	Mercury.exe

PROBLEM DESCRIPTION:  The Mailbox Client could report access violation if the Mailbox Trace was enabled and
the Mailbox Delivery Rules tab was selected.


FIX DESCRIPTION:  Corrrected the number of parameters passed to Trace program for the Mailbox Delivery Rules 
interface.



_______________________________________________________________________________

RTC DEFECT:   394392
APAR:         IC97716
DATE:         11/18/13
MODULE:       GNTXEng.exe, Commpost.exe

PROBLEM DESCRIPTION:  5.3.1 inbound processing occasionally gets a 1-6-2001 error ("Translation using gntxeng.exe failed with 
error 80040702 and 800706be") or 1-6-50400 errors.

FIX DESCRIPTION:  There are 2 separate issues here: (1) Translator crashes when it can't set/open a report file (the gntxeng 
errors), and (2) Commpost crashes when it can't open a report file (the 1-6-50400 "errors").  Added retry logic to both modules.
Retry settings are automatically created in the registry and set to default values:

Key1: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1\
value name1: TranslatorFileRetry
default value: 5
value name2: TranslatorFileSleep
default value: 1000  (milliseconds)

Key2: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1\Systems\<GSW-SYSTEM-NAME>
value name1: CommpostFileRetry
default value: 5
value name2: CommpostFileSleep
default value: 1000  (milliseconds)

Also added debug audits to GNTXEng.exe that will write extensive debugging info during inbound processing.
This is off by default and can be enabled by changing the following registry setting to 1:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1
value name: TranslatorDebugAudits
default value: 0  (off)


_______________________________________________________________________________

RTC DEFECT:   408709
APAR:         IC98934
DATE:         1/17/14   
MODULE:       patch install   

PROBLEM DESCRIPTION:  The patch install should not execute SQL scripts that are no longer needed since the database changes 
are already in the base product.  The patch install could fail if the database tables that are being updated unnecessarily 
have a gigantic amount of data.

FIX DESCRIPTION:  Removed execution of SQL scripts from the patch install.


_____________________________________________________________

RTC DEFECT:   409246
APAR:         IC98936
DATE:         1/21/14
MODULE:       Translator

PROBLEM DESCRIPTION:  Translation using Maps with TP Lookup instructions threw ODBC Exceptions.  This defects was introduced in the initial release of the 5.3.1.3 Fix Pack.

FIX DESCRIPTION:  Corrected ODBC Connection used by TP Lookup class, to use the correct connection type based on Curson Library definition.  Fix was delivered in the redistribution of the 5.3.1.3 Fix Pack.



**************************************************************************
                                 PATCH 4
**************************************************************************

RTC DEFECT:   396640
APAR:         IC98432
DATE:         12/20/13      
MODULE:       ArchiveEngine.exe, ArchiveAuditMsgs.xml

PROBLEM DESCRIPTION:  When archiving mailbox messages, there are 2 separate issues that look somewhat similar but are not related:

1) Random, unknown exceptions are thrown resulting in the 7-1-30 audit with "empty" message and attachment IDs shown.  
Archive fails and quits.  Archive can be rerun again and get further along but an exception may be thrown again.

2) An .atm file is missing or locked resulting in the 7-1-29 audit with the actual message and attachment IDs shown.  
Archive fails and quits.  Archive can't be rerun successfully without unlocking the problem file or removing the database entry 
for the missing file. 

In both cases, when archive quits, no archive file is saved and since it fails before the delete operation, nothing is deleted.

FIX DESCRIPTION:  Modified Archive to handle these errors by retrying or skipping the archiving of the problem attachments and 
continue archiving if possible.  Modified the 7-1-29 audit to give more details.


_______________________________________________________________________________

RTC DEFECT:   406001
APAR:         IC98434
DATE:         12/20/13      
MODULE:       Mercury.exe, MClient.exe, MailboxEvent.xml

PROBLEM DESCRIPTION:  Customer for RTC#396640 has requested registry settings for the retry & sleep values that are used in the 
OpenAttachmentStream function in Mercury.exe.  When Archive calls that function during mailbox archive it can currently take up 
to 50 seconds (5 retries with 10 seconds sleep between each retry) before the function returns with an error (for either locked 
or missing file).  This also affect the Mailbox UI since it uses the same function to open attachments.  However, no error
is displayed in the Mailbox UI if the attachment can't be opened.

FIX DESCRIPTION: The Mailbox UI will now display a popup error if the attachment file cannot be displayed.  The following fixes 
in the Mailbox service affect Archive and the Mailbox UI:

1) New registry settings created automatically for the retry/sleep values used in Mercury.exe when opening an attachment file

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Mailbox\5.3.1\Server
value name: MailboxFileRetry
default value: 5
value name: MailboxFileSleep
default value: 10000 (ms)

2) If an attachment file open error happens, check to see if the file exists before doing any sleep/retry.  Write a new audit 
error (2-1-1087) and quit immediately if file is missing.

  2-1-1087: OpenAttachmentStream failed for attachment Id(41), message Id(36). Attachment file is missing: 
  C:\GENSRVNT\Store\#2013\12\12\14\41.ATM

Otherwise, if the file exists, write a new audit message for each retry attempt (2-1-1088) and when the max retries have been 
exceeded (2-1-1089).

  2-1-1088: OpenAttachmentStream failed for attachment Id(41), message Id(36). Attempt #5. Could not open file:
  C:\GENSRVNT\Store\#2013\12\12\14\41.ATM. Error returned: 0x20 - The process cannot access the file because it is being used by 
  another process.


  2-1-1089: OpenAttachmentStream failed for attachment Id(41), message Id(36). Maximum retries exceeded. Could not open file:
  C:\GENSRVNT\Store\#2013\12\12\14\41.ATM. Error returned: 0x20 - The process cannot access the file because it is being used by 
  another process.



_______________________________________________________________________________

RTC DEFECT:	407612
APAR:   	IC98648
DATE:         	1/9/2014
MODULE:         Special Maps - BLD999_DETAILEDPARTIAL&REJECTCODES

PROBLEM DESCRIPTION:  999 Partial and Reject map does not use the R in the IK5 segment



FIX DESCRIPTION:  Found two extended rules in the BLD997P&R that did not exist in the
BLD999_DetailedP&R.  One was on the Transaction Group which defines a integer variable.
The other was at the Segment level>Segment_Record>01 Segment_Position which would change
the Ack_Code in at the Transaction level if there were any error present.  Copying
both of these rules over to the BLD999_DetailedP&R map resolved the problem.  These 
Updated files can be found at:

Maps > Special > Source: BLD999_DETAILEDPARTIAL&REJECTCODES.MAP

Maps > Special > Compiled: BLD999_DETAILEDPARTIAL&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:	404890
APAR:   	IC98961
DATE:      	1/23/14
MODULE:       	Vatprint.exe

PROBLEM DESCRIPTION:  When Vatprint.exe was run from the command line, on a Windows 2003 Server, the program would display an "Unhandled Exception" error message.  Vatprint would complete, generating the output report and/or error file, but the error message would be displayed with each execution of Vatprint.exe.



FIX DESCRIPTION:  Changed Vatprint to conditional free objects in it's destructor, preventing UI objects from being freed if they were not initialized.




_______________________________________________________________________________

RTC DEFECT:	404978
APAR:   	IC99137
DATE:         	1/31/14
MODULE:       	edimgr.exe

PROBLEM DESCRIPTION:  Documents viewed in the Out Drawer could display an incorrect document.  If the Drawer contained more than 65535 documents, the 65536th item in the list would display the 1st document, the 65537th item would display the 2nd document, and so on.  


FIX DESCRIPTION:  The data structure than holds the document position in a list was changed to correctly correlate documents up to the 2147483647th position. The fix is included in each of the Edimgr Document List Display modules, OutDrawer, InDrawer, Workspace, Inbox, Outbox, ... 





_______________________________________________________________________________

RTC DEFECT:	393711, 417116
APAR:   	IC99224
DATE:           2/6/14 
MODULE:         ArchiveEngine.exe

PROBLEM DESCRIPTION:  Archive on Gentran clusters not releasing System Archive Mutex



FIX DESCRIPTION: We've added additional logging around the Attachment Archiving process
when we attempt to close a stream when we've encountered an exception.  Also added more
exception handling in the parent function in case additional exceptions are thrown. If
that happens, a 7-1-53 error audit will be written detailing what threw the exception.




_______________________________________________________________________________

RTC DEFECT:	412129
APAR:   	IC99424
DATE:         	2/18/14
MODULE:       	edimgr.exe

PROBLEM DESCRIPTION:  The Interchange Filter From Date would display 12/31/69 or 1/1/70, unless No Date/Time Checking was selected.


FIX DESCRIPTION:  Fixed bug in 64 bit Date/Time class.  The "From Date" was not initialized properly, causing the 64 bit portion of Date to include values that make the date larger than the Dialog could display.




_______________________________________________________________________________

RTC DEFECT:	412657
APAR:   	
DATE:         	2/20/14
MODULE:       	MClient.exe

PROBLEM DESCRIPTION:  If a mailbox message has a status of SEND_FAILED or DELIVERY_FAILED, the mailbox UI will display a blank 
entry instead of "Send Failed" or "Delivery Failed" under the Status column in the list view.

FIX DESCRIPTION:  Added code to display the corresponding text for SEND_FAILED and DELIVERY_FAILED message statuses


_______________________________________________________________________________

RTC DEFECT:	407474
APAR:   	IC99550
DATE:         	2/20/14
MODULE:       	GICheck.exe

PROBLEM DESCRIPTION:  The Mailbox Spooler is an internal queue used by the Mailbox service to delivery mailbox messages from
one mailbox to another (e.g., from the Gentran Application mailbox to an outbound comm mailbox).  If a message gets stuck in the
Spooler during a send operation, the message is not visible in the Mailbox UI, but is still in the database Message_tb table with
a folder id of 4 (spooler) in the destination mailbox.  Once stuck, the message cannot be removed unless it's manually deleted
from the database since its not visible in the UI.  The original message in the source mailbox is still visible but has a 
"Sending" status.

FIX DESCRIPTION:  Added a new "Message" tab to GICheck to search for mailbox messages stuck in the Mailbox Spooler and remove them
from Message_tb along with the corresponding Attachment_tb, Recipient_tb, DataAuditLog_tb entries.  The status of the original 
messages are also updated to "Send Failed".  The .atm files are left untouched since they also belong to the original messages.


_______________________________________________________________________________

RTC DEFECT:	412527
APAR:   	IT00358
DATE:         	2/20/14
MODULE:       	Unattend

PROBLEM DESCRIPTION:  Process Control Command GDW_Print fails to print docs from designated location 



FIX DESCRIPTION:  When using GDW_PRINT to print documents from a specified location in EDIMGR the user will receive
the following error in the Audit log even when the documents are present:  No data available for Command GDW_Print; 
Ptr: <All>, Doc Type: <All>".  This message should only be displayed when no documents exist for the given partner
and doc type.  This is can be the result of either the Partner Relationship not being found or therelationship not 
having a print template associated with it.  Two new error messages have been added to Unattend.exe to inform the 
customer in the audit log which is missing.  




_______________________________________________________________________________

RTC DEFECT:   408775
APAR:         IT00854
DATE:         2/5/14
MODULE:       ArchiveEngine.exe

PROBLEM DESCRIPTION:  Customer has requested registry settings for the retry/sleep values that are used in handling the stream write 
exceptions that happen while writing an attachment file to the archive file.

FIX DESCRIPTION:  Added the following fixes to ArchiveEngine:

1) New registry settings created automatically for the retry/sleep values used in ArchiveEngine.exe when a stream write exception happens
while writing an attachment file to the archive file:

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Archive\5.3.1\Systems\<my-Gentran-System-Name>
value name: ArchiveFileRetry
default value: 5
value name: ArchiveFileSleep
default value: 10000 (ms)

7-1-30: "Encountered exception (ArchiveAttachmentFile - Stream.Write - Attempt #5 - CFileException: An unknown error occurred while 
accessing an unnamed file.) while archiving attachment Id(10697339) of message Id(5336250)."

2)  The 7-1-29 audit has been reworded to say "cannot archive attachment file" instead of "unable to open/read file" since it also covers 
the stream.write exceptions while writing to archive file scenario (no problems reading the atm file in that instance).

7-1-29: "Unable to archive attachment Id(10697339) for message Id(5336250). Cannot archive attachment file: E:\GENSRVNT\Store\#2014\01\22\16\10697309.ATM"

3) Added code to close the read stream of the source .atm file after max retries have been exceeded when trying to write the .atm file 
to the archive.  This addresses the original symptom of .atm files being locked after exceptions are thrown and archive aborts.


_______________________________________________________________________________

RTC DEFECT:	415043
APAR:   	IT00857
DATE:         	3/31/14
MODULE:       	MBMAPI30.dll

PROBLEM DESCRIPTION:  5.3.1 MAPI Gateway randomly crashes Mailbox service when receiving MAPI message with EDI content.  The same 
message does not crash 5.2 mercury.exe and processes fine.

FIX DESCRIPTION:  The MAPI Gateway code was looking for the "Content-Type:" MIME tag in the attachment section of the email message 
and assigning the tag value to a string variable when it crashed.  The API call to query the attachment MIME headers returned a bad 
pointer value (0x8004010F = MAPI_E_NOT_FOUND) for that field in the MIME array.  Added code to look for MAPI_E_NOT_FOUND before 
assigning it to the string variable. 


_______________________________________________________________________________

RTC DEFECT:   416002
APAR:         IT00947
DATE:         4/4/14
MODULE:       Unattend.exe

PROBLEM DESCRIPTION:  5.3.1 unattend session using the "If File Below Exists" condition does not find the file being searched for when 
the file is created by an external app in the previous step.

FIX DESCRIPTION:  Due to potential OS performance issues, Unattend may not see the external file just yet despite being "created" in
the previous step in the Unattend session. 

1) Added retry/sleep logic to keep searching for the file until found or until retries have been exceeded.  

1-3-1594: Process Control - Condition_Check_File attempt #5. FindFirstFile(C:\temp\pet_810b.txt) returned INVALID_HANDLE_VALUE: 
The system cannot find the file specified.

2) Added new registry settings for retry/sleep values:

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1
value name: UnattendFileRetry
default value: 5
value name: UnattendFileSleep
default value: 2000 (ms)

3) If registry settings are not found, they are automatically created (new warning audit):

1-3-1520: Process Control - Registry value (UnattendFileRetry) under the "HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1" 
registry key was not found. The registry value will be set to the default value (5).

1-3-1520: Process Control - Registry value (UnattendFileSleep) under the "HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1" 
registry key was not found. The registry value will be set to the default value (2000).

4) If registry setting values are too big, they will get reset to the maximum allowed value (new warning audit):

1-3-1521: Process Control - Registry value (UnattendFileRetry) under the "HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1" 
registry key has exceeded the maximum allowed value (20). The registry value will be reset to 20.

1-3-1521: Process Control - Registry value (UnattendFileSleep) under the "HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1" 
registry key has exceeded the maximum allowed value (10000). The registry value will be reset to 10000.


_______________________________________________________________________________

RTC DEFECT:	417779
APAR:   	IT01052
DATE:         	4/9/2014
MODULE:       	ANServer.exe

PROBLEM DESCRIPTION:  ANServer.exe could attempt to write duplicate entries to the ProcAuditLog_tb or DataAuditLog_tb tables, if the 
AuditEntryKey registry entry was set to a value that exists in the ProcAuditLog_tb or DataAuditLog_tb tables.  

FIX DESCRIPTION:  Added new registry entry UseMaxAuditEntryKEY to force ANServer to use the max value of AuditEntryKey from 
ProcAuditLog_tb and DataAuditLog_tb, update the registry, and use this value as the next AuditEntryKey value during startup.  The new 
entry should be created as a 32-bit DWORD, and set to a non zero value (e.g. 1) to enable, and registry entry should be created under 
HKEY_LOCAL_MACHINE/.../Gentran/AuditNotification/5.3.1/Server.




_______________________________________________________________________________

RTC DEFECT:   420484
APAR:         IT01044
DATE:         4/14/14
MODULE:       ArchiveEngine.exe

PROBLEM DESCRIPTION:  While archiving mailbox messages, if the archive file reaches the 2GB file size limit, it will still keep on trying 
to archive more attachments until it eventually aborts.  The errors in the audit log do not indicate that the 2GB limit was reached.

FIX DESCRIPTION:  Code now checks the exception thrown to see if the error is the 2GB limit error.  If so, it will write the following 
audit messages and abort the archive.

7-1-30: "Encountered exception (ArchiveAttachmentFile - Stream.Write - CFileException::m_lOsError = 0x0x80030111 - The compound file is
too large for the current implementation) while archiving attachment Id(10697339) of message Id(5336250)."

7-1-120: "Archive file has reached the 2GB file size limit."


_______________________________________________________________________________

RTC DEFECT:		417562
APAR:   		IT00358
DATE:           4/1/2014
MODULE:         TX32.exe

PROBLEM DESCRIPTION:  3-1-203 'PK_Lookup_tb'. Cannot insert duplicate key in object 'dbo.Lookup_tb'.


FIX DESCRIPTION:  This is a mapping issue and the customer will need to fix their map.  As a fix for this we are providing 
a more informative error message that will precede the ODBC error in this case that will tell the customer that they are 
either trying to create a primary key in the lookup_tb that already exists.  Or that they are trying to perform an update 
on one of the primary key fields in the table.  As part of the update error we will display the key value as it is and the 
new value they are trying to insert as part of the update.  The two new error messages are displayed below

Insert Into Lookup Table: "Primary Key already exists in Lookup_tb, exiting insert: PartnerKey = %s, TableName = %s, 
Item = %s", LookUp.m_PartnerKEY, LookUp.m_TableName, LookUp.m_Item

Update Lookup Table:  "Cannot perform an update on the Primary key fields in Lookup_tb. PartnerKey = %s, update value = %s, 
TableName = %s, update value = %s, Item = %s, update value = %s", PrtnrKEY, LookUp.m_PartnerKEY, TableName, LookUp.m_TableName, 
Code, LookUp.m_Item




_______________________________________________________________________________

RTC DEFECT:	394322, 405323, 409371
APAR:   	IC98948
DATE:         	1/23/14
MODULE:       	Partnred.exe

PROBLEM DESCRIPTION:  Occasional ODBC Cursor Library errors reported in Windows Event Application log.  Additionally, the Partner Editor would display ODBC errors if multiple edits were performed to a Trading Partner after removal of ODBC Cursor Library.


FIX DESCRIPTION:  Removal of use of the ODBC Cursor Library in all ODBC Connections.  Post removal, refreshed Trading Partner list after saving or deleting Trading Partners and/or Trading Partner components.




_______________________________________________________________________________

RTC DEFECT:	418953
APAR:   	IT01523
DATE:         	05/02/14
MODULE:       	GenCom97.exe

PROBLEM DESCRIPTION:  FtpRcvFile command returns 0 when a file or directory does not exist.  The documentation states that FtpRcvFile, when set with SetRcvNoData command, should return 1 if a file is not found.


FIX DESCRIPTION:  Changed GenCom97 to return 1 when FtpRcvFile received an FTP 550 response from FTP Sender.



_______________________________________________________________________________

RTC DEFECT:	418944
APAR:   	IT01512
DATE:         	05/02/14
MODULE:       	GenCom97.exe

PROBLEM DESCRIPTION:  GenCom97 failing to receive files from FTP Sender that transmits multiple FTP codes, 226 and 227, in the same FTP Response.  


FIX DESCRIPTION:  Fixed GenCom97 to correctly parse the IP and Data Port from the FTP Sender's 227 Response code buffer, regardless of the presence other codes in the FTP Response.


_______________________________________________________________________________

RTC DEFECT:	422854
APAR:   	IT01508
DATE:         	5/3/14
MODULE:       	Edimgr.exe

PROBLEM DESCRIPTION:  Restored EDI data could not be viewed from the Restored Interchange viewer.


FIX DESCRIPTION:  Resolved data look up errors in Restored Interchange viewer's restored EDI data query.  



_______________________________________________________________________________

RTC DEFECT:   424848
APAR:         IT01044
DATE:         5/21/14
MODULE:       ArchiveEngine.exe

PROBLEM DESCRIPTION:  Related to RTC#420484.  The customer needs the "2GB file size limit" audit log error for EDI and EXT archive types too.
The fix for RTC#420484 covered only MBX archives.

FIX DESCRIPTION:  Modified EDI and EXT archives to check the write exception thrown to see if the error is the 2GB limit error.  If so, it
will write the following audit messages and abort the archive.  The wording of the first audit (7-1-57) will vary depending on what type of 
archive is it.

7-1-57: CExtDataArchiver::ArchiveFile encountered a CFileException (cause:generic, error:m_lOsError = 0x0x80030111 - The compound file is too 
large for the current implementation) while attempting to archive file (C:\Gensrvnt\ExternalData\#2014\05\19\15\170.EXT).

7-1-120: "Archive file has reached the 2GB file size limit."


_______________________________________________________________________________

RTC DEFECT:	422104
APAR:   	IT02143
DATE:         	5/30/2014
MODULE:       	GenCom97.exe

PROBLEM DESCRIPTION:  FTP Session failed to authenticate when FTP Server sent a 220 response but did not respond to transmitted User crendentials.



FIX DESCRIPTION:  Fixed FTP processing in the Communication Service to properly handle large pre-authentication banners, and fully receive message prior to sending User credentials.




_______________________________________________________________________________

RTC DEFECT:	425381
APAR:   	IT02316
DATE:         	6/2/2014
MODULE:       	GentranAdministrator.exe

PROBLEM DESCRIPTION:  Customers using the Microsoft Oracle ODBC drivers could encounter the error, Numeric value out of range, when running the Gentran Administrator.



FIX DESCRIPTION:  Changed the Gentran Administrator to use the Gentran Mailbox DSN rather than the Audit Notification DSN.




_______________________________________________________________________________

RTC DEFECT:	427479
APAR:   	IT02295
DATE:         	6/6/2014
MODULE:       	Commpost.exe

PROBLEM DESCRIPTION:  When processing multiple Edifiact interchanges in an unblocked file, interchanges could be incorrectly flagged with error, "Splitter - no matching segment terminator found in splitter table for UNB/UNZ interchange".  



FIX DESCRIPTION:  Verify that the buffer contains a full UNB segment or the end of file is reached, prior to evaluating validity of variable length interchange wrappers. 




_______________________________________________________________________________

RTC DEFECT:	423979
APAR:   	IT02513
DATE:         	6/12/14
MODULE:       	Patch Install

PROBLEM DESCRIPTION:  When running the 5.3.1 patch 2 or 3 install on an Oracle system, the new Unattend recovery session file (System-MBRecovery.ses) 
is being installed to the root of the C: drive instead of the Gensrvnt\Unattend folder.

FIX DESCRIPTION:  When the patch install called an InstallDLL function to get the location of the Unattend directory from the database, the DSN name 
was mistakingly passed into the function instead of the database username.  While SQLServer was still able to open a database connection anyway with
the wrong parameter, Oracle did not like it at all and the database connection failed.  As a result, the function returned a blank value for the
Unattend directory.  Fixed the typo and added code to make sure that the Unattend directory returned is not blank.



**************************************************************************
                                 PATCH 5
**************************************************************************

RTC DEFECT:	431113
APAR:   	IT02768
DATE:         	6/25/2014
MODULE:       	Partnred.exe

PROBLEM DESCRIPTION:  Partner Editor could crash on a 64 bit OS when using Trading Partner Help and searching for a string
in the Help Search tab.



FIX DESCRIPTION:  Changed threading model in Help initialization to limit number of threads allowed by Help to one thread.  




_______________________________________________________________________________

RTC DEFECT:	432767
APAR:   	IT05256
DATE:         	7/17/14
MODULE:       	ArchiveEngine.exe, ArchiveManager.exe

PROBLEM DESCRIPTION:  The 5.3.1 Archive Wait Timer setting in the ArchiveManager is only visible to the Windows user that set the Wait Timer and not
to other Windows users or the Gentran Executive service (if it uses a different windows account) when it launches GDW_Archive.

FIX DESCRIPTION:  The Wait Timer setting was stored in the HKEY_CURRENT_USER section of the registry.  Modified code to store the global settings
in the HKEY_LOCAL_MACHINE section of the registry.

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Archive\5.3.1\Preferences



_______________________________________________________________________________

RTC DEFECT:	432768
APAR:   	IT05083
DATE:         	7/17/14
MODULE:       	ArchiveEngine.exe

PROBLEM DESCRIPTION:  Customer getting ODBC errors in Windows Application Event Viewer log when utilizing archive wait timer feature in Gentran. 
ODBC errors are recorded at the beginning of the archive session, the beginning of the delete phase and end of the delete phase of archive stating:
"GENTRANArchive 50008 (1) ODBC: MFC database exception encountered in GENTRAN Error: ORA-00942: table or view does not exist
SQL Statement: SELECT Event,Status FROM Schedule_tb"

FIX DESCRIPTION:  Oracle SQL queries need square brackets around database table names and column names.  Modified the Archive Wait Timer code to 
include them when it checks the Schedule table.


_______________________________________________________________________________

RTC DEFECT:	436784
APAR:   	IT03871
DATE:         	8/20/14
MODULE:       	Unattend.exe

PROBLEM DESCRIPTION:  The Send Options Preference, "Check for interchanges that did not send", does not affect the resend interchanges in Send Queue during Send Only session.  Interchanges that had previous failed to send were only resent if a Send Receive session was run or if an unset interchange was added to the mailbox queue.



FIX DESCRIPTION:  Changed Process Control to resend interchanges in the Send Queue during Send Only sessions, if the Send Option Preference, "Check for interchanges that did not send", is selected.




_______________________________________________________________________________

RTC DEFECT:	441870
APAR:   	IT04640
DATE:         	9/29/14
MODULE:       	MailboxArchive.dll

PROBLEM DESCRIPTION:  Importing export files that contain Mailbox Delivery Rules with double quotes in the comments field can result in the failure to import the delivery rule.


FIX DESCRIPTION:  Fixed Mailbox Archive to encode and decode double quotes in XML attributes during Export and Import processes.




_______________________________________________________________________________

RTC DEFECT:	438901
APAR:   	IT04794
DATE:         	10/7/14
MODULE:       	Partnred.exe

PROBLEM DESCRIPTION:  Partner Editor Table duplicate errors do not include sufficient information to identify duplicate field.  Error messages are inconsistent and format and content is dependent on database and ODBC driver versions.


FIX DESCRIPTION:  Added tests for duplicates entries and report duplicate fields in new error messages.  Added duplicates checks for each case:

Cross Reference: My Value
Cross Reference: My Partner
Lookup: Lookup Value




_______________________________________________________________________________

RTC DEFECT:   	438914
APAR:          	
DATE:         	10/15/14
MODULE:       	all modules except for mapper and components

PROBLEM DESCRIPTION:  While debugging, saw that the default type member variable for Gentran recordsets was overriding parameters passed into the Open function calls.

FIX DESCRIPTION:   Changed recordsets for all modules to use "dynaset" instead of "snapshot".  This is needed to sync with the ODBC cursor library changes.


_______________________________________________________________________________

RTC DEFECT:	442792
APAR:   	IT05257
DATE:         	10/29/14
MODULE:       	Unattend.exe, ArchiveEngine.exe

PROBLEM DESCRIPTION:  The Archive Engine would not delete items when it found Process Control Scheduled Events running during its item deletion phase.  Addtionally, the Archive Engine would not report the Event name of the running processes, and it would not filter the Process Control Event that started the Archive Engine process, causing false positives, preventing the deletion of items.



FIX DESCRIPTION:  Fixed the Archive Engine to check if a running Process Control Schedule Event has the same Session File as was used to start the Archive Engine.  If it is, and it is the only running Process Control Event, the Archive Engine ignores the running process and proceeds with the deletion of archived items.  If the Archive Engine find other running Process Control Event, it reports the first event it finds that does not have the same Session File name, and sleeps for ten seconds before checking the running process again.  This cycle will repeat until the timeout duration has expired, or the Archive Engine is able to suspend all process except its own.




_______________________________________________________________________________

RTC DEFECT:	445693
APAR:   	IT05270
DATE:         	10/30/14
MODULE:       	Commpost.exe

PROBLEM DESCRIPTION:  Commpost could incorrectly pass BIN segment binary data to the translator, rather than creating a file with the binary data and replacing the binary data with the new file name, prior to translation. 



FIX DESCRIPTION:  Fixed Commpost to correctly process binary data in valid binary segments regardless of presence of data that matches binary segment ID strings found in EDI data before or after binary segments.



_______________________________________________________________________________

RTC DEFECT:     446252
APAR:          	IT05431
DATE:         	11/10/14
MODULE:       	Unattend

PROBLEM DESCRIPTION:  Unattend reports audit error, 1-3-1594, for any Session step that included an "If File Below Exists" condition, if the file in question does not exist.  This new error message was added with patch 5.3.1.4, but the new error could not be repressed, regardless of the of associated Registry entry, UnattendFileRetry. 


FIX DESCRIPTION:  Fixed Unattend to report Audit message warning 1-3-1534 if Process Control Session condition is "If File Below Exists", the condition is true, the file does not exist, and the Registry value of UnattendFileRetry is zero.  If the registry value for UnattendFileRetry is greater than zero, Unattend will log the Audit Report error 1-3-1594.  

Additionally, Unattend was updated to create the value registry settings with default value of 0, if it does exist:

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1
value name: UnattendFileRetry
default value: 0



_______________________________________________________________________________

RTC DEFECT:   	445106
APAR:          	IT05600
DATE:         	11/12/14
MODULE:       	RpcSrv.exe, GenCom97.exe, Mercury.exe

PROBLEM DESCRIPTION:  When the Mailbox, Executive or Communications services are unregistered and re-registered as a Windows service using the 
command-line parameters, the service dependencies and/or file path are not correct and the service cannot be started in the Windows Service Control
Panel.  

FIX DESCRIPTION:  Modified code to use the correct service dependencies and file path during the registration process.


_______________________________________________________________________________

RTC DEFECT:   	447771
APAR:          	IT05976
DATE:         	11/20/14
MODULE:       	ArchiveEngine.exe

PROBLEM DESCRIPTION:  Archive sessions could fail during External Data and EDI Archive with the error, Unable to obtain Mutex.


FIX DESCRIPTION:  Added additional exception handling and recover around all file closures, stream activity, and Mutex closures within all archive classes. Added additional logging to report failures that could lead to termination of Exclutive Services thread before releasing Mutex.



_______________________________________________________________________________

RTC DEFECT:   	449799
APAR:          	IT05901
DATE:         	12/3/14
MODULE:       	Mbfile30.dll

PROBLEM DESCRIPTION:  A File System Collection Mailbox could fail to either register with Windows Notification Event or fail to be triggered by a Windows Notification when files are placed in a remote system folder.  The File System Collection Mailbox would then pick up the files from the scan folder during the next scan internal.  However, the loss of the Windows Notification within a Collection Mailbox, without an audit message reporting the problem, could cause delays processing files.


FIX DESCRIPTION:  Added new Gentran Audit Message, 2-4-1031  Mailbox collected file(s) during Master Timer Event, which will be reported when a Mailbox collects files during a scan cycle started during a Master Timer Event.  The new Audit Message is disabled by default, to be used as a debug message.



_______________________________________________________________________________

RTC DEFECT:   	450628
APAR:          	IT06101
DATE:         	12/10/14
MODULE:       	Mbfile30.dll

PROBLEM DESCRIPTION:  A File System Collection Mailbox not being triggered with a Windows Notification Event could be wait for longer between scans than the Master Timer Interval, defined in the File System Gateway.


FIX DESCRIPTION:  Fixed a problem with the Master Timer resetting function, which would reset the Master Timer Event to the Master Timer Interval each time a Windows Notification Event was caught for any File System Collection Mailbox.  The Master Timer Event is not reset to the delta of the Master Timer Interval and the seconds that have passed since the last scan trigged by the Master Timer Event.  Additionally, changed the maximum number of File System Mailboxes that will register for Windows Notification Events, to 56 from 62, to prevent the exhaustion of Windows Notification Event HANDLEs, which can cause all Mailboxes to lose their Windows Notification Events for the Master Timer Interval cycle.



_______________________________________________________________________________

RTC DEFECT:   	434124
APAR:          	IT04483
DATE:         	12/11/14
MODULE:       	sapint.exe

PROBLEM DESCRIPTION:  sapint.log does not have enough information to tell why sapint.exe is not working

FIX DESCRIPTION:  Added debug logging to sapint.exe which is enabled with the following new registry setting:

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1\SAP
reg value name: DebugLog
reg value: Y or N (off by default)


_______________________________________________________________________________

RTC DEFECT:   	453973
APAR:          	IT06773
DATE:         	1/26/15
MODULE:       	Mbfile30.dll

PROBLEM DESCRIPTION:  When a user temporarily unchecks and rechecks the "Collect files into this mailbox" checkbox in a File System Collection mailbox,
most of the mailbox settings are retained but the following will happen with the Content Type settings: (1) if originally populated, the field values 
will disappear or (2) if originally disabled, the fields will be re-enabled despite having their corresponding checkboxes selected.

FIX DESCRIPTION:  (1) Removed code that loaded the Content Type fields with default (blank) values whenever the collection checkbox is enabled.  These 
fields will now retain their original values. (2) Added code that will keep the Content Type fields disabled if they were originally disabled.


_______________________________________________________________________________

RTC DEFECT: 	453839
APAR:   	IT07072
DATE:         	2/3/2015
MODULE:       	Translator

PROBLEM DESCRIPTION:  Division Lookup could fail to to return a value during translation for the n-th document in an input file during the import processs.


FIX DESCRIPTION:  Fixed the translator to force a new query to repopulate the Lookup buffer for the next Lookup when a query returns an empty set.  




_______________________________________________________________________________

RTC DEFECT:	455655
APAR:   	IT07196
DATE:         	2/17/2015
MODULE:       	GenCom97.exe GenComPC.exe

PROBLEM DESCRIPTION:  The error "6-1-50003 RpcServerUseProtseqEp (Local) failed at line 300: The endpoint is a duplicate" can be written to the Audit Log for both GenCom97.exe and GenComPC.exe when both are running without other errors.


FIX DESCRIPTION:  Added additional logging for Duplicate Endpint RpcServerUseProtseqEp failures.  The GenCom97 error is written to the audit log when GenCom97.exe is started from the command line when the Communication Service is started or if GenCom97.exe is already running from the command line.  Similarly, the GenComPC error will be written when Mercury.exe is started from the command line, when it is already running as the Mailbox Service or from the command line.


_______________________________________________________________________________

RTC DEFECT:   	455839
APAR:          	IT07614 
DATE:         	2/25/15
MODULE:       	Mercury.exe, SCEMailGateway.dll

PROBLEM DESCRIPTION:  After upgrading from 5.1 to 5.3.1, the system cannot load the mailbox settings for email gateway mailboxes.  The Mailbox UI will
display a "gateway not configured" popup error when trying to view it.  If you create a new email mailbox in 5.3.1, it does not have this issue.

FIX DESCRIPTION:  In 5.1, 5.2 and 5.3, the mailbox properties file for an email gateway mailbox was stored in the Properties folder.  In 5.3.1, the
email gateway was accidently changed to load this file from (or save to) the Store folder.  Hence, new email mailboxes worked and existing ones failed
to load.  Fixed the email gateway to use the Properties folder again.  Also enhanced the Mailbox service to look for the properties file in the Store 
folder as well and move it to the Properties folder if it couldn't find it there originally.  The following new warning audit messages were also added:

2-1-1090: OpenAttachmentStream warning for attachment Id(20), message Id(20). Found E-Mail Gateway Settings mailbox file in the Store folder. Moving it to 
the Properties folder: C:\GENSRVNT\Store\#2015\02\11\14\20.ATM

2-1-1091: OpenAttachmentStream warning for attachment Id(20), message Id(20). Cannot move E-Mail Gateway Settings mailbox file from the Store folder to the 
Properties folder. Using it in Store for now: C:\GENSRVNT\Store\#2015\02\11\14\20.ATM


_______________________________________________________________________________

RTC DEFECT:	460799
APAR:   	IT08042
DATE:      	3/30/15
MODULE:    	RpcSrv.exe

PROBLEM DESCRIPTION:  Process Control errors 1-3-1550 and 1-3-1594 report not finding valid session files.  For example, 
1-3-1594 "Process Control - C:\GENSRVNT\Unattend\.SES"
1-3-1550 "Program Ending: Session File C:\GENSRVNT\Unattend\.SES not found".

FIX DESCRIPTION:  Report the actual SQL failure and abort, rather than passing an empty Session file name to Process control.  For example, 
1-2-1508 "Error accessing SCHEDULE_TB Query for [Event] failed to find match. [Event] value, SVR6A001 00000 0407115 120151"
1-2-6005 "Server: Failed to Create process UNATTEND.exe with , error 0"


_______________________________________________________________________________

RTC DEFECT:   	463250
APAR:          	IT08686
DATE:         	5/1/15
MODULE:       	Unattend.exe

PROBLEM DESCRIPTION:  Enabling the UnattendFileRetry registry setting allows retries for the "If File Below Exists" condition, but the corresponding 1-3-1594
retry audits can fill up the audit log.

FIX DESCRIPTION:  Added new registry setting that will enable/disable the 1-3-1594 retry audits.  This setting is created automatically and the retry audits
are disabled by default.

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1
reg value name: UnattendFileRetryAudits
reg value: 1 or 0 (off by default)


_______________________________________________________________________________

RTC DEFECT:   	463446
APAR:          	IT09022
DATE:         	5/20/15
MODULE:       	aleserver.exe

PROBLEM DESCRIPTION:  In 5.3.1 patch 2, if the "Auto Start" feature is enabled in the SAP Configuration app (Advanced dialog), pressing the stop button 
does not actually stop the ALEServer despite what the status indicator says.  Pressing the start button again actually launches another instance of 
ALEServer leading to multiple copies of aleserver.exe.  (If the Auto Start feature is disabled, the start/stop button works correctly.)

FIX DESCRIPTION:  Fixed the name of aleserver process id used by the auto-start feature to stop aleserver.exe.


_______________________________________________________________________________

RTC DEFECT:   	461375
APAR:          	IT10435
DATE:         	5/22/15
MODULE:       	sapint.exe

PROBLEM DESCRIPTION:  Need to add more debug tracing in sapint.log when executing sapint -extract command to help troubleshoot when problems arise.

FIX DESCRIPTION:  Extended the debug logging framework that was added to sapint.exe in RTC#434124 to include -extract, -update, and -startrfc commands.
As before, the following registry setting needs to be enabled to see the debug messages in sapint.log:

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1\SAP
reg value name: DebugLog
reg value: Y or N (off by default)


_______________________________________________________________________________

RTC DEFECT:   	469842
APAR:          	
DATE:         	6/30/15
MODULE:       	Mbfile30.dll

PROBLEM DESCRIPTION:  Need to add more error info to the collection mailbox error audit 2-4-1024 when windows notification event fails.

FIX DESCRIPTION: Added GetLastError info string to the end of the 2-4-1024 audit message. 


_______________________________________________________________________________

RTC DEFECT:	470217
APAR:   	IT09889
DATE:         	7/2/15
MODULE:       	patch install

PROBLEM DESCRIPTION:  Patch install fails with a "setup encountered an error" message.  Using debug popups, the last status message that 
was displayed before the error was "Importing mapper reg file into registry..."

FIX DESCRIPTION:  Removed legacy code that imported an updated mapper registry file.  It's currently not needed for the 5.3 and 5.3.1 patch 
installs.


_______________________________________________________________________________

RTC DEFECT:   	470519
APAR:          	IT09936
DATE:         	7/8/15
MODULE:       	Unattend.exe

PROBLEM DESCRIPTION:  In 5.3.1 patch 4, GDW_Print unattend session is configured to print 820 documents but writes a 1-3-1608 audit error
complaining about "no print template found" for 862 documents.

FIX DESCRIPTION:  Added additional checks to ensure that relationship and print template checks were only done for documents in the InDocs 
browser that matched the criteria specified in the GDW_Print session file.


_______________________________________________________________________________

RTC DEFECT:   	470527
APAR:          	
DATE:         	7/14/15
MODULE:       	tx32.exe, GNTXEng.exe

PROBLEM DESCRIPTION:  The translator debug audits that were added in RTC#394392 only covers the inbound break process.  Need to add debug audits
to the export process too.

FIX DESCRIPTION:  Added info debug audits (3-1-5008) to the translator export process.  They are enabled/disabled using the same registry setting
as before:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1
value name: TranslatorDebugAudits
default value: 0  (off)

This is off by default and can be enabled by changing the registry setting to 1.


_______________________________________________________________________________

RTC DEFECT:   	461082
APAR:          	IT10847
DATE:         	7/28/15
MODULE:       	MClient.exe

PROBLEM DESCRIPTION:  On a Windows 2012 OS, MClient could report an application error and terminate at startup.

FIX DESCRIPTION:  Changed the storage of the MClient Root Node Handler to static, in order to correctly find and build the 
Mailbox Tree View under the 2012 MFC Runtime threading in Windows 2012.  



**************************************************************************
                                 PATCH 6
**************************************************************************

RTC DEFECT:   	474588
APAR:          	
DATE:         	8/14/15
MODULE:       	MClient.exe

PROBLEM DESCRIPTION:  In 5.3.1 patch 5, the Mailbox Client menu options, Unregister Server, Create and others are not enabled when the mailbox nodes
are selected.  This is a new bug that appears to be related to the Win2012 MClient fix for RTC#461082.

FIX DESCRIPTION:  Fix for bug in RTC#461082 that caused the UI to only display menu options with right click, rather than through edit menu or buttons.


_______________________________________________________________________________

RTC DEFECT:   	477192
APAR:          	IT12011
DATE:         	10/1/15
MODULE:       	Mercury.exe, MailboxEvent.xml

PROBLEM DESCRIPTION:  Need ability to see that the Mailbox purge routine has been started in the Audit Log, not just as a Mercury console message.

FIX DESCRIPTION:  Added new audit message 2-1-1092 "Starting mailbox purge" at the beginning of the purge function.


_______________________________________________________________________________

RTC DEFECT:   	479627
APAR:          	IT11818
DATE:         	10/12/15
MODULE:       	MBMAPI30.dll

PROBLEM DESCRIPTION:  After applying 5.3.1 patch 4 and deleting the MAPI Gateway registry setting, when re-selecting the MAPI profile in the MAPI 
Gateway property settings, the Mailbox service crashes.

FIX DESCRIPTION:  MAPI API call to get the attachment properties returned a bad pointer value (0x8004010F = MAPI_E_NOT_FOUND).  Added code to look
for MAPI_E_NOT_FOUND before assigning MAPI values to a string variable.


_______________________________________________________________________________

RTC DEFECT:   	480882
APAR:          	IT12244
DATE:         	11/20/15
MODULE:       	SCEmailTransport.dll

PROBLEM DESCRIPTION:  When Email Gateway mailbox tries to send a message using customer's new SMTP server, they get a 16-3-5 error ("... Unable to initialize 
SMTP session using HELO command.  Check your SMTP server settings.")  New SMTP server has a multiple 220 line response to open session request.

FIX DESCRIPTION:  (1) Added more 16-6-1 audits (shown when detailed logging selected in mbx settings) during the open SMTP session and SMTP HELO commands.
(2) Modified open session command to handle multiple 220 lines returned by the SMTP server in their welcome banner response.


_______________________________________________________________________________

RTC DEFECT:   481235 	
APAR:         IT12494  	
DATE:         11/30/15 	
MODULE:       MClient.exe 	

PROBLEM DESCRIPTION:  After applying 5.3.1 patch 5 on a GSW client, user cannot expand the Mailbox tree node in the Mailbox UI to view the list of mailboxes.
Will get popup error: "<servername> is not registered server. Please, run setup program to join server at <servername>".

FIX DESCRIPTION:  A new GSW enhancement RTC#444425 was added to 5.3.1.5 which appended the GSW system name to the mailbox server name in the root node of the
Mailbox UI (e.g., "myServerName - [mySystemName]").  Modified code to also look for the "Primary Server" registry setting if it can't find the "MailboxServer"
registry setting.


_______________________________________________________________________________

RTC DEFECT:   	481647
APAR:          	IT13051
DATE:         	12/18/15
MODULE:       	MBMAPI30.DLL

PROBLEM DESCRIPTION:  After sending a MAPI message, the GSW system received a MAPI Confirmation of Delivery (COD) message as a reply and an error audit was 
generated (2-5-1052: "The MAPI attach method (5) of attachment 4102449 (message 2682289) is not supported").  COD's are not supported in GSW but customer
doesn't want to get a false-positive error notification for this audit message every time they send a MAPI message.

FIX DESCRIPTION:  Create a new info audit message for this scenario.  2-5-1056: "MAPI message contains Confirmation of Delivery (COD) in attachment %1 (message %2) 
but is not supported."


_______________________________________________________________________________

RTC DEFECT:   	423505
APAR:          	IT02393
DATE:         	6/3/14
MODULE:       	BRK997.map, BRK999_DETAILED.map

PROBLEM DESCRIPTION:  When translating inbound 997 or 999 documents containing AK103 or AK203 elements, will get "Too Many Elements" error in translator report.

FIX DESCRIPTION:  Added AK103 and AK203 elements to the BRK999_DETAILED.map and AK203 element to BRK997.map.


_______________________________________________________________________________

RTC DEFECT:   	481614
APAR:          	IT12899
DATE:         	12/7/15
MODULE:       	Partnred.exe

PROBLEM DESCRIPTION:  The Partner Editor could report an ODBC error when editing an existing record in a Partner Cross Reference Table.  If the Edit was to change the Partner Value, and the Partner Value had not been used before, the Cross Reference record could not be saved.  

FIX DESCRIPTION:  Fixed the query order of the Cross Reference table, to query the Partner Value first, then query for the My Value second.  Doing this in reverse caused the "Operation failed, no current record" error, when the new Partner Value did not exist in the DB.  An additional fix now checks if the Partner Value exists in the Cross Reference Table before attempting to Update the Record.  In this way, the warning, "Partner Value already used, {partner value}" is issued, instead of an ODBC exception.



_______________________________________________________________________________

RTC DEFECT:   485106
APAR:         IT13601
DATE:         1/24/16
MODULE:       aleclient.exe	

PROBLEM DESCRIPTION:  The aleclient.exe connection to SAP is failing and it does not log any info.  Aleclient needs logging to see if the correct values are being passed in as intended.

FIX DESCRIPTION:  Added debug logging to aleclient.exe that will write to an aleclient_trace.txt file in the Gensrvnt folder.  It is enabled using the same registry setting added in 
RTC#434124 for sapint.exe debug logging:

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1\SAP
reg value name: DebugLog
reg value: Y or N (off by default)

It will log the aleclient command-line parameters, the SAP RFC connection string and any RFC errors returned.


_______________________________________________________________________________

RTC DEFECT:   	488487
APAR:          	IT13765
DATE:         	2/2/16
MODULE:       	SCEmailGateway.dll

PROBLEM DESCRIPTION:  When the 5.3.1 Email Gateway (SMTP) mailbox has the "Send as attachment" setting checked, the email messages sent have attachments
with random filenames instead of the original filename.

FIX DESCRIPTION:  Added code to use the original filename of the attachment when constructing the email message.


_______________________________________________________________________________

RTC DEFECT:   	491727
APAR:          	IT13941
DATE:         	2/23/16
MODULE:         GNTXEng.exe

PROBLEM DESCRIPTION:  Unable to perform INSERT into DivisionLookup or PartnerLookup tables in map extended rules.  Audit log error 3-1-201: "Database Error: 
Primary Key already exists in Lookup_tb, exiting insert: PartnerKey = SYSTEMUSR, TableName = 614894, Item = 33333".  This happens with Oracle or MSSQL.

FIX DESCRIPTION:  The fix for RTC#417562 added a check for duplicate entries.  It would write a new audit message that tried to explain why it couldn't insert a 
new entry if there was a duplicate entry.  However, it wound up preventing any inserts from working (even if there was no duplicate).  Also, that new audit message 
was written in the opposite scenario that was intended (if there was a duplicate entry, no audit is written. If there is no duplicate entry, the audit is written).
Fixed code to (1) use a new recordset for the duplicate check and (2) write that audit message in the appropriate scenario.


_______________________________________________________________________________

RTC DEFECT:   	490450, 495874
APAR:          	IT13772
DATE:         	3/30/16
MODULE:       	Edimgr.exe, Partnred.exe, Proccntl.exe

PROBLEM DESCRIPTION:  After installing 5.3.1 patch 4, it takes much longer for the EDIMGR browsers to display their contents when the database is on another 
subnet or behind an intranet firewall.  This can affect the client and/or server depending on where GSW is installed in relation to the database.

FIX DESCRIPTION:  The slowness started happening when the ODBC cursor library was removed from the product due to issues found in RTC#394322.  Added code
to use the ODBC cursor library again but only for EDIMGR, Partner Editor and Process Control.


_______________________________________________________________________________

RTC DEFECT:   	506830
APAR:          	IT16052
DATE:         	7/8/16
MODULE:       	Edimgr.exe

PROBLEM DESCRIPTION:  The EDIMGR Out Drawer doc browser is not showing the datetime values for the new "Processed Time" column that was added in patch 5 (RTC#444423).

FIX DESCRIPTION:  The Out Drawer has a load function that is separate from the other doc browsers.  Added the enhancement code to it.


_______________________________________________________________________________

RTC DEFECT:   	501323
APAR:          	IT16245
DATE:         	7/19/16
MODULE:       	ANServer.exe

PROBLEM DESCRIPTION:  5.3.1 Audit service randomly crashes when sending audit notification SMTP emails.

FIX DESCRIPTION:  All the crashes happened during the execution of the Microsoft WideCharToMultiByte API call while building the email message.  Replaced those API calls
with T2A macros for the email message body text and subject field text.  Also increased the data buffers used for those string conversions by 1 to include the terminating 
NULL character and added missing cleanup operations for those data buffers.


_______________________________________________________________________________

RTC DEFECT:   	509041
APAR:          	IT16368
DATE:         	7/28/16
MODULE:       	GenCom97.exe

PROBLEM DESCRIPTION:  GenCom97 service crashes during FtpRcvFile when trying to access a file or directory that does not exist and SetRcvNoData is not set/used.

FIX DESCRIPTION:  The fix for RTC#418953 in patch 4 used a string search command without ensuring that the parameter passed into it was not NULL (which happens when 
SetRcvNoData is not set).  Added code to make sure that the RTC#418953 fix is only executed if SetRcvNoData is set.



**************************************************************************
                              PATCH 7
**************************************************************************

RTC DEFECT:   514913
APAR:         IT17197
DATE:         9/23/16
MODULE:       GNTXEng.exe

PROBLEM DESCRIPTION:  5.3.1 inbound processing occasionally gets a 1-6-2001 error ("Translation using gntxeng.exe failed with error 80040702 and 800706be").
When the TranslatorDebugAudits registry setting is turned on, the 3-1-5008 debug audits show that the translator is doing transaction level processing 
("BreakInterchange::OnInitiate() - Transaction - SetTranslatorReportFile() - \\GENTRAN\GENTRAN_DATA\TranRpt\#2016\09\21\04\INT338053.RPT") or document level processing ("BreakInterchange::OnDocumentInitiate()") right before it throws a 3-1-1741 error ("Translator: BreakInterchange::OnInitiate() - CTranslatorException - Error code: 6").

FIX DESCRIPTION:  Like RTC#394392, the inbound translator throws an exception when it can't set/open a report file, but this time at the transaction level or document level.  
Extended the retry logic and debug audits to transaction and document levels as well as interchange and ack extract levels too.

This fix uses the same retry and debug audit registry settings from RTC#394392:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1\
value name1: TranslatorFileRetry
default value: 5
value name2: TranslatorFileSleep
default value: 1000  (milliseconds)
value name: TranslatorDebugAudits
default value: 0  (off)


_______________________________________________________________________________

RTC DEFECT:   	512625
APAR:          	IT17417
DATE:         	10/7/16
MODULE:       	Unattend.exe, AuditMsgFile.xml

PROBLEM DESCRIPTION:  System-MBRecovery event hangs when other unattend events are running at the same time and accessing the same resources.

FIX DESCRIPTION:  Added code to the beginning of MBRecovery event that will check to see if other unattend events are already running.  If so, write new warning
audit 1-3-1609 "Process Control - Unable to run Recovery_Inbound right now. Other unattend events are currently running. Recovery_Inbound cancelled."  Same audit
for Recovery_Outbound command too.


_______________________________________________________________________________

RTC DEFECT:   	523662
APAR:          	IT18713
DATE:         	1/6/17
MODULE:       	ANServer.exe

PROBLEM DESCRIPTION:  When doing a file collection with a mailbox name longer than 42 characters, it creates audit log entries with an event name longer than the 
max database column size (50 chars).  While the Audit service truncates the event name string to 50 chars before doing a SQL insert, it still writes a warning
message to the Event Log about the truncation.  Since multiple audit log entries are written for a single file collection, these truncation warnings fill up the
Event Log making it difficult to find real errors.  Also, if any notifications are generated during the file collection, the Audit service does not truncate the 
event name string in that case and SQL truncation errors are written to the Event Log.

FIX DESCRIPTION:  Changed the audit log writes to not write a truncation warning message to the Event Log and added a max string length check and truncation code
to the notify log writes.


_______________________________________________________________________________

RTC DEFECT:   	527992
APAR:          	IT19266 
DATE:         	2/17/17
MODULE:       	Partnred.exe

PROBLEM DESCRIPTION:  Can't save an existing Cross Reference entry in Partner Editor after editing the Description or Reference Data fields.  Will get "ERROR: 
Duplicate Item" popup.  The CrossRef Entry dialog will also close and lose all the changes.

FIX DESCRIPTION:  The fix for RTC#481614 wound up being too restrictive when editing an existing entry.  Added code to only display the duplicate error if the user
changed the Partner Value to another existing value.  Also, if a duplicate error does popup, the Entry dialog will now stay open to allow the user to change the
Partner Value to another value and try saving again.


_______________________________________________________________________________

RTC DEFECT:   	530115
APAR:          	IT19664
DATE:         	3/10/17
MODULE:       	Mercury.exe

PROBLEM DESCRIPTION:  If mailbox tracing is enabled in MClient, while creating or editing a mailbox archive definition in Archive Manager, clicking the Add or Edit 
buttons will display a popup error ("Unable to get Mailboxs from the server") and crash the Mailbox service.

FIX DESCRIPTION:  The mailbox tracing code in Mercury did not properly initialize the message parameters pointer array resulting in some unused elements having
invalid memory addresses.  Added code to clear out the pointer array before being used.


_______________________________________________________________________________

RTC DEFECT:   	533358
APAR:          	IT20100
DATE:         	4/5/17
MODULE:       	tx32.exe

PROBLEM DESCRIPTION:  Trying to import flat file to TRADACOMS INVOIC will get the following audit errors:
3-1-1731 Translator:######: TRANSACTION SET: INVOIC, RELEASE: 0, TEST MODE: P
3-1-1730 Translator: Primary key: PARTNER: ABCDEF, DIRECTION: Out, AGENCY: A, VERSION: ANA001,
3-1-1729 Translator: Relationship not found
Audit shows "RELEASE: 0" but the partner outbound relationship is set to Release 9 per TRADACOMS standards.

FIX DESCRIPTION:  When translator was searching for the partner relationship in the database, it always passed in 0 for the Release value.  While this was fine for
other standards that don't have a Release value (or use Release 0), it's an issue for any standards like TRADACOMS that have non-zero Release values.  Added code to
try the database query again with the actual Release value if the initial query fails to find a match.  Also, modified audit 3-1-1731 to report the actual Release
value.


_______________________________________________________________________________

RTC DEFECT:   	535345
APAR:          	
DATE:         	4/13/17
MODULE:       	sapint.exe

PROBLEM DESCRIPTION:  Need more debug logging with the sapint.exe -extract option to see what values are used when creating the Response/Status IDOC.

FIX DESCRIPTION:  Added more debug logging to the WriteStatus function that's used by sapint -extract.  As before, the following registry setting needs to be enabled 
to see the debug messages in sapint.log:

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1\SAP
reg value name: DebugLog
reg value: Y or N (off by default)


_______________________________________________________________________________

RTC DEFECT:   	542883
APAR:          	IT21192
DATE:         	6/27/17
MODULE:       	sapint.exe

PROBLEM DESCRIPTION:  (1) When SAPINT.EXE -Translate is not writing to SAPStatus_tb, sapint.log has a debug info message that is too cryptic with variable names:
"[DoPostProcess] Not writing SAP statuses. Send_Tran_Stat = 0. Send_Failed_Stat_Only = 0"
Need to alter that log message to indicate why this message is happening in more user-friendly terms.
(2) When compliance status is not ok, debug logging incorrectly states "Not writing SAP Statuses..." but SAP statuses are written in error cases too.

FIX DESCRIPTION:  (1) Altered log message to use the checkbox names in SAPConfig instead of variable names:
"[DoPostProcess] Not writing SAP statuses due to SAPConfig settings: 'Transaction Status' is unchecked and 'Send Failed Statuses Only' is checked"
(2) For compliance-not-ok case and partner-or-map-not-found case, adjusted logic to write appropriate debug log message when SAP statuses are or are not written.
(3) Appended filename being processed to existing debug log message: "DoPreProcess: filename = C:\gensrvnt\imports\SAP_R3_40_810_3050_I.txt"


_______________________________________________________________________________

RTC DEFECT:   	543021
APAR:          	
DATE:         	7/7/17
MODULE:       	sapint.exe

PROBLEM DESCRIPTION:  For sapint.exe -update, sapint.log does not indicate when SAPStatus_tb entries are skipped due to the SAPConfig options under the General tab
like it does for sapint.exe -translate.

FIX DESCRIPTION:  Added more debug log messages to sapint -update to indicate whether it was "Writing SAP statuses" or "Not writing SAP statuses due to SAPConfig settings...".


_______________________________________________________________________________

RTC DEFECT:   	518334
APAR:          	IT22953
DATE:         	10/25/17
MODULE:       	Commpost.exe

PROBLEM DESCRIPTION:  Inbound 275 containing multiple BIN segments will only export first iteration of LX group containing the BIN segment.

FIX DESCRIPTION:  The BIN 01 field contains the length of the binary data in the BIN 02 field.  For example:
BIN*734340*SUkqAPw0AQAtolEL8mydFnMlK50UIyAkJJF......

When the inbound interchange goes through the splitter, the binary data is saved into a file in the IntIn folder and replaced with the file's UNC filepath in the 
BIN 02 field:
BIN*734340*\\myPC\GENSRVNT\IntIn\#2017\01\20\09\IN0935560894444.BIN~

If there's a second BIN segment in the interchange, the splitter will create another file for that binary data:
BIN*329396*\\myPC\GENSRVNT\IntIn\#2017\01\20\09\IN0935560894444_2.BIN~

When the translator starts the export process, it reads the BIN 01 field and thinks the BIN 02 data (UNC filepath) is 734340 bytes long (when it's actually just 
56 bytes now).  As a result, the translator continues to read everything afterwards as part of the BIN 02 data which includes the 2nd LX group and its BIN segment.  
This behavior was not an issue when there is only one BIN segment and it's the last item in the document.  Modified the splitter code to replace the length of the 
binary data in the BIN 01 field with the length of the UNC filepath instead.


_______________________________________________________________________________

RTC DEFECT:   	545486
APAR:          	
DATE:         	12/12/17
MODULE:       	aleclientnw.exe, aleservernw.exe, sapint.exe, sapconfg.exe, sapserver.dll, rpcsrv.exe

PROBLEM DESCRIPTION:  The SAP classic libraries (librfc32.dll) are being sunset and replaced by NetWeaver libraries (32-bit, unicode).  We've created new aleclientnw.exe 
and aleservernw.exe command-line programs to use the NetWeaver libraries in our SAP Extension product.

FIX DESCRIPTION:  (1) Added new radio button controls to the General tab in SAPConfig UI to indicate whether the classic SAP libraries or the NetWeaver libraries are used.  
This is set to "classic" by default.  (2) Modified sapint.exe, sapserver.dll, and rpcsrv.exe to add new NetWeaver parameters used to invoke aleclientnw.exe and aleservernw.exe
(3) Added aleclientnw.exe and aleservernw.exe to the 5.3.1 patch install.



**************************************************************************
                              PATCH 8
**************************************************************************

RTC DEFECT:   	558118
APAR:          	IT23844
DATE:         	1/24/18
MODULE:       	GNTXEng.exe, tx32audits.xml

PROBLEM DESCRIPTION:  When processing an inbound ISA interchange containing both X12 and UCS groups, translator will error some of the groups since only one agency is 
allowed per interchange.  Unfortunately, the errors written to the audit log (3-1-1736: "Translator: Template not found for partner: <PARTNER-NAME> and templatekey ") 
are not desciptive enough to indicate what's wrong.

FIX DESCRIPTION:  Added a new error audit message detailing what parameters were used in the SQL query when it couldn't find the relationship in the partner database tables:
3-1-1737: "Translator: Relationship not found for Partner: <PARTNER-NAME>, Direction: In, Agency: X, Version: 004010UCS, TransactionSet: 940, Release: 0, TestMode: 0".
Also added more translator debug audits showing those parameters too whenever that SQL query is executed.


_______________________________________________________________________________

RTC DEFECT:   	567539
APAR:          	IT25202
DATE:         	5/25/18
MODULE:       	Edigmr.exe

PROBLEM DESCRIPTION:  When resending an outbound Tradacoms interchange from the Interchange Browser, a popup error displays "The parameter is incorrect" and
crashes Edimgr.

FIX DESCRIPTION:  DCOM function call to TradacomsVersion.dll is not working and causes the popup error to be displayed.  Since that DCOM function (UpdateTradacomsVersion)
is only called by Edimgr, it has been copied over to Edimgr and converted into a local function call instead.


_______________________________________________________________________________

RTC DEFECT:   	571256
APAR:          	IT25526
DATE:         	6/27/18
MODULE:       	mbfile30.dll

PROBLEM DESCRIPTION:  When the File System mailbox extracts data to a file, it does not write any audit messages indicating the extraction happened and makes analysis
difficult if issues arise.

FIX DESCRIPTION:  Add new info audit and fixed an number of audit-related issues in the extraction mailbox:

1) Added new info audit messages (2-4-1032 and 2-4-1033) to indicate successful extraction: "Gateway extracted data from message (%1) attachment (%2) into file (%3)"

2) In the unable-to-lock-file case, it does not write an audit message.  Added code to write an audit error in this case.  2-4-1029: "Unable to lock the file (%1), aborting".

3) The extraction-started audit message 2-4-1026 already exists, but was not used in the code.  Added it and also added a new parm to indicate the message id number 
in the audit too: "Gateway extraction started for message (%1)"

4) Audit message 2-4-1016 ("Unable to write the attachment data to the file") was missing parms that was used in the code.  Added these parms to the audit definition.


_______________________________________________________________________________

RTC DEFECT:   	573151
APAR:          	IT26204
DATE:         	9/5/18
MODULE:       	tx32.exe

PROBLEM DESCRIPTION:  tx32.exe crashes with audit error 3-1-1708 "Translator: Setup Failed" when manually sending 40+ documents from Out Documents browser.

FIX DESCRIPTION:  Similar to RTC#394392, the outbound translator crashes when it can't set/open a report file.  Added retry logic to it.  As before, if the number of retries
exceeds the maximum specified in the registry setting, the translator will error the process.  Also, added info debug audits (3-1-5008) to the translator build process.

This fix uses the same translator retry and debug audit registry settings as before:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1\
value name1: TranslatorFileRetry
default value: 5
value name2: TranslatorFileSleep
default value: 1000  (milliseconds)
value name: TranslatorDebugAudits
default value: 0  (off)


_______________________________________________________________________________

RTC DEFECT:   	573801
APAR:          	IT26425
DATE:         	9/26/18
MODULE:       	Proccntl.exe

PROBLEM DESCRIPTION:  On Windows Server 2016, when multiple 5.3.1 Unattend events run at the same time, the Process Control's Active Events tab will not allow users to
click on the other events running to see what command that event is current executing.  The UI is "stuck" showing the first event only.  Selecting other running events
to view what's happening works on older operating systems like Windows 7 and Windows Server 2012.  The Unattend events do complete successfully on Windows Server 2016.

FIX DESCRIPTION:  Created a new Process Control app that is compiled using Microsoft Visual Studio 2013 for use on newer operating systems.  The UI now works on Windows 
Server 2016.  To use this fix, users will need to (1) download and install the "Microsoft Visual C++ 2013 Redistributable (x86)" from Microsoft if they don't have it 
already and (2) copy the VS2013 Proccntl.exe from the patch Support folder to the Gentran Bin folder.  The VS2013 app will not be installed automatically by the patch install.


_______________________________________________________________________________

RTC DEFECT:   	575992
APAR:          	IT26740
DATE:         	10/16/18
MODULE:       	ACKHDR.tpl

PROBLEM DESCRIPTION:  Inbound 817 data contains P in ISA15 (for "Production") but the partner inbound 817 relationship is Test (with Generate Acknowledgments enabled) and the 
outbound 997 relationship is Test too.  During Commpost, the Translator goes into an infinite loop and does not stop.

FIX DESCRIPTION:  Modified the ACKHDR system map to use a key field to only process the 2 record from the positional flat file when importing to create the 997 acknowledgment.



**************************************************************************
                              PATCH 9
**************************************************************************

RTC DEFECT:	577840
APAR:   	IT28324
DATE:         	1/9/19
MODULE:       	BLD999_DETAILEDPARTIAL&REJECTCODES.tpl

PROBLEM DESCRIPTION:  The BLD999_DETAILEDPARTIAL&REJECTCODES.map causes the 999 to be generated incorrectly in the ?Out box since the translator is creating the Partner_Key 
(position2) of the 2 and 3 records in the flat file with 10 spaces.  This causes the wrong data to be read in to create the 999.  This happens in both 5.3 and 5.3.1.

FIX DESCRIPTION:  After increasing the Partner_Key to 25 spaces, the 999s are created as expected. The BLD999.map already has this change.



_______________________________________________________________________________

RTC DEFECT:   	579377
APAR:          	IT28335
DATE:         	2/18/19
MODULE:       	Commpost.exe

PROBLEM DESCRIPTION:  When processing multiple 275 transactions containing multiple BIN segments, the Splitter appears to skip a transaction and include the BIN from the skipped 
transaction into the previous transaction.  The .int file generated by Commpost in the IntIn folder shows this merged EFI/BIN segment in the problem transaction:

EFI*0BIN*59*\\AL540\Gensrvnt\IntIn\#2019\02\11\13\IN1318314139400_2.BIN~

It's supposed to be:

EFI*05~
BIN*59*\\AL540\Gensrvnt\IntIn\#2019\02\11\13\IN1318314139400_2.BIN~

FIX DESCRIPTION:  (1) This particular BIN data actually had "BIN" in the encoded binary string.  While Commpost did recognize that this was not the start of another BIN segment, 
it did not adjust it's BIN counter correctly.  Fixed counter to deal with this scenario.  (2) Also modified code to always use "~BIN*" when searching for the BIN segment tag in 
the data buffer when adding the UNC file path.


_______________________________________________________________________________

RTC DEFECT:   	581561
APAR:          	
DATE:         	3/23/19
MODULE:       	tx32.exe, GNTXEng.exe

PROBLEM DESCRIPTION:  The import process in the 5.3.1 translator does not have any debug audits.  Need to add them to the import translator too.

FIX DESCRIPTION:  Added info debug audits (3-1-5008) to the translator import process.  They are enabled/disabled using the same registry setting
as before:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1
value name: TranslatorDebugAudits
default value: 0  (off)

This is off by default and can be enabled by changing the registry setting to 1.


_______________________________________________________________________________

RTC DEFECT:   	567843
APAR:          	IT29078
DATE:         	4/7/19
MODULE:       	RpcSrv.exe

PROBLEM DESCRIPTION:  When GDW_Send session is running, in addition to sending new interchanges, it will occasionally send an old interchange as a new mailbox message resulting
in duplicate interchanges being sent.

FIX DESCRIPTION:  (1) The NextMessage ID counter on the customer's system was somehow reset to an earlier/old number and their system wound up reusing old MessageId numbers again.
While sending a new message, RPCSRV does a SQL query to lookup the interchange Id by the Message Id in order to update the interchange status from "Ready To Send" to "Sent".
Normally, this SQL query would only return one interchange.  This customer had multiple interchanges per Message Id.  Modified the SQL query to get the newest matching interchange 
instead. (2) Add more 1-2-50400 debug audits (enabled by UnattendTrace reg value in the registry) to indicate interchange Id and message Id currently being sent.  (3) Info message
"Resending %d interchanges stuck in ReadyToSend/Queued state at:" was only being written to the console window when RPCSRV was running in console mode.  Also write it as 1-2-50400 
debug audit too if that scenario occurs.


_______________________________________________________________________________

RTC DEFECT:   	586251
APAR:          	IT30304
DATE:         	9/24/19
MODULE:       	SAPServer.dll

PROBLEM DESCRIPTION:  Customer needs to see the command line parameters used to launch aleserver.exe in the SAP Extension.

FIX DESCRIPTION:  Added debug logging to SAPServer.dll to detail the starting/stopping of aleserver.exe or aleservernw.exe.  When the following registry setting is enabled, 
it will write log messages to C:\Gensrvnt\SAPServer.log.  This same registry setting is also used by sapint.exe and aleclient.exe to enable debug logging to their log files too:
C:\Gensrvnt\Bin\sapint.log and C:\Gensrvnt\aleclient_trace.txt, respectively.

reg key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Server\5.3.1\SAP
reg value name: DebugLog
reg value: Y or N (off by default)


_______________________________________________________________________________

RTC DEFECT:   	585231
JIRA DEFECT:    GT-2611
APAR:          	IT31005
DATE:         	12/8/19
MODULE:       	Partnred.exe

PROBLEM DESCRIPTION:  When importing a file to create Outbound EDIFACT data, the translator is adding a Release character ? to the data for every occurrence of the < symbol.  
While the < character is the default Repetition Separator in EDIFACT Syntax version 4, the customer is using Syntax version 3 which does not implement Repetition Separators.
So, the < is not used as a delimiter on the Trading Partner, nor does the Map contain values in the Delimiters tab or the Syntax Record tab.  In GSW 5.3.1 Patch #4 with same 
data, map, and partner - the output is generated correctly.

FIX DESCRIPTION:  A tx32.exe hotfix in patch 5 (RTC#435867) uses Repetition Separators in its code fix and was adding the ? release character in front of the < characters
due to a bug in Partner Editor that still saves the default Repetition Separator < in the GenericEnvelopeSegment_tb database table even if the partner is using EDIFACT Syntax
version 3.  Added code to NULL out the Repetition Separator field in the database when saving the Outbound UNB Envelope dialog if the EDIFACT syntax version is less than 4.
Users will need to open all EDIFACT Syntax version 3 partners (outbound relationships, interchange envelopes) and resave the Outbound UNB Envelope dialogs.



**************************************************************************
                              PATCH 10
**************************************************************************

JIRA DEFECT:    GT-2644/L3REQ-802
APAR:          	IT32297
DATE:         	3/1/20
MODULE:       	Partnred.exe

PROBLEM DESCRIPTION:  5.3.1 customer needs to use GSW Client apps that don't require admin rights on their laptop due to company policy.  There are already some of these 
apps in the "Support\NonAdmin" folder on the patch install image but Partner Editor is not included.  Need a NonAdmin version of Partnred.exe.

FIX DESCRIPTION:  As done in RTC#376817, added new project build modes that use the "AsInvoked" UAC setting so that non-admin Partnred.exe could be created without the 
"Run as Administrator" requirement.  This non-Admin executable 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
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


_______________________________________________________________________________

JIRA DEFECT:   	GT-2625/L3REQ-353
RTC DEFECT:		586870
APAR:          	IT32997
DATE:         	5/27/20
MODULE:       	Commpost.exe

PROBLEM DESCRIPTION:  When processing an interchange containing multiple BIN segments in a document, the resulting .INT file still has some of binary data in one of the BIN 
segments instead of the filepath of the .BIN file.  This seems to happen when a BIN segment has a short binary data length (in the 1000s) compared to the next BIN segment in
the same document.  Also, while all the .BIN files are generated correctly, the first BIN segment in the document lists the filepath of the last .BIN file in the document 
instead.

FIX DESCRIPTION:  Since the inbound file had no CR-LF characters and the binary data for the first BIN segment was relatively short, the file buffer wound up containing two BIN 
segments instead of one in a single read sequence.  Added more code to handle this scenario within the read loop.


_______________________________________________________________________________

JIRA DEFECT:   	GT-2649/L3REQ-409
APAR:          	IT33163
DATE:         	6/11/20
MODULE:       	aleclientnw.exe

PROBLEM DESCRIPTION:  Using SAP Netweaver mode, aleclientnw.exe cannot upload file containing multiple IDOCs to the SAP server.  Will get error message: "Error 2 when reading ... 
- unable to load idoc".

FIX DESCRIPTION:  aleclientnw was opening the IDOC file in text mode which converted all CR/LF pairs to just LF during read operations.  This affected the file pointer tracking.
Changed the app to open the IDOC file in binary mode which keeps all the CR/LF pairs in the read buffer and file pointer on track.


_______________________________________________________________________________

JIRA DEFECT:   	GT-2588
RTC DEFECT:		580608
APAR:          	IT33234
DATE:         	6/16/20
MODULE:       	Edimgr.exe

PROBLEM DESCRIPTION:  On Windows 10 (Version 1703 and newer) and Windows Server 2019, Edimgr.exe will crash if user clicks on the root node in the Interchange Browser.

FIX DESCRIPTION:  On newer Windows OS builds released after 2016, whenever a user selects a tree node in a tree view browser, the property mask that the Windows OS passes
into the TVN_SELCHANGED message handler can now be 0xfffffffe (-2).  This value when evaluated returns a false positive which fools the app into thinking there is a valid 
tree node pointer that can be used and causes the app to crash.  Added code to not use the message handler's lParam value if the property mask value is -2 (0xfffffffe).


_______________________________________________________________________________

JIRA DEFECT:   	GT-2652/L3REQ-854
APAR:          	IT33332
DATE:         	6/25/20
MODULE:       	ANServer.exe

PROBLEM DESCRIPTION:  The Audit/Notification service crashes when attempting to write a 5-1-12 system error audit due to a failed notification alert that couldn't be sent.

FIX DESCRIPTION:  Resulting crash dumps showed that the string pointer for the first parameter in the 5-1-12 audit was invalid and the service crashed when it tried to use it.
Added code to make sure that each parameter has a non-zero length before trying to use it.


_______________________________________________________________________________

JIRA DEFECT:   	GT-2666/L3REQ-1681
APAR:          	IT34540
DATE:         	9/14/20
MODULE:       	GNTXEng.exe

PROBLEM DESCRIPTION:  When processing inbound interchanges, the translator will sometimes write 3-1-203 thru 3-1-205 ODBC exception audit messages (3-1-204: "ODBC: MFC database 
exception in Program/RETCODE: Translation/-1State:S1T00,Native:0,Origin: [Microsoft][ODBC SQL Server Driver] Login timeout expired") before any translator debug audits in the 
break process.  While translator was able to recover from the ODBC exception and successfully redo the database operation again as shown in 3-1-205 audit, it's hard to tell 
which translator function was throwing those ODBC exception errors.

FIX DESCRIPTION:  Added more translator debug audits to the very beginning of the interchange break process and to the OpenDbConnection function.  The new audits showed in this 
scenario that the ODBC exceptions happened and recovered during the OpenDbConnection function.

The debug audits are enabled/disabled using the same registry setting as before:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1
value name: TranslatorDebugAudits
default value: 0  (off)


_______________________________________________________________________________

JIRA DEFECT:   	GT-2668/L3REQ-1892
APAR:          	IT34713
DATE:         	10/26/20
MODULE:       	tx32.exe, GNTXEng.exe

PROBLEM DESCRIPTION:  Some Translator registry settings that should have been created by previous translator hotfixes are missing for some users.  The settings should have been in:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1
reg values: TranslatorFileRetry, TranslatorFileSleep, TranslatorDebugAudit

The "Translation\5.3.1" registry tree itself is also missing too.

FIX DESCRIPTION:  The "Translation\5.3.1" registry tree is normally created by the TxTrace.exe UI when the user sets the txtrace log location.  If TxTrace was previously used then the 
translator registry settings would be created successfully.  However, not everyone has used the TxTrace utility.  (1) Added code to the translator to check for the "Translator\5.3.1" 
registry tree and create if it doesn't exist. (2) Also optimized the registry setting code in the import translator.



**************************************************************************
                              PATCH 11
**************************************************************************

JIRA DEFECT:   	GT-2680\L3REQ-20099
APAR:          	IT35718
DATE:         	1/26/21
MODULE:       	Edimgr.exe

PROBLEM DESCRIPTION:  In 5.3.1 patch 10 Edimgr app, the Help->About dialog does not show "10" for the patch number.  It only shows "Version 5.3.1 patch".  The file properties of edimgr.exe
does show "5.3.1.10" for File Version on the Details tab.

FIX DESCRIPTION:  Widened the version text field to accommodate 2-digit patch numbers.  The About dialog now shows "Version 5.3.1 patch 10".


_______________________________________________________________________________

JIRA DEFECT:   	L3REQ-21766/GT-2691
APAR:          	IT36634
DATE:         	4/16/21
MODULE:       	tx32.exe

PROBLEM DESCRIPTION:  When trying to build interchanges to send, tx32.exe crashes with audit error 3-1-1708 "Translator: Setup Failed".  This results in documents stuck in Processing.

FIX DESCRIPTION:  Similar to RTC#573151, the outbound translator crashes when it can't set/open a report file, this time at the group level and interchange level.  Added retry logic to those
places.  As before, if the number of retries exceeds the maximum specified in the registry setting, the translator will error the process.

This fix uses the same translator retry and debug audit registry settings as before:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1\
value name1: TranslatorFileRetry
default value: 5
value name2: TranslatorFileSleep
default value: 1000  (milliseconds)
value name: TranslatorDebugAudits
default value: 0  (off)


_______________________________________________________________________________

JIRA DEFECT:   	L3REQ-19305/GT-2690
APAR:          	IT36722
DATE:         	10/4/21
MODULE:       	Partnred.exe

PROBLEM DESCRIPTION:  Customer created P-OTHER import & export maps and partner relationships with mix of "ALL" and "All" versions.  1) After they changed some of the map versions 
from "ALL" to "All", they tried to edit the corresponding "ALL" inbound relationships, but in the Inbound Translation dialog, the updated "All" maps are no longer listed in the 
Export File template dropdown and the dialog can't be saved.  The Outbound Translation dialog for outbound relationships has the same problem with the Import template dropdown too.
2) Despite having both "ALL" and "All" maps being registered, when creating a new relationship, the Version dropdown only shows one case of "ALL" or "All" but not both.  The case 
shown is the first one retrieved from the database.  So if only "ALL" is shown in the Version dropdown, then the Transaction Set dropdown only shows transactions for "ALL" and not
for "All".  So in this scenario, the user can't create a relationship for the "All" transactions unless they re-compile/re-register their "All" maps to be "ALL".

FIX DESCRIPTION:  1) Added code to both Inbound and Outbound Translation dialogs to do a case-insensitive lookup in Template_tb database table for versions "ALL", "All", and "all"
only if the agency is type "OTHER" (P, J, K, M, etc).  For regular agencies and non-all versions, the version lookup in Template_tb is still case-sensitive. 2) Added code to both
Inbound and Outbound Relationship dialogs to do same as (1) for version lookup but only add "ALL" to the dropdown (even if there are only "All" or "all" maps).  For the Transaction 
Set dropdown, when version "ALL" is selected, show transactions for all matching "ALL", "All" or "all" maps.  When the new relationship is saved in the database, the version saved
will be "ALL" even if the template selected has "All" or "all" defined in the map details.  This will still work for the Translator when it does partner and map lookups.


_______________________________________________________________________________

JIRA DEFECT:   	L3REQ-28272/GT-2711
APAR:          	IT39005
DATE:         	11/5/21
MODULE:       	tx32.exe

PROBLEM DESCRIPTION:  GSW processes an inbound ISA correctly but the corresponding outbound 997 winds up in the red ?Out Tray and a 3-1-1729 "Translator: Relationship not found" error 
gets written to the Audit Log.  While the preceding 3-1-1730 and 3-1-1731 audits together detail some of the parameters used in the database queries, it's not totally clear which exact 
SQL query is failing to find a match.

FIX DESCRIPTION:  Added more translator debug audits (3-1-5008) detailing the function and SQL query that is failing to find a match with the SQL parameters used since there are several 
queries between where this could fail:  3-1-5008: ImportFile::FindDocumentTemplate() - SelectRelationshipKEY: PartnerKey = ABC123, Direction = 1, Agency = 88(X), Version = 005010X222A1,
TransactionSetID = 997, Release = 0, TestMode = 0

The debug audits are enabled/disabled using the same registry setting as before:

Key: HKEY_LOCAL_MACHINE\SOFTWARE\Sterling Commerce\GENTRAN\Common Components\Translation\5.3.1
value name: TranslatorDebugAudits
default value: 0  (off)


_______________________________________________________________________________

JIRA DEFECT:   	GT-2710
APAR:          	
DATE:         	11/19/21
MODULE:       	GenCom97.exe

PROBLEM DESCRIPTION:  When trace mode is enabled in the ftp mailbox settings, the FTP login password will be written out to the Communications Sessions log.  Need to replace the password string with asterisks in the log.

FIX DESCRIPTION:  Added code to replace the FTP password string with asterisks in the Sessions log.


_______________________________________________________________________________

JIRA DEFECT:   	L3REQ-25865\GT-2708
APAR:          	IT39799
DATE:         	12/22/21
MODULE:       	Patch Install

PROBLEM DESCRIPTION:  The VS2013 Proccntl.exe hotfix for Win2016 (APAR IT26425) that was in the Support\VS2013 folder on 5.3.1 patch 8 is missing from patch 9 and 10.

FIX DESCRIPTION:  Added the VS2013 Proccntl.exe hotfix to the 5.3.1 patch build process so it's automatically included in patch 11 and subsequent patches.


______________________________________________________________________________

JIRA DEFECT:   	L3REQ-29857/GT-2718
APAR:          	IT39592
DATE:         	1/7/22
MODULE:       	T_CREGRP.tpl

PROBLEM DESCRIPTION:  Customer needs new Tradacoms Group Build map for the CREDIT message.  Currently we provide the T_INVGRP Group Build map for Tradacoms INVOIC.

FIX DESCRIPTION:  Added new Functional Group Build map (source & compiled) for the Tradacoms CREDIT NOTE DETAILS.

This new map and tpl can be found in the Support folder of the patch install under: 

	Maps > Special > Source > T_CREGRP.map

	Maps > Special > Compiled > T_CREGRP.tpl

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


_______________________________________________________________________________

JIRA DEFECT:   	GT-2716
APAR:          	
DATE:         	1/31/22
MODULE:       	Patch Install

PROBLEM DESCRIPTION:  The 5.3.1 patch installer was upgraded to InstallShield 2019 for patch 11.  Customer ran the patch install but they didn't realize that they still 
had the Edimgr UI open.  While most of the GSW binaries in the Bin folder were successfully patched to patch 11, 3 binaries were still at the previous patch version: 
Edigmr.exe, Gensec.dll, and ANADCTXW.dll.  No errors were reported by the patch install though.

FIX DESCRIPTION:  Added check to the beginning of the patch install to look for any GSW modules that might still be open or running.  If the setup finds any, it will 
display a popup error listing the GSW modules that are still running and exit the setup before any patching is done.



**************************************************************************
                              PATCH 12
**************************************************************************

JIRA DEFECT:   	L3REQ-31529/GT-2728
APAR:          	IT40990
DATE:         	5/17/22
MODULE:       	Vatprint.exe

PROBLEM DESCRIPTION:  VATPRINT.EXE used to work in a delivery rule on a GSW 5.1 system but after GSW was upgraded to 5.3.1, VATPRINT now crashes when the delivery rule 
is invoked.  It also crashes when it's executed directly in a cmd window.

FIX DESCRIPTION:  The string buffer variable for the VATPRINT command-line had a maximum limit of 80 characters.  Since the customer had long paths (including $Input which
gets converted into an actual path at runtime), the command-line wound up exceeding 80 characters and corrupted the resulting file paths after parsing it.  Increased the 
string buffer size to accommodate long filepaths.


_______________________________________________________________________________

JIRA DEFECT:   	L3REQ-28712/GT-2730
APAR:          	IT41093
DATE:         	5/31/22
MODULE:       	Edimgr.exe

PROBLEM DESCRIPTION:  In Edimgr.exe, the doc browser views that have the "Processed Time" column do not sort in chronological order after that column header is clicked.

FIX DESCRIPTION:  Historically, the columns to sort on in the doc browsers just had names and/or numbers.  So, the sort algorithm just did a simple left-to-right string 
character compare.  When the Processed Time column was added later on in 5.3.1, it wound up using the default string sort instead of doing a datetime sort.  Added a 
datetime sort function for the Processed Time column.


_______________________________________________________________________________

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





**************************************************************************
                              PATCH 3
**************************************************************************

RTC DEFECT:     388212   
APAR:           IC94653
DATE:           8/5/2013         
MODULE:         TxEngine.lib

PROBLEM DESCRIPTION:  TX32 crashes/disappears when importing with a SQL map

FIX DESCRIPTION:  GSW 5.3.1 translator was updated to use MFC code for ODBC translation with a field to column binding limit of 
255 fields.  Trying to bind more than 255 fields to a DB table would result in TX32 crashing when performing cleanup.  We resolved
this issue by increasing the Field to Columns binding limit to 1024 to coincide with the amount of columns allowed in a single 
MSSQL Server table.


_____________________________________________________________

RTC DEFECT:  388554
APAR:        IC94814
DATE:        8/9/2013
MODULE:      MAPPER.EXE

PROBLEM DESCRIPTION:  Extended rule does not overwrite the linked value, when the source field is empty

FIX DESCRIPTION: Ported forward fix for GSW 5.0 SR1343625.  We had to change the way the string expression 
is parsed.  A temporary storage area in memory was created to store the result of the expression while it 
is evaluated first and then once it is evaluated that new tempary storage value contains the result we are 
looking for.



_____________________________________________________________

RTC DEFECT:   399147
APAR:         IC96978
DATE:         10/17/13
MODULE:       TxEngine.lib

PROBLEM DESCRIPTION:  Translator hangs when importing from MSSQL 2005 database if a date/time field is used in 
the update record, since migrating to GSW 5.3.1

FIX DESCRIPTION:  Added conditional formatting to Date / Time syntaxes for both MSSQL and Oracle to prevent
translator hangs when performing SQL Updates to records containing a Date / Time field.


_____________________________________________________________

RTC DEFECT:    400802  
APAR:          IC97265
DATE:          10/25/2013
MODULE:        TxEngine.lib

PROBLEM DESCRIPTION:  GSW 5.3.1 TX32.EXE crashes on import from MSSQL database

FIX DESCRIPTION:  Zero values pulled from a DB and fed into the Translator as a date would cause the Translator to crash.
We've added to check to catch any invalid dates or dates that are before 1970 and default them to a date/time of
Jan 1, 1970 the same as GSW 5.2


_____________________________________________________________
RTC DEFECT:     400808   
APAR:           IC97255   
DATE:           10/24/2013   
MODULE:         Mapper.exe   
     
PROBLEM DESCRIPTION:  Reported map compilation error line numbers could become incorrect if a SQL command spanned   
multiple lines.   
   
FIX DESCRIPTION:  Fixed line count to accurately reflect actual lines within a SQL command, rather than count   
each SQL command as a single line.   
   
   

_______________________________________________________________________________

RTC DEFECT:     399959
APAR:           
DATE:           11/12/2013
MODULE:         tx32.exe

PROBLEM DESCRIPTION:  Translation could fail with an assertion error if a trailing % followed a valid parameter 
list in the strdate Mapper function.  This is an extension of the fix for RTC defect 378775.


FIX DESCRIPTION:  Strip tailing % from strdate format strings, and enhanced translator to catch access violations
associated with runtime errors caused by invalid date formating or null dates.




**************************************************************************
                              PATCH 4
**************************************************************************

RTC DEFECT:     407895
APAR:           IC98783   
DATE:           1/14/2014   
MODULE:         Mapper.exe   

PROBLEM DESCRIPTION:  Mapper allowed Extended Rule CERROR with constant or variable as second argument, but this
OpCode feature was not available in the translator.  

FIX DESCRIPTION:  Report compilation error: 2011, No Field Specified, when CERROR Extended Rule does not include 
a Field number or name.


_____________________________________________________________

RTC DEFECT:     410622
APAR:           IC99186
DATE:           2/5/2014
MODULE:         Tx32.exe

PROBLEM DESCRIPTION: Translation error during build process of XML Interchange.  Large number of node related errors caused out of memory during translation. 

FIX DESCRIPTION:  Fix translator to limit generated node errors to 1000 per transaction.  Previously, no limit to node errors allowed excessive node errors to cause OOM errors during translation.


_______________________________________________________________________________

RTC DEFECT:     418946
APAR:           IT01226
DATE:           04/24/14
MODULE:         Mapper.exe

PROBLEM DESCRIPTION:  Activating a deactivated element/field with associated conditional fields does not automatically enable the associated conditional fields, nor does it warn that by not enabling associate field will invalidate conditional rules during translation.


FIX DESCRIPTION:  Added validation to Mapper when a element/field is activated and contains conditional rules with associated element.  If an element is activated and the element contains conditional rules that includes other disabled element, the Mapper will display a warning indicating relationship and ask for confirmation before enabling all associated elements.  If the user selects not to enable other elements, not elements will be enabled.




**************************************************************************
                              PATCH 5
**************************************************************************

RTC DEFECT:     431175
APAR:           IT03378
DATE:           6/24/2014
MODULE:         Txde.exe

PROBLEM DESCRIPTION:  Translation from EDI to Forms does not produce output in Forms Integrator for Partner cross 
reference lookup extended rules.


FIX DESCRIPTION:  Enabled Select extended rule in txde translator for EDI to Forms map direction.




_______________________________________________________________________________

RTC DEFECT:  429789
APAR:        IT02642
DATE:        6/17/14
MODULE:      Mapper.exe

PROBLEM DESCRIPTION:  After loading a map, Mapper crashes after trying to save the map, create a DDF, or delete any field/group structures.

FIX DESCRIPTION:  The customer map had an inactive field that was corrupt.  Activating that field or viewing the properties of that field 
(Conditions tab) causes Mapper to crash too.  Added the following popup warning in case a corrupt element is found during the open/save 
operation: "The <element name> field appears to be corrupt.  Element is NULL.  Please delete this field and recreate it."  The operation 
will still complete with the corrupt field in the map.  Manually deletion of the corrupt field is required to fix the map.


_______________________________________________________________________________

RTC DEFECT:     435867 
APAR:           IT03894
DATE:           8/25/2014
MODULE:         tx32.exe

PROBLEM DESCRIPTION:  Repeating element separator characters in data were not prefixed with Release Characters during 
outbound EDI translation.  The Repeating element separator characters would either be left un-released or trimmed from 
the output.



FIX DESCRIPTION:  Fixed release character insertion before repeating element separators found in output segments data.




_____________________________________________________________

RTC DEFECT:   444051
APAR:
DATE:         10/6/14
MODULE:       Mapper.exe

PROBLEM DESCRIPTION:  The fix for QC#1004 successfully reports a map-level compiler error when two equal signs (or other operators) are used 
with reals in an extended rule (e.g, x=y=2).  However, the .tpl file still gets generated.  This should not happen with any map error.


FIX DESCRIPTION:  Added code to return an error to the parent functions when that type of compiler error is encountered and delete the pending
.tpl file.


_____________________________________________________________

RTC DEFECT:   447972
APAR:         IT06521
DATE:         1/6/15
MODULE:       tx32.exe (txengine.lib)

PROBLEM DESCRIPTION:  Translator crashes when executing a SQL command with a blank line above it in an ODBC import map.

FIX DESCRIPTION:  The Map Editor was fine with having a blank line above the SQL command but the translator had problems parsing the SQL command
with it.  Modified translator to remove any preceding whitespace in the SQL command.


_____________________________________________________________

RTC DEFECT:   453562
APAR:         IT07123
DATE:         2/11/15
MODULE:       txde.exe

PROBLEM DESCRIPTION:  In 5.3.1 EDIMGR, when doing a formatted print of a document to a file (PDF printer), the document name no longer appears in the
filename field of the PDF printer dialog like it did in 5.3.  It's just a blank filename.

FIX DESCRIPTION:  In EDIMGR, the document title is always set before any print job is initiated.  However, when a formatted print is initiated, the 
document key is passed to Txde.exe to initiate the print job.  Txde did not set the document title.  Fixed.  Txde now does a database lookup to get 
the document name based on the document key.  If the document name is not blank, that is used as the document title and filename for the PDF print job.
Otherwise, the document key is used instead.


_____________________________________________________________

RTC DEFECT:   458576
APAR:         IT07985
DATE:         3/26/15
MODULE:       tx32.exe (txengine.lib)

PROBLEM DESCRIPTION:  After upgrading from 5.1 to 5.3.1, some ODBC maps using an AS/400 DB2 database no longer worked.

FIX DESCRIPTION:  In 5.3.1, a semi-colon was appended to the end of SQL commands generated by the ODBC Output Record Properties dialog (insert, update, 
or delete).  This delimiter was fine for most databases except for AS/400 which reported a "Token ; was not valid" error.  Removed the semi-colon from 
the SQL commands.


_____________________________________________________________

RTC DEFECT:   460950
APAR:         IT08598
DATE:         4/28/15
MODULE:       Mapper.exe

PROBLEM DESCRIPTION:  When referencing a field in an extended rule (such as "#temp = #field;"), it causes the #temp to now exist.  So even if the #field 
did not contain data, and therefore #temp does not contain data, it will still trigger links.  There was a fix done on 5.0 which did not get ported to 5.2
until patch 25, which caused this behavior to change, and the links to trigger now.  This change happened in RTC#388554 in 5.2 patch 25, 5.3 patch 7 and 
5.3.1 patch 3.  However, this customer sees it as a defect and wants it to not trigger like before.

FIX DESCRIPTION:  Added code to automatically create a new registry setting when the mapper starts up that will enable or disable the RTC#388554 fix.  
The fix is enabled by default.  Users can manually edit this registry setting and it will be rechecked each time a map compile starts.

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Sterling Commerce\GENTRAN\Common Components\Integration\8.1
reg value name: ReferencedFieldsTriggerLinks
reg type: REG_DWORD
reg value: 1 or 0 (1 by default)


_____________________________________________________________

RTC DEFECT: 470809
APAR:
DATE:       7-15-15
MODULE:     Mapper.exe

PROBLEM DESCRIPTION: Map Editor can only open a limited number of maps, and not all the same number. Seems dependent on length of name.

FIX DESCRIPTION: Increased buffer size for the file list we were using in our CDialog object for Open File



**************************************************************************
                              PATCH 6
**************************************************************************

RTC DEFECT:   471091
APAR:         IT10830
DATE:         8/21/15    
MODULE:       Mapper.exe

PROBLEM DESCRIPTION:  If an extended rule count() function is in an index (e.g., $Group1[count($Group2[*]) + 1] ), it does not increment properly when 
compiled with a 5.3.1 mapper.

FIX DESCRIPTION:  The index generated in the count() function was not cleaned up.  Cleared the index array at the end of the function.


_____________________________________________________________

RTC DEFECT:   471294
APAR:         IT11065
DATE:         9/3/15
MODULE:       tx32.exe, gntxeng.exe

PROBLEM DESCRIPTION:  ODBC SQL Update statements that included Date fields in the WHERE clause could fail on Oracle DB UPDATE commands.

FIX DESCRIPTION:  Format SQL WHERE cause Date field values with TO_DATA() function, for example "PO_DATE" = TO_DATE('2015-09-03 00:00:00','yyyy-mm-dd hh24:mi:ss');


_____________________________________________________________

RTC DEFECT:   478896
APAR:         IT11958
DATE:         10/22/15
MODULE:       tx32.exe, gntxeng.exe

PROBLEM DESCRIPTION:   5.3.1 Translator could crash in the Microsoft runtime libraries if an Exended Rule strdate() function included an Time format that included the string fragment, %:%.  For example, %H%:%M, instead of %H:%M.

FIX DESCRIPTION:  Fixed the translator to clean up the strdate() invalid format string before passing to Microsoft time formatting runtime libraries.  Additionally, the specific map format that caused the error is written to translator trace log, if enabled.  The trace file new error message for the %H%:%M format world appear as below.

Error processing DATETOSTRINGDPP Time.GetTime, with format,%H%:%M


_____________________________________________________________

RTC DEFECT:   480457
APAR:         IT12226 
DATE:         11/13/15
MODULE:       Mapper.exe

PROBLEM DESCRIPTION:  Mapper "Print to file" feature does not output extended rule lines if they are too long.  It outputs a blank line instead if the
line exceeds 200 characters.

FIX DESCRIPTION:  Fixed issue by (1) increasing the maximum characters on a line to 1000 chars and (2) removing the trailing whitespace from each line.
It used to pad each line to 200 chars.


_____________________________________________________________

RTC DEFECT:  480403
APAR:        IT12748 
DATE:        12/11/15
MODULE:      tx32.exe (txengine.lib)

PROBLEM DESCRIPTION:  After upgrading from 5.2 to 5.3.1, exporting large files into an Oracle 10.2 ODBC database crashes tx32.exe.  The ODBC map has the 
"On failure, automatically switch selected operation and retry Inserts as Updates or Updates as Inserts" checkbox enabled in the ODBC Output Record
Properties dialog.  Debug logging revealed "ORA-01000 maximum open cursors exceeded" errors.

FIX DESCRIPTION:  5.3.1 translator did not explicitly close the SQL cursor after SQL inserts failed and eventually consumed all available cursors.  Added
code to explicitly close SQL cursor and free SQL handle after SQLExecute command failures for SQL insert/update/delete operations.


_______________________________________________________________________________

RTC DEFECT:     480324
APAR:           IT12535
DATE:           12/2/15
MODULE:         tx32.exe, gentxeng.exe

PROBLEM DESCRIPTION:  Export errors from DB include the error from the ODBC driver, but not the failed SQL statement.  Prior versions of the product included the SQL Error as part of the Error message.

FIX DESCRIPTION:  Added failed SQL Statement to Translation SQL error messages.



_____________________________________________________________

RTC DEFECT:   487519
APAR:         IT13004
DATE:         1/5/16
MODULE:       tx32.exe

PROBLEM DESCRIPTION:  Rounding is not consistent when the Input format has an explicit number as opposed to an implicit.

For 5.2 (patch 25) and 5.2J (patch 27)
If the input data = 94.5555 (R6 input format) the output field will generate either
N3 = 94555 or R3 = 94.555
If the input data = 945555 (N6 input format) the output field will generate either
N3 = 94556 or R3 = 94.556

For 5.3.1
If the input data = 94.5555 (R6 input format) the output field will generate either
N3 = 94555 or R3 = 94.555
If the input data = 945555 (N6 input format) the output field will generate either
N3 = 94555 or R3 = 94.555

FIX DESCRIPTION:   This problem has to do with imprecision of doubles and float values stored with binary representations.  This fix addresses the precision 
as outlined in this case.  It does not address all possible rounding issues that might occur, as all rounding issues are undefined.  Additionally, the specific 
fix logic is only performed if the number of significant digits are less than 1e-14, to prevent the altering of significant digits provided in the data.


_____________________________________________________________

RTC DEFECT:     481955
APAR:           IT13201
DATE:           1/13/2016
MODULE:         Tranlator

PROBLEM DESCRIPTION:
Translation from ODBC Data Source dumps when SQL Query is a Stored Procedure.

FIX DESCRIPTION:
Corrected SQL format before opening CRecordSet, to encase Stored Procedure name, sp_name, in required {call sp_name} wrapper.


_____________________________________________________________

RTC DEFECT:     495479
APAR:           IT14847
DATE:           4/14/16
MODULE:         tx32.exe (txengine.lib)

PROBLEM DESCRIPTION:  A mandatory empty XML node "<node1/>" is not in the correct order as specified on the output side of an XML map.
Instead of having:
  <node1/>
  <node2 attrib2="a2" ></node2>

The output is:
  <node2 attrib2="a2" ></node2>
  <node1/>

FIX DESCRIPTION:  When translator encountered any mandatory empty nodes, they were not output immediately since they didn't contain any
data or attributes.  Fixed translator to write out any pending empty nodes in order to maintain the sequence order specified in the map.



**************************************************************************
                              PATCH 7
**************************************************************************



                There were no new Core Translator fixes in this patch.



**************************************************************************
                              PATCH 8
**************************************************************************



                There were no new Core Translator fixes in this patch.



**************************************************************************
                              PATCH 9
**************************************************************************



                There were no new Core Translator fixes in this patch.



**************************************************************************
                              PATCH 10
**************************************************************************



                There were no new Core Translator fixes in this patch.



**************************************************************************
                              PATCH 11
**************************************************************************

JIRA DEFECT:    L3REQ-21936/GT-2692
APAR:           IT37393
DATE:           6/21/21
MODULE:         tx32.exe (txengine.lib)

PROBLEM DESCRIPTION:  EDIFACT map fails when the data for the first element in a segment contains more than one release character in a row.  For example, a COM segment that 
starts with "COM+???+" for released string "?+".  Translator report shows EDI-0121 error "Too Many Elements".

FIX DESCRIPTION:  The function that counts the number of consecutive release characters before the delimiter did not include the first instance in the count.  Modified code to 
include the first instance of the release character in the count too.



**************************************************************************
                              PATCH 12
**************************************************************************



                There were no new Core Translator fixes in this patch.



_____________________________________________________________

JIRA DEFECT:     
APAR:           
DATE:           
MODULE:         

PROBLEM DESCRIPTION:

FIX DESCRIPTION:


_____________________________________________________________