IBM Mainframe Forum

I'm working on changing the text in the DFHMDF from a hard-coded literal to a program-filled variable. So far, this is working fine - and I can see that the Module Size for the map increased, from F38 to F48. This is a decimal change of 16 - so I am a little surprised there.

Here's the original map:

Select all

TAG0020  DFHMDF POS=(13,59),LENGTH=0012,ATTRB=ASKIP
         DFHMDF POS=(14,03),LENGTH=0020,ATTRB=ASKIP,                   C
               INITIAL='BOX 7 (NON-EMPLOYEE)'
TAG0021  DFHMDF POS=(14,25),LENGTH=0012,ATTRB=ASKIP

I changed this to:

Select all

TAG0020  DFHMDF POS=(13,59),LENGTH=0012,ATTRB=ASKIP
TAG0021  DFHMDF POS=(14,03),LENGTH=0020,ATTRB=ASKIP
TAG0022  DFHMDF POS=(14,25),LENGTH=0012,ATTRB=ASKIP

It's interesting that the length of the field remained the same, but the map increased 16 characters. I expected 3 (length and attribute), but the extra 13 makes me scratch my head.

Here's the production output:

Select all

                                                                   NOT
 + DATE-PAID  REIMB-AMT       BOX 1        BOX 6        BOX 7     REPORTED
   123119     236728.61          .00    226364.35     10343.76        20.50
   011420     425615.42          .00    404313.12     21042.30       260.00
   012820     363880.53          .00    349010.18     14726.85       143.50
   021120     381060.26          .00    366017.28     14883.82       159.16
   022520     347942.11          .00    332315.02     15482.93       144.16
   031020     362151.91          .00    349353.24     12699.92        98.75

And my output:

Select all

                                                                   NOT
 + DATE-PAID  REIMB-AMT       BOX 1        BOX 6        BOX 7     REPORTED
   123119     236728.61          .00    226364.35     10343.76        20.50
   011420     425615.42          .00    404313.12     21042.30       260.00
   012820     363880.53          .00    349010.18     14726.85       143.50
   021120     381060.26          .00    366017.28     14883.82       159.16
   022520     347942.11          .00    332315.02     15482.93       144.16
   031020     362151.91          .00    349353.24     1269

As you can see, line 6 is truncated part way through line 6.

By my count, I'm missing about 18 characters. In the program, the map size is calculated from (LENGTH OF BLV5073-SCREEN). I have new copied the map and the program into the CICS region. I have checked CEMT, but there doesn't appear to be any map settings there.
I'm not sure where to turn next.

Any suggestions???

Interesting update: I changed the size of the literal field from 20 to 15 and 5 missing characters of data reappeared.

Here's the question:

Why does changing a DFHMDF from

Select all

        DFHMDF POS=(14,03),LENGTH=0020,ATTRB=ASKIP,           C
                  INITIAL='BOX 7 (NON-EMPLOYEE'

to

Select all

TAG0021  DFHMDF POS=(14,03),LENGTH=0020,ATTRB=ASKIP

somehow change the map size?????

OK, there are an extra 3 bytes for field length and field attribute, but for the full length of the bloody field??? All I did was give it a name and remove the initial value.

I changed a map from toand the size of the map load module went up 40 bytes. So it's not just attribute and length that are affected.

Wow! What a difference a data tag makes!

So the module size gets bigger and this pushes out the fields? For example, try this one:

Select all

NAMEFD   DFHMDF POS=(23,01),LENGTH=20,INITIAL='                   '          C
                  ATTRB=ASKIP
NAME2FD   DFHMDF POS=(23,31),LENGTH=20,ATTRB=ASKIP

 

It seems that what is happening to me is before the NAMEFD moniker is made, NAME2FD appears on the screen in it's entirety. All 20 bytes in the correct columns. BUT, after adding the label NAMEFD on the first DFHMDF, NAME2FD starts in the correct position, but it suffers truncation because the new label eats up available map characters starting at the end and walking backwards.

God, I thought I understood maps & all, but now I am seriously considering a trip to the funny farm.

After all of this, I decided to just create a new map and bypass the problem altogether. Not an ideal solution, but it works.