Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook
Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook
When you import a COBOL copybook into a data map from the PowerExchange Navigator, the Navigator can generate trace output that shows an enhanced data memory map.
In comparison to the data division map that the IBM IGYWC compile procedure produces, the trace memory map provides additional information and uses a format in which FILLER and REDEFINES groups are easy to identify. Use the trace when you need to perform any of the following tasks:
Troubleshoot mapping errors from the PowerExchange Navigator machine instead of from the z/OS system
Verify that the memory map is consistent with the data map
Check the offsets of copybook items in storage
Check FILLER and REDEFINES items to ensure that they're correctly mapped
Ensure that any FILLER_REDEF_
nn
fields that PowerExchange adds for redefinitions are consistent with padding values
Identify any fields that do not need to be mapped
View map information that is not available from the IBM IGYWC compiler, including COBOL levels, locations of FILLER and REDEFINES items, padding, and OCCURS values
To configure and run the trace, perform the following steps:
In the dbmover.cfg configuration file on the Windows system where the PowerExchange Navigator runs, specify the following TRACE statement:
TRACE=(COBDTL,0,99)
In the PowerExchange Navigator, import the COBOL copybook into a data map.
PowerExchange Navigator generates the trace output in the detail log, or in an alternative log file if you specified the TRACING statement in the dbmover.cfg file.
Compare the generated trace output to your copybook to ensure that data storage is correctly mapped.