Sequel Data Warehouse Server

August 2023

Version: 8.3.04

August 21, 2023

  • Corrected a validation issue, where a user was not allowed to access the Scripts function if defined to be in a User Class.

  • A build error occurred when a timestamp source element was mapped to a time data element in an extract. See Note 2.

  • A runtime error could occur in an extract where a source element was mapped to a varchar data element with a shorter length. See Note 2.

  • An extract build could end in error where an SQL expression for the Transaction Data Source referenced a special value such as [Job Date] as a run-time variable. See Note 2.

  • Use of free form SQL statements in expressions could result in incomplete data to be loaded where the extract selected data via SQL. See Note 2.

  • Fixed an issue where Data Element Omit rules may not work correctly. See Note 2.

  • Corrected a problem with a data set build, where the data set contained more than 100 data elements with long names greater than 30 characters. See Note 1.

  • Corrected an issue with build of a data set when attributes have been changed for a UTF-8 data element. See Note 1.

  • Fixed an issue where a run-time error occurred when a CDC server called a real-time extract. See Note 6.

  • New parameters have been added to the CPYRDNENV command to specify whether to copy any extract error data and archived data objects. The Apply to Data Sets parameter has been removed.

  • The CHGENVOWN command has been modified to apply the changes to objects in the export library. The Apply to Data Sets parameter has been removed.

  • The extract audit report could and in error if a real-time push was defined for the extract.

  • When checking in one or more changed data elements, the process now identifies all extracts that use affected data sets as either a data source or target, checking them out and refreshing the affected definitions. The use needs to review, build and test the extracts.

  • A new built-in function %stripnpchar has been provided to strip non-printable characters from a text string, optionally replacing them with spaces.

  • Menu 121 (Work with CL programs) has been enhanced to allow an existing program/source member to be copied to a new member.

  • Where system parameters specify to associate Export Groups with Projects, any new extracts that had never been built were not listed as being associated with the Project for an Export Group.

March 2023

Version: 8.3.03

March 16, 2023

  • Extract error report did not always list date conversion errors correctly. See Note 2.

  • Correction to Group Export for Scripts when Export Groups are linked to Projects.

  • Correction to extract program generation where multiple run-time parameters are used in SQL select predicate. See Note 2.

February 2023

Version: 08.3.02

February 20, 2023

  • Enhancements to CMDRDNENV command to allow comparison of Environments on different LPARS, and new Configuration Comparison report.
  • Enhancement to Menu 10 to print a detailed Configuration report.
  • Ensure the default Authorization List is applied to Data sets created by Reverse Engineering.
  • eGateway fix for Microsoft SQL statements that require a semicolon terminator in a Batch push script.

  • Fix to extract program generation for join type ‘Get Previous Row by Full or Partial Key’. See Note 2.

January 2023

Version 08.3.01

January 29, 2023

  • No changes for this release.

December 2022

Version 08.3.00

December 27, 2022

  • You can now define Constants globally (outside of a specific extract) to allow re-use in multiple extracts.
  • A new Scripting facility has been added to the green screen menu as menu option 122.

  • New built-in functions for use in expressions in extracts have been added:

    • %range

    • %list

    • %weekno

    • %getdtaara

    • %runcommand

    • %chgextparm

    • %encrypt

    • %decrypt

    • %mask

    • %sndusremail

  • New encryption functions are provided as simple mechanism to encrypt certain columns in detail level data sets.

  • Support for calling RESTful Web Service APIs within user-defined functions has been provided.

  • Support for Boolean columns was added by IBM in OS Release 7.5, and this new data type is now supported for Data Sources.

  • Custom reject messages where free form text is defined for the ‘Reject If’ rule statement, that text will be used for the reject message.

  • Explicit data types--numeric and character--are now allowed.

  • LCT load and Data Push processes are now submitted as a separate batch job, which starts a new JVM for each load.

  • A new parameter Stream File Override (STMFOVR) allows you to override the name and path for a stream file (text file) used as the Transaction Data Source in the extract.

  • System parameters (Legacy Date-Time Handling, and Change Management) have been added or changed.
  • When adding a new user, the user profile is now automatically added to the Environment Authorization list.

  • New advanced properties are now supported for data set indexes:

    • Page Size

    • Distinct Values

    • Preferred Disk Unit

    • Keep in Memory

  • A timestamp can now be used as the ‘Effective-to-date’ for a SCD Data Set.

  • Client UI Enhancements:

    • The Expressions property panel in extracts has been enhanced to:

      • Group built-in and user-defined functions by Type for easier searching

      • Display the text for functions, virtual elements, and source elements.

      • Allow the panel to be resized.

    • On the flowchart in extract visualization, ‘Read’ has been changed to ‘Join’ on the block indicating a join to an Associated table.

    • Data Set names in a Subject Area now show the short or long names as per the Naming button setting.

    • An Add Another checkbox is now available on the Virtual Element wizard.

    • An Add Another checkbox is now available on the New Data Element wizard.

    • The JDBC properties entry field for LCT Data Sources has been enlarged to a text area to allow all defined properties to be visible without scrolling.

    • The completion message issued on check-in of data elements has been enhanced to be more informative.

    • When manually adding an index over a DB2 data source, a completion message is now displayed to confirm the index was built successfully.

    • Only the latest 200 messages for the user profile are loaded in the Message Queue section in the information area, to prevent performance issues if thousands of messages exist for the user.

    • The Jobs function now uses a more efficient method to display active jobs in the Environment subsystem.

    • The ‘active’ Environment in the tree is now displayed in blue, to make it easier to identify the Environment you are working in when more than one Environment is displayed.

    • The currently active Environment name is displayed in the properties bar at the bottom of the client.

  • Green screen menu enhancements:
    • New Menu Item 1 Work with my spool files from today simplifies access to today’s audit and error reports.

    • New Menu Item 2 Work with my submitted jobs from this session simplifies access to today’s submitted jobs.

    • Menu Item 10 Display Environment Configuration now allows a detailed configuration report to be printed and optionally emailed. This includes all user-configurable settings and defaults for the Environment.

    • New Menu Item 16, Work with Environment Authorization List allows view and (if authorized) edit of the authorization list members.

    • Menu Item 17, previously Change Developer for a Checked-out Definition has been greatly enhanced and renamed to Work with Checked-out Definitions and now uses new command WRKRDNOBD.

    • Menu Items 41 and 42 (Start/Stop Remote Data Servers) are now redundant and have been removed, as have been the applicable commands STRRDNRSVR and ENDRDNRSVR.

    • Menu 46 Change Source Group for Data Sources and associated command CHGSRCGRP have been deprecated. This functionality is now provided by the CHGDTASRCA command (Menu 83 – Change Data Source Attributes).

    • New menu item 76 Work with Trend Tables allows you to work with trend definitions (build, clear, query, run, view audit logs) from the green screen menu. This is also available as the WRKRDNTRD command.

    • New menu item 77 Run Trending is now available.

  • Command Enhancements:

    • Special value *JOBDATE is now allowed for the run date on the RUNRDNTRD command.

    • New special values *SYDATE, *JOBDATE are now allowed on the CHGRDNEPP command.

    • The PRGRDNLOG function has been enhanced to allow eGateway logs to be purged, based on their creation date or age.

    • The CMPRDNENV Compare Environments command has been enhanced to:

      • Allow compare of Environments across different LPARs/Systems

      • Include a new Compare Configuration report, to highlight configuration differences between environments.

    • A new parameter on the STRCDCSVR command now allows a CDC server to be started under a specified user profile.

    • The job details for a CDC server job (active or inactive) can now be viewed via menu 51. (Option 9 to view the logs, then 7 to view the job details).

  • Miscellaneous Enhancements:

    • Print of a Subject Area now includes any Free Form Text defined for the Subject Area.

    • A new data area EMAIL_LOGO allows you to set the path and image file name for a logo to be included in subscription emails.

    • The MSSQL 9.4 JDBC driver is now shipped with the software.

    • The eGateway trace has been enhanced to:

      • Include the timestamp of each message in the trace

      • Only load the first 1,000 records in a trace file viewed in the client, preventing client performance issues in situations where a large load rejected all data, resulting in trace files with (e.g.) hundreds of thousands of error message records.

      • Trace files are now named based on the Data Source (or Push) name, for easier identification.

    • Performance of the Data Set rebuild process has been improved in certain situations where the data set data needs to be copied to a new table instance.

    • The Trend Table rebuild process has been enhanced to only recreate the Trend Table where necessary.

    • The column text for columns in a DB2-REMOTE data source is now retrieved and included in the metadata.

    • MQTs built over data sets are now available as DB2-LOCAL data sources.

    • Sandbox connections are now supported for Salesforce Source Groups.

November 2021

Version: 08.2.10

November 10, 2021

  • Group Import error for Views or MQTs when requested from the ‘Type’ panel.

  • Group Import error when working with Data Sources if Text data sources exist.

  • Error introducing a DDM file as a data source if it was based on a remote logical file.

  • Creation of the first UDF in an environment failed.

  • Creation of the error recovery file for an extract could fail if the Transaction table had an SQL name longer than 30 characters.

  • View/MQT Comparison report between two environments could show incorrect differences due to different generated short name.

  • Execution error in extract could occur if multiple run-time parameters were referred to more than once in the SQL select expression.

December 2020

Version: 08.2.09

December 14, 2020

  • Ensure all User-defined Functions are kept in the same order in the service program to avoid extract errors. See Note 2

  • Correction to Start Journaling command, to avoid error where Mimix has taken over the journal and changed ‘System Managed Receivers’ to No.

  • Calculate elapsed seconds in the audit log for LCT Loads and Pushes.

  • Modification to Data Set Push to Salesforce: Updates are now processed as UPSERTS. If the Salesforce ID is null in the data being pushed, the row will be inserted, else it will be updated.

  • Enhancement to eGateway logs to include timestamps, and to calculate the number of seconds spent in each step of the process. For LCT Loads, the log file name is now LOAD_DataSourceName_yyyymmddhhmm.

  • For Data Set Pushes, the log file name is now PUSH_PushName_ yyyymmddhhmm. For all other remote eGateway connections, the log file name remains unchanged.

  • Correctly determine precision of timestamp columns when creating a new data set based on an existing table.

August 2020

Version: 08.2.08

August 28, 2020

  • The EXTERROR Report could show incorrect values for rejects due to invalid dates if the date is in ISO format. The validation was correct. This was a reporting issue only. See Note 2

  • (Further) correction to creation of error recovery table where transaction data source is a data set that uses a primary index, and it is also introduced as a source table and the extract was originally created in a different environment. See Note 2

  • Ensure the SWLVL data area in the base software library is correct

  • Rebuild of an existing data set could drop and recreate indexes unnecessarily

June 2020

Version: 08.2.07

June 30, 2020

  • Correction to display of spool files in client for certain CCSIDs.

  • Correction to generation/processing of 2-Stage load extracts where items are sequenced before the transaction data source. See Note 2.


    This is a deprecated function and not available/applicable to most customers.

  • Correction to install of User-defined functions metadata for certain CCSIDs.

Version: 08.2.06

June 11, 2020

  • The path to a text file used as a data source in an extract was corrupt in certain CCSIDs due to character translation. See Note 2.

  • Ensure a data set table is correctly recreated if the definition is changed to prefer SSD or Keep in memory See Note 1.

  • Support Timestamp precision when reverse engineering tables.

  • Corrections to handling of UTF-16 columns in reverse engineering.

  • Corrections to import of data set views/MQTs.

  • Correction to User-defined functions service program import audit report.

  • Correction to the Verify Data Set Metadata report for Row Update Timestamps.

  • Apply column headings on Local Cache tables.

  • Set date/time format to *ISO in metadata for DB2-REMOTE data source definitions.

  • Correction to creation of error recovery table where transaction data source is a data set that uses a primary index, and it is also introduced as a source table. See Note 2.

October 2019

Version 08.2.05
  • Ensure all library names are updated on import of a CDC server.

  • Performance improvements for copying large data sets when a change has required the table to be recreated (i.e. where Alter Table cannot be used).

  • Corrections to import of Views/MQTs No Detail apply table name may be truncated if it is > 9 characters when using CHGCDCTBL command.

  • Add Build Type parameter to the BLDTRDTBL command (Build Trend Table) to avoid recreation of table where possible.

  • Ensure current SW level and project code is written to change log records in all cases.

  • Correction to import of extract program where Transaction Table is a remote type and the first associated table is a data set.

  • Correction to import of a DB2-REMOTE data source of the same name as an existing DB2-LOCAL table.

  • In extract programs, sequencing virtual elements prior to the transaction data source rules could result in a build failure. See Note 2.

  • Fix error with Reverse Engineering when a character column has a default value, and subsequent character columns allow null.

  • Fix error in Work with Data Elements (menu 71) where more than 9,999 data elements exist.

June 2019

Version 08.2.04
  • Remove IBM I 7.1 as a target release for compiles.

  • Incorrect generation of SQL WHERE clause in an extract, when using a Date parameter in selection. See Note 2.

  • Import of User Defined Function service program could leave a lock on the object.

  • Correction to handling of IP address for a remote system for DDM files used in an extract.

  • Import of a CDC Server failed if the Source Groups used by the server did not exist. They are now created automatically.

  • Retrieve text and column headings for a remote DB2/400 table data source.

  • New built-in functions %scanrpl and %weekno.

  • Added support for IBM i Release 7.4. Since the only Java version supported by this OS releases is Java SE 8, all JDBC connections are now forced to use Java 8 if the OS level is 7.4, regardless of the data source definition/version.

  • Ensure Data Library value is always set for a new Trend Table.

  • Ensure ‘Expressions Exist’ flag is not set off for source columns on refresh of a data source. This could result in expression rules not being applied.See Note 2.

  • Correctly determine if a Daily or Weekly Trend definition is supposed to run on a certain date, if an unusual calendar setup exists.

November 2018

Version 08.2.02
  • Parallel load jobs did not retain the library list of the parent job.
  • An extract processing a data queue did not handle rejects correctly because of missing or potential duplicate sequence numbers. A job unique sequence number is now generated and used as the key of rejected data. See Note 2.
  • Install of training environment encountered errors if an IASP install.
  • Clear Environment fails if an IASP install.
  • Subsystem startup program fails if an IASP install.
  • Leap Year function in structured rules in extracts generated incorrect code, causing extract build to fail. See Note 2.
  • An extract processing a transaction table using SQL select, with columns defined as Implicitly Hidden did not process any data or report an error. See Note 2.
  • Change Developer command (CHGRDNOBD) did not honor the Developer Access Authority setting.
  • Data Set build could fail if a new data element was added to the middle of the record layout. See Note 1.
  • Build LCT could incorrectly report failure to create table if a table already existed with a duplicate SQL name.
  • New special value *JOBDATE is now supported for running trending.

August 2018

Version 08.2.01
  • Issues with import of MQT.
  • CHGVWOWN and CHGMQTOWN command validation corrections.
  • Correction to FIXRDNSEQ processing for older extracts where the Virtual element constant flag is not initialized to N.
  • Ensure the Implied Decimal places property on a data source is correctly set.
  • Correction to determining if Alter table can be used for a data set change.
  • Ensure null capable columns set correctly when defining a Trend Table over a View. See Note 5.

July 2018

Version 08.2.00
  • Base Release

Back to Sequel Products