Informatica PowerExchange (Version 9.5.1)

Utilities Guide

Informatica PowerExchange Utilities GuideVersion 9.5.1December 2012Copyright (c) 1998-2012 Informatica. All rights reserved.This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use anddisclosure 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 internationalPatents 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 inDFARS 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013(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 inwriting.Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange,PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica OnDemand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and InformaticaMaster Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other companyand product names may be trade names or trademarks of their respective owners.Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rightsreserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rightsreserved.Copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright MetaIntegration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems Incorporated. Allrights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All rights reserved.Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights reserved. Copyright InformationBuilders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rightsreserved. Copyright International Organization for Standardization 1986. All rights reserved. Copyright ej-technologies GmbH. All rights reserved. Copyright JaspersoftCorporation. All rights reserved. Copyright is International Business Machines Corporation. All rights reserved. Copyright yWorks GmbH. All rights reserved. Copyright Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc.Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved.Copyright LogiXML, Inc. All rights reserved. Copyright 2003-2010 Lorenzi Davide, All rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Boardof Trustees of the Leland Stanford Junior University. All rights reserved. Copyright EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved.This product includes software developed by the Apache Software Foundation (http://www.apache.org/), and other software which is licensed under the Apache License,Version 2.0 (the "License"). You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0. Unless required by applicable law or agreed to in writing,software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See theLicense for the specific language governing permissions and limitations under the License.This product includes software which was developed by Mozilla (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright 1999-2006 by Bruno Lowagie and Paulo Soares and other software which is licensed under the GNU Lesser General Public License Agreement, which may be found at http://www.gnu.org/licenses/lgpl.html. The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but notlimited to the implied warranties of merchantability and fitness for a particular purpose.The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine,and Vanderbilt University, Copyright () 1993-2006, all rights reserved.This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution ofthis software is subject to terms available at http://www.openssl.org and http://www.openssl.org/source/license.html.This product includes Curl software which is Copyright 1996-2007, Daniel Stenberg, . All Rights Reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://curl.haxx.se/docs/copyright.html. Permission to use, copy, modify, and distribute this software for any purpose with or withoutfee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.The product includes software copyright 2001-2005 () MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms availableat http://www.dom4j.org/ license.html.The product includes software copyright 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http://dojotoolkit.org/license.This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding thissoftware are subject to terms available at http://source.icu-project.org/repos/icu/icu/trunk/license.html.This product includes software copyright 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http://www.gnu.org/software/ kawa/Software-License.html.This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & WirelessDeutschland. Permissions and limitations regarding this software are subject to terms available at http://www.opensource.org/licenses/mit-license.php.This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subjectto terms available at http:/ /www.boost.org/LICENSE_1_0.txt.This product includes software copyright 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http://www.pcre.org/license.txt.This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to termsavailable at http:// www.eclipse.org/org/documents/epl-v10.php.This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?License, http://www.stlport.org/doc/ license.html, http://www.asm.ow2.org/license.html, http://www.cryptix.org/LICENSE.TXT, http://hsqldb.org/web/hsqlLicense.html, http://httpunit.sourceforge.net/doc/license.html, http://jung.sourceforge.net/license.txt , http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org,http://slf4j.org/license.html, http://www.sente.ch/software/OpenSourceLicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/jsch/LICENSE.txt. http://jotm.objectweb.org/bsd_license.html; . http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http://developer.apple.com/library/mac/#samplecode/HelpHook/Listings/HelpHook_java.html; http://nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://www.sqlite.org/copyright.html, http://www.tcl.tk/

software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iODBC/License; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http://www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#FAQ; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/license.txt; http://www.schneier.com/blowfish.html;http://www.jmock.org/license.html; http://xsom.java.net; and http://benalman.com/about/license/.This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and DistributionLicense (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code LicenseAgreement Supplemental License Terms, the BSD License (http:// www.opensource.org/licenses/bsd-license.php) the MIT License (http://www.opensource.org/licenses/mit-license.php) and the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0).This product includes software copyright 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this softwareare subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For furtherinformation please visit http://www.extreme.indiana.edu/.This product includes software developed by Andrew Kachites McCallum. "MALLET: A Machine Learning for Language Toolkit." http://mallet.cs.umass.edu (2002).This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775;6,640,226; 6,789,096; 6,820,077; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110, 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422;7676516; 7,720,842; 7,721,270; and 7,774,791, international Patents and other Patents Pending.DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the impliedwarranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. Theinformation provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation issubject to change at any time without notice.NOTICESThis Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress SoftwareCorporation ("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 OFTHE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACHOF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS.

Part Number: PWX-UTG-951-0001

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiInformatica Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Informatica Customer Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiInformatica Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiInformatica Web Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixInformatica How-To Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixInformatica Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixInformatica Multimedia Knowledge Base. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixInformatica Global Customer Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1: Introduction to PowerExchange Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1PowerExchange Utilities Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1PowerExchange Utilities by Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2PowerExchange Utilities Syntax Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3PowerExchange Sample JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 2: DTLCCADW - Adabas PCAT Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5DTLCCADW Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5DTLCCADW Utility Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

P (Populate PCAT Control File) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6R (Report on PCAT Control File) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6I (Insert) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6D (Delete) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6L (Reset Latest Sequence Number) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6V (Rebuild the PCAT Control File) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6A (Add) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7S (Submit ADASEL) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7T (Submit ET Record Extraction) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7E (ET/BT Record Extraction) Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3: DTLCUIML - IMS Log Marker Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8DTLCUIML Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8DTLCUIML Utility Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8DTLCUIML Utility Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

SYSPRINT: Control Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9DFSSTAT: IMS Activity Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9User-Defined Log Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Table of Contents i

Chapter 4: DTLINFO - Release Information Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11DTLINFO Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Supported Operating Systems for the DTLINFO Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Control Statement Syntax for the DTLINFO Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Control Statement Parameters for the DTLINFO Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Running the DTLINFO Utility on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Running the DTLINFO Utility on Linux, UNIX, and Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Running the DTLINFO Utility on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13DTLINFO Utility on i5/OS Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

DTLINFO Utility on i5/OS - Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13DTLINFO Utility on i5/OS - Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

DTLINFO Utility on Linux, UNIX, and Windows Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14DTLINFO Utility on Linux, UNIX, and Windows - Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . 14DTLINFO Utility on Linux, UNIX, and Windows - Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . 14

DTLINFO Utility on z/OS Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14DTLINFO Utility on z/OS - Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14DTLINFO Utility on z/OS - Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 5: DTLREXE - Remote Execution Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16DTLREXE Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Supported Operating Systems for the DTLREXE Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Control Statement Syntax for the DTLREXE Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Control Statement Parameters for the DTLREXE Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

DELETE Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17PING Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18SUBMIT Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18SYSTEM Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Running the DTLREXE Utility on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Running the DTLREXE Utility on Linux and UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Submitting a Remote z/OS Job Specifying a PDS Member. . . . . . . . . . . . . . . . . . . . . . . . . . . 20Submitting a Remote z/OS Job Specifying a Sequential MVS Data Set. . . . . . . . . . . . . . . . . . . . 20Deleting a File from a Remote System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Running a File on a Remote System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Running the DTLREXE Utility on Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Running the DTLREXE Utility on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Running the DTLREXE Utility with PROG=SUBMIT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Running the DTLREXE Utility with PROG=PING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Running the DTLREXE Utility with PROG=DELETE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Running the DTLREXE Utility with PROG=SYSTEM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

DTLREXE Utility Usage Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23DTLREXE Utility on z/OS Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

DTLREXE Utility on z/OS Example JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

ii Table of Contents

DTLREXE Utility on z/OS Output Data Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 6: DTLUAPPL - Restart Token Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26DTLUAPPL Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Supported Operating Systems for the DTLUAPPL Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Connection Statements for the DTLUAPPL Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Connection Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Connection Statement Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Application Entry Statements for the DTLUAPPL Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28ADD and MOD Statement Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28ADD and MOD Statement Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Running the DTLUAPPL Utility on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Running the DTLUAPPL Utility on Linux, UNIX, and Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Running the DTLUAPPL Utility on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31DTLUAPPL Utility Usage Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33DTLUAPPL Utility Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Generating Restart Tokens at the Application Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Generating Restart Tokens at the Capture Registration Level. . . . . . . . . . . . . . . . . . . . . . . . . . 33Generating Restart Tokens for Continuous Extraction Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . 33Adding an Application with Restart Tokens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Adding an Application and Generating Restart Tokens on a Remote Instance . . . . . . . . . . . . . . . 34Modifying Restart Tokens in an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Modifying an Application and Adding a Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Printing an Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 7: DTLUCBRG - Batch Registration Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36DTLUCBRG Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Supported Operating Systems for the DTLUCBRG Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37DTLUCBRG Utility Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Specifying Multiple Sets of Parameters on the DTLUCBRG Utility. . . . . . . . . . . . . . . . . . . . . . . 41DTLUCBRG Utility Source-Specific Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

DTLUCBRG Code Page Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Code Page Processing for DB2 Registrations in Local Mode on z/OS. . . . . . . . . . . . . . . . . . . . 44

Running the DTLUCBRG Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Sample Input for the DTLUCBRG Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Running the DTLUCBRG Utility on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Running the DTLUCBRG Utility on Linux, UNIX, and Windows. . . . . . . . . . . . . . . . . . . . . . . . . 45Running the DTLUCBRG Utility on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

DTLUCBRG Utility Usage Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Chapter 8: DTLUCDEP - CDEP Maintenance Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49DTLUCDEP Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Supported Operating Systems for the DTLUCDEP Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Table of Contents iii

Control Statement Syntax for the DTLUCDEP Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Control Statement Parameters for the DTLUCDEP Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

CDEP Definition Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Running the DTLUCDEP Utility on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Running the DTLUCDEP Utility on Linux, UNIX, and Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Running the DTLUCDEP Utility on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51DTLUCDEP Utility on i5/OS Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53DTLUCDEP Utility on Linux, UNIX, and Windows Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54DTLUCDEP Utility on z/OS Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 9: DTLUCSR2 - IDMS SR2 and SR3 Records Utility. . . . . . . . . . . . . . . . . . . . . . . . 56DTLUCSR2 Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Running the DTLUCSR2 Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Chapter 10: DTLUCUDB - DB2 for Linux, UNIX, and Windows CDC Utility . . . . . . . . . . 58DTLUCUDB Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Running the DTLUCUDB Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

DTLUCUDB Utility Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Command Options for the DTLUCUDB Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Gathering Diagnostic Information to Resolve a DB2 Capture Problem. . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 11: DTLULCAT and DTLULOGC - IDMS Log Catalog Utilities. . . . . . . . . . . . . . . 66DTLULCAT and DTLULOGC Utilities Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Running the DTLULCAT Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Running the DTLULOGC Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Manually Manipulating the Log Catalog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Guidelines for Adding Logs to the Catalog with the DTLULCAT and DTLULOGC Utilities. . . . . . . . . . . 71

Chapter 12: DTLURDMO - Data Map Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72DTLURDMO Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Supported Operating Systems for the DTLURDMO Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Control Statement Overview for the DTLURDMO Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Control Statement Syntax for the DTLURDMO Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Control Statements and Parameters for the DTLURDMO Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Global Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74DM_COPY Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77REG_COPY Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83XM_COPY Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Running the DTLURDMO Utility on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Running the DTLURDMO Utility on Linux, UNIX, and Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Running the DTLURDMO Utility on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96DTLURDMO Utility Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Copying Selected Data Maps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

iv Table of Contents

Copying All Data Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Copying and Modifying Data Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Copying Registrations and Generating Extraction Maps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Copying Registrations, Generating Extraction Maps, and Merging Extraction Maps with Bulk DataMaps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Copying IMS Data Maps and Copying and Modifying Registrations. . . . . . . . . . . . . . . . . . . . . . 98Copying IMS Data Maps and Registrations and Modifyng the IMSID Data Map Property. . . . . . . . 99

Scope of Operands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Chapter 13: DTLUTSK - Task Control Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103DTLUTSK Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103DTLUTSK Command Line Utility on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103DTLUTSK Command Line Utility on Linux, UNIX, and Windows. . . . . . . . . . . . . . . . . . . . . . . . . . 104

DTLUTSK Utility Help on Linux, UNIX, and Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105DTLUTSK Job on MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

DTLUTSK Job on MVS - Example JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106DTLUTSK Job on MVS - Example Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

DTLUTSK Command Line Utility on MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106LISTTASK Command on MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107STOPTASK Command on MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107LISTLOCATIONS Command on MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107LISTALLOC Command on MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107FREEALLOC Command on MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Running the DTLUTSK Utility in the PowerExchange Navigator. . . . . . . . . . . . . . . . . . . . . . . . . . . 108DTLUTSK Utility Security Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

DTLUTSK Utility Security Requirements on MVS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109DTLUTSK Utility Security Requirements on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Using Signon.txt to Authorize Users to Display or Stop Tasks. . . . . . . . . . . . . . . . . . . . . . . . . 109

Chapter 14: EDMLUCTR - Log Scan and Print Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110EDMLUCTR Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Supported Operating Systems for the EDMLUCTR Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Control Statement Syntax for the EDMLUCTR Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Control Statement Parameters for the EDMLUCTR Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

-SEL Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111-MASK Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Running the EDMLUCTR Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112EDMLUCTR Utility Usage Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113EDMLUCTR Utility Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

EDMLUCTR Utility - Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113EDMLUCTR Utility - Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114EDMLUCTR Utility - Example 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115EDMLUCTR Utility - Example 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Table of Contents v

Chapter 15: EDMXLUTL - Event Marker Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117EDMXLUTL Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Creating an Event Marker in Batch Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117EDMXLUTL Utility JCL Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118EDMXLUTL Utility Control Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118EDMXLUTL Utility EVENT Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

EVENT Command Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119EVENT Command Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

Keyword Sets for the BASEEDM Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119MARK Keyword Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120NOTIFY Keyword Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

EDMXLUTL Utility Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Chapter 16: HOSTENT - TCP/IP Address Reporter Utility. . . . . . . . . . . . . . . . . . . . . . . . . . 123HOSTENT Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Supported Operating Systems for the HOSTENT Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Running the HOSTENT Utility on i5/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Running the HOSTENT Utility on Linux and UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Running the HOSTENT Utility on z/OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124HOSTENT Utility Usage Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

HOSTENT Utility Resolver Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125HOSTENT Utility Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125HOSTENT Utility on i5/OS Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126HOSTENT Utility on Linux and UNIX Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126HOSTENT Utility on z/OS Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Chapter 17: PWXUCDCT - Logger for Linux, UNIX, and Windows Utility. . . . . . . . . . . 128PWXUCDCT Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Supported Operating Systems for the PWXUCDCT Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Control Statement Syntax for PWXUCDCT Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129PWXUCDCT Commands and Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Summary of Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Parameter Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Running the PWXUCDCT Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Usage Notes for the PWXUCDCT Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Examples of PWXUCDCT Utility Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Example 1. Creating a Backup of the CDCT File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Example 2. Restoring the CDCT File from a Backup File. . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Example 3. Re-creating the CDCT File After a Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Example 4. Reporting and Deleting Orphan CDCT Records. . . . . . . . . . . . . . . . . . . . . . . . . . 136Example 5. Reporting and Deleting Expired CDCT Records . . . . . . . . . . . . . . . . . . . . . . . . . 137Example 6. Determining Why a Checkpoint Was Done. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

vi Table of Contents

Example 7. Warm Starting the PowerExchange Logger to an Earlier Point in Time. . . . . . . . . . . 138

Chapter 18: PWXUCREG - Capture Registration Suspend Utility. . . . . . . . . . . . . . . . . . 140PWXUCREG Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140PWXUCREG Usage Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Supported Operating Systems for the PWXUCREG Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Suspending Change Capture for Registered Sources Temporarily. . . . . . . . . . . . . . . . . . . . . . . . . 142General Syntax for PWXUCREG Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Summary of PWXUCREG Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Global SET_CONTROL_VALUE Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Registration-specific Command Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Running the PWXUCREG Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Examples of PWXUCREG Utility Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Example 1. Suspending a Capture Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Example 2. Reactivating a Capture Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Chapter 19: PWXUDMX - Data Maps Update Time ECSA Memory Utility. . . . . . . . . . . . 155PWXUDMX Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Supported Operating Systems for the PWXUDMX Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Running the PWXUDMX Utility on z/OS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156PWXUDMX Commands and Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156

CREATE_ECSA Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157DECREMENT_FILE_COUNT Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157DELETE_ECSA Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157DISPLAY_ECSA Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157DUMP_ECSA Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157INCREMENT_FILE_COUNT Command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Chapter 20: PWXUSSL - PowerExchange SSL Reporting Utility. . . . . . . . . . . . . . . . . . . 159PWXUSSL Utility Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Supported Operating Systems for the PWXUSSL Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Running the PWXUSSL Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Certificate Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Ciphers Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Version Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Table of Contents vii

PrefaceThis guide describes a collection of utility programs that are designed to aid maintenance of your PowerExchangeinstallation.This guide 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://mysupport.informatica.com. The site contains product information, user group information, newsletters,access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library,the Informatica Knowledge Base, the Informatica Multimedia Knowledge Base, Informatica ProductDocumentation, and access to the Informatica user community.

Informatica DocumentationThe Informatica Documentation team takes every effort to create accurate, usable documentation. If you havequestions, comments, or ideas about this documentation, contact the Informatica Documentation team throughemail at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let usknow if we can contact you regarding your comments.The Documentation team updates documentation as needed. To get the latest documentation for your product,navigate to Product Documentation from http://mysupport.informatica.com.

viii

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

Informatica How-To LibraryAs an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com.The How-To Library is a collection of resources to help you learn more about Informatica products and features. Itincludes articles and interactive demonstrations that provide solutions to common problems, compare features andbehaviors, and guide you through performing specific real-world tasks.

Informatica Knowledge BaseAs an Informatica customer, you can access the Informatica Knowledge Base at http://mysupport.informatica.com.Use the Knowledge Base to search for documented solutions to known technical issues about Informaticaproducts. You can also find answers to frequently asked questions, technical white papers, and technical tips. Ifyou have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Baseteam through email at KB_Feedback@informatica.com.

Informatica Multimedia Knowledge BaseAs an Informatica customer, you can access the Informatica Multimedia Knowledge Base at http://mysupport.informatica.com. The Multimedia Knowledge Base is a collection of instructional multimedia filesthat help you learn about common concepts and guide you through performing specific tasks. If you havequestions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Baseteam through email at KB_Feedback@informatica.com.

Informatica Global Customer SupportYou can contact a Customer Support Center by telephone or through the Online Support. Online Support requiresa user name and password. You can request a user name and password at http://mysupport.informatica.com.Use the following telephone numbers to contact Informatica Global Customer Support:

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

Toll FreeBrazil: 0800 891 0202Mexico: 001 888 209 8853North America: +1 877 463 2435

Toll FreeFrance: 0805 804632Germany: 0800 5891281Italy: 800 915 985Netherlands: 0800 2300001Portugal: 800 208 360Spain: 900 813 166Switzerland: 0800 463 200United Kingdom: 0800 023 4632 Standard Rate

Toll FreeAustralia: 1 800 151 830New Zealand: 09 9 128 901 Standard RateIndia: +91 80 4112 5738

Preface ix

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

Belgium: +31 30 6022 797France: +33 1 4138 9226Germany: +49 1805 702 702Netherlands: +31 306 022 797United Kingdom: +44 1628 511445

x Preface

C H A P T E R 1

Introduction to PowerExchangeUtilities

This chapter includes the following topics: PowerExchange Utilities Overview, 1 PowerExchange Utilities by Operating System, 2 PowerExchange Utilities Syntax Conventions, 3 PowerExchange Sample JCL, 4

PowerExchange Utilities OverviewThis guide is intended for PowerExchange administrators who run one or more utilities to manage theirPowerExchange installations.Each chapter provides some or all of the following reference information for a specific utility: The tasks that you can complete with the utility Any prerequisites to running the utility The systems 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 systems Examples of utility syntax by operating system, task, or bothPowerExchange 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

system log data set (SLDS). 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 CDEP file with specified applications and

capture registrations.

1

DTLUCBRG - Batch registration utility. Use the DTLUCBRG utility to add or modify capture registrations andextraction 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. 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 tocapturing changes.

EDMXLUTL - Event marker utility. Use EDMXLUTL to create an event marker in your PowerExchange Logger. HOSTENT - TCP/IP Address Reporter Utility. Use HOSTENT to display the TCP/IP host name and address for

a system and to diagnose problems with PowerExchange communication and licensing. PWXUCDCT - PowerExchange Logger for Linux, UNIX, and Windows utility. Use PWXUCDCT to manage and

regenerate the CDCT file, delete log files that are not referenced by CDCT records, and print reports on theCDCT file, checkpoint files, and log files.

PWXUCREG - PowerExchange Capture Registration Suspend Utility. Use PWXUCREG to temporarily suspendchange capture processing for registered sources. Later, you can use the utility to reactivate the suspendedregistrations to resume change capture.

PWXUDMX - PowerExchange Data Maps Update Time ECSA memory utility. Use PWXUDMX to allocate,display, and delete ECSA memory, which holds time stamps of the latest updates to data maps files, and tomodify the use counts of a file.

PWXUSSL - PowerExchange SSL Reporting Utlity. Use PWXUSSL to generate reports about SSL libraries andcertificates on Linux, UNIX, and Windows.

PowerExchange Utilities by Operating SystemThe following table lists the operating systems on which each utility can run. If the utility is available only forspecific databases, those databases are listed.

Utility Linux UNIX Windows z/OS i5/OS

DTLCCADW Yes, for Adabasonly

DTLCUIML Yes, for IMS only

DTLINFO Yes Yes Yes Yes Yes

DTLREXE Yes Yes Yes Yes Yes

2 Chapter 1: Introduction to PowerExchange Utilities

Utility Linux UNIX Windows z/OS i5/OS

DTLUAPPL Yes Yes Yes Yes Yes

DTLUCBRG Yes Yes Yes Yes Yes

DTLUCDEP Yes Yes Yes Yes Yes

DTLUCSR2 Yes, for IDMSCDC only

DTLUCUDB Yes, for DB2only

Yes, for DB2only

Yes, for DB2only

DTLULCAT andDTLULOGC

Yes, for IDMSLog-Based CDConly

DTLURDMO Yes Yes Yes Yes Yes

DTLUTSK Yes Yes Yes Yes Yes

EDMLUCTR Yes

EDMXLUTL Yes

HOSTENT Yes Yes Yes Yes

PWXUCDCT Yes Yes Yes

PWXUCREG Yes

PWXUDMX Yes

PWXUSSL Yes Yes Yes

PowerExchange Utilities 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 anditalics, for example, instance.

Square brackets [ ] indicate optional parameters. You can consider any parameters without these brackets tobe required.

A vertical bar | separates alternative options of which one can be entered for a parameter. Single braces { } enclose alternative entries. Use only one of the entries. Do not type the braces when you

enter the option. Underlining indicates the default option for a parameter, if available. Italics indicate a variable or positional parameter for which the value varies.

PowerExchange Utilities Syntax Conventions 3

PowerExchange 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 z/OSInstallation Assistant, the installation process moves the sample JCL to the HLQ.DTLEXPL library.

4 Chapter 1: Introduction to PowerExchange Utilities

C H A P T E R 2

DTLCCADW - Adabas PCAT UtilityThis chapter includes the following topics: DTLCCADW Utility Overview, 5 DTLCCADW Utility Functions, 5

DTLCCADW Utility OverviewThe PCAT utility program, DTLCCADW, is used by the Adabas ECCR process to manipulate the contents of thePCAT file. The PCAT utility is controlled by settings of the parameters passed via the PARM= on the EXECstatement. There are examples of the JCL required for each function in the PowerExchange DTLEXPL library withnames DTLCCADx, where x corresponds to the parameter value.Typically, these functions are used only internally by PowerExchange. However, there may be times when manualoverrides are desired, which are described below. When in doubt about usage, contact Informatica GlobalCustomer Support.

DTLCCADW Utility FunctionsThe DTLCCADW utility has the following 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)

5

P (Populate PCAT Control File) FunctionExample job DTLCCADP - no other parameters are required.This function may be used after the VSAM Control File has been initially established with its 999999999 controlrecord, to pre-populate the PCAT file with previously-created PLOG data set names. By default, when the AdabasPowerExchange ECCR is started, only the most recent archived PLOG will be recognized. So, if there is a need tocollect older captured changes, this is the function to use. The list of data set names is input through DDCARDDTLCCADF either directly as SYSIN, or in a file of 80-byte card images. It is the user's responsibility to obtainthose PLOG data set names. The 999999999 PCAT control record is then updated with the highest sequencenumber added.Note: Use this function only after initializing the control file, not after normal operation has begun.

R (Report on PCAT Control File) FunctionExample 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 filesequence number from where the report will commence. If no second parameter is specified then the whole file isprinted to SYSOUT.Note: The following functions may be of use in case of operational PLOG difficulties, not related to the AdabasPowerExchange Change processing. For instance, if the PLOG files get out of sequence operationally, thesefunctions will ensure that the PCAT can be reset to correct data set name sequence, as well.

I (Insert) FunctionExample 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 nameof a PLOG to be inserted. Note - DTLCCADW does NOT check that the PLOG is in the correct chronologicalsequence - it is the user's responsibility to ensure this.

D (Delete) FunctionExample 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 beadded, you must immediately run the L function (see below) to reset the latest key value in the 999999999 controlrecord.

L (Reset Latest Sequence Number) FunctionExample job DTLCCADL - no other parameters are required.This function re-populates the latest sequence number added field in the 999999999 PCAT control record. Theonly 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) FunctionExample 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.

6 Chapter 2: DTLCCADW - Adabas PCAT Utility

A (Add) FunctionExample 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 PCATfile, taking the highest sequence number so far added and adding 100 to it (gaps are left in the sequence in caseolder PLOGs need to be inserted into the sequence later). This function is automatically invoked during the PLOGflip in the JCL executing the PLCOPY function and so should not be necessary to invoke manually, in normaloperation.

S (Submit ADASEL) FunctionExample 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 forthe PLOG data set name recorded in the control record. It submits the job which runs the ADASEL and creates anoutput file, the data set name of which is recorded in the control record. This function is automatically invoked bythe ECCR and so should not be necessary to invoke manually in normal operation.

T (Submit ET Record Extraction) FunctionExample job DTLCCADT - requires a second parameter of PCAT file sequence number.DTLCCADW reads the PCAT control record specified by the sequence number and constructs anotherDTLCCADW job for the PLOG recorded in the control record, building a data set name for the output ET file usingdate and time parameters. It submits the job which reads the PLOG specified in the control record and creates anoutput file of ET/BT records, the data set name of this file then being recorded in the control record. This functionis normally invoked by the ECCR and so should not be necessary to invoke manually in normal operation.

E (ET/BT Record Extraction) FunctionExample 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 ECCRnormally controls this operation and this function is only provided in case of difficulties which might require manualintervention.

DTLCCADW Utility Functions 7

C H A P T E R 3

DTLCUIML - IMS Log Marker UtilityThis chapter includes the following topics: DTLCUIML Utility Overview, 8 DTLCUIML Utility Parameters, 8 DTLCUIML Utility Reports, 9

DTLCUIML Utility OverviewUse the DTLCUIML utility to define a marker for the IMS log-based ECCR in the IMS system log data set (SLDS).Once the IMS log-based ECCR encounters one of the markers, it triggers a message in the PowerExchangeLogger 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 startpoint for an extraction.There is no limit or restriction on the number of markers being set in the IMS SLDS. The IMS Log Record IDchosen has to be unique for the individual installation, and the number needs to be part of the input parameters forthe 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 canuse any PSB as long as the first PCB in the PSB is an IOPCB. The utility uses the IMS LOG Call to write IMS logrecords.This utility must run as an IMS BMP job. This ensures that the IMS Log record is written into the IMS logstreamand that the associated log is read by the IMS log-based Collector. In an IMS DCI situation the DTLUAPPL utilityhas to be used to establish an extraction point for the changed data.

DTLCUIML Utility ParametersEach SYSIN record contains the following parameters: DBDNAME. IMS DBD name. DBID. IMS instance (Recon Identifier).

8

RECID. A value in (uppercase) hexadecimal from A0 through 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 ascomments.Example:

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

DTLCUIML Utility ReportsFile 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.

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 arezero.

DTLCUIML Utility Reports 9

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 IMSsuffix 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 InformationUtility

This chapter includes the following topics: DTLINFO Utility Overview, 11 Supported Operating Systems for the DTLINFO Utility, 11 Control Statement Syntax for the DTLINFO Utility, 12 Control Statement Parameters for the DTLINFO Utility, 12 Running the DTLINFO Utility on i5/OS, 12 Running the DTLINFO Utility on Linux, UNIX, and Windows, 12 Running the DTLINFO Utility on z/OS, 13 DTLINFO Utility on i5/OS Examples, 13 DTLINFO Utility on Linux, UNIX, and Windows Examples, 14 DTLINFO Utility on z/OS Examples, 14

DTLINFO Utility OverviewUse 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 hotfix. For example, use the utility to determine the

maintenance level of your PowerExchange software at the request of Informatica Global Customer Support.

Supported Operating Systems for the DTLINFO UtilityThe DTLINFO utility can run on the following operating systems: i5/OS Linux and UNIX Windows z/OS

11

Control Statement Syntax for the DTLINFO UtilityUse the following syntax:

DTLINFO [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. Themodule name is the name of any program included in your PowerExchange installation.

Control Statement Parameters for the DTLINFO UtilityThe 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 the DTLINFO Utility on i5/OSTo run the DTLINFO utility on i5/OS:u To view release information for PowerExchange, enter:

CALL PGM(dtllib/DTLINFO) To view release information for a PowerExchange module, enter:

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

Running the DTLINFO Utility on Linux, UNIX, andWindows

To run the DTLINFO utility on Linux, UNIX, and Windows:1. Navigate to the Informatica PowerExchange directory.2. 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

12 Chapter 4: DTLINFO - Release Information Utility

Running the DTLINFO Utility on z/OSThe JCL for the DTLINFO utility is located in hlq.RUNLIB(DTLINFO), where hlq is the high-level qualifier used forinstalling 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.To run the DTLINFO utility on z/OS:1. 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 asshown 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 PARMvalue. Also, supply the library and member name for the module by using the SYSIN DD as shown in thefollowing 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=*

The JCL statements are:EXEC PGM=DTLINFO

Invokes the utility.STEPLIB DD

Defines the PowerExchange LOAD library that contains the utility.SYSPRINT DD

Defines the print location for the report.2. Submit the DTLINFO job.

DTLINFO Utility on i5/OS ExamplesThe following are examples of the DTLINFO utility on i5/OS.

DTLINFO Utility on 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-yyyyThis Software is protected by U.S. Patent Numbers patents.Segment#Revision :Build :

Running the DTLINFO Utility on z/OS 13

DTLINFO Utility on i5/OS - Example 2The following command displays the release information for the PowerExchange module DTLREXE:

CALL DTLINFO DTLREXE

The resulting output is:DTLINFO Embedded Version History:Copyright: Informatica Corporation. yyyy-yyyyThis Software is protected by U.S. Patent Numbers patents.Segment#Revision :Build :DTLINFO AS400 Module Segments For DTLREXESegment#Revision :Built :

DTLINFO Utility on Linux, UNIX, and WindowsExamples

The following are examples of the DTLINFO utility on Linux, UNIX, and Windows.

DTLINFO Utility on Linux, UNIX, and Windows - Example 1The following command displays the release information for PowerExchange:

dtlinfo

DTLINFO Utility on Linux, UNIX, and Windows - Example 2The following command displays the release information for the PowerExchange module DTLREXE:

dtlinfo dtlrexe.exe

DTLINFO Utility on z/OS ExamplesThe following are examples of the DTLINFO utility on z/OS.

DTLINFO Utility on z/OS - 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=*

DTLINFO Utility on z/OS - Example 2The following JCL EXEC statement specifies the PowerExchange module DTLREXE as the PARM value. Also, thefollowing SYSIN DD provides the library and member name for the module:

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

14 Chapter 4: DTLINFO - Release Information Utility

//SYSIN DD DISP=SHR,DSN=hlq.LOADLIB(DLTREXE)//SYSPRINT DD SYSOUT=*

DTLINFO Utility on z/OS Examples 15

C H A P T E R 5

DTLREXE - Remote ExecutionUtility

This chapter includes the following topics: DTLREXE Utility Overview, 16 Supported Operating Systems for the DTLREXE Utility, 16 Control Statement Syntax for the DTLREXE Utility, 17 Control Statement Parameters for the DTLREXE Utility, 17 Running the DTLREXE Utility on i5/OS, 20 Running the DTLREXE Utility on Linux and UNIX, 20 Running the DTLREXE Utility on Windows, 21 Running the DTLREXE Utility on z/OS, 21 DTLREXE Utility Usage Notes, 23 DTLREXE Utility on z/OS Example, 24

DTLREXE Utility OverviewUse the DTLREXE utility to perform the following tasks: Ping a remote PowerExchange Listener. Submit a remote z/OS job. Delete a file from a remote system. Run a file on a remote system.

Supported Operating Systems for the DTLREXE UtilityThe DTLREXE utility can run on the following operating systems: i5/OS UNIX and Linux Windows

16

z/OS

Control Statement Syntax for the DTLREXE UtilityUse the following syntax for the DTLREXE utility control statements:

prog=deleteloc=locationparms=file_name[uid=userid][{pwd=password|epwd=epassword}] prog=pingloc=location[uid=userid][{pwd=password|epwd=epassword}] prog=submit loc=location [uid=userid] [{pwd=password|epwd=epassword}] [fn="your jcl"] [mode=(job|task},{wait|nowait|timed)] [time=] [submittimeout=timeout_in_seconds] [output=output.file] [result=result.file]prog=systemloc=location parms=file_name

Control Statement Parameters for the DTLREXE UtilityDTLREXE has the following statements: DELETE PING SUBMIT SYSTEM

DELETE StatementUse DTLREXE DELETE to delete a file from the platform where the PowerExchange Listener is running.DELETE has the following parameters:loc

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

Required. The name of the file to delete. On z/OS, if you do not enclose the name in quotes, the utilityprovides them.

progRequired. Set to DELETE.

Control Statement Syntax for the DTLREXE Utility 17

{pwd|epwd}Optional. Password for target platform. pwd. Password for target platform in clear text. epwd. Encrypted password. Use the PowerExchange Navigator to generate an encrypted password.In pwd, non alphanumeric characters must be enclosed in quotes (). Therefore, a password cannot have anembedded double quote.

uidOptional. User ID for the target platform.

PING StatementUse DTLREXE PING to prove basic connectivity to a PowerExchange Listener. You must configure a node in theDBMover configuration file on the machine from which you issue the DTLREXE PING.PING has the following parameters:loc

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

Required. Set to PING.{pwd|epwd}

Optional. Password for target platform. pwd. Password for target platform in clear text. epwd. Encrypted password. Use the PowerExchange Navigator to generate an encrypted password.In pwd, non alphanumeric characters must be enclosed in quotes (). Therefore, a password cannot have anembedded double quote.

idOptional. User ID for the target platform.

SUBMIT StatementUse DTLREXE SUBMIT to submit a z/OS job to a remote platform or server.Alternatively, you can supply the cs parameter to point to a parameter file that contains all the required parameters.

dtlrexe cs=

SUBMIT has the following parameters:fn

Optional. The name of the file containing the JCL to be submitted including the job name. Use the followingformat:

fn=dtlusr.jcl(yourjob)

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

18 Chapter 5: DTLREXE - Remote Execution Utility

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. Use 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.prog

Required. Set to SUBMIT.pwd/epwd

Optional. Password for target platform. pwd. Password for target platform in plain text. epwd. Encrypted password. Use the PowerExchange Navigator to generate an encrypted password.In pwd, non alphanumeric characters must be enclosed in quotes (). Therefore, a password cannot have anembedded double quote.

resultOptional. The file in which the results from the job are written on the client side platform where DTLREXE isrun.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.

SYSTEM StatementUse DTLREXE SYSTEM to run a file from the path or steplib. You can specify any file that can be run, such as abatch file, rexx, or executable file.SYSTEM has the following parameters.

Control Statement Parameters for the DTLREXE Utility 19

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

parmsRequired. The name of the file to run.

progRequired. Set to SYSTEM.

Running the DTLREXE Utility on i5/OSTo run the DTLREXE utility on i5/OS:u 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)

Running the DTLREXE Utility on Linux and UNIXYou can run the DTLREXE utility on Linux and UNIX specifying either a PDS member or a sequential MVS dataset.

Submitting a Remote z/OS Job Specifying a PDS MemberTo submit a remote z/OS job specifying a PDS member:u Enter the following command, specifying a PDS member as follows:

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

Alternatively, you can enter the following command:dtlrexe prog=submit cs=/usr/pwx/MyParameterFile.txt

Submitting a Remote z/OS Job Specifying a Sequential MVS Data SetTo submit a remote z/OS job specifying a sequential MVS data set:u Enter the following command, specifying a sequential MVS data set as follows:

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

Alternatively, you can enter the following command:dtlrexe prog=submit loc=remlist fn="dtlusr.load.jcl", mode='('job,wait')', output=dtlusr.output, result=/usr/pwx/output.txt

20 Chapter 5: DTLREXE - Remote Execution Utility

Deleting a File from a Remote SystemTo delete a file from a remote system:u Enter the following command:

dtlrexe prog=delete loc=location parms=file_name

Running a File on a Remote SystemTo run a file on a remote system:u Enter the following command:

dtlrexe prog=system loc=location parms=file_nameFor example:

dtlrexe prog=system loc=node1 parms=Q:/\mydir/\myprog.bat

Running the DTLREXE Utility on WindowsTo run the DTLREXE utility on Windows:u Enter the following command:

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

Alternatively, you can enter the following command:dtlrexe prog=submit cs=c:\PowerExchange\MyParameterFile.txt

RELATED TOPICS: Running the DTLREXE Utility on Linux and UNIX on page 20

Running the DTLREXE Utility on z/OSYou can run the DTLREXE utility on z/OS with PROG=SUBMIT, PROG=PING, PROG=DELETE, orPROG=SYSTEM. In each case, the JCL statements are:JOB

Initiates the job.EXEC PGM=DTLREXE

Invokes the utility.STEPLIB DD

Defines the PowerExchange LOAD library that contains the utility.SYSPRINT DD

Defines the print location for the report.

Running the DTLREXE Utility on Windows 21

Running the DTLREXE Utility with PROG=SUBMITTo run the DTLREXE utility with PROG=SUBMIT:1. Edit the DTLREXE job JCL. 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

Then use the following JCL for the DTLREXE job step://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)"

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

2. Verify the JCL.3. Submit the DTLREXE job.

Running the DTLREXE Utility with PROG=PINGTo run the DTLREXE utility with PROG=PING:1. 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=*

Enter the location of the PowerExchange Listener in the loc parameter.2. Submit the DTLREXE job.

Running the DTLREXE Utility with PROG=DELETETo run the DTLREXE utility with PROG=DELETE:1. Edit the job that you intend to submit using DTLREXE as follows:

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

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

22 Chapter 5: DTLREXE - Remote Execution Utility

2. Submit the DTLREXE job.

Running the DTLREXE Utility with PROG=SYSTEMTo run the DTLREXE utility with PROG=SYSTEM:1. Edit the job that you intend to submit using DTLREXE as follows:

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

Enter the location of the PowerExchange Listener in the loc parameter.2. Submit the DTLREXE job.

DTLREXE Utility 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:

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 hasfinished.The %ENDJOB steps have to be included manually and are shown in the sample JCL. If the submittedjob fails with a return code greater than four, rc=16 is returned back to DTLREXE on the client.

To print help on the utility, run DTLREXE without any parameters.

DTLREXE Utility Usage Notes 23

DTLREXE Utility on z/OS ExampleTo launch DTLREXE from a z/OS 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 definesthe inline DD:

//INCMD DD *LOC=NODE1 PROG=SUBMIT FN="DTLUSR.JCL(MYJOB)"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)"

DTLREXE Utility on z/OS Example JCLThis example uses the following 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)"

DTLREXE Utility on z/OS Output Data SetThe output parameter indicates a data set that 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 specifiedby the result= parameter.The format of the output is:

timestamp|jobid|text

24 Chapter 5: DTLREXE - Remote Execution Utility

An 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