What: When a maintenance patch for this build is applied upon an 8.0.4 or previous build, two new entries are created under the Windows Start menu.  These entries are Pervasive Cosmos's Document Schema Designer and Extract Schema Designer.  The installer should simply patch the old build and no new entries into the Window Start menu should appear.

Why: With the acquisition of Data Junction by Pervasive Software Inc, all Cosmos products are being re-branded with the Pervasive company name.  Upon installation of a new build of this build of Cosmos, all products are installed under Pervasive Cosmos on the Windows Start menu.  If a maintenance patch is applied to an old build of Cosmos, all Windows Start menus should be unchanged.  This certified build simply contains this installer fix and is built from the Cosmos_8_0_5_2004011517 build.  All Cosmos products version tabs will reflect the 1/15/04 build date.

When: 2004-01-28

What: When a target is replace mode, the engine will force the target connector to use the map schema.

Why: If (1)a Transformation is in Replace Mode, (2)the Target Table already exists, and (3)a change is made to one of the Target Field's data types, then running the Transformation will NOT drop and recreate the table, the data type for the field will NOT change, and there will be no errors.

When: 2004-01-14

What: Removing of all DJ logos or acronyms in paths.  This affects the following:

Cosmos installation will now be in C:Program FilesPervasiveCosmos instead of C:Program FilesDataJunctiondjComsos

In Add Remove Programs, entry will be Pervasive Cosmos instead of djCosmos

Workspace defaults will be in C:Cosmos_work instead of C:djCosmos_work.

Application Data will now be in C:Documents and SettingsghargroveApplication DataPervasive instead of C:Documents and SettingsghargroveApplication DataDataJunction 

Why: The acquisition of Data Junction by Pervasive forced rebranding of all DJ products.

When: 2004-01-14

What: A filename was not required to save resulting in .tf.xml filenames.

Why:

When: 2003-11-24

What: The problem is with the structured schema document references a subset of DTD and the subset is not based on the root of the tree. This means that if you use qualified record names, the record layouts in the schema won't match the record layouts in the document. If you really need to use a subset, it is best to turn off the qualified record names for the XML connector and for the XML DTD metadata component. When this is done, it is possible to follow the steps describe in the bug and the browser will show the data. If you use qualified record names, you should select all of the record layouts in the DTD. This will generate record names based on the document root and the record layouts will match the ones encountered by the XML connector.

Why: The XML Data is not read in correctly - it does not appear to be reading the XML file properly.

When: 2003-09-16

What: The undo function after hitting replace was not being set correctly.

Why: Search/Replace undo feature not working.

When: 2003-09-15

What: Set Focus to the Select Connection dialog list.

Why: If the "Select Connection" dialog is opened and there have been no previous spoke selections, the hot keys will not work.

When: 2003-10-01

What: Whatever is selected in a tab that the user is currently viewing will be written to the selected connection file text box at the top of the dialog.

Why: The "Access 97" connector will be applied to the map if a user opens the Select Connection dialog/Most Recently Used tab (Access 97 is not listed in the most recently used tab), accepts the default connection (no action needed) and clicks the ok button.

When: 2003-10-01

15295

What: Add special-case code to look for the case of a title followed by a comma. In this case, re-arrange things so that everything up to the comma is put after the rest of the string (with the comma eliminated).

Why: The NamePart() function does not parse names in last,first format correctly if they have a suffix. 'last suf,first m' is recognized as 'last' being the first name, 'suf,first' being the middle name, and 'm' being the last name.

When: 2003-09-25

What: The problem is you were trying to pass a rowset variable without specifying the "self" property. I have changed the parser so that trying to pass a rowset variable will not access the default "value" property of the rowset, but rather will just reference the variable.

Why: The copy method of a DJExport object returns error "Invalid number of arguments for property" when the DJRowSet syntax. This error occurs during validation.

When: 2003-09-26

What: The problem is with the handling of variable (symbol) tables. Fixed by assigning an empty operand to all local variables when performing the user-defined function call, which forces their type to be reset.

Why: DJ thinks dimmed variable is an array.

When: 2003-09-24

What: The problem here is that as we re-use operands at the first-level function call, the dim'med type (DimType()) of the operand was not being reset. Added code to reset it, to 0 for local variables, and to the passed type for function arguments.

Why: Dimmed variables give TYPE MISMATCH error

When: 2003-09-24

What: The basic problem is that the fileappend function (in this case) is returning a value, which is never removed from the stack. After 30 iterations (or fewer, depending on the starting state of the stack), the stack will overflow from these values being left on the stack. The solution is to simply assign the return value from the function to a variable, i.e.

Why: Loop in user defined function causes stack overflow.

When: 2003-09-30

15273

What: Developer added code to check to see ifwhen the user presses CTRL-V, if CTRL-V has been pressed Data Junction will then retrieve the text from the clipboard.

Why: You can't paste data into a RIFL Editor window if the data came from another window. Also, the menu item on the Edit menu is grayed out.

When: 2003-09-25

What: Check clipboard too see, if text exist to paste and if so enable paste menu.

Why: Cannot copy and paste from one expression builder window to another using the right click (Copy) right click (paste) method. This method can be used inside the same expression builder window but not across multiple windows.

When: 2003-09-15

15355

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: Receive error when running process in engine.

When: 2003-09-26

What: Changed schema variable from local to class in order to avoid re-initializing this variable for every conversion.

Why: Memory leak when running a conversion map (HL7 Src Connector, Null Trg Connector) within a Process Map loop.

When: 2003-09-10

What: Getting an error "Workspace 1 does not exist! (-1)" when using Lookup Wizard in Expression Step

Why:Not referencing downstream files properly from Expression step.

When: 2003-11-24

What: When no more message is found, just return false instead of set EOF error and return false.

Why: Iterator errors when all "pieces" are retrieved.

When: 2003-09-16

What: Fixed an access violation when closing the queue step dialog with the sessions dialog open.

Why: Clicking on properties windows in a certain order causes process Designer to crash.

When: 2003-09-26

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. The error is 28007 - Project [test] validation failed with return code: 28007.

When: 2003-09-24

What: Added help jump for Command Button in the “Length” dialog.

Why: The link for the help command button in the "Length" dialog is missing. When help button is clicked, help file does not appear.

When: 2003-10-01

14992

What: This is by design - now that we have connectors and connections, it was decided that it would be best if we forced users to go through the building of the reject string through our dialogs instead of selecting a type then typing it in.

Why: The reject type text box in conversion props/reject connection info is grayed out and cannot be activated.

When: 2003-09-16

What: The record length is used for display purposes only inside the parser. The start of record on this form is ONLY used to help determine the record displayed in the parser length. It should NOT be confused with the binary connector property "Starting Offset". These are 2 different things and if your data has a starting offset, then you have to use the binary connector and set the starting offset property.

Why: Record lengths are not being applied or saved correctly in the parser. Record offset values are displaying incorrect data.

When: 2003-10-01

What: Section on using Target(2) to access Reject File metadata has been added to "Capturing Transformation Metadata" Topic and put in help project.

Why: Use of Target(2) to capturing reject file metadata added to the Capturing Transformation Metadata Topic.

Also .Connect and .ConnectString now replace .ConnectorName and .ConnectionInfo and a few typos cleared up.

When: 2003-09-19

What: Because there are two optional parameters at the end of the Lookup function, Direction and Default, you have to supply BOTH if you want to specify a default.

Why: Lookup Function Syntax needs adjusted.

When: 2003-09-19

What: Remove references to Application Instances for Salesforce.com Servers.

Why: References to Application Instances for Salesforce.com are no longer appropriate

When: 2003-09-18

What: Added documentation on the Repeat Search (F3) functionality.

Why: Repeat search (F3) function is not documented.

When: 2003-09-11

What: (Insert following text in topic “Workspace Tab: Workspaces Root Directory”)

"Note: To navigate to a network Workspaces Root Directory via the dropdown menu, the network drive must be mapped on your desktop or it will not appear in the Drive dropdown selection list. If the network drive is not mapped, you can still navigate to it. Just type the full path to the drive in the Workspaces Root Directory box, and click in the box below to reveal the expanded path tree. Select your destination Workspace Root Directory and click the OK button. To create a new Workspace Root Directory from this window, click the Add Workspace Location(s) button, and enter the name of the new folder."

Why: Navigating to a network Workspace needs to be documented.

When: 2003-09-18

What: Documented the following properties:

EDI (X12) FG Iterator has the following message properties:

"DJFT TransferId" --- unique ID for each transfer

"DJFT SourceName"---- source file name

"DJFT SourceSize"----- size of source file

"DJFT PieceNumber" ------piece number for this transfer

"DJFT PieceSize"-------- size of each transfer

"DJFT TotalPieces"------- total transfer piece

"DJFT Priority"-------- 0 or 1. When this is last transfer,Priority=1, otherwise Priority = 0

Why: Users should know these properties, please document them.

When: 2003-09-16

What: Add: " - Long option names may be abbreviated, but must have enough characters to be unique and must be at least 3 characters long."

Why: Long options can only be abbreviated to 3 characters long.

When: 2003-10-06

15317

What: Documented the syntax rules for Uniform Resource Identifiers (URIs).

Why: Needed to document “The '#' character in a URI indicates a fragment. We special-case handling it for raw filenames, but in any valid URI we cannot do that. The proper solution is to replace the '#' with the proper escape, which is '%23'.”

When: 2003-09-18

15305

What: Corrected documentation for Event Precedence Documentation.

Why: There is an error in the documentation for Event Precedence.

When: 2003-09-18

15351

What: Corrected typo in the Designing for the UNIX Platforms topic.

Why: Integration Engine Help Files > Designing for the UNIX Platforms > Option Files needs a re-write to correct a typo ("test editor" should be "text editor").

When: 2003-09-18

15369

What: Runtime Error Values - Spelling & Grammar Corrections.

Why:The topic Runtime Error Values contains grammar and spelling errors.

When: 2003-09-18

15395

What: Remove "Function" from certain function names in alphabetical listing.

Why: In MD Help, under Functions:All Functions, some functions have "Function" appended in the alphabetical listing.

When: 2003-09-18

15412

What: Added case-sensitive information to each function.

Why: String-search Functions are Case-Sensitive.

When: 2003-09-18

15538

What: Spelling correction to Tutor2 topic.

Why: In MD Help, under Topic "Tutorial 2", step 15 contains a spelling error: "Titor2.tf.wk4".

When: 2003-09-23

15563

What: Added links to the Integration Engine Command Line Reference topic through out the help files.

Why: In IE Help files, under topic "Integration Engine Command Line Reference" a Parameter Summary is listed. This topic should be linked elsewhere in the Help files so that it may be located easily as it provides a handy, printable alphabetic list of IE execution parameters.

When: 2003-09-23

14912

What: The "Integration Engine Command Line Reference" and "Command Line Syntax" topics in Integration 8.0 Help have been updated to include new and deprecated options.

Why: Data Junction Cosmos engine CLI syntax help topic needs updating.

When: 2003-10-06

14321

What: Added a new topic called "CVS/Source Safe Version Control Options" in Data Junction Cosmos Map Designer help.

Why: Need to add topic on CVS and Source Safe options in Repository Explorer.

When: 2003-09-16

14805

What: Removed MySQL help topics from Data Junction Cosmos.

Why: MySQL help topic exists in v8.0 Map Designer help, and MySQL is no longer available as a Connector.

When: 2003-09-18

15066

What: Added new topics to Cosmos Help files: "Component Framework" and "Why Use XML to Store Information?" Added to MapDes project.

Why: Due to improvements in v8.0, you can now change underlying Base Connector types, and the Map will still try to run with preserved Source/Target Mappings.

When: 2003-09-23

15121

What: Add Example to DOMDocument, DOMNode Object Topics

Why: There are no examples in the DOMDocument and DOMNode object topics.

When: 2003-09-18

15168

What: The existing "Accessing the SQL Query Builder" topic has been rewritten so that it just explains how to launch the Query Builder window and then links to this new book.

Why: Need to revise the SQL Query Builder Topic for Cosmos.

When: 2003-09-23

15299

What: Added more information to the Command Line Override topic.

Why: Command line Override topic is not complete.

When: 2003-09-23

15302

What: Created new topic "UNIX Connect Strings"

Why: Need to document “UNIX Connect Strings”

When: 2003-09-23

15362

What: Added -Set Parameter information to Cosmos Integration Engine help.

Why: -Set Parameter information needs to be added to Cosmos Integration Engine help.

When: 2003-09-23

15366

What: Include Sample Code for DJField Object Type Topic.

Why: There are no Samples for DJField Object type.

When: 2003-09-18

15392

What: Added topic for System Requirements.

Why: System Requirements Need Stand-Alone Topic.

When: 2003-09-16

15406

What: Revised the Repository Explorer Right-Click Menus topic.

Why: Workspace Manager and Filter All entries are missing. Refresh Grid entry is no longer available from the File Grid right-click menu.

When: 2003-09-23

15206

What: Added limitation to Excel topic of Map Designer Help.

Why: "Important! Truncation – Spreadsheets store data in such a manner that the Source Connector is unable to get exact metadata. This sometimes causes source truncation errors. If you experience a truncation error, and the log indicates that it is Source truncation, you may adjust the Source field size. To do this, navigate to the Map tab. In the Source Schema, find the Size column, and the row that represents the truncated field. Adjust the field Size and run the transformation"

When: 2003-09-18

14614

What: Add Time Mask info to Document Schema Designer Help

Why: Document Schema Designer enhanced to include fractional seconds when specifying Time Masks.

When: 2003-09-16

15281

What: Added “In the Structured Schema Designer, there are five basic ways to create the data structure for your Source or Target schema:” and "Important! To build a Structured Schema from a Target XML file, select “Source Schema” in the Datatype Filter drop-down menu. If you select “Target Schema”, no layout will be created. Structured Schema Designer does not read metadata from a Target XML file." to the help files.

Why: Unable to build XML schema s with Target selection in Structured Schema Designer.

When: 2003-09-25

What: Support customization of the User-Agent setting for Salesforce connector

Why: Some customers need use their own user agent id in order to have access to more advanced features.

When: 2003-12-02

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: If a pre-existing MicroFocus Cobol file is being written to that has a space in its path, that file will be deleted. Now error is generated when a space is found in a file path.

Why:The file should not be deleted because of a limitation to the MicroFocus Cobol connector.

When: 2003-11-24

What:HTML target spoke does not produce valid html.

Why:The DOCTYPE tag is missing from DJ produced HTML docs.

When: 2003-11-24

What: Oracle apparently does not like having empty numeric fields padded with all spaces. Change code so that numeric fields (NUMBER, FLOAT) will not be padded.

Why: Oracle9i is having a problem with Cobol datatypes

When: 2003-09-18

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

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

When: 2003-09-24

What: This problem is not specific to Oracle, it happens with any SQL spoke. It only happens when first setting the mode to update, if you save a conversion in update mode, when it reloads it will work properly.

The problem is with the implicit selection of the first field as the update key. If you were to change the mode to update, then go in and select another field as the update key, it would work properly. The way the implicit selection of the first field was working, the ActionKey property for the field would not get passed through the proxy.

Changed DJConvertControl::setAddUpdateField to call incRecordLayoutsChanged and incExternalSchemaChanges(), to force the ActionKey setting(s) to get updated through the proxy before the conversion runs.

Why: When running in Update mode or Delete mode, Map Designer produces error message "Execute in UpdateRecord: error 921 (ORA-00921: unexpected end of SQL command" along with DJCosmos error 25504 "Error writing to file or table".

When: 2003-09-26

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: Force Extract Schema Designer “Debug Extract Design...” window to repaint when opened as stand alone.

Why: Extract Schema Designer "Debug Extract Design..." window has no title bar when first brought up from Stand alone.

When: 2003-09-23

What: Disallow opening of extracts more than once within Extract Schema Designer.

Why: Opening Extract more than once in Extract Schema Designer causes multipule errors.

When: 2003-09-23

What: Addressed an issue accessing URL’s via Extract Schema Designer.

Why: If you access a URL via Extract Schema Designer and then you close that "Extract" and open a new one to another file that is larger (more lines) than the URL. You will still see the data from the URL rather than the new extract file.

When: 2003-08-21

What: Address Font issues with use of toggle button.

Why: Using the "Toggle Space abs symbol" causes the fonts to change with Extract Schema Designer.

When: 2003-08-22

What: Addressed an issue with the Debug Extract Design tool.

Why: If a user opens up Extract Schema Designer (from Rep Exp or stand-alone, it doesn't matter), loads up a source file, sets up line styles and fields, chooses Tools->Debug Extract Design, hits the >> to move all of the Line Styles to the Select List, nothing happens.

When: 2003-08-22

What: The splash window will get serial number, version and build date from license file.

Why: The wrong product version and build dates are displayed when checking the help/about splash screen for DSD 755.

When: 2003-08-20

What: he index error was an old error message left over from editing the map design. Map designer handles the index error condition, so the user does not usually see it. The engine tries to display the last error message when it terminates abnormally. It sees the old error left over from map designer and displays it. Fixed by clearing out old error messages before executing the map.

Why: When running a null to null test found that if I drag & drop the Record Number field to the Target field, run the Transformation, but prematurely abort, it aborts fine. But if I write "Record Number" in the Target Field Name and select Fields ("Record Number") in the Target field Expression and abort I receive an error.

When: 2003-08-22

What: Cosmos was trying to reference the user variable object when it didn't exit.

Why: RIFL Script Editor throws an error when it is run from the Expression Template Editor.

When: 2003-08-13

What: Anytime user selects, clicks or double clicks on a connection in the MRU list, if it doesn't exist, we tell them and give them the opportunity to remove it from the list.

Why: If the most recently used list contains one or more connections (.sc.xml or .tc.xml) that no longer exist, there is no indication of a problem when the user selects one of them.

When: 2003-08-25

What: The problem was that the OK button was set to be the default so that when you hit the enter key, it acted like you were pressing the ok button. Changed the form to not have a default button.

Why: If the enter button is used to select an action three successive errors occur.

When: 2003-08-20

What: Cosmos will no longer try to resize the form if the user is minimizing it.

Why: Minimizing the "Build New Connection String" Window causes Automation Error.

When: 2003-08-21

What: A Collection variable was not being initialized with each Record Layout so the same RecordPutConditions element was being used for all of the RecordPutConditions.

Why: The Put Condition is not being saved in the map.xml correctly.

When: 2003-08-22

What: Added function FileReadLine in the djsyntax.ini file for the expression editor.

Why: Need to include FileReadLine in the djsyntax.ini

When: 2003-08-22

What: Address an issue where array variables were being seen as functions.

Why: Array variable "arrComment" is being seen as a function.

When: 2003-08-22

What: The schema resolution was changed to ignore the schema for the connector, since the target schema is always defined by the map.

Why: If a field is added via the map tab to an existing multimode TRL layout errors will appear.

When: 2003-08-25

What: Addressed an issue with text value boxes in action’s parameters.

Why: Opening a text value box in an action's parameters causes the contents of the action dropdown list to be duplicated.

When: 2003-08-25

What: The engine was automatically refreshing the metadata when the connection was made. The connection code has been changed to disable the automatic refresh of metadata if the metadata is has been defined or changed outside of the connector. This means that when the user changes something in the schema from the UI or when maps are loaded, the changed metadata takes precedence over the metadata returned by the connector.

The engine has changed to automatically setting the 'match by name' layout mismatch option as the default for connectors that have to sniff out metadata. This makes the conflict resolution for the XML file and the DTD automatic.

Unfortunately, the UI is resetting the layout mismatch option to 'error'. This forces the user to select either the 'match by name' or 'use map' options when connecting to the XML file. We should consider changing the behavior of the UI to address this particular situation.

Why: Loading an XML file after loading an XML DTD schema, the record layout in the XML file replaces the previously loaded record layout from the DTD.

When: 2003-08-25

What: Addressed issue with saving maps & properties.

Why: If a user opens a SAVED map, opens the TF and Map Properties Dialog, changes the Execution properties, hits OK, (saves map here if he/she wishes to), Re- Opens TF and Map Props, DOES NOT GO TO EXECUTION PROPERTIES, hits OK, the Execution Properties change to an old state.

When: 2003-08-27

What: This problem was introduced just recently with the fix for bug 15325. This fix also seems to fix bug 15352.

Why: After loading a structured schema (based on a DTD), and then choosing an XML file which complies with that DTD, a "possible source schema mismatch" error window opens. Selecting "use map schema" and clicking ok produces no results and reopens the window.

When: 2003-08-28

What: Changed code so that if RetainRecordOrder=true, empty elements are skipped only if they are of RECORD data type.

Why: When running a map with an XML target and the WriteEmpty property set to "True", the resultant XML document does not contain the empty elements.

When: 2003-08-26

What: Addressed an issue validating dates with the Valuator.

Why: When running the DJ Valuator against a schema with integrated data masks/code values, the time format is validated properly. When running the DJV against a schema with a separate code set file, the time format is not validated.

When: 2003-08-19

What: The GPF was occurring when djvalidator was trying to display information about the options supported by the validator component. Some of the validators use an option type that djvalidator did not know about and this caused the failure.

Why: DJValidator's "-ol" option causes abnormal program termination.

When: 2003-08-21

What: This problem is occurring because the FTP session is timing out after the connection and before the FTP command that is failing. I have made changes to improve the error messages produced so it is more apparent what is happening.

Also, when an ftp command fails, if it is an ftp connection problem a connect is tried and the command is tried again. If the second attempt to execute the command fails an error will be returned.

Why: Unable to read files from File Transfer Protocol (FTP) site.

When: 2003-08-22

What: Developer was preventing the sorting from executing if there were no files, this has been removed.

Why: Selecting a column to sort by when no files exist gives error.

When: 2003-09-04

What: Fixed a problem that prevented the multimode spokes from being displayed in the session type list.

Why: Integration Process Designer no longer lists "ODBC 3.x Multimode" (or any other multimode adaptor) in the drop-down list for SQL Sessions. Also, Transformations with "ODBC 3.x Multimode" Targets have no Target SQL Session assigned to them when they are added as a step in a Process, and there is no way to assign a SQL Session to it.

When: 2003-08-27

What: Changed column header from Layout Origin to Schema Origin. Also changed column heading Layout Name to Record Name.

Why: The descriptive term for the structure of the source or target record layout has been replaced in v8.x by the term "structured schema" or, in some instances, just "schema". Field names and column headers which use the term "record layout", or just "layout" in reference to the structure of the source or target records, should be changed to reflect the new term "structured schema" or "schema" where appropriate for clarity.

When: 2003-08-20

What: Addressed an issue with Btrieve v7 and Structured Schema Designer.

Why: If Btrieve v7 is selected, as the "Connector Type" in Structured Schema Designer, and the Pervasive engine is not installed an error will occur.

When: 2003-08-21

What: Introduced with the code branching where we needed to get the ini being used from the engine.

Why: Unable to launch standalone GoPeep!.

When: 2003-08-22