What: When creating a target file for SWIFT, there's no separator <CR><LF> for each field number.1) Programmatically add CrLf subfield at the beginning of each field (DJ record) with default mapping exp ¡° ¡± in target

2) Change block 4.0 id default mapping exp from ¡°{4: ¡± to ¡°{4:"

Why:SWIFT target no longer adds separators such as CR, LF. {, } programmatically. Instead, it tends to create additional subfield to hold separator. Therefore, all separators will be added during mapping.

When: 2003-11-24

What: OccursPad Property removed for certain Binary connectors.

Why: No longer supported feature.

When: 2003-11-14

What: When creating a target file for SWIFT, there's no separator <CR><LF> for each field number.1) Programmatically add CrLf subfield at the beginning of each field (DJ record) with default mapping exp ¡°\r\n¡± in target

2) Change block 4.0 id default mapping exp from ¡°{4:\r\n¡± to ¡°{4:"

Why:SWIFT target no longer adds separators such as CR, LF. {, } programmatically. Instead, it tends to create additional subfield to hold separator. Therefore, all separators will be added during mapping.

When: 2003-11-24

What: DJ connector/validator now also supports SAP R/3 IDoc 3.x

Why:SAP R/3 IDoc 3.x. has the different structure from SAP R/3 IDoc 4.x in Control record and leading fields of data record.

When:2003-10-24

What: Redesigned the execution method used by the process engine.

Why: Decision Step causes infinite loop if steps are too close together

When: 2003-07-09

What: Fixed a problem with escaping characters in connect strings that are passed to Map Designer.

Why: Edit override with MapDesigner is stripping away the path separator.

When: 2003-07-04

What: The problem was occurring because the target is delimited ASCII. The spoke was trying to read the file to determine the fields, but doing the read asynchronously. The spoke didn't actually try to read all records, so the read was continuing when the spoke tried to re-open the connection for writing, which was causing a race condition.

Why: Process Designer is not releasing the FTP connection.

When: 2002-11-14

What: Modified the connector so that the Process Designer will automatically create separate sessions for the source and target.

Why: Process Designer: Rollback:error 24776:ORA-24776cannot start a new transaction

When: 2003-07-09

What: Fixed a problem creating sessions for some adaptors.

Why: ODBC session information not being brought into process

When: 2003-05-22

What: Addressed an issue where users were unable to use Paradox v5 in processes.

Why: Unable to run process that utilized Paradox v5 (IDAPI) adaptor.

When: 2003-07-02

What: Modified Process Designer to recognize subprocess steps that were upgraded from 7.0.

Why: When a database is upgraded from v7.0 to v7.5. the subprocesses are empty.

When: 2003-07-22

What: Modified the annotation box to not shrink to the size of the text.

Why: If text box is resized before text is entered it either changes in size when text is entered or goes flat.

When: 2003-07-11

What: Modified GetMessage to not remove the message object on eof if the object is specified by name.

Why: With djengine 7.5.5 20030313 the end of queue appears to delete the message object. This is not consistant with the documentation provided which stated that messages will stay in existence until the transformation or process ends.

When: 2003-06-26

What: Use vsnprintf/_vsnprintf to format the log message string. This ensures that even if the resulting string is longer than 2000 bytes it will not overflow the buffer/overwrite the stack, and only the first 2000 bytes will actually get written.

Why: Attempting to write strings longer than around 2000 characters to the DJWin log using the function "LogMessage" causes djengine to end abnormally.

When: 2003-07-01

What: Schema contained the "=" operator in the REF_B 01_128 element and Value property contained multiple values which requires the use of the "Like" operator. Changed L2000 REF_B 01_128 operator from "=" to "Like". Reviewed all HIPAA Addenda Schemas and discovered similar errors. Corrected all Operators. Additionally corrected some other errors.

Why: Upon connecting to source data file with HIPAA addendum schema, the following error is generated: "Parser cannot fully parse the edi file <file name>. Parsing stopped at SegRecName=[L.2000]REF_A, SegID=REF, FilePos=377 in ConnectToAPI(vbxsupp)(25502)"

When: 2003-06-12

What: Add the ability to trap a rename error when a target exists.

Why: Unable to trap a rename error when target exists.

When: 2003-04-29

What: Addressed an issue with the DJImport Object when used in conjunction with “Is Nothing.”

Why: Public DJImport object errors with "Is Nothing.”

When: 2003-05-07

What: Addressed an issue with the use of “@” in format functions.

Why: When using the format function with the @ as the place holder, DJ generated in an incorrect result.

When: 2003-03-24

What: The trailing Segment terminator will now be skipped.

Why: Client Request to have the parser skip empty trailing segments for Hl7.

When: 2003-04-29

What: Fixed using tag name as description of first field instead of using field description

Why: When using a SWIFT schema the “Description” cell for the source field names is empty even though the description is found in the SWIFT schema file.

When: 2003-03-26

What: The bug is caused by failing to consider wrapline for release indicator.

Why: Release indicator is not being implemented.

When: 2003-05-02

What:Addressed an issue with HIPAA schemas.

Why: Trying to connect to a HIPAA 820 data with 820 sechema cause an automation error

When: 2003-04-30

What: Addressed an issue with reloading HIPAA schema files.

Why: When using HIPAA adaptor for both source and target, upon reloading the conversion, the value of SchemaFile is pointing to the CodeSetFile, in other word both SchemaFile and CodeSetFile are set to the same *.dsc.xml.

When: 2003-05-22

What: Addressed an issue where the field length was not being created correctly.

Why: The length of fields in schema continue to increase. If first 3 field sizes are 5, 8 and 4, the length of each field in conversion is 5, 13, 17. So in the map you end with fields with length over 200. All records seem to do this except AA0.

When: 2003-05-19

What: Modified code to 07 from Prognosis Code within both 2000B and 2000C loops, 2300->2400->SV5->923.

Why: Professional 837 Addenda Small Cosmetic change to the document schema. Within the 2400 loop, SV5, element 923, the sequence number is the same as the

name and needs to be modified to 07.

When: 2003-05-22

What: Modified code to 11 from Multiple Price Quantity within both 2000B and 2000C loops, 2300->2400->2410->CTP->289.

Why: Professional 837 Addenda Small Cosmetic change to the document schema. Within the 2410 loop, CTP, element 289, the sequence number is the same as the name and needs to be modified to 11.

When: 2003-05-22

What: Modified the edit option dialog to allow uri's.

Why: You can not use the Edit Overrides for the message object in a conversion.

When: 2003-03-28

What: The problem is fixed for MT545.

Why: The mandatory 95a tag in the MT545 Swift schema does not have any subfields defined.

When: 2003-03-26

What: Adjust Schema tags for SWIFT

Why: The Content/Option for SWIFT schemas tags are not set properly.

When: 2003-04-03

What: Additional fixation is the algorithm to match 16R tag. Each 16R has a name, which is defined in the 1st field of 16R segment. If the schema wants to match the spefic 16R segment, it should define the value in the code value in the 1st field of 16R segment. The 16R name can be found in SWIFT standard handbook.

Why: The MT545 Swift schema hierarchy is not correct.

When: 2003-04-28

What: Set Network paths as valid

Why: Code that checked for valid paths was inadvertently reading network paths as invalid. So for Content Extractor was unable to save to network drives.

When: 2003-05-01

What: Adjusted internal flags for Accept records.

Why: Data was not showing up in the correct record when using multiple accepts in a script where different accept records come between the first accept record and the line that contains fields to be accepted to the first record.

When: 2003-05-02

What: Fixed Typo in Install for Content Extractor

Why: The "Key Information" window that is used for entering serial #/key code info for Content Extractor installation has irrelavent text on it.

When: 2003-04-22

What: Changed the code so that simply setting the property, whether it actually changes or not, sets this flag.

Why: When using the Debug Extract Design Tool to debug a line style an Invalid field index (25005) error occurs.

When: 2003-05-26

What: Addressed an issue with the upgrade of 6.5 database upgrades.

Why: Problem upgrading 6.5 database

When: 2003-06-11

What: Fixed a problem where -1 is returned when the record count is 0.

Why: A conversion step that discards all records will cause the process to return a record count of -1.

When: 2003-04-01

What: Fixed a problem importing SQL steps that don't specify a session.

Why: On loading a project (.prj file) that contains SQL steps which invoke invalid Sessions - the GUI crashes and returns to desktop.

When: 2003-04-02

What: Modified Process Designer to display an error message when an invalid log file name is used.

Why: Unable to Connect or Send Info to Map Designer err opening conv step when logfile contains "/"s

When: 2003-04-08

What: Made corrections to the CBool Function topic in version 7.5.5 Map Designer help.

Why: The cbool function's documentation is incorrect.

When: 2003-04-22

What: Documentation adjusted for “Target General Event Handlers”

Why: You shouldn't use one of the *Put actions for a record in the AfterPut event for the same record type. This causes an infinite cascade of AfterPut events which in turn overflows the process stack. It is next to impossible to prevent this without adding significant runtime cost. The situation is somewhat nonsensical and should never really happen, so it is best to document this as a possible pitfall for map designers.

When: 2003-05-01

What: Added the following to the "Source General Event Handlers" topic in the BeforeEveryRecord section: "NOTE: The BeforeEveryRecord event is fired BEFORE reading the next record. This means that the event is fired before the conversion loop hits the EOF (end of file) on the Source file. Because of this behavior, an extra (trailing) BeforeEveryRecord event will be fired."

Why: The Source General Event Handler : BeforeEveryRecord seems to be fired too many times

When: 2003-04-29

What: Changes made to the "Reject Function" topic in Remarks section.

Why: The reject action does not appear to occur until AFTER the BeforePutRecord event. Any logic entered in the AfterMap or BeforePutRecord events will be executed before the record is rejected.

When: 2003-04-29

What: XML root element info added to both 7.5.5 and 8.0 Map Designer help in the "XML Procedure" topics.

Why: Adding XML Root Element with Attributes needs to be documented.

When: 2003-03-27

What: Added information to the URI Limitations topic in v8 Map Designer.

Why: FileRead and FileWrite don't work with 'djstream' for JMS

When: 2003-05-27

What: Updated screenshots and added text for new features in the following 7.5.5 Map Designer help topics: "Specify Conversion Properties", "Reject Connection Info", and "Version Info".

Why: Map Designer help is not complete for ‘Conversion Properties’ Dialog.

When: 2003-04-23

What: Adjusted Help files for HCFA1500-NSF, UB92-NSF and SWIFT.

Why: In HCFA1500-NSF, UB92-NSF and SWIFT, the Help Text is incorrect for specific Source/Target properties.

When: 2003-06-11

What: Have the Operating system check for both Linux and linux so that either case will work for Java.

Why: Getting an invalid expression syntax error when running Java Objects on Linux with Java 1.4 installed.

When: 2003-05-22

What: Passing a null string from Java to the JNI layer caused exception when translating to a C/C++ string object.

Why: Customer receives error when attempting to run his VB app via the SDK.

When: 2003-06-10

What: AutomaticMappingMethod is designed to be a hint for mapping fields for a default conversion (i/e when no mapping is defined).

Why: MAP_METHOD.mbPOSITION maps by Name and not position

When: 2003-05-02

What: Addressed an issue with MAP_Method static variables.

Why: MAP_METHOD static variables reference same value

When: 2003-05-15

What: Addressed an issue where SWIFT schema was failing to save the repeat tag.

Why: SWIFT schema is failing to save repeat tag.

When: 2003-03-27

What: Modifying schema by adding block tag

Why: 16R/16S is start/end repeat. The adaptor should detect the presence of segment ID other than 16R/16S.

When: 2003-04-09

What: Added schema entries of type 'PASS-THROUGH' to the table list.

Why: Tables of linked type were not showing up in the table list.

When: 2003-05-02

What: Address issue with record positioning -- Doing the connect would cause the first record to be read. When the conversion actually ran it would try to reposition to the first record, but do it incorrectly causing the first record to be returned as all empty fields.

Why: Excel not reading all of the data if the source is connected

When: 2003-03-28

What: Address an issue where Deleting an element in the source caused the sibling element to be deleted.

Why: Deleting an element in the source causes the sibling element to be deleted.

When: 2003-04-29

What: Modified the connector to not quote linked server names.

Why: The ClearMapInsert is mangling the names of the fully qualified names when using data base links in SQL Server.

When: 2003-05-09

What: Changed MID function so that if the start position is less than 1 it will generate a RTE_ARG (Invalid procedure call or argument) runtime error.

Why: Change Target causes automation error in conversion -- The GPF is occurring in a call to the Mid$() RIFL function. The problem is that the start position that is passed to the function in one of the calls to Mid$() is -2048. This is causing the Mid$() function to try and access memory that is outside of the input string.

When: 2003-06-12

What: Changed how blank rows are written in the index, writing the first and last column as 0, rather than the first column being -1.

Why: A blank row is added to the target file using Event actions to seperate group types in the target file. Map Designer outputs the file successfully but when attempting to load into Excel 2000, it crashes back to desktop.

When: 2003-04-02

What: Added support for "INFO" and "DEBUG" as message types in logmessage function.

Why: The logmessage function has never supported any types other than "ERROR" and "WARN".

When: 2003-04-02

What: The user will need to set the variable "V7Compat" to 1 in the [UserInfo]section of the appropriate ini file. If it is set to 1 they will get the old codepage tables,if it is set to any other value, or not set at all they get the newer correct tables.

Why: Customer wants support for the Compuware codepage.

When: 2003-04-02

What: Addressed issue where user was unable to write to remote private queue using map desinger.

Why: Customer cannot write to a remote private queue (RPQ) using map designer. It looks as though the source code listed in the MSMQ adapter does not account for the FORMATNAME parameter, which is essential for writing to a RPQ.

When: 2003-04-23

What: Address issue with DJ Arrays and declaration.

Why: Errors in the way DJ handles arrays declared in the Conversion Properties > Global Variables handler. After an array has been named, it writes the wrong information to the DataType column. This means that when you try to re-open the array, it returns a dialog box with the error message "Invalid property value in HandleVariableButtonClick (convprops.frm) (380)".

When: 2003-04-22

What: Fixed some problems validating processes with multiple loops.

Why: Moving step icons in PD layout can crash program.

When: 2003-04-02

What: Set max field and record length both to 32767.

Why: Btrieve max record length is too short

When: 2003-05-02

What:Address issue with Format function.

Why: The Format function has problems handling date formats.

When: 2003-06-12

What: Evaluate field references in operands used in the incore lookup.

Why: Issues with iladdrow and ilremoverow

When: 2003-04-08

What: Added cp1051/Roman-8 codepage/encoding support.

Why: Enhancement Request.

When: 2003-04-09

What: Addressed an issue with variant datatype.

Why: A variable of variant datatype of more than 49 bytes long cause GPF.

When: 2003-03-24

What: Addressed some layout mismatch inconsistencies with ASCII files.

Why: Layout mismatch inconsistencies with ASCII files.

When: 2003-03-27

What: Addressed an issue with the wide-character version of FormatNumber.

Why: Excel XP spreadsheet using Excel XP spoke (and possibly other Excel spokes, negative numbers display as dashes in the Data Browser.

When: 2003-05-05

What: Relaxed some of the schema conflict resolution on the source side, since it was causing problems for document oriented data sources (XML, EDI, etc.).

Why: Map Designer does not verify source field names match source RL - no error or warnings

When: 2003-04-17

What: Addressed an issue where the Parser icon was not becoming enabled.

Why: With ASCII (Fixed) Source Type, if you remove the reference to a Source Record Layout, the Source Record Parser icon should become enabled. It instead stays disabled.

When: 2003-05-27

What: Address an issue with window focus.

Why: Selecting a window from the Window menu on either a Map Designer, Record Layout Designer, or the ConversionMap and Record Layout Manager will not bring the selected window up if it was minimized.

When: 2003-03-26

What: Address an issue with the naming of the Record Layout Designer windows.

Why: Record Layout Designer is called the same name with each invocation of a new one. This prevents the Window menu from working correctly in that only one window can be selected for focus.

When: 2003-03-26

What: Address an issue where older map designer windows were not getting updated upon creation of a new one.

Why: Older Map Designer windows are not getting updated with the existence of each new one that is created.

When: 2003-03-26

What: Address an issue where the left pane of the ConversionMap and Record Layout Manager windows did not get updated upne getting focus from windows menu selection of child window.

Why: Left pane of ConversionMap and Record Layout Manager is not updated if it gets focus from Window menu selection of a child window.

When: 2003-03-26

What: Addressed an issue where the window menu did not get updated after changing of access database.

Why: Window menu does not get updated after change of Access database.

When: 2003-04-14

What: Addressed an issue with Dragging and Droping Record layouts.

Why: When dragging and dropping record layouts, the layouts do not insert in the record layout list where you drop it.

When:2003-06-12

What: Make sure the right link source symbol is used when step symbols overlap.

Why: In the Project Designer, decision links can get hooked to the start step if the two of them are close together.

When: 2003-04-02

What: Fixed a problem creating sessions for some adaptors.

Why: ODBC session information not being brought into process

When: 2003-05-15

What: Addressed an issue that was caused by erratically removing one composite separator when generated the record in GenerateDetailRecord function of toedi.cpp class.

Why: It appeared that composite elements were not being filled correctly if the subelements used were not consecutive.

When: 2003-05-02

What: Addressed an issue in Swift targets when Block4 is not mapped.

Why: When creating a Swift target file a blank line is appended to line 1 and a brace is attached to end line.

When: 2003-05-15

What: Added F3 as the hotkey to find next occurrence of the current search.

Why: Search has no find next hot key.

When: 2003-05-09

What: Added predefined constant symbol for the Roman-8 encoding in rifl.

Why: There was no Added predefined constant symbol for the Roman-8 encoding in rifl.

When: 2003-05-09

What: Adjusted width setting on text box for resizing.

Why: Resizing log browser window will cause the horizontal scroll not to work properly.

When: 2003-05-01

What: Addressed an issue where ChangeTarget was not being handled properly.

Why: ChangeTarget resets the target connection even if the target type is Reject.

When: 2003-05-15

What: Fixed by marking the scale property as invalid in all numeric datatypes.

Why: The Scale field property has no effect on the field output.

When: 2003-05-15

What: Changed the code to save/restore the case stack across user-defined function calls.

Why: The problem is that returning from a user-defined function in the middle of the select wasn't decrementing the case stack, so it was overflowing.

When: 2003-05-15

What: Commented out the optimization for ChangeSource which cause errors with Unicode (Fixed).

Why: Mapping from "Unicode (Fixed)" to "Unicode (Delimited)" reads second and subsequent messages but outputs the contents of the first message.

When: 2003-04-22

What: This is happening because the user's data contains the character sequence ]]> which is not allowed to appear in character data in XML. Fixed by SalesForce.com

Why: Conversion does not write out records from salesforce.com source spoke

When: 2003-04-25

What: Fixed the problem where the message had an invalid format.

Why: In pre-QA djengine 7.5.5 20030313 if you read a message from an MQSeries queue, modify it and write it back, then the message written to the MQSeries queue is corrupt.

When: 2003-03-24

What: Fixed a problem handling the optional property parameter.

Why: "The documentation provided specifies that if GetMessage is called without a parameter then the message is given a default name." Yet when call GetMessage without a parameter it does not work.

When: 2003-03-24

What: Found that the code was only checking for lower case true and not supporting True or TRUE. This was the case with all of the boolean Message Connector Properties. Unfortunately, documentation says put in True or False. I made a change to ignore case.

Why: The file folder queue object property for Browse Only does not seem to be working properly. The source files are being removed from the file system even though the BrowseOnly property is set to "True".

When: 2003-03-24

What: OccursPad Property removed for certain Binary connectors.

Why: No longer supported feature.

When: 2003-11-14

What: When creating a target file for SWIFT, there's no separator <CR><LF> for each field number.1) Programmatically add CrLf subfield at the beginning of each field (DJ record) with default mapping exp ¡°\r\n¡± in target

2) Change block 4.0 id default mapping exp from ¡°{4:\r\n¡± to ¡°{4:"

What: DJ connector/validator now also supports SAP R/3 IDoc 3.x

Why:SAP R/3 IDoc 3.x. has the different structure from SAP R/3 IDoc 4.x in Control record and leading fields of data record.

When:2003-10-24

15808

What: Added a new feature code, DJLIC_MULTITIER_ODBC(616), to the license API and change the ODBC 2.x and ODBC 3.x connectors to check for this feature.Why:The current licensing for the ODBC connectors requires an Enterprise license to use multi-tier ODBC drivers.

When: 2003-10-21

What: The problem appears to be in the HIPAA connector. When the gXML schema file is parsed, some of the objects used by the connector (e.g. seglist) are corrupt.

Why: Application error when trying to run included Process.

When: 2003-10-13

What: The problem is that EDI adaptor fails to check the existence of schema file once it is defined in a djs file. The problem happens in all e-doc adaptors, so the change has been made to all e-doc adaptors.

Why: If a Conversion run through the Java SDK cannot find the Schema File specified for a HIPAA Source connection, an exception is thrown outside of the JVM.

When: 2003-10-17

What: The problem is the SharedExpressionContext is creating the DJBasicCompiler objects without specifying a module name. This means the compiler must generate it's own unique name each time one is created. These names have to be available at execute time, so they go into the program strings, which are never deleted/pruned.

Fixed by having the SharedExpressionContext generate a module name to pass to the DJBasicCompiler object(s).

Why: Calling SharedExpressionContext's execute() method repeatedly from within a java program generates a memory leak.

When: 2003-10-17

What: The connector/validator will report the separator errors.

Why: HIPAA Adaptor not parsing TA1 file correctly

When: 2003-10-14

What: Check the existance of schema file before loading the schema.

Why: Automation error when running Conversion with invalid Schema path.

When: 2003-09-09

What: Removed code related to Acucobol from Maint installer.

Why: The error "Error unregistering AcuCobol" appears when installing the DJ755 maintenance patch. If the user clicks "OK" on the error message, installation will continue without any adverse effects.

When: 2003-10-14

What: Issue with “Before Collecting” introduced with previous fix, this has been addressed.

Why: “Before collecting” not working in Extract Schema Designer.

When: 2003-09-24

What: Modified MQSeries adatptor to make sure transactions that are not committed are rolled back. Modified DJEngine to abort processes.

Why: If abort executed before a commit, msg is lost in MQS transact

When: 2003-09-26

What: The problem appears to be in the HIPAA connector. When the gXML schema file is parsed, some of the objects used by the connector (e.g. seglist) are corrupt.

Why: Application error when running Process Designer.

When: 2003-10-13

What:Added a mutex to protect finding the incore lookup object. Added a mutex to each incore lookup object, to protect all methods of the object.

Why: Using Ilookups in 2 conversions in a process. The process loops several times. Eventually an error occurs. This seems to only happen with the engine. Works in Process Designer.

When: 2003-09-26

What: Changed the code so that if the literal prefix is any character followed by a single quote, then the code will try to double-up the single quote. Otherwise, if the literal prefix is more than one character, it will not try to double up anything.

Why: The problem occurs any time the character N appears in any nchar field, no matter the length of the field. The problem is the literal prefix for these fields is N' (N followed by a single quote), and the code that tries to double-up the literal prefix was doubling up the N.

When: 2003-08-06

What: Modified project engine to remove automatic formatting of dates.

Why: Dates that are passed into the IVariables interface that are dates are transformaed in the the format dd/mm/yyyy.

When: 2003-08-13

What: Don't check for table existance if the table name is empty.

Why: DB2 multimode always logs an error: "unexpected token"

When: 2003-09-24

What: When referencing local variables, we always setting them to BYREF with (somewhat) unpredictable results. Changed code so that only actual parameters will be set to BYREF, true locals will not.

Why: Global variables are being modified by declaration of local variables in functions.

When: 2003-08-08

What:Stopped using GenericPutField to write out numeric fields, as it always pads.

Why: FillFields property in ASCII-Fixed and number datatype.

When: 2003-09-19

What: Addressed issue inporting and saving maps.

Why: When a conversion map is newly imported into Map Designer and then saved, the file name does not appear in the ConversionMap and Record Layout Manager window.

When:2003-09-08

What: After determining what might be a record separator wasn't, the file was not being seeked back to the proper place. This is now fixed.

Why: Variable Sequential (User Defined) doesn't parse all records when CR-LF is selected as record separator.

When: 2003-09-24

What: Check the setting for UpdateNullFields and obey it.

Why: When updating a salesforce.com table, nulls are put into fields where source value is null even though 'update fields' option is set to 'update only mapped fields'.

When: 2003-09-26

What: Changed connector to treat nchar/nvarchar/nlongvarchar as if they were char/varchar/longvarchar. This should allow these fields to be read/written.

Why: When connecting to a SQL Server table with an ODBC driver, receive an error. This happens when a field's datatype is nvarchar, nchar, or ntext.

When: 2003-09-24

What: Fixed a problem with transaction control that was causing the messages to be left on the queue.

Why: JMX (Fixed) Source does not pull messages off of the queue. It only browses the messages, whether the "Browse Only" option is checked or unchecked.

When: 2003-07-31

What: Fixed a problem with using IgnoreErrors on applications steps.

Why: When running a process with an Application Step with "Ignore Error" checked, the Process Designer still errors.

When: 2003-09-22

What: Fixed a problem running a subprocess more than once.

Why: If a subprocess is executed more than once in a process, will receive an error.

When:2003-09-24

What: Fixed a problem in the JMS SD adaptor when attaching to an existing JVM.

Why: If a Process has a Conversion that uses "JMS (XML)" or "JMS (Fixed)" as the Source or Target, it will run successfully the first time, but error out every subsequent time.

When: 2003-08-27

What: Redesigned the execution method used by the process engine.

Why: Process skips steps and causes infinite loop.

When: 2003-08-27

What: Address issue with Engine only installs.

Why: If only the engine is installed at the end of install an error dialog pops up.

When: 2003-09-08

What: Removed registration code for file that nolonger exist in product.

Why:DJ engine install throws the error.

When: 2003-08-29

What: The conversion Run functions in the SDKs were forcing a connection to the source before calling _Convert(). Since _Convert() already forces a connection, this is redundant behavior. Source connecting was removed from Java and COM SDK Run functions.

Why: Looping through data with the message object causes the map to read data from a previous message in certain circumstances.

When: 2003-09-16

What: Address an issue with conversion of strings to doubles which was introduced by a previous fix.

Why: A recent fix broke conversion of strings to doubles, when the string represented a negative number.

When: 2003-08-06

What: Update documentation for combo boxes or grids that have columns with drop down menus, use the keyboard shortcut <ALT>-<DownKey> to drop the list down. From there you can move up or down with the down arrows and press <Enter> to close the drop down.

Why: Outdated documentation for comboboxes and grids.

When: 2003-09-08

What: Added note to "Use Query Language" topic on size limits for text control boxes.

Why: "The textbox control says that if the multiline property is set (which it is), then the limit is "about 32K characters". Since this has to allow room for double-byte characters, this would appear to be a limit of 64K bytes in the text control"

When: 2003-09-18

What: Changed "Accessing the SQL Query Builder" topic to say that the .pdf is located in the default installation directory (instead of the installation CD).

Why: Distributor mentions that "DJ's Online help says that for the Querybuilder there is a ELSQBUGuide.pdf I cannot find this file on the CD

When: 2003-09-19

What: Add Credits section to Integration Engine online Help.

Why: Help About is not avalilable for Integration Engine so Credits must be listed in the Online Help files

When: 2003-09-26

What:Add the following note to several adaptors:

Important! To connect to DataFlex files, you will need to own the necessary API files, purchase them from a software vendor, or use ODBC. If you attempt to connect to DataFlex without installing the required API files, you will receive a 25547 error: Setting connector (DataFlex) name: Unable to find required module .dllname.

Why: User must now use ODBC as connector for several adaptors due to license expirations.

When: 2003-09-26

What: Added new topic called "Change Target Spokes and Retain Mapping".

Why: There is no information on how to change Target spokes and retain mapping, events and settings in Conversion and Map Properties in version 7.5.5 Map Designer help.

When: 2003-09-02

What: The help/about and splash screen will now get serial number, version and build date from license file.

Why: The wrong product version and build date are displayed when checking the help/about splash screen for the Document Schema Designer.

When: 2003-08-20

What: Address an issue saving extracts that use URLs.

Why: URLs are not saved properly in Content Extractor Mana

When: 2003-08-06

What: Addressed issue with accept records occuring before collection of fields.

Why: When a line style's action is "Accept Record Before Collecting This Line’s Fields" and options "Do Accept at End" and "Skip First Accept" are selected, all fields except the ones in the accept record shift down one record.

When: 2003-09-24

What: A recent fix broke conversion of strings to doubles, when the string represented a negative number.

Why: Format function not working with negative numbers.

When: 2003-08-06

What: Addressed an issue with saving URLs in Content Extractor’s Extract Manager.

Why: URLs are not saved properly in Content Extractor’s Extract Manager

When: 2003-08-06

What: Addressed issue that caused steppes in a process to be skipped after a decision step.

Why: Process designer is skipping steps after a decision step within large processes.

When: 2003-08-18

What: Changed MID function so that if the start position is less than 1 it will generate a RTE_ARG (Invalid procedure call or argument) runtime error.

Why: Use of Change Target caused automation error in conversion.

When: 2003-06-12

What: Changed code so that when trying to match by OLEDB type, identity datatypes are not even considered.

Why: SQL Source Query Statement detects identity status incorrectly

When: 2003-07-23

What: Addressed an issue where the use of ChangeTarget was resetting the target connection information.

Why: ChangeTarget resets the target connection even if the target type is Reject

When: 2003-05-30

What: Whenever we institute a new session to Oracle, alter it so the nls_territory value is AMERICAN. This way, numeric values come in with a period as the decimal separator, and that is what Oracle expects. Modify the number conversion routine in field.cpp to use our own string to double conversion, rather than wcstod. That way, even if the machine environment specifies a comma (or something else) as the decimal separator, we can still normalize the numeric string to use period and convert it successfully.

Why: Can not read from a decimal data type in Oracle on German operating system.

When: 2003-07-09

What: The function VariantToOp was not handling variant type VT_DECIMAL.

Why: Cannot return numeric data type from Oracle SP via ADO

When: 2003-07-02

What: The OpenUpdate function used to call OpenInsert, which would start an explicit transaction. At some point we changed OpenUpdate to not call OpenInsert, but didn't add code to start the transaction, thus updates would run in autocommit mode. Added code to start an explicit transaction in OpenUpdate.

Why: Commit frequency in single mode does not work in update mode

When: 2003-07-16

What: The problem is that returning from a user-defined function in the middle of the select wasn't decrementing the case stack, so it was overflowing. Changed the code to save/restore the case stack across user-defined function calls.

Why: Repeated calling of code module function causes failure of variable.

When: 2003-06-12

What: Addressed an issue with the parameters that are being passed to MoveRecordLayout method.

Why: Cannot drag and drop layouts in the desired order

When: 2003-06-12

What: The sepset flag that keeps GuessDelimiters from running after a separator/delimiter property has been set was only being set if the property was actually changed. Changed the code so that simply setting the property, whether it actually changes or not, sets this flag.

Why: Error in Debugger when a specific line style is searched for.

When: 2003-05-26

What: Added dd/mm/yy to the list of Excel formats we recognize as dates. Fixed code so that a field that has been assigned the type of date will be converted properly to a date.

Why: Custom data type not being read properly

When: 2003-07-07

13647-b

What: Added note to Excel Procdure regarding custom datatype. Did not add to Excel 2000 or XP procedure.

Why: Custom date of dd/mm/yy for Excel is not documented.

When: 2003-07-07

13485

What: Addressed an issue with Drag & Drop from leftmost column.

Why: Click-dragging on leftmost column can map incorrect field name

When: 2003-07-04

13485-b

What: Document when you should Drag & Drop from the Leftmost column.

Why: It is recommended that you drag and drop from the field number column. The only time you should drag and drop from the left most record selection column is if you are trying to drag multiple selected rows.

When: 2003-07-04

What: Changed max length for CHAR/NCHAR types to 2000.

Why: Oracle 9i's CHAR datatype only supports up to 255 bytes

When: 2003-06-17

What: Add definition of –Null_Handeling to the help files for DJEngine.

Why: -Null_Handling parameter for DJEngine not defined

When: 2003-07-07

What: Correct documentation for Option EvaluateManual Statement.

Why: Option Evaluate Manual Statement

When: 2003-06-17

What: Correct documentation for Option EvaluateAutomatic Statement.

Why: Option Evaluate Automatic Statement

When: 2003-06-06

What: Adjust Documentation for the Like Operator.

Why: % matches any string of zero or more characters _ matches any single character # matches any single digit (this is an extension to the SQL LIKE operator)

When: 2003-06-20

What: The code was already doing proper incoming conversion, but was not applying the code page setting when writing. Added appropriate calls.

Why: SQL Server 2000 Code Page property doesn't work.

When: 2003-07-11

What: Addressed an issue with right alignment of fields.

Why: In Data Junction 7.5.5 20030324Mon11 on Windows 2000 it appears that it is not possible to specify right alignment for target fields.

When: 2003-07-01

What: The time it takes to determine if an IP address exists is determined by the system. The DNS lookup of the host is failing and system routines (in the kernel) are determining this. We do not have control of how long it takes to return. The FTP Message Connector does wait 1 second between tries.

Why: Using pre-QA version 7.5.5 20030227Thu16 of djengine it appears that specifying a retrycount > 0 in the FTP message adapter with an IP address that does not exist causes djengine to hang.

When: 2003-07-07

What: Set dj750ec.dll to selfregister.

Why: dj750ec.dll wasn't getting registered by the installer

When: 2003-06-18

What: Remove the MicroFocus COBOL runtime from the installers

Why: Users should be using versions of these DLLs that are shipped with the MicroFocus COBOL compiler or with the MicroFocus operating system extensions (OSX) instead of ones we providide. Alternatively, users should consider using the MicfoFocus COBOL ODBC driver for data access to MicroFocus COBOL files.

When: 2003-07-23

What: Modified the files to be valid xml.

Why: In the install root are two XML documents: djsdjms_conf.xml djaic_specs.xml that have more than one top level element.

When: 2003-07-09

What: Addressed an issue with how the format function handles dates. Note that it does not, and should not, return a null. It returns an empty string.

Why: The Format function has problems handling date formats. If the date format is not recognized, or if the value is null, Format returns today's date rather than a null value.

When: 2003-06-12

What: Fixed by marking the scale property invalid in all numeric datatypes, so it should not display any more.

Why: The Scale field property has no effect on the field output for numeric datatypes.

When: 2003-05-15

What: Addressed an issue with the enabling and disabling of the parser.

Why: Source Record Parser stays disabled when it should re-enable

When: 2003-05-27

What: Fixed a problem with transaction control that was causing the messages to be left on the queue.

Why: JMS (Fixed) can only browse Source Messages

When: 2003-07-07

What: Removing 13095 from blocks list.

Why: Message Object source pulling data from some unknown place.

When: 2003-07-22

What: Adjusted Documentation for DJMessage URI information.

Why: DJMessage URI information has error in number of slashes used

When: 2003-05-29

What: Made changes to pass back error information when there is a problem with the Builder Working Directory.

Why: Using djengine 7.5.5 20030227Thu16 a DJFT transfer produces no error message but does not create a target file if there is a problem with the builder directory.

When: 2003-03-25

What: Made changes to properly pass back the error when there is a problem with the notification directory.

Why: With djengine 7.5.5 20030227Thu16 if the directory specified by the "notifydirectory" attribute of the Builder adapter is read-only or full, then no notification messages are produced but there is no error message indicating this.

When: 2003-06-26

What: When I removed isSameFile from CodeSetFile, the bug is fixed.isSameFile is used to compare two constant file name regardless of their directory and is not to set any string value. This function seems to have some effects on UI.

Why: SchemaFile and CodeSetFile are mixed up in the Source and Target Properties.

When: 2003-05-22

What: Fixed an access violation when reusing a message object as a conversion target with the Binary spoke.

Why: JVM crashes if Conversion's HIPAA Source is a DJMessage

When: 2003-07-09

What: The problem is caused by failing to initialize the property.

Why: When opening an existing map that uses the HIPAA source type the QFN Property is incorrectly being set to the value of the previous map open.

When: 2003-07-15

What: The bug is caused by erratically removing one composite separator when generated the record in GenerateDetailRecord function of toedi.cpp class.

Why: Composite elements are not being filled correctly

When: 2003-07-07

What: The problem is that SBK segment (10th segment) in schema is bad, this has been fixed.

Why: Error when loading Tradacoms schema and source file.

When: 2003-05-28

What: Schema contained the "=" operator in the REF_B 01_128 element and Value property contained multiple values which requires the use of the "Like" operator. Changed L2000 REF_B 01_128 operator from "=" to "Like". Reviewed all HIPAA Addenda Schemas and discovered similar errors. Corrected all Operators. Additionally corrected some other errors.

Why: Error generated on connection to new HIPAA data file/schema

When: 2003-06-12

What: If these codeset files are XML, then the option type should be set to the new option type REPFILE, otherwise set to FILE. I am going to open a new bug for you to set the SchemaFile option type to the new REPFILE for all EDI type connectors that have a SchemaFile option.

Why: Unable to browse to point to where the codesetfile resides.

When: 2003-06-20

What: Addressed an issue with parsing columnar data with headings.

Why: Parse Columnar with Heading Errors When Parsing And Viewing Data

When: 2003-06-11

What: Addressed an upgrade error with 6.5 databases.

Why: Unable to upgrading 6.5 databases due to "Invalid Use of Null (94)" error.

When: 2003-06-18

What: Got everything synced up between Preferences menu and Options screen.

Why: Many of the Preferences menu options are also available under the Source Menu - > Options Item but fail to update in both locations upon selection.

When: 2003-05-09