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.4.0 HotFix 1
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to PowerExchange Utilities
  3. createdatamaps - Data Map Creation Utility
  4. DTLCCADW - Adabas PCAT Utility
  5. DTLCUIML - IMS Log Marker Utility
  6. DTLINFO - Release Information Utility
  7. DTLREXE - Remote Execution Utility
  8. DTLUAPPL - Restart Token Utility
  9. DTLUCBRG - Batch Registration Utility
  10. DTLUCDEP - CDEP Maintenance Utility
  11. DTLUCSR2 - IDMS SR2 and SR3 Records Utility
  12. DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility
  13. DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities
  14. DTLURDMO - Data Map Utility
  15. DTLUTSK - Task Control Utility
  16. EDMLUCTR - Log Scan and Print Utility
  17. EDMXLUTL - Event Marker Utility
  18. HOSTENT - TCP/IP Address Reporter Utility
  19. PWXCATMY - MySQL Catalog Utility
  20. PWXUCCLPRT - Print Log Summary Utility
  21. PWXUCDCT - Logger for Linux, UNIX, and Windows Utility
  22. PWXUCREG - Capture Registration Suspend Utility
  23. PWXUCRGP - Capture Registrations Print Utility
  24. PWXUDMX - Data Maps Update Time ECSA Memory Utility
  25. PWXUGSK - SSL Reporting Utility for z/OS
  26. PWXUMAP - Map List Utility
  27. PWXUSSL - PowerExchange SSL Reporting Utility

Utilities Guide

Utilities Guide

Back Next

Example: IMS DBD Import with COBOL Overlays

Example: IMS DBD Import with COBOL Overlays

This example describes a control file that creates two IMS data maps. The first data map imports DBD metadata only. The second data map imports DBD metadata and the overlaying COBOL copybook metadata for each segment.
The records in the resulting data map derive the fields and CCKs from the COBOL copybooks but retain the search fields from the DBD.
To define the DBDs and COBOL copybooks to import, the second imsDatamapInstance element includes the following elements:
  • A importDBDDetails element defines the file name and path of the DBD.
  • For each of the two segments defined in the DBD, an overlayDetails element defines the file path of the COBOL copybook and the name of the segment for which the copybook provides overlaying metadata.
The second imsDatamapInstance element also includes a datamapProperties element that defines the data map type, IMS SSID, PSB name, and PCB name.
As in Example: IMS DBD Import with No COBOL Overlay, although the DBD redefines the CRSEKEY field in the CORSECN record, the utility generates a table and record for the first redefine only.
Command Line
To run this example on the Informatica services machine, enter the following command at the command line: 
Informatica_services_installation_directory
\isp\bin\infacmd pwx createDatamaps 
-datamapOutputDir
 Output -controlFile ims_advanced.xml -logFile Output\ims_advanced.log 
-verbosity
 INFO
Control File
The control file for this example, ims_advanced.xml, contains the following lines: 

<?xml version="1.0" encoding="UTF-8"?>
<!-- 
NOTE: Metadata file paths in this sample control file are relative to current directory. 
If 'infacmd' command is issued from a different directory, all relative file paths must be replaced with absolute file paths.
-->

<!-- xmlSchemaVersion set to 1.0 -->
<DatamapGeneration xmlSchemaVersion="1.0" xmlns="http://com.informatica.cmd.pwx.createdatamaps/DatamapGeneration">
	<imsGen>
	
		<!-- Global settings for copybooks -->
		<globalCopybookParserConfig>
			<startColumn>7</startColumn>
			<endColumn>72</endColumn>
		</globalCopybookParserConfig>
		
		<!-- Global settings for datamap file name and contents -->
		<globalGenConfig>
			<schemaName>IMSADV</schemaName>
			<datamapName>TRAIN8</datamapName>
		</globalGenConfig>
		
		<datamapInstances>
			
			<!-- Datamap 1: Import from a DBD without segment overlays -->
			<imsDatamapInstance>

				<importDBDDetails>
					<filePath>
						<windowsPath>metadata\train8.dbd</windowsPath>
					</filePath>
				</importDBDDetails>
				
				<datamapProperties>
					<mapType>DL1</mapType>
					<imsSSID>SS1</imsSSID>
					<pcbNumber>1</pcbNumber>
				</datamapProperties>
			</imsDatamapInstance>
			
			
			<!-- Datamap 2: Import from a DBD with both segments overlaid -->
			<imsDatamapInstance>
				<genConfig>
					<datamapName>TRAIN8OVR</datamapName>
				</genConfig>
				
				<importDBDDetails>
					<filePath>
						<windowsPath>metadata\train8.dbd</windowsPath>
					</filePath>
				</importDBDDetails>
				
				<!-- Overlay segment 'STUDENT' with a Cobol copybook -->
				<overlayDetails>
					<nativeRecordName>STUDENT</nativeRecordName>
					<overlayCopybookDetails>
						<filePath>
							<windowsPath>metadata\student.cob</windowsPath>
						</filePath>
					</overlayCopybookDetails>
				</overlayDetails>
				
				<!-- Overlay segment 'CORSECTN' with a Cobol copybook -->
				<overlayDetails>
					<nativeRecordName>CORSECTN</nativeRecordName>
					<overlayCopybookDetails>
						<filePath>
							<windowsPath>metadata\course.cob</windowsPath>
						</filePath>
					</overlayCopybookDetails>
				</overlayDetails>
				
				<datamapProperties>
					<mapType>ODBA</mapType>
					<imsSSID>SS1</imsSSID>
					<psbName>psb</psbName>
					<pcbName>pcb</pcbName>
				</datamapProperties>
			</imsDatamapInstance>
			
		</datamapInstances>
	</imsGen>
</DatamapGeneration>
DBD File
This example uses the train8.dbd file. For the contents of this file, see Example: IMS DBD Import with No COBOL Overlay.
COBOL Copybook Files
The following lines show the contents of the student.cob copybook. This copybook overlays the DBD metadata for the first segment in the second data map. 

      *****************************************************************
      *
      *   COBOL FD DEFINITION FOR STUDENT FILE
      *
      *****************************************************************
       01  STUDENT-RECORD.
           04  ST-NAME                       PIC X(040).
           04  ST-ADDRESS-1                  PIC X(040).
           04  ST-ADDRESS-2                  PIC X(040).
           04  ST-CITY                       PIC X(030).
           04  ST-STATE                      PIC X(002).
           04  ST-ZIP                        PIC X(009).
           04  ST-NUMBER                     PIC 9(012).
           04  ST-BIRTH-DATE.
               08  ST-BIRTH-MM               PIC 9(002).
               08  ST-BIRTH-DD               PIC 9(002).
               08  ST-BIRTH-YY               PIC 9(002).
           04  ST-SEX                        PIC X(001).
           04  ST-HEIGHT                     PIC 9(002).
           04  ST-WEIGHT                     PIC 9(003).
           04  ST-HAIR                       PIC X(005).
           04  ST-EYES                       PIC X(005).
           04  ST-DATE-ENROLL-MM             PIC 9(002).
           04  ST-DATE-ENROLL-YY             PIC 9(002).
           04  ST-DATE-GRAD-MM               PIC 9(002).
           04  ST-DATE-GRAD-YY               PIC 9(002).
           04  ST-TUITION-FEES               PIC S9(8) COMP.
           04  ST-COURSE-COUNT               PIC X(003).
           04  ST-COURSE-DATA OCCURS 10.
               08 ST-COURSE-CODE             PIC 9(005).
               08 ST-COURSE-HOURS            PIC 9(002).
               08 ST-COURSE-TIME             PIC X(005).
               08 ST-COURSE-DAY              PIC X(005).
               08 ST-COURSE-INSTRUCTOR       PIC X(015).
               08 ST-COURSE-BLDG             PIC 9(002).
The following lines show the contents of the course.cob copybook. This copybook overlays the DBD metadata for the second segment in the second data map. 

      *****************************************************************
      *
      *   COBOL FD DEFINITION FOR COURSE
      *
      *****************************************************************
       01  COURSE.
           04  CRS-COURSE                        PIC X(8).
           04  CRS-SECTN                         PIC 9(1).
           04  CRS-DAY                           PIC 9(1).
           04  CRS-BEG                           PIC X(4).
           04  CRS-END                           PIC X(4).
           04  FILLER                            PIC X(4).
Log File
The log file for this example, ims_advanced.log, contains the following lines: 

2013-12-05 15:31:03 INFO [MDO_34613] Configuration for this run: location=, user name=, datamap directory=Output, control file=ims_advanced.xml
2013-12-05 15:31:10 INFO [MDAdapter_34100] Finding metadata. Path filter = metadata\train8.dbd
2013-12-05 15:31:10 INFO [MDAdapter_34101] Fetching file metadata\train8.dbd
2013-12-05 15:31:11 INFO [MDAdapter_34108] Definition CRSEKEY selected
2013-12-05 15:31:11 INFO [MDAdapter_34109] Redefinition CRSCOURS skipped
2013-12-05 15:31:11 INFO [MDAdapter_34109] Redefinition CRSSECTN skipped
2013-12-05 15:31:11 INFO [MDAdapter_34109] Redefinition CRSDAY skipped
2013-12-05 15:31:11 INFO [MDAdapter_34109] Redefinition CRSBEG skipped
2013-12-05 15:31:11 INFO [JDMX2_34801] 2 records imported.
2013-12-05 15:31:11 INFO [JDMX2_34802] 16 fields imported.
2013-12-05 15:31:11 INFO [JDMX2_34803] 3 tables imported.
2013-12-05 15:31:11 INFO [MDO_34619] Datamap file 'Output\IMSADV.TRAIN8.dmp' was written.
2013-12-05 15:31:11 INFO [MDAdapter_34100] Finding metadata. Path filter = metadata\train8.dbd
2013-12-05 15:31:11 INFO [MDAdapter_34101] Fetching file metadata\train8.dbd
2013-12-05 15:31:11 INFO [MDAdapter_34100] Finding metadata. Path filter = metadata\student.cob
2013-12-05 15:31:11 INFO [MDAdapter_34101] Fetching file metadata\student.cob
2013-12-05 15:31:11 INFO [MDAdapter_34100] Finding metadata. Path filter = metadata\course.cob
2013-12-05 15:31:11 INFO [MDAdapter_34101] Fetching file metadata\course.cob
2013-12-05 15:31:11 INFO [MDAdapter_34108] Definition CRSEKEY selected
2013-12-05 15:31:11 INFO [MDAdapter_34109] Redefinition CRSCOURS skipped
2013-12-05 15:31:11 INFO [MDAdapter_34109] Redefinition CRSSECTN skipped
2013-12-05 15:31:11 INFO [MDAdapter_34109] Redefinition CRSDAY skipped
2013-12-05 15:31:11 INFO [MDAdapter_34109] Redefinition CRSBEG skipped
2013-12-05 15:31:11 INFO [JDMX2_34801] 2 records imported.
2013-12-05 15:31:11 INFO [JDMX2_34802] 35 fields imported.
2013-12-05 15:31:11 INFO [JDMX2_34803] 3 tables imported.
2013-12-05 15:31:11 INFO [MDO_34619] Datamap file 'Output\IMSADV.TRAIN8OVR.dmp' was written.
2013-12-05 15:31:17 INFO [MDO_34614] Run complete: 2 datamap(s) created. 0 error and 0 warning messages.
Data Map Files
This example creates data maps with the following file names and relative paths:
  • Output\IMSADV.TRAIN8.dmp
  • Output\IMSADV.TRAIN8OVR.dmp
0 COMMENTS
We’d like to hear from you!