FIX	EXPLANATION
A	Sets fix-level indicator to "A" for initial general release of tRelational 4.1.1.
B	During auto-generation of a data model, an appropriate error-message is failing to be produced when the FDT of the source ADABAS file is inaccessible (i.e., when a non-zero return code is received by LF calls for retrieval of the source ADABAS file's FDT). An empty data model is produced by the data model auto-generation function when the "generate tables for level 1 group fields" option is selected and the source ADABAS file has no level-one elementary fields. Various abends occur during file analysis if the file being analyzed is on a remote database. After an abend occurs during any File Analysis process and tRelational is immediately restarted, various ADABAS errors (such as 3018 or 3021) may be encountered. No components are shown when PF9 is pressed for view/edit superdescriptor when a userview is implemented using Predict version 4. The Repeating Field Analysis Report has an incorrect heading for the records with muliple values column. The GENDPS and GENPARML batch function may produce DDPARML output with FTTE entries in an incorrect order. FTTE entries for a child table may incorrectly precede FTTE entries for its parent table. A NAT936 error occurs on line 460 of API-PGM1. tRePC Fixes The message 'A mapping for a column can only be created for an ADABAS Implemented field from the same file as other mappings for this table' is displayed when using drag and drop functions to establish a mapping. When a column is dragged and dropped on an implemented field, the column color remains red (indicating not mapped) until it is saved and re-opened or themapping details are viewed and the OK button is pressed. The message 'LOAD METHOD option is not valid' is encountered when performing a remote open of a mainframe model, realigning the tables, and attempting a remote save. Frequent GPFs occur when executing tRePC on a Windows 2000 machine The implemented file list contains duplicate entries A GPF occurs when 'NO FILE' is selected in the file drop down box when inserting a new table. Enhanced the messages associated with invalid drag and drop actions. A table that extends below or to the right of the current screen can not be repositioned. The message 'File not valid' is incorrectly displayed when performing a remote auto-gen from tRePC. When TREBATCH functions (such as GENDPS) issue warning messages, they are not properly issuing a return code of 4. tRelational's Autogeneration function incorrectly assigns a datatype of RAW for a column derived from an ADABAS field defined as binary 1-4. This fix will assign a datatype of NUMBER and a column length of 10. This affects Oracle-targeted data models only.
C	When "start" and "end" positional values for a special descriptor component are not explicitly defined in PREDICT, display of the start and end positional values for a corresponding implemented special descriptor component on the "Component List" window (accessed via PF9 from tRelational's "Implemented Field Detail" window) are displayed as "(0-0)". This fix assures that only non-zero start and end values will be displayed. This fix provides publication of the tRelational API for implemented file and implemented field queries. During tRelational descriptor analysis, a NAT3061 error may be encountered if a superfield (i.e., a superdescriptor for which no physical inverted list exists on the ADABAS file) exists on the implemented file. On certain "Physical DDL Parms" interfaces for DB2, labels are inconsistent with DB2 terminology. An appropriate "IN tablespace" clause may be missing from DDL generated for non-mainframe versions of DB2 (DB2-UDB). On the Mapping Detail interface, entry of a field routine should be permitted even when no ADABAS field is explicitly involved in the mapping. This will allow for field routines to be used in conjunction with special mappings. In auto-generated data models, the default external transformation routine for Natural-TIME-field-derived mappings should be changed from FLDANATT to FLDAISOT. Certain table components may not be successfully copied when using the table "copy" function (accessed from the Table Summary interface). During TRELOAD processing, a NAT1301 error may occur if the input file has more than 99,999 lines. In the batch data model auto-generation function (GENMODEL), an abend was improperly occurring when the RDBMS version parameter was not submitted. Instead, when the RDBMS version parameter is not submitted the function should use the default RDBMS version as defined on the System Defaults interface. Uppercase translation is failing in "FIND" field on ADABAS Name Conversion summary interface. On the "Physical DDL Parameters" interface for DB2-mainframe-targeted models, the ability to store indexname for primary key index is required The "D"enormalization option (available on the field pick list via PF10 from the Column Summary window) is improperly bypassing ADABAS Name Conversion. Documentation of internal API (read/write) for ADABAS Name Conversion records is required. During reimplementation of a file, orphaned mappings are not being properly reset. A new function code has been added to submit a batch file implementation that uses NATURAL field synonyms from PREDICT as the basis for implemented field names. The new function code (used with the "FILEIMPL" function) is "N". In Implemented Field Summary interfaces, provide for alteration of color/intensity of an implemented field that is not involved in any mappings. During autogeneration of a data model, a NAT1301 error may occur in object TRECG if a prospective column name is invalid according to an RDBMS restriction (e.g., if the column name begins with a non-alphabetic character). In the DPS Parameters Subsystem, Extraction and Transformation Parameters screen, a maximum value of 100000 K should be valid for Extraction Workpool, Extraction Userpool, and Transformation Workpool. Inconsistency in tRelational's internal column record validation logic and mapping record validation logic causes various problems, including (1) failures in the column creation process and the column repositioning process which could result in disappearance of a column record and "orphaning" of its associated mapping record, and (2) general failures in the column repositioning process. In the data model autogeneration process (accessed online via PF10 from the Data Model Summary or Table Summary screens, or in batch via the "GENMODEL" TREBATCH function), a column/mapping derived from a NATURAL binary field or a NATURAL logical field was sometimes inappropriately being assigned the designation "consider null when empty". tRePC Fixes An extraneous NULL mapping is created when a column routine is added to the mapping. Renaming a Primary Key Column results in a GPF during remote save. Pressing the BACKSPACE key during the rename of a column causes help facility to be activated. tREPC loses mappings to constant values during remote open of a model. On the Implemented File selection list in the Table Properties interface, if multiple Implemented Files appear with the same file name (but different DBID/FNR combinations), only the first Implemented File of such a group is selectable. When a field is mapped to an MU, the selection box for Special Value has the correct entries, and is active, but does not allow the selection of M*. It also incorrectly displays NONE when remote open is performed on a data model with an MU field mapped with a special value of M*. A column with a special value mapping does not appear in the mapping summary. When displaying superdescriptor components (right-click on superdescriptor name, Properties, Components tab), the column heading for (long) Name is blank for all components.
D	When the Table Summary interface is accessed from the Implemented File Summary screen via the "T" option, some tables may fail to be properly displayed in the table summary list. In GENDDL for DB2 and Oracle models, prevent a NAT1308 error by changing the replacement of a single-quote from two single-quotes to a double-quote. In GENDDL for Oracle models: Use "owner" as high-level qualifier for INDEX name (instead of "database"). For DB2-targeted data models, the GENDPS function incorrectly generates FTTE entries of "TYPEDEF=D" for mappings involving DB2 columns of type "TIME". This results in subsequent DPS materialization jobs (which use this incorrect FTTE as input) to output incorrect CTL file entries for the column of type "TIME". The correct FTTE entry for the GENDPS function to generate in this case is "TYPEDEF=T". PREDICT version is incorrect when more than 12 SAG products are installed. Reference 1-4178 * Added support for DPS-VERSION value of '4.0.0E'. This version specification will cause FKEY entries to be produced if a column is part of a primary key. DPS will then change the update of a parent table into a delete/update pair, emulating the transformations of DPS v4.0.0. An incorrect column length is being auto-generated for columns derived from binary components of a superdescriptor. When calculating COLLGTH, if PE-LOW or MU-LOW is 0 but PE-HIGH or MU-HIGH is non-zero, assume a PE-LOW or MU-LOW value of 1. Change the default ETR for TIME-derived mappings targeted to SQL Server to FLDANATT, with a mask of "MM/DD/YYYY HH:MM:SS". Enhance sample code in API-PGM1 to include documentation and an example for reading mapping records (by making calls to TREEL). When tRe is calculating COLSCALE, at end of all other processing, when COLSCALE is 0, set COLSCALE equal to column's scale. The File Implementation process has been enhanced to allow stipulation of a Field Name Prefix (similar to functionality available in PREDICT during PREDICT's generation of a NATURAL DDM). A Field Name Prefix may be stipulated during online File Implementation through entry of a Field Name Prefix in the new "Add Field Name Prefix" field on the File Implementation parameters window. In batch, a Field Name Prefix may be stipulated in the FILEIMPL batch function through addition of a "FIELD-NAME-PREFIX=xxxxxxxxxxxxxxxx" parameter, where xxxxxxxxxxxxxxxx is the desired prefix (up to 16 characters in length) to be added to all implemented field names. A NAT1305 error may occur in TRE#IS when field information is viewed in the Field Summary window. For Oracle-targeted Data Models, improper truncation of "COMMENTS ON" clauses is occuring in two situations: (1) when the fully qualified name of a column is longer than 80 characters (2) when the length of PREDICT "abstract" text imported into table or column comments is longer than 200 characters For Oracle-targeted Data Models, version "10" should be accepted as a valid version and accepted on the System Defaults screen as a valid default RDBMS version when "ORACLE" is the default RDBMS. tRePC Fixes Mappings are not shown for a column (in the mapping windows) when the "shading" of the field indicates they are. A Data Model fails to download into tRelational PC when it contains a single parent/child pair of tables with more than one foreign key relationship between them. The message "Scale not allowed for this datatype" is displayed when performing a remote save with a data type of DATETIME after an ODBC import with Microsoft SQL Server.