Optional DM841-50

DETAILS:

The DataMiner system variable PARM-DATA can collide with a user-defined variable 

or EZT defined work field.

RESOLUTION:

Apply the following optional fix to remove the variable.

NAME CSIDMBIP CSIDMBIP

IDRDATA F007463

VER C3EC 60

REP C3EC 5B

Fix DM841-02

DETAILS:

A SOC4 ABEND is possible in CSIDMBMD when executing a DataMiner load module.

This module is generated with either the OPTION LINK statement or EZT PARM LINK

statement for later execution.  

RESOLUTION:

Apply the following fix.

NAME CSIDMBMD CSIDMBMD

IDRDATA F007464

VER 03E4 A70A0010

REP 03E4 A70A0048

Fix: DM841-01

DETAILS:

The internal simulation for the EZTPX01 toolkit macro produces the following 

DMIN005E error message:

    DMIN005E Invalid fieldname                          'fieldname '

RESOLUTION:

Apply the following fix.

NAME CSIDMBIP CSIDMBIP

IDRDATA F007462

VER 000772 D460

VER 00B8C0 5890A768589090445800AE7850009050

VER 011A70 D2314000A838

REP 000772 D46D

REP 00B8C0 5810AE74581010005010905007000700

REP 011A70 D2244000A838

Fix DM834-03

DETAILS:

"¬=" is not recognized as the not equals symbol.  This causes the following

syntax error messages:

    DMIN012E Invalid literal                            ¬

    DMIN068E Invalid expression                          fld1 ¬= value

RESOLUTION:

Apply the following fix.

NAME CSIDMBIP CSIDMBIP

IDRDATA F007454

VER 1300 6E4C

REP 1300 B07E

Fix DM834-02

DETAILS:

The following DB2 automatic retrieval method will cause subsequent errors

further down in the script.  In this example, it produces the DMIN006E error

message.

JOB INPUT SQL

SELECT * FROM DSN81210.EMP

 DISPLAY EMPNO FIRSTNME LASTNAME WORKDEPT EDLEVEL SALARY

DMIN006E Field start position is invalid            FIRSTNME

RESOLUTION:

Apply the following fix.

NAME CSIDMBIP CSIDMBIP

IDRDATA F007451

VER 00C6 B0C6B0C8B0CAB0CCB0CEB0D0B0D2B0D4

VER 00D6 B0D6B0D8B0DAB0DCB0DEB0E0B0E2B0E4

VER 9102 D207A9C3C1D8

VER 910C 4780C056

VER F15A 94FBD726

VER 0177BA 4770C1F4

REP 00C6 94FBD7269108D8DC4710CF0847F0CEF6

REP 00D6 4770C1F495E2A7204780C1F447F0C1E6

REP 9102 D23FA7F8AA45

REP 910C 47F0C056

REP F15A 47F0B0C6

REP 0177BA 47F0B0D6

Fix PTF DM834-01

DETAILS:

When displaying or reporting DB2 fields (columns), the columns widths are only

set properly for Character fields.  Varchar, packed, zoned, and binary fields

are not set correctly and unpredictable output results.

RESOLUTION

Apply the following fix.

NAME CSIDMBCR CSIDMBCR

IDRDATA F007450

VER 00C6 B0C6B0C8B0CAB0CCB0CEB0D0

VER 209C 4010905E

REP 00C6 4010905E401090CA47F0C158

REP 209C 47F0B0C6

Fix DM833-05

DETAILS: 

Correct issues with FILE EXIT close.

The process of calling the FILE EXIT may fail when the LE environment is

established AND the script is using the report writer.

RESOLUTION:

Apply the following fix.

NAME CSIDMBPR CSIDMBPR

IDRDATA F007442

VER 00DA B0DA,B0DC,B0DE,B0E0,B0E2,B0E4

VER 00E6 B0E6,B0E8,B0EA,B0EC,B0EE,B0F0,B0F2,B0F4

VER 00F6 B0F6,B0F8,B0FA,B0FC,B0FE,B100

VER 374C 47F0,C326

REP 00DA D203,AEF0,C908,D203,D5AC,6140

REP 00E6 D203,D5B0,6144,50C0,D194,58C0,C904,05EC

REP 00F6 58C0,D194,94BF,60D9,47F0,C326

REP 374C 47F0,B0DA

Fix PDM833-04

DETAILS:

A complex IF statement that contains a not equal condition and a list of values

may not function correctly.  Certain cases will always result in a false 

condition and branch around the statements between the IF and the following ELSE

or END-IF.

For example:

    FLD1   W   4   P VALUE 1

    FLD2   W   4   P VALUE 2

    FLD3   W   4   P VALUE 3

    JOB INPUT NULL

      IF FLD1 = 1 AND +

         FLD2 NE 1 AND +

         FLD3 = 2,3

       DISPLAY 'MATCH' FLD1 FLD2 FLD3

      ELSE

       DISPLAY 'NO MATCH' FLD1 FLD2 FLD3

      END-IF

      STOP

The list component of the IF statement above (FLD3 = 2,3) will not function

correctly, leading to an incorrect outcome for the script.

RESOLUTION:

Apply the following fix:

NAME CSIDMBIP CSIDMBIP

IDRDATA F007440

VER 0000E8 B0E8B0EAB0ECB0EEB0F0

VER 0000F2 B0F2B0F4B0F6B0F8B0FA

VER 015760 58E0D8EC

REP 0000E8 58E0D8ECD203D6A0B74B

REP 0000F2 D202D6A4B57447F0C1FC

REP 015760 47F0B0E8

Fix DM833-03

DETAILS:

When an OCCURS field matches exactly to a previous record field, an error

message is incorrectly issued:

DMIN075E Invalid OCCURS clause statement

Although valid, this example (and similar code) will cause the DMIN075E error:

FILE FILEA

FIELD1 1 10 A OCCURS 5

FIELD2 1 10 A OCCURS 5

RESOLUTION:

Apply the following fix.

NAME CSIDMBIP CSIDMBIP

IDRDATA F007439

VER 0000D2 B0D2B0D4B0D6B0D8

VER 0000DA B0DAB0DCB0DEB0E0B0E2B0E4B0E6

VER 0133F0 4720C0E8

REP 0000D2 4720C0E84770C054

REP 0000DA D501904830484780C0E847F0C054

REP 0133F0 47F0B0D2

Fix DM833-02

DETAILS:

A S0C1 ABEND at OFFSET=00003046 in CSIDMBPR may result when using direct access

(READ, POINT and WRITE) to an IAM dataset. This error occurs because the IAM key

length and relative key position are incorrectly initialized with high values.

RESOLUTION:

Apply the following fix.

NAME CSIDMBBF CSIDMBBF

IDRDATA F007438

VER 00C6 B0C6B0C8B0CAB0CCB0CEB0D0B0D2

VER 00D4 B0D4B0D6B0D8B0DAB0DCB0DEB0E0

VER 00E2 B0E2B0E4

VER 1B0A 50106098

VER 1B12 501060FC

REP 00C6 12114740C2965010609847F0C296

REP 00D4 121147B0B0DEA71800FF501060FC

REP 00E2 47F0C29E

REP 1B0A 47F0B0C6

REP 1B12 47F0B0D4

Fix PTF DM833-01

DETAILS:

Specifying an OCCURS field greater than 32K produces a S0C4 ABEND in CSIDMBIP.

This fix corrects the issue by increasing the internal literal table size from

from 32K to 1MB.

RESOLUTION:

Apply the following fix.

NAME CSIDMBIP CSIDMBIP

IDRDATA F007437

VER 097C 00007D00

REP 097C 00100000

Fix DM821-03

DETAILS:

If the REPORT SUM subcommand is encountered before the LINE subcommand, fields

are not summarized.

RESOLUTION:

Apply the following fix.

NAME CSIDMBIP CSIDMBIP

IDRDATA F007418

VER 0000C6 B0C6B0C8B0CAB0CCB0CE

VER 019006 47F0C222

REP 0000C6 D701D69CD69C47F0C222

REP 019006 47F0B0C6

Fix DM821-02

DETAILS:

When running a compile and link, the following DMIN109E message is written and 

the job terminates with rc=16.  This will occur when the script references a

sequential file (via INPUT or FILE statements) and the DD is not specified or

included in the JCL.

    DMIN109E No blocksize or lrecl for filename - cannot continue

The DD statement is not required until the program is actually executed, however

the compile and link step incorrectly flags this scenario with the DMIN109E

message.

The compile an link is controlled via the OPTION command with LINK operand or

the PARM statement with LINK operand.

RESOLUTION:

Apply the following fix.

NAME CSIDMBBF CSIDMBBF

IDRDATA F007416

VER 00C6 B0C6B0C8B0CAB0CCB0CEB0D0B0D2B0D4

VER 1CA6 4710C236

REP 00C6 4710C2369108A6F04710C23647F0C082

REP 1CA6 47F0B0C6

Fix DM821-01

DETAILS:

Use of one or more subscripted field in an assignment command/statement

will cause various syntax errors on the commands/statements that follow.

For example:

    FIELD1(1) = 123 or FIELD2(index) = 'ABC'

can cause the following subsequent syntax errors:

    DMIN076E Invalid or missing subscript

    DMIN068E Invalid expression

    DMIN033E No matching "IF" or "DO" command

RESOLUTION:

Apply the following fix.

NAME CSIDMBIP CSIDMBIP

IDRDATA F007415

VER 6910 47F0C1CE

REP 6910 47F0C196