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.