Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • PowerExchange for CDC and Mainframe 10.5.3
  • All Products

Table of Contents

Search

  1. Preface
  2. PowerExchange Navigator Introduction
  3. Data Maps
  4. Data Maps for Specific Data Sources
  5. Copybooks
  6. Registration Groups and Capture Registrations
  7. Extraction Groups and Extraction Maps
  8. Personal Metadata
  9. Database Row Test
  10. PowerExchange Navigator Examples
  11. Appendix A: PowerExchange Functions for User-Defined Fields
  12. Appendix B: User Access Method Programs
  13. Appendix C: Application Groups and Applications
  14. Appendix D: Data Map Properties
  15. Appendix E: Record, Field, and Table Properties
  16. Appendix F: DTL__CAPXTIMESTAMP Time Stamps
  17. Appendix G: Trace for Creating a Memory Map When Importing a COBOL Copybook

Navigator User Guide

Navigator User Guide

Back Next

Example Trace Output for a COBOL Memory Map

Example Trace Output for a COBOL Memory Map

If you specify the TRACE=(COBDTL,0,99) statement in the DBMOVER configuration file, the PowerExchange Navigator can generate trace output that describes the memory map for the source data record when you import a COBOL copybook into a data map in the PowerExchange Navigator.
For example, assume that you are importing the following COBOL copybook: 
      01  TESTREC1.                                      
         02  REC1-1.                                      
           05  ITEM-1.                                    
               10  ITEM-1-1            PIC  X(4).         
               10  ITEM-1-2            PIC  X(4).         
           05  ITEM-2.                                    
               10  ITEM-2-1            PIC  X(4).         
           05  ITEM-3.                                    
               10  ITEM-3-1            OCCURS 4 TIMES.    
                   15  ITEM-3-1-1      PIC XX.            
           05  FILLER REDEFINES ITEM-3.                   
                   15  ITEM-4-1-1      PIC XX.            
                   15  ITEM-4-1-2      PIC XX.            
                   15  ITEM-4-1-3      PIC XX.            
                   15  ITEM-4-1-4      PIC XX. 
           ...
Based on this COBOL copybook, the PowerExchange Navigator generates the following trace output: 
COBOL Memory Map for TESTREC1

 1  01 TESTREC1                                0CL121       pad 0    type G occurs 0       00000000 (     0) last NEW_2
... 2  02 REC1_1                               0CL42        pad 0    type G occurs 0       00000000 (     0) last ITEM_8_1_2
...... 3  05 ITEM_1                            0CL8         pad 0    type G occurs 0       00000000 (     0) last ITEM_1_2
......... 4  10 ITEM_1_1                       CL4          pad 0    type D occurs 0       00000000 (     0)
......... 4  10 ITEM_1_2                       CL4          pad 0    type D occurs 0       00000004 (     4)
...... 3  05 ITEM_2                            0CL4         pad 0    type G occurs 0       00000008 (     8) last ITEM_2_1
......... 4  10 ITEM_2_1                       CL4          pad 0    type D occurs 0       00000008 (     8)
****** 3  05 ITEM_3                            0CL8         pad 22   type R occurs 0       0000000C (    12) last ITEM_3_1_1
......... 4  10 ITEM_3_1                       0CL8         pad 0    type O occurs 4       0000000C (    12) last ITEM_3_1_1
............ 5  15 ITEM_3_1_1                  CL2          pad 0    type D occurs 0       0000000C (    12)
====== 3  05 FILLER                            0CL8         pad 22   type R occurs 0       0000000C (    12) last ITEM_4_1_4
......... 4  15 ITEM_4_1_1                     CL2          pad 0    type D occurs 0       0000000C (    12)
......... 4  15 ITEM_4_1_2                     CL2          pad 0    type D occurs 0       0000000E (    14)
......... 4  15 ITEM_4_1_3                     CL2          pad 0    type D occurs 0       00000010 (    16)
......... 4  15 ITEM_4_1_4                     CL2          pad 0    type D occurs 0       00000012 (    18)
...
This trace output includes the following information:
  • Hierarchical position followed by COBOL level. For example, in the following line, "1" is the hierarchical position and "01" is the COBOL level: 
    1  01 TESTREC1
  • Record name. For example: TESTREC1.
  • Item or group length. For example: OCL8 for a group, and CL4 for an item.
  • Padding. The pad values reflect any FILLER_REDEF_
    nn
     fields that PowerExchange adds to the data map when a REDEFINE has multiple redefinitions of varying lengths. The padding and offsets should be consistent.
  • Type of item: G for group, D for display, or R for a REDEFINES group.
    The first group of redefinitions is preceded by a series of asterisks (*). Subsequent redefinition groups are preceded by equals (=) signs.
  • OCCURS value, or 0 if no OCCURs clause is defined.
  • Offset in hexadecimal and decimal formats. The decimal offset is enclosed in parentheses.
  • Last dependent item in a group.
Compare the trace output to the following COBOL compiler output: 
Source   Hierarchy and                                    Base      Displacement  Asmblr Data                      Data Def     
LineID   Data Name                                        Locator     Structure   Definition        Data Type      Attributes   
     2  PROGRAM-ID UAMC--------------------------------------------------------------------------------------------------------*
    17   1  TESTREC1. . . . . . . . . . . . . . . . . . .             000000000   DS 0CL121         Group                       
    18     2  REC1-1. . . . . . . . . . . . . . . . . . .             000000000   DS 0CL42          Group                       
    19       3  ITEM-1. . . . . . . . . . . . . . . . . .             000000000   DS 0CL8           Group                       
    20         4  ITEM-1-1. . . . . . . . . . . . . . . .             000000000   DS 4C             Display                     
    21         4  ITEM-1-2. . . . . . . . . . . . . . . .             000000004   DS 4C             Display                     
    22       3  ITEM-2. . . . . . . . . . . . . . . . . .             000000008   DS 0CL4           Group                       
    23         4  ITEM-2-1. . . . . . . . . . . . . . . .             000000008   DS 4C             Display                     
    24       3  ITEM-3. . . . . . . . . . . . . . . . . .             00000000C   DS 0CL8           Group                       
    25         4  ITEM-3-1. . . . . . . . . . . . . . . .             00000000C   DS 0CL2           Group          O            
    26           5  ITEM-3-1-1. . . . . . . . . . . . . .             00000000C   DS 2C             Display                     
    27       3  FILLER. . . . . . . . . . . . . . . . . .             00000000C   DS 0CL8           Group          R            
    28         4  ITEM-4-1-1. . . . . . . . . . . . . . .             00000000C   DS 2C             Display                     
    29         4  ITEM-4-1-2. . . . . . . . . . . . . . .             00000000E   DS 2C             Display                     
    30         4  ITEM-4-1-3. . . . . . . . . . . . . . .             000000010   DS 2C             Display                     
    31         4  ITEM-4-1-4. . . . . . . . . . . . . . .             000000012   DS 2C             Display
...
Notice that the trace provides the following additional information: COBOL level, padding, OCCURS value, offset in decimal format, and name of the last item in a group. It also clearly identifies redefinition items.
0 COMMENTS
We’d like to hear from you!