DETAILS:

 Note: This service pack does not require a (re)BIND of the DataMiner-Dash DB2 plans.

1. Fix DUMP shortcut command when the performance option is 18 enabled. DUMP is a native DataMiner-Dash command.
2. Correct PROC translation issue when the PROC name ends with 'FILE'.
3. Resolve ABEND in CSIDMBRW +1FC following return from SORT. Occurs when an LE program ABENDs and a REPORT statement is present.
4. Correct trailer message statistics showing zero for printer files.
5. Resolve issue where a WRITE statement gets error message DMIN005E, for example, WRITE file1 UPDATE FROM file2.
6. Correct issues for Synchronized File Processing (SFP) activities when the first input file is empty.
7. Correct issues for SFP activities when the first input file is DUMMY.
8. Correct issues with VARYING fields.
9. Improve performance for alphanumeric fields in IF/DO statements and assignments.
10. Using redefined fields as key(s) in SFP causes IF MATCH to fail.
11. Title lines are missing from summary reports when CONTROL NOPRINT is used with REPORT PROC(s).
12. With REPORT PAGESIZE(n n), the second parameter is now supported.
13. Resolve S013 ABEND when SORTing a member into itself.
14. Performance option 23 disables the DMIN320W message altogether.
15. Performance option 24 disables the DMIN901I message altogether.

DETAILS:

1. Center numeric fields under longer heading(s) to match EZT layout.

2. SELECT INTO:host variables update.

• When specifying multiple host variable's null indicators, the PREPARE gets SQLCODE -104.
• Added support for DB2-controlled access using GET command. 
• Host variables are now set when using JOB INPUT SQL ... automatic input.

3. Only issue DMIN701E message on negative (error) SQLCODEs.

4. Handle CASE END when processing SQL SELECT, resolving SQLCODE -104.

5. Support SQL SELECT INTO :occursfield, resolving DMIN087E.

6. Resolve SB37 ABEND when a program has both a SORT and a Synchronized File Processing JOB.

7. Support SORTing a file into itself. Previously, specifying the same file for FROM and TO caused an SB37 error.

8. Resolve various syntax error messages like DMIN012E or DMIN068E on statements following the SQL FETCH/SELECT INTO statement. These errors generally were caused by a misplaced colon or parenthesis.

 9. Re-initialize internal (auto-defined) SQLVARnnn fields before each FETCH. Subsequent SQL OPENs for a cursor no longer re-allocates auto-defined fields.

10. Resolve a storage overlay that can cause various syntax error messages, including DMIN003E and DMIN005E.

11. Resolve an SB37 error with DISPLAY fieldname when the fieldname begins with the filename.

12. Resolve two issues with DECLARE and FETCH in multiple JOB activities:

• FETCH in subsequent JOB(s) does not set the host variable.
• The SQL OPEN in subsequent JOB(s) gets bypassed.

13. Resolve a loop in the script parser for SQL FETCH when the INTO parameter is not specified.

DETAILS:

1. Correct a problem with SELECT WHERE using 4-byte binary host variable. It was incorrectly returning no rows (SQLCODE 100).
2. Resolve a problem with INSERT null indicators (getting SQLCODE -180).

DETAILS:

1.     Handle SQL SELECT || without leading/trailing spaces. Previously, this would cause a loop.

2.     SORT now detects the end parenthesis before consuming the next operands. Previously, this would cause error DMIN006E: Field start position is invalid.

3.     JOB statement now detects the end of the KEY ( list ). Previously, it would cause error DMIN090E: Invalid number or length of keys.

4.     STOP statement inside JOB START PROC now ends the activity. Previously, STOP would end the procedure but not the activity.

5.     Change to variable-length fields (VARYING): Enforce minimum field length of 3.

6.     Performance option 12 update: Corrected problem with AND/OR compound IF statements.

7.     The date is now displayed on TITLE 1 when REPORT NOPAGE is specified.

8.     The report heading with all dashes was missing one dash; this is now corrected.

9.     Updates to SQLCODE variable:

• Added new global system variables SQLCODE and SQLSTATE.
•  SQLCODE is now treated as signed to handle negative codes.
• DISPLAY now displays signed binary fields correctly.

10.    Resolve SQL FETCH 0C1 ABEND following PREPARE error.

11.    Statement following an inline SQL SELECT INTO prints twice in the script listing.

12.    SORT BEFORE procedure name starting with "SORT" gets DMIN010E error message.

DETAILS:

1. Resolve 0C1 ABEND that can occur if/when the SQL PREPARE statement has an error. This is related to using automatic processing only.
2. Support DECLARE optional operands like WITH HOLD and WITHOUT HOLD.
3. Resolve DMIN012E error when SELECT INTO also specifies a WHERE clause containing host variable(s).

Note: This service pack does not require a bind if fix DM852-10 has already been applied.

DETAILS:

1. Add support for SQL SELECT INTO statement. This resolves the SQLCODE -104.
2. Resolve DMIN033E error related to DO WHILE statement nested inside an IF/ELSE statement.
3. Resolve the SQLCODE -302 for very large SQL statements.
4. Increase the maximum number of SQL cursors from 20 to 50. This resolves the DMIN706E error. 

DETAILS:

1.  Correct interaction of SPACE configuration/setting with SPREAD reports.

2.  Handle IF condition between character and zoned decimal fields when performance 12 is disabled.

3.  Correct SQL issue where a long cursor name causes error message DMIN068E.

4.  Correct SQL command-buffer truncation causing SQLCODE -104.

5.  Correct SQL issue where a field definition immediately following a SQL statement causes SQLCODE -104.

DETAILS:

1.  Correct issues caused by fix DM852-07. 

2.  Adjust ALPHABETIC condition check to work correctly when a space (x'40') is in the field.

3.  Adjust DISPLAY of zoned decimal fields to allow leading spaces in the field.

DETAILS:

1.  SQL updates. Continuing program support enhancements.

•  Support invoking DataMiner-Dash from IBM's utility program IKJEFT01. The CSIDMBS2 DBRM must be bound into a package and plan. 
• Resolve issue of PARM statement following CONNECT causing CAF error.
• Add diagnostic code for SQLCODE, 104, on PREPARE. To activate this facility, specify trace statement @#_TRACE SQ,ON in the script.
• Tolerate spaces before and after ":" in SQL statements.
• Tolerate no spaces between host variable and null indicator.
• Resolve problems when SQL statement follows a field definition containing OCCURS.
• Enhance SCHEMA (prefix) support for subsequent tables.
• Resolve various cascading errors following SQL SELECT.
• Resolve issues with JOB statement following SQL DECLARE, including S0C1 following the last SYSIN card and/or message DMIN098E.

2.  Support "++INCLUDE" as a synonym for INCLUDE.

3.  New configuration options to handle leading zero in SYSDATE and SYSTIME variables:

• For date, global option parameter DATELEAD=SPACE|ZERO.
• For time, global option parameter TIMELEAD=SPACE|ZERO.

4.  Handle parentheses with SORT statement parameter BEFORE(proc). The proc name can now be enclosed with parentheses.

5.  Fields in TITLE statement are off 1 column to the left. This applies only to fields using COL n positioning.

6.  Correction to title update: specifically resolve the S0C4 Report CB expansion issue.

7.  Performance option 12 now supports the IF/DO NOT operand.

DETAILS:

1.  SQL updates. This is a continuation of an earlier update.

• Handle Fetch and Insert with a comma leading on a subsequent continued line.
• Insert now handles null indicator fields.
• Support SQL SELECT.
• Support SQL SET.
• Support for 20 cursors, an increase from 10.
• Resolve issue with consecutive SQL statements.
• Handle multiple declares.

2.  Resolve message DMIN005E regarding commas.

3.  Resolve message DMIN005E when first field definition begins with "SQL".

4.  Fix copybook continuation symbols (+ and -) not working.

DETAILS:

1.  Fix for S0C4 ABEND. This corrects a problem introduced in DM852-04.

2.  New schema configuration for SQL unqualified tablenames.

• Global option parameter SCHEMA=name. This sets the global default DB2 schema.
• CONNECT statement parameter SCHEMA=name. This will override any global setting.
• Unqualified tablenames will automatically have the configured schema prefixed to the tablename.

3.  Macro parameter tolerance for parentheses.

4.  Update the DMDSPOPT report to display all DB2 configuration fields including the new default schema.

DETAILS:

1.  SQL native statement support for UPDATE, INSERT, DELETE. This also corrects an issue discovered with FETCH.

2.  Removed the 8-character limitation on the length of the cursor name.

3.  Correct trailer message regarding rows selected.  It now correctly reports the number of rows fetched.

4.  Support for a special SELECT statement when in a nested (2nd level) SORT BEGIN procedure.

5.  Handle "||" within a SQL statement.

6.  Correct issue with Report title literals containing all minus signs, where one gets stripped off.

7.  Correct issue where unsigned numeric fields with a user MASK added a reserved column (for sign) when used with DISPLAY statements.

8.  Increased TALLYSIZE maximum to 19 (was 13).

9.  Support for the IF/DO conditions ALPHABETIC and ALPHANUMERIC.

10.  REPORTs now support up to 99 titles. Also, the length of titles is no longer limited to 132. The title length is controlled by the LINESIZE.

11.  The REPORT SPACE parameter now accepts "SPACES" as an alias. 

12.  Support for 4 field headings. This affects both field definitions and the REPORT HEADING statement.

13.  Added missing NOT support for IF/DO statements (when using vectors enabled by PERF option 12).

14.  "%%" no longer causes macro invocation.

DETAILS:

1.    Update to SQL statement support.

• Resolve 0C7 ABENDS.
• Support DECLARE, OPEN, FETCH, CLOSE, COMMIT.
• Support NULL host variables.

2.    Macro support update.

•  % followed by a space is no longer treated as a macro invocation.
• Special check for %EPnnnn (and remove EP).

3.    FILE FB(lrecl FULLTRK) is now supported.

4.    Support for field definition parameter VARYING.

• Remove fieldname length limit of 25; it is now 48.
• Handle work-field definition VARYING with VALUE.

5.    Bypass issuing DMIN325W when compiling or linking program. Only issue message during execution.

6.    Bypass issuing DMIN106E when compiling or linking program. Only issue message during execution.

DETAILS:

 1.    Initial support for Easytrieve-controlled access SQL statements. 

2.    OPTION PERF no longer consumes next statement.

3.    OPTION PERF 20 disables the maximum-length (1 MB) check for work fields.

4.    Handle work fields with INDEX and no OCCURS.

DETAILS:

LIST statement directly following an OPTION statement causes error message DMIN067E Invalid parameter.

DETAILS:

1. WRITE to VSAM KSDS dataset may fail with DMIN203 ILLOGICAL Request.  This is a correction to the DM851-17 fix.
2. If the optional THEN keyword is used with IF statement and followed by unknown word, the DM parser may loop.                                                      
3. The system fields LINE-COUNT and PAGE-COUNT are now static.  This was only an issue when including either of them on the REPORT LINE statement, which is generally not done.

DETAILS:

1. Various issues related to Synchronized File Processing (SFP) are resolved.
2. SFP extended file support included.  DM now supports more than 2 files. 

DETAILS:

1. POINT statement not working correctly for IAM files. Following a successful POINT, the subsequent GET incorrectly returns the first record in the file. This is specific to files marked for output.   
2. Another correction for variable-length SUMFILE datasets. This is a follow-on to corrections included in DM851-16. The record length for the SUMFILE was not getting set correctly when the output file is variable length. 

DETAILS:

1. Support for RRDS and ESDS direct access:  

• Both POINT and READ (with) KEY now supported for RRDS.                     
• READ (with) KEY now supported for ESDS.                                    
• Note: POINT support for ESDS will be added in a future update.

2. Correction for numeric literals ending with a period: 

• Certain conditions cause message DMIN005E Invalid fieldname.              
• Other cases can cause an S0C4 ABEND.

3. Corrections for REPORT SUMFILE processing: 

• Resolve problem when the SUMFILE is V|VB and not writing any records.     
• Expand the allowed number of control fields from 8 to 32.                 
• Log error DMIN050E error message when more than 32 control fields are requested. Prior, there was no check for more than 8, and hence the potential for storage overlay and an ABEND.

4. Bypass DMIN319W when doing a script compile/link. 

DETAILS:

1. Reorganized script execution processor and removed overhead of diagnostic code.
2. Support for the BUFNO DD parameter in the Global Options table, OPTION command, and FILE statement. The IBM® default is 5. Setting this higher will reduce run times.
3. Performance option 18: Control fast path for auto-read scripts.
4. Performance option 19: Control fast path for QSAM I/O.  

To enable these options, you can add 18 and 19 to the PERF global option setting or use an OPTION command statement in scripts.

DETAILS:

1. REPORT SUMFILE not writing records when sum file is sequential disk.
2. Force leading 2 bytes of PL10 record fields to low values (as opposed to PAD setting).
3. Fields included in the report titles print blank when report procedures are involved.
4. The first DISPLAY statement within the termination procedure now combines the print control character (cc) from both the DISPLAY SKIP n and the CONTROLSKIP setting for the report.
5. Correct problem detecting empty lines for SUMCTL ALL/HIAR reports.
6. Treat multiple-LINE report lines separately when removing empty summary lines.
7. The leading Z in user masks gets truncated or blanks. The leftmost significant digit can be truncated in some cases.
8. Added two system variables: CSIDMPTF-VERSION and CSIDMPTF-TIMESTAMP.

DETAILS:

IF, DO, CASE, and assignment statements will now consume less CPU. The amount reduced varies based on the script and the system load. In general, all scripts will experience a CPU usage reduction of 10 to 30 percent.

DETAILS:

1. Reports can cause 0C7 ABEND or titles out of place/order and other errors. This is a sort-record-related issue introduced in DM851-10.
2. Intermittent 0C4 ABENDs can occur when static fields are used within report procedures.
3. The Report Writer will now detect invalid numeric fields within the sort record. This check occurs while the report is being produced. If an error is detected: 

• Increments the VALIDATION-ERRORS system variable.
• Calls the VALIDATION-CHECK if it is present in the script. Prior to this enhancement, the field would simply show blanks or spaces in the report. 

DETAILS: 

When static work fields are re-defined and then a sub-field is referenced in a report procedure, the value may be incorrect. This is due to the sub-field not inheriting the static indicator from primary static field.

DETAILS: 

When FILE EXIT parameter is specified and the script also contains CALL statements to external programs, a 0C4 ABEND can occur.

DETAILS:

When static work fields are referenced in a report procedure and specified on the report line, the work field value is incorrect. This is because the value gets extracted from the sort record rather than the static work field.

DETAILS:

When DISPLAY statements are issued outside of report procedures, the printer control character is incorrectly set to '1' for each line.

DETAILS:

1. DISPLAY statements within the BEFORE-LINE report procedure overlayed the current print line.
2. DISPLAY statements in report procedures did not increment the LINE-COUNT system variable.
3. PAGE-COUNT variable was not incremented when the report contained no titles.
4. ENDPAGE report procedure did not reference record fields.
5. Static work fields were not supported. 
6. Fields referenced in report procedures were not included in the SORT record. Except for static fields, referenced fields are now included in the SORT record and made available at report time.
7. The DISPLAY SKIP n parameter did not adjust the LINE-COUNT system variable properly.

DETAILS:

Literals continued across more than one line were inadvertently uppercased.

DETAILS:

The sign bit could be incorrect for both assignment and IF-type statements. Data exceptions (0c7 ABENDs) could also occur.

DETAILS:

Reports using the SUMMARY parameter could be missing some totals lines.

DETAILS:

Assignment statements and IF-type statements for signed binary fields of length 2 and 4 were losing the sign bit.

DETAILS:

Under a certain scenario, the control character does not match what Easytrieve produces. This isolated case can occur when a REPORT uses the CONTROL statement, and the NOPRINT parameter is specified on the first field.

DETAILS:

If the input files are concatenated, fields may be populated with random data.