Sequel

November 2023

Version: R11M19

November 15, 2023

Enhancements:
  • Sequel Web Server has been enhanced to support TLS 1.2 configuration to secure all endpoints.
  • The retention period for Catalina logs generated by Sequel Web Server has been changed to 7 days.
Fixes
  • A fix has been made to correctly handle data date variables in views displayed in Sequel Web Server, when running in Repository mode.
  • Security updates have been made to the Apache and Tomcat web servers used in Sequel Web Server.
  • Bar charts in a dashboard displayed in the Sequel Web Interface now show labels above the bars, where applicable.

August 2023

Version: R11M18

August 15, 2023

Fixes
  • Using the MNTHOSTF to add an entry for either an *ISERIES or *DB2 with nothing in the driver or connection was not adding the entry into the file. This is fixed in 11.18.

  • Modify SQJJOBD to specify *NOLIST to prevent joblogs being created.

  • MCH1210 error in QRYO07 after upgrading to R11M17 when view contains a variable and PC file format is CSV.

  • Special characters such as the tilde symbol ~ now display correctly in a client report, using SQJCRO.

  • Corrected an issue where the Sequel Java Server could stop processing CRO reports after processing many thousands of requests.

  • Remote DB2 database on Windows path not set correctly.

September 2022

Version: R11M17

September 13, 2022

Enhancements
  • Log4j has been upgraded to version 2.17.2.
  • Under 7.5, BOOLEAN fields are supported.
  • An enhancement has been made to allow the use of UDF's when connecting to a remote Power server. Note, Sequel must be installed in the same library on the remote Power server.
  • When running a CRO report with SQJCRO, if no records were returned the message you would see was the Java Server Process Failed. This has been enhanced to now show the message that No Records Were Returned.
  • SQJCRO was enhanced with additional parameters SETPJLTYPE and JLDRAWER to allow selection of a printer drawer.
  • Based on Sequel Default setting for Mail Distribution, if the users 'Send if no data' is set to Y, SQJCRO will now also send the email if the CRO report returns no records
  • A timeout setting was added for SQJCRO requests and can be found in SEQUELWI/SWIVPDFT.
Fixes
  • *LOCALSYS *SEQUEL SQL conversion using *PARTOUT or *ONLYDFT did not build the translated SQL statement correctly when the join fields did not match the order of the files on the FROM clause.
  • Removes unnecessary messages from job log - CPF9801 object SEQUEL in library *LIBL type *PRDDFN not found
  • The following fixes have been made to SQJCRO:
    • Running a CRO report with SQJCRO that has a formula written using the last column in the Select clause will fail. This has been fixed.
    • SQJCRO fails if more than one email recipient is specified.
    • A fix was made when running a CRO report with SQJCRO would not display DATE type fields. They were displaying blank.
    • Emailing a CRO with SQJCRO would fail if the text or subject began with a *.
    • Client Report output using barcodes will not show the correct font when the font exists in the /QOpenSys/QIBM/ProdData/JavaVM/jdk80/64bit/jre/lib/fonts or /QOpenSys/QIBM/ProdData/JavaVM/jdk80/32bit/jre/lib/fonts folder.
    • Some printers where not handling output from SQJCRO because of spaces at the end of the spooled file. These spaces have been replaced with a null character.
    • Generic SQJ1216 error when running a CRO from the Sequel Java Server when column names are longer than 10 characters.
    • A fix was made to display more complex charts ie: stacked bar charts when CRO is processed with the SQJCRO command.

January 2022

Version: R11M16

January 6, 2022

Enhancements
  • Support for IBM Db2 Mirror for i added.
Fixes
  • A fix was made to correct the way Script Views were being analyzed during the audit process. This caused corrupted entries into the journal receivers, and the data was not available to load into the audit history files

  • SQJCRO will now resolve the library when *LIBL is specified.

August 2021

Version: R11M15

August 23, 2021

New Features
  • The SQJCRO command runs a Client Report in batch and from SWI using the Sequl Java Server on the host. This method eliminates the need to configure a VPServer to use RUNRMTCMD or VPListener to use VPTRMTCMD. Performance is also greatly improved.

  • The command CHKIFSLOCK checks for locks on sequelcc.jar which is used in connections types using JDE, ADS and *LOCALSYS/*SEQUEL. This command can be used before an install to check for object locks.

Enhancements
  • An enhancement was made to include subtotal details in a view when using DSPVIEWD or the Print Definition in Viewpoint

  • The Microsoft JDBC Driver version 9.2 is now shipped with the Software. This driver supports MSSQL version 2012 and above, and requires Java 1.8.

  • *PGMs ANZAUDDTAC and DLTAUDDTAC will now determine the product library from GETSQLIB *PGM instead of the *PRDDFN which is no longer used.

Fixes
  • WRKDCTUSR Fails when scrolling if more than 9999 user profiles exist

  • EXPR Variable input value was truncated at 50 characters but now allows 80 characters which is the maximum default value.

  • CHGVIEW on any view, pressing F23 causes error RNQ0202.

  • When saving results to Excel or opening up results in Excel, negative values with currency symbol editing had two dollar signs ($$).

  • A *LOCALSYS/*SEQUEL connection using file.field syntax will not ignore edit codes.

  • SQJENDSVR introduced in 11.14 waits indefinitely for the Sequel Java Server (SEQJVASVR) to stop.

  • In 11.14 CVTDATE was modified and no longer worked when using an remote database connection to another IBM i.

  • Using the TABLE command to create an xlsx file from a host table with data containing a special character (i.e. $) would create an excel file that would not open.

  • With an ADS connection in Repository Mode, variable default value will now work with an SQL statement like SQL(CHAR(CURRENT DATE,ISO)).

  • CVTDATE with NULL value gives SQ20205 using *LOCALSYS on 11.14

  • Null variable replacement with *LOCALSYS *SERVER did not correctly handle variable names embedded in strings like descp LIKE '%&&descp%' .

  • SEQJVASVR ends in error when SEQUEL on System Library List.

  • A second Sequel product install can cause problems related to the Sequel Java Server (SEQJVASVR)

  • SEQJVASVR ends in error following an IPL with CPD0078 Value ' ' for parameter OBJ not a valid name.

  • Running a view from the Green Screen that had DBLIST and CHECK(UC) ignored the upper case setting.

  • Script running multiple views with multiple unions over remote IBM i errors with MCH0601 on SQLQRYM.

  • Running the script from DSNSCRIPT or the RUNSCRIPT command, using a CHGVAR with VALUESQL on a *DEC variable did not pass variables correctly.

  • JDE error: Column XXXXX or expression in SELECT list not valid - JDE Decimal field in message is included in an expression in the GROUP BY clause.

  • INSERT command using a UNION in an SQL statement caused a syntax error in CVTANSI.

  • Variable with blank value gives RNQ0100 Length or start position is out of range when passing two single quotes and no space for a blank.

  • RNX0100 in RUNP with QSTRING values larger than 80 characters

June 2020

Version: R11M14

June 29, 2020

Enhancements
  • Two new User Defined Functions were added for use on Date fields. YYYYMM will create a 6,0 Decimal field and YYMM will create a 4,0 Decimal field.

  • CVTDATE and CVTTIME can be used with *LOCALSYS/*SERVER views.

  • Support added for the MariaDB driver. This will be added during install.

  • Enabled support for JD Edwards EnterpriseOne 9.2 native long password support. This requires E1 Tools 9.2.0.5 or higher.

  • Versioning of the same object was limited to 1000 times due to the file naming convention and gave an MCH1201 ‘Receiver value too small’ error. The file will now have date/time suffix therefore removing the 1000 limit.

Fixes
  • Custom JDE table is missing UDC fields and data dictionary formatting in Viewpoint or browser.

  • When a numeric JDE field that supported variable precision (via the data dictionary) was used in a GROUP BY, an SQL error occurred.

  • Using the Viewpoint Universal Driver for JDE and ADS connections to build a view will allow file list over libraries have more 999 files.

  • Scripts running commands with email requests that encountered EML0070 ‘Spool file attributes not eligible for selection’ will end abnormally so it is apparent that the email was not send.

  • A previous change from version 11.08 related to EXPR variables used in Scripts has been reverted back so that trailing blanks on a character value will be trimmed.

  • Script with EXPR type variables passing blank value does not build quotes properly.

  • From a script a REPORT command successfully produces a spooled file, but fails to email the file due to EML0070 did not cause the script to end abnormally despite an Escape 40 message. The script will now end abnormally.

  • EXECUTE PCFMT(*XLSX) with RCDFMT created excel file that is corrupt.

  • EXECUTE command can write the view results to another IBMi by specifying the appropriate TOSERVER and TOTABLE using a runtime prompted view failed.

  • EXECUTE to XLSX file using a *LOCALSYS/*SERVER view gave MCH0603 unmonitored by QRYO07 in rare instances when the offset for the column headings equaled 48.

  • QSTRING variable values without default values now truncate after first 3 positions

  • Sequel Install may fail if CPI432A was previously journaled.

  • Repeated running of the same view using *LOCALSYS *SEQUEL may result in MCH1210 ‘Receiver value too small to hold result’.

  • ADS Server Options set to only return libraries in the user's library list from View Builder, the second attempt to create a view did not show the list of files.

July 2019

Version R11M13
Enhancements
  • VPTRMTCMD—A replacement for RUNRMTCMD to run Client Reports, Client Tables from SWI and from scripts has been created. VPTRMTCMD is also supported on Windows 10.
  • CURDATE() and CURTIME() functions added to SEQUEL/SQLPARMS so they will appear in the Viewpoint Expression Editor list of functions.
Fixes
  • EXECUTE to XLSX displays Function check and MCH1210 from QRYO07 signaled to SQLEXEC for some data.
  • In the Expression Editor for a view set to Syntax *SERVER, the FLOAT function was not in the list.
  • EXECUTE over SQLServer database erroneously gives error QRY2301 Identifier 'NAME' preceding '(VARCHAR)2' is used incorrectly.
  • No records selected caused by incorrect quoting on SETVAR variable values for QSTRING variables.
  • Client Report gives error "Column $CNM04 or expression in SELECT list not valid" when using a the Viewpoint Universal Driver (ADS or JDE connection) when the GROUP BY clause had an expression.
  • Using *LOCALSYS and *SEQUEL, the SQL translation was not ordering files correctly when using a partial outer join with several files and a subquery.
  • A Localsys/*Server view with parenthesis in the column heading truncates the heading after the first ) when results saved as physical file.
  • From a Script, MONMSGs following RUNCMDs are being triggered when the command ends in error.
  • While in Viewpoint Designer, JDE driver not dynamically creating calculation when length of a field is changed by user (host fix).
  • Using EXECUTE to create xlsx output, the sheet name had a random V00000xxxx name instead of Sheet1.
  • EXECUTE to send an email in PDF no longer ignores the SETDFT setting of ‘Send if no data’ when no records are returned.
  • The VFYREPO command can cause a CPF1ED7 message if the current directory is not '/'.

November 2018

Version R11M12
Enhancements
  • A new Verify Repository command has been added to be used by an Administrator that verifies the integrity of the repository, by performing cross-checks between the repository files and a list of specified libraries. If any orphaned files or user spaces are found, reports are produced identifying the orphaned objects.
  • Java connections for remote databases now allow custom values for SystemDefault.Properties & Environment Variables.
Fixes
  • Commitment control should not be automatically started for *LOCALSYS and *LOCAL views.
  • CVTSQTOIFS will create repository objects with lower case extensions (i.e. vptview).
  • Using RUNSCRIPT with SETVAR if last variable is an EXPR the first character of the preceeding variable value is truncated
  • DSPVIEWD fails with the error MCH0601 Space offset message when the source being written exceeds 9999 lines.
  • Error MCH3402 Tried to refer to all or part of an object that no longer exists when running multiple scripts from a CL program in batch.
  • RUNSCRIPT passing an empty string on the SETVAR gives RNX0100 length or start position is out of range for the string operation.
  • UPDATE and INSERT fail for users with *STRICT authority with MCH0801 Argument associated with external or internal parameter not passed.
  • Results from a CTE were not displaying Column headings defined from the inner SELECT correctly.
  • Script passing EXPR variables fails in some instances with CPD0020 Character '0' not valid following string ''sequel/ex'. (Caused in Mod08).
  • EXECUTE fails to signal error if pre existing target IFS file is checked out (CHKOUT)
  • EXECUTE using ALIAS keyword gives error CPF327D alternative name specified more than once.
  • Running *LOCALSYS views, , if MSG(*NO) is specified, query messages should be suppressed.
  • Auditing was not showing use of EXECUTE command.
  • Host Install will now add new connection types to MNTHOSTF.
  • ADS security now supports fields with long names (greater than 10)

June 2018

Version R11M11
Enhancements
  • GETLAST and GETLASTLOC functions will now support a blank delimiter.
  • The Viewpoint Universal Driver with a JDE connection was not observing the decimal positions when the field was used on the WHERE or HAVING clause.
  • Script Designer/Warehouse Builder did not allow command strings over 5,000 positions gave MCH1210 ‘receiver value too small to hold result’ error.
  • Scripts/Warehouse Builder Definitions with commands using UNION gave Java exception error in EXPORTSQL.
Fixes
  • EXECUTE to create of XLSX output produces sets of folder in /tmp that are not removed when errors happen. The process can fail due to IFS1007 user profile space constraints, QRY7018 spreadsheet size constraint, MCH1201 Scalar data cannot be changed to type required, CPF9838 User profile storage limit exceeded, MCH3603 Pointer addresses object type not valid for this operation and probably others. The excess folders will no longer remain in the event of an error.
  • EXECUTE gives CPF2479 ‘Call stack entry not found’ when the user has *STRICT authority, the query does not contain any of the fields that the user is prohibited from using, and the SQL is invalid.
  • Running BLDJDELF multiple times in a job results in ‘CPF4205 Shared open not allowed.’ User had to start a new job in order to run the command again.
  • Directly running the CVTSQTOIFS command does not copy any extra .rpt objects into the repository for CRO reports. It also does not copy extra .json files out there for client tables.
  • CVTSQTOIFS will not attempt to migrate dashboard objects to Repository mode.
  • RUNSCRIPT from a command line with Variables defined longer than 30 are losing the first line of prompt when running a script.
  • EXECUTE to XLSX format will now use the value from the RCDFMT parameter for the sheet name in the spreadsheet.
  • CVTQRY fails with error QRY2301 on CVTANSI when the view contains fields that are SQL keywords like PLAN and TYPE and using SERER(*LOCALSYS) SYNTAX(*SERVER).
  • From Mod 8 to Mod 10, running scripts with an EXPR variable type whose length was less than the maximum length, would send informational message of CPI4314 ‘Comparison of selection operands may never be equal’. This was due to a change where we were truncating trailing blanks on an expression variable value. It has been changed to pass the value with the padded blanks.
  • Running a DYNSQL request to delete records from a file could result in CPF4278 ‘Query definition template not valid’. Then all subsequent DYNSQL requests, even SELECT statements that worked previously in the job now fail with QRY9995 java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0.
  • Email sent using BCHEXECUTE did not resolve variables in view Description.
  • XLSX file would show error -We found a problem with some content in file name.xlsx. Do you want us to try to recover as much as we can- when opening if there were special characters GT LT in the text attribute on a View result.
  • Viewpoint Script Designer gave error CPD0074 “Value 'EXECUTE SQ' for COMMAND exceeds 5000 characters” when trying to run a script/warehouse builder definition with a long command line.
  • Viewpoint Script Designer gave error "An error occurred initializing the script: Index and length must refer to a location within the string. ‘Parameter name:’ Length" trying to edit a script/warehouse builder definition with a long command string that has been saved.
  • A Host Table when user had *SEQUEL authority would give QRY2303 ‘operator follows proper SQL statement from QRYP01’ or if *STRICT would give CPF9898 ‘Data Access restriction instead of QRY9999’.
  • From DSNSCRIPT on the green screen, previously the script could only be run once using F19 if changes were made. Now the script can be run multiple times.
  • Exporting view output in Viewpoint to an Excel file when using SERVER(*LOCALSYS) SYNTAX(*SERVER) and numeric fields that have an edit word or an edits code that places non-numeric characters in the field (such as / or -), causes the export to error out.
  • Passing complex variable values fail with QRY3004 -string never ended or longer than 256 error- in a script or CL program. For instance: SEQUEL/DISPLAY VIEW(library/viewname) SETVAR((&PARM -CSTTE =IL))
  • REPORT command to PDF to the IFS, should not have added a ^ character prior to the & character when an ampersand was use in the file name.
  • BCHPRINT command does not submit for prompted views.
  • EXECUTE to produce XLSX output has skipped the shared strings processing due to performance reasons since R11M09. That meant we did not generate the /x1/sharedStrings.xml portion of the xlsx document. But the [Content_Types].xml we zipped into the xlsx document still made a reference to the missing /x1/sharedStrings.xml. This did not cause Excel to complain when opening the document, but other products such as the ClearSwift email filter can treat the xlsx as defective.
  • The WEEK function over a JDE date field mistakenly started the week on Monday rather than Sunday.
  • Runtime SQL conversion using SERVER(*LOCALSYS) SYNTAX(*SEQUEL) cause error RNX0301 ‘Java exception received when calling java method’ using a sub-query.
  • Presence of an ALIAS name in a view causes the field names to be displayed rather than column headings.
  • Using *LOCALYS/*SEQUEL the converted SQL may have been written to change the ordering of list of join field to try to map with the order of the files in the FROM clause. The should allow a more accurate rebuilding of the FROM/JOIN clause.

February 2018

Version R11M10
Enhancements
  • Connections to Oracle 12 databases are now supported.
Fixes
  • The method to retrieve a list of files by the View Builder in Viewpoint was improved to increase performance.
  • Presence of an ALIAS name in a view causes the field names to be displayed rather than column headings for derived fields.
  • REPORT command using back slashes (\) in the IFS path was not creating the PC file for TXT, RTF or HTML.
  • Running a script from SWI with a variable Default value *USER required *NOPROMPT in uppercase in order for user id to substitute.
  • RUNSCRIPT could fail when non-EXPR type variables were followed by EXPR type variables on the SETVAR.
  • RUNSCRIPT fails when some, but not all variable values are passed and fails to use the default value on the others.
  • In host mode, editing an existing object and then saving it to repository will save the user space object in the library of the original object. Previously it saved to the repository library.
  • Repository Mode:
    • Datasources names now support mixed-case.
    • A Script View run from Viewpoint failed to release file locks when script view results window is closed.
    • In Viewpoint repository mode, when a JDE server is prompted for Environment and Role, the server is disconnected to ensure the new credentials are used. If a user designed a view using a JDE datasource and immediately designed any other JDE view which used the same server as the original view a ‘file not found’ error was sent.
    • With versioning off, the SAVE AS option, even though you specify the same object name, you will get multiple versioned objects of the *USRSPC object.

December 2017

Version R11M09
Enhancements
  • In views using the Viewpoint Universal Driver for JDE and ADS connections when edit code or edit word is not explicitly stated on the SELECT clause will assign codes using the following rules:
    • Numeric fields with no decimal places will be given edit code M, which is no comma separator, no decimal places and a minus sign for negative numbers.
    • Numeric fields with decimal places will be given edit code J, which is comma separated, decimal places and a minus sign for negative numbers.
  • The installation will create the SEQUELEX objects in the Repository.
Fixes
  • DSPSCRIPTD will now include Script View attributes in the command.
  • EXECUTE with RECIPIENT in PDF format truncated subject line at 50 characters.
  • From View Designer or View Builder, iASP libraries and files are not listed in Add Database dialog with an Advanced Database Security connection using the Viewpoint Universal Driver.
  • Creating XLSX output ends with a Scalar error after a certain amount of data is produced.
  • A JDE connection using the Viewpoint Universal Driver with a concatenation expression like, concat(trim(field1),concat(',',field2)) yielded results like so: àÁ>ÎÁÊä.
  • CVTTIME and TIMESTAMP expressions only recognized as General format when saved to XLS.
  • Connections made with the Viewpoint Universal Driver with JDE or ADS connections, would have column headings that ran together and on a single line.
  • Connections using the Viewpoint Universal Driver for JDE or ADS connections will now allow expression in mixed case, not merely all upper case.
  • MNTHOSTF copies both Driver and Connection strings from corresponding type template.
  • The Viewpoint Universal Driver used for JDE and ADS connection with an expression using the CAST function gave error ‘QRY9995 Token - was not valid. Valid tokens.’
  • Changes were made to enable ViewPoint to offer better support of Advanced Database Security when libraries and files reside on an independent auxiliary storage pool (iAsp).

October 2017

Version R11M08
Enhancements
  • All XLSX files will be created as UTF-8. UTF-8 supports conversions from both single-byte and double-byte character sets. It also creates XLSX files that can be read on Apple devices. However, the Apple device must have Excel installed. Many iphones may not have Excel by default but information is available here:
  • http://forums.imore.com/iphone-6s/347823-when-i-receive-emails-my-iphone-excel-file-attached
  • XLXS output created from the EXECUTE command has been enhanced to support use in a view as an Excel datasource.
  • View description will be carried through to the File Properties Title when saving results as an XLSX file
  • Encrypt the password for the remote databases within the MNTHOSTF entry.
  • Scripts viewed from Viewpoint will now log script commands in the joblog.
  • Request run from Automate Schedule that produce no records (which can be reasonable at times) were erroneously emailing the versioned copy of the results.
Fixes
  • When using a remote connection to an IBM i, Viewpoint did not use the SYSTEM_COLUMN_NAME which could cause fields to appear as RENAMED00x instead of the actual field name.
  • Connection to a remote iSeries which is configured with system value QPWDLVL 0 (i.e. 10 characters) fails with MCH3401 ‘Cannot resolve to object GETSQLIB’ and RNQ020 ‘The call to JNIAAllocEn ended in error’.
  • When using the Viewpoint Universal Driver (i.e. JDE and ADS connections) it did not return the 10-character field name when there was an ALIAS and RENAMED00x would be used.
  • DBCS data printed from view with overflow to SQLPRTx files causes random strike through.
  • Error ‘User does not match with the protocol specified in URL’ when connecting to a JD Edwards EnterpriseOne datasources due to conflicts with java versions.
  • .VPT Shortcuts are unnecessarily created in repository folder when saving Sequel objects from Viewpoint this causes issues for users without proper authority.
  • Scripts and Script Views not passing correct quoted values in SETVAR when run from Viewpoint Explorer.
  • A script with a REPORT command to run a CRO report from Viewpoint gave error ‘Stream file error – no such path or directory’. Problem was introduced in Mod 7.
  • View uses the default value for a variable rather than the value passed in SETVAR in unique circumstances (view had a variable with a *ALL default value, an integrity test of a DBList or values list, and the presence of a *NOPROMPT variable).
  • Viewpoint objects could be created an iAsp and if existing iAsp objects were designed and saved, the view is corrupted and unusable and caused error CPFA0A9 ‘Object not found. Object is QSYS.LIB/yourlib.LIB’. Introduced in Mod 7.
  • EXECUTE to an outfile with KEYFLDCNT(*ALL) using a Viewpoint Universal Driver connection (i.e. JDE or *ADS) when the ORDER BY uses numbers, not names caused error CPF3206 ‘Key field xxxx not found in VIEWFMT’.
  • SERVER(*LOCALSYS) SYNTAX(*SEQUEL) views not displaying column headings correctly. Alt names were used instead of column headings, and *BLANK did not blank out the column heading.

April 2017

Version R11M07
Enhancements
  • Repository mode now offers an authentication model that allows for:
    • Users don’t require an IBM i profile
    • JDE prompting for Environment and Role
    • An interface that is based on the folder structure of the Repository
    • Use of long object names in both Viewpoint and SWI from the Repository
  • PostgreSQL database support added.
  • The TOSTMF path on the EXECUTE command size limit was increased from 128 characters to 2,000 characters.

Fixes
  • Runtime SQL conversion for SERVER(*LOCALSYS) SYNTAX(*SEQUEL) displays the error QRY2232 ‘Cannot translate SQL from *SEQUEL syntax to standard SQL’ when field was named MOD.
  • After installing R11M05, processes writing to the QNTC folder no longer created a file.
  • When user defaults are set to Versioning and the view (*USRSPC) had an Authorization List to secure the object, re-saving the view would remove the Authorization List.
  • The Viewpoint Universal drivers for an ADS or JDE connection was initially designed with an internal limit for the longest string that can be passed of 9999 characters. The limit was increase to 20,000.
  • OPNSQLF on a DDM file at V7R2 failed with the error ‘Value specified in UFCB (User File Control Block) is not valid at offset 151’.
  • Some views return a "SQL0305 Indicator Variable Required" error when no records are returned using *LOCALSYS connection.
  • Versioned output was not produced if the target folder did not exist. Now the folder will automatically be created.
  • Using EXECUTE to email PDF results when no records are selected, and user defaults are set to ‘Send if No Data No’ results in error EML0070 ‘Spool file attributes not eligible for selection’.
  • When emailing view or host table output that exceeds 132 width and no records were selected, and the user defaults were set to send the email, the email was not sent because the second, not the first spooled file was searched for.

January 2017

Version R11M06

Created for internal use only.

October 2016

Version R11M05
Enhancements
  • Added EDTWRD and EDTCDE handling when using SERVER(*LOCALSYS) or SERVER(*LOCAL). f the underlying column/table/schema for a given result column can be determined, the edit word/edit code, if one exists for a numeric field, will be displayed as follows (in order of precedence): 1)The value provided by EDTCDE() or /*<S-EDTCDE()-S>*/ in the SQL, 2)The value provided by EDTWRD() or /*<S-EDTWRD()-S>*/ in the SQL, 3)The edit code or edit word associated with the field in the DDS, 4)The edit code J.
  • Within the user defaults (SETDFT), a prompt was added for selection of Default Data Base (SERVER).
  • SETAUDDFT command will not error when there are more 9,999 user data areas.
  • EXECUTE command now retains field text when creating output files when using SERVER(*LOCAL) or SERVER(*LOCALSYS).
Fixes
  • Using DSPVIEWD to generate CL source generates MCH0603 ‘an array index is out of range’ in program DSPVIEWD1 in rare instances when the formatted SQL string uses spaces at the end of the line feed.
  • Referencing a UDF without the qualified library that is not in the SEQUEL or SCSERVER10 library, generates an error that the item was not found in *LIBL, even though the UDF library is part of the Viewpoint or Green Screen job. Introduced in Mod 4.
  • Character fields defined with CCSID 65535 are unreadable when using Viewpoint Universal Driver for Advanced Database Security or JDE connections.
  • Using EXECUTE command, when no records are selected, still sends and email when SETDFT E-Mail Distribution flag is set to N. Mail should only be sent if ‘Send if no Data’ is set to Y.
  • All commands changed to Allow Limited Users *NO.
  • EXECUTE command creates output fields without field text when using SERVER(*LOCALSYS) or SERVER(*LOCAL).
  • Convert/Import Query (CVTQRY) command errors when the % sign is used in LIKE comparisons.
  • A host report over a *LOCALSYS view with runtime prompting ( SQLVIEWMP ) does not create a proper report definition (PRTRPTD).
  • Error RNX0100 ‘Length or start position is out of range for the string operation in SWPGETOBJD’ displays when saving a Client Table if the view has exactly 60 fields on the SELECT clause.
  • EXECUTE to an outfile sporadically displays message ‘MCH1210 in *PGM QRYO03 at instruction x'00EE'’ with views that are SERVER(*LOCALSYS) SYNTAX(*SEQUEL).
  • Running a Script View where the SCRETURN command has a TEXT parameter shows the script object text at runtime, not the text specified on the parameter.
  • Using the CHGVAR command in a script with a SERVER parameter to a remote database, fails to return a value.
  • ANZAUDDTA command fails with duplicate timestamps CPF5149 ‘Operation for program device or member CPIALL is not valid’.

April 2016

Version R11M04
Enhancements
  • When using SYNTAX(*SERVER), the Edit Code (EDTCDE) and Column Heading (COLHDG) values will now be supported.
  • A new value for the user defaults for the Security setting of *ADS has been created. This setting makes it easier to enforce the Advanced Database Security settings.
Fixes
  • Issue corrected when DSPVIEWD is used to create a source file, where derived fields with a certain length expression caused the line to break inappropriately, depending on the length of the keyword that follows the expression.
  • DSPVIEWD now supports the REMARKS parameter of a view, and wild card names like CUST* when used to create a source file.
  • For the JOBQ parameter of the BCHEXECUTE, BCHPRINT, BCHREPORT, RUNSCRIPT, RUNSCRIPTV and RUNSCRVPT commands, *JOB was removed as it was not a valid value.
  • The SEQUEL object ZLIB was renamed to SEQZLIB to avoid potential conflicts with objects of the same name.
  • Issue fixed where loading the Query Audit data (ANZAUDDTA) errored with ‘CPF5009 and CPF5026 duplicate key in QRYSUM when the timestamp of the requests is identical’.
  • The runtime SQL conversion for SERVER(*LOCALSYS) and SYNTAX(*SEQUEL) now supports CHAR(date, format) function with the formats JUL, JL1, MDY, YMD and DMY.
  • Issue corrected where scripts were incorrectly parsing out a RUNCMD command if prompted views are used in both the CMD and VIEW parameters of the command.
  • VALID_DATE function loops causing job to hang in rare instances.
  • Using the JDE driver, the descriptions of date fields were not displayed correctly.
  • Security setting *STRICT always gave error when view was SERVER(*LOCALSYS) and SYNTAX(*SERVER).

November 2016

Version R11M03

The following updates are included in this version:

  • DSPVIEWD now supports syntax of *LOCALSYS/*SERVER and will exclude host table objects (*SQLTBLV).
  • Within the user defaults (SETDFT) the expected behavior of the new Query Time Out setting is that if there is a value there (*NOMAX for example), that setting will be used, but if its left blank, the Query Time out Setting in the QAQQINI file will be used.
  • EDIT Function may result in the decimal being moved 1 position to the right for some fields.
  • Script Views that contain variables, do not retain the Description Text when they are saved. It keeps the default value of SEQUEL Script.
  • RUNSCRIPT was not handling SETVAR for EXPR variable with one value using all single quotes.
  • DSPSCRIPTD TYPE(*SRCCL) fails with ‘RNX0100 Length or Start position out of range’.

The following enhancements are included in this version:

  • Excel and Access can now be referenced as a view data source.
  • Update Microsoft JDBC driver to 1.2 with hot fix for greater compatibility.

May 2015

Version R11M02

The following updates are included in this version:

  • Runtime SQL conversion (SERVER(*LOCALSYS) and SYNTAX(*SEQUEL) cause error with the CEILING function.
  • A view with SERVER(*LOCALSYS) and Alt-named fields where the name contains the # character, produces quotes around the name which causes a syntax error.
  • When running command SCHSCRIPT to search for a given text string, a spooled file report is generated called SCRFNDRPL. Overprinting was changed to make the column headings visible.
  • REPORT and REPORTVPT commands allow *XLS for the PCFMT parameter when running Client Reports.
  • JDE driver connection caused error running view when a Julian date field is used in a CASE statement in SELECT clause with DATE function wrapped around it and same column added in GROUP BY. The JDE driver by default adds the DATE wrapper (if already not added) around such columns (JDE Julian date format column), hence the converted date field in GROUP BY clause was getting customized with Date() causing an error.

The following updates are included in this version:

  • CVTQRY ( import query ) fails on a qry/400 query that has file and library names containing a period and gives error QRY3004 ‘String beginning 'T02 ON' is never ended or is longer than 256’.
  • CVTQRY (import query) fails on a qry/400 query that has file named ORDER and gives error QR2303.
  • *LOCALSYS views with an Edit Word for a trailing % causes JSON error in SEQUEL Web Interface.
  • Runtime SQL Conversion updates when using SERVER(*LOCALSYS) SYNTAX(*SEQUEL) in these conditions:
    • Unqualified field reference in join clause causes syntax conversion errors and invalid query results.
    • Partial Outer Join with some fields from the secondary file in the grouping clause produces a null value which caused erroneous where conditions preventing a valid drill down request.
    • A partial outer join with many files could qualify the field on the join clause with the wrong file when the view specifies joins that are not in the order that the files are listed.
    • Fields in views with three files ignored the column headings of the field.
    • CASE with CVTDATE and GROUP BY clause.
    • When one file joined to many files (F1 to F2 and F3 and F4) may give error SQL5001 Column qualifier or table xx undefined.
  • Runtime SQL conversion error using SEQUEL syntax and Oracle Server with the field names had special characters gives error ‘SQLSTATE 42000 Native Error Code 923’.
  • The REPORT command to create a stream file, when the user did not have an Esend default created, issues the error CPF4102 ‘File ESNDPF in library *LIBL with member X not found’.
  • DSPVIEWD to a CL source file when view has integrity tests using quotes can cause errors like CPD0014 ‘A matching apostrophe not found’.
  • DSPVIEWD on a view which has an expression greater than 2000 characters gives MCH0603‘Range of subscript value or character string error’.
  • Script view using a SCRETURN on an *LOCALSYS SQL statement causes 'Cannot translate Sequel syntax to local SQL' error.
  • Using DO or GOTO in a script MONMSG command gives CPD0031 ‘Command DO not allowed in this setting’.
  • CRTSCRIPT over CL Source member loops with CPF5812 ‘Member SCRCMDPF already exists in file SCRCMDPF in library QTEMP’.
  • DYNSQL was not working .
  • From the Green Screen script designer using DSNSCRIPT, F10 to toggle the script to a script view causes an MCH1210 ‘Receiver value too small to hold result’ error.
  • Script view with a variable length longer than 80 positions for the first variable will ignores other variables when run from the Viewpoint Explorer or SWI Explorer.
  • Script view with prompts could not create a PDF or RTF stream file from the EXECUTE command.

January 2015

Version R11M01

The following enhancements are included inthis version:

  • Create UDF for SQL to retrieve overridden dates and times named GETDATTIM. This function is useful with AnyDate.
  • The LOADJOINDB process utilized by the Viewpoint auto-join feature now supports *LOCALSYS and *LOCAL views when the join criteria is on the JOIN clause.
  • See the SEQUEL 11 Enhancements doc for a complete list of enhancements.

Back to Sequel Products

Sequel 10

April 2014

Version R10M30

The following updates are included in this version:

  • TABLE command gives MCH0601 ‘Space offset’ error in TBLO01 when file has 1.95 million records.
  • Running a view with *LOCALSYS and syntax *SERVER with syntax in native DB2 for results sets greater than 32,000 bytes in total record size causes MCH0601 ‘Space offset’ unmonitored by QSQCLI in SQLEF.
  • Using an edit word (EDTWRD) with server *LOCALSYS and syntax *SEQUEL, was ignored.
  • Prefacing a command with a question mark in a script (i.e. ? DLTF FILE(library/file)) should cause the command to be prompted at run time from the green screen.
  • Using R10M29 and Java 1.5 (5722JV1 Option 8) with *LOCALSYS and syntax *SEQUEL, some views gave error CPF4278 ‘The specified query definition template contains a specification that is not valid.’
  • Application (SQLAPP) hangs when running a view with DBLIST with a filter because only a double quote was tested for, instead of double or single quote.
  • Using BCHEXECUTE with a prompted view to send an email, enclosed the message in single quotes.
  • The Viewpoint Report Designer ended in error when the view had more than 9,000 positions.

The following enhancement is included in this version:

  • GETLASTLOC and GETLAST functions created. Using similar syntax, they return either the position for the last occurrence of a specified character, or return the remainder of the search string after the last occurrence of a specified character.

October 2013

Version R10M29

The following updates are included in this version:

  • Creating a remote database file with dates greater than year 2039 were written to the remote data base as the null value rather than the actual date.
  • Host tables that return a very large number of records were unable to rank correctly. Only the first row showed a rank of 1 and remaining rows are unranked.
  • UPDATE over a remote database view (SQLVIEWM) view gives an SQL conversion error.
  • SCRETURN used in Script Views did not handle *ALL or *OMIT for a variable value.
  • In the Viewpoint Script Designer, when prompting the EXECUTE command, the last PC format in the list did not show.
  • SCRETURN in a Script View over a Client Report or Host Report did not respect the UNIQUEKEY parameter.
  • Runtime SQL conversion causes syntax errors when multiple files had correlation names.
  • Runtime SQL conversion causes error when unqualified field name is the same as a file name.
  • Runtime SQL conversion did not handle the MIN and MAX functions with more than one parameter, rather than just one parameter.

The following enhancements are included in this version:

  • The SYNTAX parameter was added to the CVTQRY command to facilitate Query conversion with view attributes to utilize the SQE.
  • Host Table performance on V6R1 and above was dramatically improved. Testing results were at least five times faster.

August 2013

Version R10M28

The following updates are included in this version:

  • Designing a Host Report with an SQL statement over a remote database caused error MCH0801 ‘Argument associated with external or internal parameter not passed’.
  • In SWI, intermittent JSON errors or no records returned when more than 100 SWI results tabs opened. The limit was increased to 1,000.
  • From the Design View (DSNVIEW), F9 screen Green Screen designer produces .txt file when *XLSX was chosen.
  • When Viewpoint options set to send joblog when submitted job completes did not send email if a spooled joblog was not produced.
  • From SWI, PDF output can be truncated because page size attributes not used from user SEQUEL defaults (SETDFT).
  • SEQUEL Defaults (SEDFT) provides and allows a value of *JOB for the Job Description. This is not valid and should not be allowed.
  • The green screen Script Designer should not a host table to be placed on the SCRETURN command.

May 2013

Version R10M27

The following updates are included in this version:

  • A Script Command Label name is truncated at seven characters when run from the green screen using RUNSCRIPT.
  • Scripts run from both green screen and Viewpoint are not properly monitoring for the message (MONMSG). Scripts ended with the error instead of continuing to process when the monitored message was encountered.
  • In Viewpoint Script Designer, saving a script to a Library that doesn't exist gives a false success message.
  • Saving script or running script from Script Designer when script has a comment line of all asterisks (*****) gives error RNX1255 - ‘Session or device error occurred in file SCRCMDD’.
  • Message handling was improved within the Script Designer to provide the statement number of the command line with the error.
  • If there is a remote server entry with a blank name, prompting the SQLCONNECT for list of servers shows none of them. Blank server entries will not be allowed to be entered through the MNTHOSTF command or Viewpoint Administrator.
  • Using the DURATION function in either STRSQL (even when properly qualified) or using *LOCALSYS and *SEQUEL produces the error SQL0204 - ‘DURATION in *LIBL type *N not found’.

March 2013

Version R10M26

The following updates are included in this version:

  • DSPVIEWD to a source file with view variables with Integrity Checks close to the maximum size of 80 create a corrupted file.
  • Submitting a script in batch, produces the error ‘CPF4101 File SCRPROC in library QTEMP not found or inline date file missing - on program SCRRUNR2’
  • *STRICT authority was not enforced for Reports, Client Reports, and Client Tables.
  • Runtime SQL Conversion for server *LOCALSYS and syntax *SEQUEL errored with derived expressions on the JOIN clause.
  • Runtime SQL Conversion for server *LOCALSYS and syntax *SEQUEL errored when view with HAVING clause in subquery.
  • Runtime SQL Conversion for server *LOCALSYS and syntax *SEQUEL errored when the TIMESTAMP function was used.

The following enhancement is included in this version:

  • Script views combine the multi-step processing capabilities of standard scripts with the ability to direct results to multiple output options like a view.

December 2012

Version R10M25

The following updates are included in this version:

  • Authorization code support added for Live Partition Mobility.

November 2012

Version R10M24

The following updates are included in this version:

  • In SWI, when a script that has multiple host reports to process, if any one of the reports returns no records, nothing gets displayed from that point down.
  • In SWI from the Explorer, scrolling through a large record set gives MCH0603 unmonitored by QRYO07BUF.
  • Application Drill-down failing from SWI with JSON Error and No Records Selected when the field referenced has an ALIAS (long field name) associated with it.
  • In jobs with DECFMT(J) or DECFMT(I), INSERT command results in QRY7010 ‘x fields specified for output but z were supplied as input’.
  • When emailing a host report emailed in RTF format, any fields that contains a slash (\) will truncate characters after the slash.
  • Improved EXECUTE with TOSERVER and OUTFILE parameter dependencies. The current change specifically prevents specification of OUTFILE and TOSERVER unless SERVER(*SEQUEL) is also used. All other requests, whether against *local, *localsys or other remote database will get QRY2234 'OUTFILE, TOSERVER and SERVER values are not compatible' if the OUTFILE parameter is provided.
  • REPORT command sending results to IFS, gets a CPE3486 'Path Name Too Long' error when the TOSTMF parameter uses one slash instead of two.

October 2012

Version R10M23

The following updates are included in this version:

  • Running the UPDATE command, based on a view did not change the 'Last used Date' on the view object.
  • FNCCLN on a specific function, instead of *ALL, gives CPD3130 ‘Missing operator in expression’.
  • In SQL Runtime Conversion, SERVER(*LOCALSYS) and SYNTAX(*SEQUEL), gives SQL0122 ‘Column x or expression in SELECT list not valid’ on a grouping view with expression in SELECT clause.

The following enhancements are included in this version:

  • The Search Script (SCHSCRIPT) command allows you to find text in the content of Script User Spaces, and optionally replace that text with alternative text.
  • The Create Script (CRTSCRIPT) command now allows many scripts to be created at one time using SCRMBR(*ALL).

June 2012

Version R10M22

The following fixes are included in this version:

  • Multiple EXECUTES from a SEQUEL host table when the table is defined using a character field for the column (i.e. no summing, etc.) created inconsistent results when the runtime generated column names are forced to RENAMED001 and RENAMED002, and so on.
  • Reports created or saved from Viewpoint using a DBCS OPEN field returned an RPT7018 ‘Field &N defined in the report is not compatible with the query view’ message.
  • Issue where WEEKDAYS function wasn't always returning correct results resolved.

The following enhancement is included in this version:

  • The SQLJOINDB file for Auto Join entries was increased from 256 positions to 2048 positions.

May 2012

Version R10M21

The following fixes are included in this version:

  • Running a view with more than 378 quotes gave the error MCH0603 ‘Range of subscript value or character string error’.
  • Using the SQL runtime conversion gave error RNX0301 ‘Java exception’ when using CHARACTER() and DECIMAL().
  • Using the SQL runtime conversion, referenced fields will be expanded with the replacement value enclosed in parenthesis.

April 2012

Version R10M20

The following updates are added in this version:

  • From the DSNVIEW green screen view designer, the FROM clause prompt won’t prompt for a member name when using SERVER(*LOCALSYS) SYNTAX(*SEQUEL).
  • EXECUTE to XLSX creates a temporary directory, such as XLSXDIRnnn, that is then zipped to create the actual .xlsx file. If the maximum .xlsx file size (uncompressed 4GB) was exceeded, the temporary directory was not cleaned up. Also improved the message text for QRY7018.
  • DBCS field attributes were returned incorrectly as zero length in both Viewpoint and green screen.
  • A view with columns that contain the $ character sending output as xlsx created a file that was empty when opened.
  • From SWI, a view display that contained a field with a \ as the last character in that field, caused the display to come out as an unformatted string, beginning with the JSON Decode Error.
  • Executing a view gave message, CPF950A storage limit exceeded for data queue, when creating a PC file or running a client table from views with large amounts of columns or data.
  • From the Viewpoint Administrator Set Defaults option, Apply to All Users to make a global change to the SYNTAX and SERVER parameters didn’t work.
  • From Viewpoint, a view with DBLIST with filter that passes a value of an ampersand looped.
  • DSPVIEWD with a generic library name did not return view definition data.
  • In the green screen tabler designer (DSNTABLE), editing a dimension and using the Expression Editor caused error, MCH0603—unmonitored by TBLO01.
  • EXECUTE to stream file as XLSX when no file extension was specified created a zip file, but the file extension should be blank.
  • VALID_TIME was not working when a single numeric field or value was specified.
  • Writing XLSX data that includes invalid character data resulted in Excel spreadsheets that wouldn’t open, and caused error QRY7018, Spreadsheet size or row limit exceeded. Unable to insert additional rows.'
  • DSNSCRIPT evaluates CONDSQL based on the value returned. RUNSCRIPT is correct in evaluating true if 1 or more records are returned, false otherwise.
  • BCHSCRIPT ships with ALWLMTUSR(*YES).
  • A limited user running a script could encounter error, CPD0175 Command xxx in library zzz not allowed.
  • A script would hang when the last statement was a MONMSG.
  • EXECUTE with FTP sent different messages whether using view (SQLVIEW) or a runtime prompted view (SQLVIEWP).
  • When there are more than 999 user default data areas , SETAUDDFT gave error RNX1255 unmonitored by SETAUDDFTR. The limit has been increased to 9,999.

The following enhancements are included in this version:

  • The DISTANCE file used by the functions: DIST_KM, DIST_MILES, DIST_REF_KM, and DIST_REF_MILES has been updated with current zip codes.
  • A new function named DURATION easily creates a time duration in the specified elapsed time (such as, months, days, hours, etc.) from two time stamps.
  • In BLDJDELF, the number of UDC fields allowed was increased from 32 to 64.
  • Improved the space utilization of data queues, which are used when writing to PC files and Client Tables.
  • The non-prompted version of VPCLEANUP in SEQUEL was replaced with the prompted version from SEQUELEX.

February 2012

Version R10M19

The following updates are included in this version:

  • When using EXECUTE to a stream file (TOSTMF), the change of the view was modified.
  • When using DSNVIEW to open a view with SERVER(*LOCALSYS), received RNQ0202, The call to *LIBL/GETTOK ended in error.
  • With EXECUTE and *XLSX when no records were selected, the stream file process ended abnormally. The files will be written out empty so that headers show.
  • With EXECUTE and *XLSX, the process was improved to more accurately calculate when the *XLSX spreadsheet reaches its internal 4GB limit and avoid message QRY7018, Spreadsheet row limit exceeded.
  • When running a script in green screen DSNSCRIPT, the MONMSG command did not correctly monitor for the specified message. For example, MONMSG MSGID(CPF0001) didn’t detect a CPF0001 escape message.
  • Prompting the PCFMT of the EXECUTE command did not show *TXT even though it was allowed.
  • Changed all service programs to be owned by QSYS.
  • DSPDASHD did not return results.

The following enhancements are included in this version:

  • Made a performance enhancement to the Viewpoint Expression Editor in View Designer when using *LOCALSYS connections and join logical files.
  • Opening the green screen view designer using DSNVIEW *CREATE uses the Default Server from the user defaults (SETDFT).
  • Added a new function named WEEKDAYS to calculate the number of weekdays between two dates.
  • The RTVRPTD size limit for embedded SQL statements was increased to 20,000 positions.
  • CVTQRY now has a SERVER parameter so Queries can be imported to use *LOCALSYS.

December 2011

Version R10M18

The following update is included in this version:

  • When using SEQUEL R10M17 and the RBTADMIN user profile didn’t exist on the system, SEQUEL gave error MCH1001, Attempt to use permanent system object DFMT10 without authority.

November 2011

Version R10M17

The following updates are included in this version:

  • LONGJUL format of VALID_DATE returned all zeros implying the dates were not valid.
  • When creating xlsx output and the DECFMT is I or J, which uses a comma as the decimal separator, the command needed to be written in the xml data using a period.
  • From the SWI Explorer, sorting on a column with data with embedded double quotes (“) failed.
  • From the SWI Explorer view results, sorting on a field with an alias name caused error QRY2006, field specified in ORDER BY clause not found in file list, because the ORDER BY clause used the alias and not the field name.
  • Large, complex views with many single quotes caused MCH1202, Decimal Data Error, in GETSTR.
  • MONMSG in a script failed if preceded by a blank line.
  • Script with QSTRING variables run from a green screen environment was putting extra quotes around the variable.
  • LIDLOBJX used USRPRF(*OWNER), changed to USRPRF(*USER).
  • PRINT should not issue errors CPD4008, Printed record of file SQLPRT1 continued on next line, or CPD4090, Printer device not found.
  • BCHPRINT truncated SQL statements when it ran.
  • EXECUTE to PDF with password and runtime prompted view did not require the password when opening the PDF.
  • From the SWI Explorer, received an unexpected error when displaying user spaced dashboard (SQLDASH) saved from PC dashboard (.vpt) with Viewpoint 10.11.280.

The following enhancements are included in this version:

  • Auditing now supports remote database views, including *LOCALSYS views.
  • Additional checking when designing or running a host report to detect the data type of fields has changed from numeric to non-numeric.
  • Number of SUM calculations in a host report was increased from 100 to 200 to avoid MCH0603 error in QRYO03.
  • Enhanced the xlsx process to use command SQZIP instead of ZIP to avoid potential conflicts.

October 2011

Version R10M16

The following updates are included in this version:

  • In Viewpoint, fields with a Numeric edit code with a floating dollar sign (for example, EDTCDE(1$) ) gave error QRY2301, Identifier '$' preceding ') FROM seq' is used incorrectly.
  • Designing a host report over a view with a remote database connection with a 10-character field name on the ORDER BY clause caused error RP7011, Report summary levels are incompatible with query ordering.
  • SQVER gave error RNX0100, length or start position is out of range for the string operation, when the company name was between 38 and 40 positions.
  • Host reports were not correctly displaying Chinese characters. Attributes of display files were changed to support DBCS.

The following enhancements are included in this version:

  • Added the STRICT setting to Object Authority Checking Provides to provide an additional layer of security to restrict design and run-time access based on the entries in the SEQUEL Security Dictionary.
  • Work with Audit was enhanced to analyze strings up to 25,000 positions to avoid MCH3601 error on exit.

September 2011

Version R10M15

The following updates were included in this version:

  • When a report has ORDER ONLY fields, the message RPT7011, Report summary levels are incompatible with query ordering, is now a Diagnostic, not an Escape message.
  • Report Designer was not handling 10-character ORDER BY field names when the view used a remote database.
  • The automatic Host Report conversion process, which happens only when there have been long lapses between updates, was changed to leave the report CCSID set to 0 during the conversion. This allows the report to be designed with the correct CCSID in non-English environments.
  • Changed the TOSTMF parameter of the EXECUTE command so a string beginning with // is not assumed to be a remote database connection.
  • The process to zip a *XLSX file when the job had a non-English CCSID gave error CPRF9898, ‘error in opening ¢Content_Types!.xml for reading’.
  • An EXECUTE with a view that used SERVER(*LOCALSYS) to override the view caused error QRY9995, SQL statement empty or blank.
  • When connecting to a remote database, if ADDENVVAR to specify JAVA_HOME was used, error MCH3601 in SQLQRYMJNI occurred.
  • Runtime SQL Conversion ( *LOCALSYS *SEQUEL) gave error QRY2232, Cannot translate SQL from *SEQUEL syntax to standard SQL, with *PARTOUT join on derived field.
  • The PRINT command did not include the SQL summary at the bottom even though SUMMARY(*YES) was specified.
  • EXECUTE using a host table (SQLTBLV) that uses a runtime prompted view (SQLVIEWP) created an output file with the same name as the table in the library of the table, not based on the OUTFILE parameter.
  • Creating an XLSX file to an unqualified directory caused the error, Excel cannot open the file myfile.xlsx because the file format or file extension is not valid, when opening the file.

The following enhancements are included in this version:

  • The INSERT, UPDATE, and DELETE commands were enhanced to include the SERVER and SYNTAX parameters to allow data manipulation on remote databases.
  • Print Report Definition (PRTPRTD) was enhanced to include an SQL statement from view.
  • From DSNVIEW, the F9 screen to create a PC file now supports *XLSX, *XMLXLS, and *PDF formats.

July 2011

Version R10M14

The following updates were included in this version:

  • When ORDER BY fields have been removed from the SELECT clause, running the report gave error MCh3405, Tried to deactivate program QRYO06 while it is running.
  • From the SEQUEL Web Interface, when SEQUEL User Defaults were set to Query Auditing Y, creating a remote database table created the table, but erroneously sent message MCH3401, Cannot resolve to object SQLEXEC.
  • An EXECUTE in *XLSX format when the view contains edit codes with a currency symbol ($) to an IFS stream file using the TOSTMF parameter caused an error when opening the file in Excel.
  • Execute of Host Table (SQLTBLV) over a prompted view (SQLVIEWP) to a stream file as PDF or RTF did not create the file.
  • RUNCMD *PGM now runs under *USER, not *OWNER.

The following enhancement was added to this version:

  • The method for Java startup to make remote database connections was improved to connect using the new technology JVMs under V7R1.

June 2011

Version R10M13

The following updates were included in this version:

  • Improved message handling on DSNVIEW when not using SERVER *SEQUEL or *LOCALSYS.
  • From the SEQUEL Web Interface, when Query Auditing in user defaults was set to Y, it gave error CPF2479 in SNDJRNE01.
  • Using SQL Runtime Conversion, SERVER(*LOCALSYS) and SYNTAX(*SEQUEL) with HREF gave error SQL0204.
  • From Viewpoint, a host table (SQLTBLV) that produces more than 34 columns would give error CPF2498 ‘Invalid length. MAXLEN for data queue is 2048’.
  • REPORT to a stream file ended in error if the file existed and REPLACE(*NO) was used on the command.
  • Submitting a runtime prompted report from the exit screen of DSNREPORT using F14 would give errors CPD0020 ‘Character ''' not valid following string 'SAME’ and CPD0014 ‘Matching apostrophe not found’.

The following enhancements are included in this version:

  • In SQL Runtime Conversion, SERVER(*LOCALSYS) and SYNTAX(*SEQUEL) now handle System/36 file names that include periods.
  • Added support for Excel .xlsx and .xmlxsl formats.

May 2011

Version R10M12

The following updates were included in this version:

  • From the SEQUEL Web Interface, Download View results to Excel showed numbers as negative, blank, or a box the first time it was downloaded (requires SEQUEL Web Interface R10M02).
  • From Viewpoint, ‘No records returned’ messages were returned properly in unique cases.
  • REPORT command to send an e-mail message (EMLMSG) that was less than four characters did not include the attachment.
  • EXECUTE a VIEW to e-mail as PDF sent two e-mails with attachments when no records were selected.
  • From the green screen designer (DSNVIEW), when changing a SQLVIEW to SQLVIEWP by adding a variable or prompting the SELECT clause of a view larger than 9800 characters, caused message QRY3004, String beginning is never ended.

The following enhancement was added to this version:

  • Added a new function, VAL2WRD, which converts numeric values to words.

May 2011

Version R10M11

The following updates were included in this version:

  • Saving a runtime prompted view with more than 9,800 characters from Viewpoint caused error CPD0014, A matching parenthesis note found.
  • Running a view from Viewpoint that returned no records and included a date expression converting a literal to a date data type caused error MCH1202, Decimal data error in VPTROUTER.
  • In the Viewpoint View Designer, the Join Type was not saving when Database was changed on the Properties tab.
  • Designing a Client Report in Viewpoint over a view where one variable has an integrity test that depends on another variable resulted in error MCH1202, Decimal data error, when trying to save the report.
  • When using PRINT or EXECUTE to e-mail PDF output when the user default value of ‘Send if no data’ was No, the associated spooled file was not deleted.

The following enhancements are included in this version:

  • In the Administrator Set Defaults Host tab, *LOCALSYS was added as an value and the Server parameter was added.
  • Performance improvement to QRYO07 on V6R1 when creating files on the IFS.

March 2011

Version R10M10

The following updates were included in this version:

  • TABLE command gave error message CPD0078 “Value ' 'for parameter JOB not a valid name” when using F14 to submit from a prompt variable.
  • EXECUTE with TOSTMF with *STDOUT and run-time prompted view did not create a file.
  • Runtime prompted views (SQLVIEWP) with many expressions caused MCH0603, ‘Array Index Error’ in GETTOK.

The following enhancement was added to this version:

  • CVTQRY now supports a CROSS JOIN.

March 2011

Version R10M09

The following updates were included in this version:

  • Table with an Embedded Category field longer than 40 positions gave error MCH0603, Unmonitored by TBLO01.
  • Using the batch commands (for example, BCHEXECUTE, BCHPRINT, and BCHREPORT) could cause error MCH1210, Unmonitored by SQLRQSC, when the message queue was full.
  • Script definitions from DSPSCPRIPTD showed wrong order of variables in a script.
  • View or script with a COMP Integrity test with a DATE variable gave MCH1202 Decimal Data error.
  • Green screen designer, DSNSCRIPT, removed comments from internal commands.
  • List dictionary commands had wrong names. LSTXCLOBJ was changed to LSTDCTOBJ; LSTXCLUSR was changed to LSTDCTUSR.
  • Sequel Field Level Authorization report had EXCLUSION in the title regardless of actual dictionary type.
  • Using *LIBL file designation on a FROM clause in conjunction with *SEQUEL Inclusion security resulted in error, “can’t find file *libl/”, when designing a view.

January 2011

Version R10M08

The following updates were included in this version:

  • Improved message handling when host table gives MCH1210 unmonitored by TBLO01 and SQLTBLC when maximum number of column groups is reached.
  • From a script in Viewpoint, REPORT with RECIPIENT picked the wrong spooled file for e-mailing when the same host report was run multiple times in the same script.
  • PDF output without a PDF password gave the message “Adobe Reader could not open.”

November 2010

Version R10M06

The following updates were included in SEQUEL version R10M06:

  • SEQUEL functions were not created when using FNCRUN if the decimal format (DecFmt) was a comma.
  • Using EXECUTE to create a TOTABLE on a TOSERVER gave an error when the OUTFILE library and name were long. Various Java errors were issued that did not seem specific to the problem.
  • The time and date in the SEQUEL Host Report showed wrong values when an AnyDate override was active.
  • In rare instances, running a script from Viewpoint gave the error MCH1202 “Decimal Data” in VPTROUTER.

October 2010

Version R10M05

The following updates were included in this version:

  • The SPLIT function gave error MCH3601, Pointer not set for location referenced, on V6R1 when null values are returned.
  • Using SQL Runtime Conversion, SERVER(*LOCALSYS) and SYNTAX(*SEQUEL), EXECUTE was creating variable-length (Unicode) fields two bytes shorter than they are supposed to be. This caused error SQL0332, Character conversion between CCSID 13488 and CCSID 65535.
  • SQLCONNECT gave error QRY9995, The driver could not establish a secure connection, on a V7R1 connection to an SQL Server 2005 database.
  • Using SQL Runtime Conversion, SERVER(*LOCALSYS) and SYNTAX(*SEQUEL), on a UNION view with more than one UNION gave error MCH0603, Range of subscript value or character string unmonitored by QRYP02.
  • Using SERVER *LOCAL or *LOCALSYS with SYNTAX(*SERVER) when the ORDER BY used an expression caused error MCH3601, Pointer not set for location referenced.
  • Using SERVER *LOCAL or *LOCALSYS with SYNTAX(*SERVER) with EXECUTE to create a keyed physical file when the ORDER BY used an expression caused error CPF3206, Key field x not found in record format VIEWFMT.
  • Using SQL Runtime Conversion, SERVER(*LOCALSYS) and SYNTAX(*SEQUEL), on view/SQL statement with IN or NOT IN using only one value gave QRY2232, Cannot translate SQL from *SEQUEL syntax to standard SQL.
  • Using SQL Runtime Conversion, SERVER(*LOCALSYS) and SYNTAX(*SEQUEL), didn’t translate CONTAINS predicate.
  • From Viewpoint, a submitted e-mail request to create an Excel file using SERVER(*LOCALSYS) and SYNTAX(*SEQUEL) and CVTDATE caused error SQL0104, Token.1 was not valid.
  • E-mailing a PDF created with a password from EXECUTE and PRINT did not require a password to open the PDF document.
  • Any process using multiples of the following parameters: OPTIMIZE, ALWCPY, IGNDECERR, UNIQUEKEY, MSG, JTYPE, JORDER, DTSTYLE, SERVER, SYNTAX, or TEXT could cause error CPF0013, A matching parenthesis not found.
  • On the AutoPrompt window for runtime prompts, lengthy extended help text was truncated in Viewpoint.

The following enhancement was added to this version:

  • Using SQL Runtime Conversion, SERVER(*LOCALSYS) and SYNTAX(*SEQUEL), on a partial outer join on a derived field caused error SQL0199, Keyword AND not expected. Valid tokens: ON FULL LEFT CROSS INNER RIGHT USING EXCEPTION.

August 2010

Version R10M04

This version included changes that were internal to the product.

July 2010

Version R10M03

The following updates were included in this version:

  • Saving a Client Table built on embedded SQL failed with an error about an invalid server name.
  • SEQUEL was unable to save results from a *LOCAL or *LOCALSYS view to a remote database.
  • Entering an empty string for a column heading caused incorrect column headings at runtime and various design problems on the Files/Fields tab.
  • Column headings for SERVER(*LOCAL/*LOCALSYS) used the field names rather than the column headings in the file.
  • Views using SYNTAX(*SEQUEL) that include WDATA fields used wrong column headings.
  • In the green screen designer, diagnostic messages didn’t appear to the user when using the SEQUEL Inclusion/Exclusion security dictionary.
  • In the green screen designer, using F9 to EXECUTE and ADD Records resulted in existing records being replaced.
  • Sending SEQUEL output to a PC file in text or pdf format in a CL program resulted in an unmonitored CPF3344 message even though the PC file results were created successfully.

The following enhancement was added to this version:

  • Improved the conversion of *SEQUEL statements to *LOCAL//*LOCALSYS for grouping views to preserve correct file qualification on the Group By clause.

June 2010

Version R10M02

The following updates were included in this version:

  • In the green screen Design View, the ORDER BY clause prompting was not working correctly.
  • In the green screen Design View, the WHERE F13 Subquery prompt returned a jumbled SQL statement.
  • PRINT with PCFMT(*TEXT) gave error QRY2218, Invalid PC Format specified
  • CHGVIEW gave errors QRY2305 or QRY2006 indicating an invalid SQL statement. This was most commonly seen when using CHGVIEW in a CL program.
  • EXECUTE with OUTFILE and REPLACE(*YES) did not delete the outfile first.
  • Saving a view from the CHGVIEW screen gave MCH3601, Pointer not set for location referenced.
  • EXECUTE to *xls gave MCH0603, Range of subscript value or character string error, in QRYO07 when intermediate storage for the XLS file was exceeded.

The following enhancements are included in this version:

  • Added help text for the DSPDASHD command.
  • The Date Style (DTSTYLE) of a remote database view (SQLVIEWM) will always use *ISO for the date/time format.Databases other than DB2 do not have the concept of a run-time DTSTYLE so this allows for consistent date styles across databases.
  • Changed the format of excel files created through EXECUTE to be considered from a trusted site to avoid a warning message in Excel 2010.

May 2010

Version R10M01

The following updates were included in this version:

  • IS NULL comparisons generated a CPD4325 selection error.
  • OVRPRTF FILE (*PRTF) caused the PRINT and REPORT commands to fail with MCH1210 ‘Receiver value too small to hold result’.
  • RUNCMD returned CPD0043 ‘SYNTAX keyword not valid’ when a runtime prompted view (SQLVIEWP) was used in the VIEW parameter.
  • SQLPARMS file was changed to support LEFT and RIGHT functions from the Viewpoint Expression Editor.
  • Batch commands (such as BCHEXECUTE) failed with message CPD00014, Matching apostrophe not found. This was a random occurrence based on the message key variable.
  • Removed obsolete object SWI815DA from the SEQUEL library.
  • In Viewpoint, selecting ‘Save Results As>Physical File’ with a prompted view (SQLVIEWP) set to run immediately generated RNP6999 ‘Variables must be set before this runtime view can be run’.
  • The initial size of CPIALL *FILE has been changed to *NOMAX.
  • The OUTFILE command generated error CPD0172, Parameters passed on call do not match.
  • Table views (SQLTBL) over remote database to create a PC document failed with QRY9995 and CPF4278.
  • F16 (User Defined Options) in the Work with SEQUEL Objects display (WRKSEQUEL) showed an incorrect option list based on file name.
  • Change added for remote database views (SQLVIEWM) with field names greater than 10 positions.
  • In a runtime prompted view (SQLVIEWP), the title or TEXT parameter was truncated at 40 positions if a variable was included as part of the value.

The following enhancements are included in this version:

  • Output from REPORT TOSTMF(*STDOUT) has been enhanced to allow PCFMT(*PDF) and PCFMT(*TEXT) values.
  • Added SEQUEL 10 runtime conversion support for the following UDF functions: INDEX, VERIFY, and XLATE.
  • The CVTANSI size limit was increased from 9,000 to 20,000 positions.

 

Back to Sequel Products