Read a DC081017 invalid internal data snap dump to determine the cause of the abend

Products

• IDMS

Issue/Introduction

Is there a way to find the data in memory, the external picture clause, the internal data type and length of the field.

Environment

Release: All supported releases.

Resolution

The DC081017 message identifies the row and column of the field on the map and the map name.

1. Go into MAPC and browse this map.
2. On the main MAPC screen enter the map name and version number and position the cursor on the DISPLAY option on the command line.
3. Next select 1 for browse.
4. Step through with PF5 for next until you are taken to the MAP LAYOUT screen.
5. Position the cursor on the field that is at the location specified by the row and column from the DC081017 message.
6. Press PF2 to select this field then PF5 to be taken to the Field Definition Screen in MAPC.
7. On this screen, the record name and field name will appear. Note both names and the external picture for the field.

Now determine the hexadecimal offset of the field in the record. To do this, display the record in IDD. Identify the field in the record and note the position of the field in the record and also the internal picture clause. Use the POSITION IS nn and ELEMENT LENGTH IS nn values. Convert nn for the POSITION which is a decimal number to its hexadecimal equivalent and subtract 1. The result of this will be the hexadecimal offset of the field in the record.

In the snap dump produced by the DC081017, do a find on RBE* and repeat this find until you locate RBE* followed immediately by the record name taken from the Field Definition Screen in MAPC. Add x'34' to the hexadecimal offset of the field into the record then add this result to the address where the RBE* eyecatcher is located in the dump. Go to the resulting address which is the sum of the RBE* address, x'34', and hexadecimal offset of the field into the record. This address will have the internal data. Check the validity of the data at this location based on the internal picture clause and the ELEMENT LENGTH IS nn taken from IDD. If the datatype at this location is incompatible with internal picture clause then this would explain the DC081017. Also verify that the external picture length is correct because that could also potentially cause the DC081017.

Additional Information

Mapping Facility