DPS V4.2.1 |
Supported Platforms: |
OS/390, VSE |
Supported ADABAS Versions: |
5.x, 6.x, 7.x |
Current Fix Level: |
D |
Current Zap Level: |
-- |
Batch, On-line, or Both: |
Batch |
Current Version: |
4.2.1 |
Currently, no Zaps are necessary for DPS V4.2.1.
Fixes
FIX | EXPLANATION |
A | COLAUNIQ - COLAUNIQ has been changed to save the first and last unique values assigned. These values may be displayed in the DPS end of job statistics with the application of optional zap P15144 (contact Treehouse Software for more details on this optional zap). Reference #1-5144 A S0C4 occurs in MXTRSAVE when running materialization involving A S0C4 occurs in DPSMFAB when running materialization involving A S0C4 occurs in EXTRPLOG when a backed-out transaction belongs to an expanded file component file. Reference #1-5327 Columns mapped as Strong or Group are not included in the CTL output file when no primary key is specified. Reference #1-5350 A VBM_VALUE column is not being suppress in the CTL, MAT and SQL statements. This fix sets the DPSv421 default behavior to suppress the column, if the column name is VBM_VALUE and there is no COLSUPPRESS indicator specified (this will cause DPSv421 to behave in the same manner as DPSv411. Note: this will only happen if ACTAVBM is being used. Reference #1-5358 |
B | ACTALODF - A numeric column mapped to a varchar or char column with collgth longer than the length of the data in ADABAS causes numerous extra blanks to be placed after the column values in the DDIMAGE output. This new version will stop the extra blanks from being placed in the DDIMAGE output. There will still be 1 extra blank after any column defined to ADABAS as unpacked with an even length. It is necessary to adjust to collgth values to eliminate extra blanks at the end of the column value if one extra blank is not desired. Reference #1-5158
ACTAVBM - When fields mapped to VBM_VALUE columns are null suppressed and contain nulls, ACTAVBM may incorrectly identify transactions as meeting the criteria specified in the VBMPARM file, causing DPS output to be incorrect. Reference #1-5533 COLAMAX - A S0C3 abend is encountered in COLAMAX, the message +COLAMAX ERROR: GETMAIN FAILED FOR BUFFER AREA is issued. Reference #1-4724 COLASUPR - A new column ETR that examines the field components that make up the column and if any field component is null in ADABAS the column value will be set to null. Incorrect results may occur if COLASUPR is used for propagation. THIS ETR SHOULD ONLY BE USED IN MATERIALIZATION. Reference #1-5330 DPS Propagation processing incorrectly issues a 'DPS00011--MAXIMUM ALLOWABLE DBIDS ENTERED' message when more than 50 identical DBID statements are in the DDPARM file. Reference #1-5302 DPS generates incorrect statements in the CTL file for DB2-targeted tables with columns defined with 'NOT NULL WITH DEFAULT' constraint (COLNULL=NOTNULLWD). This causes materialized records to be rejected by the DB2 loader utility. For a column that is defined as NOT NULL WITH DEFAULT in DB2, a corresponding DEFAULT IF clause should be generated by DPS in the CTL file entry for that column. A new parameter has been added to DPS that will allow DPS processing to be treated as end-of-file when a specific checkpoint is encountered. The syntax for this is the same as the CHECKPOINT parameter which is documented in the DPSv421 manual in the Extraction Parameters section, page VI-2, but the keyword is STOP CHECKPOINT instead of CHECKPOINT. Here is an example of a STOP CHECKPOINT parameter: Special mapping coded as FIELD=FILE should have been FIELD=FNR as documented in the DPS manual. Reference #1-5427 The error 'LTR00155--RDBTYPE MUST BE ORACLE WHEN CODING A LOAD PARAMETER' is incorrectly issued when executing APC and the LOAD=INSERT parameter is present. Reference #1-5435 The Windows version of DPSSPLIT has been enhanced. The old version of DPSSPLIT would open and close the files being created many times during a single execution. The revised version of DPSSPLIT has an option to keep all the files open as they are being created. It is possible that using the new option could cause DPSSPLIT to reach the windows maximums for number of files open at one time, causing an abend. Sites will need to determine if the KEEPOPEN option can be used or if the number of files being created by the split processes prevents its use. The new switch is KEEPOPEN and the format of the command is as follows: dpssplit ___________ [output_path] [KEEPOPEN] Note that if Keepopen is specified the output_path must also be specified (i.e. the parameters are positional). Entering a '.' for the output_path will keep the output in the directory DPSSPLIT is running from. Reference #1-5437 A S0C4 abend occurs in MXTRSAVE. Reference #1-5446 The column value generated for special mappings FIELD=FNR and FIELD=DBID is incorrect in a Propagation run. Reference #1-5454 The error 'DPS00041--INVALID OPTION SPECIFIED FOR FILE DEFINITION; CHECK FILE= PARAMETER' may be encountered when processing FILE statements that contain SUBFILE and/or SUBDBID parameters if no corresponding FNDEF statements are present. Reference #1-5533 When a transaction is split across PLOG datasets, it is not always written to the RESTART file. It is possible that the transaction is not processed by DPS. Reference #1-5605 A S0C1 abend may occur when a DPS materialization or propagation job includes more than 256 file statements in the DDPARM dataset. Reference #1-5651 |
C | COLACLZ - COLACLZ has been changed to correctly observe COLSCALE. In the case of a column value having less digits after removing leading zeros than the number of digits to the right of the decimal point, a change has been made to place 1 zero to the left of the decimal point and the correct number of digits to the right of the decimal point. Reference #1-6406 FLDACLZ - FLDACLZ has been changed to correctly observe COLSCALE. In the case of a field value having less digits after removing leading zeros than the number of digits to the right of the decimal point, a change has been made to place 1 zero to the left of the decimal point and the correct number of digits to the right of the decimal point. Reference #1-6406 COLAPACK - An additional action, exit leaving the column value as is, may be specified when the input column value is not a valid packed value. For information on how to activate this new choice refer to the comments near the top of the code. Reference #1-6214 * For SQLSERVER and Sybase, the sequence numbers on the CTL statements do not match the sequence of DDL statements. Reference #1-5827 * DPSGETF does not properly set response code 40 when there is no before image and response code 44 when there is no after image. Reference #1-5881 * Materialization may receive a S0C7 or loop due to DPS incorrectly identifying data storage records on an ADASAV. This only occurs when the RABN number equals the maximum RABN f or the last extent defined for the file. Reference #1-5978 * Checkpoint x'59' DEFINE NEW FIELD may be attributed to an incorrect file. Reference #1-6010 * Only the first byte of the delimiter is placed in the MAT statement when using a 2-byte COLDELIMITER or 2-byte CHARDELIMITER. NOTE: This fix will cause a column value of a blank to have a column delimiter followed by 1 blank followed by a column delimiter where previously this column would have had 2 column delimiters with no value of a blank, or a null value. Reference #1-6011 * When CHECKEXP, AUTOFDT, CHECKFDT or SHOWFDT, is specified for multiple files, DPS only applies the parameters to the last file specified. Reference #1-6049 * Checkpoint x'44' DELETE FILE may be attributed to an incorrect file. Reference #1-6051 * For DB2 only, when COLNULL=NULL, for a column defined with TYPEDEF=V, contains a null value, materialization generates a value of x'0000', which is a 2-byte length of 0 and no value. DPS processing has been modified to generate a value of x'000140', which is a 2-byte length of 1 followed by a 1-byte blank value. Reference #1-6074 * When processing an expanded file with an anchor and only one component file specified in the EXP= parameter, records from the component file are not included. Reference #1-6077 |
D |
ACTALODD - Add a close call to close the DDIMAGE file. Make ACTALODF WTOs and I/O functions operating system independent. ACTALOD2 Reference #1-6684 ACTALODF - COLSCALE not working properly in the case of a null column value. Reference #1-7027 ACTAVBM - When fields mapped to VBM_VALUE columns are nullsuppressed and contain nulls, ACTAVBM may incorrectly identify transactions as meeting the criteria specified in the VBMPARM file, causing DPS output to be incorrect. This correction is for an update with either the before image or after image containing a null value. Reference #1-6698 COLADAT8 - COLADAT8 incorrectly allowed a day value of 00. Reference #1-6613 FLDAPACK - FLDAPACK is a new field ETR that handles packed data in the middle of an ADABAS redefined field. Reference #1-6222 COLACAB - Make WTOs and I/O operating system independent. COLACLB COLACLZ COLACMB COLACNP COLACTB COLADATI COLANATT COLAPACK FLDACAB FLDACMP FLDACNP FLDACTB FLDACZD FLDAFLOT FLDAHEXV FLDAISOT FLDANATS FLDANATT FLDAPACK FLDASBIN FLDAUBIN FLDAYR4 Reference #1-6935 * There may be missing updates when an MU in a PE is denormalized and concatenated in a PE row. Reference #1-6471 * DPSGETC does not return column information on a F (first) call. A new parameter was added as the last parameter in the list for Return Order. The possible values are I, for CSQL order (DPS interal), or F, for FTTE order (I is the default). FTTE order should always be specified if DPSGETC is called from one of the ACTALODx action ETRs. Reference #1-6492 * Checkpoint x'41' AOS/DBS CHANGE FIELD LENGTH should not assume a file list, only the first file number in the checkpoint should be evaluated. Reference #1-6505 * For DB2AIX (DB2 UDB or DB2 non-mainframe) only - add NOCHARDEL after the COLDEL0X09 value in the CTL statement is there has been no value specified for CHARDELIMITER in the DDPARML file. Reference #1-6608 * For DB2AIX (DB2 UDB or DB2 non-mainframe) only - add 1 header record to the CTL file for each table in the CTL file. This will allow sites to utilize the new "include table name in name of output file" option in DPSSPLIT (Java version). Reference #1-6614 * For DB2AIX (DB2 UDB or DB2 non-mainframe) only - add a delimiter in the CTL file that contains CTLxxx ; after the last column for each table. Reference #1-6631 * Duplicate column order numbers may be generated in the CTL file. Reference #1-6659 * Rows were incorrectly generated when Primary Key(PKEY) columns contained null values. This fix prevents a row from being generated if any portion of the PKEY is null. Reference #1-6672 * If a specific MU or PE occurrence is mapped to every row of a child table, DPS incorrectly generates an update only to the row that matched the occurrence number. This fix will cause an update to be generated for every row, if a specific occurrence was modified and is mapped to that row. Reference #1-6677 * Make a close call to the ACTALODx modules to close the DDIMAGE file. Reference #1-6684 * If column suppress is set to yes, the column count was incorrectly incremented on the method statement for DB2 UDB only. Reference #1-6706 * Corrected a S0C4 abend during a materialization extract or materialization run that was processing expanded file components when there were many files included in the run. Reference #1-6776 * The column sequence number in the CTL statement was being incorrectly set if multiple FTTE statements were defining a single column. Affects SQL Server and SYSBASE only. Reference #1-6865 * An IEC143I 213-17 abend may occur when processing an input file with a large block interface and a file defined with more than 65535 tracks on 1 volume. Reference #1-7077 |