Example of a Formatted Dump - IBM - RPG

The following figures show an example of a formatted dump of a module similar to DBGEX (see “Sample Source for Debug Examples”). In order to show how data buffers are handled in a formatted dump we added the output file QSYSPRT.

The dump for this example is a full-formatted dump; that is, it was created when an inquiry message was answered with an ’F’.

Program Status Information

Program Status Information

  1. Procedure Identification: the procedure name, the program and library name, and the module name.
  2. Current status code.
  3. Previous status code.
  4. ILE RPG source statement in error.
  5. ILE RPG routine in which the exception or error occurred.
  6. CPF or MCH for a machine exception.
  7. Information about the last file used in the program before an exception or error occurred. In this case, no files were used.
  8. Program information. ’*N/A*’ indicates fields for which information is not available in the program. These fields are only updated if they are included in the PSDS.
  9. This is the file feedback section of the INFDS. Only fields applicable to the file type are printed. The rest of the INFDS feedback sections are not dumped, since they are only updated if they have been declared in the program.
  10. This is the file open feedback information for the file.
  11. This is the common I/O feedback information for the file.

Example of a Formatted Dump

Example of a Formatted Dump

The common open data path and the feedback areas associated with the file are included in the dump if you respond to an ILE RPG inquiry message with an F option.

Information Provided for Full-Formatted Dump

Information Provided for Full-Formatted Dump

Data Information

Data section of Formatted Dump

  1. Optimization level
  2. General indicators 1-99 and their current status (’1’ is on, ’0’ is off). Note that indicators *IN02, *IN04, and *IN06 were not yet set.
  3. Beginning of user variables, listed in alphabetical order, and grouped by procedure. Data that is local to a subprocedure is stored in automatic storage and is not available unless the subprocedure is active. Note that the hexadecimal values of all variables are displayed. :nt Names longer than 131 characters, will appear in the dump listing split across multiple lines. The entire name will be printed with the characters ’...’ at the end of the lines. If the final portion of the name is longer than 21 characters, the attributes and values will be listed starting on the following line.
  4. Internally defined fields which contain indexes multiple-occurrence data structures.
  5. Internally defined fields which contain the null indicators for null-capable fields.
  6. Internally defined fields which contain indexes for tables.
  7. Multiple-occurrence data structure.
  8. Data structures with no subfields are displayed as character strings.
  9. Data structure subfields are listed in alphabetical order, not in the order in which they are defined. Gaps in the subfield definitions are not shown.
  10. 4-byte and 8-byte float fields.
  11. Indicates negative infinity.
  12. Stands for ’not a number’ indicating that the value is not a valid floating-point number.
  13. Indicates positive infinity.
  14. The attribute does not differentiate between basing and procedure pointer.
  15. The local data inside subprocedures is listed separately from the main source section.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

IBM - RPG Topics