April 2017
Version: R10M07
The following Enhancements are included in this version:
- 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.
The following Updates are included in this version:
- 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.
October 2016
Version: R10M05
The following enhancements are included in this version:
- 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).
The following updates are included in this version:
- 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: R10M04
The following updates are included in this version:
- 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).
The following enhancements are included in this version:
- 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.
November 2015
Version: R10M03
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: R10M02
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.