PowerExchange Utilities Guide - Informatica Documentation... · 2016-09-02 · vi Table of Contents...

Informatica® PowerExchange®

(Version 8.6)

Utilities Guide

Informatica PowerExchange Utilities Guide

Version 8.6 June 2008

Copyright (c) 1998–2008 Informatica Corporation. All rights reserved.

This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending.

Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing.

Informatica, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Exchange and Informatica On Demand are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners.

Copyright, Byte Designs Ltd. All rights reserved.

This product includes ICU software which is copyright (c) 1995-2003 International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://www-306.ibm.com/software/globalization/icu/license.jsp.

The product includes the zlib library copyright (c) 1995-2005 Jean-loup Gailly and Mark Adler.

DISCLAIMER: Informatica Corporation provides this documentation “as is” without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of non-infringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice.

Part Number: PWX-DUM-860-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixInformatica Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Informatica Customer Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Informatica Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Informatica Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Informatica Knowledge Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Informatica Global Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Chapter 1: PowerExchange Utilities Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1PowerExchange Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

PowerExchange Utilities by Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Sample JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2: DTLCCADW - Adabas PCAT Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Utility Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

P (Populate PCAT Control File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

R (Report on PCAT Control File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

I (Insert) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

D (Delete) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

L (Reset Latest Sequence Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

V (Rebuild the PCAT Control File) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

A (Add) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

S (Submit ADASEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

T (Submit ET Record Extraction) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

E (ET/BT Record Extraction) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3: DTLCUIML - IMS Log Marker Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9DTLCUIML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 4: DTLINFO - Release Information Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Control Statement Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Control Statement Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Running DTLINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Linux, UNIX, and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

z/OS and OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table of Contents iii


z/OS and OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 5: DTLREXE - Remote Execution Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15



PING Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

SUBMIT Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Running DTLREXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Linux and UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

DTLREXE PROG=SUBMIT on z/OS and OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

DTLREXE PROG=PING on z/OS and OS/390 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

MVS Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Output Data Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 6: DTLUAPPL - Restart Token Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24


Adding or Modifying Application Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Running DTLUAPPL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27


z/OS and OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Chapter 7: DTLUCBRG - Batch Registration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . 33Overview of the Batch Registration Utility (DTLUCBRG) . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

DTLUCBRG Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Multiple Sets of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Source Specific Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Running DTLUCBRG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Sample Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38


OS/390 and z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Sample Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

iv Table of Contents

Chapter 8: DTLUCDEP - CDEP Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43



Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Running DTLUCDEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

UNIX, Linux, and Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

z/OS and OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46


z/OS and OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 9: DTLUCSR2 - IDMS and Datacom SR2 and SR3 Records Utility . . . . . . . . 49Scanning for SR2 and SR3 Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Running DTLUCSR2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 10: DTLUCUDB - UDB CDC Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Using DTLUCUDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

CCATDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

DBINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

DUMPDIAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

LOGPRT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

SETDEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

SNAPSHOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

SNAPUPDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

SQUISH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

UPDTDRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Gathering Diagnostic Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Chapter 11: DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities. . . . . . . . . . . . 59Creating the PowerExchange Log Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Running DTLULCAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Running DTLULOGC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Manually Manipulating the Log Catalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Log Catalog Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 12: DTLURDMO - Data Map Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Windows and UNIX Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

v Table of Contents

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

DTLURDMO Definition File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

MVS DTLURDMO Job Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66


MVS Example JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

i5/OS Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67


Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

DTLURDMO Definition File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

User Input Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

dm_copy Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

reg_copy Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

xm_copy Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Example Definition File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

DTLURDMO Example Output from the Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Chapter 13: DTLUTSK - Task Control Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Linux, UNIX, and Windows Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

MVS DTLUTSK Job Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

MVS Example JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

MVS Command Line Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

MVS LISTTASK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

MVS STOPTASK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

MVS LISTLOCATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

MVS LISTALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

MVS FREEALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Running the Utility in the PowerExchange Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Security Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

AS400 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Signon.txt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Chapter 14: EDMXLUTL - Event Marker Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Creating an Event Marker in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

JCL Statements for Creating a Special Event Marker. . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

EVENT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Syntax for the EVENT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Keyword Sets for the BASEEDM Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

MARK Keyword Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

NOTIFY Keyword Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Control Statements for the Event-Marker Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

vi Table of Contents

Chapter 15: EDMLUCTR - Log Scan and Print Utility . . . . . . . . . . . . . . . . . . . . . . . . . 89Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89



-SEL Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

-MASK Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Running EDMLUCTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Chapter 16: HOSTENT - TCP/IP Address Reporter Utility . . . . . . . . . . . . . . . . . . . . . 95Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Running HOSTENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Linux and UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

z/OS and OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Resolver Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

HOSTENT Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

i5/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Linux and UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

z/OS and OS/390. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Table of Contents vii

viii Table of Contents

Preface

This manual describes a collection of utility programs that are designed to aid maintenance of your PowerExchange installation.

This manual applies to the following PowerExchange products:

♦ PowerExchange for Adabas®

♦ PowerExchange for CA Datacom®

♦ PowerExchange for CA IDMS™

♦ PowerExchange for DB2® for i5/OS®

♦ PowerExchange for DB2 for Linux®, UNIX®, and Windows®

♦ PowerExchange for DB2 for z/OS®

♦ PowerExchange for IMS™

♦ PowerExchange for Oracle®

♦ PowerExchange for SQL Server®

♦ PowerExchange for VSAM

Informatica Resources

Informatica Customer PortalAs an Informatica customer, you can access the Informatica Customer Portal site at http://my.informatica.com. The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica Knowledge Base, Informatica Documentation Center, and access to the Informatica user community.

Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email at [email protected]. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments.

ix

Informatica Web SiteYou can access the Informatica corporate web site at http://www.informatica.com. The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services.

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://my.informatica.com. Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips.

Informatica Global Customer SupportThere are many ways to access Informatica Global Customer Support. You can contact a Customer Support Center through telephone, email, or the WebSupport Service.

Use the following email addresses to contact Informatica Global Customer Support:

♦ [email protected] for technical inquiries

♦ [email protected] for general customer service requests

WebSupport requires a user name and password. You can request a user name and password at http://my.informatica.com.

Use the following telephone numbers to contact Informatica Global Customer Support:

North America / South America Europe / Middle East / Africa Asia / Australia

Informatica Corporation Headquarters100 Cardinal WayRedwood City, California 94063United States

Toll Free +1 877 463 2435

Standard RateBrazil: +55 11 3523 7761 Mexico: +52 55 1168 9763 United States: +1 650 385 5800

Informatica Software Ltd.6 Waltham ParkWaltham Road, White WalthamMaidenhead, BerkshireSL6 3TNUnited Kingdom

Toll Free 00 800 4632 4357

Standard RateBelgium: +32 15 281 702France: +33 1 41 38 92 26Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511 445

Informatica Business Solutions Pvt. Ltd.Diamond DistrictTower B, 3rd Floor150 Airport RoadBangalore 560 008India

Toll Free Australia: 1 800 151 830Singapore: 001 800 4632 4357

Standard RateIndia: +91 80 4112 5738

x Preface

C H A P T E R 1

PowerExchange Utilities Overview

This guide is intended for PowerExchange administrators who will need to run one or more of the utilities to manage their PowerExchange installations. Each chapter provides some or all of the following reference information for a specific utility:

♦ The tasks that you can perform with the utility

♦ Any prerequisites to running the utility

♦ The platforms on which the utility can run

♦ The syntax of the utility commands and parameters

♦ Detailed descriptions of the required and optional parameters

♦ How to issue the utility control statements on the various platforms

♦ Examples of utility syntax by platform or task or both

PowerExchange UtilitiesPowerExchange includes the following utilities to help you manage your PowerExchange installation:

♦ DTLCCADW - Adabas PCAT file utility. Use DTLCCADW to manipulate the contents of the PCAT file.

♦ DTLCUIML - IMS log marker utility. Use DTLCUIML to define a marker for the IMS log-based ECCR in the IMS Log Stream.

♦ DTLINFO - Build information utility. Use DTLINFO to display the version, release, and build level for PowerExchange.

♦ DTLREXE - Remote program utility. Use DTLREXE to run programs on remote platforms.

♦ DTLUAPPL - Restart token utility. Use DTLUAPPL to update the Change Data Extraction Repository (CDEP) file with specified applications and capture registrations.

♦ DTLUCBRG - Batch registration utility. Use the DTLUCBRG utility to add or modify capture registrations and extraction maps.

♦ DTLUCDEP - CDEP utility. Use DTLUCDEP to modify or print out the contents of the CDEP file.

♦ DTLUCSR2 - IDMS SR2 and SR3 records utility. Use DTLUCSR2 to determine the position of SR3 records.

♦ DTLUCUDB - DB2 CDC utility. Use DTLUCUDB to create a catalog snapshot to initialize the capture catalog table and to generate diagnostic information.

♦ DTLULCAT and DTLULOGC - IDMS log catalog utilities. Use DTLULCAT and DTLULOGC to populate the log catalog with information about the logs to process.

♦ DTLURDMO - Data map utility. Use DTLURDMO to migrate data maps, capture registrations and capture extraction map definitions, from one environment or location to another.

♦ DTLUTSK - Task control utility. Use DTLUTSK to list active tasks and stop them if required.

1

♦ EDMLUCTR - Scan and print utility for PowerExchange logs. Use EDMLUCTR to display information about the changes that are captured in the logs of the PowerExchange Logger, or to diagnose problems related to capturing changes.

♦ EDMXLUTL - Event marker utility. UseEDMXLUTLto create an event marker in your PowerExchange Logger.

PowerExchange Utilities by PlatformTable 1-1 indicates the platforms on which each utility can run. If the utility is available only for specific databases, those databases are indicated.

Table 1-1. PowerExchange Utilities by Platform

Syntax ConventionsThis guide uses the following syntax conventions for the utility commands and parameters:

♦ All UPPERCASE letters are used for command names and for most parameter names, regardless of the type of platform. However, positional parameters for which you enter a specific value are shown in lowercase and italics, for example, instance.

♦ Square brackets [ ] indicate optional parameters. You can consider any parameters without these brackets to be required.

♦ A vertical bar | separates alternative options of which one can be entered for a parameter.

♦ Underlining indicates the default option for a parameter, if available.

♦ Italics indicate a variable or positional parameter for which the value varies.

Utility Linux UNIX Windows MVS i5/OS

DTLCCADW Yes, for Adabas only

DTLCUIML Yes, for IMS only

DTLINFO Yes Yes Yes Yes Yes

DTLREXE Yes Yes Yes Yes Yes

DTLUAPPL Yes Yes Yes Yes Yes

DTLUCBRG Yes Yes Yes Yes Yes

DTLUCDEP Yes Yes Yes Yes Yes

DTLUCSR2 Yes, for IDMS Log-Based CDC only

DTLUCUDB Yes, for DB2 only

Yes, for DB2 only

Yes, for DB2 only

DTLULCAT and DTLULOGC

Yes, for IDMS Log-Based CDC only

DTLURDMO Yes Yes Yes Yes Yes

DTLUTSK Yes Yes Yes Yes Yes

EDMLUCTR Yes

EDMXLUTL Yes

2 Chapter 1: PowerExchange Utilities Overview

Sample JCLWhen you install PowerExchange on z/OS, you install sample JCL to the HLQ.RUNLIB library.

If you chose to select the Delete Install Members option on the Select Additional Parameters tab of the MVS Installation Assistant, the installation process moves the sample JCL to the HLQ.DTLEXPL library.

3

4 Chapter 1: PowerExchange Utilities Overview

C H A P T E R 2

DTLCCADW - Adabas PCAT Utility

This chapter includes the following topics:

♦ Purpose, 5

♦ Utility Functions, 5

PurposeThe PCAT utility program, DTLCCADW, is used by the Adabas ECCR process to manipulate the contents of the PCAT file. The PCAT utility is controlled by settings of the parameters passed via the PARM= on the EXEC statement. There are examples of the JCL required for each function in the PowerExchange DTLEXPL library with names DTLCCADx, where x corresponds to the parameter value.

Typically, these functions are used only internally by PowerExchange. However, there may be times when manual overrides are desired, which are described below. When in doubt about usage, contact Informatica Global Customer Support.

Utility Functions♦ P (Populate PCAT control file)

♦ R (Report on PCAT control file)

♦ I (Insert)

♦ D (Delete)

♦ L (Reset latest sequence number)

♦ V (Rebuild the PCAT control file)

♦ A (Add)

♦ S (Submit ADASEL)

♦ T (Submit ET record extraction)

♦ E (ET/BT record extraction)

P (Populate PCAT Control File)Example job DTLCCADP - no other parameters are required.

5

This function may be used after the VSAM Control File has been initially established with its 999999999 control record, to pre-populate the PCAT file with previously-created PLOG data set names. By default, when the Adabas PowerExchange ECCR is started, only the most recent archived PLOG will be recognized. So, if there is a need to collect older captured changes, this is the function to use. The list of data set names is input via DDCARD DTLCCADF either directly as SYSIN or a file of 80-byte card images. It is the user's responsibility to obtain those PLOG data set names. The 999999999 PCAT control record is then updated with the highest sequence number added. Note: this function must ONLY be used after initializing the control file, not after normal operation has begun.

R (Report on PCAT Control File)Example job DTLCCADR - optionally, a second parameter of control file sequence number.

Prints to SYSOUT with a DD Name of DTLCCRPT. The optional second parameter allows you to specify a file sequence number from where the report will commence. If no second parameter is specified then the whole file is printed to SYSOUT.

Note: The following functions may be of use in case of operational PLOG difficulties, not related to the Adabas PowerExchange Change processing. For instance, if the PLOG files get out of sequence operationally, these functions will ensure that the PCAT can be reset to correct data set name sequence, as well.

I (Insert)Example job DTLCCADI - requires two further parameters.

The first is a PCAT control file sequence number, which must not already exist. The second is the data set name of a PLOG to be inserted. Note - DTLCCADW does NOT check that the PLOG is in the correct chronological sequence - it is the user's responsibility to ensure this.

D (Delete)Example job DTLCCADD - requires a second parameter of control file sequence number.

DTLCCADW reads the PCAT control record and deletes it. If you delete the record which was the latest to be added, you must immediately run the L function (see below) to reset the latest key value in the 999999999 control record.

L (Reset Latest Sequence Number)Example job DTLCCADL - no other parameters are required.

This function re-populates the "latest sequence number added" field in the 999999999 PCAT control record. The only circumstance that this function would be necessary is if the user deletes the record which is the latest added, which would invalidate the '999999999' control record.

V (Rebuild the PCAT Control File)Example job DTLCCADV - no other parameters are required.

This function can be used to delete and re-build the overall PCAT control record '999999999'.

Note: The following functions should be used only under the direction of Informatica Global Customer Support.

A (Add)Example job DTLCCADA - no other parameters required.

Takes the PLOG specified by the data set name in the DDCARD DTLCCPLG and creates an entry in the PCAT file, taking the highest sequence number so far added and adding 100 to it (gaps are left in the sequence in case older PLOGs need to be inserted into the sequence later). This function is automatically invoked during

6 Chapter 2: DTLCCADW - Adabas PCAT Utility

the PLOG flip in the JCL executing the PLCOPY function and so should not be necessary to invoke manually, in normal operation.

S (Submit ADASEL)Example job DTLCCADS - requires a second parameter of PCAT file sequence number.

DTLCCADW reads the PCAT control record specified by the sequence number and constructs an ADASEL job for the PLOG data set name recorded in the control record. It submits the job which runs the ADASEL and creates an output file, the data set name of which is recorded in the control record. This function is automatically invoked by the ECCR and so should not be necessary to invoke manually in normal operation.

T (Submit ET Record Extraction)Example job DTLCCADT - requires a second parameter of PCAT file sequence number.

DTLCCADW reads the PCAT control record specified by the sequence number and constructs another DTLCCADW job for the PLOG recorded in the control record, building a data set name for the output ET file using date and time parameters. It submits the job which reads the PLOG specified in the control record and creates an output file of ET/BT records, the data set name of this file then being recorded in the control record. This function is normally invoked by the ECCR and so should not be necessary to invoke manually in normal operation.

E (ET/BT Record Extraction)Example job DTLCCADE - requires a second parameter of PCAT file sequence number.

This function is in fact the same as the job which is dynamically created and submitted by the T function above - the difference being that the user has to explicitly define the data set name of the output ET/BT file in the JCL, DDNAME DTLCCETL, and the name of the archived PLOG being processed in DDNAME DTLCCPLG. The ECCR normally controls this operation and this function is only provided in case of difficulties which might require manual intervention.

Utility Functions 7

8 Chapter 2: DTLCCADW - Adabas PCAT Utility

C H A P T E R 3

DTLCUIML - IMS Log Marker Utility

This chapter includes the following topic:

♦ DTLCUIML, 9

DTLCUIMLThis utility is used to define a marker for the IMS log-based ECCR in the IMS Log Stream. Once the IMS log-based ECCR encounters one of the markers, it triggers a message in the PowerExchange Logger which stipulates a Restart and Sequence Token for the affected Registration Tags.

These Tokens can then be used as input for the Application Maintenance Utility (DTLUAPPL) to define the start point for an extraction.

There is no limit or restriction on the number of markers being set in the IMS Log Stream. The IMS Log Record ID chosen has to be unique for the individual installation, and the number needs to be part of the input parameters for the IMS log-based ECCR.

This utility is used to write user-defined records to the IMS log.

The parameters controlling the utility are specified in the SYSIN file in the JCL.

The utility runs as a standard IMS application program. There is no need to provide a specific PSB. The utility can use any PSB as long as the first PCB in the PSB is an IOPCB. The utility uses the IMS LOG Call to write IMS log records.

This utility has to run as an IMS BMP job. This ensures that the IMS Log record is written into the IMS logstream and that the associated log is read by the IMS log-based Collector. In an IMS DCI situation the DTLUAPPL utility has to be used to establish an extraction point for the changed data.

File SYSPRINT reports validation of the input parameters and progress in writing to the IMS log.

File DFSSTAT reports IMS activity.

Sample JCL is supplied in member IMSLOGW.

Defining input parameters in SYSIN.

Each SYSIN record contains 3 parameters:

♦ DBDNAME. IMS DBD name.

♦ DBID. IMS instance (Recon Identifier).

♦ RECID. A value in (uppercase) hex which must lie between A0 and FF. It defines the log record type for the User-defined IMS log record, so it should be different to any other user-defined values which the site is using.

Leading spaces are ignored. Records are ignored where the first non-space characters are /* so can be used as comments.

9

Example:

//SYSIN DD * DBDNAME=DTLD004,DBID=IMS7,RECID=A0 DBDNAME=DTLD006,DBID=IMS7,RECID=A0 DBDNAME=DTLD007,DBID=IMS7,RECID=A0/*

SYSPRINT: Control ReportThe control report shows the following information:

♦ Date and time when the program started. This time is also used on each user-defined log record written to the IMS log.

♦ Validation messages for the SYSIN records. If any record is invalid, the run aborts and no records are written to the IMS log.

♦ Progress messages as the records are written to the IMS log.

Example:

2002-10-15 14:06:14 DTLCUIML REPORT=====================================================================.Input Records Read------------------ DBDNAME=DTLD004,DBID=IMS1,RECID=A0 DBDNAME=DTLD006,DBID=IMS1,RECID=A0 DBDNAME=DTLD007,DBID=IMS1,RECID=A03 record(s) validated from the input file.LOG record processing begins-----------------------------Processing dbname=DTLD004 dbid=IMS1 recid=A0 timestamp=20021015140614Processing dbname=DTLD006 dbid=IMS7 recid=A0 timestamp=20021015140614Processing dbname=DTLD007 dbid=IMS7 recid=A0 timestamp=20021015140614.Number of LOG calls = 3.Run completed successfully

DFSSTAT: IMS Activity ReportCounts for SYS LOG CALLS will match the number of records processed from file SYSIN. All other counts will be zero.

Example:

//DFSSTAT STATISTICS FOR: JOB=UIMLRUN STEP=G---------------------------------------------- *** PST ACCOUNTING STATISTICS ***SYS LOG CALLS 3

User-Defined Log RecordsEach user-defined log record contains 35 bytes of user data. The actual IMS Log record adds the standard IMS suffix to this data.

Field Start Length Type Description

Length 1 2 unsigned binary Length of user-defined log record = 35 bytes.

Zeros 3 2 unsigned binary Always hex '0000'.

Recid 5 1 char Record ID supplied in SYSIN parameters, such as hex 'A0'.

Dbname 6 8 char IMS DBNAME.

Dbid 14 8 char IMS instance (Recon Identifier).

Timestamp 22 14 char Time when program DTLCUIML ran.

10 Chapter 3: DTLCUIML - IMS Log Marker Utility

C H A P T E R 4

DTLINFO - Release Information Utility


♦ Purpose, 11

♦ Platforms, 11

♦ Control Statement Syntax, 12

♦ Control Statement Parameters, 12

♦ Running DTLINFO, 12

♦ Examples, 13

PurposeUse the DTLINFO utility to perform the following functions:

♦ Display the version, release, and release level for PowerExchange or for a specific PowerExchange module.

♦ Verify the installation of the product, a service pack, or a hot fix. For example, use the utility to determine the maintenance level of your PowerExchange software at the request of Informatica Global Customer Support.

PlatformsThe DTLINFO utility can run on the following platforms:

♦ i5/OS

♦ Linux and UNIX

♦ Windows

♦ z/OS and OS/390

11

Control Statement SyntaxDTLINFO [module_name]

To view the release information for the PowerExchange product do not specify the module_name parameter.

To view the release information for a specific PowerExchange module, use the module_name parameter. The module name is the name of any program included in your PowerExchange installation.

Control Statement ParametersThe DTLINFO utility has the following optional parameter:

module_name

Displays the version, release, and release level for a specific PowerExchange module, such as DTLREXE.

Running DTLINFOThis section describes how to run the DTLINFO utility.

i5/OSTo run the DTLINFO utility:

To view release information for PowerExchange, enter:

CALL PGM(dtllib/DTLINFO)

or

To view release information for a PowerExchange module, enter:

CALL PGM(dtllib/DTLINFO) parm ('module_name')

Linux, UNIX, and WindowsTo run the DTLINFO utility:

1. Navigate to the Informatica PowerExchange directory.

2. Enter enter the dtlinfo statement in one of the following ways:

To view release information for PowerExchange, enter:

dtlinfo

To view release information for a specific PowerExchange module, enter:

dtlinfo module_name

z/OS and OS/390The JCL for the DTLINFO utility is located in hlq.RUNLIB(DTLINFO), where hlq is the high-level qualifier used for installing PowerExchange. The DTLINFO program is located in hlq.LOADLIB(DTLINFO)

You can incorporate the DTLINFO job step into a batch job, or add a job card and run the DTLINFO job separately.

12 Chapter 4: DTLINFO - Release Information Utility

To run the DTLINFO utility on an z/OS or OS/390 system, define the JCL EXEC statement for the DTLINFO program. To view release information for the PowerExchange product, do not specify a PARM value or SYSIN DD as shown in the following syntax:

//BLDSTEP EXEC PGM=DTLINFO//STEPLIB DD DISP=SHR,DSN=hlq.LOADLIB//SYSPRINT DD SYSOUT=*

To view release information for a specific PowerExchange module, specify a module name as the PARM value. Also, supply the library and member name for the module by using the SYSIN DD as shown in the following sample:

//BLDSTEP EXEC PGM=DTLINFO,PARM=('DTLREXE')//STEPLIB DD DISP=SHR,DSN=hlq.LOADLIB//SYSIN DD DISP=SHR,DSN=hlq.LOADLIB(DTLREXE)//SYSPRINT DD SYSOUT=*

EXEC PGM=DTLINFOInvokes the utility.

STEPLIB DDDefines the PowerExchange LOAD library that contains the utility.

SYSPRINT DDDefines the print location for the report.

To run the DTLINFO utility:

Submit the DTLINFO job.

Examples

i5/OS

Example 1The following command displays the release information for PowerExchange:

CALL DTLINFO

The resulting output is:

DTLINFO Latest Version:Copyright: Informatica Corporation. yyyy-yyyySegment#Revision :<//pwx/prod/vnnn_spn/source/dtlinfod/dtlinfod.c #n >Build :<vnnn><Month dd yyyy hh:mm:ss>

Example 2The following command displays the release information for the PowerExchange module DTLREXE:

CALL DTLINFO DTLREXE


DTLINFO Embedded Version History:Copyright: Informatica Corporation. yyyy-yyyySegment#Revision :<//pwx/prod/vnnn_spn/source/dtlinfod/dtlinfod.c #n >Build :<vnnn><Month dd yyyy hh:mm:ss>

DTLINFO AS400 Module Segments For DTLREXESegment#Revision :<//pwx/prod/vnnn_spn/source/dtlrexe/dtlrexe.c #n >Built :<Month dd yyyy hh:mm:ss>

Examples 13

Linux, UNIX, and Windows

Example 1The following command displays the release information for PowerExchange:

dtlinfo

Example 2The following command displays the release information for the PowerExchange module DTLREXE:

dtlinfo dtlrexe.exe

z/OS and OS/390

Example 1The following JCL EXEC statement does not specify a PARM value or SYSIN DD for the DTLINFO program:

//BLDSTEP EXEC PGM=DTLINFO//STEPLIB DD DISP=SHR,DSN=hlq.LOADLIB//SYSPRINT DD SYSOUT=*

Example 2The following JCL EXEC statement specifies the PowerExchange module DTLREXE as the PARM value. Also, the following SYSIN DD provides the library and member name for the module:

//BLDSTEP EXEC PGM=DTLINFO,PARM=('DLTREXE')//STEPLIB DD DISP=SHR,DSN=hlq.LOADLIB//SYSIN DD DISP=SHR,DSN=hlq.LOADLIB(DLTREXE)//SYSPRINT DD SYSOUT=*

14 Chapter 4: DTLINFO - Release Information Utility

C H A P T E R 5

DTLREXE - Remote Execution Utility


♦ Purpose, 15

♦ Platforms, 15



♦ Running DTLREXE, 18

♦ Usage Notes, 20

♦ Examples, 20

PurposeUse the DTLREXE utility to perform the following tasks:

♦ Ping a remote PowerExchange Listener.

♦ Submit a remote job.

PlatformsThe DTLREXE utility can run on the following platforms:

♦ i5/OS

♦ UNIX and Linux

♦ Windows

♦ z/OS and OS/390

15

Control Statement SyntaxUse the following syntax for the DTLREXE utility control statements:

prog=pingloc=location[uid=userid][pwd/epwd=password]

prog=submit loc=<location> [uid=<userid>] [pwd/epwd=<password>] [fn="your jcl"] [mode=(job/task,wait/nowait/timed)] [time=<time_in_seconds>] [submittimeout=<timeout_in_seconds>] [output=output.file] [result=result.file]

Control Statement ParametersDTLREXE has the following statements:

♦ PING

♦ SUBMIT

PING StatementUse DTLREXE PING to prove basic connectivity to a PowerExchange Listener. You must configure a node in the DBMover configuration file on the machine from which you issue the DTLREXE PING. For more information about the NODE configuration file parameter, see the PowerExchange Reference Manual.

PING has the following parameters:

locOptional. Location as defined in the dbmover.cfg as a node giving the address of the PowerExchange Listener.

progRequired. Set to PING.

pwd/epwdOptional. Password for target platform

♦ pwd. Password for target platform in clear text.

♦ epwd. Encrypted password. Use the PowerExchange Navigator to generate an encrypted password. For more information, see the PowerExchange Navigator User Guide.

In pwd, non alphanumeric characters must be enclosed in quotes (“”). Therefore, a password cannot have an embedded double quote.

uidOptional. User ID for the target platform. For more information about the SECURITY parameter, see the PowerExchange Reference Manual.

SUBMIT StatementUse DTLREXE SUBMIT to submit an MVS job to a remote platform or server.

16 Chapter 5: DTLREXE - Remote Execution Utility

Alternatively, you can supply the cs parameter to point to a parameter file that contains all the required parameters.

dtlrexe cs=<parameterFile>

SUBMIT has the following parameters:

fnOptional. The name of the file containing the JCL to be submitted including the job name. Use the following format:

fn=”dtlusr.jcl(yourjob)”

When invoked from Windows, the format is: fn=\”dtlusr.jcl(yourjob)\”

locLocation as defined in the dbmover.cfg as a node giving the address of the PowerExchange Listener.

modeOptional. Specifies the submit mode. Use the following format:

mode=(job¦task,wait¦nowait¦timed)

♦ job. Submitted job

♦ task. Started task. Not currently supported.

♦ wait. Synchronous. Report result at end and wait for completion.

♦ nowait. Asynchronous. Submit job but do not wait to report completion.

♦ timed. Synchronous. Waits for a length of time as specified by the time parameter.

outputOptional. The file name containing the results from the job. se the following format:

output=dtlusr.output.

If the output is a PDS member the same format requirements are in place as for the fn parameter.

progRequired. Set to SUBMIT,

pwd/epwdOptional. Password for target platform

♦ pwd. Password for target platform in plain text.

♦ epwd. Encrypted password. Use the PowerExchange Navigator to generate an encrypted password. For more information, see the PowerExchange Navigator User Guide.

In pwd, non alphanumeric characters must be enclosed in quotes (“”). Therefore, a password cannot have an embedded double quote.

resultOptional. The file in which the results from the job are written on the client side platform where DTLREXE is run.

The file specification have to be suitable for the relevant platform.

If the output is a PDS member the same format requirements are in place as for the fn parameter.

submittimeoutOptional. This is the time, in seconds, to allow for the submitted job to actually start running.

timeOptional. This is the wait period, in seconds, for the job to return. This time starts when the job is submitted.

uidOptional. User ID for the target platform. For more information, see the PowerExchange Reference Manual.

Control Statement Parameters 17

Running DTLREXEThis section describes how to run the DTLREXE utility.

i5/OSTo run the DTLREXE utility:

Enter the following command:

CALL PGM(DTLREXE) PARM('prog=submit loc=mvs fn=dtlusr.load.jcl mode=(job,wait) output=dtlusr.output, result=dtlusr.result’)

Linux and UNIXTo run the DTLREXE utility using a PDS member:


dtlrexe prog=submit loc=remlist fn=\"dtlusr.jcl.cntl'('db2load')'\", mode='('job,wait')', output=dtlusr.output, result=/usr/pwx/output.txt

or

dtlrexe prog=submit cs=/usr/pwx/MyParameterFile.txt

To run the DTLREXE utility using a sequential MVS data set:


The format for UNIX using a sequential MVS data set is:

dtlrexe prog=submit loc=remlist fn=dtlusr.load.jcl, mode='('job,wait')', output=dtlusr.output, result=/usr/pwx/output.txt

or

dtlrexe prog=submit loc=remlist fn="dtlusr.load.jcl", mode='('job,wait')', output=dtlusr.output, result=/usr/pwx/output.txt

WindowsTo run the DTLREXE utility:


dtlrexe prog=submit loc=remlist fn=\”dtlusr.jcl.cntl(db2load)\” mode=(job,nowait) output=dtlusr.output result=c:\submit\output\output.txt uid=user01 pwd=pass01

or

dtlrexe prog=submit cs=c:\PowerExchange\MyParameterFile.txt

DTLREXE PROG=SUBMIT on z/OS and OS/390Edit the following DTLREXE job JCL before you submit:

1. The following two lines must be the first step of the job:

//START EXEC PGM=DTLNTS,PARM='"%STRTJOB"'//STEPLIB DD DSN=&HLQ..LOADLIB,DISP=SHR

2. Add the JCL of the job.

//STEP1 EXEC PGM=DTLREXE,// PARM=('CS=DD:INCMD'),// REGION=0M,TIME=NOLIMIT

//INCMD DD *


LOC=NODE1 PROG=SUBMIT FN="DTLUSR.JCL(MYJOB)"MODE=(JOB,WAIT) OUTPUT=DTLUSR.DB2LOAD.SYSPRINTRESULT="DTLUSR.JCLRESTXT)"

3. After the final step, you must add the following lines:

// IF ((RC > 4) | (ABEND=TRUE)) THEN//*//ENDERR EXEC PGM=DTLNTS,// PARM='"%ENDJOB" C 16'//STEPLIB DD DSN=&HLQ..LOADLIB,DISP=SHR//SYSPRINT DD SYSOUT=*//*// ELSE//*//ENDOK EXEC PGM=DTLNTS,// PARM='"%ENDJOB"'//STEPLIB DD DSN=&HLQ..LOADLIB,DISP=SHR//SYSPRINT DD SYSOUT=*// ENDIF

JOBInitiates the job.

EXEC PGM=DTLREXEInvokes the utility.



To run the DTLREXE utility:

1. Verify the JCL.

2. Submit the DTLREXE job.

DTLREXE PROG=PING on z/OS and OS/390You must edit the job that you intend to submit using DTLREXE as follows:

//STEP1 EXEC PGM=DTLREXE,// PARM='loc=node1 prog=ping'//STEPLIB DD DSN=CEE.SCEERUN,// DISP=SHR// DD DSN=&HLQ..LOADLIB,// DISP=(SHR)//SYSPRINT DD SYSOUT=*


EXEC PGM=DTLREXEInvokes the utility.



To run the DTLREXE utility:

1. Enter the location of the PowerExchange Listener in the loc parameter.

2. Submit the DTLREXE job.

Running DTLREXE 19

Usage NotesConsider the following points before using the DTLREXE utility:

♦ DTLREXE submits the job on the host named in the loc parameter.

♦ If the mode is (job,nowait), the output and result data sets are of no interest.

♦ If the mode is (job,wait) or (job,timed), PowerExchange waits for the job to complete and reads the return code. The parameters are required to ensure that the job has completed and the output data set is available.

♦ Substitution is performed on the job for the %STRTJOB and %STRTJOB tokens. The following table describes the %STRTJOB and %STRTJOB tokens:

♦ To print out help on the utility, run DTLREXE without any parameters. The following help text is generated:

Usage: dtlrexe parmsparms:loc= node to communicate with [parms= parameters for program] prog= program to run remotely [pwd= password for user] [uid= remote userid]prog=submit: [fn= filename for jcl] [mode= (job/task,wait options)] [time= wait time][result=result data set on client]

Examples

MVS ExampleTo launch DTLREXE from an MVS job you must use PowerExchange command set syntax as follows:

//STEP1 EXEC PGM=DTLREXE,// PARM=('CS=DD:INCMD'),// REGION=0M,TIME=NOLIMIT

An inline DD is specified in the JCL above. You can change this to an external member.

The specified inline or external DD contains the parameters of the DTLREXE command. The following JCL defines the inline DD:

//INCMD DD *LOC=NODE1 PROG=SUBMIT FN="DTLUSR.JCL(MYJOB)"

Parameter Description

%STRTJOB The name token for the first step in the JCL of the job that is to be submitted. - If the mode parameter is set to (job,wait/timed), %STRTJOB is substituted with a

name token generated by the submitter. - If the mode parameter is not set to (job,wait/timed), %STRTJOB is set to

DONOTRETURNTOKEN.

%ENDJOB The name token for the last step in the JCL of the job that is to be submitted. The wait/timed processing retrieves these values to determine if the job has started, is running, or has finished. The %ENDJOB steps have to be included manually and are shown in the sample JCL. If the submitted job fails with a return code greater than four, rc=16 is returned back to DTLREXE on the client.


MODE=(JOB,WAIT) OUTPUT=DTLUSR.DB2LOAD.SYSPRINTRESULT="DTLUSR.JCLRESTXT)"

The following JCL specifies the external member:

//INCMD DD DSN=HLQ..RUNLIB(MYCS)

The member MYCS has the following contents:

LOC=NODE1 PROG=SUBMIT FN="DTLUSR.JCL(MYJOB)"MODE=(JOB,WAIT) OUTPUT=DTLUSR.DB2LOAD.SYSPRINTRESULT="DTLUSR.JCLRESTXT)"

Example JCL//DTLREXE JOB 'DTLREX',MSGLEVEL=(1,1),MSGCLASS=X,CLASS=A,// NOTIFY=&SYSUID//*// SET HLQ=DTLUSR.V850//*//STEP1 EXEC PGM=DTLREXE,REGION=24M,// PARM=('CS=DD:INCMD')//STEPLIB DD DSN=CEE.SCEERUN,DISP=SHR// DD DSN=&HLQ..LOADLIB,DISP=SHR//DTLCFG DD DSN=&HLQ..RUNLIB(DBMOVER),DISP=SHR//DTLKEY DD DSN=&HLQ..RUNLIB(LICENSE),DISP=SHR//DTLMSG DD DSN=&HLQ..DTLMSG,DISP=SHR//DTLLOG DD DSN=&HLQ..LOG,DISP=SHR//SYSUDUMP DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSPRINT DD SYSOUT=*//CEEDUMP DD SYSOUT=*//SYSIN DD *//* EXECUTE THE PROCEDURE//*//DTLLSTN EXEC DBMOVE//INCMD DD * LOC=NODE1 PROG=SUBMIT FN="DTLUSR.JCL(MYJOB)" MODE=(JOB,WAIT) OUTPUT=DTLUSR.DB2LOAD.SYSPRINT RESULT="DTLUSR.JCL(RESTXT)"

Output Data SetThe output= parameter indicates a data set which should contain the results of the submitted job.

When the job completes, the output is read and transferred back to the client where it is written to a file specified by the result= parameter.

The format of the output is:

timestamp|jobid|text

Example Output Data SetAn example of the output is:

20060223172636000000|JOB03370|1DSNU000I DSNUGUTC - OUTPUT START FOR UTILITY, UTILID = DB2LDJCL |20060223172636000000|JOB03370|0DSNU050I DSNUGUTC - LOAD DATA RESUME NO REPLACE LOG YES|20060223172636000000|JOB03370| DSNU650I -DSN7 DSNURWI - INTO TABLE DTLUSR.T3|20060223172636000000|JOB03370| DSNU650I -DSN7 DSNURWI - (COL1 POSITION(3) CHAR(100) NULLIF(1='Y'),|20060223172636000000|JOB03370| DSNU650I -DSN7 DSNURWI - COL2 POSITION(*) CHAR(100) NULLIF(2='Y'))|20060223172636000000|JOB03370| DSNU350I -DSN7 DSNURRST - EXISTING RECORDS DELETED FROM TABLESPACE|20060223172636000000|JOB03370| DSNU304I -DSN7 DSNURWT - (RE)LOAD PHASE STATISTICS - NUMBER OF RECORDS=3 FOR TABLE DTLUSR.T3 |20060223172636000000|JOB03370| DSNU302I DSNURILD - (RE)LOAD PHASE STATISTICS - NUMBER OF INPUT RECORDS PROCESSED=3 |20060223172636000000|JOB03370| DSNU300I DSNURILD - (RE)LOAD PHASE COMPLETE, ELAPSED TIME=00:00:08|20060223172636000000|JOB03370| DSNU010I DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN CODE=0 |

Examples 21

C H A P T E R 6

DTLUAPPL - Restart Token Utility


♦ Purpose, 23

♦ Platforms, 24



♦ Running DTLUAPPL, 27

♦ z/OS and OS/390, 28

♦ Examples, 29

♦ Purpose

The DTLUAPPL utility updates the Change Data Extraction Repository (CDEP) file with the applications and capture registrations specified. Use DTLUAPPL to perform the following tasks:

♦ Generating restart tokens for CDC sessions.

♦ Printing restart tokens and application name entries.

♦ Adding or modifying application name entries.

DTLUAPPL generates restart tokens for all PowerExchange change data capture sources. PowerExchange uses restart tokens to determine where in the change stream to begin extracting changed data. Restart tokens are comprised of a sequence token and a restart token. The length of the restart tokens varies based upon the data source.

When you use PowerExchange Client for PowerCenter connections to extract changed data, the application entries in the CDEP file are not used to store restart tokens or restart token history. After materializing the target tables and before capturing any changed data, run DTLUAPPL to generate the starting restart tokens for extraction. Update the PowerExchange Client for PowerCenter restart token file with the generated restart tokens.

If you are extracting changed data using ODBC, PowerExchange maintains the restart tokens in the CDEP file. Use DTLUAPPL to create the application entry with the starting restart tokens. PowerExchange creates an application entry on the first extraction if one does not exist. Using DTLUAPPL immediately after materialization creates a restart point before any data has been captured or applied. After the initial extraction, you can use DTLUAPPL to reset the extraction start point for any application. You can also reset the extraction start point using the PowerExchange Navigator.

23

PlatformsThe DTLUAPPL utility can run on the following platforms:

♦ i5/OS

♦ UNIX and Linux

♦ Windows

♦ z/OS and OS/390

Control Statement SyntaxDTLUAPPL allows you to specify user and password information. Only PowerExchange encyrpted passwords are allowed. Specifying user and password information is necessary when you use DTLUAPPL to:

♦ Generate restart tokens for capture registrations for Oracle, Microsoft SQL Server, and DB2 for i5/OS.

♦ Generate restart tokens when PowerExchange security is active on MVS or i5/OS (AS/400).

The connection statement also allows you to specify a CAPI_CONNECTION override. PowerExchange allows specification of numerous CAPI_CONNECTION statements in the configuration file but only one statement can be designated the default connection. Since the default CAPI_CONNECTION statement may not correct for the task being performed, DTLUAPPL allows you to override the default connection when generating restart tokens.

When using the connection statement, UID and EPWD are required. The syntax is:

UID user EPWD epwd CONN_OVR capi_connection

DTLUAPPL has the following parameters:

CONN_OVRSpecifies the CAPI_CONNECTION name to use when running the utility. DTLUAPPL uses the default connection if this is not specified.

EPWDSpecifies the encrypted password for the user name. Generate encrypted passwords using the PowerExchange Navigator.

UIDSpecifies the user name.

Control Statement Parameters

Review the parameter descriptions to determine which parameters to use in the DTLUAPPL control statements.

Adding or Modifying Application EntriesDTLUAPPL adds and modifies application entries as well as capture registration entries in an application entry. You can modify an existing application to add a new capture registration.

Restart tokens can be either be provided or generated by the utility. Use the RSTTKN GENERATE option at the application level or the GENERATE option at the registration level to generate restart tokens.

If you use PowerExchange Client for PowerCenter connections to extract changed data, use DTLUAPPL to generate restart tokens. Any active capture registration can be used. Do not use the application name specified in the PowerExchange Client for PowerCenter application connection when generating restart tokens. PowerExchange Client for PowerCenter maintains the restart tokens in the state table in the relational database

24 Chapter 6: DTLUAPPL - Restart Token Utility

or the state file on the Integration Service machine. Therefore, you do not use DTLUAPPL to add the application or any of the capture registrations specified in an extraction. For more information about PowerExchange Client for PowerCenter and restart token management, see PowerExchange Interfaces for PowerCenter.

For ODBC users, provide the list of the capture registrations included in the application by specifying the list of registrations to add within an application block. PowerExchange maintains restart tokens for each registration in an application entry in the CDEP file. The restart tokens can be generated or provided at the application or capture registration level. Restart tokens at capture registration level override those specified at the application level. If no token is specified at capture registration level, the one at application level will be propagated to that capture registration.

ADD and MOD Statement SyntaxUse the following guidelines when coding statements:

♦ To add a new application, use the ADD APPL and ADD RSTTKN statements.

♦ To modify an existing application, use the MOD APPL statement.

♦ To add or modify an existing capture registration in an existing application use the MOD RSTTKN statement.

♦ DTLUAPPL produces an error when adding an application that already exists.

♦ The ADD or MOD APPL statement must always complete with an END APPL statement. Use the following syntax:

ADD|MOD APPL application_name instance RSTTKN GENERATE CAPTMETH=acc_meth CONDTYPE=P JRN=library/journal ORACOLL=collection ORACONN=connection ORAINST=instance ORASCHEMA=schema UDBDB=database

ADD|MOD RSTTKN registration_name DB=library/table GENERATE END APPL application_name

DTLUAPPL has the following parameters:

application_nameSpecifies the name of the application to be added. This is case sensitive.

DBOverrides the table specified in the capture registration. Valid for AS/400 CDC only.

CAPTMETHSpecifies the capture access method:

♦ CAPXRT for real-time or continuous extraction mode

♦ CAPX for batch extraction mode

Valid for Oracle CDC only.

COND_TYPESpecifies the Condense Type:

♦ P for Partial condense.

Valid for Oracle CDC only.

GENERATEGenerates restart tokens at the current end of the change stream for the capture registration specified.

instanceSpecifies the Registration and Extraction Group instance value. See Table 6-1 on page 26 for additional information.

Control Statement Syntax 25

JRNOverrides the journal specified in the capture registration. Valid for AS/400 CDC only.

ORACOLLOverrides the collection identifier specified in the capture registration. Valid for Oracle CDC only.

ORACONNOverrides connection string for the required Oracle connection. Valid for Oracle CDC only.

ORAINSTOverrides the Oracle instance name. Valid for Oracle CDC only.

ORASCHEMAOverrides the Oracle schema name. Valid for Oracle CDC only.

registration_nameSpecifies the name of the capture registration. This is case sensitive.

RSTTKN GENERATEGenerates restart tokens at the current end of the change stream for the application.

UDBDBSpecifies the connection database where this is different from the registration database. Valid for UDB CDC only.

The instance variable relates to the Instance field displayed in the PowerExchange Navigator in Registration or Extraction Group. The following table describes the instance value by data source:

Additional Parameters for DB2 on i5/OSAdditional parameters are available for DB2 on i5/OS:

ADD|MOD APPL application_name instance JRN=library/journalADD|MOD RSTTKN registration_name DB=library/table

JRNOverrides the journal and DB overrides the table name of the capture registration.

Additional Parameters for OracleAdditional parameters are available for Oracle:

ADD|MOD APPL application_name instance RSTTKN GENERATE CAPTMETH=acc_meth CONDTYPE=P

Table 6-1. Instance Values by Data Source

Data Source INSTANCE

Adabas DBID value

DB2 for i5/OS DBID value in CAPTPARM member of the CFG file

Datacom MUF name

DB2 for z/OS Subsystem id

IDMS CV name

IMS IMS System identifier

Microsoft SQL Server Instance name chosen when creating the Registration Group

Oracle Collection identifier from the ORACLEID statement in the dbmover.cfg configuration file

DB2 for Linux, UNIX, and Windows

Registration Database

VSAM Instance name chosen when creating the Registration Group


ORACOLL=collection ORACONN=connection ORAINST=instance ORASCHEMA=schema

CAPTMETHSpecifies the capture extraction method that DTLUAPPL uses to generate the correct format of restart tokens for Oracle sources.

CONDTYPE Specifies that DTLUAPPL generates restart tokens for partial condense.

ORACOLLAllows the user to override the Oracle collection id.

ORACONN Allows the user to override Oracle connection information for a given Oracle Collection Id. This means that the user can use a single set of registrations to capture data from multiple Oracle instances. The user can specify either or both Instance/Connection string; if one of the keywords is not specified, Oracle Capture will pick up the value of the other from the PowerExchange configuration file.

ORAINSTAllows the user to override Oracle instance information for a given Oracle Collection Id. This means that the user can use a single set of registrations to capture data from multiple Oracle instances.

ORASCHEMA Allows the user to override the Oracle schema.

Additional Parameters for DB2 for Linux, UNIX, and WindowsAdditional parameters are available for DB2 for Linux, UNIX, and Windows:

ADD|MOD APPL application_name instance UDBDB=database

UDBDBSpecifies the connection database when it is different from the registration database.

Running DTLUAPPL

i5/OSThe following command copies the data maps based on the options specified in the default member CFG/DTLUAPPL in the current datalib library:

SBMJOB CMD(CALL PGM(DTLLIB/DTLUAPPL)PARM('DATALIB/CFG(TKNPARMS)')) JOB(MYJOB) JOBD(DATALIB/DTLLIST) PRTDEV(*JOBD) OUTQ(*JOBD) CURLIB(DATALIB) INLLIBL(*JOBD)

The parameters controlling the utility are specified in the TKNPARMS member of the CFG file of the PowerExchange datalib library.

Running DTLUAPPL 27

Linux, UNIX, and WindowsPowerExchange installs DTLUAPPL into the base PowerExchange directory. Control statements should be entered into member DTLTKNP.TXT which is supplied with sample statements.

The following table shows the alternative ways of running DTLUAPPL:

z/OS and OS/390PowerExchange provides sample JCL for the DTLUAPPL utility in the DTLUAPPL member of the RUNLIB library.

The following JCL statements are required to run the utility:

//DTLUSBRG JOB 'DTLSETFL',MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID,// CLASS=A,REGION=0M//STEP1 EXEC PGM=DTLUAPPL,//STEPLIB DD DISP=SHR,DSN=&HLQ..LOADLIB// DD DISP=SHR,DSN=&HLQ..LOAD// DD DISP=SHR,DSN=&SCERUN//SYSPRINT DD SYSOUT=*//


EXEC PGM=DTLUAPPLInvokes the utility.



To run the DTLUAPPL utility:

1. Verify that your JCL contains the required control statements.

2. Submit the DTLUAPPL job.

Usage NotesConsider the following point before using the DTLUAPPL utility:

♦ Combining Commands. It is possible to combine the ADD/MOD and the PRINT commands in a single request as shown below.

ADD APPL IMSAPP1 IMS1 rsttkn GENERATE add rsttkn d002long sequence 00000A036E160000000000000A036BAA00000000

Command Action

dtluappl DTLUAPPL assumes the utility statements are in dtltknp.txt and display the output in the command window.

dtluappl > logname.txt DTLUAPPL assumes the utility statements are in DTLTKNP.TXT and writes the output to logname.txt.

dtluappl myfile.txt > logname.txt DTLUAPPL reads the utility statements from myfile.txt and the writes the output to logname.txt.


RESTART AAAAAAAA4040000000002BA700000000 add rsttkn d002root SEQUENCE 00000A036E160000000000000A036BBBB0000000 RESTART AAAAAAAA4040000000002BA700000000 add rsttkn d003root add rsttkn d008addr add rsttkn d008pay add rsttkn d008skil SEQUENCE 00000A036E160000000000000A036CCC00000000 RESTART AAAAAAAA4040000000002BA700000000END IMSAPP1PRINT APPL ALL

Examples

Example 1. Generating Restart Tokens - Application LevelThis example generates restart tokens for source registration DB2DEMO1 using an application name of tokens and then prints the restart tokens generated. When you use PowerExchange Client for PowerCenter, the restart tokens generated by DTLUAPPL can be added to the restart token file specified in the application connection for the extraction.

UID user1 EPWD CDFB2EE51CFC16C7ADD APPL tokens DSN7 RSTTKN GENERATE ADD RSTTKN db2demo1END APPL tokensPRINT APPL tokens

Example 2. Generating Restart Tokens - Capture Registration LevelThis example generates restart tokens for source registration DB2DEMO1 using an application name of tokens and then prints the restart tokens generated. When you use PowerExchange Client for PowerCenter, the restart tokens generated by DTLUAPPL can be added to the restart token file specified in the application connection for the extraction.

MOD APPL tokens DSN7 ADD RSTTKN db2demo1 GENERATEEND APPL tokensPRINT APPL tokens

Example 3. Generating Restart Tokens for Continuous Extraction ModeIn this example, an existing application called dummy is used to generate restart tokens for registration rrtb001 in instance FOX920. The default CAPI_CONNECTION in dbmover.cfg is overridden with a CAPX CAPI_CONNECTION called CAPXORA. The capture method is CAPXRT and the condense type is P for partial.

DTLUAPPL uses these parameters to generate the restart tokens with the format required for Oracle continuous extraction mode from condensed files. DTLUAPPL generates restart tokens for continuous extract mode when the CAPI_CONNECTION statement used is TYPE=CAPX and the CAPTMETH=CAPXRT. The generated restart tokens are printed.

UID user01 EPWD 40ABC4B0E32FD99F CONN_OVR CAPXORA MOD APPL dummy FOX920 RSTTKN GENERATE CAPTMETH=CAPXRT CONDTYPE=P MOD RSTTKN rrtb001 END APPL dummyPRINT APPL dummy

Examples 29

Example 4. Adding an Application with Restart TokensIn this example, an application IMSAPP1 is added with capture registrations d002long, d002root, d003root, and d008addr. The restart tokens are provided for d002long and d002root. Capture registration d003root is added without any restart tokens. Restart tokens for capture registration d008addr are generated by DTLUAPPL and added to the CDEP file.

Only ODBC users need to add all capture registrations in an application used to extract changed data. With ODBC extractions, the restart tokens are stored in the CDEP file. When you use PowerExchange Client for PowerCenter to extract changed data, add new capture registrations and their associated restart tokens to the restart token file specified in the application connection for the extraction.

ADD APPL IMSAPP1 IMS1 ADD RSTTKN d002long SEQUENCE 00000A036E160000000000000A036BAA00000000 RESTART AAAAAAAA4040000000002BA70000000 ADD RSTTKN d002root SEQUENCE 00000A036E160000000000000A036BBBB0000000 RESTART AAAAAAAA4040000000002BA700000000 ADD RSTTKN d003root ADD RSTTKN d008addr GENERATE

Example 5. Modifying Restart Tokens in an Existing ApplicationThis example shows the MOD application and MOD restart token keywords being used. The restart tokens for registration d002long in application IMSAPP1 are changed to the new values supplied.

MOD APPL IMSAPP1 IMS1 MOD RSTTKN d002long SEQUENCE 000000032D4500000000000000032D4500000000 RESTART C4D6C3D34040000000032CBD00000000END APPL IMSAPP1

Example 6. Modifying an Existing Application and Adding a New RegistrationThis example shows how to add a new capture registration, d003long, with restart tokens to the existing application IMSAPP1. Use ADD RSTTKN when adding new capture registrations to an existing extraction application name. This action is only necessary when using ODBC to extract changed data because the restart tokens are stored in the CDEP file. When you use PowerExchange Client for PowerCenter to extract changed data, add new capture registrations and their associated restart tokens to the restart token file specified in the application connection for the extraction.

MOD APPL IMSAPP1 IMS1 ADD RSTTKN d003long SEQUENCE 000000032D4500000000000000032D4500000000 RESTART C4D6C3D34040000000032CBD00000000END APPL IMSAPP1

Example 7. Printing an ApplicationDTLUAPPL can print a given application or all applications.

PRINT APPL application_name|ALL

You can print more than one application by concatenating several PRINT APPL statements or using the ALL keyword.

Sample OutputApplication name=<DB2APPL5> Rsttkn=<2> Ainseq=<0> Preconfig=<N> FirstTkn =<> LastTkn =<> CurrentTkn=<> Registration name=<db2v52c.1> tag=<DB2DSN1db2v52c1> Sequence=<000000035D5000000000000000035D5000000000> Restart =<C4D6C3D34040000000035CC800000000>


Registration name=<db2tst5c.1> tag=<DB2DSN1db2tst5c1> Sequence=<000000035D5000000000000000035D5000000000> Restart =<C4D6C3D34040000000035CC800000000>

This shows an application that has been added but for which no extractions have been run. When data has been extracted the format will change to the following (example given for a different application):

Application name=<DB2APPL1> Rsttkn=<1> Ainseq=<0> Preconfig=<N> FirstTkn =<C4D6C3D340400000000335D000000000> LastTkn =<C4D6C3D3404000000003453E00000000> CurrentTkn=<> Registration name=<db2v52c.1> tag=<DB2DSN1db2v52c1>Sequence=<0000000319140000000000000003191400000000>Restart=<4D6C3D3404000000003188C00000000>

The following table describes the contents of the fields:

Note: If you use ODBC for extraction, you can also view the tokens displayed in the printed output in the PowerExchange Navigator Extract Application dialog box.

Field Description

Rsttkn Number of RSTTKNs that exist within the application. The application IMSAPP1 added earlier in Additional Parameters for Oracle would have a value of 6 For more information, see “Adding or Modifying Application Entries” on page 24.

Ainseq Field for internal use only.

Preconfig Not used at this time.

FirstTkn Restart token for first successful run of the application if using ODBC.

LastTkn Restart token for last successful run of the application if using ODBC.

CurrentTkn Restart token for current active or last failed run of the application if using ODBC.

Examples 31

C H A P T E R 7

DTLUCBRG - Batch Registration Utility


♦ Overview of the Batch Registration Utility (DTLUCBRG), 33

♦ DTLUCBRG Parameters, 34

♦ Running DTLUCBRG, 38

Overview of the Batch Registration Utility (DTLUCBRG)

PurposeMany customers using change data capture in production environments need to register hundreds of tables for capture. It would not be practical for them to use the PowerExchange Navigator to configure and activate large numbers of registrations. The DTLUCBRG utility is designed to facilitate bulk capture registration and would be useful for new implementations of change capture technology. It creates capture registrations and extraction maps at specified Listener locations for a set of existing tables or data maps based on generic settings for all registrations.

Note: All registrations created by DTLUCBRG will be created at version 1. This utility will not set registrations to history and create subsequent versions of the registrations.

This utility performs a number of different tasks:

♦ Add a registration and extraction map.

♦ Modify existing inactive or active registrations.

♦ Use a mask to limit the scope of the registration creation.

♦ Report on the scope of the registrations in a test run before actual creation.

PlatformsDTLUCBRG is available on the following platforms:

♦ Linux

♦ UNIX

♦ Windows

33

♦ OS/390 and z/OS

You can create registrations on other platforms by using PowerExchange Listeners.

DTLUCBRG ParametersThis section describes DTLUCBRG parameters. The parameters are supplied in the following locations:

♦ Linux, UNIX, and Windows. Parameters are supplied in the dtlucbrg.txt file. The directory you are located in when you run DTLUCBRG should include this file.

♦ OS/390 and z/OS. Parameters are located in the SYSIN of the JCL.

Table 7-1 describes DTLUCBRG parameters. You are not required to specify parameters that have default values.

Table 7-1. DTLUCBRG Parameters

Parameter Default Description

DBTYPE Enter the three character mnemonic for the data source to be registered as follows:

ADA - AdabasAS4 - i5/OSDB2 - DB2 for OS/390 and z/OSDCM - DatacomIDL - IDMS for MVS log basedIDM - IDMS for MVS synchronousIMS - IMSMSS - Microsoft SQL ServerORA - OracleUDB - DB2 for Linux, UNIX, and WindowsVSM - VSAMNote: DB2 can only be used for DB2 on OS/390 or z/OS. Use UDB for DB2 for Linux, UNIX, and Windows.

CONDTYPE Specifies if the captured data is to be condensed. The options are FULL, PART and NONE. The validity of each condense option for each individual data source is documented in the relevant PowerExchange Adapter Guide.

CRGPREFIX Specify one to four character prefix for the registration names. The format of the registration name will be:

xnnnn, xxnnnn, xxxnnnn or xxxxnnnn

where:x = the value assigned by CRGPREFIX. Allowable characters, a-z, 0-9nnnn = a sequential number starting from 00001.

The default behavior, if CRGPREFIX is not specified, is to use the first four characters of the data map table name. If the table name contains characters that are not allowed (such as: not a-z or 0-9), an error message is generated informing the user that the table will be ignored but that processing will be continued. No registration will be generated for the table name shown in the message.

EPWD Encrypted password. Passwords can be encrypted by selecting the File, Encrypt Password...PowerExchange Navigator option. Use this instead of parameter PWD, shown later in this table, if passwords are not to be stored in a readable format. EPWD and PWD are mutually exclusive.

34 Chapter 7: DTLUCBRG - Batch Registration Utility

INSTANCE The value of the instance is dependent upon the data source set in DBTYPE:

ADA - Adabas Nucleus NameAS4 - Must agree with CAPI/Instance name in PowerExchange configuration file. If the captured data is to be condensed must also agree with the value of DBID in CAPTPARM.DB2 - DB2 SSIDDCM - MUF Task NameIDL - LOGSID ValueIDM - CV Task NameIDX - LOGSID ValueIMS - IMSID (must be present in the PowerExchange configuration file)MSS - Not UsedORA - Oracleid in PowerExchange configuration file on targetUDB - UDB Registration Database NameVSM - Collection Identifier

LOCATION There are four different location parameters. As a minimum, LOCATION must be specified which will point to the target node. If the registrations, data maps and data source all reside on the same machine there will be no requirement to code any other LOCATION parameter. A location of LOCAL can be used.

LOCATION_CRG Value of LOCATION

Location of the registration file (CCT).

LOCATION_DM Value of LOCATION

Location of the DATAMAP file.

LOCATION_XDM Value of LOCATION

Location of the extraction maps.

OUTPUT On z/OS SYSPRINT, on Win STDOUT

This option describes the location and name of the report from DTLUCBRG.Format OUTPUT=c:\pwx\outfile.txt for Windows. On MVS the report will be directed to the SYSPRINT DD output. Where the path includes names which have spaces please enclose the path and name with quotes.

PWD Password in clear text. If it is preferred use the EPWD option documented earlier in the table, which allows the entry of a password in encrypted format.

REPLACE N Specify Y or N.Y = Replace inactive registrations that already exist and fit the mask specified in the TABLE parameter.N = Do not replace any existing registrations. Add registrations for any tables that fit the mask and do not already exist.

REPLACEACTIVE N Specify Y or N.Y = Replace any active registrations that already exist and fit the mask specified in the TABLE parameter. For this to be accepted REPLACE must also be set to Y.N = Do not replace active registrations.

REUSECRGNAME N Specify Y or N.Y = For existing registrations retain the current nameN = Replace the exisiting registration name using the CRGPREFIX and sequential number format.

RPTCOLS Y Specify Y or N.N = Report on only the table names which have been registered during the run.Y = Report on table names, and additionally their constituent columns, registered during the run.



DTLUCBRG Parameters 35

Multiple Sets of ParametersMultiple sets of parameters can be placed in the same parameters file. These sets must be separated with a ‘;’ positioned on a new line between the sets of parameters. For example:

DBTYPE DB2TABLE DTL*OUTPUT=c:\dtlucdb2.txtetc. ...;DBTYPE DB2TABLE PWX*OUTPUT=c:\dtlucdb2_1.txtetc. ...

Note: To see output from each set of parameters, define a different file for OUTPUT=.

STATUS I Specify A or I.A = Create registrations in an active state.I = Create registrations in an inactive state. Registrations will need to be made active before they become eligible for capture.

TABLE This provides the mask to restrict the extent of registrations to be created. For relational tables this will be specified in the format:OWNER.TABLEWhere the data source is non-relational this will equate to the data map structure and will be specified in the format:SCHEMA.MAPNAMEAn asterisk can be used, in either part of the name, to specify a group of tables as follows:OWNER.T*This will cause all tables with the OWNER/SCHEMA as specified which commence with the letter T to be registered for capture.For IMS this parameter can be further refined by using a third parameter which equates to the table of the data map. This can be used when multiple tables are defined in a datamap but not all tables are required for registration (note the asterisk can be used in this tablename also). When this additional filtering is required code:SCHEMA.MAPNAME.TABLENAMEFor non-relational data sources other than IMS the same functionality is available to refine the selection but the format is slightly different. When additional filtering is required code:SCHEMA.MAPNAME_TABLENAME

TESTRUN Y Specify Y or N.Y = Run the utility and report on the registrations to be updated or added. No registrations will be affected by this run.N = Run the utility and add/update registrations.

UID User ID for access to the source data. The requirement for this parameter is dependent both upon the data source being registered and the value of the SECURITY parameter specified in the PowerExchange configuration file. For more information, see the PowerExchange Reference Manual.




Source Specific ParametersCertain data sources, Adabas, IMS, Oracle and Microsoft SQL Server, require additional information to enable registration updates to be made. These are in parameters that start with the DBTYPE and have a suffix of OPTS. These parameters are placed in the same parameter file as those specified in Table 7-1 on page 34.

Table 7-2 lists the required values for the data sources in additional parameters:

Adabas ADAOPTS ParameterThe syntax of the ADAOPTS parameter is:

ADAOPTS=(FileNo=<file number>,DBID=<dbid>)

If ADAOPTS is specified for any DBTYPE other than Adabas an error message will result.

IMS IMSOPTS ParameterThe syntax of the IMSOPTS parameter is:

IMSOPTS=(TYPE=<type>,DBDNAME=<name>,IMSID=<name>, PRIMDSN=<dsname>)

If IMSOPTS is specified for any DBTYPE other than IMS an error message will result.

Microsoft SQL Server MSSOPTS ParameterThe syntax of the MSSOPTS parameter is:

MSSOPTS=(DBSERVER=<name>,DBNAME=<name>)

If MSSOPTS is specified for any DBTYPE other than Microsoft SQL Server, an error message will result.

Table 7-2. Additional Parameters

Parameter Sub-parameter Default Mandatory Description

ADAOPTS FileNo None Y Adabas File Number

DBID None Y Adabas DBID

IMSOPTS TYPE SYN N Valid values SYN or LOG. Determines if capture is for a SYNchronous or LOG based environment.

DBDNAME From Datamap

N Database name taken from the DBD

IMSID None N IMS ID used in DBMOVER in RUNLIB

PRIMDSN None N Primary Dataset Name

MSSOPTS DBSERVER None Y Name of database server

DBNAME FromDatamap

Y Name of the database within which the tables for capture reside.

ORAOPTS DDLFILE dtlucbrg_ora.sql

N File name for file where Alter DDL for Supplemental Log Groups is stored. This parameter can include a path, such as c:\sql\oraopts.sql. If a path is specified which includes spaces in the name do not use quotes to delimit the name and path. If DDLFILE= is coded then the default name is assigned and placed in the default directory. If a different name is required then code the full path and name. If just a path is coded with no name the utility will give an error.

DTLUCBRG Parameters 37

Oracle ORAOPTS ParameterThe syntax of the ORAOPTS parameter is:

ORAOPTS=(DDLFILE=<filename>)

The value of the parameters are detailed in Table 7-2 on page 37.

DDLFILE is a mandatory sub-parameter of ORAOPTS. To access the default path and file name code:

ORAOPTS=(DDLFILE=)

The DDL created by the run must be run manually to create the supplemental log groups required for PowerExchange Oracle capture.

Running DTLUCBRGIt is strongly advised that the utility is run with TESTRUN=Y initially to assess the scope of the changes and additions to registration resulting from a particular run. After you see the changes reported by the TESTRUN=Y execution, change TESTRUN to N and run to see the changes take effect.

Sample InputThe following sample input will register all DB2 tables, in subsystem DSN1 (INSTANCE) and with an owner starting with characters DTL (TABLE).

The target data is on the machine addressed by MP3000 (LOCATION relating to a node in the PowerExchange configuration file), together with the registration, datamap and extraction map files.

Any registrations which satisfy the mask specified in the TABLE parameter, whether inactive or active will be replaced during this run (REPLACE and REPLACEACTIVE).

Registrations will be created as active (STATUS), prefixed by DB2 (CRGPREFIX), and will be reported on by table name only (RPTCOLS) with no column information.

The data will not be available for condensing because CONDTYPE is specified as NONE. For more information, see the relevant adapter guides for rules determining which data source is eligible for condense.

The report is written to the ucbrgoutput.txt file as follows:

OUTPUT=\MyDir\ucbrgoutput.txt

For more information about the output from these parameters, see “Sample Report” on page 40.

The following sample shows input for DTLUCBRG:

DBTYPE DB2TABLE DTL*CONDTYPE NONEINSTANCE DSN1LOCATION MP3000LOCATION_CRG MP3000LOCATION_DM MP3000LOCATION_XDM MP3000CRGPREFIX DB2TESTRUN NSTATUS AUID dtlusrPWD dtlusrOUTPUT=c:\dtlucdb2.txtREPLACE YREPLACEACTIVE YRPTCOLS N


Linux, UNIX, and WindowsThe input parameters should be supplied in the dtlucbrg.txt file by default. If the parameters are coded in this file, run the utility by entering DTLUCBRG on the command line. Parameters may be supplied in a file of another name. The report will be written to the location specified in the OUTPUT parameter.

Linux and UNIX SyntaxOn Linux and UNIX, run the utility by entering DTLUCBRG on the command line as follows:

dtlucbrg CS=/MyParms/PWX/ucbrgtest.txt

Windows SyntaxOn Windows, to run with a specified file path and name, use the following syntax:

c:\>dtlucbrg CS=C:\MyParms\PWX\ucbrgtest.txt

or if the path or file name contains imbedded blanks:

c:\>dtlucbrg CS="C:\MyParms\PWX\In Quotes for Imbedded Blanks.txt"

OS/390 and z/OS

Sample JCLThe following is an example of JCL to use when you run this utility on OS/390 or z/OS.

//DTLUSRRG JOB 'DTLSETFL',MSGCLASS=X,NOTIFY=&SYSUID,// CLASS=A,REGION=64M//********************************************************************//* *//* RUN BATCH REGISTRATION UTILITY *//* *//********************************************************************//INCS1 INCLUDE MEMBER=GENBULK//***//RUN EXEC PGM=DTLUCBRG/*/*//STEPLIB DD DISP=SHR,DSN=&HLQ..LOADLIB// DD DISP=SHR,DSN=&HLQ..LOAD// DD DISP=SHR,DSN=&SCERUN// DD DISP=SHR,DSN=&DB2LOAD// DD DISP=SHR,DSN=&DB2EXIT//*//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//***//SYSIN DD *DBTYPE DB2TABLE DTLUSR.DTL*CONDTYPE NONEINSTANCE DSN1LOCATION node1LOCATION_CRG node1LOCATION_DM node1LOCATION_XDM node1CRGPREFIX DB2TESTRUN NSTATUS AUID <logonid>PWD xxxxxxREPLACE YREPLACEACTIVE YRPTCOLS N/*

Running DTLUCBRG 39

//* - other parms//* EPWD//* REUSECRGNAME//*//* CDC Datasets - need to be open if CDC to be used//*//DTLMSG DD DISP=SHR,DSN=&HLQ..DTLMSG//DTLCFG DD DISP=SHR,DSN=&RUNLIB(DBMOVER)//DTLKEY DD DISP=SHR,DSN=&RUNLIB(LICENSE)//DTLSGN DD DISP=SHR,DSN=&RUNLIB(SIGNON)//DTLLOG DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSPRINT DD SYSOUT=*//CEEDUMP DD SYSOUT=*

Sample Report2005-01-24 11:07:16 DTLUCBRG REGISTRATION REPORT (TESTRUN=N)CONDTYPE = <None>CRGPREFIX = <DB2>DBTYPE = <DB2>INSTANCE = <DSN1>LOCATION = <MP3000>LOCATION_CRG = <MP3000>LOCATION_DM = <MP3000>LOCATION_XDM = <DB3000>OUTPUT = <c:\dtlucdb2.txt>REPLACE = <Y>REPLACEACTIVE= <Y>REUSECRGNAME = <N>RPTCOLS = <N>STATUS = <A>TABLE = <DTL*>IMSOPTS: Not relevant for this run ORAOPTS: Not relevant for this run MSSOPTS: Not relevant for this run ADAOPTS: Not relevant for this run RegName Old Table-name Old Old Vers RegName Cond Status >1 =========================================================================db20008 db2captc DTLUSR.DTLRESTART Part A - db20009 db20001 DTLUSR.DTLSTATUS None A - db20010 db20002 DTLUSR.DTLTST4 None A - db20011 db20003 DTLUSR.DTLTST5 None A - db20012 db20004 DTLUSR.DTLTST6 None A - db20013 db20005 DTLUSR.DTLTST8 None A - db20014 db20006 DTLUSR.DTLTST9 None A - =========================================================================Summary of registrations created with status ACTIVE and condense type NONENo of registrations created = 0No of registrations updated = 7No of existing registrations not matching update parameters: = 02005-01-24 11:08:13 END OF DTLUCBRG REGISTRATION REPORT


RPTCOLS=N Report DescriptionThe example shows a simple report at the table level with no column detail (RPTCOLS=N). The header will contain the value of TESTRUN and this should be checked to ensure the utility has been run in the expected mode. After the header, the values of the input parameter file are echoed in the report.

Table 7-3 describes the expected content for such a report format:

RPTCOLS=Y Report DescriptionThe following example shows the extra information delivered when RPTCOLS is specified as Y:

-------------------------------------------------------------------------db20030 db20023 DTLUSR.DTLSTATUS None A - -Column Name ----------------Type-----Precision--Scale--Nulls-Key-------- TABLE_NAME VARCHAR 255 0 N Y STATUS CHAR 20 0 N N STATUS_REASON CHAR 20 0 N N APPLY_SEQUENCE VARCHAR 255 0 Y N RESTART_POINT VARCHAR 255 0 Y N-------------------------------------------------------------------------

Table 7-4 describes the fields for the extended report format:

Column information is displayed immediately after the relevant table registration information.

Note: Table and Column names may be truncated in the report.

Table 7-3. Table Report Values

Report Field Description

Registration Name The name of the new registration.

Old Registration Name The name of the old registration name where these have been replaced by new names (determined by setting REUSECRGNAME=N). The “Sample Report” on page 40 shows all registrations being replaced with new names.

Table Name The table that is being registered for capture.

Old Condense Type Where a registration is being replaced the old condense option value.

Old Status Where a registration is being replaced the old status value.

Table 7-4. Column Report Values

Field Description

Column Name Column name

Type Type, e.g CHAR, VARCHAR etc.

Precision Length of column

Scale Decimal places

Nulls Nulls, Y/N

Key Key column, Y/N

Running DTLUCBRG 41

C H A P T E R 8

DTLUCDEP - CDEP Utility


♦ Purpose, 43

♦ Platforms, 43



♦ Running DTLUCDEP, 45

♦ Examples, 46

PurposeIn the course of running your PowerExchange change capture processes there may be need of some housekeeping to remove old or unwanted applications and extractions from your PowerExchange Capture Extraction Process Control (CDEP) file.

You can use DTLUCDEP to modify or print out the contents of the CDEP file. This file contains information regarding the change capture extraction processes that have been run, timings, and input. The CDEP file is written or read by the extraction process to establish the starting point for an extraction.

Warning: It is extremely important that this utility is used appropriately as any modifications performed on the CDEP file are irreversible. This could mean that starting points for your change capture processes may be lost.

It is suggested that a backup copy of the CDEP file is taken before running the DTLUCDEP utility.

PlatformsThe DTLUCDEP utility can run on the following platforms:

♦ i5/OS

♦ UNIX and Linux

♦ Windows

♦ z/OS and OS/390

43

Control Statement SyntaxUse the following syntax for the DTLUCDEP utility control statements:

keyword appl appname days

Control Statement ParametersUse the DTLUCDEP definition file to specify how the DTLUCDEP utility operates. You can filter the resulting output of the CDEP modify/print utility by defining the operating parameters.

keywordYou can specify one of the following keywords:

♦ print. Prints to output the CDEP details matching the following parameters.

♦ modify. Removes from the CDEP file those details matching the following parameters.

applSet to appl.

appnameName of the application that you want to print or modify.all is used to specify all applications. Use the * character to specify wild cards, for example, LULU*.

daysThe number of days that the command is specified for. For example:

♦ modify appl LULU01 21. Removes all progress details for the application LULU01 that are more than 21 days old.

♦ print appl LULU01 21. Prints all progress details for the application LULU01 for the previous 21 days.

To remove all details for a particular application use 0 force. For example:

♦ modify appl LULU01 0 force. If no days parameter is specified then the utility will return the last 7 days progress (for print) or removes details (for modify) that are more than 40 days old.

ExamplesThe following are examples of CDEP definitions and meanings:

♦ print appl ALL 256. Prints the progress details of all applications in the CDEP file that occurred within the previous 256 days.

♦ modify appl LULU03 14. Removes all progress details for the application LULU03 prior to the last 14 days.

♦ modify appl LULU06 0 force. Removes all details of the application LULU06.

44 Chapter 8: DTLUCDEP - CDEP Utility

Running DTLUCDEP

i5/OSTo run the DTLUCDEP utility:

1. Verify the definitions in the CFG(DTLUCDEP) definition file.

2. Enter the following command:

SBMJOB CMD(CALL PGM(DTLLIB/DTLUCDEP)PARM('CS=DATALIB/CFG(DTLUCDEP)')) JOB(MYJOB) JOBD(DATALIB/DTLLIST) PRTDEV(*JOBD) OUTQ(*JOBD) CURLIB(*CRTDFT) INLLIBL(*JOBD)

UNIX, Linux, and WindowsTo run the DTLUCDEP utility:

1. Verify the definitions in the dtlucdep.txt definition file.

2. Enter the following command:

DTLUCDEP

z/OS and OS/390PowerExchange provides sample JCL for the DTLUCDEP utility in the DTLUCDEP member of the RUNLIB library.


//DTLUCDEP JOB 'DTLSETFL',MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID,// CLASS=A,REGION=0M//STEP1 EXEC PGM=DTLUCDEP,//STEPLIB DD DISP=SHR,DSN=&HLQ..LOADLIB// DD DISP=SHR,DSN=&HLQ..LOAD// DD DISP=SHR,DSN=&SCERUN//SYSPRINT DD SYSOUT=*////SYSIN DD * user DTLUSR epwd A3164A3622798FDC print appl testapp /*

The DTLUCDEP definitions can either be in-stream (as shown above) or as a referenced PDS using the DD statement.


EXEC PGM=DTLUCDEPInvokes the utility.



To run the DTLUCDEP utility:

1. Verify the definitions in the JCL.

2. Submit the DTLUCDEP job.

Running DTLUCDEP 45

Examples

i5/OSThe following output is an example of the results of the DTLUCDEP utility:

03/11/04 10:01:22 POWEREXCHANGE/CFG(DTLUCDEP) CARDS===============================================================================user XXXXXX pswd 889B042B53F132B7 print appl ALL 60Print of requested All Applications since 03/09/05 10:01:22===============================================================================Print of testdota : All Applications-------------------------------------------------------------------------------Application name=<testdota> AS4 Rsttkn=<1> Ainseq=<0> First run started =<03/06/13 16:26:19> ended <03/06/13 17:06:08> sequence =<2A102FE20A3600000000000000000770 66F22A102FE20A360000000000000000 077066F1> restart =<D9D6C4E3C5E2E3F32A102FE20A360000 000000000000077066F0> Last run started =<03/06/13 16:26:19> ended <03/06/13 17:06:08> sequence =<2A102FE20A3600000000000000000770 66F22A102FE20A360000000000000000 077066F1> restart =<D9D6C4E3C5E2E3F32A102FE20A360000 000000000000077066F0>Current run started =<> ended <> sequence =<00000000000000000000000000000000 00000000000000000000000000000000 00000000> restart =<00000000000000000000000000000000 00000000000000000000> Tokens supplied by the token utility Registration name=<dot1.1> tag=<AS4RODTEST3dot11> sequence =<2A2F96A18FC000000000000000000000 00F02A2F96A18FC00000000000000000 000000F0> restart =<D9D6C4E3C5E2E3F32A2F96A18FC00000 000000000000000000F0>Print of progress for testdota since 03/09/05 10:01:22 No progress for Application name=<testdota>Print of testdota1 : All Applications-------------------------------------------------------------------------------

Linux, UNIX, and WindowsThe output can be piped to a text file if required using the normal command line pipe option. For example:

DTLUCDEP > output.txt

The following output is an example of the results of the DTLUCDEP utility:

2.2.4DTLUCDEP Example output from the utility03/10/31 15:46:12 V:\bin\dtlucdep.txt CARDS=============================================================================== print appl LULU03

Print of requested Application LULU03 only since 03/10/24 15:46:12===============================================================================Print of LULU03 : Application LULU03 only===============================================================================Application name=<LULU03> Rsttkn=<0> Ainseq=<0> First run started =<03/10/24 11:17:37> ended <03/10/24 11:18:04> sequence =<0000000002B9960000000002B995> restart =<0000000002B9944D5045584C5F535953 54454D5F564F4C554D455F534554> Last run started =<03/10/24 11:17:37> ended <03/10/24 11:18:04> sequence =<0000000002B9960000000002B995> restart =<0000000002B9944D5045584C5F535953 54454D5F564F4C554D455F534554>Current run started =<> ended <> sequence =<0000000000000000000000000000> restart =<00000000000000000000000000000000 0000000000000000000000000000>


Print of progress for LULU03 since 03/10/24 15:46:12 No progress for Application name=<LULU03>

z/OS and OS/390The following output is an example of the results of the DTLUCDEP utility:

03/11/04 12:04:51 SYSIN CARDS=============================================================================== user DTLUSR epwd A3164A3622798FDC print appl testapp modify appl all 40Print of requested Application testapp only since 03/10/28 12:04:51===============================================================================DTL-04558 Application Index data for <testapp> not found. Application name=<testapp> does not existModify for requested All Applications before 03/09/25 12:04:51===============================================================================

Modify of TESTRUN : All Applications

Modify of progress for TESTRUN before 03/09/25 12:04:51 No progress for Application name=<TESTRUN>MOD Application name=<TESTRUN> Rsttkn=<0> Ainseq=<0>

First run started =<03/11/04 12:01:10> ended <03/11/04 12:01:45> sequence =<000000004F0200000000000000004D1B 00000000> restart =<C4D6C3D34040000000003D4700000000> Last run started =<03/11/04 12:02:46> ended <03/11/04 12:03:12> sequence =<000000004F0200000000000000004D1B 00000000> restart =<C4D6C3D34040000000003D4700000000>Current run started =<> ended <> sequence =<00000000000000000000000000000000 00000000> restart =<00000000000000000000000000000000> Application TESTRUN - 0 progress entries expired Application name=<> 0 applications 0 progress entries expired

******************************** BOTTOM OF DATA ********************************

Examples 47

C H A P T E R 9

DTLUCSR2 - IDMS and Datacom SR2 and SR3 Records Utility


♦ Scanning for SR2 and SR3 Records, 49

Scanning for SR2 and SR3 RecordsIDMS records can become split into SR2 and SR3 records when a record can no longer fit on its home page. This situation normally occurs because of database reorganization, resulting in an SR2 record of 8 bytes held on the home page and the SR3 record held elsewhere. PowerExchange Change Data Capture needs to understand the position of these SR3 records, and this must be facilitated by running utility DTLUCSR2. After DTLUCSR2 has been run, the ECCR can scan the internal tables for SR2 and matching SR3 records.

Running DTLUCSR2Utility DTLUCSR2 must be run initially before IDMS Log-based capture is run for the first time and after any subsequent database reorganizations.

1. Edit RUNLIB member DTLICSRI.

For each database for which records will be registered for capture, edit the sample statements with the relevant values as described in the following example and table:

Read,DD_NAME=ddnamePAGE_GROUP=nRADIX=x

Note: DTLUCSR2 will write control information to DD SR2TOTAL, and SR2/SR3 link information to SR2OUT. These files are created with default information at installation time, but the file sizes may need to be reviewed and amended depending upon the number of SR3 records.


DD_NAME Specify the DDNAME that must then be added to the DTLUCSR2 JCL. This does not have to match a DD name from an IDMS region but must match exactly the DD name added to your DTLUCSR2 JCL. Format: DD_NAME=STUDENT

PAGE_GROUP If the database file is normally accessed with a page group other than zero, the PAGE_GROUP number must be specified.

RADIX RADIX must be specified if it is not the default value of 8. Valid range is 2 to 12.

49

2. Add relevant DD cards to your DTLUCSR2 JCL, which match the DD names supplied in parameter file DTLICSRI.

The DD cards added point to the relevant IDMS dataset names.

3. Run RUNLIB member DTLUCSR2.

50 Chapter 9: DTLUCSR2 - IDMS and Datacom SR2 and SR3 Records Utility

C H A P T E R 1 0

DTLUCUDB - UDB CDC Utility


♦ Overview, 51

♦ Using DTLUCUDB, 51

♦ Gathering Diagnostic Information, 58

OverviewThe DTLUCUDB utility provides two functions:

♦ Create a catalog snapshot to initialize the capture catalog table. For more information about creating a catalog snapshot, see the PowerExchange for DB2 for Linux, UNIX, and Windows Adapter Guide.

♦ Generate diagnostic information.

Using DTLUCUDBTo use the DTLUCUDB utility, you can either:

♦ Issue the command directly from the command-line; for example:

DTLUCUDB HELP

♦ Create a file containing the commands you want to run and then call the command file from the command-line; for example:

DTLUCUDB mycommads.txt

This is useful when you run a number of different commands at the same time.

Note: You can include comments in the file by prefixing the input line with “/*”.

SyntaxThe database keyword information is required for all the command options (except HELP). They specify the connection prerequisites for the UDB database.

[DB=<Database>]

51

[UID=<UserId>][PWD=<Password>|EPWD=<Encrypted Password>]

The DTLUCUDB utility has the following syntax:

CCATDMP [<database keywords] [CCATALOG=<table name>] [FILE=<filename>] [REPLACE=<N|Y>];DBINFO [<database keywords>];DUMPDIAG [<database keywords>] [CCATALOG=<table name>] BVTS=<begin VTS> [EVTS=<end VTS>] DIR=<dump directory> [REPLACE=<N|Y>];HELP ;LOGPRT [<database keywords>] [CCATALOG=<table name>] [PART=<DB partition number>] [FILE=<filename>] [REPLACE=<N|Y>] [RECSPERFILE=<records per output file>] BLSN=<begin LSN>|BVTS=<begin VTS> [ELSN=<end LSN>] [EVTS=<end VTS>] [RECS=<records to select>] [TRANID=<transaction ID>] [LOGICAL=<Y|N>] [UDB=<N|MIN|FMT|MAX>];SETDEF [<database keywords>] [CCATALOG=<table name>];SNAPSHOT [<database keywords>] [CCATALOG=<table name> [REPLACE=<N|Y>];SNAPUPDT [<database keywords>] [CCATALOG=<table name>] [REPLACE=<N|Y>] [ARCHIVEOLDPOSITIONING=<N|Y>];SQUISH [<database keywords>] [CCATALOG=<table name>] VTSDT=<VTS date time> REPLACE=<Y|N>;UPDTDRP [<database keywords>] [CCATALOG=<table name>] VTSDT=<EOC|NOW|VTS date time>;


DB The name of the UDB database to which you want to connect.The default is SAMPLE.

UID User ID to be used to connect to the database.

PWD/EPWD Password or encrypted password to be used to connect to the database.

52 Chapter 10: DTLUCUDB - UDB CDC Utility

Command OptionsThere are distinct commands that are used with DTLUCUDB:

♦ CCATDMP

♦ DBINFO

♦ DUMPDIAG

♦ HELP

♦ LOGPRT

♦ SETDEF

♦ SNAPSHOT

♦ SNAPUPDT

♦ SQUISH

♦ UPDTDRP

CCATDMPThe CCATDMP command produces a dump file containing SQL insert statements corresponding to the contents of the capture catalog table.

The default file name is “ccatdmp.<database name>.<capture catalog name>.sql”. The file is saved to the current working directory when the command is executed.

CCATDMP [<database keywords>] [CCATALOG=<table name>] [FILE=<filename>] [REPLACE=<N|Y>];

DBINFOThe DBINFO command prints out environmental information.

DBINFO [<database keywords>];

An example of this type of information is:

PWX-20526 UDB capture DB/DBMS Info:PWX-20527 SQL_DATABASE_NAME: CAPTUREPWX-20527 SQL_SERVER_NAME: DB2PWX-20527 SQL_USER_NAME: PWXUSERPWX-20527 SQL_DBMS_NAME: DB2/NTPWX-20527 SQL_DBMS_VER: 08.02.0004PWX-20527 SQL_IDENTIFIER_QUOTE_CHAR: "PWX-20527 SQL_CONNECT_CODEPAGE: 1252PWX-20527 SQL_DATABASE_CODEPAGE: 1252PWX-20527 SQL_APPLICATION_CODEPAGE: 1252PWX-20527 INST_NAME: DB2PWX-20527 IS_INST_PARTITIONABLE: 1PWX-20527 NUM_DBPARTITIONS: 5PWX-20527 INST_PTR_SIZE: 32PWX-20527 RELEASE_NUM: 03050106PWX-20527 SERVICE_LEVEL: DB2 v8.1.11.973PWX-20527 BLD_LEVEL: s060120PWX-20527 PTF: WR21365

Table 10-1. CCATDUMP Parameters


CCATALOG The capture catalog table name. The default for CCATALOG is <current_user>.DTLCCATALOG.

FILE Specifies the name of the dump file. This overrides the default “ccatdmp.<database name>.<capture catalog name>.sql“ file.

REPLACE REPLACE=Y overwrites an existing file.

Using DTLUCUDB 53

PWX-20527 FIXPACK_NUM: 11PWX-20527 OS_NAME: WIN32_NTPWX-20527 OS_VERSION: 5.2PWX-20527 OS_RELEASE: Service Pack 1PWX-20527 HOST_NAME: S160019PWX-20527 TOTAL_CPUS: 2PWX-20527 CONFIGURED_CPUS: 4PWX-20527 TOTAL_MEMORY: 3072PWX-20527 CATALOG_PARTITION: 0PWX-20528 Partition[ 0]: S160019.informatica.com, 0, S160019PWX-20541 LSN at first DB connect: 00003921000C0000PWX-20541 LSN at End of Log: 00003921000C0000PWX-20528 Partition[ 1]: S160019.informatica.com, 1, S160019.informatica.comPWX-20541 LSN at first DB connect: 0000088B800C0000PWX-20541 LSN at End of Log: 0000088B800C0000PWX-20506 Command DBINFO complete

DUMPDIAGThe DUMPDIAG command produces files for the capture catalog, general database information, and the UDB log records for each partition in the directory specified by the DIR parameter.

DUMPDIAG [<database keywords>] [CCATALOG=<table name>] BVTS=<begin VTS> [EVTS=<end VTS>] DIR=<dump directory> [REPLACE=<N|Y>];

An example of this type of information is:

PWX-20512 Producing file 'dtst20061221\ccatdmp.cap14.partcaptst.sql'PWX-20512 Producing file 'dtst20061221\dbconfig.txt'PWX-20512 Producing file 'dtst20061221\p0.logdmp'PWX-20540 Begin LSN 0000042B3EBC0000 selected for BVTS valuePWX-20519 End of UDB log file reachedPWX-20512 Producing file 'dtst20061221\p1.logdmp'PWX-20540 Begin LSN 00000768C1040000 selected for BVTS valuePWX-20519 End of UDB log file reachedPWX-20512 Producing file 'dtst20061221\p20.logdmp'PWX-20540 Begin LSN 0000046B76C10000 selected for BVTS valuePWX-20519 End of UDB log file reachedPWX-20506 Command DUMPDIAG complete

HELPThe HELP command prints the syntax of the DTLUCUDB command.

Table 10-2. DUMPDIAG Parameters


CCATALOG The capture catalog table name.

BVTS Required Parameter. The starting timestamp for the diagnostics file.The BVTS parameter is specified in format YYYY-MM-DD-HH.MI.SS.SSSSSS. Year, month and day are required. BVTS values are always specified in GMT (Greenwich Mean Time).

EVTS The ending timestamp for the diagnostics file.The EVTS parameter is specified in format YYYY-MM-DD-HH.MI.SS.SSSSSS. Year, month and day are required. EVTS values are always specified in GMT (Greenwich Mean Time).

DIR Required Parameter. Specifies the directory where the diagnostics file is written. The filename of the diagnostics file is “ccatdmp.<database name>.<capture catalog name>.sql“. The filename cannot be changed.

REPLACE Use REPLACE=Y to overwrite existing files.


LOGPRTThe LOGPRT command produces a file formatting the contents of the UDB log. by default, it creates a file named “<database name>.logprt” in the current working directory when the command is executed.

LOGPRT [<database keywords>] [CCATALOG=<table name>] [PART=<DB partition number>] [FILE=<filename>] [REPLACE=<N|Y>] [RECSPERFILE=<records per output file>] BLSN=<begin LSN>|BVTS=<begin VTS> [ELSN=<end LSN>] [EVTS=<end VTS>] [RECS=<records to select>] [TRANID=<transaction ID>] [LOGICAL=<Y|N>] [UDB=<N|MIN|FMT|MAX>];

Table 10-3. LOGPRT Parameters


CCATALOG The capture catalog table name.

PART Database Partition number.

FILE Specifies the name of the formatted log file. This overrides the default “<database name>.logprt“ file.

REPLACE REPLACE=Y overwrites an existing file.

RECSPERFILE RECSPERFILE can be used to break up large output into multiple files. When this option is used the file name has the format "<database name>.<first LSN value in file>.logprt". When the FILE keyword has been specified the file names generated have the format "<file name>.< first LSN value in file >".

BLSN BLSN is a six byte UDB Log Sequence Number (LSN) specified as hexadecimal digits. If less than 12 hexadecimal digits are specified, zeros are logically added to the left. BLSN specifies where the command is to start reading the log. BLSN defaults to the beginning of the active log and if specified must represent an actual LSN. Either BLSN or BVTS must be specified.

BVTS The starting timestamp specifies where the command is to start reading the log. Either BLSN or BVTS must be specified.

ELSN ELSN is a six byte UDB Log Sequence Number (LSN) specified as hexadecimal digits. If less than 12 hexadecimal digits are specified, zeros are logically added to the left. ELSN specifies where the command is to stop. ELSN defaults to the end of the log and does not have to correspond to an actual LSN. Either BLSN or BVTS must be specified.ELSN can be used to filter the output.

EVTS EVTS can be used to filter the output. The end timestamp specifies where the command is to stop.

RECS RECS can be used to filter the output. The number of records specifies where the command is to stop.

TRANID TRANID can be used to filter the output. TRANID is a filter only. It does not stop the reading of log records when transaction ending log records are processed.

Using DTLUCUDB 55

SETDEFThe SETDEF command allows default values to be set for keywords on the other commands.

SETDEF [<database keywords>] [CCATALOG=<table name>];

SNAPSHOTThe SNAPSHOT command is used to initialize capture catalog tables. Restart points cannot precede the point in the log where a snapshot is taken, so this command should be used with care.

SNAPSHOT [<database keywords>] [CCATALOG=<table name>] [REPLACE=<N|Y>];

For more information about creating a catalog snapshot, see the PowerExchange for DB2 for Linux, UNIX, and Windows Adapter Guide.

SNAPUPDTUse the SNAPUPDT command after partitions are added to, or removed from, the instance containing the database.

A new partition position entry is added for each new partition. Positioning entries are removed from the capture catalog for each partition that is removed.

SNAPUPDT [<database keywords>] [CCATALOG=<table name>] [REPLACE=<N|Y>]

LOGICAL UDB log reading consists of reading actual UDB log records and interpreting them into logical events (known as logical log records). The LOGICAL keyword can be used to force these log records to be printed in the file. The default is Y (yes).

UDB Controls how “real” UDB log records are formatted in the file. The options are:- N does not print at all (default)- MIN prints a minimum of information- FMT formats what is known about the record- MAX dumps the record in hex as well as formatting it.

Table 10-4. SETDEF Parameters


CCATALOG The capture catalog table name. The default is DTLCCATALOG.

Table 10-5. SNAPSHOT Parameters


CCATALOG The capture catalog table name to be initialized.

REPLACE Must be specified as Y if there are existing rows in the capture catalog table.

Table 10-3. LOGPRT Parameters



[ARCHIVEOLDPOSITIONING=<N|Y>];

SQUISHAn active capture catalog has catalog (any DDL activity) and positioning (VTS/LSN/partition sets) entries added as extractions are processed.

Use the SQUISH command to advance the base of the capture catalog to a new VTS date/time value by collapsing catalog entries (table or column alters) and removing positioning entries.

SQUISH [<database keywords>] [CCATALOG=<table name>] VTSDT=<VTS date time> REPLACE=<Y|N>;

Do not run the SQUISH command while extractions are active. Perform a backup before running SQUISH.

UPDTDRPUse the UPDTDRP command to update the default restart point.

UPDTDRP [<database keywords>] [CCATALOG=<table name>] VTSDT=<EOC|NOW|VTS date time>;

Table 10-6. SNAPUPDT Parameters



REPLACE REPLACE=Y must be specified to update the capture catalog. If REPLACE is not set to Y, the command shows what changes would be made, but does not make them.

ARCHIVEOLDPOSITIONING If you specify ARCHIVEOLDPOSITIONING=Y, the positioning entries remain in the capture catalog, but are not accessible.

Table 10-7. SQUISH Parameters



REPLACE REPLACE=Y must be specified to update the capture catalog. If REPLACE is not set to Y, the command shows what changes would be made, but does not make them.

VTSDT VTSDT is a virtual timestamp date/time value. It must be within the bounds of the capture catalog.

Table 10-8. UPDTDRP Parameters



VTSDT Mandatory parameter.The value must be greater than the capture catalog’s low VTS value, and less than the current end-of-log VTS value.- vtsdt=eoc means end of catalog- vtsdt=now means current date time- vtsdt=VTS date time means you specify a date time, for example, 2007-09-

07.18.40.47

Using DTLUCUDB 57

Gathering Diagnostic InformationGlobal Customer Support may request diagnostic information to work on a UDB capture problem. The following is a Windows command line example of the diagnostic commands:

mkdir prob1234cd /prob1234dtlucudb dumpdiag db=mydb ccatalog=my.capturecat bvts=<start time> evts=<end time>

In the directory, prob1234, are several files. This directory should be zipped and sent in to Global Customer Support for analysis.

Note: If you specify EVTS in the DUMPDIAG command, you should ensure that the problem section of the log is captured.


C H A P T E R 1 1

DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities


♦ Creating the PowerExchange Log Catalog, 59

Creating the PowerExchange Log CatalogThe Log Catalog holds information about the IDMS logs which are available for the use of PowerExchange log-based capture. During the initial installation of PowerExchange, a Log Catalog VSAM file will be created (default naming will be &HLQ..LOGSCAT) and a dummy record will be added.

For IDMS log-based capture to work effectively, it is vital to ensure that the log catalog is updated in a timely fashion and that log information is both secure and available. If the logs are not in the catalog, the records they hold will be unknown to PowerExchange. The correct way to add information to the catalog is to use utility DTLULCAT to format the input, then run DTLULOGC to amend the Log Catalog with that prepared input.

RUNLIB member DTLULCAU is supplied to run the two utilities one after the other. It is expected that this be scheduled to run as soon as the latest IDMS log had been spooled off. There may, however, be times when DTLULOGC is run in isolation, involving manual coding of the input file.

Correct scheduling of the addition logs to the Log Catalog is vital to obtaining timely data from the log-based IDMS capture environment. For more information about timing log catalog updates, see “Log Catalog Procedures” on page 63.

Running DTLULCATThis utility program is used to take the supplied journal name and use it to prepare the input required by the catalog utility program DTLULOGC. The utility is delivered as an executable on Windows and member DTLULCAT in RUNLIB on MVS. Sample statements are as follows:

IDMS_VERSION=15FILE_TYPE=CMEDIA_TYPE=DMEDIA_CONTENT=BI

59

SERVICE=IDMSE150INSTANCE_IDENTIFIER=XYLOGSID.

The utility DTLULCAT writes to DDCARD SYSPUNCH. This file is then the input to utility DTLULOGC

Running DTLULOGCThe utility DTLULOGC populates the log catalog with information about the logs to process. The example below shows sample JCL DTLULCAU to run both DTLULCAT followed by DTLULOGC. Running DTLULCAU JCL is the recommended method of adding to the Log Catalog.

This example adds log DTLUSR.IDMS.E15SP0.OFF.LOADED.JOURNAL1 for an IDMS V15 environment with CV Name IDMSE150, where the log resides on disk storage and will be accessed using a LOGSID value of XYLOGSID. Here the SYSIN data is shown as instream for clarity, but the sample JCL is delivered pointing to member DTLIDLC when running against a CV (DTLIDLL for Local Job mode) in which these statements would normally be placed.

//*******************************************************************///* *///* SAMPLE JCL TO:- *///* *///* CAPTURE IDMS JOURNAL FILE INFORMATION AND INPUT STREAM *///* INTO FOR DTLULOGC LOG FILE CATALOG ROUTINE. *///* *///* NORMALLY THE SYSIN INPUT STREAM WOULD BE A PDS MEMBER. *///* *///* THIS NEEDS TO BE INTEGRATED INTO THE END USERS JOURNAL *///* ARCHIVING PROCEDURE, WHICH MAY BE DIFFERENT FROM SITE TO SITE. *///* *///* A MECHANISM WILL NEED TO BE ESTABLISHED TO REPLACE THE DATASET *///* SPECIFIED VIA THE LOGFILE DD STATEMENT WITH THE LOGFILE *///* WHICH IS CURRENTLY THE OBJECT OF THE USERS ARCHIVING PROCEDURE *///* AND OUR CATALOG OPERATION *///* *//********************************************************************///INCS1 INCLUDE MEMBER=GENBULK//DTLULCAT EXEC PGM=DTLULCAT//STEPLIB DD DISP=SHR,DSN=DTLUSR.V800B14.LOADLIB//DTLCFG DD DISP=SHR,DSN=DTLUSR.V800B14.RUNLIB(DBMOVER)//DTLKEY DD DISP=SHR,DSN=DTLUSR.V800B14.RUNLIB(LICENSE)//DTLMSG DD DISP=SHR,DSN=&HLQ..DTLMSG,FREE=CLOSE//DTLLOG DD SYSOUT=*//LOGFILE DD DISP=SHR,DSN=DTLUSR.IDMS.E15SP0.OFF.LOADED.JOURNAL1//SYSPRINT DD SYSOUT=*//SYSPUNCH DD DSN=&&LOGDATA,// DISP=(,PASS),// SPACE=(CYL,(2,1),RLSE),


IDMS_VERSION Versions 14, 15, and 16 are supported.

FILE_TYPE File type. Specifies one of the following:- C. Central version.- L. Local mode.

MEDIA_TYPE Specifies one of the following:- T. Tape.- D. Disk.

MEDIA_CONTENT Determines the images of changed records delivered:- BI. Before images.- AI. After images. - BA. Both before and after images.

SERVICE IDMS CV name or Local Job name.

INSTANCE_IDENTIFIER Chosen LOGSID identifier.

60 Chapter 11: DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities

// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SYSIN DD * IDMS_VERSION=15FILE_TYPE=CMEDIA_TYPE=DMEDIA_CONTENT=BISERVICE=IDMSE150INSTANCE_IDENTIFIER=XYLOGSID/*//DTLULOGC EXEC PGM=DTLULOGC//STEPLIB DD DISP=SHR,DSN=DTLUSR.V800B14.LOADLIB //DTLCFG DD DISP=SHR,DSN=DTLUSR.V800B14.RUNLIB(DBMOVER)//DTLKEY DD DISP=SHR,DSN=DTLUSR.V800B14.RUNLIB(LICENSE)//DTLSGN DD DISP=SHR,DSN=DTLUSR.V800B14.RUNLIB(SIGNON)//DTLMSG DD DISP=SHR,DSN=&HLQ..DTLMSG//LOGSCAT DD DISP=SHR,DSN=DTLUSR.V800B14.V1.LOGSCAT//DTLLOG DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSPRINT DD SYSOUT=*//REPORT DD SYSOUT=*//EXPORT DD SYSOUT=*//SYSIN DD DISP=SHR,DSN=&&LOGDATA

Manually Manipulating the Log CatalogDuring the normal course of IDMS log processing, the Log Catalog will be updated using the combination of DTLULCAT and DTLULOGC to add the next available log. There may be times when details about certain log entries need to be altered, or even for logs to be removed from the catalog. To do this, DTLULOGC (DTLULOGC JCL in RUNLIB) will be run stand-alone with hand-coded input.

Table 11-1 shows the parameters available to code in an 80 byte file which would be specified as input in the SYSIN DD card (see sample JCL above). The utility allows the user to:

♦ Add an instance

♦ Add a log

♦ Update a log entry

♦ Delete an entry

♦ Export an entry to another dataset for offload

Table 11-1. Log Catalog Commands

Keyword Parameter Description

ADD_INSTANCE Add a LOGSID instance to the catalog. Each LOGSID used will require an instance to be added to the log catalog.

INSTANCE_IDENTIFIER LOGSID value.

VERSION Version number of the entry.

ADD_ENTRY Adds a specific log to the log catalog.

BLOCK_SIZE Block size of the log. Required if the logs are to be shipped to another platform.

ENTRY_NUMBER Sequential number, which should be incremented by 1 for each new log added to the log catalog.

FILE_TYPE - C. Central or Shared Service Log or Journal.- L. Local Mode or Unshared Service Log or

Journal.

FIRST_RECORD_SEQUENCE_NUMBER

Sequence number of the first record in the block.

Creating the PowerExchange Log Catalog 61

Note: Keyword commands are separated by a semi-colon (;), parameters by a comma (,).

The following sample input adds two instances (LOGSIDs), adds entries (log files), deletes an entry, reports instance LOGSIDA, exports instance LOGSIDA to a file (dtlulgce.txt), and finally deletes instance LOGSIDA:

ADD_INSTANCE INSTANCE_IDENTIFIER=LOGSIDA, VERSION=224;ADD_ENTRY INSTANCE_IDENTIFIER=LOGSIDA, ENTRY_NUMBER=777, VERSION=0, ENTRY_TYPE=1, STATUS=A, LOG_DATA_TYPE=IDL, IDMS_VERSION=15, FILE_TYPE=C, MEDIA_TYPE=D, MEDIA_CONTENT=BI, SERVICE=IDMSE150, LOG_FILE_NAME=XXXXXXXXXXXXXXXXXXXXXXXXXXXX, BLOCK_SIZE=29000, NUMBER_OF_BLOCKS=445, LAST_RECORD_OFFSET=1119, LAST_RECORD_IDENTIFIER=3, FIRST_RECORD_SEQUENCE_NUMBER=4, FIRST_RECORD_TIME_STAMP="05/03/03 10:55:01";ADD_ENTRY INSTANCE_IDENTIFIER=LOGSIDA, ENTRY_NUMBER=778, VERSION=0, ENTRY_TYPE=1, STATUS=A, LOG_DATA_TYPE=IDL, IDMS_VERSION=15, FILE_TYPE=C, MEDIA_TYPE=D, MEDIA_CONTENT=BI, SERVICE=IDMSE150, LOG_FILE_NAME=MMMMMMMMMMMMMMMMMMMMMMMMMM, BLOCK_SIZE=29000, NUMBER_OF_BLOCKS=445, LAST_RECORD_OFFSET=1119, LAST_RECORD_IDENTIFIER=3, FIRST_RECORD_SEQUENCE_NUMBER=4, FIRST_RECORD_TIME_STAMP="05/03/03 12:55:01";ADD_ENTRY INSTANCE_IDENTIFIER=LOGSIDA, ENTRY_NUMBER=779, VERSION=0, ENTRY_TYPE=1, STATUS=A, LOG_DATA_TYPE=IDL, IDMS_VERSION=15, FILE_TYPE=C, MEDIA_TYPE=D,

FIRST_RECORD_TIME_ STAMP

Timestamp of the first record in the block.

IDMS_VERSION Version number of IDMS. Specified as an integer.

INSTANCE_IDENTIFIER LOGSID value

LAST_RECORD_IDENTIFIER Record ID of the last record in the block or zeros if a non-data record.

LAST_RECORD_OFFSET Offset of last valid offset in the block.

LOG_DATA_TYPE IDL for MVS IDMS log data.

LOG_FILE_NAME Name of IDMS log file.

MEDIA_CONTENT - AI. Only contains After images.- BI. Only contains Before images.- BA. Contains both Before and After images.

MEDIA_TYPE - D. Disk.- T. Tape.

NUMBER_OF_BLOCKS Number of blocks in the log.

SERVICE CV name or Local Mode job name.

STATUS - A. Active.- S. Skip.- T. Terminate.

ENTRY_TYPE - 1. File entry.- 2. Reserved for future use.

VERSION Version number of the entry.

UPDATE_ENTRY Valid parameters are those listed for ADD_ENTRY above.

Updates a log entry. The entry is identified by the value of INSTANCE_IDENTIFIER and ENTRY_NUMBER.

DELETE_ENTRY INSTANCE_IDENTIFIER Deletes the last log for the specified INSTANCE_IDENTIFIER.

REPORT_INSTANCE INSTANCE_IDENTIFIER Lists catalog entries for the specified INSTANCE_IDENTIFIER.

EXPORT_INSTANCE INSTANCE_IDENTIFIER Used to export all information for a specified INSTANCE_IDENTIFIER to a file.

Table 11-1. Log Catalog Commands

Keyword Parameter Description


MEDIA_CONTENT=BI, SERVICE=IDMSE150, LOG_FILE_NAME=ZZZZZZZZZZZZZZZZZZCCCCCCCCCCCC, BLOCK_SIZE=29000, NUMBER_OF_BLOCKS=333, LAST_RECORD_OFFSET=1119, LAST_RECORD_IDENTIFIER=3, FIRST_RECORD_SEQUENCE_NUMBER=4, FIRST_RECORD_TIME_STAMP="05/03/03 14:55:01";ADD_INSTANCE INSTANCE_IDENTIFIER=ABCDE, VERSION=0;ADD_ENTRY INSTANCE_IDENTIFIER=ABCDE, ENTRY_NUMBER=1, VERSION=0, ENTRY_TYPE=1, STATUS=A, LOG_DATA_TYPE=IDL, IDMS_VERSION=15, FILE_TYPE=C, MEDIA_TYPE=D, MEDIA_CONTENT=BI, SERVICE=IDMSE15P, LOG_FILE_NAME=BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB, BLOCK_SIZE=29000, NUMBER_OF_BLOCKS=444, LAST_RECORD_OFFSET=1112, LAST_RECORD_IDENTIFIER=2, FIRST_RECORD_SEQUENCE_NUMBER=3, FIRST_RECORD_TIME_STAMP="05/04/03 08:55:01";ADD_ENTRY INSTANCE_IDENTIFIER=ABCDE, ENTRY_NUMBER=2, VERSION=0, ENTRY_TYPE=1, STATUS=A, LOG_DATA_TYPE=IDL, IDMS_VERSION=15, FILE_TYPE=C, MEDIA_TYPE=D, MEDIA_CONTENT=BI, SERVICE=IDMSE15P, LOG_FILE_NAME=CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC, BLOCK_SIZE=29000, NUMBER_OF_BLOCKS=445, LAST_RECORD_OFFSET=1119, LAST_RECORD_IDENTIFIER=3, FIRST_RECORD_SEQUENCE_NUMBER=4, FIRST_RECORD_TIME_STAMP="05/04/03 10:55:01";UPDATE_ENTRY INSTANCE_IDENTIFIER=LOGSIDA, ENTRY_NUMBER=779, VERSION=0, ENTRY_TYPE=1, STATUS=A, LOG_DATA_TYPE=IDL, IDMS_VERSION=15, FILE_TYPE=C, MEDIA_TYPE=D, MEDIA_CONTENT=BI, SERVICE=DTLXXXXX, LOG_FILE_NAME=AAAAAAAAAAAAAAKKKKKKKKKKKKKKK, BLOCK_SIZE=29000, NUMBER_OF_BLOCKS=111, LAST_RECORD_OFFSET=1119, LAST_RECORD_IDENTIFIER=3, FIRST_RECORD_SEQUENCE_NUMBER=4, FIRST_RECORD_TIME_STAMP="05/04/03 12:55:01";DELETE_ENTRY INSTANCE_IDENTIFIER=LOGSIDA;REPORT_INSTANCE INSTANCE_IDENTIFIER=LOGSIDA;EXPORT_INSTANCE INSTANCE_IDENTIFIER=LOGSIDA;DELETE_INSTANCE INSTANCE_IDENTIFIER=LOGSIDA;

Log Catalog ProceduresCare must be taken with the order in which the logs are added to the catalog. Operational procedures for the running of DTLULCAT and DTLULOGC must be developed to ensure that logs are added in the correct sequence.

The preferred method of operation is for DTLULCAT and DTLULOGC to be included in an archive log job (run together using DTLULCAU JCL) submitted by a WTOEXIT which intercepts a message written to the operator. The following steps need to be included in such a job:

1. Active journal will be off-loaded to an archive log.

2. The archive log should be written to a file, using a utility program like IEBGENER, which can be kept as a unique dataset name (a GDG is a good dataset structure). This copy of the log must be retained until all changes have been captured by PowerExchange. This file will be added to the PowerExchange Log Catalog by the following steps.

3. Execute DTLULCAT to generate input statements for DTLULOGC.

4. Execute DTLULOGC to update the PowerExchange Log Catalog.

When Central Versions are varied off-line to run in Local Mode, ensure Local Mode logs are added before any new Central Version logs. If a database, previously varied off-line, is subsequently varied back on-line and the Local Mode log is not added immediately, then if a later log is added to the catalog and a subsequent attempt made to add the Local Mode log, then this will fail.

The rule used for checking such log additions is:

♦ A local mode journal must not be added to the catalog if the last available timestamp within the journal is greater than the timestamp of the previously added CV mode journal.

♦ If logs are added in the incorrect sequence expect to see messages similar to the following:

51007 162240 MVS 1 PWX-19862 IDMS CATLG FILE: Add Entry Failure - Timestamp not greater than previous for key XYLOGSID000000000000000000001AIDL15CDBAIDMSE150DTLUSR.IDMS.D15SP0.OFF.J4

Creating the PowerExchange Log Catalog 63

C H A P T E R 1 2

DTLURDMO - Data Map Utility


♦ Overview, 65

♦ Windows and UNIX Command Line Utility, 65

♦ MVS DTLURDMO Job Utility, 66

♦ i5/OS Utility, 67

♦ DTLURDMO Definition File, 68

♦ DTLURDMO Example Output from the Utility, 75

OverviewThe purpose of the DTLURDMO utility is to allow the migration of data maps, capture registrations and capture extraction map definitions, from one environment or location to another. In addition the various attributes of the registrations and data maps (schema name, table name etc.) can be altered when performing the copy.

The types of definitions that can be managed with this utility are:

♦ PowerExchange data maps

♦ PowerExchange capture registrations

♦ PowerExchange capture extraction data maps

On MVS the input statements for this utility will be taken from SYSIN.

On non-MVS platforms the input argument will point to a file containing the input definition. If no input argument is provided it will look for a file dtlurdmo.ini in the current path.

The utility runs on all capture platforms.

Windows and UNIX Command Line Utility

SyntaxDTLURDMO <dtlurdmo definition file>

65

For example

DTLURDMO e:\powerexchange\bin\dtlurdmo.ini

DTLURDMO Definition FileThis file is used to specify how the DTLURDMO utility will operate. If no definition file is specified it will look for a file dtlurdmo.ini in the current path.

Please refer to “DTLURDMO Definition File” on page 68 for details.

MVS DTLURDMO Job UtilityYou run the utility by submitting the DTLURDMO job.

DTLURDMO Definition FileThis file is used to specify how the DTLURDMO utility will operate. Please refer to “DTLURDMO Definition File” on page 68 for details.

MVS Example JCL//DTLUSR01 JOB 'ADA',MSGLEVEL=1,// CLASS=A,MSGCLASS=X,NOTIFY=&SYSUID//*//DTL JCLLIB ORDER=(DTLUSR.V810.RUNLIB)//*// SET HLQ=DTLUSR.V810//*//URDMO PROC HLQ=&HLQ//*//STEP1 EXEC PGM=DTLURDMO,// REGION=0M,TIME=NOLIMIT//STEPLIB DD DSN=CEE.SCEERUN,DISP=SHR// DD DSN=&HLQ..LOADLIB,DISP=SHR//*DTLCAMAP DD DSN=&HLQ..DTLCAMAP,//* DISP=SHR//*//DTLMSG DD DSN=&HLQ..DTLMSG,DISP=SHR//DTLCFG DD DSN=&HLQ..RUNLIB(DBMOVER),DISP=SHR//DTLKEY DD DSN=&HLQ..RUNLIB(LICENSE),DISP=SHR//DTLSGN DD DSN=&HLQ..RUNLIB(SIGNON),DISP=SHR//DTLLOG DD SYSOUT=*//DATAMAP DD DSN=&HLQ..V1.DATAMAPS,DISP=SHR//DTLCAMAP DD DSN=&HLQ..V1.DTLCAMAP,DISP=SHR//DTLREPOS DD DSN=&HLQ..V1.REPOS,DISP=SHR//DTLAMCPR DD DSN=&HLQ..V1.CCT,DISP=SHR//SYSUDUMP DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSPRINT DD SYSOUT=*//CEEDUMP DD SYSOUT=*// PEND//*//*//* EXECUTE THE PROCEDURE//*//DTLLSTN EXEC URDMO//*//SYSIN DD *USER DTLUSR;EPWD 095E463AC1C5D5B8;TARGET DTLUSR;SOURCE NODE1;OUTPUT DTLUSR.V811.V1.DATAMAPS.TESTMIGR;DETAIL;DM_COPY; SELECT AM=ADABAS;//*

66 Chapter 12: DTLURDMO - Data Map Utility

i5/OS Utility

SyntaxCALL PGM(<location and name of DTLURDMO executable file>)

For example

CALL PGM(dtllib/DTLURDMO)

DTLURDMO Definition FileThis file is used to specify how the DTLURDMO utility will operate. By default the definition is in the member CFG/DTLURDMO in the current datalib library.

Please refer to “DTLURDMO Definition File” on page 68 for details.

If you wish to create a separate DTLURDMO definition file rather than use the default location you must give the library and filename of the definition file as a parameter. For example:

CALL PGM(dtllib/DTLURDMO) parm ('datalib/deffile(dtlurdmo)')

Example

Input (Definition file)The following definition simply copies datamaps with a schema name starting with ASPTEST and gives the copied map a new name of NEWNAME.

user PWXUSER; epwd 095E463AC1C5D5B8; ‘hint encrypted passwords are generated in the Navigator by File, Encrypt password ...replace; detail; target local; dm_copy; select schema=ASPTEST* am=seq; modify am=seq fn="NEWNAME";

Result (i5/OS Log)041122 094120 AS4 14675 PWX-00607 DTLURDMO VRM 5.2.1 Build V521_B06 started.041122 094120 AS4 14675 04/11/22 09:41:20 DTLURDMO *LIBL/CFG(DTLURDMO)041122 094120 AS4 14675 =======================================================041122 094120 AS4 14675 Globals: User PWXUSER041122 094120 AS4 14675 Pwd/Epwd 095E463AB1C5D5B8041122 094120 AS4 14675 Source local041122 094121 AS4 14675 Target local041122 094121 AS4 14675 Output041122 094121 AS4 14675 Replace YES041122 094121 AS4 14675 Validate NO041122 094121 AS4 14675 Detail YES041122 094121 AS4 14675 =======================================================041122 094121 AS4 14675 041122 094121 AS4 14675 Datamap copy started041122 094121 AS4 14675 =======================================================041122 094121 AS4 14675 DM_Copy #1041122 094121 AS4 14675 Select:041122 094121 AS4 14675 Schema ASPTEST*041122 094121 AS4 14675 Access Method SEQ041122 094121 AS4 14675 Alter:041122 094121 AS4 14675 AM=SEQ,FN=NEWNAME041122 094121 AS4 14675 =======================================================041122 094121 AS4 14675 Scanning Datamaps041122 094122 AS4 14675 Datamap ajkamal.flatfile does not meet selection criteria041122 094122 AS4 14675 =======================================================041122 094122 AS4 14675 Datamap: Schema <asptest1 > Map <test1 >041122 094122 AS4 14675 Datamap will be renamed to Schema <asptest1 > Map <test1 >041122 094122 AS4 14675 Tables: Renamed?

i5/OS Utility 67

041122 094122 AS4 14675 ASPSAMPLE <No>041122 094122 AS4 14675 Map access method = SEQ, FN = WIB041122 094122 AS4 14675 FN will be changed to NEWNAME041122 094122 AS4 14675 PWX-16200 FN WIB changed to NEWNAME041122 094122 AS4 14675 PWX-16201 Datamap asptest1.test1 written successfully041122 094122 AS4 14675 Updated Datamap: Schema <asptest1 > Map <test1 >041122 094122 AS4 14675 Tables:041122 094122 AS4 14675 ASPSAMPLE041122 094122 AS4 14675 Map access method = SEQ, FN = NEWNAME041122 094122 AS4 14675 Datamap as400.nrdb does not meet selection criteria041122 094130 AS4 14675 041122 094130 AS4 14675 =======================================================041122 094130 AS4 14675 Totals for Copy #1041122 094130 AS4 14675 Datamaps Selected 1041122 094131 AS4 14675 Datamaps Excluded 0041122 094131 AS4 14675 Datamaps Read 1041122 094131 AS4 14675 Datamaps Written 1041122 094131 AS4 14675 041122 094131 AS4 14675 DTLURDMO Processing Totals041122 094131 AS4 14675 Datamaps Selected 1041122 094131 AS4 14675 Datamaps Excluded 0041122 094131 AS4 14675 Datamaps Read 1041122 094131 AS4 14675 Datamaps Written 1

DTLURDMO Definition FileThis file is used to specify how the DTLURDMO utility will operate.

The definition file must have a single user input statement and any number of copy statements (dm_copy, xm_copy or reg_copy)

Note: All lines must be terminated with a semi-colon (;).

For example:

USER dtlusr;PWD mypassword;OUTPUT c:\\mydocs\\sample;SOURCE node1;TARGET node1;REPLACE;DETAIL;

dm_copy;1st copy statement etc…

dm_copy;2nd copy statement etc…

Note: Only one type of copy (dm_copy, xm_copy or reg_copy) can be used in a single run of this utility. Multiple copies of the same type can be used.

User Input StatementUSER <username>;EPWD <aabbccddeeff> / PWD <cleartext>;OUTPUT <ddname/path>;SOURCE <source listener>;TARGET <target listener>;REPLACE;VALIDATE;


DETAIL;

dm_copy Statementselect schema=<schema name> map=<map name> am=<access method>exclude schema=<schema name> map=<map name> am=<access method>modify am=<access method> fn=<filename>;modify fn=<filename>;modify schema=<schemaname>;


DETAIL If included in the User input statement, prints out detailed information on the copy process that has been run.

OUTPUT Defines the output dataset (MVS) or the directory, to where the copied files will be written. On MVS, it should be an existing data maps, CCT or extraction map VSAM file.This is an optional parameter. If not specified, the default data maps, CCT or extraction map file (specified by the TARGET) is used.If a DOS path is given any \ character must be replaced by two \\. E.g.C:\\dtlusr\\maps

PWD/EPWD One or other of these is a mandatory parameter and specifies the password either as clear text or encrypted

REPLACE Specifies whether the new output data map or registration can override an existing one or not.Omit the keyword REPLACE to accept the default of NO Code REPLACE to replace.

SOURCE Defines the source node (listener). If the source is local, all access to the data map, CCT and extraction map file is handled as local. Data is retrieved from the data map DD specified in the JCL on MVS or the path specified on Windows or UNIX.

TARGET Defines the target node (listener). If no OUTPUT specification is made the default (listener) allocated files are used.

USER Mandatory parameter which defines the user ID.

VALIDATE If included in the User input statement, specifies whether this is a trial, validation type run to check the expected results. This can be used in conjunction with the DETAIL parameter to see what will be copied and or modified when the command is run.

DTLURDMO Definition File 69

modify table=(oldname,newname);


exclude You can exclude certain data maps from the result by entering the details on this line. You can filter on:schema=<schema name> map=<map name> am=<access method>


modify Modify lines can be used to change various attributes of the copied files.- am= limits the following parameter overrides to just those matching the given access method.

For example, modify am=ADABAS dbid=newid;- schema= changes the schema name of the resulting data maps to this value.- table=(oldname,newname) changes the table name of the table identified by oldname

to the name specified in newname.- fn= changes the filename of the resulting data maps to this value.

Other overrides depend on the access method:ADABAS- dbid= changes the database identifier of the resulting data maps to this value.- fileno= changes the file number of the resulting data maps to this value.DB2 and DB2UDB- db2instance= changes the database instance of the resulting data maps to this value.- db2table= changes the database table of the resulting data maps to this value.

In the format: schema.tablename These must both be specified on the same modify line. For example: modify am=db2 db2instance=db2a db2table=db2dm.new_t1;

DCOM- dbid= changes the database identifier of the resulting data maps to this value.- dbname= changes the database name of the resulting data maps to this value.- mufname= changes the MUF name of the resulting data maps to this value.IDMS- dbname= changes the database name of the resulting data maps to this value.- subschema= changes the sub-schema name of the resulting data maps to this- value.dictname= changes the dictionary name of the resulting data maps to this- value.progname= changes the program name of the resulting data maps to this- value.ddsnodename= changes the DDS node name of the resulting data maps to this

value.MQS- qname= changes the MQ Series Queue name of the resulting data maps to this value.- qmgr= changes the MQ Series Queue Manager name of the resulting data maps to this value.ODBA- dbd= changes the PSB of the resulting data maps to this value.- imsid= changes the IMS Sub-System ID of the resulting data maps to this value.- pcb= changes the PCB number of the resulting data maps to this value.HPIMAGE- volumesetname= changes the volume set name of the resulting data maps to this value.

Any number of modify lines may be used in a single dm_copy statement.

select Creates the filter which restricts the data maps that will be copied. You can filter on:schema=<schema name> map=<map name> am=<access method>

Allowable access methods are:- SEQs- DL1- ODBA- KSDS- ESDS- RRDS- ADABAS- MQS- IDMS- IMS - all data maps of type ODBA and DL1 will be selected.- DCOM- DB2- ORACLE- MSSQL- TURBOIMAGE- DB2UDB



reg_copy StatementUse the reg_copy statement to copy a capture registration. The following information describes how to use the reg_copy statement:

♦ If you use the modify statement of the DTLURDMO Utility to modify a capture registration, regenerate the extraction map using createxmaps=yes.

♦ If you previously modified the extraction map to add or remove columns and use createxmaps=yes, make the modifications again to the newly-generated extraction map.

♦ If you use createxmaps=yes to re-generate an extraction map, you do not need to use xm_copy to copy the extraction map.

♦ If you need to copy capture registrations for non-relational data sources, copy the data maps before you copy the capture registrations.

select dbid=<dbid> dbtype=<dbtype> reg_name=<registration name> keepregtag=Y/N createxmaps=(yes,filespec);exclude reg_name=<registration name>;modify schema=<schemaname>;modify regtable=<newname>;modify condense=<condense option>;modify dbid=<database identifier>;modify dbdname=<database name>;modify subschema=<sub-schema name>;modify fn=<filename>;modify new_dbid=<registration instance>;


exclude You can exclude certain registrations from those that will be copied. You can filter on reg_name=. Registrations with names specified with this parameter are excluded.


modify Modify lines can be used to change various attributes of the copied files. Any number of modify lines may be used in a single reg_copy statement.- schema= changes the schema name of the resulting registrations to this value.- regtable= changes the table of the resulting registrations to this value.- condense= changes the condense option (NONE, FULL, PART) of the resulting registrations

to this value.- new_dbid= changes the database identifier of the resulting registrations to this value. This

equates to the Instance as defined to PowerExchange. For example, this could be the subsystem id for DB2, or collection id for VSAM. This parameter is not valid for Datacom.

Other overrides depend on the dbtype:Adabas- dbid= changes the Adabas DBID.- fileno= changes the Adabas file number.DCOM- dbid= changes the Datacom DBID.- mufname= changes the MUF name of the resulting registrations to this value.IDMS- dbname= changes the database name of the resulting registrations to this value.- subschema= changes the sub-schema name of the resulting registrations to this value.IMS- dbdname= changes the IMS DBD name.MSSQL- MSSOPTS=(DBSERVER=<name>,DBNAME=<name>) . DBSERVER is the name of database server DBName is the name of the database within which the tables for capture reside.VSAM- fn= changes the filename of the resulting registrations to this value.

select Creates the filter which restricts the registrations that will be copied. You can filter on:dbid=<dbid> dbtype=<dbtype> Allowable values of dbtype are:- ADA - ADABAS - AS4 - AS400 - DB2 - DB2 - DCM - DATACOM - IDL - IDMSL - IDM - IDMS - IMS - IMS - MSS - MSSQL - ORA - ORACLE - TIM - TURBOIMAGE- UDB - DB2UDB - VSM - VSAM

reg_name=<registration name>

keepregtag=Y/NThis can be an important option. By default DTLURDMO will regenerate registration tags, and these will probably be different than the original tags (caused by different file names, subsystems etc.). If applications are being copied that require the registration tag to be the same name then you must use this option.

createxmaps=(yes,filespec)The yes parameter can be specified to rebuild the extraction map for each copied registration. The filespec parameter is optional and is used to point to a different extraction map file. If the extraction map file that is to be used is that specified in the listener and the TARGET points to a Listener node then specify createxmaps=(yes,). If the extraction fie needs to be specified explicitly then code the filespec as a file name, library name for i5/OS, or on MVS, a DD reference (in the format DD:ddname) or as a filename.Createxmaps should not be used for IDMS map copies.

Warning: If you use 'createxmaps=yes', you will lose any extension fields which exist in the original extraction map.



xm_copy StatementThe xm_copy statement is provided for full flexibility in the event extraction maps only are required to be copied. When copying a registration the normal method would be to specify a reg_copy with createxmaps=yes.

select schema=<schema name> map=<map name> am=<access method>;exclude schema=<schema name> map=<map name> am=<access method>modify regtag=<registration tag>;

Example Definition FileThis is an example for a Windows client.

USER dtlusr;PWD mypassword;OUTPUT c:\\mydocs\\sample;SOURCE node1;TARGET node1;REPLACE;DETAIL;


select Creates the filter which restricts the capture extraction data maps that will be copied. You can filter on:schema=<schema name> map=<map name> am=<access method>

exclude You can exclude certain capture extraction data maps from the result by entering the details on this line. You can filter on:schema=<schema name> map=<map name> am=<access method>

modify Modify lines can be used to change various attributes of the copied files.- regtag= Changes the registration tag of the resulting capture extraction data maps to this value.- fn= changes the filename of the resulting data maps to this value.

Other overrides depend on the dbtype:ADABAS- dbid= changes the database identifier of the resulting extraction maps to this value.- fileno= changes the file number of the resulting extraction maps to this value.DCOM- dbid= changes the database identifier of the resulting extraction maps to this value.- dbname= changes the database name of the resulting extraction maps to this value.- mufname= changes the MUF name of the resulting extraction maps to this value.IDMS- dbname= changes the database name of the resulting extraction maps to this value.- subschema= changes the sub-schema name of the resulting extraction maps to this value.- value.dictname= changes the dictionary name of the resulting extraction maps to this value.- value.progname= changes the program name of the resulting extraction maps to this value.- value.ddsnodename= changes the DDS node name of the resulting extraction maps to this

value.MQS- qname= changes the MQ Series Queue name of the resulting extraction maps to this value.- qmgr= changes the MQ Series Queue Manager name of the resulting extraction maps to this value.ODBA- dbd= changes the PSB of the resulting extraction maps to this value.- imsid= changes the IMS Sub-System ID of the resulting extraction maps to this value.- pcb= changes the PCB number of the resulting extraction maps to this value.HPIMAGE- volumesetname= changes the volume set name of the resulting extraction maps to this value.RelationalNo changes are currently valid for relational data sources apart from registration tag.

Any number of modify lines may be used in a single xm_copy statement.


/* The following copies all SEQUENTIAL data maps with a schema /* name of DTLUSR and renames the schema name to NEWDTLUSERdm_copy;select schema=dtlusr am=SEQ;modify schema=newdtluser;

/* The following copies all ADABAS data maps except those with a/* schema name of anything starting with DTLdm_copy;select am=ADABAS;exclude schema=DTL*;

/* The following copies all capture extraction data maps and /* re-tags them to REG001xm_copy;select *;modify regtag=REG001;

/* The following copies all registrations with a registration /* name of anything starting with DTLreg_copy;select reg_name=DTL*;

DTLURDMO Example Output from the Utility040227 184556 WIN 2396 04/02/27 18:45:56 DTLURDMO dtlurdmo.ini 040227 184556 WIN 2396 ======================================================== 040227 184556 WIN 2396 Globals: User dtlusr 040227 184556 WIN 2396 Pwd/Epwd 72C5133A71C4E4AB 040227 184556 WIN 2396 Output c:\filename\ 040227 184556 WIN 2396 Replace YES 040227 184556 WIN 2396 Validate NO 040227 184556 WIN 2396 Detail YES 040227 184556 WIN 2396 ======================================================== 040227 184556 WIN 2396 040227 184556 WIN 2396 DM_Copy #1 040227 184556 WIN 2396 Select: 040227 184556 WIN 2396 Schema * 040227 184556 WIN 2396 Map * 040227 184556 WIN 2396 Rename: 040227 184556 WIN 2396 Table SEG3 to NEWSEG3 040227 184556 WIN 2396 Table TESTEMP to PRODEMP 040227 184556 WIN 2396 Table root to NEWROOT 040227 184556 WIN 2396 Table seg2 to SEGMENT2 040227 184556 WIN 2396 Alter: 040227 184556 WIN 2396 AM=SEQ,FN=fred 040227 184556 WIN 2396 ======================================================== 040227 184556 WIN 2396 Datamap copy started 040227 184556 WIN 2396 Scanning Datamaps 040227 184556 WIN 2396 ======================================================== 040227 184556 WIN 2396 Datamap: Schema <demo > Map <map2 > 040227 184556 WIN 2396 Datamap will be renamed to Schema <demo > Map <map2 > 040227 184556 WIN 2396 Tables: Renamed? 040227 184556 WIN 2396 row_out <No> 040227 184556 WIN 2396 Map access method = SEQ, FN = examples\demo2.dat 040227 184556 WIN 2396 DTL-16200 FN fred changed to fred 040227 184556 WIN 2396 DTL-16201 Datamap demo.map2 written successfully 040227 184556 WIN 2396 Updated Datamap: Schema <demo > Map <map2 > 040227 184556 WIN 2396 Tables: 040227 184556 WIN 2396 row_out 040227 184556 WIN 2396 Map access method = SEQ, FN = fred 040227 184556 WIN 2396 ======================================================== 040227 184556 WIN 2396 Datamap: Schema <gg > Map <train4 > 040227 184556 WIN 2396 Datamap will be renamed to Schema <gg > Map <train4 > 040227 184556 WIN 2396 Tables: Renamed? 040227 184556 WIN 2396 train4 <No> 040227 184556 WIN 2396 Map access method = SEQ, FN = examples\train4.dat

DTLURDMO Example Output from the Utility 75

040227 184556 WIN 2396 DTL-16200 FN fred changed to fred 040227 184556 WIN 2396 DTL-16201 Datamap gg.train4 written successfully 040227 184556 WIN 2396 Updated Datamap: Schema <gg > Map <train4 > 040227 184556 WIN 2396 Tables: 040227 184556 WIN 2396 train4 040227 184556 WIN 2396 Map access method = SEQ, FN = fred 040227 184556 WIN 2396 ======================================================== 040227 184556 WIN 2396 Datamap: Schema <gg > Map <train6 > 040227 184556 WIN 2396 Datamap will be renamed to Schema <gg > Map <train6 > 040227 184556 WIN 2396 Tables: Renamed? 040227 184556 WIN 2396 MASTER_REC <No> 040227 184556 WIN 2396 Map access method = SEQ, FN = examples\train6.dat 040227 184556 WIN 2396 DTL-16200 FN fred changed to fred 040227 184556 WIN 2396 DTL-16201 Datamap gg.train6 written successfully 040227 184556 WIN 2396 Updated Datamap: Schema <gg > Map <train6 > 040227 184556 WIN 2396 Tables: 040227 184556 WIN 2396 MASTER_REC 040227 184556 WIN 2396 Map access method = SEQ, FN = fred 040227 184556 WIN 2396 Datamap access method not selected 040227 184556 WIN 2396 Datamap access method not selected 040227 184556 WIN 2396 040227 184556 WIN 2396 ======================================================== 040227 184556 WIN 2396 Totals for Copy #1 040227 184556 WIN 2396 Datamaps Selected 5 040227 184556 WIN 2396 Datamaps Excluded 0 040227 184556 WIN 2396 Datamaps Read 5 040227 184556 WIN 2396 Datamaps Written 3 040227 184556 WIN 2396 040227 184556 WIN 2396 DTLURDMO Processing Totals 040227 184556 WIN 2396 Datamaps Selected 5 040227 184556 WIN 2396 Datamaps Excluded 0 040227 184556 WIN 2396 Datamaps Read 5 040227 184556 WIN 2396 Datamaps Written 3


C H A P T E R 1 3

DTLUTSK - Task Control Utility


♦ Overview, 77

♦ Linux, UNIX, and Windows Command Line Utility, 77

♦ MVS DTLUTSK Job Utility, 78

♦ MVS Command Line Utility, 79

♦ Running the Utility in the PowerExchange Navigator, 81

♦ Security Requirements, 81

OverviewThis command line utility allows you to lists active tasks and stop them if required. There several methods of using this task:

♦ Linux, UNIX, and Windows command line

♦ MVS Job

♦ MVS command

♦ Navigator GUI Row test

Linux, UNIX, and Windows Command Line Utility

SyntaxDTLUTSK CMD=<command> [TASKID=<task id>] [APPL=<task name>] LOC=<location> [UID=<user id>] [PWD=<pwd>]

77

Parameters

Example output from the utility2003-06-27 14:20:25 TASK LIST

Name Taskid Partner Port Status Acc_Method============================================================================== 0740 Active RPX 1688 Active TASK_CNTL

DTLUTSK HelpIf you do not provide any arguments (such as DTLUTSK) or if you use a question mark (such as DTLUTSK ?) the utility will display the following assistance.

DTLUTSK Help: DTLUTSK CMD=LISTTASK/STOPTASK/LISTLOCATIONS/LISTALLOC LOC=location UID=uid PWD=pwd/EPWD=encryptpwd

The following example shows the DTLUTSK help:

DTLUTSK Help: Examples:DTLUTSK Help: DTLUTSK CMD=LISTTASK LOC=NODE1 UID=uid PWD=pwdDTLUTSK Help: DTLUTSK CMD=STOPTASK TASKID=taskid LOC=NODE1 UID=uid PWD=pwdDTLUTSK Help: DTLUTSK CMD=STOPTASK APPL=taskname LOC=NODE1 UID=uid PWD=pwdDTLUTSK Help: DTLUTSK CMD=LISTLOCATIONSDTLUTSK Help: DTLUTSK CMD=LISTLOCATIONS LOC=NODE1DTLUTSK Help: DTLUTSK CMD=LISTALLOC LOC=NODE1 UID=uid PWD=pwd

MVS DTLUTSK Job UtilityThis section provides information about submitting the DTLUTSK job.

MVS Example JCLThe following example shows JCL for the DTLUTSK job. To supply the JOB card to run this JCL, copy the JOBCARD member into the DTLUTSK member.

//*//* MEMBER DTLUTSK


CMD LISTTASKLists all current tasks.STOPTASKStops the task specified by TASKID parameter.LISTLOCATIONSLists all current locationsLISTALLOCLists all allocated data sets.

TASKID You can supply the task id (obtained using the LISTTASK command) of the task that you want to stop. Used only if CMD=STOPTASK.

APPL You can supply the task name (obtained using the LISTTASK command) of the task that you want to stop. Used only if CMD=STOPTASK.

LOC The location where the task is running. These locations are specified in the PowerExchange repository and/or the dbmover.cfg file. The location specified here must be remote, an error message will be generated for LOC=LOCAL.

UID The user ID required to access the location if required.

PWD The password (or encrypted password) required to access the location if required.Non-alphanumeric characters must be enclosed in quotes (““). You cannot have a quote character as part of the password, even if it is enclosed in quotes.

78 Chapter 13: DTLUTSK - Task Control Utility

//*//INCS1 INCLUDE MEMBER=GENBULK//*//RUN EXEC PGM=DTLUTSK,// PARM=('CMD=LISTTASK LOC=location UID=userid PWD=password')/*//* SAMPLE PARMS FOLLOW://* REMOVE COMMENT BEFORE CMD TO RUN//* DTLUTSK Help: Examples://* PARM=('CMD=LISTTASK LOC=NODE1 UID=uid PWD=pwd')//* PARM=('CMD=STOPTASK TASKID=taskid LOC=NODE1 UID=uid PWD=pwd')//* PARM=('CMD=STOPTASK APPL=taskname LOC=NODE1 UID=uid PWD=pwd')//* PARM=('CMD=LISTTASK TASKID=taskid LOC=location',//* 'UID=uid EPWD=encryptpwd')//STEPLIB DD DISP=SHR,DSN=&HLQ..LOADLIB// DD DISP=SHR,DSN=&SCERUN//*//SYSIN DD DUMMY/*//*//DTLMSG DD DSN=&HLQ..DTLMSG,DISP=SHR//* IF USING MESSAGE OVERRIDE THEN CUSTOMIZE BELOW//*DTLMSGO DD DISP=SHR,DSN=&RUNLIB(DTLMSGO)//DTLCFG DD DSN=&RUNLIB(DBMOVER),DISP=SHR//DTLKEY DD DSN=&RUNLIB(LICENSE),DISP=SHR//DTLSGN DD DSN=&RUNLIB(SIGNON),DISP=SHR//DTLLOG DD SYSOUT=*//DTLLOG01 DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSOUT DD SYSOUT=*//SYSPRINT DD SYSOUT=*//CEEDUMP DD SYSOUT=*

Example Output from the Utility********************************* TOP OF DATA **********************************

2007-10-25 13:28:45 TASK LIST0Name Taskid Partner Port Status Acc_Method Sessid ================================================================================================= x 0001 10.3.4.57 6900 Active CAPXRT 0002 127.0.0.1 6900 Active TASK_CNTL

******************************** BOTTOM OF DATA ********************************

MVS Command Line UtilityThe following command line commands are available:

♦ LISTTASK. Lists all current tasks.

♦ STOPTASK. Stops the task specified by the TASKID parameter.

♦ LISTLOCATIONS. Lists all current locations.

♦ LISTALLOC. Lists all allocated data sets.

♦ FREEALLOC. Frees the allocated data sets specified by the DDNAME and data set name.

MVS LISTTASKLists all current tasks.

Syntax MODIFY <listener name>,LISTTASK

Example output from the utility:

DTL-00711 Active tasks:DTL-00712 taskid=0, partner=10.7.16.71, port=16634, name=, am=DB2, status=DTL-00713 1 active tasks

MVS Command Line Utility 79

MVS STOPTASKStops the task specified by TASKID parameter or by application name.

Syntax for Stopping by TASKIDMODIFY <listener name>,STOPTASK TASKID=<taskid>

Syntax for Stopping by Application NameMODIFY <listener name>,STOPTASK <application name>

Syntax for the MVS modify command to stop a task by application name does not use the same syntax as DTLUTSK.

Note: When using change capture processing, STOPTASK waits for a UOW boundary before terminating the task. You can change this termination behavior using the SUBCOMMIT_THRESHOLD configuration parameter. For more information about the SUBCOMMIT_THRESHOLD configuration parameter, see the PowerExchange Reference Manual.

MVS LISTLOCATIONSLists all current locations.

Syntax MODIFY <listener name>,LISTLOCATIONS

MVS LISTALLOCLists all allocated data sets.

Syntax MODIFY <listener name>,LISTALLOC

Example output from the utility:

Alloc: DDN=<STEPLIB > DSN=<CEE.SCEERUN >Alloc: DDN=< > DSN=<DTLUSR.DEVBLD.LOADLIB >Alloc: DDN=< > DSN=<DTLUSR.DEVBLD.LOAD >Alloc: DDN=< > DSN=<DTLUSR.DEVBLD.NIML.USERLIB >Alloc: DDN=<DTLAMCPR> DSN=<DTLUSR.DEVBLD.V1.CCT >Alloc: DDN=<DTLCACDE> DSN=<DTLUSR.DEVBLD.V1.CDEP >Alloc: DDN=<DTLCACDC> DSN=<DTLUSR.DEVBLD.V1.CDCT >Alloc: DDN=<DTLCAMAP> DSN=<DTLUSR.DEVBLD.V1.DTLCAMAP >Alloc: DDN=<DTLMSG > DSN=<DTLUSR.DEVBLD.DTLMSG >Alloc: DDN=<DTLCFG > DSN=<DTLUSR.V811.RUNLIB >Alloc: DDN=<DTLKEY > DSN=<DTLUSR.V811.RUNLIB >Alloc: DDN=<DTLSGN > DSN=<DTLUSR.V811.RUNLIB >Alloc: DDN=<DTLLOG > DSN=<DTLUSR.DTLLOG.LOG >Alloc: DDN=<DATAMAP > DSN=<DTLUSR.V811.V1.DATAMAPS >Alloc: DDN=<SYSUDUMP> DSN=<DTLUSR.DTLUSR2.JOB05761.D0000101.? >Alloc: DDN=<SYSOUT > DSN=<DTLUSR.DTLUSR2.JOB05761.D0000102.? >Alloc: DDN=<URLEOUT > DSN=<DTLUSR.DTLUSR2.JOB05761.D0000103.? >Alloc: DDN=<SYSPRINT> DSN=<DTLUSR.DTLUSR2.JOB05761.D0000104.? >Alloc: DDN=<CEEDUMP > DSN=<DTLUSR.DTLUSR2.JOB05761.D0000105.? >Alloc: DDN=<CXX > DSN=<DCOM.V10.CXX >Alloc: DDN=<DTLOUT > DSN=<DTLUSR.DTLUSR2.JOB05761.D0000106.? >Alloc: DDN=<DTLERR > DSN=<DTLUSR.DTLUSR2.JOB05761.D0000107.? >Command < LISTALLOC> succeeded


MVS FREEALLOCUse FREEALLOC to close and deallocate a data set that has already been dynamically allocated by a listener.

It should only be used in situations such as when a task abends and the resource managers fail to close all the dynamically allocated data sets.

Syntax MODIFY <listener name>,FREEALLOC DDN=<ddname> FN=<data set name>

The DDN and FN parameters are mandatory.

Note: The data set is not deallocated if any of the following apply:

♦ The request is not from the listener.

♦ The request is for a file that has not been dynamically allocated by the listener, and does not have a DD name starting with SYS0.

♦ The request is issued without the file name being specified

Running the Utility in the PowerExchange NavigatorThe TASK_CNTL data access method is available so that you can perform a Row Test to retrieve the results of the LISTTASK or STOPTASKS commands from within the PowerExchange Navigator.

Note: STOPTASK will only work against tasks using the CAPXRT access method.

1. In the PowerExchange Navigator, select TASK_CNTL from the DB_Type pull-down list.

2. Select the appropriate location from the Location pull-down list.

3. Enter the appropriate command in the SQL Statement box:

(listtask, listlocations, stoptask taskid=taskid or stoptask taskname)

Do not run STOPTASK against the TASK_CNTL task. The specified TASKID will not be found because a new one is generated.

Note: The Fetch list gives you a choice of the command to select. This adds the command to the SQL Statement box.

4. Click the Go button. The results are displayed in the Database Row Test Output panel.

Security Requirements

MVSIf the SECURITY Configuration Parameter is set to (2,x), where x may be N or Y, then the following RACF (or similar security package) resources must be defined to MVS, using the RACF_CLASS configuration parameter, and access granted to the required users:

DTL.TASKCTRL.DISPLAY DTL.TASKCTRL.STOPTASK

These will allow users to display the active tasks then stop them respectively.

See the PowerExchange Reference Manual for more information.

Running the Utility in the PowerExchange Navigator 81

AS400If the SECURITY Configuration Parameter is set to (2,x), where x may be N or Y, on AS400 security must be defined using the following samples, replacing DATALIB with the required data library:

GRTOBJAUT OBJ(DATALIB/AUTHTSKLST) OBJTYPE(*FILE) USER(USERID) AUT(*USE) GRTOBJAUT OBJ(DATALIB/AUTHTSKSTP) OBJTYPE(*FILE) USER(USERID) AUT(*USE)

Signon.txtIf running with a configuration setting of SECURITY(n,Y) where n may be 0 to 2, an additional parameter is available for allowing the use of list and stop tasks:

/* 4. TASKCNTRL= is an optional function allowed/* Format is D or S/* If it is supplied, then the user can use Task Control to /* Display or Stop tasks./* This signon list will only be used if Security=(n,Y) is used/* in the config.


C H A P T E R 1 4

EDMXLUTL - Event Marker Utility


♦ Creating an Event Marker in Batch Mode, 83

♦ EVENT Command, 84

♦ Keyword Sets for the BASEEDM Category, 85

♦ Control Statements for the Event-Marker Utility, 87

Creating an Event Marker in Batch ModeUse this procedure to create an event marker in your PowerExchange Logger by using the batch utility, EDMXLUTL.

Procedure1. Make a working copy of the #EDMLUTB sample JCL from the HLQ.SAMPLIB sample library, where

HLQ is the high-level qualifier specified at installation, and edit the copy as required.

2. Run the job to create the event marker.

JCL Statements for Creating a Special Event MarkerThe EVENT command is described following this procedure.

Statement Description

EXEC Specify the EDMXLUTL program.

STEPLIB DD Include the PowerExchange Change Capture load library. If you added the load library to your system's LNKLST concatenation, you do not need to add it to the STEPLIB.

EDMPARMS DD Specify the name of the user library (YOUR.USERLIB) that contains the default options module (EDMSDIR) associated with the PowerExchange Logger you are using. If you do not include an EDMPARMS DD statement, or if you specify a library that does not contain the options modules, PowerExchange Change Capture uses the STEPLIB concatenation to obtain the configuration options.

83

EVENT CommandUse the EVENT command to create event markers in batch mode.

Syntax for the EVENT CommandEVENT TYPE=category keyword1=value1 keyword2=value2 keyword3=value3 ...

Subsequent sections discuss the parameters for this command, by category. Each category has one or more sets of keywords associated with it.

UsageTo use this command, include it as a control statement in a batch job. Then, run the job to create the event marker. The following rules apply to specifying this control statement:

♦ Your statement should be contained within columns 1 through 71.

♦ If your statement will not fit in this range, you must have a character in column 72 to indicate that your statement continues on more than one line.

♦ A statement that continues on more than one line must contain only a single command.

♦ Continued statements must begin in column 1, if column 71 on the previous line is blank.

♦ A statement can use up to a 38 lines.

♦ You can use a maximum of 255 blanks to separate commands and keywords.

The following additional information is listed for this command:

♦ Before you run a job to create an event marker, be sure that the PowerExchange Logger is active.

♦ A PowerExchange Logger failure could cause the logger to stop while running an event marker job. In this case, the control statements processed prior to the failure are still accepted. Conversely, the control statement that is in progress when the PowerExchange Logger fails, and the subsequent control statements, cause the event marker utility to abend.

♦ Take care if running this command while the PowerExchange active log is receiving other log records for the source object that the marker affects. This can mix the event marker in with the other records, producing unexpected results.

♦ When the utility successfully records the event marker record in the PowerExchange log, the utility displays message DTLEDM175016I. This message provides the RBA of the event marker record within the log. You may need the RBA to reference that record.

♦ This utility obtains the name of the PowerExchange Logger that it accesses from the default options module, EDMSDIR.

EDMMSG DD Specify the data set name to which you want to issue errors and warnings.

EDMSYSIN DD Specify the appropriate EVENT command for the marker that you want to create.

Statement Description

84 Chapter 14: EDMXLUTL - Event Marker Utility

Keyword Sets for the BASEEDM CategoryUse BASEEDM to create a special event record in the PowerExchange active log. This section describes the two keyword sets that you can use with the BASEEDM category:

♦ MARK

♦ NOTIFY

MARK Keyword SetThe MARK keyword set tells the event-marker utility to insert a special marker into the PowerExchange logger active logs. The marker returns a log address and passes a signal to a component that uses PowerExchange logger data.

Note: Use the MARK keyword set only when directed to do so by a Informatica Corporation Customer Support representative.

SyntaxEVENT TYPE=BASEEDM MARK=type DATA=text

ExampleEVENT TYPE=BASEEDM MARK=EOL DATA='any text you want'

The following table describes the keywords that you can use in place of the variable for the MARK statement.

NOTIFY Keyword SetThis set of keywords tells the utility to insert a special marker into the PowerExchange active log. The special marker notifies the component using the data of an event change, such as a change in the edition value.

This is used to generate a restart point in the PowerExchange Change Capture log.

Syntax for the NOTIFY Keyword SetFor ACCESS=STRUCTURE:EVENT TYPE=BASEEDM NOTIFY=type OBJECT=database_type ACCESS=STRUCTURE {DBD=database_name DSN=data_set_name | SYSID=ssid}For ACCESS=OBJECT:EVENT TYPE=BASEEDM NOTIFY=type OBJECT=db_type ACCESS=level_of_data_objects {EDMNAME=edmname | DBD=database_name DSN=data_set_name SEGMENT=segment_name [SEGMENT=segment_name ...] | DBD=database_name DSN=data_set_name | SYSID=ssid CREATOR=tbcreator TABNAME=table_name [TABNAME=table_name ...]}

Variable Keyword Description

type Tells the utility what type of event marker to add to the log.The following keywords are valid:- EOD creates an event marker that indicates that the end of day has been reached.§- SIGNAL creates an event marker that indicates a starting point within the log or that passes a

signal to a component that uses PowerExchange logger data.- EOL creates an event marker that indicates the end of the log. The utility places the marker at

the current end of the PowerExchange active log. For the utility to identify the precise end of the log, the PowerExchange Logger should not receive any other records.

text You can enter up to 30 characters of text that the utility adds to the event marker record. If you include embedded blanks, you must enclose the text in single quotation marks.

Keyword Sets for the BASEEDM Category 85

The following table lists and describes the variables that you can use with the category BASEEDM.

If the DB2 ECCR is active when you run the create-event-marker utility to update the edition level, you must refresh the ECCR. To do so, run the MODIFY job_name,REFRESH command (where job_name is the name of the MVS batch job or started task that runs the DB2 ECCR). This ensures that the DB2 ECCR reads the new edition level in the PowerExchange repository.

Note: Alternatively, you can stop and restart the DB2 ECCR with the WARM START keyword.

These examples show the following information:

♦ the JCL to create an event marker when the edition level changes. You can find this example in the #EDMLUTB member of the HLQ.SAMPLIB sample library (where HLQ is the high-level qualifier specified at installation).

♦ the messages that result after you run the create-event-marker utility.

Variables Description

type Tells the utility what type of notification the event marker signals.The following values is valid:- EDITION provides notification that a resource registration is changing.

db_type Indicates the database type of the associated resource. The following values are valid:- IMS- VSAM- DB2

level_of_data_objects Indicates the level of data objects to be associated with the notification. The following values are valid:- STRUCTURE indicates that all data objects within the database, data set, or

subsystem are to be associated with the notification. When you specify ACCESS=STRUCTURE, you must specify either the DBD and data set name or the subsystem ID. For example, for OBJECT=IMS, you would specify DBD and DSN.

- OBJECT indicates that only the specified object is to be associated with the notification. When you specify ACCESS=OBJECT, you can specify either the EDMNAME or the fully qualified data object name. For example, for OBJECT=IMS, you would specify DBD, DSN, and SEGMENT.

edmname You can specify a particular registered source segment, record, or table by using its EDMNAME. This variable supports delimited strings, but you must enclose them in quotation marks.

dbdname When used alone, allows you to specify the database description (DBD) name of a set of IMS segments or VSAM records. When you use the DBD name as part of a fully qualified name, this name allows you to specify a particular IMS segment or VSAM record.

data_set_name Specifies the data set name of a particular IMS segment or VSAM record as part of a fully qualified name.

segment_name Specifies a particular IMS segment as part of a fully qualified name. You can use this variable multiple times (up to 255) in a single statement to associate multiple segments with the notification.

ssid You can specify the subsystem ID of a particular set of DB2 tables when used alone, or a particular DB2 table when used as part of a fully qualified name

tbcreator Specifies the creator of a particular DB2 table as part of a fully qualified name. This variable supports delimited strings, but you must enclose them in quotation marks.Note: tbcreator cannot handle DB2 long names and is limited to 8 bytes.

table_name Specifies a particular DB2 table as part of a fully qualified name. You can use this variable multiple times (up to 255) in a single statement to associate multiple tables with the notification. These tables must be in the same subsystem and have the same creator ID.This variable supports delimited strings, but you must enclose them in quotation marks.Note: table_name cannot handle DB2 long names and is limited to 18 bytes.


Sample JCL to Create an Event Marker// JOB //*-------------------------------------------------------------------* //* DETAIL Change Capture - EVENT MARKER UTILITY TO CREATE SPECIAL EVENT //* RECORD TO REFLECT A CHANGE IN EDITION LEVELS //*-------------------------------------------------------------------* //* REPLACE THE FOLLOWING ITEMS WITH PROPER INSTALLATION VALUES //* 1. JCL DATA SET NAMES //* 2. EDMSYSIN DD CONTROL CARD //*-------------------------------------------------------------------* //EDMUTIL EXEC PGM=EDMXLUTL //STEPLIB DD DISP=SHR,DSN=HLQ.LOAD <=== CDM LOADLIB //EDMPARMS DD DISP=SHR,DSN=YOUR.USERLIB <=== EDMSDIR,EDMUPARM //EDMMSG DD SYSOUT=* //EDMSYSIN DD * EVENT TYPE=BASEEDM NOTIFY=EDITION OBJECT=DB2 ACCESS=OBJECT X EDMNAME=EDM.EDMNAME1 /*

Sample Messages for the Create an Event Marker Utility

DTLEDM175015I Control card read from EDMSYSIN** Do EVENT mark for EDMNAME=VSAM.API.SOURCE*EVENT - TYPE=BASEEDM - NOTIFY=ENDCOPY - OBJECT=IMS - ACCESS=OBJECT - EDMNAME=VSAM.API.SOURCEDTLEDM175015I Executing EVENT command; command messages may follow. Event type=BASEEDMDTLEDM175025I Event Mark Notify=ENDCOPY Summary: Event Mark Logger RBA . . . . . . :C4C7D2D340400000001E466400000000 Event Sequence number . . . . . . : 0000001E466400000000 Event Edition number. . . . . . . : B42B13970E162802 Event Source EDMNAME . . . . . . : VSAM.API.SOURCE Related Target EDMNAME . . . . . : DB2.DEAG.RDADGK.APITARGET

Control Statements for the Event-Marker UtilityThe following table lists the control statements for the event-marker utility and indicates where to find additional information about each one.

For more information, see “Syntax for the EVENT Command” on page 84.

Command

EVENT TYPE=BASEEDM NOTIFY={EDITION | ENDCOPY | COPY} OBJECT={IMS | VSAM | DB2} ACCESS=STRUCTURE {DBD=dbd_name DSN=data_set_name | SYSID=ssid}

EVENT TYPE=BASEEDM NOTIFY={EDITION | ENDCOPY | COPY} OBJECT={IMS | VSAM | DB2} ACCESS=OBJECT {EDMNAME=edmname | DBD=dbd_name DSN=data_set_name SEGMENT=segment_name [SEGMENT=segment_name ...] |DBD=dbd_name DSN=data_set_name | SYSID=ssid CREATOR=table_creator TABNAME=table_name [TABNAME=table_name ...] }

Control Statements for the Event-Marker Utility 87

C H A P T E R 1 5

EDMLUCTR - Log Scan and Print Utility


♦ Purpose, 89

♦ Platforms, 89



♦ Running EDMLUCTR, 91

♦ Usage Notes, 92

♦ Examples, 92

PurposeUse the EDMLUCTR utility to perform the following tasks:

♦ Produce summary information about each log record.

♦ Produce detailed information about change records and units of work (UOWs) records.

♦ Produce summary information, by registration tag name, about all sources for which changes are captured.

♦ List UOWs that have not yet ended.

For more information about the PowerExchange Logger and Post Log Merge, see PowerExchange Change Data Capture Guide for z/OS.

PlatformsThe EDMLUCTR utility can run on the following platform:

♦ OS/390 and z/OS

89

Control Statement SyntaxUse the following syntax for the EDMLUCTR utility control statements:

[-SEL [CHANGE-DETAIL] [LOGRBA=logrba] [PACKET-DETAIL] [RECORDS=nnnnnnnn|EOF] [SUMM] ]

[-MASK mask]

The following rules and guidelines apply:

♦ Use the SYSIN DD JCL statement to enter the utility control statements.

♦ All of the control statements are optional and begin in column 1.

♦ Control statements must end with a blank and must not exceed 80 characters in length.

♦ Use one or more spaces as a delimiter between parameters for a control statement.

♦ No continuation syntax exists.

♦ If more than a single line is required for a -SEL control statement, code -SEL at the beginning of each subsequent line that includes additional parameters.

♦ The value for a parameter cannot continue from line to line.

♦ If you code multiple -MASK statements, only the last one is used.

Control Statement ParametersReview the parameter descriptions to determine which parameters to use in the EDMLUCTR control statements.

-SEL Statement-SEL has the following parameters:

CHANGE-DETAILOptional. Prints summary and detailed information, in hexadecimal format, about change records. If not specified, only summary information for change records prints.

LOGRBAOptional. Specifies an RBA value in the log data sets that is used as the starting point for the EDMLUCTR utility. When using Post-Log Merge, LOGRBA specifies a timestamp value in the log data sets. The timestamp is an unstructured TOD-clock value.

As the starting point, EDMLUCTR uses the first log record that has an RBA or a timestamp that is equal to or higher than the specified value.

Specify up to 12 hexadecimal digits for the LOGRBA value. You can omit leading zeroes.

Note: With Post-Log Merge configurations, LOGRBA must be specified and the LOGRBA value must be 16 hexadecimal digits. LOGRBA values represent the timestamp of the requested data when using Post-Log Merge.

If no parameter is specified, LOGRBA is the default. Its default value is the RBA that is recorded in the emergency restart data set (ERDS) from the latest checkpoint.

90 Chapter 15: EDMLUCTR - Log Scan and Print Utility

PACKET-DETAILOptional. Prints summary and detailed information, in hexadecimal format, about UOW records. If not specified, only summary information for UOW records prints.

RECORDSOptional. Prints or scans the specified number of log records.

When you specify RECORDS=EOF, EDMLUCTR prints all records from the specified or default start location to the current end of the log data.

If you specify -SEL RECORDS and the -MASK statement, EDMLUCTR uses the RECORDS value as the number of records to scan for the mask value rather than as the number of records to print.

Minimum is 1. Maximum is 99999999. Default is 5,000.

SUMMOptional. Prints only change summary information.

Change summary information includes the total number of inserts, updates, and deletes found in the log data scanned, ordered by source registration tag name.

-MASK Statement-MASK has the following parameter:

maskRequired. Specify a filter in one of the following formats:

♦ A character value, such as a DB2 table name, without embedded blanks. Use the hexadecimal format for character strings with embedded blanks.

♦ A hexadecimal value, such as a UOW number. Enclose hexadecimal character strings in single quotes and proceed the string with the letter X.

If you specify both -SEL RECORDS and -MASK, EDMLUCTR uses the RECORDS value as the number of records to scan for the mask value rather than as the number of records to print.

Maximum length is 70 characters.

Running EDMLUCTRPowerExchange provides sample JCL for the EDMLUCTR utility in the LOGPRINT member of the SAMPLIB library.


// JOB //READER EXEC PGM=EDMLUCTR//STEPLIB DD DISP=SHR,DSN=hlq.LOAD//ERDS01 DD DISP=SHR,DSN=your.ERDS01//EDMPARMS DD DISP=SHR,DSN=your.USERLIB//SYSIN DD *

JOB Initiates the job.

EXEC PGM=EDMLUCTR Invokes the utility.

STEPLIB DD Defines the PowerExchange LOAD library that contains the utility.

Running EDMLUCTR 91

ERDS01 DD Defines the PowerExchange Logger emergency restart data set (ERDS) that contains the inventory of log data sets containing the log records to be displayed. Specify only one ERDS data set.

EDMPARMS DD Defines the data set that contains the EDMSDIR options module.

SYSIN DD Defines the utility control statements.

Usage NotesConsider the following points before using the EDMLUCTR utility:

♦ If you specify old LOGRBA values, the utility might read archive log data sets that have been migrated by the storage management system. Verify that you have sufficient DASD to recall any migrated archive log data sets.

♦ You can use the EDMLUCTR utility in either a single PowerExchange Logger environment or Post-Log Merge environment.

♦ You can run the EDMLUCTR utility whether or not the PowerExchange Logger is running.

Examples

Example 1The following statements print summary data for all log records, starting with the RBA recorded in the ERDS which was taken from the latest PowerExchange Logger checkpoint:

// JOB//READER EXEC PGM=EDMLUCTR//STEPLIB DD DISP=SHR,DSN=hlq.LOAD//ERDS01 DD DISP=SHR,DSN=your.ERDS01//EDMPARMS DD DISP=SHR,DSN=your.USERLIB//SYSIN DD *//


22:46:20.44 L O G S T A R T22:46:20.42 PWXEDM172502I Log Scan/Print Utility initialization in-progress product level V2.4.05 08/31/200622:46:20.44 Echo of input from SYSIN..............22:46:20.44 End of input from SYSIN..............22:46:30.57 PWXEDM172191I EDMLRDS: LMF will begin transferring data for Log Scan/Print Utility at X'0000568850000000'22:46:30.67 PWXEDM172146I EDMLRDP: LMF now processing AUSQA.PWX.V850.PRILOG.DS02 for Log Scan/Print Utility22:46:52.10 Log-rec EDP-UOW=LOGGER00005688500000000000 ECCR-UOW= h& 0000000000000000 Logrba=000056885000000022:46:52.10 Log-rec EDP-UOW=LOGGER0000568850B400000001 ECCR-UOW= h& 0000000000000000 Logrba=0000568850B4000022:46:52.10 Log-rec EDP-UOW=LOGGER00005688523400000003 ECCR-UOW= h 0000000000000000 Logrba=000056885234000022:46:57.19 PWXEDM172198I EDMLPOPU: LMF table populate tasks are terminating due to an operator stop or PAC termination22:46:57.19 PWXEDM172195I EDMLUPLU: LMF task for Log Scan/Print Utility is terminating due to an operator stop or PAC termination22:46:57.20 Totals by Source..............22:46:57.20 Open Uows.....................22:46:57.20 L O G E N D

Example 2The following statements print summary data for all log records, starting from a specific RBA. Also, because the optional CHANGE-DETAIL parameter is included, the job prints detailed information in hexadecimal format about change records.

// JOB


//READER EXEC PGM=EDMLUCTR//STEPLIB DD DISP=SHR,DSN=hlq.LOAD//ERDS01 DD DISP=SHR,DSN=your.ERDS01//EDMPARMS DD DISP=SHR,DSN=your.USERLIB//SYSIN DD *-SEL LOGRBA=00000D300D80 CHANGE-DETAIL-SEL RECORDS=100//


2:07:56.62 L O G S T A R T2:07:56.59 PWXEDM172502I Log Scan/Print Utility initialization in-progress product level V2.4.05 08/31/20062:07:56.59 Echo of input from SYSIN..............2:07:56.59 -SEL LOGRBA=00000D300D80 CHANGE-DETAIL 000521112:07:56.59 -SEL RECORDS=100 000530092:07:56.60 End of input from SYSIN..............2:07:56.60 PWXEDM172191I EDMLUCTR: LMF will begin transferring data for Log Scan/Print Utility at X'00000D300D800000'2:08:06.77 PWXEDM172146I EDMLRDP: LMF now processing AUSQA.PWX.V850.AUSL.LG1.D2007296.T1417271 for Log Scan/Print Utility2:08:06.81 Chg-rec EDP-UOW=AUSL 00000D21EC3E00000000 ECCR-UOW=AUSDB2CC000C0A596E160000 Logrba=00000D300E5200002:08:06.81 Source=DB2 Func=ISRT Srcname=DB2DSN8rrtb000412:08:06.81 Timestamp-14:16:11:85 Date-10/23/20072:08:06.81 0000 00000003 00000014 000000B4 000000B42:08:06.81 0010 000001BE 00A00101 C3C46008 00000000 CD-2:08:06.81 0020 E2C40000 00000000 000C0A5F 834F0000 SD ^c|2:08:06.81 0030 00000000 00000000 0000C163 9ED5E4FA A NU³2:08:06.81 0040 CA02C4C2 F2C4E2D5 F89999A3 82F0F0F0 DB2DSN8rrtb0002:08:06.81 0050 F4F14040 40404040 40404040 40404040 412:08:06.81 0060 40404040 4040C1E4 E2D34040 00000D21 AUSL2:08:06.81 0070 EC3E0000 00000000 0D300E52 00000000 Ö2:08:06.81 0080 C4E3D300 00000001 C1E4E2C4 C2F2C3C3 DTL AUSDB2CC....2:08:06.99 Default 5000 or RECORDS= threshold reached2:08:07.02 PWXEDM172198I EDMLPOPU: LMF table populate tasks are terminating due to an operator stop or PAC termination2:08:07.03 PWXEDM172195I EDMLUPLU: LMF task for Log Scan/Print Utility is terminating due to an operator stop or PAC termination2:08:07.03 Totals by Source..............2:08:07.03 DB2DSN8rrtb00041 Isrt= 20 Repl= 0 Dlet= 0 Unk= 02:08:07.03 DB2DSN8rrtb00031 Isrt= 49 Repl= 0 Dlet= 0 Unk= 02:08:07.03 DB2DSN8rrtb01011 Isrt= 30 Repl= 0 Dlet= 0 Unk= 02:08:07.03 Open Uows.....................2:08:07.03 Edp-UOW=AUSL 00000D30252000000000 ECCR-UOW=AUSDB2CC000C0A5F8CB40000 Logrba=00000D30252000002:08:07.04 L O G E N D

Example 3The following statements filter records by the -MASK value of DB2DSN8 and print these records starting from a specific RBA.

// JOB//READER EXEC PGM=EDMLUCTR//STEPLIB DD DISP=SHR,DSN=hlq.LOAD//ERDS01 DD DISP=SHR,DSN=your.ERDS01//EDMPARMS DD DISP=SHR,DSN=your.USERLIB//SYSPRINT DD SYSOUT=*//SYSUDUMP DD SYSOUT=*//SYSIN DD *-SEL LOGRBA=D300D80 RECORDS=100-MASK DB2DSN8//

The inclusion of the optional RECORDS parameter limits the number of record scans for the character string DB2DSN8.


2:24:09.49 L O G S T A R T2:24:09.45 PWXEDM172502I Log Scan/Print Utility initialization in-progress product level V2.4.05 08/31/20062:24:09.46 Echo of input from SYSIN..............2:24:09.46 -SEL LOGRBA=D300D80 RECORDS=100 000521112:24:09.46 -MASK DB2DSN8 000530092:24:09.47 End of input from SYSIN..............2:24:09.47 PWXEDM172191I EDMLUCTR: LMF will begin transferring data for Log Scan/Print Utility at X'00000D300D800000'2:24:19.73 PWXEDM172146I EDMLRDP: LMF now processing AUSQA.PWX.V850.AUSL.LG1.D2007296.T1417271 for Log Scan/Print Utility2:24:19.77 Chg-rec EDP-UOW=AUSL 00000D21EC3E00000000 ECCR-UOW=AUSDB2CC000C0A596E160000 Logrba=00000D300E5200002:24:19.77 Source=DB2 Func=ISRT Srcname=DB2DSN8rrtb000412:24:19.77 Timestamp-14:16:11:85 Date-10/23/20072:24:19.77 Chg-rec EDP-UOW=AUSL 00000D21EC3E00000000 ECCR-UOW=AUSDB2CC000C0A596E160000 Logrba=00000D30102400002:24:19.77 Source=DB2 Func=ISRT Srcname=DB2DSN8rrtb000412:24:19.77 Timestamp-14:16:11:85 Date-10/23/20072:24:19.77 Chg-rec EDP-UOW=AUSL 00000D21EC3E00000000 ECCR-UOW=AUSDB2CC000C0A596E160000 Logrba=00000D3011E200002:24:19.77 Source=DB2 Func=ISRT Srcname=DB2DSN8rrtb000412:24:19.77 Timestamp-14:16:11:85 Date-10/23/2007...2:24:19.81 Default 5000 or RECORDS= threshold reached2:24:19.82 PWXEDM172198I EDMLPOPU: LMF table populate tasks are terminating due to an operator stop or PAC termination2:24:19.83 PWXEDM172195I EDMLUPLU: LMF task for Log Scan/Print Utility is terminating due to an operator stop or PAC termination2:24:19.84 Totals by Source..............2:24:19.84 DB2DSN8rrtb00041 Isrt= 20 Repl= 0 Dlet= 0 Unk= 0

Examples 93

2:24:19.84 DB2DSN8rrtb00031 Isrt= 49 Repl= 0 Dlet= 0 Unk= 02:24:19.84 DB2DSN8rrtb01011 Isrt= 30 Repl= 0 Dlet= 0 Unk= 02:24:19.84 Open Uows.....................

Example 4If you run the utility in a Post-Log Merge environment, the following statements print summary data for all log records starting from a specific timestamp:

// JOB//READER EXEC PGM=EDMLUCTR//STEPLIB DD DISP=SHR,DSN=hlq.LOAD//ERDS01 DD DISP=SHR,DSN=your.ERDS01//EDMPARMS DD DISP=SHR,DSN=your.USERLIB//SYSIN DD *-SEL LOGRBA=C1A4C0D9F4813301 RECORDS=EOF//


13:14:36.51 L O G S T A R T13:14:36.47 PWXEDM172502I Log Scan/Print Utility initialization in-progress product level V2.4.05 08/31/200613:14:36.48 Echo of input from SYSIN..............13:14:36.48 -SEL LOGRBA=C1A4C0D9F4813301 RECORDS=EOF 0005202013:14:36.49 End of input from SYSIN..............13:14:36.49 PWXEDM172191I EDMLUCTR: LMF will begin transferring data for Log Scan/Print Utility at X'0000000000000000'13:14:46.66 PWXEDM172146I EDMLRDP: LMF now processing DTLUSR.V851.V1.PRILOG1.DS01 for Log Scan/Print Utility13:14:46.81 Log-rec EDP-UOW=LOGGER00000000000000000000 ECCR-UOW= 000000000000C1A4 Logrba=C1A4C0D9F481330113:14:46.81 Log-rec EDP-UOW=LOGGER0000000000B400000003 ECCR-UOW= 000000000000C1A4 Logrba=C1A4C0D9F484428113:14:46.81 Log-rec EDP-UOW=DOCL C1A4C0E3C6B7BE410000 ECCR-UOW= 0000000000000000 Logrba=C1A4C0E3C6B7BE4113:14:46.81 Srv-rec EDP-UOW=DOCDB2F0F14040404040404040 ECCR-UOW= 0000000000000000 Logrba=C1A4C0E3D6CD464113:14:46.81 Srv-rec EDP-UOW=DOCDB2F0F14040404040404040 ECCR-UOW= 0000000000000000 Logrba=C1A4C0E3D6D0984113:14:46.81 Log-rec EDP-UOW=LOGGER00000000052400000000 ECCR-UOW= 000000000000C1A4 Logrba=C1A4C209F806808113:14:46.81 Log-rec EDP-UOW=LOGGER0000000005D800000001 ECCR-UOW= Q 000000000000C1A4 Logrba=C1A4C209F806A7C113:14:46.81 Log-rec EDP-UOW=LOGGER00000000075800000003 ECCR-UOW= 000000000000C1A4 Logrba=C1A4C209F809A5C113:14:51.84 PWXEDM172198I EDMLPOPU: LMF table populate tasks are terminating due to an operator stop or PAC termination13:14:51.85 PWXEDM172195I EDMLUPLU: LMF task for Log Scan/Print Utility is terminating due to an operator stop or PAC termination13:14:51.86 Totals by Source..............13:14:51.86 Open Uows.....................13:14:51.86 L O G E N D


C H A P T E R 1 6

HOSTENT - TCP/IP Address Reporter Utility


♦ Purpose, 95

♦ Platforms, 95

♦ Running HOSTENT, 96

♦ Usage Notes, 97

♦ HOSTENT Output, 97

♦ Examples, 98

PurposeUse the HOSTENT utility to:

♦ Display the TCP/IP host name and address for a system.

♦ Diagnose problems with PowerExchange communication and licensing.

PlatformsThe HOSTENT utility can run on the following platforms:

♦ i5/OS

♦ Linux and UNIX

♦ z/OS and OS/390

95

Running HOSTENT

i5/OSTo run the HOSTENT utility:


CALL HOSTENT

Linux and UNIXTo run the HOSTENT utility:


hostent

z/OS and OS/390Use the version of the HOSTENT TCP/IP Address Reporter utility for your TCP/IP environment.

Table 16-1 lists the HOSTENT versions by type of TCP/IP environment:

You can run the HOSTENT utility from the TSO/E command line or by submitting a z/OS job.

To run the HOSTENT utility from the command line, use the following statement:

call 'hlq.LOADLIB(HOSTENT)'

Use the sample JCL in the HOSTENT member of the RUNLIB library to create a job to run the utility. The sample JCL contains the following statements:

//STEP1 EXEC PGM=HOSTENT,//STEPLIB DD DSN=&SCERUN,DISP=SHR// DD DSN=&HLQ..LOADLIB,DISP=SHR//SYSPRINT DD SYSOUT=*//


EXEC PGM=HOSTENTInvokes the utility.



Table 16-1. HOSTENT Versions

HOSTENT Version Environment

HOSTENT Standard z/OS Communications Server

HOSTENT2 Computer Associates CA-TCPAccess Communications Server

HOSTENT3 Native MVS Sockets

96 Chapter 16: HOSTENT - TCP/IP Address Reporter Utility

Usage NotesConsider the following points before using the HOSTENT utility:

♦ PowerExchange uses the TCP/IP resolver to translate the host name of the TCP/IP stack into an IP address. PowerExchange uses this address to validate the licence.

♦ On z/OS and OS/390 the resolver queries the local host table. On i5/OS, Linux, and UNIX, the resolver queries the name server before it queries the local host table.

♦ On i5/OS, z/OS, and OS/390, PowerExchange uses the primary interface address of the TCP/IP stack to verify the licence if the resolver cannot find the host name.

♦ Operating systems can run more than one TCP/IP stack. Ensure that the HOSTENT runs on the TCP/IP stack that is used by PowerExchange. You cannot specify a stack name in the HOSTENT parameters.

Resolver DetailsThe resolver uses the local site tables to look up the official host name and address. The resolver does not use name servers.

For z/OS 1.2 or later, you can add the following DD statement to the HOSTENT JCL to get a resolver trace to assist in diagnosis:

//SYSTCPT DD SYSOUT=*

This reports the configuration data sets and methods of look-up that the resolver uses.

HOSTENT OutputThe following table describes the output messages generated by HOSTENT:

Operating System Message Description

i5/OS, Linux, UNIX, z/OS, or OS/390

gethostname() gives host name Displays the host name of the TCP/IP stack. On z/OS and OS/390 systems, you can find the gethostname( ) details in the TCPIP.DATA file specified in the TCP/IP stack. On i5/OS, Linux, and UNIX, you can find the gethostname() details in the TCPIP.DATA file used by PowerExchange


official hostname host name.domain name

Displays the host name returned by the resolver. The resolver looks up the given host name to find the fully qualified name including domain name.This also displays:- Alias names found by the resolver. - TCP/IP address as returned by the

resolver. PowerExchange uses this address to validate the license.

Usage Notes 97

Examples

i5/OSThe following command displays the TCP/IP host address and host name of the system on which it was run:

CALL HOSTENT


gethostid() gives: nnn.nnn.nnn.nnn gethostname() gives host name reporting on hostname host name official hostname: host name address: nnn.nnn.nnn.nnn

Linux and UNIXThe following command displays the TCP/IP host address and host name of the system on which it was run:

hostent


gethostname() gives host namereporting on hostname host nameofficial hostname: host name address: nnn.nnn.nnn.nnn


reporting on hostname host name

Displays the host name. The TCP/IP resolver uses the following methods to find the host name:- Looks up the host name from a local

hosts file.- Uses the gethostbyname() system call to

look up host names from a name server.PowerExchange uses these details to validate the license.

i5/OS, z/OS, or OS/390

gethostid() gives: nnn.nnn.nnn.nnn

Displays the primary interface address of the TCP/IP stack. If the TCP/IP resolver cannot find the host name, PowerExchange uses this address to validate the license.On z/OS or OS/390 systems, the gethostid() details are specified in the TCP/IP stack in the PRIMARYINTERFACEADDRESS parameter of the PROFILE data set.

z/OS or OS/390 resolver gives domainname: domain name

Displays the domain name as determined by the local resolver configuration data set. PowerExchange does not use this address to validate the license.

z/OS or OS/390 resolver gives hostname : host name

Displays the host name as determined by the local resolver configuration data set. PowerExchange does not use this address to validate the license.

Operating System Message Description


z/OS and OS/390The following statement displays the TCP/IP host address and host name of the system on which it was run:

//STEP1 EXEC PGM=HOSTENT// PARM='/'//STEPLIB DD DSN=&SCERUN,DISP=SHR// DD DSN=&HLQ..LOADLIB,DISP=SHR//SYSOUT DD SYSOUT=*//SYSPRINT DD SYSOUT=*


HOSTENT:gethostid() gives: nnn.nnn.nnn.nnnresolver gives hostname : host nameresolver gives domainname: domain namegethostname() gives host namereporting on hostname host nameofficial hostname: host name.domain name alias: host name address: nnn.nnn.nnn.nnn

Examples 99

I N D E X

AA (Add) 6ADAOPTS

DTLUCBRG Adabas specific parameter 37ADD 28

BBatch Registration Utility

DTLUCBRG 33

CCapture Extraction Process Control 43CCATDMP

DTLUCUDB 53CFG file (datalib library) 27Change Data Extraction Repository file 23Condensing tables

DTLUCBRG 34CONDTYPE

DTLUCBRG parameter 34createxmaps

DTLURDMO registration copy parameter 73CRGPREFIX

DTLUCBRG parameter 34

DD (Delete) 6DB2 long names

Restriction with Event Mark Utility 86DBDNAME

DTLUCBRG IMS parameter 37DBID

DTLUCBRG Adabas parameter 37DBINFO 53DBNAME

DTLUCBRG MS SQL specific parameter 37DBSERVER

DTLUCBRG MSS specific parameter 37DBTYPE

DTLUCBRG parameter 34DDLFILE

DTLUCBRG Oracle specific parameter 38DFSSTAT

IMS activity report 10

DTLCUIML 9DTLIDLC

DTLULCAT parameter file 60DTLIDLL

DTLULCAT parameter file 60DTLREXE

Remote Program Utility 15DTLTKNP.TXT 28DTLUAPPL 23

AS400 Additional Parameters 26UDB Additional Parameters 27

DTLUCBRG 33Adabas Requirements 37IMS Requirements 37Multiple sets of parameters 36Oracle Requirements 38Purpose 33Sample Input 38Source Specific Information 36, 37

DTLUCBRG parameterCONDTYPE 34CRGPREFIX 34DBTYPE 34EPWD 34INSTANCE 35LOCATION 35LOCATION_CRG 35LOCATION_DM 35LOCATION_XDM 35OUTPUT 35PWD 35REPLACE 35REPLACEACTIVE 35REUSECRGNAME 35RPTCOLS 35STATUS 36TABLE 36TESTRUN 36UID 36

DTLUCDEP 43DTLUCSR2

Utility scan program for SR2/SR3 records 49DTLUCUDB

Gathering Diagnostic Information 58Utility 51, 59, 60

DTLULCATCatalog program 60

101

DTLURDMO Definition file 66, 67DTLUTSK 78DUMPDIAG 54

EE (ET/BT Record Extraction) 7EDMXLUTL

DB2 Long name restrictions 86Encrypted password

DTLUCBRG 34EPWD

DTLUCBRG parameter 34epwd

DTLREXE parameter 16, 17Event Mark Utility

DB2 long names restriction 86Example definition

AS/400 67MVS 66

FFILE_TYPE

dtlulcat parameter 60FileNo

DTLUCBRG Adabas parameter 37fn

DTLREXE parameter 17

HHELP

DTLUCUDB 54

II (Insert) 6IDMS_VERSION

dtlulcat parameter 60IMSID

DTLUCBRG IMS parameter 37IMSOPTS

DTLUCBRG IMS specific parameter 37DTLUCBRG Parameter 37

INSTANCE 26DTLUCBRG parameter 35

INSTANCE_IDENTIFIERDTLUCUDB parameter 60

Kkeepregtag

DTLURDMO registration copy parameter 73

LL (Reset Latest Sequence Number) 6Linux and UNIX 28Linux, UNIX, and Windows

Running DTLUCBRG 39LISTALLOC 78LISTLOCATIONS 78, 80LISTTASK 78, 79loc

DTLREXE parameter 16, 17Local Mode

Adding log restrictions 63LOCATION

DTLUCBRG parameter 35LOCATION_CRG

DTLUCBRG parameter 35LOCATION_DM

DTLUCBRG parameter 35LOCATION_XDM

DTLUCBRG parameter 35Log Catalog

Adding Logs in Order 63LOGPRT

DTLUCUDB 55

MMEDIA_CONTENT

dtlulcat parameter 60MEDIA_TYPE 60

dtlulcat parameter 60MOD 28mode

DTLREXE parameter 17MSSOPTS

DTLUCBRG MS SQL parameter 37MVS LISTLOCATIONS 80MVS LISTTASK 79, 80

OOperational procedures

Adding logs to the catalog 63ORAOPTS

DTLUCBRG Oracle parameter 38ORASCHEMA 27OS/390

Running DTLUCBRG 39OS390/zOS 28OUTPUT

DTLUCBRG parameter 35output

DTLREXE parameter 17

PP (Populate PCAT Control File) 5PRIMDSN

DTLUCBRG IMS parameter 37

102 Index

PRINT 28PRINT APPL 30prog

DTLREXE parameter 16, 17PWD

DTLUCBRG Parameter 35pwd

DTLREXE parameter 16, 17

RR (Report on PCAT Control File) 6RACF_CLASS 81Register active

DTLUCBRG 36Register Inactive

DTLUCBRG 36Registration mask

DTLUCBRG 36REPLACE

DTLUCBRG parameter 35REPLACEACTIVE

DTLUCBRG parameter 35Replacing active registrations

DTLUCBRG 35Replacing registrations

DTLUCBRG 35Report columns

DTLUCBRG 35Report location

DTLUCBRG 35result

DTLREXE parameter 17REUSECRGNAME

DTLUCBRG parameter 35RPTCOLS

DTLUCBRG parameter 35RSTTKN GENERATE 24Running DTLUCBRG

Windows and OS/390 12, 38, 96

SS (Submit ADASEL) 7Sample Input

DTLUCBRG 38Sample JCL

DTLUCBRG 39SETDEF

DTLUCUDB 56SNAPSHOT

DTLUCUDB 56SR2

Scan for SR2/SR3 record combinations 49SR2OUT

DTLUCSR2 DD Card 49SR2TOTAL

DTLUCSR2 DD Card 49SR3

Scan for SR2/SR3 record combinations 49STATUS

DTLUCBRG parameter 36

STOPTASK 78submittimeout 17Supplemental log groups

DTLUCBRG 38Syntax

AS/400 67Windows and UNIX 65

TT (Submit ET Record Extraction) 7TABLE

DTLUCBRG parameter 36Test without registering

DTLUCBRG 36TESTRUN

DTLUCBRG parameter 36time

DTLREXE parameter 17TKNPARMS 27

UUDBDB

DTLUAPPL Parameter 27UID

DTLUCBRG parameter 36uid

DTLREXE parameter 16, 17User-defined Log Records 10

VV (Rebuild the PCAT Control File) 6

WWindows 28

Index 103

104 Index

NOTICES

This Informatica product (the “Software”) includes certain drivers (the “DataDirect Drivers”) from DataDirect Technologies, an operating company of Progress Software Corporation (“DataDirect”) which are subject to the following terms and conditions:

1. THE DATADIRECT DRIVERS ARE PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.

2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

PowerExchange Utilities Guide - Informatica Documentation... · 2016-09-02 · vi Table of Contents...

Documents

Transcript of PowerExchange Utilities Guide - Informatica Documentation... · 2016-09-02 · vi Table of Contents...