File-AID/Related Data XPERT

Reference

Release 17.02
2 File-AID/RDX Reference

Please direct questions about File-AID/RDX

or comments on this document to:

Compuware Support Center

https://go.compuware.com/

This document and the product referenced in it are subject to the following legends:

Copyright 1994-2019 Compuware Corporation. All rights reserved. Unpublished rights reserved under the
Copyright Laws of the United States.

U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as
set forth in Compuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-
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. Compuware Corporation.

This product contains confidential information and trade secrets of Compuware Corporation. Use, disclosure, or
reproduction is prohibited without the prior express written permission of Compuware Corporation. Access is
limited to authorized users. Use of this product is subject to the terms and conditions of the user’s License
Agreement with Compuware Corporation.

File-AID/Related Data XPERT, File-AID/RDX, File-AID for DB2, File-AID, File-AID Data Privacy, Compuware,
Compuware Workbench, and Topaz Workbench are trademarks or registered trademarks of Compuware
Corporation.

IBM, Db2, DB2, z/OS, and RACF are trademarks of International Business Machines Corporation.

Adobe ® Reader® is a trademark of Adobe Systems Incorporated in the United States and/or other countries.

All other company and product names are trademarks or registered trademarks of their respective owners.

Doc. JUL2019
June 19, 2019.
 3

Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
How This Manual is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Alerts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Notation Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Reading the Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Compuware Support Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Product Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Invoking File-AID/RDX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
File-AID/RDX Primary Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Option 0—Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Option 1—Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Option 2—Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Option 3—Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Option 4—Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Option 5—Data Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Option 6—Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Option G—Global Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Option FD—FADB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Option C—Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Option T—Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Option X—Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Screen Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Pattern Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Escape Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Double-Byte Character Set (DBCS) Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Column Name Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Types of Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Option Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Option Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Scrollable Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Pop-Up Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Scrolling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Scrollable Fields for Db2 Long Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Long Name Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Using the LEFT and RIGHT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4 File-AID/RDX Reference

Using the EXPAND Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Command Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Assign PF Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Concatenate Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Stacking Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
ISPF/PDF JUMP Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Terminal Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Program Access (PA) Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Program Function (PF) Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Terminal Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
DB2 Subsystem ID Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
DB2 Call Attach Alert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
File-AID/RDX Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Relationship File Compatibility Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Relationship File characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Relationship File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Creating and Loading the Relationship File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Using the Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Reviewing Relationships in the File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Using Relationship Definitions from Another Db2 Subsystem . . . . . . . . . . . . . . . . . . 43
Conditional AR Criteria File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Extract/Load/Delete Request File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Dynamic Reallocation of Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Extract Summary File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Discard File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
User Profile File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Disguise Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Disguise Criteria File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Audit Trail File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Execute Saved Request (ESR) JCL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Object Override File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
SC (Selection Criteria) Override File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Option FD—Transfer to File-AID for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Profiles and Global Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Option 0—Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Select Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Editing the Profile Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Locking a Profile Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Session and Batch Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Extract Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Load Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Disguise Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
 5

Privacy Repository List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Privacy Project List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Permanent File Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Temporary File Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Option G—Global User Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Relationship Facilitator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Relationship File Compatibility Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Relationship File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Db2 Referential Integrity (RI) Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Application Relationships (AR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Conditional (“Data Driven”) Application Relationships (AR-C) . . . . . . . . . . . . . . . . . . . . . 86
Considerations for MVS Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Use of Db2 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
DB2 Relationship Facilitator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
DB2 Object List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Table List in Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Table List - SYSIBM.SYSTABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
MVS Relationship Facilitator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
MVS Object List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Object List in Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Relationship Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Graphical Relationship Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Understanding the Graphical Relationship Display . . . . . . . . . . . . . . . . . . . . . . . . . 105
Option List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Relationship Information Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
DB2 RI Update Online Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
RI Relationship Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
RI Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Application Relationship Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Relationship Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Add Relationships — Specify Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Add Application Relationships — DB2 to DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Add Relationships — DB2 to MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Add Relationships — DB2 to IMS and Output Key Files . . . . . . . . . . . . . . . . . . . . . . . . . 130
Add Relationships — MVS to DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Add Relationships — MVS to MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Add Relationships — MVS to IMS and Output Key Files . . . . . . . . . . . . . . . . . . . . . . . . . 140
Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Relationship Condition Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Selection Criteria Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Formatted Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Field Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Primary Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Building Column/Field Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
6 File-AID/RDX Reference

Extended Column Relationship Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Rules for DECIMAL/FIXPIC and CHARACTER Columns/Fields . . . . . . . . . . . . . . . . . . . . . 171
Extended Column Relationships Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Specify MVS Field Subscripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Allocate Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Batch RI Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Print Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Formatted Relationship Report Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Print Options Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Edit Print JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Relationship File - Related Objects Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Determining Which Rows Will Be Extracted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Selecting a Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Determining the Scope of the Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Using Relationship Definitions Across Db2 Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Stopping/Resuming Batch Extract Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Stop Extract Execution with z/OS Operator MODIFY Command. . . . . . . . . . . . . . . 202
Cloning Extract Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Support for Db2 XML and LOB Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Support for Db2 Temporal Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Support for Db2 Archive Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
GDG Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Download File-AID/RDX Extract Data to the Workstation Environment. . . . . . . . . . . . . . 203
Extract Driving Object - Single Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Extract - DB2 Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Use of Db2 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Use of Aliases and Synonyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Extract - MVS Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Extract Reference List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Request File Member List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Extract Requests from Releases prior to Release 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
DB2 Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Use of Db2 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Use of Aliases and Synonyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Relationship Listing Window for Db2 Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Modify Extract Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Modify Extract Request - Object Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Save Cloned Extract Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
SAVE Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
MVS Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
 7

Relationship Listing Window—No Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

MVS Catalog Utility File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
PDS Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
XREF Select Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Extract Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Extract Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Driving Object - DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Driving Object - MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Extract Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
SELECT FROM Temporal Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Extract Scope - Object View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Extract Scope - Relationship Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Extract Scope - Relationship Sampling Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
Extract Scope - Relationship Navigation Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Graphical Relationship Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Relationship Information Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Check Extract Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Update Saved Request Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Unrelated Object Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Add Unrelated DB2 Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Unrelated Object Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Modify Unrelated MVS Object Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Input Key File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Input Key File - Positional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Input Key File - Delimited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Object Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Object Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
SQL Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
MVS File Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Selection Criteria Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
Formatted Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Field Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Primary Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Selection Criteria Record Layout Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Selection Criteria for XREFs and Multiple Record Type Files . . . . . . . . . . . . . . . . . . 328
Output Key Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Output Key File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Output Key Files List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Output Key File Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
Extract File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Data Privacy Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Supporting File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Checkpoint/Resumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Checkpoint/Resumption Confirmation Windows . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Continue With Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
8 File-AID/RDX Reference

Save Extract Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

SAVE Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
XVJPRINT Execution Log Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Optional Data Privacy Report Output Written to a File . . . . . . . . . . . . . . . . . . . . . . 355
Optional Source Data Identifiers (SDIs) Override During Execution. . . . . . . . . . . . . 356
Override Data Privacy Environment Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Override Execution Parameter in a Data Privacy Project . . . . . . . . . . . . . . . . . . . . . 357
Multiple Origins for a Data Privacy Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Special Instructions for Oracle Translate Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Redirect File-AID/Data Solutions Report (Data Disguise with DCF only). . . . . . . . . . 360
Control Card Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
View REXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Submit JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Execute Rexx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Interactive Extract Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Interactive Extract Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Miscellaneous Extract Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Extract JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
DD statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
EXTPARMS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Db2 Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
File-AID/RDX Extract/Load/Delete Request File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Obsolete Record Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
File-AID/RDX Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
Product Record — 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Header Record — H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
Base Table Record — B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
Database Create Record — F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Tablespace Create Record — G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
Db2 Source Environment Record — C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
MVS File Create Record — E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
View Create Record — V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Alias Create Record — A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Synonym Create Record — S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Map Record — M. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Relationship Record — R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Data Record — D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
XML/LOB Data Record — x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Order Record — O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
Trailer Record — T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Work files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Record Layout and File-AID/MVS XREF JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
 9

File-AID/RDX Record Layout File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Sample COBOL Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Sample PL/I Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Sample FA COBOL Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
File-AID/MVS XREF File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Sample XREF for Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Topaz Extract Visualizer File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Checkpoint Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Checkpoint Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Extract Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Extract Progress Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
Relationship Navigation and Sampling Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Relationship Navigation and Sampling Excluded Object Report . . . . . . . . . . . . . . . . . . . 402
Object Sampling and Selection Criteria Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Object Sampling and Selection Criteria Excluded Object Report. . . . . . . . . . . . . . . . . . . 404
Extract Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Summary of Objects with Zero Rows Extracted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Create Record Layout Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
DB2 Index Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
RDX Hybrid Scan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Support for Db2 XML and LOB Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Support for Db2 Temporal Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Support for Db2 Archive Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
GDG Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Load Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Request File Member List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Extract File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Edit JCL for Summary File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Load Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Load Object Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
SQL Insert and Db2 Load Utility Load Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Source to Target Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
File Mapping Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Field Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Column Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Default Value Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Default Value Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Delete Literal Confirmation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Column/Field Mapping Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Data Type Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Miscellaneous Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Column Mapping Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Target Environment Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
10 File-AID/RDX Reference

Generating CREATE DDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463

Create/Edit Db2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
Create/Edit Db2 Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Tablespace Partition Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Create/Edit DB2 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Create/Edit Db2 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Create/Edit Db2 Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Create/Edit Db2 Synonym . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Create/Edit Db2 View (Simple) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Create/Edit Db2 View (Complex) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Create/Edit MVS File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Create/Edit VSAM CLUSTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Support of IAM File Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Create/Edit VSAM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Create VSAM PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Existing Data Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Save Load Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
SAVE Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Control Card Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
View REXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Submit JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Execute REXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Interactive Load Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Control Card Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
The Load Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Db2 Batch Load Utility Load Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Db2 LOAD Utility Load JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
CREATE Step Parameter List and DD Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . 514
LDDRV Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Load Control Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
DELTEnnn Step Parameter List and DD Statements. . . . . . . . . . . . . . . . . . . . . . . . . 518
FIXDLnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
SORTnnn Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
ICETOOL Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
LOADnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
RPAIRnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
CHCKDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
IMAGECPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
COPYnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
SQL Insert Load Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
SQL INSERT Load JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
CREATE Step Parameter List and DD Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . 527
 11

LDDRV Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

Db2 Load Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
DELETE Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
SORTnnn Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
ICETOOL Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
LDSQLIN Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . 533
SQL Insert Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
MVS Load Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
MVS Load JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
VSAMALOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
VSAMCRTE Step DD Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
FILEDLTE Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
FILEALLC Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
LDDRV Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
MVS Load Control Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
LDMVSIN Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . 542
SORTnnn Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
ICETOOL Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
MVS Insert Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Miscellaneous Load Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Target Environment Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Single-Table and Multi-Table Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
CHECK PENDING Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
COPY PENDING Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Restartability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Db2 Load Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
SQL Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Reusing the Discard File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
Use of Views in Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Db2 Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Privileges Required for Load Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Load Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
SQL Insert - DB2 Authority Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
DB2 Load - DB2 Authority Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Create DB2 Target Environment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
Pre-Load Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
SQL Insert: DB2 Totals Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
MVS Load - MVS Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
SQL Insert: DB2 Committed Rows Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
SQL Insert - DB2 Delete Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
DB2 Load - DB2 Delete Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
SQL Insert: DB2 Discard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
MVS Load: VSAM Discard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
12 File-AID/RDX Reference

Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Support for Db2 XML and LOB Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Delete Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
Request File Member List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Extract File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
Edit JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Delete Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
Delete Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Discard File Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
Save Delete Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
SAVE Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Viewing Delete JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Control Card Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
The Delete Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Db2 Delete Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Db2 Delete JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
DLDRV Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Delete Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
DELETE Step Parameters and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
MVS Delete Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
MVS Delete JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
DLDRV Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
MVS Delete Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
DLMVS Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
MVS Delete Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Miscellaneous Delete Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Db2 Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Db2 Delete Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
CASCADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
SET NULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Restartability (Db2 only). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Reusing the Discard File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Delete Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
Delete - DB2 Authority Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Pre-Delete Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Delete: DB2 Discard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
MVS Delete: VSAM Discard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
Delete: DB2 Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
MVS Delete: MVS Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Delete: DB2 Committed Rows Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601

Data Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Using File-AID/RDX with File-AID Data Privacy (Using DPR) . . . . . . . . . . . . . . . . . . . . . . 603
 13

Using File-AID/RDX with File-AID/Data Solutions (Using DCF) . . . . . . . . . . . . . . . . . . . . 604

What Is Disguise? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Planning Disguise Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Creating DCF Disguise Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Simple and Complex Disguise Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Disguise Control File and Disguise Criteria Storage . . . . . . . . . . . . . . . . . . . . . . . . 606
Sharing Disguised Data with Other File-AID Products . . . . . . . . . . . . . . . . . . . . . . . 606
Db2 XML and LOB Data Type Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Disguise Considerations for Conditional (Data-Driven) Application Relationships (AR-
C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
Disguise Considerations for “Cloned” Extract Requests . . . . . . . . . . . . . . . . . . . . . . . . . 607
Unicode Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
GDG Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Suggested Disguise Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Data Privacy Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
DPR: Disguise Existing Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
XVJPRINT Execution Log Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
Optional Data Privacy Report Output Written to a File . . . . . . . . . . . . . . . . . . . . . . 615
Optional Source Data Identifiers (SDIs) Override During Execution. . . . . . . . . . . . . 616
Override Data Privacy Environment Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Override Execution Parameter in a Data Privacy Project . . . . . . . . . . . . . . . . . . . . . 617
Multiple Origins for a Data Privacy Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Special Instructions for Oracle Translate Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Set Incomplete Disguise Continuation Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Control Card Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Extract Reference List for Disguise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Request File Member List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
NEW - DB2 Object Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
NEW - MVS Object Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
ObjectIn Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
Data Disguise - Object List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
ObjectOut - DB2 Object Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
ObjectOut - MVS Object Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
ObjectOut Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
MVS XREF/Record Layout Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
MVS Catalog Utility File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
PDS Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
XREF Select Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Data Disguise - Column List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Associated Rules List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
File-AID/Data Solutions Criteria Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Criteria Menu - Associated Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Criteria Menu - Related Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Criteria Menu - Unrelated Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
14 File-AID/RDX Reference

Define Global Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

File-AID/Data Solutions Aging Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
File-AID/Data Solutions Euro Conversion Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
File-AID/Data Solutions Triangulation Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
File-AID/Data Solutions Date Analysis Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
File-AID/Data Solutions Validation Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
File-AID/Data Solutions Data Analysis Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
File-AID/Data Solutions Data Translator Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
File-AID/Data Solutions Data Generator Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
File-AID/Data Solutions Pattern Data Generator Criteria . . . . . . . . . . . . . . . . . . . . . . . . 661
File-AID/Data Solutions Field Exit Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
File-AID/Data Solutions Data Encryption Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
File-AID/Data Solutions Data Replace Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Disguise Criteria Dataset Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
DCF: Disguise Existing Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667
XVJPRINT Execution Log Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Redirect File-AID/Data Solutions Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Set Incomplete Disguise Continuation Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Control Card Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
File-AID/Data Solutions Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Allocate Disguise Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Allocate Disguise Criteria File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Print Disguise Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Print DCF Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Print Disguise Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Printing Multiple Audit Trail Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Audit Trail Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
HEX Print Report Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Character Report Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Summary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Executing Print Audit Trail Independently in Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Audit Trail Print Execution Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Miscellaneous Data Privacy Topics (Using DCF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Db2 Alias, Synonym, and View Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
VSAM PATH Support for Disguise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Size Allocation of Disguise Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Unlike Column/Field Data Types and Disguise Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Special Consideration for Numeric to Character Conversion . . . . . . . . . . . . . . . . . . 686
Normalized Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Data Privacy JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Data Privacy Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Split File Allocation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
File-AID Data Privacy Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
 15

File-AID/RDX Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
RDX Utilities Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Update Saved Extract Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
JCL/Overrides Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698
Override File Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Override Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Request File Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Generated ESR JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
ESR Basic Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Extract File Compress Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
View JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
Generate DDL Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
View JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

Tutorial and Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Primary Menu Option T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
HELP Primary Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Tutorial Help Pull-down Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Help Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725

Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Primary Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
ACCEPT (A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
ADD (A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
BACK (BA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
CANCEL (CAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
CAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
CHANGE (C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
CHECK (CHE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
COND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
CREATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
CURSOR* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
DELETE (DEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
DETAIL (D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
EDIT (E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
END* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
EXCLUDE (EX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
EXPAND* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
FILTER (FIL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
FIND (F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
16 File-AID/RDX Reference

FORWARD (FOR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734

FUNCTION LOCK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
GEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
GO (G). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
GRAPHIC (G,GR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
HELP* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
HIDE (H). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
IGNORE (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
INSERT (INS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
KEYLIST* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
KEYS* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
LEFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
LIMITKEY (LK). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
LOCATE (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
NAVIGATION (NAV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
NEW (N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
NEXT (N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
OBJECTIN (OI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
OBJECTOUT (OO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
PARTITION (PART) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
PREV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
PRINT* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
PRINT-HI* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
PRINTL* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
PRINTLHI* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
REFERENCE (REF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
REFRESH (R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
REPEAT (REP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
REPORT (REP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
REQUEST (REQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
RESET (RES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
RETRIEVE* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
RETURN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
RFIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
RIGHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
SAMPLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
SHOW (SH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
SIZE (SI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
SORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
SPLIT* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
SQLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
 17

STATUS (STAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740

SUBMIT* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
SUGGEST (SUG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
SWAP* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
TABLE (TAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
TSO* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
UDTSWAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
UDTTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
UNEXCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
VALIDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
VIEW (VI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741
Line Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
A (Accept Path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
A (Add) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
A (Add/Assign Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
A (All) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
B (Browse) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
C (Change and Go) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
C (Copy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
D (Delete) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
E (Edit AR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
E (Edit Object) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
G (Go) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
I (Ignore Path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
I (Information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
I (Insert) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
L (List DB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
L (Load RI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
L (Lock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
L (Lock Table). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
M (Modify Request) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
M (Modify MVS Object) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
n (Column or Field Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
O (ObjectOut) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
P (Passthru) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
R (Related objects) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
R (Relationship View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
R (Remove). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
R (Rename) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
R (Repeat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
R (Restore original name) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
S (Select) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
U (Unassign Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
U (Unexclude) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
18 File-AID/RDX Reference

U (Undo Remove). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

U (Unlock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
U (Update) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
V (View JCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746
X (Exclude) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

Extract Navigation Criteria Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

A Closer Look . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Navigation Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Order of Accessing Objects During Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Examples Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Summary Comparison of Extract Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
DPSI=YYNY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
DPSI=YYNN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
DPSI=YYNN Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
DPSI=YYYY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
DPSI=YYYY Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755
DPSI=YYYY, CYCLE=1, QUIESCE=Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
DPSI=YYYY CYCLE=1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762
DPSI=YYNN Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Modified Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
DPSI=PYNN Direct Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Direct Plus Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
DPSI=CNNN All Children Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
All Children Only Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 771
DPSI=YYNY Example 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773
DPSI=YYNN Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
DPSI=YYYY Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
DPSI=YYYY, CYCLE=1, QUIESCE=Q Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
DPSI=YYNN Modified Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
DPSI=PYNN Direct Plus Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
DPSI=CNNN All Children Only Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
 19

Introduction
This is a detailed reference manual for users of File-AID/Related Data XPERT (File-AID/RDX). It
provides the information necessary to take advantage of the features of File-AID/RDX. This manual is
not intended as a learning tool for first time users.

How This Manual is Organized

This manual consists of the following chapters:

• Overview provides an overview of File-AID/RDX, including a brief description of the product’s

features and functionality.

• Profiles and Global Defaults describes Option 0, Profile, and.Option G, Global Defaults.

• Relationship Facilitator describes Option 1, Relationship Facilitator, the object-centric entry to

relationship maintenance.

• Extract describes Option 2, Extract.

• Load describes Option 3, Load.

• Delete describes Option 4, Delete.

• Data Privacy describes Option 5, Data Privacy.

• File-AID/RDX Utilities describes Option 6, File-AID/RDX Utilities.

• Tutorial and Online Help describes Option T, Tutorial and Online Help, and Option C, Changes.

In addition, the manual includes the following appendixes:

• Appendix , provides a summary of File-AID/RDX commands.

• Appendix , provides different examples of global navigation settings for File-AID/RDX’s extract.

• Glossary provides a summary of product-specific terms.

Alerts
The alerts found in this guide include:

Information important to remember.

A note or tip providing additional information.

20 File-AID/RDX Reference

Notation Rules
This manual uses the following notation rules:

• Screen names appear with initial caps. For example:

– …. on the Extract Specification screen

• Field names and column names appear in bold letters with initial caps. For example:

– …. in the Creator Name field

– …. in the Field Value column

• Actual field values taken from a screen appear in text in a line printer typeface. For example:

– Type S next to FRSAMP.ORDER_TABLE to select it.

• Command names appear in all uppercase. For example:

– The CANCEL command causes…

• User input appears in bold uppercase letters. For example:

– Enter YES to edit the JCL.

Reading the Syntax Diagrams

Syntax diagrams define primary command syntax.

A parameter is either a keyword or a variable.

All KEYWORDs are shown in uppercase characters and must be spelled exactly as shown. You cannot
substitute another value. If any part of a KEYWORD is shown in lowercase characters, that part is
optional.

Variables are user-specified values and are printed in lowercase italics. For example, dataset-name
indicates you are to substitute a value.

The syntax for commands is described in diagrams that help you visualize parameter use. The
following example shows a command and a parameter:

COMMAND parameter

Read the diagrams from left to right and from top to bottom. These symbols help you follow the path
of the syntax:

indicates the beginning of a statement.

indicates the statement is continued on the next line.
indicates the statement is continued from the previous line.
indicates the end of a statement.

Required parameters appear on the horizontal line (the main path). Optional parameters appear
below the main path. Default parameters appear above the main path and are optional. The
command executes the same regardless whether the default parameter is included.

DEFAULT-KEYWORD
COMMAND REQUIRED-KEYWORD
optional-variable
Introduction 21

Vertically stacked parameters are mutually exclusive. If you must choose a parameter, one item of the
stack appears on the main path. If the parameters are optional, the entire stack appears below the
main path. If a parameter in a stack is the default, it appears above the main path.

DEFAULT-KEYWORD1 default-var1
COMMAND
OPTIONAL-KEYWORD2 optional-var2
OPTIONAL-KEYWORD3 optional-var3

If the same parameters are used with several commands their syntax may be documented in a
separate diagram. In the command syntax, these common parameters are indicated with separators
before and after the parameter name.

COMMAND common-parameter

An arrow returning to the left indicates a repeatable item. If the arrow contains a comma, separate
the repeated items with a comma.

,
COMMAND required-var

Related Publications
• File-AID Installation and Configuration Guide: Provides an abbreviated set of steps to quickly
configure File-AID products, including File-AID/RDX.

• File-AID Advanced Configuration Guide: Provides advanced configuration topics on how to configure
all File-AID products, including File-AID/RDX, on your system. It is intended for database
administrators and the systems group responsible for File-AID at your installation.

• File-AID/Related Data XPERT Reference provides detailed information necessary to fully use the
features of File-AID/RDX. It is intended for users of File-AID/RDX.

• File-AID/Related Data XPERT User Guide: Step-by-step procedures on how to use File-AID/RDX
functions.

• File-AID/Related Data XPERT Reference Summary provides a summary of the File-AID/RDX commands
and functions. It is intended for users of File-AID/RDX.

• File-AID Release Notes provides a summary of the latest enhancements to File-AID products,
including File-AID/RDX. It is intended for IS management and users of File-AID/RDX. It contains
information similar to Option C, Changes.

• Compuware Installer Mainframe Products SMP/E Installation Guide Instructions on how to perform the
SMP/E installation of Compuware mainframe products, including File-AID/RDX.

Online Documentation
The File-AID/RDX product installation package does not include the product documentation. Access
the File-AID/RDX documentation from the Compuware Support Center website at
https://support.compuware.com in the following electronic formats:

• Release Notes in HTML format

• Product manuals in PDF format
22 File-AID/RDX Reference

• Product manuals in HTML format.

The product documentation is available for viewing or downloading:

• View PDF files with the free Adobe Reader, available at http://www.adobe.com.
• View HTML files with any standard web browser.

Getting Help
At Compuware, we strive to make our products and documentation the best in the industry. Feedback
from our customers helps us to maintain our quality standards.

If problems arise, consult your manual or the File-AID/RDX customer support representative at your
site. If problems persist, please obtain the following information before contacting Compuware. This
information helps us to efficiently determine the cause of the problem.

1. Obtain your client number and write it in the space below.


Client No. _________________________________
2. If you are getting an error message from File-AID/RDX, press PF1 for an extended explanation of
the error.
3. If you are getting a batch error message from File-AID/RDX, keep the JCL and output.
4. Identify the File-AID/RDX release.
5. Determine the product function being used and the sequence of events leading up to the
problem.
6. If files are involved, determine the file characteristics.
7. Determine whether there are any other I/O-related software products installed.
8. Record any ISPF/PDF error messages or operating system messages. If an abend occurs, record or
screen print the abend information.
9. Determine the versions of current operating system components that may have an impact on the
problem.

Compuware Support Center

Visit the Compuware Support Center, https://support.compuware.com, to find product
documentation, knowledge articles, and other technical resources. You can open a case with the
Customer Solutions team, order products, and much more.

Contact Customer Solutions by phone:

• USA and Canada: 1-800-538-7822 or 1-313-227-5444.

• All other countries: Contact your local Compuware office. Contact information is available at
https://support.compuware.com.

Visit Compuware on the web at http://www.compuware.com for additional product information.

 23

Overview
Product Introduction
File-AID/Related Data XPERT (File-AID/RDX) enables developers, auditors, QA analysts, and data base
administrators to easily extract, load, and delete complete sets of related Db2 and MVS data. Data
related by referential integrity or application-defined relationships is copied within the respective
Db2 and MVS environments with full support for all relational constraints.

File-AID/RDX uses a familiar ISPF-like format to create and populate test objects that accurately
reflect the production relationships, yet contain only a relevant subset of the data—without coding SQL
or writing programs. Users can migrate related sets of data from one Db2 or MVS environment to
another or archive complete sets of data, confident that all parent/child relationships are properly
maintained.

When extracting sensitive production data, it can also be disguised to protect privacy while
maintaining all relationships. Data Privacy requires installation of Compuware’s File-AID/Data
Solutions Release 4.4 or more recent.

Invoking File-AID/RDX
File-AID/RDX executes as a dialog under IBM’s ISPF/PDF dialog manager facility. You can invoke File-
AID/RDX by selecting the File-AID/RDX option from a customized version of the ISPF/PDF Primary
Option Menu, or from a sub-menu panel your installation has set up.

You can also invoke File-AID/RDX from File-AID for DB2 (Option R). When coming to File-
AID/RDX from File-AID for DB2, however, you can only connect to the Db2 subsystem that
you are connected to in File-AID for DB2. To connect to another Db2 subsystem in File-
AID/RDX, you must return (exit) to File-AID for DB2 and change the subsystem there, or exit
File-AID for DB2 and invoke File-AID/RDX by itself.

The File-AID/RDX Primary Option Menu shown in Figure 1 is the first screen displayed when you
invoke File-AID/RDX.

When Db2 is being used by another application in your current TSO session, File-AID/RDX
issues a warning when connecting to Db2 (see DB2 Call Attach Alert on page 36).
24 File-AID/RDX Reference

Figure 1. File-AID/RDX Primary Option Menu

File-AID/RDX 17.2 ------- Primary Option Menu -------------------------------

OPTION ===> 
USERID - TSOID01
0 PROFILE - Select, Create or Change Profile TIME - 14:15
1 RELATIONSHIPS - Relationship Facilitator TERMINAL - 3278
2 EXTRACT - Extract from Related Objects PF KEYS - 24
3 LOAD - Load Data Records
4 DELETE - Delete Extracted Rows from DB2 Tables and/or MVS Files
5 DATA PRIVACY - Data Privacy Menu
6 UTILITIES - Utility Functions
G GLOBAL DEFAULTS - Define User Parms
FD FADB2 - Transfer to File-AID for DB2
C CHANGES - Summary of File-AID/Related Data XPERT changes
T TUTORIAL - Information about File-AID/Related Data XPERT
X EXIT - Exit File-AID/Related Data XPERT

Profile ===> RDXMENU RDXMENU - DISPLAY ALL OF THE MENU OPTIONS
Type ===> SITE (SITE, USER or prefix)

Online Technical Support available at: https://go.compuware.com 
Copyright (c) 1994-2019, by Compuware Corporation. All Rights Reserved. 
Unpublished rights reserved under the Copyright Laws of the United States.
Type LEGAL on the command line for Copyright/Trade Secret Notice. 


To select an option from the File-AID/RDX Primary Option Menu, enter the appropriate code in the
Option field and press Enter. See File-AID/RDX Primary Options on page 24 for a detailed
explanation of each option.

The Primary Option Menu also displays the name of the current Profile and its Type (SITE, USER, or
prefix). SITE profiles can only be modified by authorized users. The profile establishes the default
values for the extract and load functions. This allows you, for example, to run an extract job by
simply accepting all the profile provided defaults, without stepping through a lengthy extract
specification process.

To specify a profile, simply enter the type and name. When specifying a profile name that doesn’t
exist or a pattern, File-AID/RDX will display the Select Profile Screen screen (see Figure 14 on page
51).

File-AID/RDX Primary Options

The following are options available from the File-AID/RDX Primary Option Menu.

Option 0—Profile
Select and define your File-AID/RDX profiles for extract, load, and disguise functions. You can modify
an existing SITE profile and save it as your own USER profile. SITE profiles may only be modified by
authorized administrators.

After the File-AID/RDX installation has been completed, your site’s File-
AID/RDX administrator should modify the SITE profiles to site-specific
settings and establish access authorities according to your site’s standards.

Option 1—Relationships
The Relationship Facilitator assists you in maintaining relationships. Specify a Db2 or MVS object
and then perform relationship activities:

• Browse, refresh, load, and remove Db2 referential integrity (RI) relationships in the File-AID/RDX
relationship file.
• Browse, edit, delete, and create application relationships (AR) between Db2, MVS objects, and/or
IMS or Output Key File in the File-AID/RDX relationship file.
Overview 25

• Create, view, delete, and edit conditional (data-driven) application relationships.

These Relationship Utilities allow you to:

• Allocate relationship file

• Load and update RI in relationship file
• Print relationship file

Option 2—Extract
Extract relationally intact sets of data from one or more related or unrelated objects (Db2 tables and
MVS files). Optionally, File-AID/RDX will extract Db2 data from Db2 image copy so you can execute
the extract outside of your Db2 production environment. You can create or modify extract criteria to
apply during the extract process. File-AID/RDX generates the JCL to perform the extract in batch
mode. Optionally, the extract can be executed interactively online. Additionally, you can combine
the extract and load steps into a single JCL procedure.

When the extract request includes a relationship to an Output Key File, File-AID/RDX creates an
Output Key File that File-AID/RDX can use as an Input (external) Key File against a driving object in
another extract (see also Input Key File Specification on page 295) or as input into another process as
you choose. When the relationship is to an IMS segment, use the Output Key File with File-AID for
IMS to extract IMS data.

When you also create a COBOL record layout of the extracted file, you can use File-AID/EX to
download and convert the extracted data to other client/server or workstation based DBMS.

The extract process can also disguise the extracted data to provide security for sensitive data. The
disguise criteria can be defined by either using the File-AID/RDX Option 5, Data Privacy, or the File-
AID Data Privacy component of the Topaz Workbench1.

Batch Extract Checkpoint and Resumption

File-AID/RDX provides the ability to stop a checkpoint enabled extract and resume the extract
execution from the checkpoint (see also Stopping/Resuming Batch Extract Execution on page 202).
Use this functionality when you anticipate a long running extract that might not complete within
your site’s constraints or when executing complex related extracts.

Topaz Workbench Data Visualizer

The Data Visualizer component of the Topaz Workbench provides another way to view the
relationship definitions in an extract request file. Also, when requesting a Topaz Extract Visualizer
file for an extract (see 9 - Supporting Files on page 242), it allows for step-by-step Extract
Visualization within the Data Visualizer component of the Topaz Workbench. The insight provided
by the Topaz Extract Visualizer allows you to better understand complex related extracts, extract
requests, and relationship repositories. You will benefit by developing higher quality extracts,
enhanced understanding of troublesome extract areas, and quicker problem resolution if tuning is
needed. Refer to the Topaz Workbench documentation for more information on the Data Visualizer.

Option 3—Load
Load relationally intact sets of data into one or more related objects (Db2 tables and MVS files). To
load Db2 objects you can choose between using SQL INSERT statements or the Db2 LOAD Utility.
Load data into existing objects (Db2 tables and MVS files) that are empty or already contain data. In
addition, File-AID/RDX can create new tables or files automatically before it loads the data. File-
AID/RDX generates the JCL to perform the load in batch mode. Optionally, the load can be executed
interactively online.

1. The Compuware Workbench has been replaced by the Topaz Workbench. The Topaz Workbench provides all of the
functionality of the previous Compuware Workbench as well as any additional chargeable functionality.
26 File-AID/RDX Reference

Option 4—Delete
Delete records from one or more related Db2 or MVS objects from which you have previously
extracted data. File-AID/RDX determines which records should be deleted based on the contents of a
File-AID/RDX extract file that you specify.

Option 5—Data Privacy

Disguise sensitive extracted data prior to moving it into a test environment. In this context,
disguising data means to change the identifying characteristics from the data, such as name and
address information, while still maintaining the structure and relationships of the original data. You
have the option to define disguise criteria by either using the File-AID/RDX Option 5, Data Privacy, or
the File-AID Data Privacy component of the Topaz Workbench. Data Privacy requires installation of
Compuware’s File-AID/Data Solutions and, optionally, File-AID Data Privacy products.

These Disguise Utilities allow you to:

• Allocate Disguise Control File

• Allocate Disguise Criteria File
• Print Disguise Control File
• Print Audit Trail

Option 6—Utilities
The RDX utilities allow you to:

• Update relationships in saved Extract Requests

• Specify Execute Saved Request (ESR) options
• Compress or Decompress Extract File
• Generate readable DDL from Extract File.

Option G—Global Defaults

Specify the maximum number of entries in your Extract and Load Reference lists, specify whether or
not to delete the File-AID/RDX control card PDSEs at the end of an extract, load, delete, or disguise
job, specify a Dynamic Privacy Rules Repository, and enter default job statement information. In
addition, this option displays which version of File-AID/RDX is in use.

Option FD—FADB2
Transfer to File-AID for DB2.

Option C—Changes
Display a summary of changes made to various releases of File-AID/RDX.

Option T—Tutorial
View an online tutorial for novice users.

Option X—Exit
Terminates your File-AID/RDX session.

Screen Conventions
In general, the first three lines of each display are formatted as follows:

Screen Title Short Message or Db2 Subsystem ID

Command or Option prompt Scroll amount or Db2 Subsystem prompt
Long Message
Overview 27

Pattern Characters
Many screens accept pattern characters. Valid pattern characters are:

Asterisk (*)—Matches all values. Valid for specifying objects, creators, tables, and members. Any
characters following the asterisk (*) are disregarded, unless when searching for MVS objects in the
MVS catalog, then the asterisk is treated the same as in ISPF dialogs.

Underscore (_)—Matches an occurrence of any single character. If an underscore is embedded in

a string, the string must end with a percent sign (%). For example, xyz, xaz, and xbz all match
x_z%. Valid for specifying Db2 objects only.

Percent sign (%)—Matches the occurrence of no characters or an unlimited number of

characters. If a percent sign is embedded in a string, the string must end with a percent sign (%).
For example, xyz, xz, and xmnoz all match x%z%. Valid for specifying Db2 objects only.

After you enter a pattern, File-AID/RDX displays a selection list. You can then select the
appropriate name from the list.

Escape Characters
Escape characters are required when you specify a creator or table name that does not conform to the
DB2 alphanumeric character set. Escape characters are also required when you do not want uppercase
translation of creator or table names.

Double-Byte Character Set (DBCS) Support

File-AID/RDX supports the use of the Double-Byte Character Set (DBCS). DB2 must be installed with
the mixed data option and your terminal must support the use of DBCS data.

File-AID/RDX enables you to do the following using DBCS:

• Specify tables whose names contain double-byte characters.

• Specify WHERE clause arguments on the Selection Criteria screen in Option 2, Extract.

If you have column names that contain DBCS characters, File-AID/RDX displays them enclosed in
shift in and shift out characters on the Selection Criteria screen, the Relationship Information
window, and the Column Relationships screen.

Table Names
You can specify table names that contain DBCS characters. Use the following syntax:

" > dbcs-string < "

where,

“ (double quote) escape character

> DB2 shift out character
< DB2 shift in character
dbcs-string DBCS data

You can use mixed strings to specify values in the Where field on the Selection Criteria screen. Use
the following syntax for CHAR, VCHAR, and LVCHAR strings:

= ’ sbcs-string > dbcs-string < sbcs-string ’

where,

= any valid operator (see Where on page 307 for a list of valid
operators)
28 File-AID/RDX Reference

’(apostrophe) delimiter
> DB2 shift out character
< DB2 shift in character
sbcs-string DBCS data
dbcs-string DBCS data

Use the following syntax for GRPH, VGRPH, and LVGRPH strings:

=G' > dbcs-string <'

where,

= any valid operator (see Where on page 307 for a list of valid
operators)
G constant
’(apostrophe) delimiter
> DB2 shift out character
< DB2 shift in character
dbcs-string DBCS data

Column Name Display

If you have column names defined using DBCS characters, File-AID/RDX will display them using
DBCS enclosed in shift out and shift in characters.

Types of Screens
There are several types of screens in File-AID/RDX. These screen types are defined in the following
sections.

Option Selection Screen

The Option Selection screen displays a list from which you select an option by entering the
appropriate character(s) in the Option field and pressing Enter. The File-AID/RDX Primary Option
Menu shown in Figure 2 is an example of an Option Selection screen.

Figure 2. Option Selection Screen Example

File-AID/RDX 17.2 ------- Primary Option Menu -------------------------------

OPTION ===> 
USERID - TSOID01
0 PROFILE - Select, Create or Change Profile TIME - 14:15
1 RELATIONSHIPS - Relationship Facilitator TERMINAL - 3278
2 EXTRACT - Extract from Related Objects PF KEYS - 24
3 LOAD - Load Data Records
4 DELETE - Delete Extracted Rows from DB2 Tables and/or MVS Files
5 DATA PRIVACY - Data Privacy Menu
6 UTILITIES - Utility Functions
G GLOBAL DEFAULTS - Define User Parms
FD FADB2 - Transfer to File-AID for DB2
C CHANGES - Summary of File-AID/Related Data XPERT changes
T TUTORIAL - Information about File-AID/Related Data XPERT
X EXIT - Exit File-AID/Related Data XPERT

Profile ===> RDXMENU RDXMENU - DISPLAY ALL OF THE MENU OPTIONS
Type ===> SITE (SITE, USER or prefix)

Online Technical Support available at: https://go.compuware.com 
Copyright (c) 1994-2019, by Compuware Corporation. All Rights Reserved. 
Unpublished rights reserved under the Copyright Laws of the United States.
Type LEGAL on the command line for Copyright/Trade Secret Notice. 

Overview 29

Option Information Screen

The Option Information screen enables you to specify information necessary to perform the function
selected. The DB2 Relationship Facilitator screen shown in Figure 3 is an example of an Option
Information screen.

Figure 3. Option Information Screen Example

File-AID/RDX --------- DB2 Relationship Facilitator ------------------------

Option ===> Scroll ===> CSR 
SITE Profile: RDXMENU

Primary commands: menu-option, MVS Relationship Facilitator 

1 BROWSE ALL - Browse all existing Relationships 
2 EDIT AR - Edit existing Apllication Relationships 
3 ADD AR - Add new Application Relationships 
4 LIST RDX - List DB2 objects from RDX Relationship File 
5 LOAD RI - Load RI Relationships from DB2 Catalog tables 
6 LIST DB2 - List DB2 objects from DB2 Catalog 
A ALLOCATE - Allocate Relationship File 
L BATCH RI LOAD - Batch Job to Load RI Relationships
P PRINT - Print the Relationship File 

Specify a Table Name or pattern: 
SSID ===> DSN (* or pattern for selection list)
Location ===> (* or pattern for selection list)
Creator ===> TSOID01 (* or pattern for selection list)
Table Name ===> ORD* (* or pattern for selection list)


See DB2 Relationship Facilitator on page 88 for a description of this screen example.

Scrollable Data Screen

The Scrollable Data screen shows information about multiple relationships and allows up/down
scrolling. The Relationship Detail screen shown in Figure 4 is an example of a scrollable data display.

Figure 4. Scrollable Data Screen Example

File-AID/RDX Relationship Detail Row 1 to 6 of 6

COMMAND ===> SCROLL ===> CSR

Relationships for: LOCATION.FRSAMP.ORDER_TABLE

Line Commands: S - Select Relationship to Modify D - Delete Relationship
A - Add Application Relationship I - Relationship Information

Obj Rel
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.FRSAMP.CUSTOMER_TABLE DB2 AR
LOCATION.FRSAMP.ORDER_TABLE DB2
_ LOCATION.FRSAMP.ORDER_TABLE DB2 RI
LOCATION.FRSAMP.ORDER_LINE_TABLE DB2 ORDLORD
_ LOCATION.FRSAMP.CUSTOMER_TABLE DB2 RI ASSOCIATED REL.
LOCATION.FRSAMP.CONTACT_TABLE DB2 CONTCUST
_ LOCATION.FRSAMP.PART_TABLE DB2 RI ASSOCIATED REL.
LOCATION.FRSAMP.ORDER_LINE_TABLE DB2 ORDLPRT
_ LOCATION.FRSAMP.PART_TABLE DB2 RI ASSOCIATED REL.
LOCATION.FRSAMP.SUPPLIER_TABLE DB2 SUPPPART
******************************* Bottom of data *************************

See Relationship Detail on page 101 for a description of this screen example.
30 File-AID/RDX Reference

Pop-Up Windows
File-AID/RDX uses several types of pop-up windows to perform functions such as displaying a
selection list and displaying detailed information about a single relationship.

Selection Pop-Up Window

The selection pop-up window displays a scrollable list of items from which you can select one or
more entries. This type of window displays minimal information about the items on the list. The
Table List shown in Figure 5 is an example of a selection pop-up window.

Figure 5. Selection Pop-Up Window Example

File-AID/RDX ------------- DB2 Driving Object -------------------------------

OPTION ===> 
Table List - SYSIBM.SYSTABLES 
Primary Comma Row 1 to 8 of 238 
COMMAND ===> SCROLL ===> CSR 
Specify table 
SSID Enter 'S' to select table name 
Location 
Creator CMD Location Creator Table Name Type 
Table Name --- ---------------- -------- ------------------- ----- 
_ LOCATION FADBTST ACT TABLE 
Relationship _ LOCATION FADBTST ADEPT ALIAS 
File name o _ LOCATION FADBTST AEMP ALIAS 
_ LOCATION FADBTST CHANGER TABLE 
_ LOCATION FADBTST CHILD TABLE 
_ LOCATION FADBTST COLS750 TABLE 
_ LOCATION FADBTST COPY_FROM TABLE 
_ LOCATION FADBTST DBCS_1 TABLE 




Information Display Screen

The information display screen displays information about an object or a relationship. The
Relationship Information window shown in Figure 6 is an example of an information display screen.

Figure 6. Information Display Screen Example

File-AID/RDX Relationship Information DB2 Row 1 to 2 of 2 

COMMAND ===> SCROLL ===> CSR 

Parent Name: LOCATION.FRSAMP.ORDER_TABLE Type: DB2 



Dependent Name: LOCATION.FRSAMP.ORDER_LINE_TABLE Type: DB2 



Relationship Details: 
Description: RI - ORDLORD 
Status: Not in Dataset 
Created: User: 
Last Modified User: 
Parent Columns /Type(Length) Dependent Columns /Type(Length) 
----------------------------------------- ------------------------------------ 
ORDER_NUMBER ORDER_NUM 
CHAR(6) CHAR(6) 
*** End Of Columns *** *** End Of Columns *** 
Overview 31

See Relationship Information Screen on page 107 for a description of this screen example.

Scrolling
When a scrollable data display or pop-up window is displayed, the information to be displayed may
exceed the screen or window size. The scrolling commands enable you to move the information up or
down relative to the screen or window allowing you to view all displayable data. You can scroll
through the data by using the UP and DOWN commands.

UP Causes scrolling toward the top of the data by the specified scroll amount.
DOWN Causes scrolling toward the bottom of the data by the specified scroll
amount.

Only the Selection Criteria screen and scrollable fields (see also Scrollable Fields for Db2 Long Names)
permit left and right scrolling. You can use the LEFT and RIGHT commands to scroll through the
data.

LEFT Causes scrolling toward the first column of data by the specified amount.
RIGHT Causes scrolling toward the last column of data by the specified amount.

The scrolling commands have the following syntax:

UP
DOWN n
LEFT CSR
RIGHT CUR
C
DATA
D
HALF
H
PAGE
P

Valid scroll amounts are:

Table 1. Valid Scroll Amount Values

Value Description
Number from 1 to 9999 Scroll the specified number of lines.
PAGE Scroll one logical page.
HALF Scroll half of one logical page.
MAX Scroll to the top or bottom of data (depending on the scroll command used).
DATA Scroll one logical page less one line.
CURsor Scroll such that the line on which the cursor is positioned moves to the top or
CSR bottom of the screen, depending on the scroll command used. If the cursor is
not in the body of the data or is already on the top or bottom line of the
screen, a full-page scroll occurs.

For scrolling purposes, a “page” is defined as the amount of information currently visible on the
logical screen. A pop-up window, for example, might have 10 lines of scrollable data. In this case a
scroll amount of HALF would scroll 5 lines.
32 File-AID/RDX Reference

Scrollable Fields for Db2 Long Names

Table and Creator names, for example, can be up to 128 characters long. File-AID/RDX supports Db2
long names and uses scrollable fields to display them on panels.

Long Name Indicator

When the complete table or creator (schema) name fits in the viewable field on a panel, the field
name is followed by “===>”, but when there are more data in the field, the panel will show the “ +++>”
long name indicator instead. This should alert you to scroll or expand the field to view the name in
its entirety. In Figure 7, the long name indicator “+++>” for Table Name alerts that
EMP_GENERATED_TIMESTAMP_HIDD is longer than displayed EMP_GENERATED_TIMEST.

Figure 7. Long Name Indicator Example

File-AID/RDX --- Add Application Relationships -------------------------

Command ===> 

Specify Parent DB2 Table for Relationship Definition: 
Location ===> DSNLOCAT 
Creator ===> FRSAMP (* or pattern for selection list) 
Table Name +++> EMP_GENERATED_TIMEST (* or pattern for selection list) 


You can view the long names in two ways:

• Using the LEFT and RIGHT commands to scroll through the long name within an existing field
• Using the EXPAND command to display the long name in a separate window

The ZCLRSFLD command (PF24), introduced in z/OS 1.8, clears the contents of the scrollable field to
blanks without having to EXPAND the scrollable field.

Scrollable fields are a standard ISPF feature. Refer to the “ISPF Dialog Developer’s Guide” for more
information about scrollable fields.

Using the LEFT and RIGHT Commands

In order to view a long name in File-AID/RDX, use the LEFT and RIGHT commands to scroll in the
field on the panel. A “Start of field” or “End of field” message displays in the upper right-hand corner
of the screen, when the beginning or end of the field is reached.

Scrollable fields are not supported within dynamic display panels. The following is a list of the most
commonly used dynamic display panels:

• Graphical Relationship Display

Use the KEYS command to set LEFT and RIGHT commands to a PF key (see also Assign PF Keys).

Using the EXPAND Command

The EXPAND command enables you to view a long object name in a separate window from the panel
of the field. In order to view a long name, type EXPAND in the command line of the panel, move the
cursor into the field to expand, and press ENTER (see Figure 8 and Figure 9 for an example).

Use the KEYS command to set the EXPAND command to a PF key (see also Assign PF Keys).
Overview 33

Figure 8. EXPAND Command in Scrollable Field

File-AID/RDX --------------- DB2 Object List -------------- Row 1 to 2 of 2

Command ===> EXPAND SCROLL ===> CSR

Line Commands: A = Add Application Relationship B = Browse Relationship 
E = Edit Application Relationship L = Load RI Relationships 

Relation
CMD Object Name Type SSID 
--- -------------------------------------- ------ ----
_ DSNLOCAN.TSOID01.ORDER_TABLE AR/RI DB28
_ DSNLOCAN.TSOID01.table_name_up_to_128_ catlg DB28
******************************* Bottom of data ********************************

Figure 9. EXPANDed Field

File-AID/RDX --------------- DB2 Object List -------------- Row 1 to 2 of 2

FRQSNAME+0 
Line 1 of 4 
Command ===> Scroll ===> CSR

DSNLOCAN.TSOID01.table_name_up_to_128_characters_long_with_location_and_cr 
ator_the_complete_object_name_can_be_up_to_274_characters_long 


Command Entry
Enter commands by:

• typing the command in the COMMAND or OPTION field and pressing Enter; or
• pressing a PF key to which you assigned a command.

Assign PF Keys
Assign commands to your File-AID/RDX PF keys using the KEYS command from any screen in File-
AID/RDX. When you press a PF key, the processing is the same as if you typed the command in the
COMMAND field and pressed Enter. See Program Function (PF) Keys on page 34 for more
information about PF keys.

Concatenate Commands
Enter information in the COMMAND field before you press a PF key. The PF key definition is
concatenated ahead of the contents of the COMMAND field. For example, suppose you assign the
DOWN command to PF8. If you type 6 in the COMMAND field and press PF8, the results are the
same as if you had typed DOWN 6 in the COMMAND field and pressed Enter.

Stacking Commands
Stack commands for File-AID/RDX to process in a single step by using a delimiter. Enter the delimiter
between the commands. The default delimiter is a semicolon (;). Change the default using ISPF/PDF
option 0.1.

The commands provided by File-AID/RDX are described in a summary format in Appendix , .

Commands are described in detail in the appropriate chapters.

ISPF/PDF JUMP Function

The ISPF/PDF JUMP function enables you to switch from one option to another without going
through the File-AID/RDX Primary Option Menu. Invoke the JUMP function by entering an equal
34 File-AID/RDX Reference

sign (=) followed by a primary option. You can enter it in any prompt field that is preceded by an
arrow (===>).

Terminal Keys
You can use program access (PA) and program function (PF) keys to perform commonly used
operations. Although PF keys are not required for File-AID/RDX operation, you can assign commands
to PF keys using the KEYS and/or KEYLIST command (see also Program Function (PF) Keys on page
34).

Program Access (PA) Keys

File-AID/RDX supports two PA keys as follows:

PA1 (Attention) If you press PA1 once, File-AID/RDX responds as if you pressed PA2 (Reshow). If
you press PA1 a second time without any intervening interaction, the current
processing is terminated and the ISPF/PDF Primary Option Menu is redisplayed.

PA2 (Reshow) Redisplays the contents of the screen. PA2 may be useful if you pressed the
ERASE INPUT or CLEAR keys accidentally, or if you typed unwanted information
but have not yet pressed Enter.

Program Function (PF) Keys

File-AID/RDX utilizes key lists that provide PF key assignment for many File-AID/RDX panels.

Set the KEYLIST status to ON to enable the File-AID/RDX defined key list. To change PF key
assignments use the KEYLIST command. Then File-AID/RDX determines whether KEYLIST is ON or
OFF.

• If OFF, File-AID/RDX executes the KEYS command so you can change the PF key settings.

• If ON, File-AID/RDX executes the KEYLIST command so you can change the key list settings.
When you change the File-AID/RDX default key lists you only change your private copies (Key
list Type changes from Shared to Private).

Table 2 shows the default key lists for File-AID/RDX:

Table 2. Default Key Lists for File-AID/RDX

PF Key F2CMDS3 F2CMDS3B F2CMDS8A RDXDFLT1 RDXHELP RDXPARMS
PF1/13 HELP HELP HELP HELP/EXPAND HELP HELP/EXPAND
PF2/14 SPLIT SPLIT SPLIT SPLIT SPLIT SPLIT
PF3/15 END END END END END END
PF4/16 RETURN RETURN RETURN RETURN RETURN TOGGLE/RETURN
PF5/17 RFIND RFIND RFIND RFIND RFIND LOCK/RFIND
PF6/18 RCHANGE RCHANGE EXECUTE RCHANGE RCHANGE UNLOCK/RCHANGE
PF7/19 UP UP UP UP UP UP
PF8/20 DOWN DOWN DOWN DOWN DOWN DOWN
PF9/21 SWAP SWAP SWAP SWAP SWAP SWAP
PF10/22 LEFT PREV LEFT LEFT BACK/PREV PREV/LEFT
PF11/23 RIGHT NEXT RIGHT RIGHT NEXT NEXT/RIGHT
PF12/24 RETRIEVE RETRIEVE RETRIEVE CANCEL RETRIEVE RETRIEVE/ZCLRSFLD
Overview 35

File-AID/RDX and ISPF/PDF maintain separate PF key definitions. When you modify PF key
definitions within File-AID/RDX, you modify only your File-AID/RDX PF keys. Conversely, when you
modify PF key definitions within ISPF/PDF, you modify only your ISPF/PDF PF keys.

Terminal Types
File-AID/RDX only supports the standard IBM 327x terminal types supported by IBM ISPF, which
have dimensions such as 24x80 (24 lines by 80 columns), 32x80, 43x80, and 27x132.

If you are using 3270 emulator software on a PC, you may have the dimensions set to some other
proportions. Not all possible dimension settings will work with File-AID/RDX. That is, if you edit
your PC settings file and change the dimensions to some nonstandard setting, File-AID/RDX screen
displays may fail.

If you use a nonstandard setting and you are not concerned about it causing occasional screen display
failures, Compuware recommends to select choice "3. Max" under ISPF Option 0 - Settings, Terminal
Characteristics - Screen format. That is an IBM ISPF setting, not a File-AID/RDX setting. It controls
IBM ISPF screen handling. Choosing Screen format 3.Max tends to give best results for working with
the broadest range of screen dimensions. Note again that File-AID/RDX only supports the standard
dimensions of standard IBM terminal types.

DB2 Subsystem ID Selection

The Subsystem ID Selection window shown in Figure 10 is displayed when you try to change to
another Db2 subsystem and have either entered an invalid Subsystem ID, or a pattern. A message in
the window’s first line tells you why File-AID/RDX could not connect to your entered SSID.

Figure 10. Subsystem ID Selection Window

File-AID/RDX ------------- DB2 Driving Object ------------------------------- 

Option ===> 
Subsystem ID Selection 
Primary Commands: MVS Row 1 from 4 
Command ===> 
Specify table to driv 
SSID == Enter 'S' to select SSID t) 
Location == t) 
Creator == Cmd SSID Description t) 
Table Name == --- ---- ---- ------------------------------ 
_ DSNF 1010 
Relationship Informat _ DSNH 1010 
File name or patter _ DSNI 1110 
_ DSNJ 1110 
****** Bottom of data **************************** 






This window includes a selection list of all subsystems that have been defined for your site during
File-AID/RDX’s installation.

If you are running File-AID for DB2 during the same TSO session, the list will be limited
to only those subsystems that are defined for the same Db2 load library that File-AID for
DB2 is connected to. To connect to a subsystem using a different Db2 load library,
terminate one of the two applications before switching subsystems.
36 File-AID/RDX Reference

Move the cursor to the desired subsystem and enter the S line command.

When you receive the message

"Successful Connect"

you have successfully switched to another subsystem.

DB2 Call Attach Alert

The DB2 Call Attach Alert window shown in Figure 11 is displayed when another application other
than File-AID for DB2 or File-AID/RDX is accessing Db2 in your current TSO session.

Figure 11. DB2 Call Attach Alert

File-AID/RDX ------------- DB2 Driving Object -------------------------------

Option ===> 
DB2 Call Attach Alert 
Primary Commands 
Command ===> 
Specify table to 
SSID Another DB2 application is currently active ection list) 
Location within this TSO session. ection list) 
Creator ection list) 
Table Name You may experience DB2 Call Attach problems 
if these applications attempt to allocate 
Relationship Inf different levels of the DB2 load libraries. 
File name or p 
You should proceed with caution or terminate 
all other active DB2 applications. 






File-AID/RDX detected another application other than File-AID/RDX or File-AID for DB2 accessing
Db2. Disregard this alert only when the other application shares the same Db2 load libraries with
File-AID/RDX. To prevent Db2 call attach problems with unpredictable results Compuware
recommends to terminate the other applications before you continue with the File-AID/RDX session.

Press ENTER to continue with your File-AID/RDX session.

File-AID/RDX Files
File-AID/RDX uses the following files:

• Relationship File
• Extract/Load/Delete Request File
• Extract File
• Extract Summary File
• Discard File
• User Profile File
• Disguise Control File
• Disguise Criteria File
• Audit Trail File
• Execute Saved Request (ESR) JCL File
• Object Override File
• SC (Selection Criteria) Override File.
Overview 37

Relationship File
The relationship file contains information about relationship definitions that File-AID/RDX uses in
the extract process.

Relationship File Compatibility Notes

1. Relationship files can be shared between File-AID for DB2 and File-AID/RDX.
2. Db2 long name support requires File-AID/RDX Release 4.3, or higher, or File-AID for DB2 Release
4.8.1, or higher. Once a Db2 long name has been added to a Version 2 relationship file, File-
AID/RDX updates it to a Version 3 relationship file. Version 3 relationship files are not downward
compatible with earlier product releases.

Relationship File characteristics

The relationship file has the following characteristics:

File Organization: VSAM-KSDS

Record Format: Variable
Logical Record Length: Maximum record size is 4765
Maximum columns: 38
Key Length: 74

Use the File-AID/RDX Relational Facilitator Option A to allocate a new relationship file (see Allocate
Relationship File on page 180).

The relationship file stores information about relationships including the following:

• Db2 table names;

• Db2 column names and attributes; and

• Db2 subsystem ID.

• MVS file names;

• MVS record layout and XREF information;

• MVS field names and attributes;

The relationship file stores information about two types of relationships:

Referential Integrity (RI)

Db2-defined referential integrity information taken from the Db2 catalog. Referential integrity
information is initially loaded using a batch job and can be updated with the File-AID/RDX Batch
RI Load utility. See Batch RI Load on page 182 for a description. You also can load individual RI
relationships using the online Load RI option or line command in Option 1, Relationships.

Application Relationship (AR)

User-defined relationship information for relationships between Db2 and/or MVS objects, as well
as relationship information for Db2 or MVS parent objects to IMS dependent object relationships.
You can create and modify AR relationship information from within File-AID/RDX.

Relationship File Layout

The File-AID/RDX Release 2.0 Relationship File contains information about RI and AR relationships.
File-AID/RDX takes information about RI relationships from the Db2 catalog. You provide
38 File-AID/RDX Reference

information about AR relationships when you create them in Option 1 with the Add AR option or
line command.

The relationship file is a fixed format file. There is one record in the file for each parent and child
object. Each record contains the following groupings depending on whether the object is a parent or
child and whether it is a DB2, MVS, or IMS or Output Key object type.

Key (all objects)

Identifies the object, the object type and whether it is the parent or child in the relationship.

Related Object Information (all objects)

Identifies the related object, the product and release that created the relationship as well as the
relationship type, RI or AR.

Relationship Details (parent objects only)

Includes the relationship description and creation and last modification timestamps, database
version, and parent and child column/field information.

MVS Record Layout Information

Identifies the record layout and cross-reference data used when defining the relationship.

Key
Identifies the object, the object type and whether it is the parent or child in the relationship.

Table 3. Key Fields

Field Name Type Length Description
RDX-key Sync GRP 74 RDX key group.
Obj-group CHAR 16 Object group. Reserved for future use.
Obj-type CHAR 1 Object type. D = DB2, I = IMS and KEY, M = MVS.
Obj-name Object name. Fully qualified name of the object; for Db2
CHAR 52
objects, for example, it consists of location.creator.object.
Obj-nm-DB2 Sync Redefines the object name to fit Db2 naming
GRP 52
convention.
Location CHAR 16 Location name
Creator CHAR 8 Creator ID
Table CHAR 18 Table or view name
Filler CHAR 10 Filler
Obj-nm-MVS Sync Redefines the object name to fit MVS naming
GRP 52
convention.
MVS-DSN CHAR 44 Fully qualified MVS file name
Filler CHAR 8 Filler
Obj-nm-IMS Sync GRP 52 Redefines the object name to fit IMS naming convention.
DBD-LIB CHAR 44 Fully qualified IMS DBD-Library name
DBD-Member CHAR 8 Member name
Overview 39

Table 3. Key Fields (Continued)

Field Name Type Length Description
SEQ-NO Binary 4 Unique number to identify specific relationship
Par-child-ind CHAR 1 Parent child indicator: P = Parent, C = Child (dependent)

Related Object Information

Identifies the object that is related to the object specified in the above Key.

Table 4. Related Object Information

Field Name Type Length Description
Rel-Object Sync GRP 73 Related object information group
Rel-Obj-group CHAR 16 Related object group. Reserved for future use.
Obj-type CHAR 1 Related object type. D = DB2, I = IMS, M = MVS.
Rel-Obj-name Related Object name. Fully qualified name of the object; for
CHAR 52 Db2 objects, for example, it consists of
location.creator.object.
Rel-Obj-SEQ-NO Unique number to identify specific relationship for the
Binary 4
related object
Version-stamp
GRP 18 Information about the product that created this entry.
Sync
product_id CHAR 2 ID of the product that created this entry.
product_rel Version, release, and modification level of the product that
CHAR 8
created this entry.
Func-release CHAR 8 Relationship release used to update this entry.
Rel-type Relationship type:

RI
CHAR 2 Referential Integrity

AR
Application Relationship
Depend-full-
PIC S9999 Offset for dependent full name (long object names only)
name-offset
Parent-full-
PIC S9999 Offset for parent full name (long object names only)
name-offset
Long-name-text Full object name (long object names only) for parent and
dependent Db2 long name objects. Includes: total length,
PIC X(550) object type, location name length, location name, creator
name length, creator name, table name length, table
name.

Relationship Details (parent objects only)

The following fields provide information about the Relationship Details and is only included for
parent objects.

Table 5. Relationship Details (parent objects only)

Field Name Type Length Description
rel-description Description of the relationship. For RI relationships, this is the RELNAME
CHAR 30 from the Db2 catalog. For AR relationships, this is the description entered
on the Column Relationships screen.
40 File-AID/RDX Reference

Table 5. Relationship Details (parent objects only) (Continued)

Field Name Type Length Description
Parent-delim-ind Parent delimiter indicator.

0
No delimiter required

1
Delimiter required for Table

2
Delimiter required for Creator

3
CHAR 1 Delimiter required for Table and Creator

4
Delimiter required for Location

5
Delimiter required for Table and Location

6
Delimiter required for Creator and Location

7
Delimiter required for Table, Creator and Location
Depend-delim- Dependent delimiter indicator. See Parent delimiter indicator for
CHAR 1
ind explanation of possible values.
Audit-info Sync GRP 68 Timestamp and User ID for creation and modification of the relationship
Load-tmstmp Timestamp indicating when the relationship was created or loaded into the
CHAR 26 relationship file. The timestamp is written in the following format: YYYY-
MM-DD-HH.MM.SS.NNNNNN
Load-userid CHAR 8 Userid that created or loaded the relationship.
Mod_tmstmp Timestamp indicating when the relationship was last modified. The
CHAR 26 timestamp is written in the following format: YYYY-MM-DD-
HH.MM.SS.NNNNNN
Mod_userid CHAR 8 Userid that last modified the relationship.
Rel-data-DB2
GRP 14 Database information for the relationship
Sync
DBMS-info-
GRP 7 Database information for the parent
parent Sync
DBMS-VRM CHAR 3 DBMS version
DBMS-SubsysID CHAR 4 DBMS subsystem ID
DBMS-info-child
GRP 7 Database information for the dependent
Sync
DBMS-VRM CHAR 3 DBMS version
DBMS-SubsysID CHAR 4 DBMS subsystem ID
Filler CHAR 4 Filler
Parent-full-name-
PIC S9999 Offset for parent full name (long names only)
offset
Depend-full-
PIC S9999 Offset for dependent full name (long names only)
name-offset
Column-source
GRP 112 Parent and child column/field information
Sync
Overview 41

Table 5. Relationship Details (parent objects only) (Continued)

Field Name Type Length Description
Number-cols Binary 2 Number of related columns.
Column-detail (1) Parent and child column/field detail information; occurs 1 to 38 times
GRP 110
Sync depending on the number of related columns
Par-col-name CHAR 31 Parent column/field name
Par-col-sub1 Binary 2 Parent column subscript 1
Par-col-sub2 Binary 2 Parent column subscript 2
Par-col-sub3 Binary 2 Parent column subscript 3
Par-col-type Binary 2 Parent column type
Par-col-length Binary 2 Parent column length
Par-col-offset Binary 4 Parent column offset
Par-no-subscr Binary 2 Number of Parent column subscripts
Par-precision Binary 2 Precision of Parent column
Par-scale Binary 2 Scale of Parent column
Filler Binary 4 Filler
Dep-col-name CHAR 31 Child column/field name
Dep-col-sub1 Binary 2 Child column subscript 1
Dep-col-sub2 Binary 2 Child column subscript 2
Dep-col-sub3 Binary 2 Child column subscript 3
Dep-col-type Binary 2 Child column type
Dep-col-length Binary 2 Child column length
Dep-col-offset Binary 4 Child column offset
Dep-no-subscr Binary 2 Number of Child column subscripts
Dep-precision Binary 2 Precision of Child column
Dep-scale Binary 2 Scale of Child column
Filler Binary 4 Filler
Long-name-text Full object name (long object names only) for parent and dependent Db2
long name objects. Includes: total length, object type, location name
PIC X(550)
length, location name, creator name length, creator name, table name
length, table name.

MVS Record Layout Information

The following fields contain information about the MVS Record Layouts that are used to define the
relationship.

Table 6. MVS Record Layout Information

Field Name Type Length Description
Rel-data-file MVS Record Layout Information; (only applicable if one or both objects of the
GRP 294
Sync relationship are MVS object types)
Num-layouts Binary 2 Number of MVS layouts defined in the relationship
Layout-info (1) Layout information for MVS object in the relationship; occurs 0 to 2 times
GRP 146
Sync depending on the number of MVS objects defined in the relationship.
42 File-AID/RDX Reference

Table 6. MVS Record Layout Information

Field Name Type Length Description
Layout-type Layout type

S
CHAR 1 Single

X
XREF
Layout-DSN CHAR 44 Layout file name
Layout-Member CHAR 10 Layout file member name
XREF-DSN CHAR 44 XREF file name
XREF-Member CHAR 8 XREF file member name
IO-exit-name CHAR 8 IO exit name
Rec-01-name CHAR 31 Rec-01 level name

Creating and Loading the Relationship File

The person who installs File-AID/RDX at your site will create a relationship file and load referential
integrity relationships into it from the Db2 catalog. After the initial installation of File-AID/RDX, you
can use Option 1, Relationship Facilitator, to create a new relationship file (Option A) and load or
update RI into a relationship file (Option L).

You can load and refresh RI relationships defined on different subsystems into a single relationship
file by resubmitting the RI load job for each subsystem. Refer to Batch RI Load on page 182 for more
information. In addition, you can load select RI relationships using the online Load RI option (see 5
- Load RI on page 89) or the L (Load RI) line command (see L on page 93) in the Relationship
Facilitator.

Section Refreshing Relationship File from an Outside Source in the File-AID Advanced Configuration
Guide also includes instructions and a sample program on how to load application relationships from
other relationship sources, such as code generators.

Using the Relationship File

The relationship file is integral to the extract function of File-AID/RDX. The relationship file acts as a
repository containing information about the Db2 referential integrity (RI) relationships and the
application-defined (AR) relationship definitions. File-AID/RDX uses the RI and AR information to
extract data from the objects specified by the relationship information. Subsequently, File-AID/RDX
loads the extracted data into related objects.

File-AID/RDX is designed to exploit the advantages of having all users accessing a single, common
relationship file. Sharing a common relationship file has many benefits. You do not have to
individually set up and document your RI and AR relationships. One individual in your organization
can manage this task. You are not limited, however, to the relationships created by the initial load
job. If a relationship that you need is not defined in the file, File-AID/RDX lets you create or load
one.

In addition, the common relationship file ensures a consistent model for everyone to use and one
that is easy to keep up-to-date. With a common file, all users have access to the most current version
of the relationship file. Changes to the relationship file are implemented through the Relationship
options on the File-AID/RDX Primary Option Menu. You can make changes to RI relationships using
the Load RI option or L (load RI) line command from Option 1, and to AR definitions using the Edit
AR or Add AR options or the E (Edit AR) or A (Add AR) line commands from Option 1. The product
installer or a DBA can run the File-AID/RDX Relationship Facilitator Option L- Batch RI Load
Overview 43

periodically to refresh the file with referential integrity information from the Db2 catalog (see also L-
Batch RI Load on page 90).

Reviewing Relationships in the File

With File-AID/RDX, you can see all of the relationship definitions that exist in the relationship file.
To see these relationships, select the Browse option or use the B (Browse) line command from Option
1, Relationships. Specifically for Db2 objects, File-AID/RDX searches the relationship file for
relationship definitions involving the name of the object you specify to act as a point of reference.
File-AID/RDX displays all of the objects with relationships that match the name of the Db2 object
you specified, when using a pattern for the creator ID of the object. That relationship information
could also be used as a model for extracting related data. This information is displayed on the
Relationship Detail screen (Figure 34 on page 102).

Data Visualizer
The Data Visualizer component of the Topaz Workbench provides another way to view the
relationship definitions in a relationship file. Refer to the Topaz Workbench documentation for more
information on the Data Visualizer.

Using Relationship Definitions from Another Db2 Subsystem

An important concept behind using a common relationship file with File-AID/RDX is that the
product uses the relationship file to store information about RI and AR relationships that reside on
other Db2 subsystems. File-AID/RDX searches the relationship file for relationship information based
on the name of the driving object. You can use these relationship definitions to extract from similarly
related Db2 tables on another subsystem. As a result, you do not have to define relationships for Db2
objects in your subsystem, but rather you can copy data to your subsystem based on a relationship
from another subsystem. In this way, you can model your extract after the relationships defined on a
different subsystem.

For example, you have a set of relationship definitions for a given group of tables in subsystem A. You
want to extract data from a similar group of tables that reside in subsystem B. To perform this extract:

1. specify the table to drive the extract from subsystem B; and

2. use the relationship definitions from subsystem A to view and specify the extract criteria for the
tables in subsystem B.

Refer to Cloning Extract Requests on page 202 for details on accessing relationship information from
one subsystem and using it on another.

Conditional AR Criteria File

The Conditional AR Criteria file contains the selection criteria information created when you define a
data driven application relationship (AR-C) using the COND primary command in option 1 of File-
AID/RDX. See also Relationship Condition Definition on page 151.

The Criteria file must have the following characteristics:

File organization Partitioned (DSORG=PO)

Record format Variable-blocked (RECFM=VB)
Logical record length 300 (LRECL=300)
Minimum block size 304 (BLKSIZE=304)

Conditional AR Criteria files must be maintained with File-AID/RDX

option 1 (see also Relationship Condition Definition on page 151).
44 File-AID/RDX Reference

Extract/Load/Delete Request File

File-AID/RDX uses the extract/load/delete request file to select the data to be extracted using Option
2, Extract, loaded using Option 3, Load, or deleted using Option 4, Delete. This file contains both
relationship criteria and selection criteria as well as load target information. The request file can
contain data for an extract only, load only, extract with continue to load, or delete only request.

The request file has the following characteristics:

File organization Either partitioned or sequential (DSORG=PO or DSORG=PS)

Record format Variable-blocked (RECFM=VB)
Logical record length 1004

Pre-Release 4.3 extract/load request files have fixed or fixed-blocked (RECFM=F or

RECFM=FB) record format. When saving a Pre-Release 4.3 request file, File-AID/RDX will
issue an invalid format message. Specify a new name to save the request file in variable-
blocked (RECFM=VB) format (see also Save Extract Request on page 352).

See File-AID/RDX Extract/Load/Delete Request File on page 368 for more information about how File-
AID/RDX uses this file and how it is structured.

Data Visualizer
The Data Visualizer component of the Topaz Workbench provides another way to view the
relationship definitions in an extract request file. Refer to the Topaz Workbench documentation for
more information on the Data Visualizer.

Extract File
This file is the output from the extract process and the input for the Load and Delete process.

The extract file has the following characteristics:

File organization Sequential (DSORG=PS) or partitioned (DSORG=PO)

Record format Variable-blocked (RECFM=VB)
Logical record length Maximum LRECL determined by File-AID/RDX (default = 27994)

1. File-AID/RDX will dynamically reallocate a sequential extract file to adjust to the

needed space. Dynamic reallocation is only available for sequential files
(DSORG=PS).
2. The maximum data record length (LRECL) that can be extracted into the extract file
is 32,748 (max. of 32,756 minus 4 bytes RDX data, minus 4 bytes VB data). File-
AID/RDX will issue a message when an object file has a longer LRECL, but allow you
to start the extract. However, when a record to be extracted exceeds 32,748, the
extract will fail.

See Extract for more information about how File-AID/RDX uses this file. See File-AID/RDX Extract File
on page 377 for more information about the structure of this file.

Dynamic Reallocation of Extract File

File-AID/RDX will dynamically reallocate a sequential extract file to adjust to the needed space.
Dynamic reallocation is only available for sequential files (DSORG=PS).

When during an extract the allocated space for an extract file is exceeded (X37 abend), File-AID/RDX
initiates a reallocation routine (X37 abend recovery) that creates an intermediary file and copies the
extracted data into it. Then the routine deletes and redefines the original extract file with increased
Overview 45

primary and secondary quantities of the originally allocated space units (BLK, TRK or CYL). File-
AID/RDX uses a multiplier to increase the quantities. The data is then copied from the intermediary
file into the newly allocated extract file, the intermediary file is deleted and File-AID/RDX continues
to add extracted data.

If the extract requires additional space, this routine repeats until the extract file can hold all of the
extracted data or the reallocation attempts a second multi-volume allocation. The dynamic
reallocation routine can request a multi-volume allocation only once during an extract. Multi-
volume allocation is requested when there is no space left on single volume.

When creating the intermediary file, the routine changes the last character
of the file name to a letter between J and R, for example, FRSAMP.EXTRACT
to FRSAMP.EXTRACK. If these files already exist, File-AID/RDX will not create
the intermediary file and the dynamic reallocation will fail.

Extract Summary File

This summary can be created from the extract file and is used for the Load, Delete, or Disguise from
Tape or Multi-Volume File process. When the specified extract output is to tape or cartridge, File-
AID/RDX automatically creates a summary file on DASD.

The summary file has the following characteristics:

File organization Sequential (DSORG=PS) or partitioned (DSORG=PO)

Record format Variable-blocked (RECFM=VB)
Logical record length Maximum LRECL determined by File-AID/RDX

See Specify Extract “TO” File Information on page 338, Load or DCF: Disguise Existing Extract on
page 664 for more information about how File-AID/RDX uses this file.

Discard File
If you request that discarded rows be saved, File-AID/RDX writes rows discarded to the discard file
during SQL Insert and delete processing.

The discard file has the following characteristics:

File organization Sequential (DSORG=PS)

Record format Variable-blocked (RECFM=VB)
Logical record length Maximum LRECL determined by File-AID/RDX

File-AID/RDX uses this file during delete processing and during load processing when you specify the
SQL Insert processing option. See Load and Delete for more information about how File-AID/RDX
uses this file.

The structure of this file is similar to that of the extract file. See File-AID/RDX Extract File on page
377.

User Profile File

File-AID/RDX stores the user profiles as members in the profile file (PDSE). This enables File-AID/RDX
to prefill all required input fields for extract, load, and delete processes with the values stored in the
profile(s).
46 File-AID/RDX Reference

The profile file has the following characteristics:

File organization Partitioned (DSORG=PO)

Record format Variable-blocked (RECFM=VB)
Logical record length 32756

Some of the information maintained in your user profiles includes:

• creator and table name

• file names
• subsystem ID
• SQLID
• file names and member names
• Job statement information
• extract, data disguise, and load options
• extract and load reference lists

The profile information is saved permanently and can be modified in Option 0—Profile. The physical
file name for the profile is displayed in the RDX Profile Screen (see Figure 13 on page 49) and includes
the prefix and midlevel qualifier for the profile. The midlevel qualifier (product parameter variable
RDXPMDQL) is specified during configuration of File-AID/RDX.

Disguise Control File

The Disguise Control File (DCF) determines what disguise criteria is applied to which object. The
actual criteria created by File-AID/Data Solutions will be stored in the Disguise Criteria File that the
Disguise Control File points to.

This file can be created with Option 4- Control in the Data Privacy Menu (see page 610).

The Disguise Control File has the following characteristics:

File organization VSAM-KSDS

Record format Variable-blocked (RECFM=VB)
Logical record length Maximum record size is 6168
Key length 255

See Data Privacy for more information about how File-AID/RDX uses this file.

Disguise Criteria File

The Disguise Criteria File (dataset) contains disguise criteria information created using File-AID/Data
Solutions. Optionally, you can add selection criteria information to your disguise criteria member.
Disguise criteria and XREF members can be stored in the same file.

This file can be created with Option 5- Criteria in the Data Privacy Menu (see page 611).

Disguise criteria files for related extracts should be maintained only

through the bridge to File-AID/Data Solutions using Option 5 Data
Privacy. Editing a disguise criteria file with ISPF causes the file to be
unusable by File-AID/Data Solutions.

The disguise Criteria file has the following characteristics:

File organization Partitioned (DSORG=PO)

Record format Variable-blocked (RECFM=VB)
Overview 47

Logical record length 300 (LRECL=300)

Minimum block size 304 (BLKSIZE=304)

See Data Privacy for more information about how File-AID/RDX uses this file.

Audit Trail File

Audit Trail files are created when Auditing is requested during the disguise operation. A separate
Audit Trail file will be produced for each object being disguised.

The naming convention used for the Audit Trail files is:

prefix.RDXA.DnnnBnnn.Dyymmdd.Thhmmss.Msss

The prefix is specified when the Extract File is disguised. Dnnn identifies the number assigned to the
object in the Extract File. Bnnn is only used when an Audit Trail is produced for an MVS object that
uses an XREF; Bnnn is the layout number within the XREF.

The Audit Trail file has the following characteristics:

File organization Sequential (DSORG=PS)

Record format Variable-blocked Spanned (RECFM=VBS)
Logical record length Maximum LRECL 32760

Use Option A - Print Audit in the Data Privacy Menu (see page 611) to print an audit trail file.

Execute Saved Request (ESR) JCL File

The Execute Saved Request (ESR) JCL File (dataset) contains the generated JCL to execute a saved
extract, load, or delete request along with any override files.

This file can be created with Option 2- JCL/Overrides in the RDX Utilities Menu (see page 691).

The ESR JCL file has the following characteristics:

File organization Partitioned (DSORG=PO)

Record format Fixed-blocked (RECFM=FB)
Logical record length 80 (LRECL=80)

See JCL/Overrides Utility on page 698 for more information about how File-AID/RDX creates and
updates this file.

Object Override File

The Object Override file (dataset) contains the old and new object entries in a request file that may be
overridden at execution time.

This file can be created with Option 2- JCL/Overrides in the RDX Utilities Menu (see page 691).

The Object Override file has the following characteristics:

File organization Partitioned (DSORG=PO) for per request or Sequential (DSORG=PS) for
global override file
Record format Variable-blocked (RECFM=VB)
Logical record length 1004 (LRECL=1004)
48 File-AID/RDX Reference

See JCL/Overrides Utility on page 698 for more information about how File-AID/RDX creates and
updates this file.

SC (Selection Criteria) Override File

The SC (Selection Criteria) Override file (dataset) contains the old and new selection criteria for the
driving object in a request file that may be overridden at execution time.

This file can be created with Option 2- JCL/Overrides in the RDX Utilities Menu (see page 691).

The Selection Criteria Override file has the following characteristics:

File organization Partitioned (DSORG=PO) for per request or Sequential (DSORG=PS) for
global override file
Record format Variable-blocked (RECFM=VB)
Logical record length 1004 (LRECL=1004)

See JCL/Overrides Utility on page 698 for more information about how File-AID/RDX creates and
updates this file.

Option FD—Transfer to File-AID for DB2

Option FD invokes File-AID for DB2 if your site has it installed. The File-AID for DB2 Primary Option
Menu shown in Figure 12 is the first screen displayed when you invoke Option FD.

When you end File-AID for DB2, you return to File-AID/RDX option from which you invoked File-AID
for DB2.

Figure 12. File-AID for DB2 Primary Option Menu

File-AID for DB2 - 17.2 ------ Primary Option Menu --------------- Enter option
OPTION ===> 
More: + 
0 DEFAULTS and USER PARMS USERID - TSOID01 
1 BROWSE TIME - 08:03 
2 EDIT TERMINAL - 3278 
3 UTILITIES PF KEYS - 24 
3.1 - Object Administration CCSID - 00037
3.2 - Create, Model, Drop, Alter DB2 Objects DB2 SSID ===> DSN 
3.3 - Copy Rows Between Tables 
3.4 - Object List Processing 
3.5 - SQL Command Manager 
3.6 - Display, Grant, Revoke or Modify DB2 Privileges 
3.7 - Extract and Load Tables 
3.8 - Column Impact Analysis 
3.9 - Batch Execute SQL with Auto-COMMIT Processing 
4 SQL ANALYSIS - SQL Development and Analysis 
5 PRINT - Print table Data or Audit Trail 
6 RELATIONSHIPS - Maintain relationship definitions 
7 DATA DISGUISE - Define Disguise Criteria and Disguise Extract files
Copyright (c) 1989 - 2016 Compuware Corporation. All Rights Reserved. 
Online Technical Support available at: https://go.compuware.com. 
Type LEGAL on the command line for Copyright/Trade Secret Notice. 
Unpublished - rights reserved under the Copyright Laws of the United States.

 49

Profiles and Global Defaults

The File-AID/RDX main menu displays the current user or site profile for your File-AID/RDX session.
The profile sets all the default values for your extract and load functions, thus enabling you to submit
an extract or load job as a one step process. You select, create, and modify your profiles in Option 0.

Option G, Global Defaults, displays the current File-AID/RDX release level. Here, you also set the
maximum number of entries allowed in your user reference lists for the extract, load and delete
functions. See Option G—Global User Defaults on page 82.

Option 0—Profile
The RDX Profile Screen shown in Figure 13 is displayed when you select Option 0 from the File-
AID/RDX Primary Option Menu. On this screen you select the profile for which you would like to
view or update its settings. Options 1 through 6 set the defaults for the currently selected profile.

Figure 13. RDX Profile Screen

File-AID/RDX --------------- RDX Profile ------------------- Profile loaded 

Option ===> 

Primary commands: menu-number, ALL, CANCEL 
Line commands: S or / to create flow through selected options. 

Active Profile 
Profile Type ===> SITE (SITE, USER or prefix) 
Name ===> RDXFLOW (* or blank for list) 
Description ===> RDXFLOW - FLOW THROUGH THE MENU OPTIONS 
Profile Dataset : FARDX.SITE.PROFILE

_ 1 Batch defaults - Modify session and batch defaults 
_ 2 Extract Defaults - Modify extract parameter defaults 
_ 3 Load Defaults - Modify load and delete parameter defaults 
_ 4 Disguise Defaults - Modify Data Disguise parameter defaults
_ 5 Permanent File - Specify permanent file defaults 
_ 6 Temporary File - Specify temporary file defaults 







Active profile

Profile Type
Specify which profile file to open. If the specified profile doesn’t exit, File-AID/RDX attempts to
create the profile file.

SITE

Identifies the installation wide profile file.

USER
50 File-AID/RDX Reference

Enter USER to select your own profile file (your userid.mlq.PROFILE, see also Profile Dataset).
The TYPE field then displays your userid.

prefix

Identifies a profile file with the specified high level qualifier (up to 26 positions) (see also
Profile Dataset). Entering a prefix that includes the string &USERID will substitute the
current userid when the profile file is allocated. The prefix must not include the midlevel
qualifier.
Example: prefix FDM.&USERID allocates FDM.userid.RDX.PROFILE.

The TYPE field, however, continues to display &USERID.

Name
Specify the profile name (member name in the profile file). Enter an asterisk (*) or leave blank to
display a list.

Description
Enter text that provides a concise description of the profile’s content or purpose.

Profile Dataset
Displays the full name of the physical profile dataset (PDSE) including the prefix and midlevel
qualifier (mlq) for the profile. The midlevel qualifier (product parameter variable RDXPMDQL) is
specified during configuration of File-AID/RDX.

Enter the option number (1 - 6) to select the desired option or enter ALL to step through all options
in sequence. Alternatively, you may also select one or more options with the S or / line command.

1 - Batch Defaults
Displays the Session and Batch Defaults screen where you can set batch job parameters and job
statements for the current profile.

2 - Extract Defaults
Displays the Extract Defaults screen where you can set all the extract related defaults for the
current profile.

3 - Load Defaults
Displays the Load Defaults screen where you can set all the load related defaults for the current
profile.

4 - Disguise Defaults
Displays the Disguise Defaults screen where you can set all the data disguise related defaults for
the current profile.
Profiles and Global Defaults 51

5 - Permanent Files
Displays the Permanent File Defaults screen where you specify all the default names and
parameters for permanent extract and load related files for the current profile.

6 - Temporary Files
Displays the Temporary File Defaults screen where you specify all the default allocation
parameters for temporary extract and load related files for the current profile.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

ALL
Selects all profile options for you to step through in sequence.

CANCEL
Cancels all profile edits since the last save and returns to the File-AID/RDX Primary Option
Menu.

The CANCEL command is also a valid command in any and all of the Profile subpanels.
CANCEL returns to the next higher level panel and discards any changes made in the panel
where CANCEL is entered.
If you specify ALL in the RDX Profile screen or select multiple subpanels, CANCEL returns
to the RDX Profile screen instead of going to the next panel selected, and all changes while
in the CANCELed Profile screen will be discarded. Updates made in screens you exited with
END will be retained, unless you also enter CANCEL on this RDX Profile screen.

END
Saves the current profile and returns to the File-AID/RDX Primary Option Menu.

Select Profile
The Select Profile Screen shown in Figure 14 is displayed when you entered an asterisk (*) or blanked
out the profile field of the File-AID/RDX Primary Option Menu (Figure 1) or the RDX Profile Screen
(Figure 13). Use this screen to select the current profile as well as copy, rename or delete site or user
profiles.

Figure 14. Select Profile Screen

File-AID/RDX --------------- Select Profile ------------------ Row 1 to 3 of 3 

Command ===> Scroll ===> CSR 

Type ===> SITE (SITE, USER or prefix)
Dataset . .: FARDX.SITE.PROFILE 

Line commands - Enter S = Select, R = Rename, C to Copy, D to Delete 
- Profile - New Name - Description --------------------------------------------
_ RDXFLOW RDXFLOW - FLOW THROUGH THE MENU OPTIONS 
S RDXMENU RDXMENU - DISPLAY ALL OF THE MENU OPTIONS 
_ RDXQUICK RDXQUICK - THE QUICKER SETTER UPPER 
******************************* Bottom of data ********************************

52 File-AID/RDX Reference

Specify profile information to display

Type
Specify in which profile file to look for the profile member(s) to display. If the specified profile
doesn’t exit, File-AID/RDX attempts to create the profile file.

SITE identifies the installation wide profile file.

USER identifies your own profile file (your userid). When you enter USER your userid displays to
indicate your USER profile type.

prefix identifies a profile file with the specified high level qualifier (up to 26 positions). Entering
a prefix that includes the string &USERID will substitute the current userid when the profile file is
allocated. The prefix must not include the midlevel qualifier.
Example: prefix FDM.&USERID allocates FDM.userid.RDX.PROFILE

Dataset
Displays the full name of the physical profile dataset including the prefix and midlevel qualifier for
the profile. The midlevel qualifier (product parameter variable RDXPMDQL) is specified during
configuration of File-AID/RDX.

Profile List Area

line command
Enter line command in the first column of the list area. See Line Commands for valid line
commands.

Profile
Lists the profile name (member name in the SITE or USER profile file).

New Name
Space to specify the new profile name when renaming (R line command) or copying (C line
command) the profile.

Description
Text can be used to provide a more detailed description of the profile’s content or purpose.
Description can be entered when copying or renaming a profile.
Profiles and Global Defaults 53

Line Commands

C
Copy the profile. If you leave NEW NAME column blank, the Copy Profile window (Figure 15)
displays where you can specify the new profile name (member name) and profile type, USER,
SITE, or prefix.

If your installation has restricted your access authorization to the SITE or

prefix profile file, the copy attempt to that profile may fail.

In order to copy a profile from the SITE to the USER or prefix profile, set the Profile Type to USER
or prefix in the Copy Profile window.

Figure 15. Copy Profile window

File-AID/RDX --------------- Select Profile ------------------ Row 1 to 3 of 3 

Command ===> Scroll ===> CSR 

Type ===> SITE (SITE, USER or prefix)
Dataset . .: FARDX.SITE.PROFILE 


Copy Profile 
COMMAND ===> 

Copy profile RDXMENU 

Specify new profile information: 

Profile type ===> SITE (SITE, USER or prefix) 
Name ===> 
Description ===> RDXMENU - DISPLAY ALL OF THE MENU OPTIONS 

Press ENTER to process, CANCEL or END to return 


R
Rename the profile. Type the new profile name in the NEW NAME column. If you don’t enter a
name in the NEW NAME column, the Rename Profile window (Figure 16) allows you to enter a
new name and also to modify the old profile description in the Description field.

Figure 16. Rename Profile window

File-AID/RDX --------------- Select Profile ------------------ Row 1 to 3 of 3 

Command ===> Scroll ===> CSR 

Type ===> SITE (SITE, USER or prefix)
Dataset . .: FARDX.SITE.PROFILE 


Rename Profile 
COMMAND ===> 

Rename profile RDXMENU 

Profile type ===> SITE (SITE, USER or prefix) 
Name ===> 
Description ===> RDXMENU - DISPLAY ALL OF THE MENU OPTIONS 

Press ENTER to process, CANCEL or END to return 

54 File-AID/RDX Reference

S
Select the profile (member name in the profile file) to be the current profile. File-AID/RDX
automatically saves the current profile when selecting another profile.

D
Delete the profile (member name) from the profile file.

Editing the Profile Settings

After selecting the profile to edit you then select one or all of the profile options. The profile options
panels provide fields to enter your specific settings.

Navigation
Some of the panels have a large scrollable area. Be sure to navigate to the bottom of the scrollable
area as to not miss any fields. Use the UP and DOWN keys to scroll up or down in the panels.

Use the END (PF3) command to save your entries in the current panel and return to the RDX Profile
Menu. If flow through mode is active, END proceeds to the next selected profile option panel.

Use the PREV (PF10) and/or NEXT (PF11) commands to navigate to the next or previous panel when
in flow through mode.

Enter CANCEL to return to the next higher level panel and discard any changes made in the panel
where CANCEL is entered.

If you specify ALL in the RDX Profile screen or select multiple subpanels, CANCEL returns
to the RDX Profile screen instead of going to the next panel selected, and all changes while
in the CANCELed Profile screen will be discarded. Updates made in screens you exited with
END will be retained, unless you also enter CANCEL on this RDX Profile screen.

Locking a Profile Value

When you enter the TOGGLE (PF4 with KEYLIST ON) command while your cursor is on an input
field, it locks or unlocks the field. A locked profile field prevents you from changing the profile value
during an extract, load or delete session.

Session and Batch Defaults

The Session and Batch Defaults screen shown in Figure 17 is displayed when you select Option 1 from
the RDX Profile Screen. Use this screen to specify the batch defaults for the current profile.
Profiles and Global Defaults 55

Figure 17. Session and Batch Defaults

File-AID/RDX ---------- Session and Batch Defaults --------------------------

COMMAND ===> SITE Profile: RDXMENU 
More: + 
-------------------- Locking Values and Navigation ---------------------------
Any profile value setting can be locked so that it can not be changed on the 
FA/RDX function panels. Values can always be changed in the Profile function.
To LOCK a value place the cursor on the value and press the TOGGLE key. 

----------------------- Session and Batch Defaults ----------------------------
Batch Job Options: 
Region size ===> 8192K (nnnK; nnnM) 
Include a SYSUDUMP DD in JCL ===> Y (Y = Yes; N = No) 
(required for Abend-Aid report) 
Table Progress row count ===> 10000 (* = Object end; 
0 = None; 
nn = rows) 
Increment job name ===> N (Y = Yes; N = No)

Job Statement Information: 
===> 
===> 
===> 
===> 
===> 

NOTE: If the Job Statement Information is specified here, RDX will use this 
information. If not specified here, then the Job Statement Information 
specified via Global Parameters will be used. If not specified via 
Global Parameters, then the latest TSO Job Statement Information will 
be used. 

Batch Job Options Area

Region size
Specify the region size for extract or load batch jobs to be run with this profile.

Include a SYSUDUMP DD in JCL (required for an Abend-AID report)

Specify whether or not the batch job (Extract, Disguise or Load) should generate an Abend-AID
report. Of course, you must have Compuware’s Abend-AID program installed in order to receive
the reports. If Abend-AID is not installed and an abend occurs a standard SYSUDUMP will be
written to this DD statement.

Table Progress Row Count

Values allowed are 0 to 99999999, or *. For an extract with progress report active, the Table
Progress Row Count parameter specifies the update interval per rows extracted for each object. *
(asterisk) means that the progress report is updated each time File-AID/RDX has completed
extracting rows from an object. The value 0 turns off progress reporting. See also Extract Progress
Report on page 399.

Increment job name

Specify whether you want the automatic job name incrementation or not for all jobs using this
profile. If Yes, File-AID/RDX will increment the last character of the job name after each
submission for the current TSO session.
56 File-AID/RDX Reference

Job Statement Information

Specify job card information for batch jobs using the current profile. If left blank here in the
profile, File-AID/RDX will use the job card information specified in Option G—Global User
Defaults on page 82.

When disguising an extract with File-AID Data Privacy defined Dynamic

Privacy Rules (DPR), specify a region size large enough to run Java
(REGION=0M is suggested, 200M is the minimum) in your jobcard. See also
Disguise Extract File on page 71, option 2, DPR.

Extract Defaults
The Extract Defaults screen shown in Figure 18 on page 57 is displayed when you select Option 2
from the RDX Profile Screen. Use this screen to specify the default values for an extract using the
current profile.

This screen has a large scrollable area. Be sure to navigate to the bottom of the scrollable area as to
not miss any fields. Use the UP and DOWN keys to scroll up or down in this screen.
Profiles and Global Defaults 57

Figure 18. Extract Defaults - Scrollable Screen

File-AID/RDX ---------------- Extract Defaults------------------------------

Command ===> SITE Profile: RDXMENU
More: +
-------------------- Locking Values and Navigation --------------------------
Any profile value setting can be locked so that it can not be changed on the 
FA/RDX function panels. Values can always be changed in the Profile function.
To LOCK a value place the cursor on the value and press the TOGGLE key. 

------------------------- All Extract Request Defaults ------------------------
Extract Scope Options:
Direct ===> Y (Y = Yes; N = No; 
P = Plus; C = All Children Only)
Parents ===> Y (Y = Yes; N = No) 
Siblings ===> N (Y = Yes; N = No) 
Indirect ===> N (Y = Yes; N = No) 

Default detail view ===> N (N = None, O = Object, 
R = Relationship) 

Maximum cycles ===> 1 (* for no limit) 
Maximum rows/records 
from all objects ===> * (* for no limit) 
Action at maximum count ===> Q (Q = Quiesce, S = Stop) 
Extract w/ Uncommitted Reads ===> N (Y = Yes; N = No) 

File Options: 
Capture View DDL ===> N (Y = Yes; N = No) 
Capture Alias DDL ===> N (Y = Yes; N = No) 
Capture Synonym DDL ===> N (Y = Yes; N = No) 

Create File-AID/MVS XREF ===> N (Y = Yes; N = No) 
Create record layouts 
for DB2 objects ===> N (Y = Yes; N = No) 
Language ===> 1 (1 = COBOL, 2 = PL/I;
3 = FA COBOL)
Use DB2 Image Copy ===> N (Y = Yes; N = No) 
DB2 Format ===> 2 (1 = Unicode; 
2 = Compatibility; 
convert Unicode; 

---------------------------- Driving Object Defaults --------------------------
DB2 Object Defaults: 
Default SQLID: ===> USER 
Convert To Upper Case? ===> Y (Y = Yes; N = No)

DB2 Environment: 
DB2 Subsystem ===> * 
Location ===> 
Creator ===> 
Table Name ===> 

Driving Object Input Key File Options: 
Extract driven by
Input Key file ===> N (Y = Yes; N = No) 

--------------------------- Panel Customization ------------------------------
Extract Panel Flow Options: 
Default driving object type ===> DB2 (DB2 or MVS) 
First extract panel ===> R (R = Recently Referenced List; 
F = Saved Request File;
S = Single panel extract) 
Display Extract Menu ===> Y (Y = display Extract Menu
N = display first flow panel 
if you select N you must 
have at least one FLOW
menu option below)
Extract Menu contents: 
1 - Driving Object ===> SHOW Place the cursor on value and
2 - Extract Scope ===> SHOW press TOGGLE to change value.
3 - Unrelated Objects ===> SHOW SHOW = Include on extract menu.
4 - Input Key File ===> SHOW LOCK = Lock menu choice.
5 - Selection Criteria ===> SHOW FLOW = Include on the extract menu
6 - Output Key File ===> SHOW and pre-select the option
7 - Extract File ===> SHOW for flow mode navigation. 
8 - Data Privacy ===> SHOW 
9 - Supporting Files ===> SHOW 
10 - Checkpoint/Resumption ===> SHOW 
11 - Continue with Load ===> SHOW 
12 - Save Extract Request ===> SHOW 
13 - View JCL ===> SHOW 
14 - Submit JCL ===> SHOW 
58 File-AID/RDX Reference

All Extract Request Defaults Area

Extract Scope Options Area

Specify the Navigational Criteria Options associated with the current profile. See Extract Scope on
page 247 for detailed information.

Direct
Specify to extract the dependents (children) of the driving object and their dependents.

Extract the dependents of the driving object and their dependents (default).

Do NOT extract the dependents of the driving object and their dependents.

(All Children only) Extract the dependents of the driving object and all of their dependents
only. This option ignores all other Navigational Criteria Options (DPSI) settings, resets them
to DPSI=CNNN, and cannot be modified during the extract specification.

Using the C method to extract data and only its dependent data can lead to extracted data
that is not loadable because of referential integrity issues due to the omitted related parent
data. This can be useful for extracting specific data that is then used for a purge procedure.

(Plus) Extract all of the direct relationships of the driving object, i.e. all of its parents and
first level dependents only. Direct "Plus" means resolve all objects’ parents until there are no
more parents to return. This option ignores all other Navigational Criteria Options (DPSI)
settings, resets them to DPSI=PYNN, and cannot be modified during the extract specification.

The C and P settings for Direct can only be set in the profile. The profile
settings are used to build the relationship tree with its related objects when
starting an extract specification.

Parents
Specify to extract parents of all extracted data to maintain the integrity of the extracted data.

Siblings
Specify to extract other dependents of the extracted parents from the same relationships.

Indirect
Specify to extract other dependents of the extracted parents from other relationships.

Specify the Detail Display Options. See Extract Scope on page 247 for detailed information.
Profiles and Global Defaults 59

Default Detail View

Specify which detail extract scope view is displayed when you enter the Extract Scope display:

None does not display either of the detail extract scope panels.

Object displays the Extract Scope - Object View panel, listing all objects related to the driving
object from which to extract data.

Relationship displays the Extract Scope - Relationship Criteria panel, listing all the
relationships associated with the driving object.

Specify the extract quantity options. See Extract Scope on page 247 for detailed information.

Maximum Cycles
Specify the number of extract cycles after which the extract process should stop. Enter a number
between 1 and 99, or an asterisk (*) to specify no cycle limit.

Maximum Rows From All Objects

Specify the maximum number of rows you want to extract from all related objects. Enter an
asterisk (*) to set no limit.

Action at Maximum Count

Specify how the extract should terminate when the maximum count has been reached:

Quiesce resolves all orphan records after maximum count has been reached. (May result in
more records than the maximum count.)

Stop does not resolve possible orphan records (may extract dependent records without their
parents).

Extract w/ Uncommitted Reads

Specify whether File-AID/RDX should extract data from Db2 objects that include Uncommitted
Reads or not.

Whether the value entered here will be used in the extract screens depends on the setting of the
UNCOMMITTED_READ_DEFAULT parameter of the Db2 Environment PARMLIB member (see also
UNCOMMITTED_READ_DEFAULT in the File-AID Advanced Configuration Guide).
60 File-AID/RDX Reference

File Options Area

Capture View DDL

Specify whether the DDL for Db2 View objects should be saved in the Extract file in order for File-
AID/RDX to create Db2 views for the Load process.

Capture Alias DDL

Specify whether the DDL for Db2 Alias objects should be saved in the Extract file in order for File-
AID/RDX to create Db2 Alias objects for the Load process.

Capture Synonym DDL

Specify whether the DDL for Db2 Synonym objects should be saved in the Extract file in order for
File-AID/RDX to create Db2 Synonym objects for the Load process.

Create File-AID/MVS XREF

Specify whether or not to create a File-AID/MVS XREF (record layout cross reference) file when
File-AID/RDX performs the extract. File-AID/RDX will create the record layout cross reference for
the data elements of the extract file. See also File-AID/MVS XREF File on page 395 for detailed
information.

Create Record Layouts for DB2 objects

Specify whether or not to create a COBOL, PL/I, or FA COBOL record layout file when File-
AID/RDX performs the extract. See also File-AID/RDX Record Layout File on page 392 for detailed
information.

Language
Specify whether the record layout will be in COBOL (1), PL/I (2), or FA COBOL (3) format. FA
COBOL (3) creates a File-AID COBOL layout with special type VAR for Db2 column type VCHAR
or VC (see also Table 13 on page 306), for example when the FIRSTNME column is defined to Db2
as VARCHAR(12), with FA COBOL it will be generated as 10 FIRSTNME PIC X(12) VAR. Use option
3, FA COBOL when you need to define disguise criteria for Db2 tables with column type
VARCHAR.

Use DB2 Image Copy

Specify whether File-AID/RDX should extract data from the most recent full Db2 Image Copy or
not. File-AID/RDX must be executed from an authorized library. This option is only available if
your site installation set the parameter variable ALLOW_EXTRACT_FROM_DB2_IMAGE_COPY to
Yes. Refer to ALLOW_EXTRACT_FROM_DB2_IMAGE_COPY in the File-AID Advanced
Configuration Guide.

DB2 Format
Specify whether Db2 data extracted from tables with Unicode encoding is written to the extract
file in Unicode or EBCDIC format.
Profiles and Global Defaults 61

Unicode option will write the data using Unicode encoding without utilizing IBM z/OS
Conversion Services.

Compatibility format will maintain the EBCDIC encoding utilizing IBM z/OS Conversion
Services used in previous releases of File-AID/RDX (default).

Driving Object Defaults Area

DB2 Object Defaults Area

Default SQLID
Specify the Db2 SQLID to be used during an extract using this profile.

Convert To Upper Case

Controls whether File-AID/RDX always converts lowercase characters to uppercase for Db2
objects (creator IDs and table names, for example). If set to YES (default), you must enclose
lowercase characters in quotes to prevent conversion to uppercase (example: "order_table"
remains lowercase, but order_table converts to ORDER_TABLE. Set it to NO to allow lowercase
characters. NO is recommended for DBCS mode.

Db2 utilities do NOT support enclosing lowercase creator IDs with quotes.

DB2 Environment Area

DB2 Subsystem
Specify the Db2 subsystem ID for the Db2 objects to be extracted using this profile.

Location
Specify the location of the object you want to drive the extract if it resides in a remote Db2
subsystem. The location you enter must be defined in the Db2 system catalog table,
SYSIBM.LOCATIONS.

You may leave this field blank if the table you want to drive the extract is in the Db2 subsystem
in the DB2 Subsystem field.

Creator
Specify the authorization ID of the owner of the table, view, synonym, or alias that you want to
drive the extract process using this profile.
62 File-AID/RDX Reference

Table Name
Specify the name of the table, view, alias, or synonym that you want to drive the extract process
using this profile. For more information about how File-AID/RDX supports view, aliases, and
synonyms in Extract, see Use of Db2 Views on page 223 and Use of Aliases and Synonyms on page
223.

Driving Object Input Key File Options

Extract driven by Input Key file

Specify Yes only when you are using an input (external) key file as selection input criteria for the
driving table. No is the default.

Panel Customization
The profile also stores information on what panels will be part of the online extract specification
process, allowing you to customize the flow through the extract panels.

Extract Panel Flow Options

Default driving object type

Specify whether default driving object for the extract is a DB2 or MVS object.

First extract panel

Specify which panel displays first when selecting Option 2 Extract from the File-AID/RDX
Primary Option Menu.

Reference List (default)

Request File

Single panel extract

Display Extract Menu

Yes will display the Extract Menu, No will bypass the display of the Extract Menu and go directly
to the first FLOW panel, unless Single Panel Extract has been set. In that case, No disables the
MENU command on the Extract - DB2 Driving Object and Extract - MVS Driving Object panels,
not allowing you to switch to the full Extract Menu.

Extract Menu contents

For each of the Extract Menu options you can specify whether the menu option will be displayed,
locked or its selection automatically included in the extract panel flow.

Place the cursor on value in each field and press TOGGLE (PF4) to change the value.

The toggle values are:

Profiles and Global Defaults 63

SHOW
Include on extract menu.

LOCK
Lock menu choice.

FLOW
Include on extract menu and pre-select the option for flow mode navigation. When your first
extract panel is either Reference List or Request File and Display Extract Menu is set to No, you
must set at least one Extract Menu option to FLOW.

Load Defaults
The Load Defaults screen shown in Figure 19 on page 64 is displayed when you select Option 3 from
the RDX Profile Screen. Use this screen to specify the default values for a load using the current
profile.

This screen has a large scrollable area. Be sure to navigate to the bottom of the scrollable area as to
not miss any fields. Use the UP and DOWN keys to scroll up or down in this screen.
64 File-AID/RDX Reference

Figure 19. Load Defaults - Scrollable Screen

File-AID/RDX ----------------- Load Defaults --------------------------------

Command ===> SITE Profile: RDXMENU
More: +
-------------------- Locking Values and Navigation --------------------------
Any profile value setting can be locked so that it can not be changed on the 
FA/RDX function panels. Values can always be changed in the Profile function.
To LOCK a value place the cursor on the value and press the TOGGLE key. 

--------------------------- DB2 Data Defaults -------------------------------
Target DB2 Enxironment:
Default SQLID: ===> 
SSID ===> * 
Location ===> 
Creator ===> 
Index name prefix value ===> 
Index name suffix value ===> 

DB2 Load Method ===> DB2 (DB2 OR SQL) 

Auto Create Defaults for DB2 Objects: 
Database ===> 
Tablespace ===> 
Implicit Tablespace ===> N (Y = Yes; N = No) 
STOGROUP ===> 
Primary Quantity(K) ===> 20 
Secondary Quantity(K) ===> 15 
Freepage ===> 10
Pctfree ===> 10 
Buffer Pool ===> BP0
Space recalculation ===> N (Y = Yes; N = No) 

....................Defaults for Load Method = SQL Insert .....................
Existing Data Options: 
Delete all rows ===> N (Y = Yes; N = No) 
Replace matches ===> Y (Y = Yes; N = No) 

Processing Options: 
Lock during load ===> N (Y = Yes; N = No) 
Commit Every Nth Row ===> 2000 (1 - 2000) 
Maximum Rows to Discard ===> * (* for no maximum) 
Save Discarded Rows ===> N (Y = Yes; N = No) 
....................Defaults for Load Method = DB2 Load........................
Existing Data Option: 
Delete all rows ===> Y (Y = Yes; N = No) 

Processing Options: 
Log Option ===> 1 (1 = Log; 2 = Image Copy 
3 = Repair; 4 = Inline Image Copy)
--------------------------- MVS Data Defaults ---------------------------------
Auto Create Defaults for MVS Objects: 
High level qualifier ===> 
File name suffix value ===> 
Space recalculation ===> Y (Y = Yes; N = No) 
Storage Class ===> 
Management Class ===> 

Existing Data Options for MVS Objects:
Delete and Define ===> Y (Y = Yes; N = No) 
Replace Matches ===> Y (Y = Yes; N = No) 

--------------------- Objects with Zero Rows Extracted ------------------------
Include Objects with Zero Rows Extracted: 
Generate Control Datasets ===> N (Y = Yes; N = No) 

--------------------------- Panel Customization ------------------------------- 
Load Panel Flow Options: 
First load panel ===> R (R = Recently Referenced List; 
F = Saved Request File)
Display Load Menu ===> Y (Y = display Load Menu
N = display first FLOW panel)

Load Menu Contents: 
1 - Load Object Specification ===> FLOW Place the cursor on value and
2 - Source to Target Mapping ===> FLOW press TOGGLE to change value.
3 - Target Environment ===> SHOW SHOW = Include on load menu.
4 - Existing Data Options ===> SHOW LOCK = Lock choice on load menu.
5 - Processing Options ===> SHOW FLOW = Include on the load menu
6 - Save Load Request ===> SHOW and pre-select the option
7 - View JCL/View REXX ===> SHOW for flow mode navigation.
8 - Submit JCL/Execute REXX ===> SHOW 
Profiles and Global Defaults 65

DB2 Data Defaults

Target DB2 Environment Area

Default SQLID
Specify the Db2 SQLID to be used during load and delete processing using this profile. If blank,
SQLID defaults to USER.

SSID
Specify the Db2 subsystem ID of the target Db2 objects to be loaded using this profile.

Location
Specify the location of the target objects you want to load if they reside in a remote Db2
subsystem. The location you enter must be defined in the Db2 system catalog table,
SYSIBM.LOCATIONS.

You may leave this field blank if the Db2 objects you want to load reside in the Db2 subsystem
you specified in the SSID field.

Creator
Specify the authorization ID of the owner of the target Db2 objects that you want to load using
this profile.

Index name prefix value

Specify the default prefix to be added to the index names in the target environment. Leave blank
if you don’t want to specify a default prefix.

Index name suffix value

Specify the default suffix to be added to the index names in the target environment. Leave blank
if you don’t want to specify a default suffix.

If an index were named XDEPT1, adding a prefix of T would make the new index name
T_XDEPT1, adding a suffix of T would make it XDEPT1_T, adding both prefix and suffix would
make it T_XDEPT1_T.

DB2 Load Method

Specify whether you want to load Db2 data using SQL INSERT statements or the IBM Db2 Batch
Load Utility. See also SQL Insert and Db2 Load Utility Load Options on page 429.

SQL

Perform the load using SQL INSERT statements. This option allows you to update rows if they
already exist.

DB2

Perform the load using the IBM Db2 Batch Load Utility.
66 File-AID/RDX Reference

Auto Create Defaults for DB2 Objects Area

When File-AID/RDX creates Db2 objects it uses the DDL as extracted. You can specify the following
default values to override the extracted values.

Database
Specify the default Db2 database in which the new tables will reside. When loading an extract file
created with a Release earlier than 4.0, the database must already exist in the target environment.

Leave blank if the target database name should be the same as the source.

Tablespace
Specify the default tablespace in which the new tables will reside. Leave blank if the target
tablespace name(s) should be the same as the source. When loading an extract file created with a
Release earlier than 4.0, the tablespace must already exist in the database specified in the
Database field above. See also Create/Edit Db2 Tablespace on page 465.

Implicit Tablespace
Specify whether Db2 should create an implicit tablespace for each table to be created. If set to
Yes, it overrides the name specified in the Tablespace field above. Implicit tablespace request does
not apply to tables that are extracted from multi-table or partitioned tablespaces.

STOGROUP
Specify the default target storage group for database, index, and tablespace creation.

Primary Quantity(K)
Specify the default number of storage units to be allocated for the file in which your tablespace or
index is to reside.

Secondary Quantity(K)
Specify how much more space should be allocated for the file if it exceeds the primary quantity.

Freepage
Specify how often the system should leave a free page when the tablespace or index is updated.

Pctfree
Specify how much of each page to leave free when the tablespace or index is updated.
Profiles and Global Defaults 67

Buffer Pool
Specify the default Db2 buffer pool name associated with the target database, tablespace or index.

Space recalculation
Specify Yes if you want File-AID/RDX to calculate the space allocation for the new target Db2
objects based on the extracted data. The calculated space will not exceed the space allocation of
the source.

When set to No the Db2 allocation parameters for the new object will be the same as for the
source object.

Defaults for Load Method = SQL Insert

Existing DB2 Data Options Area

Delete all rows

Specify whether or not File-AID/RDX should delete ALL of the data residing in the target objects
before it loads data from the extract file. For Db2 tables, Db2 delete rules are in effect.

Replace Matches
When you are adding data to an object that is not empty and the INSERT operation fails because
the row or record already exists, specify whether or not it should be replaced. Only applies to SQL
INSERT load option.

Processing Option Defaults Area

Lock During Load

Indicates whether or not tables will be locked during load. You cannot change the value in this
field if File-AID/RDX was configured at installation to prevent users from locking tables. In this
case, the values in this column will always be set to No.

Commit Every Nth Row

Specify the number of rows File-AID/RDX should insert or update before it performs a Db2
COMMIT. This value must be less than or equal to the value specified for the Max Commit
Interval installation parameter.

Maximum Rows to Discard

Specify the maximum number of errors encountered before processing stops. Specify an asterisk
(*) for no maximum or a value greater than 0. Specify 1 if you want processing to stop if any
errors are encountered. Specify YES in the Save Discarded Rows field to save these rows for
future use. The discard file need not exist to specify a value in this field.

Save Discarded Rows

Specify whether or not to save rows, or records, that could not be inserted or updated.
68 File-AID/RDX Reference

Defaults for Load Method = DB2 Load

Existing DB2 Data Options Area

Delete all rows

Specify whether or not File-AID/RDX should delete ALL of the data residing in the target objects
before it loads data from the extract file. For Db2 tables, Db2 delete rules are in effect.

Processing Option Defaults Area

Log Option
Specify which log option to use during the execution of the Db2 LOAD utility for the Db2
objects.

Log Db2 logging will occur during the load process.

Image Copy Db2 logging of data will not occur during the load process. Db2 sets a COPY
PENDING restriction against the tablespace being loaded. An IMAGECOPY step is generated
to remove the COPY PENDING status.

Repair Db2 logging of data will not occur during the load process. Db2 sets a COPY
PENDING restriction against the tablespace being loaded. A REPAIR step is generated to set
NOCOPYPEND for the tablespace(s). To execute this utility, the privilege set of the process
must include one of the following:

• REPAIR privilege for the database

• DBADM or DBCTRL authority for the database
• SYSCTRL or SYSADM authority.

Inline Image Copy When “Delete All” is also set to ‘YES’ this option will invoke inline image
copy. Db2 logging of data will not occur during the load process. The tablespace into which
the data is being loaded will not be placed into a copy pending state.

If there are multiple tables in a tablespace then inline image copy is not used; instead an
IMAGECOPY step is generated to remove the COPY PENDING status.

MVS Data Defaults

Auto Create Defaults for MVS Objects Area

High level qualifier

Specify the default high level qualifier you want to use when creating MVS objects in the target
environment.
Profiles and Global Defaults 69

File name suffix value

Specify the default file name suffix to be added when creating MVS objects in the target
environment, e.g. FRSAMP.ORDERTAB becomes FRSAMP.ORDERTAB.NEW.

Space recalculation
Specify YES if you want File-AID/RDX to calculate the space allocation for the new target file
based on the extracted data. The calculated space will not exceed the space allocation of the
source.

When set to NO the MVS file allocation parameters for the new object will be the same as for the
source file.

Storage Class
Specify the default storage class for the target files.

Management Class
Specify the default management class for the target files.

Existing Data Options for MVS Objects Area

Delete/Define
Specify whether or not File-AID/RDX should delete the target file and then redefine it before it
loads data from the extract file.

Yes

File-AID/RDX generates a step in the JCL to delete the object and then create it again before
loading data.

No

Appends data to the existing target object.

Replace Matches
When you are adding data to an object that is not empty and the INSERT operation fails because
the row or record already exists, specify whether or not it should be replaced. Only applies if the
target object is indexed.

Objects with Zero Rows Extracted Area

Generate Control Datasets

Specify whether or not File-AID/RDX should create Load Control Table (LCT) datasets and SORT
datasets for objects which have zero rows extracted. By default Load will not process objects with
zero rows extracted.

Yes
70 File-AID/RDX Reference

File-AID/RDX generates LCT and SORT datasets and associated JCL steps for objects with
zero rows extracted.

No

Do not generate these datasets and JCL steps.

Panel Customization
The profile also stores information on what panels will be part of the online load specification
process, allowing you to customize the flow through the load panels.

Load Panel Flow Options

First load panel

Specify which panel displays first when selecting Option 3 Load from the File-AID/RDX Primary
Option Menu.

Recently Referenced List (default)

Saved Request File

Display Load Menu

YES will display the Load Menu, NO will bypass the display of the Load Menu and go directly to
the first FLOW panel. When set to No, you must set at least one Load Menu option to FLOW.

Load Menu contents

For each of the Load Menu options you can specify whether the menu option will be displayed,
locked or its selection automatically included in the load panel flow.

Place the cursor on value in each field and press TOGGLE to change the value.

The toggle values are:

SHOW
Include on load menu.

LOCK
Lock menu choice.

FLOW
Include on load menu and pre-select the option for flow mode navigation. When Display Load
Menu is set to No, you must set at least one Load Menu option to FLOW.
Profiles and Global Defaults 71

Disguise Defaults
The Disguise Defaults screen shown in Figure 20 on page 71 is displayed when you select Option 4
from the RDX Profile Screen. Use this screen to specify the default values for the data disguise option
using the current profile.

This screen has a large scrollable area. Be sure to navigate to the bottom of the scrollable area as to
not miss any fields. Use the UP and DOWN keys to scroll up or down in this screen.

Figure 20. Disguise Defaults - Scrollable Screen

File-AID/RDX -----------------Disguise Defaults ------------------------------

Command ===> SITE Profile: RDXMENU
More: +
-------------------- Locking Values and Navigation --------------------------
Any profile value setting can be locked so that it can not be changed on the 
FA/RDX function panels. Values can always be changed in the Profile function.
To LOCK a value place the cursor on the value and press the TOGGLE key. 

------------------------- All Disguise Request Defaults -----------------------
Disguise Extract File ===> 3 (1 = Use DCF; 2 = Use DPR; 3 = No) 
Retain pre-disguise file ===> Y (Y = Yes; N = No) 
Create audit trail ===> N (Y = Yes; N = No) 
Audit trail file prefix ===> 

Audit Trail Allocations: 
UNIT ===>
Storage Class ===>
Management Class ===>

Files Used During Disguise: (Enter file name or pattern)
Business Rules ===>
DCF: Disguise Control ===> 
Disguise Criteria ===> 
DPR: Repository Name ===>
Project Name ===>

------------------------- Panel Customization -------------------------------
Disguise Panel Flow Options: 
Default NEW object type ===> DB2 (DB2 or MVS)
First Disguise panel ===> R (R = Recently Referenced List; 
F = Saved Request File
S = NEW Object List)


All Disguise Request Defaults

Disguise Extract File

Specify whether File-AID/RDX should disguise the extracted data as part of the extract batch job
or not. When set to 1 (DCF) or 2 (DPR), all extracted objects which have disguise criteria defined
in the Disguise Control file (DCF) or in the Dynamic Privacy Rules Project (DPR) will be
disguised.

Use DCF. Disguise the extracted data using a disguise control file (DCF). This option requires
installation of Compuware’s File-AID/Data Solutions.

Use DPR. Disguise the extracted data using a Dynamic Privacy Rules Project (DPR). This
option requires installation of Compuware’s File-AID/Data Solutions and the File-AID Data
Privacy component of the Topaz Workbench.

3
72 File-AID/RDX Reference

No Disguise. The extracted data will not be disguised.

When disguising an extract with File-AID Data Privacy defined Dynamic Privacy Rules
(DPR), specify a region size large enough to run Java (REGION=0M is suggested, 200M
is the minimum) in your jobcard. See also Job Statement Information on page 56.

Retain Pre-Disguise File

Specify whether File-AID/RDX should retain the masked temporary extract file after a successful
extract with disguise or not. Regardless of this setting, the pre-disguise file is always retained
should the disguise step not complete successfully. You may want to retain the pre-disguise file
for testing different disguise criteria on the same extract data.

Create Audit Trail

Specify whether or not the related extract disguise process should produce an audit trail report for
each object whose data is subject to be disguised.

Audit trail file prefix

Specify the prefix to be used for the disguise audit trail reports. Prefix plus USERID can be up to
14 positions, the remainder of the dataset name will follow the above mentioned naming
convention. If prefix is blank, only the USERID will be used. Any value specified will be appended
to the USERID. Precede the prefix value with a single quote (‘) to use the value without the
USERID.

Audit Trail Allocations Area

Unit
Specify the default unit for the disguise audit trail files.

Storage Class
Specify the default storage class for the disguise audit trail files.

Management Class
Specify the default management class for the disguise audit trail files.

Files Used During Disguise Area

Business Rules
Specify the name of the file to be used as the default business rules file for data disguise. The
business rules files is used when File-AID/Data Solutions operates on date fields; it can also be
used by field exits. Refer to File-AID/Data Solutions Parameters on page 669 for more
information.
Profiles and Global Defaults 73

DCF: Disguise Control

Specify the name of the file to be used as the default Disguise Control File (DCF). The Disguise
Control File keeps track of which disguise criteria is applied to which extract object and its
related objects. If the file does not exist, use Option 4- Control in the Data Privacy Menu (see
page 610) to allocate it. Refer to Disguise Control File on page 46 for more information.

DCF: Disguise criteria

Specify the name of the file to be used as the default disguise criteria file. File-AID/RDX generates
the member name for the disguise criteria member when defining disguise criteria through the
File-AID/Data Solutions interface.

Refer to Disguise Criteria File on page 46 for more information.

DPR: Repository Name

Specify the name of the Repository to be used as the default repository with Disguise Extract File
option 2 for this profile (see Disguise Extract File on page 71). The repository stores the Dynamic
Privacy Rules Projects created with the File-AID Data Privacy component of the Topaz
Workbenchk.

Specify the full repository name (up to 128 characters). Leave blank or enter an asterisk (*) by
itself for a list of all repositories. Then select the desired repository from the list (see Privacy
Repository List on page 74).

If the Repository Name field is blank, File-AID/RDX will use the name specified in Option G—
Global User Defaults (see DPR: Repository Name on page 83). The Repository Name must be set
properly, and will be used in combination with Dynamic Privacy Rules Project Name (see also
DPR: Project Name) throughout the rest of the product.

DPR: Project Name

Specify the name of the Dynamic Privacy Rules Project to be used as the default Dynamic Privacy
Rules Project for this profile. The Dynamic Privacy Rules Project keeps track of how to apply the
privacy rules to which extracted data element. This option requires installation of Compuware’s
File-AID/Data Solutions and File-AID Data Privacy. Refer to Project Name on page 613 for more
information.

Specify the full project name (up to 128 characters) or a pattern ending with an asterisk (*) for a
list of matching projects. Asterisk (*) by itself lists all projects. When entering a pattern, it will
present a list of all matching projects when used during the disguise specification. Then, you can
select the desired project from the list (see Privacy Project List on page 74).

Panel Customization
The profile also stores information on what panels will be part of the online data disguise
specification process, allowing you to customize the flow through the disguise panels.

Disguise Panel Flow Options

Default NEW object type

Specify whether default object type for the data disguise is a DB2 or MVS object.
74 File-AID/RDX Reference

First Disguise panel

Specify which panel displays first when selecting Option 5 Data Disguise from the File-AID/RDX
Primary Option Menu.

Recently Referenced List

Saved Request File

NEW Object List

Privacy Repository List

The Privacy Repository List Screen lists all File-AID Data Privacy Repositories when you specified an
asterisk (*) in the DPR: Repository Name field of the Disguise Defaults screen (Figure 20 on page 71)
or the Global User Defaults Screen (Figure 25 on page 82). Select the desired repository name and
press <Enter> .

Figure 21 shows the Privacy Repository List Screen.

Figure 21. Privacy Repository List Screen

File-AID ------------- Privacy Repository List ------------ SELECT REPOSITORY 

COMMAND ===> SCROLL ===> CSR 
Use ENTER to process 
* denotes Unavailable Repository 
----- R E P O S I T O R Y N A M E -------------------------------------- 
_ FA-Data-Privacy 
* FA-Data-Privacy-SQLServer 
***************************** END OF REPOSITORY LIST **************************



REPOSITORY NAME
Displays the name of the available File-AID Data Privacy Repository.

When a repository is unavailable (disabled), its entry is marked with an asterisk (*) in the line
command column. If you select an unavailable repository, the following short message is
displayed:

DISABLED REPOSITORY

Press PF1 to view the long message:

DR076-CANNOT SELECT DISABLED/UNAVAILABLE REPOSITORY

Privacy Project List

The Privacy Project List Screen lists all File-AID Data Privacy projects that match the full name or
pattern you specified in the DPR: Dynamic Privacy Project field. Select the desired project name and
press <Enter> .

Figure 22 shows the Privacy Project List Screen.

Profiles and Global Defaults 75

Figure 22. Privacy Project List Screen

File-AID/Data Solutions Privacy Project List --------- Select Criteria Project

COMMAND ===> SCROLL ===> CSR
Use ENTER to process
Repository Name: FA-Data-Privacy
----- P R O J E C T N A M E ---------------- Description ------------------
_ ALPHA Project ALPHA Checklist
_ SSID Social Sec. Disguise
_ EMPNBR Employee No. privacy project
_ Encryption Encryption privacy project



Repository Name
Displays the name of the selected File-AID Data Privacy Repository.

PROJECT NAME
Displays the name of the Privacy Project. You created the Privacy Project with the File-AID Data
Privacy plugin of the Topaz Workbench.

Description
Displays the description of a Privacy Project if a description was entered when the Privacy Project
was created with the File-AID Data Privacy plugin of the Topaz Workbench.

Permanent File Defaults

The Permanent File Defaults screen shown in Figure 23 is displayed when you select Option 5 from
the RDX Profile Screen. Use this screen to specify the default values for permanent File-AID/RDX files
when using the current profile.

This screen has a large scrollable area. Be sure to navigate to the bottom of the scrollable area as to
not miss any fields. Use the UP and DOWN keys to scroll up or down in this screen.
76 File-AID/RDX Reference

Figure 23. Permanent File Defaults - Scrollable Screen

File-AID/RDX Permanent Dataset Defaults 

COMMAND ===> SITE Profile: RDXMENU
More: +
------------------------- Permanent File Defaults -----------------------------
Files Used During Extract: (Enter file name or pattern)
Relationship file ===>
Extract file ===> EXTRACT
Extract Summary ===> SUMMARY
Input Key file ===> KEYFILE
Output Key file ===> IMSKEYS
Extract request ===> 
MVS driving object ===> 

Supporting Files for MVS Objects: (Enter file name or pattern)
Record Layouts ===> 
XREF ===> XREF

Files Used During Load: (Enter file name or pattern)
Discard file ===> DISCARD

Files Used for Execute Saved Requests: (Enter file name or pattern)
ESR JCL file ===> 
Override file ===> 
SC Override file ===> 

Permanent File Allocations:
UNIT ===> SYSDA
Storage Class ===> 
Management Class ===> 

Extract File Allocations and Defaults:
Space units ===> CYL (BLKS; TRKS; CYLS)
Primary quantity ===> 10 (In above units)
Secondary quantity ===> 2 (In above units)
Compress ===> N (N = No; V=VARCHAR; C=Compress)

Control File Allocations:
UNIT ===> SYSDA
Storage Class ===> 
Management Class ===> 


In any of the fields asking for a file name you may enter a an asterisk (*) or pattern and File-AID/RDX
presents a selection list for you to select the desired file.

Files Used During Extract Area

Relationship file
Specify the name of the default File-AID/RDX relationship file to be used for this profile. Refer to
Relationship File on page 37 for more information about the relationship file.

Extract file
Specify the name of the default File-AID/RDX extract file to be used for this profile. This file is
the output from the extract process and the input for the Load process. Refer to Extract File on
page 44 for more information.

Extract Summary
Specify the name of the default File-AID/RDX extract summary file to be used for this profile.
This summary is created from the extract process and used for the Load, Delete, or Disguise from
Tape process. Refer to Extract Summary File on page 45 and Specify Extract “TO” File Information
on page 338 for more information.
Profiles and Global Defaults 77

Input Key file

Specify the name of the default File-AID/RDX Input (external) Key file to be used for this profile.
This Input Key file is used as selection criteria for the driving object. Refer to Input Key File
Specification on page 295 for more information.

Output Key file

Specify the name of the default File-AID/RDX Output Key file to be used for this profile. File-
AID/RDX will copy the extracted key values for the selected KEY relation into the Output key file.
This Output Key file can be used as the Input Key file for another extract or other process of your
choosing.If the relationship is to an IMS segment, the resulting key file can then be used by File-
AID for IMS to extract the related IMS data. Refer to Output Key Files on page 330 for more
information.

Extract Request
Specify the name of the default File-AID/RDX Extract Request file to be used with this profile.
File-AID/RDX will copy the extract request into the named file. The request file can then be used
as a model for a future extract request.

MVS Driving Object

Specify the name of the default MVS driving object for extract and load requests.

Supporting Files For MVS Objects Area

Record Layouts
Specify the name of the default File-AID/RDX record layouts (copybook) file to be used for this
profile. Refer to Record layout file on page 98 for more information.

XREF
Specify the name of the default File-AID/RDX XREF file to be used for this profile. Refer to XREF
file on page 234 for more information.

Files Used During Load Area

Discard File
Specify the default name of the file to which discarded rows will be saved. The discard file must
be sequential. Refer to File for Discarded Rows on page 503 for more information.

Files Used for Execute Saved Requests Area

ESR JCL file

Specify the default name of the file to which Execute Saved Request (ESR) JCL will be saved. The
ESR JCL file must be PDS. Refer to ESR JCL File on page 699 for more information.
78 File-AID/RDX Reference

Override file
Specify the default name of the file to which the template object override file will be saved. The
override file can be sequential or PDS. Refer to Object Override File on page 699 for more
information.

SC Override file
Specify the default name of the file to which the SC (Selection Criteria) override file will be saved.
The override file can be sequential or PDS. Refer to SC Override File on page 699 for more
information.

Permanent File Allocations Area

Unit
Specify the default unit for the permanent files. File-AID/RDX will verify that the unit specified is
a valid generic unit (for example, SYSDA) on the LPAR where you are currently logged on.

Storage Class
Specify the default storage class for the permanent files.

Management Class
Specify the default management class for the permanent files.

Extract File Allocations and Defaults

Space Units
Specify whether space for the new file will be allocated in blocks (BLK), tracks (TRK), or cylinders
(CYL).

Primary QTY
Specify the initial number of space units that will be allocated for the new file.

Secondary QTY
Specify the number of space units that will be allocated for each secondary extent.

Compress
Specify one of the compress options for the extracted data in the extract file:

C Compress; The extracted data will be compressed to reduce the file size and
preserve disk space. The entire data record is compressed. This technique
provides the greatest amount of data compression. File-AID/RDX recognizes these
compressed extract files as valid input files for all functions: Load, Delete, and
Disguise.
Profiles and Global Defaults 79

V VARCHAR compression only affects VARCHAR, LONGVAR, VARGRAPHIC, and

LONGVARGRAPHIC columns of Db2 objects; it will not apply to MVS objects. The
VARCHAR compression option only writes the actual data within each VARCHAR
column without padding the records with trailing blanks; the length of a
VARCHAR column will vary for each row based on the data within the row.
VARCHAR data written to the Extract file using VARCHAR compression will be
readable since only the trailing blanks will be dropped.

File-AID/RDX recognizes these compressed extract files as valid input files for all
functions: Load, Delete, and Disguise..
N File-AID/RDX won’t compress the extracted data.

If you intend to use a compressed extract file outside of File-AID/RDX, for example to
load the extract file via File-AID/EX or manipulate it with File-AID/Data Solutions, you
must decompress it beforehand. Use the decompress utility provided with the File-
AID/RDX Utilities to decompress a compressed extract file.

Control Allocations Area

Control files include the following datasets:

• Conditional AR file,
• Execute Saved Request files,
• Layout file, XREF file,
• Output Key file,
• Discard file,
• Summary file,
• Extract Request file,
• Load Request file,
• Delete Request file,
• Disguise Criteria file,
• various reports if they are saved as files.

Control files also include datasets created when generating JCL and are deleted after successful
execution:

• FBCNTL,
• VBCNTL,
• EXTPARMS.

Unit
Specify the default unit for the control files. Control files are required to be on DASD. Typically
this will be the same unit as used for permanent files. File-AID/RDX will verify that the unit
specified is a valid generic unit (for example, SYSDA) on the LPAR where you are currently logged
on.

Storage Class
Specify the default storage class for the control files.

Management Class
Specify the default management class for the control files.
80 File-AID/RDX Reference

Temporary File Defaults

The Temporary File Defaults screen shown in Figure 24 is displayed when you select Option 6 from
the RDX Profile Screen. Use this screen to specify the default values for Temporary File-AID/RDX files
when using the current profile. File-AID/RDX uses temporary files during extract, load, delete, and
disguise processing.

The format of a temporary file name with prefix and suffix is:

7 character user ID:

userid.prefix.XXXXXXXX.Dnnnnnn.Tnnnnnn.suffix

where the 3rd level dataset name qualifier XXXXXXXX is a constant indicating the type of the temporary
file, for example, SPLIT001 or CKSRTOUT.

8 character user ID1:

userid.prefix.XXXXXXX.Dnnnnnn.Tnnnnnn.suffix

where the 3rd level dataset name qualifier XXXXXXX is a constant indicating the type of the temporary
file, for example, SPLT001 or CKSROUT.

Only when an 8 character TSO user ID is used, any 8 character long 3rd level dataset name
qualifier for dynamically generated or dynamically allocated datasets will change for these
cases (DDNAMEs are unaffected):
1. Data disguise with a File-AID XREF dataset: The 3rd qualifier changes from
S001B001 to S001001.
2. Extract chase key processing: The SORTOUT dataset 3rd qualifier changes from
CKSRTOUT to CKSROUT. For chase key files to be sorted, the 3rd qualifier changes
from R000001P to R00001P.
3. Loading XML columns to a Db2 table: The work dataset 3rd qualifier changes from
XMLFR001 to XMFR001.

Figure 24. Temporary File Defaults Screen

File-AID/RDX ------------ Temporary File Defaults

---------------------------
COMMAND ===> SITE Profile: RDXMENU
More: +
------------------------ Temporary File Defaults ------------------------------
Temporary file allocations:
UNIT ===> SYSDA 
Storage Class ===> 
Management Class ===> 

File Prefix ===> RDX 
File Suffix ===> 

Sort Work File Allocation: 
Space Units ===> CYL (BLK, TRK, or CYL) 
Primary Quantity ===> 6 
Secondary Quantity ===> 1 
Number of Sort Work files ===> 3 (3 - 6) 
Use ICETOOL for Batch Sorts ===> N (Y = Yes; N = No)

Temp Work File Allocation: 
Space Units ===> CYL (BLK, TRK, or CYL) 
Primary Quantity ===> 1 
Secondary Quantity ===> 1 

Chase Key File Allocation: 
Space Units ===> CYL (BLK, TRK, or CYL) 
Primary Quantity ===> 1 
Secondary Quantity ===> 1 

1. Only if 8 character TSO user ID has been implemented at your site with z/OS 2.3 or later.
Profiles and Global Defaults 81

Temporary file allocations Area

UNIT
Specify the default unit for the temporary files. File-AID/RDX will verify that the unit specified is
a valid generic unit (for example, SYSDA) on the LPAR where you are currently logged on.

Storage Class
Specify the default storage class for the temporary files.

Management Class
Specify the default management class for the temporary files.

File Prefix
Specify the default file prefix for all temporary files for this profile. This is the prefix used for files
that must be allocated for batch functions. File-AID/RDX will prefix temporary files with
userid.prefix. To prefix a file without a userid, place one double quote as the first character of the
pattern. For example, “RDX will prefix a temporary file with RDX. only. If the resulting file name
exceeds 44 characters, the specified prefix will be truncated to fit the maximum name length.

Entering the string &USERID will substitute the current userid at the time a temporary file is
allocated. For example, “RDX.&USERID will generate temporary files beginning with RDX,
followed by the current userid, followed by the rest of the generated dataset name.

File Suffix
Specify a file suffix for all temporary files for this profile, if one is desired. This is the suffix used
for files that must be allocated for batch functions. File-AID/RDX will append this suffix to the
names of generated file names for batch jobs.

The combined length of the file prefix and suffix cannot exceed 19
characters.

Sort Work, Temp Work and Chase Key File Allocation Areas

You can specify different default file allocation values for each of the Sort Work, Temp Work and
Chase Key files.

Number of Sort Work files

Specify the default number of sort work files (3 or 6) to be used with this profile.

Use ICETOOL for Batch Sorts

Specify whether Load JCL should be generated to use the ICETOOL utility for sorting. If set to
Yes, generate JCL for ICETOOL. If set to No, generate JCL for SORT.
82 File-AID/RDX Reference

Space Units
Specify whether space for the new file will be allocated in blocks (BLK), tracks (TRK), or cylinders
(CYL).

Primary QTY
Specify the initial number of space units that will be allocated for the new file.

Secondary QTY
Specify the number of space units that will be allocated for each secondary extent.

If your extract exceeds the size of these temporary file allocations (B37 abend) change
the allocation parameters here and repeat the extract (see Extract).
File-AID/RDX will dynamically reallocate temporary work files, key tree and chase key
files only when running extracts using 64 bit memory (above the bar) processing
support. See also parameter EXTENDED_ADDRESSING_AREA_IN_GIGABYTES in the File-
AID Advanced Configuration Guide.

Option G—Global User Defaults

The Global User Defaults screen shown in Figure 25 is displayed when you select Option G from the
File-AID/RDX Primary Option Menu. Use this screen to specify global parameters for the extract, load
and delete reference lists, whether or not to delete the File-AID/RDX control card PDSEs at the end of
extract, load, delete, or disguise jobs, default job statement information, a default Dynamic Privacy
Rules Repository, and view the current File-AID/RDX version number.

The values you specify here are applied only when your current profile’s corresponding values are
blank.

Figure 25. Global User Defaults Screen

File-AID/RDX -------------- Global User Defaults ----------------------------

Command ===> FA/RDX Version: 17.2.0 

Reference List controls:
Extract reference list entries ===> 50 Maximum Number of entries
Load reference list entries ===> 50 Maximum Number of entries

Increment job name ===> N (Y = Yes; N = No)
Delete in-stream data datasets at EOJ ===> N (Y = Yes; N = No)

DPR: Repository Name ===>

Job Statement Information:
===> //
===> //
===> //
===> //
===> //

NOTE: If the Job Statement Information is not specified via the RDX Profile,
then the Job Statement Information specified here will be used. If no
information is specified here, then the latest TSO Job Statement 
Information will be used. 


FA/RDX Version
Displays the current version of File-AID/RDX you are using.
Profiles and Global Defaults 83

Reference List controls

Extract reference list entries

Values allowed are 10 to 250, installation default is 50. Specify the maximum number of extract
requests to be stored in the Extract reference list. When the reference list exceeds the maximum
number of entries the oldest unlocked entry will roll off the list. See also Extract Reference List on
page 213.

Load reference list entries

Values allowed are 10 to 250, installation default is 50. Specify the maximum number of load or
delete requests to be stored in the Load/Delete reference list. When the reference list exceeds the
maximum number of entries the oldest unlocked entry will roll off the list. See also Load
Reference List on page 412 and Delete Reference List on page 566.

Job Statement Information

Increment job name

Specify whether you want the automatic job name incrementation or not. If Yes, File-AID/RDX
will increment the last character of the job name after each submission for the current TSO
session.

Delete in-stream data datasets at EOJ

The last steps, CLEANCTL and CLEANEXT, in the extract, load, delete and disguise jobs delete the
File-AID/RDX control card PDSEs and parameter files (FBCNTL, VBCNTL, EXTPARMS). Keeping
the datasets until all steps run successfully allows for the restarting of the JCL at any step. See
also Control Card Cleanup on page 360, page 505 and page 581, as well as CLEANCTL—File
Cleanup (IEFBR14) - Optionalon page 509, page 523, page 535, page 582, and page 587.

YES

Deletes the File-AID/RDX control card PDSEs and parameter files at the end of an extract,
load, delete or disguise job.

NO

Does not delete the File-AID/RDX control card PDSEs and parameter files at the end of an
extract, load, delete or disguise job (Steps CLEANCTL and CLEANEXT are commented out).

DPR: Repository Name

Specify the name of the Repository to be used as the default repository with Disguise Extract File
option 2 (see Disguise Extract File on page 71). The repository stores the Dynamic Privacy Rules
Projects created with the File-AID Data Privacy component of the Topaz Workbench.

If your current profile does not include the Repository Name, File-AID/RDX will use the name
you specify here. The Repository Name must be set properly, and will be used in combination
with Dynamic Privacy Rules Project Name (see also DPR: Project Name on page 73) throughout
the rest of the product.

File-AID/Data Solutions and File-AID Data Privacy are required.

84 File-AID/RDX Reference

Specify the full repository name (up to 128 characters). Leave blank or enter an asterisk (*) by
itself for a list of all available repositories. Then select the desired repository from the list (see
Privacy Repository List on page 74).

Job Statements
Specify the default job card information for batch jobs.

If your current profile does not include job card information, File-AID/RDX will use the default
job card information you specify here. If your current profile includes job card information, the
profile’s job card will be used for all extract, load, delete and disguise JCL (see also Job Statement
Information on page 56).

When disguising an extract with File-AID Data Privacy defined Dynamic

Privacy Rules (DPR), specify a region size large enough to run Java
(REGION=0M is suggested, 200M is the minimum) in your jobcard. See also
Disguise Extract File on page 71, option 2, DPR.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

CANCEL (CAN)
Cancels your updates since the last save and returns to the File-AID/RDX Primary Option Menu.

END
Saves the current updates and returns to the File-AID/RDX Primary Option Menu.
 85

Relationship Facilitator
Overview
This chapter describes Option 1, Relationship Facilitator. The Relationship Facilitator enables you to
view and manipulate the relationship file to:

• view all relationships defined to File-AID/RDX.

• load Db2-defined referential integrity (RI) relationships, including non-enforced RI, from the
Db2 catalog table, SYSIBM.SYSRELS, into the relationship file.
• refresh the relationship file when its RI information does not match the Db2 catalog.
• delete RI and user-defined application relationship information from the relationship file.
• add application relationship information to the relationship file.
• define data driven (“conditional”) application relationships.
• modify existing application relationship information.
• allocate a new relationship file.
• refresh RI information using batch
• print formatted contents of a relationship file.

Relationship File Compatibility Notes

1. Relationship files can be shared between File-AID for DB2 and File-AID/RDX.
2. Db2 long name support requires File-AID/RDX Release 4.3, or higher, or File-AID for DB2 Release
4.8.1, or higher. Once a Db2 long name has been added to a Version 2 relationship file, File-
AID/RDX updates it to a Version 3 relationship file. Version 3 relationship files are not downward
compatible with earlier product releases.

Relationship File Contents

The relationship file (relationship repository) is a VSAM-KSDS file in which File-AID/RDX stores the
following types of information:

Db2 Referential Integrity (RI) Relationships

This relationship is one in which the dependent table rows contain foreign keys, the values of which
are the primary index of the parent table. The rules that define RI relationships are enforced by Db2.

Use Option 5, LOAD RI from the DB2 Relationship Facilitator menu (Option 1, RELATIONSHIPS) for
an online load or update of the RI information in the Relationship File. For more information, see
DB2 RI Update Online Options on page 112.

To load or refresh RI information from the Db2 catalog with a batch job, use Option L, Batch RI Load,
from the DB2 Relationship Facilitator menu (Option 1, RELATIONSHIPS) For more information, see
Batch RI Load on page 182.

Application Relationships (AR)

This relationship is one in which values from dependent MVS file fields, Output Key file layout fields,
IMS database root segments, or Db2 table or view columns match the values in corresponding parent
MVS file fields or Db2 table or view columns. The rules that define application relationships are
enforced by user applications, not by Db2 or other databases.
86 File-AID/RDX Reference

To define an application relationship File-AID/RDX needs to know the parent and dependent object
names along with the names of the related column(s) or field(s). File-AID/RDX can assist you with the
application relationship definition through its SUGGEST feature: File-AID/RDX will suggest
relationships when column or field name, type, and length in the parent and dependent objects are
identical.

When defining an application relationship for an MVS object, you must always identify the specific
record layout or XREF information that defines the related field within the file.

A relationship can also be established from a Db2 or MVS parent to an Output Key file which
contains a record layout, an IMS segment or both. The layout file or IMS segment is considered the
dependent object. You define relationships for each field that is to be included in the extract Output
Key file. The layout will determine the location and format of each field within the Output Key file.
When the extract request is executed the Output Key file will be populated based upon the key values
for the KEY relationship in the related extract.

The Output Key File can then be used by File-AID/RDX as an input (external) keys file against a
driving object in another extract (see also Input Key File Specification on page 295) or as input into
another process of your choosing. When the relationship is to an IMS segment, use the Output Key
File with File-AID for IMS to extract IMS data.

In addition, you can define relationships in File-AID for DB2 and store them in the same relationship
file you use with File-AID/RDX. You can view and modify these relationships using File-AID/RDX
Option 1. File-AID for DB2, however, does not support application relationships involving KEY (IMS)
or MVS objects in its Related Edit/Browse function.

Conditional (“Data Driven”) Application Relationships (AR-C)

File-AID/RDX also allows you to define one or more conditions on the parent object within an
application relationship. Use the COND primary command (see COND on page 151) to specify the
conditions to test for. At extract execution time, the condition on the conditional object will be
evaluated and the defined relationship will be navigated only when the condition is true.

A very simple example of this concept is a parent column that contains a code that if it has a value of
"S" then a column named ID_COL has a social security number which is related to a table keyed by
SSN, but if the code is "D" then the ID_COL has a driver's license number which is related to a
different table.

For the sample scenario in Figure 26 on page 87, you would create four conditional application
relationships with the respective conditional criteria defined on the parent object ACCOUNT.
Relationship Facilitator 87

Figure 26. Sample Scenario of Conditional AR

Considerations for MVS Objects

File-AID/RDX supports defining application relationships for MVS objects as either parent and/or
dependent objects. Before defining a relationship keep in mind:

• file type must be SEQ, including GDG and GDS, KSDS, ESDS, or IAM 1
• MVS object must be defined with a COBOL or PL/I record layout; COBOL and unaligned PL/I
record layouts are compiled as interpreted by File-AID/RDX.
• only one record layout per object in a relationship file (layout usage S); if more than one is
required, use XREF (layout usage X)
• only one XREF file per object in a relationship file
• the LRCL must be less than or equal to 32,756 in order for the data records to be extracted
• File-AID/RDX does not support undefined record format (RECFM=U).

GDG Considerations

File-AID/RDX supports relative GDG numbers in addition to the G0000V00 (i.e. .G0001V00) hard
coded number for physical sequential files. File-AID/RDX allows you to define application
relationships (AR) to or from a GDG or a GDS. Relationships are allowed between generations of the
same GDG. If, for example, your current quarterly report is to extract from the current and the two
previous months, you define these relationships:

1. GDG.PAYMENTS.QUARTER(0) to GDG.PAYMENTS.MONTH(0)
2. GDG.PAYMENTS.QUARTER(0) to GDG.PAYMENTS.MONTH(-1)
3. GDG.PAYMENTS.QUARTER(0) to GDG.PAYMENTS.MONTH(-2)

When specifying the GDG base in a relationship, for example GDG.PAYMENTS.MONTH, File-
AID/RDX extracts from all existing generations.

1. For File-AID/RDX to continue support of IAM (Innovation Access Method) file types, apply the appropriate IAM version
fix(es): IAM Version 9.1 fixes P910005 and P910167, IAM Version 9.2 fix P920095, and IAM Version 9.3 fix P930003.
88 File-AID/RDX Reference

Use of Db2 Views

File-AID/RDX supports defining application relationships for views in the suboptions of the
Relationships Option function (Primary Menu Option 1). Views are treated just like tables and can be
entered in any Table field. For example, you can define an application relationship for a view to any
other dependent object (MVS, DB2 or KEY).

When you specify a view in either Relationships suboption, File-AID/RDX will display all
relationships defined for the view. If no relationships are defined for the view, File-AID/RDX will not
display any relationships. To see the relationships for the view’s base table you must enter the base
table name.

DB2 Relationship Facilitator

The DB2 Relationship Facilitator screen shown in Figure 27 is displayed when you select Option 1,
Relationships, from the File-AID/RDX Primary Option Menu and your profile specifies Db2 as the
default driving object type (see also Default driving object type on page 62). The DB2 Relationship
Facilitator screen also appears when you enter the DB2 command in the MVS Relationship Facilitator
screen.

Figure 27. DB2 Relationship Facilitator

File-AID/RDX -------- DB2 Relationship Facilitator-------------------------

Option ===> Scroll ===> CSR 
SITE Profile: RDXMENU 
Primary commands: menu-option, MVS Relationship Facilitator 

1 BROWSE ALL - Browse all existing Relationships 
2 EDIT AR - Edit existing Application Relationships 
3 ADD AR - Add new Application Relationships 
4 LIST RDX - List DB2 objects from RDX Relationship File 
5 LOAD RI - Load RI Relationships defined to DB2 
6 LIST DB2 - List DB2 objects from DB2 Catalog 
A ALLOCATE - Allocate Relationship File 
L BATCH RI LOAD - Batch Job to Load RI Relationships
P PRINT - Print the Relationship File 

Specify a Table Name or pattern: 
SSID ===> * (* or pattern for selection list)
Location ===> * (* or pattern for selection list)
Creator ===> * (* or pattern for selection list)
Table Name ===> * (* or pattern for selection list)

Specify Relationship Information: 
File name ===> FRSAMP.RELATION 

Use this screen to specify the name of the table or view for which you want to maintain relationships
and the File-AID/RDX relationship file that contains the information about those relationships. Then
enter one of the menu options to specify the action you want to perform. When pressing Enter
without selecting an option, File-AID/RDX selects option 4, List RDX, and lists all matching entries
found in the relationship file. File-AID/RDX issues a message when the relationship file does not
contain any entries for the specified Db2 object.

Menu Options
The following File-AID/RDX-specific menu options are valid on this screen:

1 - Browse All
Browse Relationship File. Select Option 1 to search the relationship file for previously stored
relationships that match the specified object.
Relationship Facilitator 89

Option 1, Browse All, enables you to view a list of all objects defined to your relationship file that
are “related” to the object (MVS file or Db2 table or view) you specify. You can then select a single
relationship about which you want to view detailed information from the list. See Relationship
Detail on page 101 for more detail.

When browsing existing relationships you can also modify, delete, and add new application
relationships.

2 - Edit AR
Edit Application Relationships. Select Option 2 to search the relationship file for previously
stored application relationships.

Option 2, Edit AR, enables you to view a list of all objects defined to your relationship file that
are “related” to the object (MVS file or Db2 table or view) you specify. From the list, you can then
select a single relationship about which you want to view detailed information. See Application
Relationship Detail on page 121 for more detail.

3 - Add AR
Add Application Relationship. Select Option 3 to add an application relationship. Displays the
Add Relationships — Specify Object Types so you can specify the parent and dependent object
types for the new relationship. See Add Relationships — Specify Object Types on page 123.

4 - List RDX
(Default) List all Db2 objects from the Relationship File. Select Option 4 to search the
relationship file for matching Db2 objects.

Option 4, List RDX, enables you to view a list of all Db2 objects defined to your relationship file
that “match” the object specification. See DB2 Object List on page 91.

5 - Load RI
Select Option 5 to maintain the relationship file for Db2 RI information. Option 5 enables you to
load or refresh Db2-defined RI information in your relationship file using information from the
Db2 catalog. In addition, you can delete RI relationship data from the relationship file. See DB2
RI Update Online Options on page 112.

6 - List DB2
Search the Db2 Catalog and Relationship File. Select Option 6 to find objects in the Db2 catalog
that match your specified pattern.

Option 6 enables you to view a list of all objects in the Db2 catalog that match the specified
pattern. It also checks the relationship file and informs you whether it includes an entry for the
object. See DB2 Object List on page 91.

A - Allocate
Displays the Allocate Relationship File panel where you can allocate a new relationship file. The
File-AID/RDX relationship file is the repository that stores the RI and AR relationship definitions
so you can extract related data. See Allocate Relationship File on page 180.
90 File-AID/RDX Reference

L- Batch RI Load
Displays the Batch RI Load screen where you can submit batch jobs to update a relationship file
with the current RI information for one or more Db2 subsystems. See Batch RI Load on page 182.

P - Print
Print Relationships. Displays the Formatted Relationship Report Screen screen where you can
submit a batch job to print a formatted report that contains information from the File-AID/RDX
relationship file that you specify. You can also save this report to an existing or new file. See Print
Relationship File on page 186.

Specify a Table Name or Pattern Area

Use the fields in this area to specify the Db2 object for which you want to retrieve relationship
information. When specifying patterns in the fields, File-AID/RDX presents selection lists. These
fields don’t apply for the P, Print Relationship file, menu option.

SSID
Specify the Db2 subsystem ID of the Db2 subsystem on which the table resides for which you
want to view relationship information.

Location
Specify the Db2 remote location ID of the Db2 subsystem on which the table resides for which
you want to view relationship information. Leave blank if your site does not use DDF.

Special Notes for SSID and Location fields

1. When you enter a pattern and select option 1, 2, or 4 at the same time
File-AID/RDX will search the relationship file for matching entries.
2. For option 3, 5, or 6 you must select the one subsystem ID in the SSID
field that is valid for the remote location ID you specify/select in the
Location field.

Creator
Specify the authorization ID of the owner of the table for which you want to view relationship
information. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).
Relationship Facilitator 91

Table Name
Specify the name of the Db2 object (table or view) for which you want to see relationship
information. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).

Notes for Creator and Table fields

Which list File-AID/RDX will display depends on the option you select:

1
Table List in Relationship File

2
Table List in Relationship File

3
Table List - SYSIBM.SYSTABLES

4
DB2 Object List

5
Table List - SYSIBM.SYSTABLES

6
DB2 Object List

If you specify a pattern and press the Enter key without selecting an option,
the DB2 Object List screen shown in Figure 28 on page 92 is displayed. See
DB2 Object List on page 91 for more information. In the other table lists,
select the desired Creator.Table combination with the S line command.

Specify Relationship File Area

File Name
Specify the name of the File-AID/RDX relationship file that contains the relationship information
you want to display or maintain. Refer to Relationship File on page 37 for more information
about the relationship file.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

MVS
Switch to the MVS Relationship Facilitator panel to specify an MVS driving object for your
Relationship task.

DB2 Object List

The DB2 Object List screen shown in Figure 28 is displayed when you select Option 4, List RDX, or
Option 6, List DB2, and specify a pattern in the Creator or Table Name field on the DB2 Relationship
Facilitator screen, Figure 27 on page 88.
92 File-AID/RDX Reference

Figure 28. DB2 Object List

File-AID/RDX --------------- DB2 Object List -------------- Row 1 to 6 of 6

Command ===> SCROLL ===> CSR

Line Commands: A = Add Application Relationship B = Browse Relationship 
E = Edit Application Relationship L = Load RI Relationships 

Relation
CMD Object Name Type SSID 
--- -------------------------------------- ------ ----
_ DSNLOCAN.TSOID01.CONTACT_TABLE RI DSN
_ DSNLOCAN.TSOID01.CUSTOMER_TABLE AR/RI DSN
_ DSNLOCAN.TSOID01.ORDER_LINE_TABLE RI DSN
_ DSNLOCAN.TSOID01.ORDER_TABLE AR/RI DSN
_ DSNLOCAN.TSOID01.PART_TABLE RI DSN
_ DSNLOCAN.TSOID01.SUPPLIER_TABLE CATLG DSN
******************************* Bottom of data ********************************

This screen displays a list of objects retrieved from either the Db2 catalog (Option 6) or the
relationship file (Option 4). It also displays whether an object is already involved in relationships
defined in the relationship file (AR or RI) or not (CATLG). If there are more objects that match the
pattern you specified on the previous screen than will fit on the screen, you can scroll the list using
standard scrolling commands. Enter one of the available line commands for an object.

CMD
Enter a line command in this column next to the object for which you want to maintain
relationships. The available line commands are shown in the top part of this screen.

Object Name
Displays the names of either Db2 or MVS objects that match the value specified in the Creator
and Table name fields on the preceding screen.

Relation Type
Displays the Relationship Type of the displayed objects.

AR One or more Application Relationships exist for this object in the relationship file.
RI One or more Db2 RI relationships exist for this object in the relationship file.
AR/RI Both AR and RI exist for this object in the relationship file.
catalg There are no relationships defined for this object in the relationship file.

SSID
Displays the ID of the Db2 subsystem from which the relationship had been defined or loaded.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
Relationship Facilitator 93

A
Add Application Relationship. Enter the A line command to add an application relationship.
Displays the Add Relationships — Specify Object Types so you can specify the parent and
dependent object types for the new relationship. See Add Relationships — Specify Object Types
on page 123.

B
Browse Relationship File. Enter the B line command to search the relationship file for previously
stored relationships.

B enables you to view a list of all objects defined to your relationship file that are “related” to the
object (MVS file or Db2 table or view) you specify. You can then select a single relationship about
which you want to view detailed information from the list. See Relationship Detail on page 101
for more detail.

The message "Selection not viewable" appears if no relationships exist in the relationship file for
the object (Relation Type CATLG).

E
Edit Application Relationships. Enter the E line command to search the relationship file for
previously stored application relationships for the selected object.

E displays a list of all application relationships defined to your relationship file that are “related”
to the selected object (MVS file or Db2 table or view). You can then maintain (modify, add,
delete) application relationships or display more detail information about any of the application
relationships from the list.

The message "Selection not viewable" appears if no relationships exist in the relationship file for
the object (Relation Type CATLG).

The message "Can’t edit RI relationship" appears if only RI relationships exist in the relationship
file for the object (Relation Type RI).

L
Load RI. Enter the L line command to maintain the relationship file for Db2 RI information for
the selected object. L enables you to load or refresh Db2-defined RI information in your
relationship file using information from the Db2 catalog. In addition, you can delete RI
relationship data from the relationship file.

Table List in Relationship File

The Table List in Relationship File screen shown in Figure 29 is displayed when you select Option 1,
Browse All, or Option 2, Edit AR, and specify a pattern in the Creator or Table Name field on the DB2
Relationship Facilitator screen, Figure 27 on page 88.
94 File-AID/RDX Reference

Figure 29. Table List in Relationship File

File-AID/RDX -------- DB2 Relationship Facilitator ------------------------- 

O Table List in Relationship File ===> CSR 
Row 1 to 6 of 6 e: RDXMENU
P Command ===> SCROLL ===> CSR 

Enter 'S' to select table name 
Relation 
CMD Object Name Type SSID 
--- -------------------------------------- ------ ---- 
DSNLOCAT.FRSAMP.CONTACT_TABLE RI DSN es 
DSNLOCAT.FRSAMP.CUSTOMER_TABLE AR/RI DSN 
DSNLOCAT.FRSAMP.ORDER_LINE_TABLE RI DSN 
DSNLOCAT.FRSAMP.ORDER_TABLE AR/RI DSN 
S DSNLOCAT.FRSAMP.PART_TABLE AR/RI DSN 
DSNLOCAT.FRSAMP.SUPPLIER_TABLE AR/RI DSN ction list)
********************** Bottom of data *********************** ction list)
ction list)
ction list)

S 




This screen displays a list of objects involved in relationships defined in the relationship file. If there
are more relationships that match the pattern you specified on the previous screen than will fit on
the Table List in Relationship File window, you can scroll the list using standard scrolling commands.
Use this window to select the object for which File-AID/RDX will search the relationship file. The
resulting list of relationships associated with the selected object is displayed on the Relationship
Detail screen.

CMD
Enter an S line command in this column next to the object for which you want to see a list of
relationships. The S line command is the only valid line command for this screen.

Object Name
Displays the names of Db2 objects that match the value specified in the DB2 Relationship
Facilitator screen.

Relation Type
Displays the Relationship Type of the displayed objects.

AR One or more Application Relationships exist for this object in the relationship file.
RI One or more Db2 RI relationships exist for this object in the relationship file.
AR/RI Both AR and RI exist for this object in the relationship file.

SSID
Displays the ID of the Db2 subsystem from which the relationship had been defined or loaded.

Line Commands
The following File-AID/RDX-specific line command is valid on this screen:
Relationship Facilitator 95

S (Select)
Use the S line command to select an object for which you want to display relationship
information. Relationship information about the object you select is displayed on the
Relationship Detail screen as shown in Figure 34 on page 102.

Table List - SYSIBM.SYSTABLES

The Table List - SYSIBM.SYSTABLES screen shown in Figure 30 is displayed when you select Option 3,
Add AR, or Option 5, Load RI, and specify a pattern in the Creator or Table Name field on the DB2
Relationship Facilitator screen, Figure 27 on page 88.

Figure 30. Table List - SYSIBM.SYSTABLES

File-AID/RDX -------- DB2 Relationship Facilitator ------------------------- 

O Table List - SYSIBM.SYSTABLES ===> CSR 
Row 1 to 12 of 12 e: RDXMENU 
P Command ===> SCROLL ===> CSR 

Enter 'S' to select table name 
Relation 
CMD Object Name Type SSID 
--- -------------------------------------- ------ ---- 
DSNLOCAT.FRSAMP.CONTACT_TABLE RI DSN es 
DSNLOCAT.FRSAMP.CONTACT_VIEW CATLG DSN 
DSNLOCAT.FRSAMP.CUSTOMER_TABLE AR/RI DSN 
DSNLOCAT.FRSAMP.CUSTOMER_VIEW CATLG DSN 
S DSNLOCAT.FRSAMP.ORDER_LINE_TABLE RI DSN 
DSNLOCAT.FRSAMP.ORDER_LINE_VIEW Catlg DSN ction list) 
DSNLOCAT.FRSAMP.ORDER_TABLE AR/RI DSN ction list) 
DSNLOCAT.FRSAMP.ORDER_VIEW CATLG DSN ction list) 
DSNLOCAT.FRSAMP.PART_TABLE AR/RI DSN ction list) 
DSNLOCAT.FRSAMP.PART_VIEW CATLG DSN 
S DSNLOCAT.FRSAMP.SUPPLIER_TABLE AR/RI DSN 
DSNLOCAT.FRSAMP.SUPPLIER_view CATLG DSN 
********************** Bottom of data *********************** 



This screen displays a list of Db2 objects defined in the Db2 catalog that match the pattern. If there
are more objects that match the pattern you specified on the previous screen than will fit on the
Table List - SYSIBM.SYSTABLES window, you can scroll the list using standard scrolling commands.
Use this window to select the object for which File-AID/RDX will add an application relationship or
load the RI information to the relationship file. The resulting list of relationships associated with the
selected object is displayed on the Relationship Detail screen.

CMD
Enter an S line command in this column next to the object for which you want to see a list of
relationships or add a relationship.The S line command is the only valid line command for this
screen.

Object Name
Displays the names of Db2 objects that match the value specified in the DB2 Relationship
Facilitator screen.
96 File-AID/RDX Reference

Relation Type
Displays the Relationship Type of the displayed objects.

AR One or more Application Relationships exist for this object in the relationship file.
RI One or more Db2 RI relationships exist for this object in the relationship file.
AR/RI Both AR and RI exist for this object in the relationship file.
CATLG There are no relationships defined for this object in the relationship file. This status
only applies when selecting option 3, Add AR.

SSID
Displays the ID of the Db2 subsystem from which the relationship had been defined or loaded.

Line Commands
The following File-AID/RDX-specific line command is valid on this screen:

S (Select)
Use the S line command to select an object for which you want to display relationship
information or add a relationship. When loading RI for the selected object the DB2 RI Update
Online Options Screen as shown in Figure 40 on page 113 is displayed. When adding an AR for
the selected object, the Object Type Selection Screen for Adding Application Relationship screen
as shown in Figure 47 on page 124 is displayed.

MVS Relationship Facilitator

The MVS Relationship Facilitator screen shown in Figure 31 is displayed when you select Option 1,
Relationships, from the File-AID/RDX Primary Option Menu and your profile specifies MVS as the
default driving object type (see also Default driving object type on page 62). The MVS Relationship
Facilitator screen also appears when you enter the MVS command in the DB2 Relationship Facilitator
screen.

Figure 31. MVS Relationship Facilitator

File-AID/RDX -------- MVS Relationship Facilitator

-------------------------
Option ===> TSOID01 Profile: A1 

Primary commands: menu-option, DB2 Relationship Facilitator 

1 BROWSE ALL - Browse all existing Relationships 
2 EDIT AR - Edit existing Application Relationships 
3 ADD AR - Add new Application Relationships 
4 LIST RDX - List MVS objects from RDX Relationship File 
A ALLOCATE - Allocate Relationship File 
P PRINT - Print the Relationship File 


Specify a File Name or Pattern: 
File name ===> 'TSOID01.FRSAMP.*' 
Record layout usage ===> S (S = Single; X = XREF;) 
Record layout file ===> 
Member name ===> (Blank or pattern for member list) 
XREF file name ===> 
Member name ===> 
I/O exit name ===> 

Specify Relationship Information: 
File name ===> FRSAMP.RELATION 
Relationship Facilitator 97

Use this screen to specify the name of the MVS file for which you want to maintain relationships and
the File-AID/RDX relationship file that contains the information about those relationships. Then
enter one of the menu options to specify the action you want to perform. When pressing Enter
without selecting an option, File-AID/RDX selects option 4, List RDX, and lists all matching entries
found in the relationship file. File-AID/RDX issues a message when the relationship file does not
contain any entries for the specified MVS object.

Menu Options
The following File-AID/RDX-specific menu options are valid on this screen:

1 - Browse All
Browse Relationship File. Select Option 1 to search the relationship file for previously stored
relationships that match the specified object.

Option 1, Browse All, enables you to view a list of all objects defined to your relationship file that
are “related” to the object (MVS file or Db2 table or view) you specify. You can then select a single
relationship about which you want to view detailed information from the list. See Relationship
Detail on page 101 for more detail.

When browsing existing relationships you can also modify, delete, and add new application
relationships.

2 - Edit AR
Edit Application Relationships. Select Option 2 to search the relationship file for previously
stored application relationships.

Option 2, Edit AR, enables you to view a list of all objects defined to your relationship file that
are “related” to the object (MVS file or Db2 table or view) you specify. From the list, you can then
select a single relationship about which you want to view detailed information. See Application
Relationship Detail on page 121 for more detail.

3 - Add AR
Add Application Relationship. Select Option 3 to add an application relationship. Displays the
Add Relationships — Specify Object Types so you can specify the parent and dependent object
types for the new relationship. See Add Relationships — Specify Object Types on page 123.

4 - List RDX
(Default) List all MVS objects from Relationship File. Select Option 4 to search the relationship
file for matching objects.

Option 4, List RDX, enables you to view a list of all objects defined to your relationship file that
“match” the object specification. See MVS Object List on page 99.

A - Allocate
Displays the Allocate Relationship File panel where you can allocate a new relationship file. The
File-AID/RDX relationship file is the repository that stores the RI and AR relationship definition
so you can extract related data.
98 File-AID/RDX Reference

P - Print
Print Relationships. Enables you to print a formatted report that contains information from the
File-AID/RDX relationship file that you specify. You can also save this report to an existing or
new file.

Specify a File Name or Pattern Area

Use the fields in this area to specify the MVS file for which you want to retrieve or add relationship
information from the relationship file. When specifying patterns in the fields, File-AID/RDX presents
selection lists.

File Name
Specify the MVS file name of the object for which you want to view relationship information. To
view a list of files, specify a pattern. Valid pattern character is * (see Pattern Characters on page
27).

If you leave this field blank and you specify a pattern in the Record layout file or XREF file name
fields together with menu options 1 or 2, File-AID/RDX searches the relationship file for any
objects with a matching layout or XREF definition.

Record layout usage

Indicate whether a single record layout (usage “S”), or an XREF (usage “X”) is to be used to define
the selection criteria.
You must also supply a Record Layout file and either a layout member (Usage=S) or an XREF file
and member (Usage=X).

Record layout file

Specify the record layout file for the MVS object for which you want to view relationship
information. To view a list of layout files, specify a pattern. Valid pattern character is * (see
Pattern Characters on page 27).

Member name
Specify the member of the record layout file that contains the layout information for the MVS
object. Leave blank or use a pattern to select a member from a list.

XREF file name

Only needed if layout usage is X. Specify the XREF file name for the MVS object for which you
want to view relationship information. To view a list of XREF files, specify a pattern. Valid
pattern character is * (see Pattern Characters on page 27).

Member name
Specify the member of the XREF file that contains the layout information for the MVS object.
Leave blank or use a pattern to select a member from a list.
Relationship Facilitator 99

I/O Exit Name

Specify the I/O Exit Name for the MVS object for which you want to view relationship
information.

You only need to fill in this field when you want File-AID/RDX to use an I/O exit routine when
accessing the above MVS file. Not needed to search the relationship file.

Specify Relationship File Area

Relationship File Name

Specify the name of the File-AID/RDX relationship file that contains the relationship information
you want to display. Refer to Relationship File on page 37 for more information about the
relationship file.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

DB2
Switch to the DB2 Relationship Facilitator panel to specify a Db2 driving object for your
Relationship task.

MVS Object List

The MVS Object List screen shown in Figure 32 is displayed when you select Option 4 and specify a
pattern in the File Name field on the MVS Relationship Facilitator screen, Figure 31 on page 96.

Figure 32. MVS Object List

File-AID/RDX --------------- MVS Object List -------------- Row 1 to 6 of 6 

Command ===> SCROLL===> CSR 

Line Commands: A = Add Application Relationships B = Browse Relationship 
E = Edit Application Relationship 

CMD Object Name 
--- ------------------------------------------------------ 
TSOID01.FRSAMP.CONTACTT 
TSOID01.FRSAMP.CUSTOMER 
TSOID01.FRSAMP.ORDERLIN 
TSOID01.FRSAMP.ORDERTAB 
TSOID01.FRSAMP.PARTTABL 
TSOID01.FRSAMP.SUPPLIER 
******************************* Bottom of data ********************************

This screen displays a list of objects retrieved from the relationship file (Option 4, List RDX). If there
are more objects that match the pattern you specified on the previous screen than will fit on the
screen, you can scroll the list using standard scrolling commands. Enter one of the available line
commands for an object.

CMD
Enter a line command in this column next to the object for which you want to maintain
relationships. The available line commands are shown in the top part of this screen.
100 File-AID/RDX Reference

Object Name
Displays the names of MVS objects that match the pattern specified in the File Name field on the
preceding screen.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

A
Add Application Relationship. Enter the A line command to add an application relationship.
Displays the Add Relationships — Specify Object Types so you can specify the parent and
dependent object types for the new relationship. See Add Relationships — Specify Object Types
on page 123.

B
Browse Relationship File. Enter the B line command to search the relationship file for previously
stored relationships.

B enables you to view a list of all objects defined to your relationship file that are “related” to the
object (MVS file or Db2 table or view) you specify. You can then select a single relationship about
which you want to view detailed information from the list. See Relationship Detail on page 101
for more detail.

The message "Selection not viewable" appears if no relationships exist in the relationship file for
the object (Relation Type CATLG).

E
Edit Application Relationships. Enter the E line command to search the relationship file for
previously stored application relationships for the selected object.

E displays a list of all application relationships defined to your relationship file that are “related”
to the selected object (MVS file or Db2 table or view). You can then maintain (modify, add,
delete) application relationships or display more detail information about any of the application
relationships from the list.

The message "Selection not viewable" appears if no relationships exist in the relationship file for
the object (Relation Type CATLG).

The message "Can’t edit RI relationship" appears if only RI relationships exist in the relationship
file for the object (Relation Type RI).

Object List in Relationship File

The Object List in Relationship File window shown in Figure 33 is displayed when you specify a
pattern in the MVS file name field and selected Options 1, Browse All, or 2, Edit AR, on the MVS
Relationship Facilitator screen, Figure 31 on page 96.
Relationship Facilitator 101

Figure 33. Object List in Relationship File

File-AID/RDX -------- MVS Relationship Facilitator -------------------------

O Object List in Relationship File e: SAMPMENU
Row 1 to 6 of 6 
P Command ===> SCROLL ===> CSR 

Enter 'S' to select table name 

CMD Object Name 
--- ------------------------------------------------------ 
_ TSOID01.FRSAMP.CONTACTT 
_ TSOID01.FRSAMP.CUSTOMER 
_ TSOID01.FRSAMP.ORDERLIN 
S _ TSOID01.FRSAMP.ORDERTAB 
_ TSOID01.FRSAMP.PARTTABL 
_ TSOID01.FRSAMP.SUPPLIER 
********************** Bottom of data *********************** 
list) 




S 


This screen displays a list of objects involved in relationships defined in the relationship file. If there
are more relationships that match the pattern you specified on the previous screen than will fit on
the Object List in Relationship File window, you can scroll the list using standard scrolling
commands. Use this window to select the object for which File-AID/RDX will search the relationship
file. The resulting list of relationships associated with the selected object is displayed on the
Relationship Detail screen.

CMD
Enter an S line command in this column next to the object for which you want to see a list of
relationships. The S line command is the only valid line command for this screen.

Object Name
Displays the names of MVS objects that match the value specified in the MVS File name field on
the Process MVS Objects screen.

Line Commands
The following File-AID/RDX-specific line command is valid on this screen:

S (Select)
Use the S line command to select an object for which you want to display relationship
information. Relationship information about the object you select is displayed on the
Relationship Detail screen as shown in Figure 34 on page 102.

Relationship Detail
The Relationship Detail screen shown in Figure 34 is displayed when you selected Options 1, Browse
All, or 2, Edit AR, on the DB2 or MVS Relationship Facilitator screen for a single object, or entered the
B or E line command in the DB2 or MVS Object List, or after selecting a single object from a table or
object list window.
102 File-AID/RDX Reference

When your profile has navigation criteria Direct set to C or P (see also Direct on page 58), a message
displays alerting you that the relationship tree has been built using those settings. The resulting
relationship listing may be different than that resulting from navigation criteria Direct Y or N.

Figure 34. Relationship Detail

File-AID/RDX ----------- Relationship Detail ------------ Row 1 to 5 of 9 

Command ===> SCROLL ===> CSR 

Base object: 'TSOID01.FARDX2.SAMP.SALEHIST' 

Line Commands: S - Select Relationship to Modify D - Delete Relationship
A - Add Application Relationship I - Relationship Information

Obj Rel Status/
CMD Parent/Dependent Type Type Description
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.TSOID01.ORDER_TABLE DB2 AR
'TSOID01.FARDX2.SAMP.SALEHIST' MVS Order to Sales H
_ 'TSOID01.FARDX2.SAMP.SALEHIST' MVS AR
'TSOID01.FARDX2.SAMP.CREDIT' MVS Sales History to
_ 'TSOID01.FARDX2.SAMP.SALEHIST' MVS AR
'TSOID01.FARDX2.SAMP.ZIPCODE' MVS Sales History ZI
_ LOCATION.TSOID01.ORDER_TABLE DB2 RI ASSOCIATED REL.
LOCATION.TSOID01.ORDER_LINE_TABLE DB2 ORDLORD
_ LOCATION.TSOID01.PART_TABLE DB2 RI ASSOCIATED REL.
LOCATION.TSOID01.ORDER_LINE_TABLE DB2 ORDLPRT

Use this screen to view a list of all relationships associated with the specified object and to select a
relationship about which you want to display detailed information with the I line command.

Other line commands and the ADD primary command allow you to add, change or delete
relationships.

The Relationship Detail screen displays a scrollable list of relationships involving the object specified
with a previous Browse or Edit option or line command.

A relationship will appear more than once on this screen if there is more than one relationship
between a given pair of objects.

CMD
Enter line commands in this column. See Line Commands on page 107 for information about
commands that are valid for this screen.

Parent/
Displays the name of the object defined as the parent in a relationship in the upper row (the row
with the CMD input field).

/Dependent
Displays the name of the object defined as the dependent in a relationship in the lower row,
under its parent.

For long object names, you scroll Parent and Dependent entries separately: 
Place the cursor in a Parent entry to scroll all Parent entries to the left or right.
Place the cursor in a Dependent entry to scroll all Dependent entries to the left or right.
Relationship Facilitator 103

Obj Type
Indicates the object type of the parent and dependent.

DB2 Db2 table.

MVS MVS file.
KEY Output Key file or IMS database (dependent only).

Rel Type
Indicates the kind of relationship that exists between the corresponding parent and dependent
objects.

RI Db2-defined referential integrity.

AR User-defined application relationship. Created and maintained by the user.
AR-C User-defined conditional (data driven) application relationship. Created and
maintained by the user.

Status/Description
Indicates the condition of each relationship in the upper row (Status) and the RI Relationship
Name if it is a Db2 RI in the lower row (RelName) or the AR description for each relationship. If
there is an error for the dependent object, it will override the Description in the lower row. The
status row is blank if the relationship file is consistent with the Db2 catalog for the particular
relationship. Refer to Status/Description on page 122 for a list of possible messages.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

A (Add)
Adds an application relationship for this parent object. Displays the Add Relationships — Specify
Object Types screen so you can specify the parent and dependent object types for the new
relationship. See Add Relationships — Specify Object Types on page 123.

D (Delete)
Deletes an AR or RI relationship from the relationship file.

I (Relationship Information)
Invokes the Relationship Information screen, which displays detailed information about the
selected RI or application relationship. See Relationship Information Screen on page 107 for more
information on the contents of the screen.

S (Select)
Selects an AR relationship for modification and displays the Column/Field Relationships screen.
Not valid for RI relationships. See Building Column/Field Relationships on page 167 for more
information.
104 File-AID/RDX Reference

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

ADD
Enter the ADD command in the COMMAND field to add an application relationship. Displays the
Add Relationships — Specify Object Types so you can specify the parent and dependent object
types for the new relationship. See Add Relationships — Specify Object Types on page 123.

GRAPHIC (G)
Enter the GRAPHIC command in the COMMAND field to invoke the Graphical Relationship
Display screen and show RI and application relationships for the table specified on the Browse
Relationship File screen. See Graphical Relationship Display on page 104 for more information
on the Graphical Relationship Display screen. There are no operands associated with this
command.

SQLID
Enter the SQLID primary command to change the current Db2 SQLID. Enter the SQLID command
without an operand to change the current SQLID to match the current userid. Use the new-sqlid
operand to specify any SQLID.

Graphical Relationship Display

The Graphical Relationship Display screen shown in Figure 35 is displayed when you enter the
GRAPHIC command on the Relationship Detail screen, the RI Relationship Detail screen, or the AR
Relationship Detail screen.

Figure 35. Graphical Relationship Display Screen

File-AID/RDX ---- Graphical Relationship Display ---------- Row 1 to 18 of 23 

COMMAND ===> SCROLL ===> CSR 

TAB to Object and press ENTER for an Option List 
* Denotes the object is involved in additional relationships 

MVS-'TSOID01.FARDX2.SAMP.ZIPCODE' 
| 
|__ DB2-CUSTOMER_TABLE 
| 
|__ MVS-'TSOID01.FARDX2.SAMP.CREDIT' 
| 
|__ DB2-CONTACT_TABLE 
| 
|__ MVS-'TSOID01.FARDX2.SAMP.SALEHIST' 
| 
|__ MVS-'TSOID01.FARDX2.SAMP.INVOICE' 
| 
|__ DB2-ORDER_TABLE 
| 
*|__ DB2-ORDER_LINE_TABLE 


DB2-PART_TABLE 
| 
*|__ DB2-ORDER_LINE_TABLE 
| 
|__ DB2-SUPPLIER_TABLE 
Relationship Facilitator 105

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:

CREATOR
Enter the CREATOR primary command in the graphical relationship display and all Db2 objects
will include their Creator ID. This command acts as a toggle command, thus, when entering the
command again, Db2 objects will include their Creator ID only when there is more than one
object with the same name.

Understanding the Graphical Relationship Display

The body of this screen consists of a graphical representation of the relationships in which the object
you selected on the Browse Table Specification screen or Browse File Specifications screen is involved.
Read the Graphical Relationship Display as follows:

• Objects are identified by their:

– Object type, either DB2, MVS, or KEY

– Object name

• DB2 objects include the table or view name. The Creator name is displayed only if
necessary to have a unique name or when you enter the CREATOR primary command
(see CREATORprimary command).
• MVS objects include the fully qualified file name (quoted).
• KEY objects include the fully qualified KEY record layout file or IMS database name
(quoted).

• Relationships are arranged such that each object that has no parents is at the top of a group. Each
group consists of an object that has no parents, its dependents, their dependents, etc. File-
AID/RDX displays one group of relationships for each object that has no parents. For example, in
Figure 35, MVS-'TSOID01.FARDX2.SAMP. ZIPCODE' and DB2-PART_TABLE have no parents.
They are at the top of their groups, respectively. There is one group displayed for MVS-'TSOID01.
FARDX2.SAMP.ZIPCODE' and one group displayed for DB2-PART_TABLE.

For situations involving cyclical relationships, File-AID/RDX puts the object

for which the most detailed dependent display can be shown at the top of
the group.

• The object you specified on the Browse Specifications screens is highlighted. In Figure 35, MVS-
'TSOID01.FARDX2.SAMP.CREDIT' is the object specified and is therefore highlighted.

• Relationships are displayed as lines that connect the boxes. Lines start at the bottom of parent
objects and end at the left side of dependent objects. In Figure 35, MVS-
'TSOID01.FARDX2.SAMP.ZIPCODE' is a parent of DB2-CUSTOMER_TABLE. DB2-
CUSTOMER_TABLE itself is a parent of MVS-'TSOID01.FARDX2.SAMP.CREDIT' and four other
objects.

• Objects that are displayed more than once are denoted by an asterisk (*). In Figure 35 on page
104, DB2-ORDER_LINE_TABLE is displayed with an asterisk next to it because it is displayed
twice (once as a dependent of DB2-ORDER_TABLE and again as a dependent of DB2-
PART_TABLE).

You can scroll UP and DOWN, LEFT and RIGHT to see information that does not fit on a single
screen.
106 File-AID/RDX Reference

Use the TAB key to move the cursor from object name to object name. When the cursor is next to an
object name, you can press ENTER to display a list of options available as shown in Figure 36. In
addition, you can enter the I line command to display the Relationship Information screen. See Line
Commands on page 107 for more information about the I line command.

Figure 36. Graphical Relationship Display with Option List

File-AID/RDX ---- Graphical Relationship Display ---------- Row 1 to 18 of 23 

COMMAND ===> SCROLL ===> CSR 

TAB to Object and press ENTER for an Option List 
* Denotes the object is involved in additional relationships 

MVS-'TSOID01.FARDX2.SAMP.ZIPCODE' 
| 
|__ DB2-CUSTOMER_TABLE 
Option List for: MVS-'TSOID01.FARDX2.SAMP.CREDIT' 
Row 1 to 3 of 3 
COMMAND ===> 

Enter "S" to select an option 

CMD Description 
--- ----------------------------------------------------------------- 
_ Display Relationship Information(I) 
_ Go to expanded view of dependents 
_ Go to dependent of MVS-'TSOID01.FARDX2.SAMP.SALEHIST' 
***************************** Bottom of data ***************************** 




Option List
To select an option from the Option List, type an S in the CMD column next to an option and press
Enter.

The options in the Option List are as follows:

Display Relationship Information (I)

Displays the Relationship Information pop-up window. See Relationship Information Screen on
page 107 for more information about the Relationship Information window.

Go to expanded view of dependents

Scrolls the display such that the first occurrence of the selected object is positioned at the top of
the display. The first occurrence of a given object in the Graphical Relationship Display has an
expanded display of its dependents (if it has any). Subsequent occurrences of a given object do
not repeat expanded detail.

In Figure 35 on page 104, for example, if the cursor was positioned on the occurrence of DB2-
ORDER_LINE_TABLE under DB2-PART_TABLE, selecting Go to expanded view of dependents
would position the first occurrence of ORDER_LINE_TABLE at the top of the display. The first
occurrence of ORDER_LINE_TABLE under ORDER_TABLE would display any dependents if
ORDER_LINE_TABLE had any.

Go to dependent of objectname
Scrolls the display such that the occurrence of the selected object that is a dependent of
objectname is at the top of the display. Use this option to determine where the object is a
dependent in other relationships.
Relationship Facilitator 107

For example, if the cursor was positioned on the second occurrence of ORDER_LINE_TABLE when
you pressed ENTER, the following entry would be displayed:

Go to dependent of ORDER_TABLE

Selecting this entry would position the occurrence of ORDER_LINE-TABLE under

ORDER_TABLE at the top of the display. If ORDER_LINE_TABLE had additional parents, there
would be an entry on the Option List for each parent.

Line Commands
The following File-AID/RDX-specific line command is valid on this screen.

I (Relationship Information)
Displays the Relationship Information screen. See Relationship Information Screen for more
information about the Relationship Information screen.

Relationship Information Screen

The Relationship Information screen contains information about the relationship you specified on
the Relationship Detail screen. If there are more columns comprising the relationship than can be
displayed in this screen at one time, you can scroll the Parent Columns and Dependent Columns
fields using standard scrolling commands.

Depending on the object types File-AID/RDX displays slightly different information. When you select
a Db2 RI relationship, the Relationship Information window is displayed as shown in Figure 37.

Figure 37. Relationship Information Screen—RI relationship information

File-AID/RDX Relationship Information DB2 Row 1 to 2 of 2 

Command ===> Scroll ===> CSR 

Parent Name: LOCATION.TSOID01.PART_TABLE Type: DB2 



Dependent Name: LOCATION.TSOID01.SUPPLIER_TABLE Type: DB2 



Relationship Details: 
Description: RI - SUPPPART 
Status: 
Created: 1996-01-09 14.55.16.425499 User: TSOID01 
Last Modified 1996-01-09 14.55.16.425499 User: TSOID01 
Parent Columns /Type(Length) Dependent Columns /Type(Length) 
----------------------------------------- ------------------------------------
PART_NUMBER PART_NUMBER 
CHAR(6) CHAR(6) 
*** End Of Columns *** *** End Of Columns *** 




When you select an application relationship between an MVS and Db2 object, the Relationship
Information window is displayed as shown in Figure 38 on page 108.
108 File-AID/RDX Reference

Figure 38. Relationship Information Screen—MVS to DB2 Application Relationship Information

File-AID/RDX Relationship Information Row 1 to 2 of 2 

Command ===> Scroll ===> CSR 

Parent Name: 'TSOID01.FRSAMP.PARTTABL' Type: MVS 
Layout Dataset: ‘TSOID01.FRSAMP.LAYOUTS’ Mbr: PARTTABL 
XREF Dataset: Mbr: 
01 Level Name: PROD001-PART-TABLE 
Dependent Name: LOCATION.TSOID01.SUPPLIER_TABLE Type: DB2 



Relationship Details: 
Description: AR - 
Status: ADDED 
Created: 2006-11-01 16.00.16 User: TSOID01 
Last Modified User: 
Parent Fields /Type(Length) Dependent Columns /Type(Length) 
----------------------------------------- ------------------------------------
1/PART-NUMBER 1/PART_NUMBER 
CHAR(6) CHAR(6) 
*** End Of Fields *** *** End Of Columns *** 





When you select an MVS to MVS AR relationship, the Relationship Information screen is displayed as
shown in Figure 39.

Figure 39. Relationship Information Screen—MVS to MVS AR Relationship Information

File-AID/RDX Relationship Information Row 1 to 2 of 2 

Command ===> SCROLL ===> CSR 

Parent Name: 'TSOID01.FASAMP.EMPLOYEE' Type: MVS 
Layout Dataset: TSOID01.FASAMP.LAYOUTS Mbr: EMPLOYEE 
XREF Dataset: Mbr: 
01 Level Name: EMPLOYEE-MASTER-FILE 
Dependent Name: 'TSOID01.FASAMP.ORDRFILE' Type: MVS 
Layout Dataset: TSOID01.FASAMP.LAYOUTS Mbr: ORDERWO 
XREF Dataset: Mbr: 
01 Level Name: INTERNAL-WORK-ORDER 
Relationship Details: 
Description: AR - 
Status: 
Created: 2006-11-01 15.26.06 User: TSOID01 
Last Modified User: 
Parent Fields /Type(Length) Dependent Fields /Type(Length) 
----------------------------------------- ------------------------------------
1/EMP-NUMBER 2/ORDER-NO 
CHAR(1,5) CHAR(1,5) 
*** End Of Fields *** *** End Of Fields *** 




The Relationship Information screen consists of the fields described below. Fields that vary according
to relationship or object type are described under separate headings.

Parent and Dependent Object Name Area

The fields in this area provide information about the parent and dependent objects.

Parent Name
Displays the fully qualified name of the parent object according to the parent’s object type.
Relationship Facilitator 109

Type
Indicates the object type of the parent and dependent object.

DB2
Db2 table.

MVS
MVS file.

KEY
Output Key file or IMS database (dependent only).

Layout File
Displays only if parent or dependent object is an MVS file or a dependent Output Key file or IMS
segment with a layout. Identifies the record layout file for the MVS object, Output Key file or IMS
segment used for this relationship.

XREF File
Only displays if layout usage is X. Identifies the XREF file name for the MVS object in this
relationship.

01 Level Name
Only displays for MVS object. Identifies the 01 Level name for the MVS object in this
relationship.

Mbr
Displays only if parent or dependent object is an MVS file. Each Mbr field identifies the member
of the record layout file or the XREF file that contains the layout information for the parent or
dependent MVS object in this relationship.

Dependent Name
Displays the fully qualified name of the dependent object according to the dependent’s object
type.

Relationship Details Area

The fields in this area provide information about the relationship such as the Relationship
Description, the Status of the relationship, creation and modification dates. The * AR Conditional *
110 File-AID/RDX Reference

heading indicates that it is a conditional application relationship created with the COND command.
The column displays a value only for already defined relationships in the Parent portion.

Description

A description of the selected relationship. The contents of this field vary according to the relationship type
as follows:
RI

The RELNAME from the Db2 catalog table, SYSIBM.SYSRELS (see Figure 37 on page 107).
AR

The description entered by the user when adding an application relationship (see Figure 38 on
page 108).
Status

Indicates the condition of each relationship. For Db2 RI relationships, this column is blank if the
information in the File-AID/RDX relationship file is consistent with the Db2 catalog for the particular
relationship. If the relationship file is not consistent with the Db2 catalog, File-AID/RDX displays one of
the following messages:
Message Explanation
Not in Dataset Indicates that this relationship exists in the Db2 catalog, but does not exist
in the relationship file specified on the RI Relationships screen. May indicate
that the relationship did not exist the last time the relationship file was
refreshed.
Not in DB2 Cat Indicates that this relationship exists in the relationship file specified on the
RI Relationships screen, but does not exist in the Db2 catalog.
Out of Sync 1 Indicates that the relationship exists in both the relationship file and the
Db2 catalog, but the timestamps on each table do not match each other.
May also indicate that the columns that comprise the foreign key are
inconsistent.
ASSOCIATED REL At least one of the objects involved in this relationship is a descendant of
the driving object, or the driving object is a descendant of at least one of
the objects in this relationship.
In addition, File-AID/RDX displays the following messages as a result of line command processing:
Message Explanation
Deleted Displayed after you enter the D line command. Indicates that this
relationship has been deleted from the relationship file. It does not
however, indicate that the relationship has been deleted from the Db2
catalog.
Loaded Displayed after you enter the S line command. Indicates that this
relationship has been loaded into the relationship file.
Refreshed Displayed after you enter the S line command for a relationship that had
the message Out of Sync 1 displayed. Indicates that the Db2 catalog and
the relationship file are now consistent with respect to this relationship.
For RI relationships one of the following messages may be displayed:
Modified Displayed when you enter the S line command and complete the Field
Relationships screen. Indicates that this relationship has been modified.
Loaded Displayed after you enter the S line command. Indicates that this
relationship has been loaded into the relationship file.
Refreshed Displayed after you enter the S line command for a relationship that had
the message Out of Sync 1 displayed. Indicates that the Db2 catalog and
the relationship file are now consistent with respect to this relationship.
For AR application relationships one of the following messages may be displayed.
Relationship Facilitator 111

Modified Displayed when you enter the S line command and complete the Field
Relationships screen. Indicates that this relationship has been modified.
Added Displayed when you enter the A line command and complete the
Column/Field Relationships screen. Indicates that this relationship has
been added to the relationship file.
Deleted Displayed when you enter the D line command. Indicates that this
relationship has been deleted from the relationship file.
In addition, File-AID/RDX could display the following error messages:
Object not Found File-AID/RDX cannot find the parent object in the MVS or Db2 catalog. This
may indicate that the object not found has been dropped. Use the D line
command to delete the invalid relationships.
Column Errors An invalid field relationship exists within the relationship. Invalid field
relationships may be caused by eliminating or changing a column from a
table defined in the Db2 catalog. Use the S line command to display the
Column/Field Relationships screen where the invalid column/field
relationships are indicated by the ERR> flag.
DBD not Found File-AID/RDX cannot find the dependent IMS database. This may indicate
that the database not found has been deleted or renamed. Use the D line
command to delete the invalid relationship.
Segment Errors An invalid root segment relationship exists within the KEY (IMS)
relationship. Invalid relationships may be caused b eliminating or changing
a root segment in the IMS database.

Use the S line command to display the Column/Segment Relationships

screen where the invalid relationships are indicated by the ERR> flag.

Created
Displays the date and time that the relationship was created. For Db2 RI relationships it
represents when it was loaded into the Db2 catalog. File-AID/RDX displays date and time in the
format specified at the time of Db2 installation.

User
Displays the user ID of the person who created the AR relationship or who loaded the RI
relationship into the relationship file using either the initial load batch job or with the Load RI
option or line command.

Last Modified
Display date, time, and user ID indicating when the relationship was last modified and who
modified it. File-AID/RDX displays date and time in the format specified at the time of Db2
installation.

Parent Columns or Parent Fields

Displays the numbers and names of the columns from the Db2 parent table or the numbers and
names of the fields from the MVS parent file that are involved in the relationship.

Type(Length)
The line directly below the parent field’s or column’s name displays the field’s or column’s data
type. The length of the data is displayed in parentheses immediately following the data type for
112 File-AID/RDX Reference

CHAR, VCHAR, GRPH, VGRPH, and DEC data types only. If an extended column relationship has
been defined, File-AID/RDX indicates this by displaying the start position and length of the
string from the parent column in parentheses instead of the column’s length. For example, for
character data types:

CHAR(2,3)

indicates a string in a column with a data type of CHAR has an extended column relationship
defined beginning in position 2 for a length of 3.

If the Db2 column data type is distinct (UDT), File-AID/RDX displays only the
underlying built-in data type.

Dependent Columns or Dependent Fields

Displays the numbers and names of the columns from the dependent table or the numbers and
names of the fields from the MVS dependent file or the dependent Output Key file or IMS
segment with a layout that are involved in the relationship.

Type(Length)
The line directly below the dependent field’s or column’s name displays the field’s or column’s
data type. The length of the data is displayed in parentheses immediately following the data type
for CHAR, VCHAR, GRPH, VGRPH, and DEC data types only. If an extended column relationship
has been defined, File-AID/RDX indicates this by displaying the start position and length of the
string from the parent column in parentheses instead of the column’s length. For example, for
character data types:

CHAR(2,3)

indicates a string in a column with a data type of CHAR has an extended column relationship
defined beginning in position 2 for a length of 3.

If the Db2 column data type is distinct (UDT), File-AID/RDX displays only the
underlying built-in data type.

Root Segment
Displays the name of the Root Segment from the IMS database that correspond to the columns or
fields from the parent object (see Figure 50 on page 130).

DB2 RI Update Online Options

The DB2 RI Update Online Options Screen shown in Figure 40 is displayed when you select Load RI
(option 5 on the DB2 Relationship Facilitator menu) or enter the L line command for a specified Db2
object in the DB2 Object List.
Relationship Facilitator 113

Figure 40. DB2 RI Update Online Options Screen

File-AID/RDX ------- DB2 RI Update Online Options ----------------------- 

Option ===> Scroll ===> CSR 

RI Load Filter: 
SSID ===> DSN 
Location ===> LOCATION 
Creator ===> FRSAMP 
Table Name ===> ORDER_TABLE 

RI Load Scope ===> _ (Enter load option) 
1 = Load entire related thread for the creator and table 
2 = Load only relationship to or from this creator and table 
3 = Load all relationships for this creator 
4 = Load all relationships for this subsystem 

Note: Option 1 will display the entire related thread. 
Options 2-4 will only display relationship changes. 

Specify Relationship Information: 
File name ===> FRSAMP.RELATION 

This screen provides different options, or filters, on how you want to select RI relationships to be
loaded into the relationship file. The RI Load Filter and Relationship file information is prefilled with
your selections of the previous screen.

RI Load Filter
The RI Load Filter information is prefilled with your selections on the previous screen and cannot be
changed on this screen.

SSID
Specifies the Db2 subsystem ID of the Db2 subsystem on which the table resides for which you
want to view relationship information.

Location
Specifies the Db2 remote location ID of the Db2 subsystem on which the table resides for which
you want to view relationship information.

Creator
Specifies the authorization ID of the owner of the table for which you want to view relationship
information.

Table Name
Specifies the name of the Db2 object (table or view) for which you want to see relationship
information.

RI Load Scope
The RI Load Scope allows you to enter one of the RI Load Scope options.
114 File-AID/RDX Reference

1
Load the entire related thread for the above specified creator and table, including associated
relationships. The RI Relationship Detail Screen (Figure 41 on page 115) will then list the
qualifying RI relationships, including those already loaded into the relationship file.

2
Load only relationship to or from this creator and table. This option represents the narrowest
filter. The RI Relationship Detail Screen (Figure 42 on page 115) will then list the qualifying RI
relationships that need to be added to or updated in the relationship file. See also No Updates to
Process.

3
Load all relationships for this creator. The RI Relationship Detail Screen (Figure 43 on page 116)
will then list all qualifying RI relationships for the specified creator ID that need to be added to
or updated in the relationship file. See also No Updates to Process.

4
Load all relationships for this subsystem. The RI Relationship Detail Screen (Figure 44 on page
116) will then list all qualifying RI relationships for the specified Db2 subsystem that need to be
added to or updated in the relationship file. See also No Updates to Process.

No Updates to Process
The message ‘No Updates to Process’ indicates that for the selected RI load option the relationship
file already contains the up-to-date relationships based on the timestamps in the Relationship file
matching to the Db2 catalog.

Specify Relationship File Area

File Name
Specify the name of the File-AID/RDX relationship file that contains the relationship information
you want to display or maintain. Refer to Relationship File on page 37 for more information
about the relationship file.

RI Relationship Detail Screen

Depending on your RI Load Scope option selection in the DB2 RI Update Online Options Screen the
RI Relationship Detail screen has a different look.

RI Load Scope Option 1

When selecting RI Load Scope Option 1, the RI Relationship Detail screen displays as shown in Figure
41.
Relationship Facilitator 115

Figure 41. RI Relationship Detail Screen RI Load Option 1

File-AID/RDX ------ RI Relationship Detail ------------ Row 1 to 3 of 3

Command ===> SCROLL ===> CSR 

Primary Commands: ALL 
Line Commands: S = Select Relationship to Load D = Delete Relationship 
I = Relationship Information 

Base Object: LOCATION.FRSAMP.ORDER_TABLE

Obj Rel 
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.FRSAMP.ORDER_TABLE DB2 RI Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE DB2 
_ LOCATION.FRSAMP.PART_TABLE DB2 RI Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE DB2 
_ LOCATION.FRSAMP.PART_TABLE DB2 RI Not in Dataset
LOCATION.FRSAMP.SUPPLIER_TABLE DB2 
******************************* Bottom of data ********************************

This screen lists all Db2 RI relationships associated with the driving table, the Db2 table specified in
the Base Object: field, the table for which you had specified the Load RI option or L line command.

Use this screen to load and refresh relationships in the File-AID/RDX relationship file (S line
command or ALL primary command), delete relationships from the relationship file (D line
command), and select relationships about which you want to view more detailed information (I line
command).

This screen displays information from the Db2 catalog and File-AID/RDX’s relationship file about all
RI relationships involving the specified table.

Relationships in which the driving table is either the parent or the dependent are listed first. Those
relationships that involve the dependents of the driving table are listed below and are marked
ASSOCIATED REL.

RI Load Scope Options 2, 3, or 4

When selecting RI Load Scope Options 2, 3, or 4, the RI Relationship Detail screen displays as shown
in Figure 42, Figure 43, and Figure 44. The screens are identical, only the listed relationships are
different.

In this version of the RI Relationship Detail screen you can only load or update RI relationships in
your relationship file. The D (Delete) and I (Information) line commands are not available.

Figure 42. RI Relationship Detail Screen RI Load Option 2

File-AID/RDX ------ RI Relationship Detail ------------ Row 1 to 1 of 1

Command ===> SCROLL ===> CSR 

Primary Commands: ALL 
Line Commands: S = Select Relationship to Load 

Base Object: LOCATION.FRSAMP.ORDER_TABLE

Obj Rel 
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.FRSAMP.ORDER_TABLE DB2 RI Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE DB2 
******************************* Bottom of data ********************************
116 File-AID/RDX Reference

Figure 43. RI Relationship Detail Screen RI Load Option 3

File-AID/RDX ------ RI Relationship Detail ------------ Row 1 to 4 of 4

Command ===> SCROLL ===> CSR 

Primary Commands: ALL 
Line Commands: S = Select Relationship to Load 

Base Object: LOCATION.FRSAMP.ORDER_TABLE

Obj Rel 
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.FRSAMP.ORDER_TABLE DB2 RI Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE DB2 
_ LOCATION.FRSAMP.CUSTOMER_TABLE DB2 RI Not in Dataset
LOCATION.FRSAMP.CONTACT_TABLE DB2 
_ LOCATION.FRSAMP.PART_TABLE DB2 RI Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE DB2 
_ LOCATION.FRSAMP.PART_TABLE DB2 RI Not in Dataset
LOCATION.FRSAMP.SUPPLIER_TABLE DB2 
******************************* Bottom of data ********************************

Figure 44. RI Relationship Detail Screen RI Load Option 4

File-AID/RDX ------ RI Relationship Detail -------- Row 1 to 7 of 4,454

Command ===> SCROLL ===> CSR 

Primary Commands: ALL 
Line Commands: S = Select Relationship to Load 

Base Object: LOCATION.FRSAMP.ORDER_TABLE

Obj Rel 
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.$172.AGTANSIR DB2 RI Not in Dataset 
LOCATION.$172.AGTANSHS DB2 
_ LOCATION.$172.AGTZIP DB2 RI Not in Dataset 
LOCATION.$172.AGTANSIR DB2 
_ LOCATION.$172.AGTVER DB2 RI Not in Dataset 
LOCATION.$172.AGTASGN DB2 
_ LOCATION.$172.AGTZIP DB2 RI Not in Dataset 
LOCATION.$172.AGTASGN DB2 
_ LOCATION.$172.AGTZIP DB2 RI Not in Dataset 
LOCATION.$172.AGTCITY DB2 
_ LOCATION.$172.AGTZIP DB2 RI Not in Dataset 
LOCATION.$172.AGTZIPHS DB2 
_ LOCATION.$172.VKTVENRQRSLOG DB2 RI Not in Dataset 
LOCATION.$172.VKTRQRSXREF DB2 

For each relationship, the following columns are displayed:

CMD
Enter line commands in this column. See Line Commands on page 107 for information about
commands that are valid for this screen.

Parent/Dependent
Displays the name of the Db2 table defined as the parent in an RI relationship in the upper row
(the row with the CMD input field). The foreign keys in the dependent table refer to this table.
Table names are displayed in the format location.creator.table.

Displays the name of the Db2 table defined as the dependent in an RI relationship in the lower
row. This table contains the foreign keys. Table names are displayed in the format
location.creator.table.
Relationship Facilitator 117

Obj Type
Indicates the object type of the parent and dependent. For RI relationships, the object type
should always be DB2.

Rel Type
Indicates the kind of relationship that exists between the corresponding parent and dependent
objects.

RI Db2-defined referential integrity.

Status
Indicates the condition of each relationship in the upper row (Status) for each relationship. If
there is an error for the dependent object, it will override the Description in the lower row. The
status row is blank if the relationship file is consistent with the Db2 catalog for the particular
relationship. If the relationship file is not consistent with the Db2 catalog, File-AID/RDX displays
one of the following messages:

Message Explanation
Not in Dataset Indicates that this relationship exists in the Db2 catalog, but does not
exists in the relationship file specified on the RI Relationship screen. May
indicate that the relationship did not exist the last time the relationship
file was refreshed.
Not in DB2 Cat Indicates that this relationship exists in the relationship but does not exist
in the Db2 catalog. Indicates that the parent or dependent tables, or a
foreign key has been dropped.
Out of Sync1 Indicates the relationship exists in both the relationship file and the Db2
catalog, but the timestamps on each table do not match each other. May
also indicate that the columns that comprise the foreign key are
inconsistent.
In addition, File-AID/RDX displays the following messages as a result of line command
processing:
Deleted Displayed after you enter the D line command. Indicates that this
relationship has been deleted from the relationship file. It does not,
however, indicate that the relationship has been deleted from the Db2
catalog.
Loaded Displayed after you enter the S line command. Indicates that this
relationship has been loaded into the relationship file.
Refreshed Displayed after you enter the S line command for a relationship that had
the message Out of Sync 1 displayed. Indicates that the Db2 catalog and
the relationship file are now consistent with respect to this relationship.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

D (Delete)
(Load Option 1 only, see Figure 41) Deletes an RI relationship only from the relationship file and
displays the message Deleted in the Status column. Use this command to delete a relationship
from the relationship file when it no longer exists in the Db2 catalog.
118 File-AID/RDX Reference

I (Relationship Information)
(Load Option 1 only, see Figure 41) If you enter the I line command on a relationship for which a
message is displayed in the Status column, the RI Information window is displayed (see Figure 45
on page 119). If you enter the I line command on a relationship for which the Status column is
blank (RI already in relationship file), the Relationship Information window is displayed (see
Figure 37 on page 107).

S (Select)
Selects a relationship to be loaded or refreshed. File-AID/RDX retrieves information about the RI
relationship from the Db2 catalog. If the relationship does not yet exist in the relationship file,
File-AID/RDX loads the relationship and displays the message Loaded in the Status column. If the
relationship does exist but is inconsistent with the Db2 catalog, File-AID/RDX uses the
information from the Db2 catalog to refresh the relationship file and displays the message
Refreshed in the Status column. File-AID/RDX also displays the messages Loaded and Refreshed
in the Status column.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

ALL
Enter the ALL command to select and load all RI relationships into the relationship file. There are
no operands associated with this command.

GRAPHIC (G)
Enter the GRAPHIC command to invoke the Graphical Relationship Display screen and show RI
relationships for the selected table. See Graphical Relationship Display on page 104 for more
information on the Graphical Relationship Display screen. There are no operands associated with
this command.

SQLID
Enter the SQLID primary command to change the current Db2 SQLID. Enter the SQLID command
without an operand to change the current SQLID to match the current userid. Use the new-sqlid
operand to specify any SQLID.

RI Information Screen
The RI Information screen is displayed when you enter the I line command on the RI Relationship
Detail screen on a relationship and press Enter. This window contains detailed information about the
relationship on which you invoked the I line command on the RI Relationship Detail screen.
Relationship Facilitator 119

Figure 45. RI Information Screen

File-AID/RDX Relationship Information DB2 Row 1 to 2 of 2 

Command ===> Scroll ===> CSR 

Parent Name: LOCATION.FRSAMP.EMP Type: DB2 



Dependent Name: LOCATION.FRSAMP.DEPT Type: DB2 



Relationship Details: 
Description: RI - REP 
Status: Not in Dataset 
Created: User: 
Last Modified User: 
Parent Columns /Type(Length) Dependent Columns /Type(Length) 
----------------------------------------- ------------------------------------ 
LNAME REP 

*** End Of Columns *** *** End Of Columns *** 


Parent and Dependent Object Name Area

The fields in this area provide information about the parent and dependent objects.

Parent Name
Displays the name of the table defined as the parent table in an RI relationship. This table’s
primary index contains values that match the foreign keys defined in the corresponding
dependent table. Tables are displayed in the format location.creator.table.

Type
Indicates the object type of the parent and dependent object.

DB2 indicates a Db2 table.

Dependent Name
Displays the name of the table defined as the dependent table in an RI relationship. This table
contains the foreign key, the values of which match the parent table’s primary index. Tables are
displayed in the format location.creator.table.

Relationship Details Area

The fields in this area provide information about the relationship such as the Relationship
Description, the Status of the relationship, creation and modification dates.

Description
A description of the selected relationship.

RI The RELNAME from the Db2 catalog table, SYSIBM.SYSRELS (see Figure 37 on
page 107).
120 File-AID/RDX Reference

Status
Displays the message displayed in the Status column on the RI Relationship Detail screen.

Message Explanation
Not in Dataset Relationship in Db2 catalog is not loaded in the relationship
file.
NOT IN DB2 CAT Relationship cannot found in the Db2 catalog.
OUT OF SYNC 1 Timestamp is inconsistent between Db2 catalog and
relationship file.

Created
Displays the date and time that the relationship was created. For Db2 RI relationships it
represents when it was loaded into the Db2 catalog. File-AID/RDX displays date and time in the
format specified at the time of Db2 installation.

User
Displays the user ID of the person who loaded the RI relationship into the relationship file using
either the initial load batch job or the Load RI option or line command.

Last Modified
Display date, time, and user ID indicating when the relationship was last modified and who
modified it. File-AID/RDX displays date and time in the format specified at the time of Db2
installation.

Parent Columns
Displays the names of the columns from the parent table that are referenced by the foreign key.

Dependent Columns
Displays the names of the columns from the dependent table that comprise the foreign key.

Type(Length)
The line directly below the parent column’s name displays the column’s data type. The length of
the data is displayed in parentheses immediately following the data type for CHAR, VCHAR,
GRPH, VGRPH, and DEC data types only. Note that the length value only displays after the RI has
been loaded into the relationship file.

If the Db2 column data type is distinct (UDT), File-AID/RDX displays only the
underlying built-in data type.
Relationship Facilitator 121

Application Relationship Detail

The Application Relationship Detail screen shown in Figure 46 is displayed when you select the Edit
AR option or enter the E line command for an object that already has an application relationship
defined in the current relationship file.

Figure 46. Application Relationship Detail Screen

File-AID/RDX Application Relationship Detail Row 1 to 1 of 1 

Command ===> SCROLL ===> CSR


Base object: LOCATION.TSOID01.BILLING 

Line Commands: S - Select Relationship to Modify D - Delete Relationship
A - Add Application Relationship I -
Relationship Information 

Obj Rel Status/
CMD Parent/Dependent Type Type Description
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.TSOID01.BILLING DB2 AR 
LOCATION.TSOID01.PURCHASEORDER DB2 Billing to Purch
******************************* BOTTOM OF DATA ********************************

This screen displays a list of application relationships (AR) for the object and relationship file
specified with the Edit AR option or E line command. It is similar to the Relationship Detail on page
101, except that it only displays application relationships for the selected object.

Use this screen to select application relationships from the relationship file that you want to modify
(S line command) or delete (D line command). You can also use this screen to display detailed
information about a relationship (I line command) or to begin the process of adding new application
relationships (A line command or ADD primary command).

CMD
Enter a valid line command next to the appropriate relationship. See Line Commands on page
107 for information about valid line commands.

Parent/
Displays the name of the object defined as the parent in a relationship in the upper row (the row
with the CMD input field).

/Dependent
Displays the name of the object defined as the dependent in a relationship in the lower row,
under its parent.

Obj Type
Indicates the object type of the parent and dependent.

DB2 Db2 table.

122 File-AID/RDX Reference

MVS MVS file.

KEY Output Key file or IMS database (dependent only).

Rel Type
Indicates the kind of relationship that exists between the corresponding parent and dependent
objects. (Always AR or AR-C as only application relationships are displayed.)

AR User-defined application relationship. Created and maintained by the user.

AR-C User-defined data driven, conditional application relationship. Created and
maintained by the user.

Status/Description
Indicates the condition of each relationship in the upper row (Status) and the Application
Relationship Description for each relationship in the lower row. If there is an error for the
dependent object, it will override the Description in the lower row. The status row is blank if the
relationship file is consistent with the Db2 catalog for the particular relationship. Refer to Status
on page 120 for a list of possible messages.

Message Explanation
Modified Displayed when you enter the S line command and complete the
Relationships screen. Indicates that this relationship has been modified.
Added Displayed when you enter the A line command or ADD primary
command and complete the Relationships screen. Indicates that this
relationship has been added to the relationship file.
Deleted Displayed when you enter the D line command. Indicates that this
relationship has been deleted from the relationship file.

In addition, File-AID/RDX could display the following error messages:

Message Explanation
Object not Cannot find one of the objects (dependent or parent) in the MVS or Db2
found catalog. This may indicate that the object not found has been dropped.
Use the D line command to delete the invalid relationship.
Column Errors An invalid column relationship exists within the application relationship.
Invalid column relationships may be caused by eliminating or changing a
column from a table defined in the Db2 catalog.

Use the S line command to display the Column/Field Relationships screen

where the invalid column/field relationship is in indicated by the ERR>
flag.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

A (Add)
Adds an application relationship for this parent object. Displays the Add Relationships screen.
See Add Relationships — Specify Object Types on page 123.
Relationship Facilitator 123

D (Delete)
Deletes an application relationship from the relationship file.

I (Relationship Information)
Invokes the Relationship Information screen. See Relationship Information Screen on page 107
for more information.

S (Select)
Selects an application relationship for modification and displays the Column/Field Relationships
screen. See Building Column/Field Relationships on page 167 for more information.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

ADD
Enter the ADD command in the COMMAND field to add an application relationship. Displays the
Add Relationships screen. See Add Relationships — Specify Object Types on page 123.

GRAPHIC (G)
Enter the GRAPHIC command in the COMMAND field to invoke the Graphical Relationship
Display screen and show application relationships for the selected table. See Graphical
Relationship Display on page 104 for more information on the Graphical Relationship Display
screen. There are no operands associated with this command.

Relationship Information
The Relationship Information screen is displayed when you enter the I line command on the
Relationship Detail screen or the Application Relationship Detail screen. Use the Relationship
Information screen to view detailed information about the relationship on which you entered the I
line command. See Relationship Information Screen on page 107 for more information about the
contents of this window.

Add Relationships — Specify Object Types

The Add Relationships — Specify Object Types screen shown in Figure 47 is displayed when you do
one of the following:

• Enter the Add AR option or A line command for a specific object.

• Enter the Edit AR option or E line command for a specific object and no object match is found in
the relationship file
• Enter the ADD primary command on the Relationship Detail screen
• Use the A (Add) line command on the Relationship Detail screen (see Figure 34 on page 102).
124 File-AID/RDX Reference

Figure 47. Object Type Selection Screen for Adding Application Relationship

File-AID/RDX -------------- Add Relationships ------------------------------

Command ===> 

Line Commands: S to specify object Types: 

Parent Object Type: Dependent Object Type: 

S_ DB2 Table S_ DB2 Table 

__ MVS file __ MVS file 

__ IMS and Output Key Files 

Specify Relationship File: 
File Name ===> FRSAMP.RELATION



Use this screen to specify the object type of the parent and the dependent object for the new
relationship.

Parent Object Type

Select one of the two choices to indicate the object type of the parent:

DB2 Table Place an S line command in front of this option if the parent object is a Db2 table.
MVS File Place an S line command in front of this option if the parent object is an MVS file.

Dependent Object Type

Select one of the three choices to indicate the object type of the dependent:

DB2 Table Place an S line command in front of this option if the dependent object is a Db2
table.
MVS File Place an S line command in front of this option if the dependent object is an
MVS file.
IMS and Output Place an S line command in front of this option if the dependent object is an IMS
Key Files Segment or an Output Key file. Use this option when you want your extract to
create a key file that can be used by File-AID for IMS as an external key file (keys
dataset) to extract related IMS data or by File-AID/RDX as an Input Key file for
another extract.

Press Enter and continue with one of the six possible parent-dependent combinations:

1. DB2 ==> DB2, see Add Application Relationships — DB2 to DB2 on page 124
2. DB2 ==> MVS, see Add Relationships — DB2 to MVS on page 126
3. DB2 ==> KEY, see Add Relationships — DB2 to IMS and Output Key Files on page 130
4. MVS ==> DB2, see Add Relationships — MVS to DB2 on page 133
5. MVS ==> MVS, see Add Relationships — MVS to MVS on page 136
6. MVS ==> KEY, see Add Relationships — MVS to IMS and Output Key Files on page 140

Add Application Relationships — DB2 to DB2

This Add Application Relationships screen shown in Figure 48 is displayed after you specified Db2
tables for both parent and dependent objects in the previous screen, Add Relationships — Specify
Object Types on page 123 or Application Relationship Detail on page 121.
Relationship Facilitator 125

Figure 48. Add Relationships Screen — DB2 to DB2

File-AID/RDX ---------------- Add Application Relationships ----------------

Command ===> 

Specify Parent DB2 Table for Relationship Definition:
Location ===> LOCATION
Creator ===> TSOID01 (* or pattern for selection list)
Table Name ===> EMP (* or pattern for selection list) 

Specify Dependent DB2 Table for Relationship Definition:
Location ===> LOCATION
Creator ===> TSOID01 (* or pattern for selection list)
Table Name ===> EMP (* or pattern for selection list) 

Suggest Relationships when column name/type/length are identical:
Suggest ===> N (Y = Yes; N = No)

SSID ===> DSN (* or pattern for selection list)
Description ===>

Use this screen to specify the parent and dependent table for the new relationship.

Specify Parent DB2 Table for Relationship Definition Area

Use the fields in this area to specify the Db2 table that is the parent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.

Location
Specify the Db2 remote location ID of the Db2 subsystem on which the table resides for which
you want to add an application relationship.

Creator
Specify the authorization ID of the owner of the table for which you want to add an application
relationship. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).

Table Name
Specify the name of the Db2 object (table or view) for which you want to add an application
relationship. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).

Specify Dependent DB2 Table for Relationship Definition Area

Use the fields in this area to specify the Db2 table that is the dependent in the new relationship.
When specifying patterns in the fields, File-AID/RDX presents selection lists.

Location
Identifies the Db2 remote location ID of the Db2 subsystem on which the table resides which is
to be the dependent table of the new application relationship. Protected field; same as the parent
location by default.
126 File-AID/RDX Reference

Creator
Specify the authorization ID of the owner of the table that is to be the dependent for the new
application relationship. To view a list of tables, specify a pattern. Valid pattern characters are %,
_, and * (see Pattern Characters on page 27).

Table Name
Specify the name of the Db2 object (table or view) that shall be the dependent (child) table for
the new application relationship. To view a list of tables, specify a pattern. Valid pattern
characters are %, _, and * (see Pattern Characters on page 27).

Suggest Relationships when column name/type/length are identical Area

Suggest
Specify whether you want File-AID/RDX to select relationships when column name, type, and
length in the parent and dependent tables are identical.

Y Yes, File-AID/RDX will select columns with identical names, type and length for this
relationship definition and present them in the following Column Relationships Screen
(see Figure 54 on page 144). A message will inform you how many relationships have
been suggested. You can then accept them or delete individual relationship definitions
and/or add your own definitions.
N No, File-AID/RDX will not suggest any application relationships when entering the
following Column Relationships Screen (see Figure 54 on page 144).

When parent and dependent objects are the same object, File-AID/RDX will bypass the
automatic suggest functions as all columns/fields would be suggested. You can still
issue the SUGGEST primary command in the Field/Column Relationships screen.
Remember, File-AID/RDX only allows up to 20 field/column relationship definitions.

SSID
Specify the Db2 subsystem ID of the Db2 subsystem on which the table resides for which you
want to add a relationship. To view a list of subsystems, specify a pattern.

Relationship Description Area

Description
Enter a description up to 128 characters in length of the application relationship to be created.
This information is displayed in the Relationship Information window.

After specifying all required parent and dependent information, press Enter. You then continue
with the Column Relationship screen to define the related columns, see Relationships on page
144.

Add Relationships — DB2 to MVS

This Add Relationships screen shown in Figure 49 is displayed after you specified Db2 table as parent
object and MVS file as dependent object in the previous screen, Add Relationships — Specify Object
Types on page 123 or Application Relationship Detail on page 121.
Relationship Facilitator 127

Figure 49. Add Relationships Screen — DB2 to MVS

File-AID/RDX ---------------- Add Relationships ----------------------------

Command ===> Scroll ===> CSR

Specify Parent DB2 Table for Relationship Definition:
SSID ===> DSN (* or pattern for selection list)
Location ===> LOCATION
Creator ===> TSOID01 (* or pattern for selection list)
Table Name ===> EMP (* or pattern for selection list) 

Specify Dependent MVS File for Relationship Definition:
Name ===>
Record Layout usage ===> (S = Single; X = XREF;)
Record layout file ===>
Member name ===> (Blank or pattern for member list)
XREF file name ===>
Member name ===> (Blank or pattern for member list)
I/O Exit Name ===> 

Suggest Relationships when column and field name/type/length are identical:
Suggest ===> N (Y = Yes; N = No)

Description ===>

Use this screen to specify the Db2 parent table and the dependent MVS file for the new relationship.

Specify Parent DB2 Table for Relationship Definition Area

Use the fields in this area to specify the Db2 table that is the parent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.

SSID
Specify the Db2 subsystem ID of the Db2 subsystem on which the table resides for which you
want to add relationship information.

If the dependent file is already involved in another relationship definition

with a Db2 object, you must use the same SSID to add a new relationship.

Location
Specify the Db2 remote location ID of the Db2 subsystem on which the table resides for which
you want to add an application relationship.

Creator
Specify the authorization ID of the owner of the table for which you want to add an application
relationship. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).

Table Name
Specify the name of the Db2 object (table or view) for which you want to add an application
relationship. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).
128 File-AID/RDX Reference

Specify Dependent MVS File for Relationship Definition Area

Use the fields in this area to specify the MVS file that is the dependent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.

If the file is already involved in another relationship definition, you must use
the same layout, if usage=S, or use the same XREF file to add a new
relationship.

File name
Specify the MVS file name of the dependent in the new relationship. To view a list of files, specify
a pattern. Valid pattern character is * (see Pattern Characters on page 27).

Record layout usage

Indicate whether a single record layout (usage “S”), or an XREF (usage “X”) is to be used to define
the selection criteria.
You must also supply a Record Layout file and either a layout member (Usage=S) or an XREF file
and member (Usage=X).

Record layout file

Specify the record layout file for the MVS object that is to be the dependent in the new
relationship. To view a list of layout files, specify a pattern. Valid pattern character is * (see
Pattern Characters on page 27).

Member name
Specify the member of the record layout file that contains the layout information for the MVS
file. Leave blank or use a pattern to select a member from a list.

XREF file name

Only needed if layout usage is X. Specify the XREF file name for the MVS file that is to be the
dependent in the new relationship. To view a list of XREF files, specify a pattern. Valid pattern
character is * (see Pattern Characters on page 27).

Member name
Specify the member of the XREF file that contains the layout information for the dependent MVS
file. Leave blank or use a pattern to select a member from a list.

I/O Exit Name

Specify the I/O Exit Name for the dependent MVS file.

You only need to fill in this field when you want File-AID/RDX to use an IO exit routine when
accessing the above MVS file. Not needed to search the relationship file.
Relationship Facilitator 129

Suggest Relationships when column and field name/type/length are identical Area

Suggest
Specify whether you want File-AID/RDX to select relationships when column and field name,
type, and length in the parent and dependent tables are identical.

Y Yes, File-AID/RDX will select columns and fields with identical names, type and length
for this relationship definition and present them in the following Column/Field
Relationships Screen (see Figure 54 on page 144). A message will inform you how
many relationships have been suggested. You can then accept them or delete
individual relationship definitions and/or add your own definitions.
N No. File-AID/RDX will not suggest any application relationships when entering the
following Column/Field Relationships Screen (see Figure 54 on page 144).

When parent and dependent objects are the same object, File-AID/RDX will bypass the
automatic suggest functions as all columns/fields would be suggested. You can still issue the
SUGGEST primary command in the Field/Column Relationships screen. Remember, File-
AID/RDX only allows up to 20 field/column relationship definitions.

Relationship Description Area

Description
Enter a description up to 128 characters in length of the application relationship to be created.
This information is displayed in the Relationship Information screen.

After specifying all required parent and dependent information, press Enter. You then continue
with the Column/Field Relationship screen to define the related Db2 columns and MVS fields, see
Relationships on page 144.
130 File-AID/RDX Reference

Add Relationships — DB2 to IMS and Output Key Files

This Add Relationships screen shown in Figure 50 is displayed after you specified Db2 table as parent
object and IMS and Output Key Files as dependent object in the previous screen, Add Relationships —
Specify Object Types on page 123 or Application Relationship Detail on page 121. IMS key files can be
used to drive a File-AID for IMS extract. MVS key files can be used to drive File-AID/RDX extracts as an
Input Key file to the driving object.

If you intend to use the Output Key File as an Input Key File for a File-AID/RDX extract
(see Input Key File Specification on page 295), the Input Key File can only have data in
three formats: CHARACTER, BINARY, and DECIMAL. For DECIMAL, the length can only
be specified in bytes and the number of decimal places is implied to be 0.

Figure 50. Add Relationships Screen — DB2 to KEY

File-AID/RDX -------------- Add Application Relationships

-------------------
Command ===> Scroll ===> CSR 

Specify Parent DB2 Table for Relationship Definition: 
SSID ===> DSN (* or pattern for selection list) 
Location ===> LOCATION 
Creator ===> FRSAMP (* or pattern for selection list) 
Table Name ===> ORDER_TABLE (* or pattern for selection list) 

Specify Method to Define Output Key File Relationship:
Method ===> 1 1 - MVS Record Layout 2 - IMS DBD
3 - Both 
Specify IMS/Output Key File Definition: 
Record Layout File ===> 
Member Name ===> (Blank or pattern for member list) 

DBD Library ===> 
DBD Member ===> (Blank or pattern for member list) 

Suggest relationships when column and field name/type/length are identical: 
Suggest ===> N (Y = Yes; N = No) 

Description ===> 


Use this screen to specify the Db2 parent table and the dependent Output Key File method with its
record layout information and/or IMS database for the new relationship.

You have the choice to define the dependent record layout information and/or IMS database in three
ways:

1. with the Record Layout File name with a member name, if it is a PDS. The Record Layout
File must exist.

or

2. with the DBD Library name and a member name. The DBD Library must exist.

or

3. with the DBD Library name and a DBD member name and also the Segment (Record)
Layout File name with a member name, if it is a PDS. The Segment Layout File must exist.

Specify Parent DB2 Table for Relationship Definition Area

Use the fields in this area to specify the Db2 table that is the parent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.
Relationship Facilitator 131

SSID
Specify the Db2 subsystem ID of the Db2 subsystem on which the table resides for which you
want to add relationship information.

Location
Specify the Db2 remote location ID of the Db2 subsystem on which the table resides for which
you want to add an application relationship.

Creator
Specify the authorization ID of the owner of the table for which you want to add an application
relationship. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).

Table Name
Specify the name of the Db2 object (table or view) that is to be the parent table in the new
application relationship. To view a list of tables, specify a pattern. Valid pattern characters are %,
_, and * (see Pattern Characters on page 27).

Specify Method to Define Output Key File Relationship Area

Method
Specify which method to use for your IMS/Output Key File relationship definition:

1 MVS Record Layout. Select method 1 when you have a File-AID record layout describing
either the IMS segment or MVS record layout of the dependent object for which you
want to create an Output Key File during an extract.
2 IMS DBD. Select method 2 when you have an IMS DBD library for which you want to
establish a relationship with the parent Db2 table and for which you want to create the
Output Key File during an extract.
3 Both. Select method 3 when you have a File-AID record layout describing either the IMS
segment and an IMS DBD library for which you want to create an Output Key File during
an extract.

Specify IMS/Output Key File Definition Area

Use the fields in this area to specify the record layout and/or IMS database that is the dependent in
the new relationship. When specifying patterns in the fields, File-AID/RDX presents selection lists.

Record Layout File

Specify the record layout file that describes the record layout or IMS segment layout for which
you want to establish a relationship with the parent Db2 table.

Member Name
Specify the member of the record layout or IMS segment layout file for which you want to
establish a relationship. If you leave this field blank or enter a pattern other than an asterisk (*),
132 File-AID/RDX Reference

File-AID/RDX displays a Member List window containing a list of members that match the
specified pattern.

DBD Library
Specify the IMS DBD library for which you want to establish a relationship with the parent Db2
table.

Member
Specify the member of the DBD library for which you want to establish a relationship. If you
leave this field blank or enter a pattern other than an asterisk (*), File-AID/RDX displays a
Member List window containing a list of members that match the specified pattern.

Suggest relationships when column and field name/type/length are identical Area

Suggest
Specify whether you want File-AID/RDX to select relationships when column, field or segment
name, type, and length in the parent and dependent objects are identical.

Y Yes, File-AID/RDX will select columns and fields with identical names, type and length
for this relationship definition and present them in the following Column/Field
Relationships Screen (see Figure 54 on page 144). A message will inform you how
many relationships have been suggested. You can then accept them or delete
individual relationship definitions and/or add your own definitions.
N No. File-AID/RDX will not suggest any application relationships when entering the
following Column/Field Relationships Screen (see Figure 54 on page 144).

When parent and dependent objects are the same object, File-AID/RDX will bypass the
automatic suggest functions as all columns/fields would be suggested. You can still issue
the SUGGEST primary command in the Column/Field or Column/Segment Relationships
screen. Remember, File-AID/RDX only allows up to 20 Column/Field relationship
definitions.

Relationship Description Area

Description
Enter a description up to 128 characters in length of the application relationship to be created.
This information is displayed in the Relationship Information screen.

After specifying all required parent and dependent information, press Enter. You then continue
with the Column/Field or Column/Segment Relationship screen to define the related Db2
columns and Output Key File layout or IMS root segment, see Relationships on page 144.
Relationship Facilitator 133

Add Relationships — MVS to DB2

This Add Relationships screen shown in Figure 51 is displayed after you specified MVS file as parent
object and Db2 table as dependent object in the previous screen, Add Relationships — Specify Object
Types on page 123 or Application Relationship Detail on page 121.

Figure 51. Add Relationships Screen — MVS to DB2

File-AID/RDX ---------------- Add Relationships ----------------------------

Command ===> 

Specify Parent File for Relationship Definition: 
Name ===> 
Record Layout usage ===> (S = Single; X = XREF;) 
Record layout file ===> 
Member name ===> (Blank or pattern for member list) 
XREF file name ===> 
Member name ===> (Blank or pattern for member list) 
I/O Exit Name ===> 

Specify Dependent DB2 Table for Relationship Definition: 
SSID ===> DSN (* or pattern for selection list) 
Location ===> LOCATION 
Creator ===> TSOID01 (* or pattern for selection list) 
Table Name ===> EMP (* or pattern for selection list) 

Suggest Relationships when field and column name/type/length are identical:
Suggest ===> N (Y = Yes; N = No)

Description ===> MVS to DB2 relationship 

Use this screen to specify the parent MVS file and the dependent Db2 table for the new relationship.

Specify Parent File for Relationship Definition Area

Use the fields in this area to specify the MVS file that is the parent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.

If the file is already involved in another relationship definition, you must use
the same layout, if usage=S, or use the same XREF file to add a new
relationship.

File name
Specify the MVS file name of the parent in the new relationship. To view a list of files, specify a
pattern. Valid pattern character is * (see Pattern Characters on page 27).

If your current relationship file has an existing relationship for this MVS file
to a Db2 table, the new relationship must be to a Db2 table on the same
Db2 subsystem.

Record layout usage

Indicate whether a single record layout (usage “S”), or an XREF (usage “X”) is to be used to define
the selection criteria.
You must also supply a Record Layout file and either a layout member (Usage=S) or an XREF file
and member (Usage=X).
134 File-AID/RDX Reference

Record layout file

Specify the record layout file for the MVS object that is to be the parent in the new relationship.
To view a list of layout files, specify a pattern. Valid pattern character is * (see Pattern Characters
on page 27).

Member name
Specify the member of the record layout file that contains the layout information for the MVS
file. Leave blank or use a pattern to select a member from a list.

XREF file name

Only needed if layout usage is X. Specify the XREF file name for the MVS file that is to be the
parent in the new relationship. To view a list of XREF files, specify a pattern. Valid pattern
character is * (see Pattern Characters on page 27).

Member name
Specify the member of the XREF file that contains the layout information for the parent MVS file.
Leave blank or use a pattern to select a member from a list.

I/O Exit Name

Specify the I/O Exit Name for the parent MVS file.
You only need to fill in this field when you want File-AID/RDX to use an I/O exit routine when
accessing the above MVS file. Not needed to search the relationship file.

Specify Dependent DB2 Table for Relationship Definition Area

Use these fields to specify the Db2 table that is the dependent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.

SSID
Specify the Db2 subsystem ID of the Db2 subsystem on which the table resides for which you
want to add relationship information.

If the parent file is already involved in another relationship definition with a

Db2 object, you must use the same SSID to add a new relationship.

Location
Specify the Db2 remote location ID of the Db2 subsystem on which the table resides for which
you want to add an application relationship.

Creator
Specify the authorization ID of the owner of the table for which you want to add an application
relationship. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).
Relationship Facilitator 135

Table Name
Specify the name of the Db2 object (table or view) for which you want to add an application
relationship. To view a list of tables, specify a pattern. Valid pattern characters are %, _, and * (see
Pattern Characters on page 27).

Suggest Relationships when field and column name/type/length are identical Area

Suggest
Specify whether you want File-AID/RDX to select relationships when column/field name, type,
and length in the parent and dependent objects are identical.

Y Yes, File-AID/RDX will select columns and fields with identical names, type and length
for this relationship definition and present them in the following Column/Field
Relationships Screen (see Figure 54 on page 144). A message will inform you how
many relationships have been suggested. You can then accept them or delete
individual relationship definitions and/or add your own definitions.
N No. File-AID/RDX will not suggest any application relationships when entering the
following Column/Field Relationships Screen (see Figure 54 on page 144).

When parent and dependent objects are the same object, File-AID/RDX will bypass the
automatic suggest functions as all columns/fields would be suggested. You can still issue
the SUGGEST primary command in the Field/Column Relationships screen. Remember,
File-AID/RDX only allows up to 20 field/column relationship definitions.

Relationship Description Area

Description
Enter a description up to 128 characters in length of the application relationship to be created.
This information is displayed in the Relationship Information screen.

After specifying all required parent and dependent information, press Enter. You then continue
with the Field/Column Relationship screen to define the related MVS fields and Db2 columns, see
Relationships on page 144.
136 File-AID/RDX Reference

Add Relationships — MVS to MVS

This Add Relationships screen shown in Figure 52 is displayed after you specified MVS file as both
parent and dependent object in the previous screen, Add Relationships — Specify Object Types on
page 123 or Application Relationship Detail on page 121.

Figure 52. Add Relationships Screen — MVS to MVS

File-AID/RDX ---------------- Add Relationships ----------------------------

Command ===> 

Specify Parent File for Relationship Definition:
Name ===>
Record Layout usage ===> (S = Single; X = XREF;)
Record layout file ===>
Member name ===> (Blank or pattern for member list)
XREF file name ===>
Member name ===> (Blank or pattern for member list)
I/O Exit Name ===> 

Specify Dependent MVS File for Relationship Definition:
Name ===>
Record Layout usage ===> (S = Single; X = XREF;)
Record layout file ===>
Member name ===> (Blank or pattern for member list)
XREF file name ===>
Member name ===> (Blank or pattern for member list)
I/O Exit Name ===> 

Suggest Relationships when field name/type/length are identical:
Suggest ===> N (Y = Yes; N = No)
Description ===> MVS to MVS relationship

Use this screen to specify the parent MVS file and the dependent MVS file for the new relationship.

Specify Parent File for Relationship Definition Area

Use the fields in this area to specify the MVS file that is the parent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.

If the file is already involved in another relationship definition, you must use
the same layout, if usage=S, or use the same XREF file to add a new
relationship.

File name
Specify the MVS file name of the parent in the new relationship. To view a list of files, specify a
pattern. Valid pattern character is * (see Pattern Characters on page 27).

Record layout usage

Indicate whether a single record layout (usage “S”), or an XREF (usage “X”) is to be used to define
the selection criteria.
You must also supply a Record Layout file and either a layout member (Usage=S) or an XREF file
and member (Usage=X).
Relationship Facilitator 137

Record layout file

Specify the record layout file for the MVS object that is to be the parent in the new relationship.
To view a list of layout files, specify a pattern. Valid pattern character is * (see Pattern Characters
on page 27).

Member name
Specify the member of the record layout file that contains the layout information for the MVS
file. Leave blank or use a pattern to select a member from a list.

XREF file name

Only needed if layout usage is X. Specify the XREF file name for the MVS file that is to be the
parent in the new relationship. To view a list of XREF files, specify a pattern. Valid pattern
character is * (see Pattern Characters on page 27).

Member name
Specify the member of the XREF file that contains the layout information for the parent MVS file.
Leave blank or use a pattern to select a member from a list.

I/O Exit Name

Specify the I/O Exit Name for the parent MVS file.

You only need to fill in this field when you want File-AID/RDX to use an I/O exit routine when
accessing the above MVS file. Not needed to search the relationship file.

Specify Dependent MVS File for Relationship Definition Area

Use the fields in this area to specify the MVS file that is the dependent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.

If the file is already involved in another relationship definition, you must use
the same layout, if usage=S, or use the same XREF file to add a new
relationship.

File name
Specify the MVS file name of the dependent in the new relationship. To view a list of files, specify
a pattern. Valid pattern character is * (see Pattern Characters on page 27).

Record layout usage

Indicate whether a single record layout (usage “S”), or an XREF (usage “X”) is to be used to define
the selection criteria.
You must also supply a Record Layout file and either a layout member (Usage=S) or an XREF file
and member (Usage=X).
138 File-AID/RDX Reference

Record layout file

Specify the record layout file for the MVS object that is to be the dependent in the new
relationship. To view a list of layout files, specify a pattern. Valid pattern character is * (see
Pattern Characters on page 27).

Member name
Specify the member of the record layout file that contains the layout information for the MVS
file. Leave blank or use a pattern to select a member from a list.

XREF file name

Only needed if layout usage is X. Specify the XREF file name for the MVS file that is to be the
dependent in the new relationship. To view a list of XREF files, specify a pattern. Valid pattern
character is * (see Pattern Characters on page 27).

Member name
Specify the member of the XREF file that contains the layout information for the dependent MVS
file. Leave blank or use a pattern to select a member from a list.

I/O Exit Name

Specify the I/O Exit Name for the dependent MVS file.

You only need to fill in this field when you want File-AID/RDX to use an I/O exit routine when
accessing the above MVS file. Not needed to search the relationship file.

Suggest Relationships when field name/type/length are identical Area

Suggest
Specify whether you want File-AID/RDX to select relationships when field name, type, and length
in the parent and dependent objects are identical.

Y Yes, File-AID/RDX will select columns and fields with identical names, type and length
for this relationship definition and present them in the following Column/Field
Relationships Screen (see Figure 54 on page 144). A message will inform you how
many relationships have been suggested. You can then accept them or delete
individual relationship definitions and/or add your own definitions.
N No. File-AID/RDX will not suggest any application relationships when entering the
following Column/Field Relationships Screen (see Figure 54 on page 144).

When parent and dependent objects are the same object, File-AID/RDX will bypass the
automatic suggest functions as all columns/fields would be suggested. You can still issue the
SUGGEST primary command in the Field/Column Relationships screen. Remember, File-
AID/RDX only allows up to 20 field/column relationship definitions.
Relationship Facilitator 139

Relationship Description Area

Description
Enter a description up to 128 characters in length of the application relationship to be created.
This information is displayed in the Relationship Information screen.

After specifying all required parent and dependent information, press Enter. You then continue
with the Field Relationship screen to define the related MVS fields, see Relationships on page 144.
140 File-AID/RDX Reference

Add Relationships — MVS to IMS and Output Key Files

This Add Relationships screen shown in Figure 53 is displayed after you specified MVS file as the
parent object and IMS and Output Key Files as the dependent object in the previous screen, Add
Relationships — Specify Object Types on page 123 or Application Relationship Detail on page 121.
IMS key files can be used to drive a File-AID for IMS extract. MVS key files can be used to drive File-
AID/RDX extracts as an Input Key file to the driving object.

If you intend to use the Output Key File as an Input Key File for a File-AID/RDX extract (see
Input Key File Specification on page 295), the Input Key File can only have data in three
formats: CHARACTER, BINARY, and DECIMAL. For DECIMAL, the length can only be
specified in bytes and the number of decimal places is implied to be 0.

Figure 53. Add Relationship Screen — MVS to KEY

File-AID/RDX ---------------- Add Relationships ----------------------------

Command ===> 

Specify Parent File for Relationship Definition:
Name ===>
Record Layout usage ===> (S = Single; X = XREF;)
Record layout file ===>
Member name ===> (Blank or pattern for member list)
XREF file name ===>
Member name ===> (Blank or pattern for member list)
I/O Exit Name ===> 

Specify Method to Define Output Key File Relationship:
Method ===> 1 1 - MVS Record Layout 2 - IMS DBD
3 - Both 
Specify IMS/Output Key File Definition: 
Record Layout File ===> 
Member Name ===> (Blank or pattern for member list) 
DBD Library ===> 
DBD Member ===> (Blank or pattern for member list) 

Suggest Relationships when field name/type/length are identical:
Suggest ===> N (Y = Yes; N = No)
Description ===> MVS to IMS relationship

Use this screen to specify the parent MVS file and the dependent Output Key File method with its
record layout information and/or IMS database for the new relationship.

You have the choice to define the dependent record layout information and/or IMS database in three
ways:

1. with the Record Layout File name with a member name, if it is a PDS. The Record Layout
File must exist.

or

2. with the DBD Library name and a member name. The DBD Library must exist.

or

3. with the DBD Library name and a DBD member name and also the Segment (Record)
Layout File name with a member name, if it is a PDS. The Segment Layout File must exist.
Relationship Facilitator 141

Specify Parent File for Relationship Definition Area

Use the fields in this area to specify the MVS file that is the parent in the new relationship. When
specifying patterns in the fields, File-AID/RDX presents selection lists.

If the file is already involved in another relationship definition, you must use
the same layout, if usage=S, or use the same XREF file to add a new
relationship.

File name
Specify the MVS file name of the parent in the new relationship. To view a list of files, specify a
pattern. Valid pattern character is * (see Pattern Characters on page 27).

Record layout usage

Indicate whether a single record layout (usage “S”), or an XREF (usage “X”) is to be used to define
the selection criteria.
You must also supply a Record Layout file and either a layout member (Usage=S) or an XREF file
and member (Usage=X).

Record layout file

Specify the record layout file for the MVS object that is to be the parent in the new relationship.
To view a list of layout files, specify a pattern. Valid pattern character is * (see Pattern Characters
on page 27).

Member name
Specify the member of the record layout file that contains the layout information for the MVS
file. Leave blank or use a pattern to select a member from a list.

XREF file name

Only needed if layout usage is X. Specify the XREF file name for the MVS file that is to be the
parent in the new relationship. To view a list of XREF files, specify a pattern. Valid pattern
character is * (see Pattern Characters on page 27).

Member name
Specify the member of the XREF file that contains the layout information for the parent MVS file.
Leave blank or use a pattern to select a member from a list.

I/O Exit Name

Specify the I/O Exit Name for the parent MVS file.

You only need to fill in this field when you want File-AID/RDX to use an I/O exit routine when
accessing the above MVS file. Not needed to search the relationship file.
142 File-AID/RDX Reference

Specify Method to Define Output Key File Relationship Area

Method
Specify which method to use for your Output Key file:

1 MVS Record Layout. Select method 1 when you have a File-AID record layout describing
either the IMS segment or MVS record layout of the dependent object for which you
want to create an Output Key File during an extract.
2 IMS DBD. Select method 2 when you have an IMS DBD library for which you want to
establish a relationship with the parent Db2 table and for which you want to create the
Output Key File during an extract.
3 Both. Select method 3 when you have a File-AID record layout describing either the IMS
segment and an IMS DBD library for which you want to create an Output Key File during
an extract.

Specify IMS/Output Key File Definition Area

Use the fields in this area to specify the record layout and/or IMS database that is the dependent in
the new relationship. When specifying patterns in the fields, File-AID/RDX presents selection lists.

Record Layout File

Specify the record layout file that describes the record layout or IMS segment layout for which
you want to establish a relationship with the parent Db2 table.

Member Name
Specify the member of the record layout or IMS segment layout file for which you want to
establish a relationship. If you leave this field blank or enter a pattern other than an asterisk (*),
File-AID/RDX displays a Member List window containing a list of members that match the
specified pattern.

DBD Library
Specify the IMS DBD library for which you want to establish a relationship with the parent Db2
table.

Member
Specify the member of the DBD library for which you want to establish a relationship. If you
leave this field blank or enter a pattern other than an asterisk (*), File-AID/RDX displays a
Member List window containing a list of members that match the specified pattern.
Relationship Facilitator 143

Suggest Relationships when field name/type/length are identical Area

Suggest
Specify whether you want File-AID/RDX to select relationships when field and root segment
name, type, and length in the parent and dependent objects are identical.

Y Yes, File-AID/RDX will select columns and fields with identical names, type and length
for this relationship definition and present them in the following Column/Field
Relationships Screen (see Figure 54 on page 144). A message will inform you how
many relationships have been suggested. You can then accept them or delete
individual relationship definitions and/or add your own definitions.
N No. File-AID/RDX will not suggest any application relationships when entering the
following Column/Field Relationships Screen (see Figure 54 on page 144).

When parent and dependent objects are the same object, File-AID/RDX will bypass the
automatic suggest functions as all fields would be suggested. You can still issue the SUGGEST
primary command in the Field Relationships screen. Remember, File-AID/RDX only allows up
to 20 Field relationship definitions.

Relationship Description Area

Description
Enter a description up to 128 characters in length of the application relationship to be created.
This information is displayed in the Relationship Information screen.

After specifying all required parent and dependent information, press Enter. You then continue
with the Field or Field/Segment Relationship screen to define the related MVS fields and IMS root
segment, see Relationships on page 144.
144 File-AID/RDX Reference

Relationships
The Relationships screen shown in Figure 54 is displayed after you

• specified the related objects in the Add Relationship screen.

• used the S (Select) line command on the Application Relationship Detail screen.

The screen title varies depending on the object types involved.

Table 7 shows the possible title combinations.

Table 7. Relationship Titles

Object Type Parent Object Type Dependent Title
DB2 DB2 Column Relationships
DB2 MVS Column/Field Relationships
Column/Segment Relationships 
DB2 KEY or
Column/Field Relationships if record/segment layout is used
MVS MVS Field Relationships
MVS DB2 Field/Column Relationships
Field/Segment Relationships 
MVS KEY or
Field Relationships if record/segment layout is used

Figure 54. Relationships Screen - Column Relationships not yet defined

File-AID/RDX ------------- Column Relationships ----------------------------

Command ===> SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Column Number to Define Relationship D = Delete Relationship 

Parent: DB2-LOCATION.TSOID01.EMP
Dependent: DB2-LOCATION.TSOID01.ORDKFL
CMD Parent Columns Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
____ EMPNO CHAR(6)
____ FIRSTNME VCHAR(12)
____ MIDINIT CHAR(1)
____ LASTNAME VCHAR(15)
____ WORKDEPT CHAR(3)
____ PHONENO CHAR(4)
____ HIREDATE DATE
NMBR Dependent Columns Type(Length)
---- ------------------------------- ------------
1 ORDER_NUMBER CHAR(6)
2 CUST_NUM CHAR(6)
3 ORD_TYPE CHAR(8)
4 ORD_DATE DATE
5 ORD_STAT CHAR(8)
6 ORD_AMOUNT DEC(9,2)

Figure 54 shows the Relationships screen as it appears when adding a DB2 to DB2 application
relationship, before any column relationships have been defined or suggested.

The Relationships screen shown in Figure 55 on page 145 is displayed when maintaining an MVS to
MVS application relationship, with field relationships already defined.
Relationship Facilitator 145

Figure 55. Relationships Screen — Field Relationships already defined

File-AID/RDX ------------- Field Relationships ----------------------------

Command ===> SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships, CANcel
Line Commands: Field Number to Define Relationship D = Delete Relationship 

Parent: MVS-TSOID01.FARDX2.SAMP.SALEHIST 
Dependent: MVS-TSOID01.FARDX2.SAMP.ZIPCODE
CMD Parent fields Type(Length) Mapped fields
---- ------------------------------- ------------ -----------------------------
____ FILLER CHAR(15) 6(1,11,1)
____ SH-DATE-SHIP CHAR(8) 3(1,4,1)
- - - - - - - - - End of Related Columns - - - - - - - - -
____ SH-CUST-NO CHAR(6)
____ SH-ORD-NO CHAR(6)
____ SH-ORD_TYPE CHAR(8)
____ SH-DATE-SHIP CHAR(8)
____ SH-SHIP-CUST-NO CHAR(6)
NMBR Dependent fields Type(Length)
---- ------------------------------- ------------
1 ZM-BASE-ZIP CHAR(5)
2 ZM-ZIP-SUF CHAR(4)
3 ZM-TIME-DIFF DEC(2,0)

Figure 55 shows the Relationships screen as it appears when modifying an MVS to MVS application
relationship. Notice that the titles now include the MVS naming convention where Parent Fields and
Dependent Fields are used in place of Db2 columns. Also, the Parent Portion of the screen includes
another scrollable area — Relationships — that lists the defined relationships.

The Relationships screen shown in Figure 56 is displayed when maintaining an MVS to DB2
application relationship, with Unicode data types and field/column relationships already defined.

Figure 56. Relationships Screen — with Unicode data

File-AID/RDX -------- Field/Column Relationships ---------------------------

-
Command ===> SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships, CANcel
Line Commands: Column Number to Define Relationship D = Delete Relationship

Parent: MVS-TSOID01.FASAMP.EMPLOYU2 
Dependent: DB2-LOCATION.TSOID01.UNI_CUSTOMER_TABLE
CMD Parent fields Type(Length) Mapped fields
---- ------------------------------- ------------ -----------------------------
____ 24/OUT-POSTAL-CODE N(5) U16 15(1,5,1)/CONTACT_ZIP
- - - - - - - - - End of Related Columns - - - - - - - - - 
____ OUT-STREET-ADDRESS N(25) U16 
____ FILLER N(1) U16 
____ OUT-CITY N(15) U16 
____ OUT-STATE N(2) U16 
____ FILLER N(2) U16 
NMBR Dependent Columns Type(Length) 
---- ------------------------------- ------------ 
14 CONTACT_STATE CH(2) U-8 
15 CONTACT_ZIP CH(9) U-8 
16 CONTACT_COUNTRY CH(10) U-8 
17 CONTACT_AREA_CD CH(3) U-8 
18 CONTACT_TELEPHONE CH(7) U-8 

Use the relationship screen to create or update the column or field level relationship detail for the
related objects in the relationship file. See Building Column/Field Relationships on page 167 for more
information about how to use the Relationships screen.

The body of the Relationships screen consists of two portions: a parent portion and a dependent
portion. The parent portion includes two scrollable areas, Defined Relationships and Parent
Columns/Fields. When the parent and dependent portions contain more information than can be
146 File-AID/RDX Reference

displayed at one time, use the scroll commands to scroll through the data. Each area can also be
scrolled individually with scroll mode CSR: move the cursor into the area you want to scroll and use
the UP or DOWN scroll commands.

Object Names
The top portion of this screen displays the object names for the relationship:

Parent
Displays the full name of the parent object preceded by the object type. For example, Db2 tables
are identified in the form 
location.creator.table.

Dependent
Displays the full name of the dependent object preceded by the object type. For example,

– Db2 tables are identified in the form

DB2-location.creator.table.

– MVS files are identified in the form

MVS-hlq.dataset(member).

– IMS root segments are identified in the form

KEY-hlq.DBD library dataset(member).

– IMS segment layouts are identified in the form

KEY-hlq.segment layout dataset(member).

– Output Key File layouts are identified in the form

KEY-hlq.record layout dataset(member).

Parent Portion
The Parent portion of this screen represents the parent information for the relationship.

If relationships have already been defined, the Parent portion is divided into two scrollable areas by a
dashed line, for example

- - - - - - - - - End of Related Columns - - - - - - - - -

The part above the dashed line contains the names of the columns/fields participating in the
application relationship with the Mapped Fields values filled in. The part below the dashed line
contains the names of all of the columns/fields for the parent.

CMD
Enter line commands in this column. See Line Commands on page 107 for information about
valid commands. This column displays the ERR> flag when you select an existing relationship
from the Application Relationship Detail screen in the following situations:

– When File-AID/RDX cannot find a column or field that is defined as part of an application
relationship. You should delete such a relationship before you exit from this screen.
Relationship Facilitator 147

– When there is a conflict between column information stored in the relationship file and
column information stored in the Db2 catalog table, SYSIBM.SYSCOLS.

Parent Columns or Parent Fields

Displays the names of the columns in the Db2 parent table, or, if the parent is an MVS file,
displays the names of the fields. If the field contains an occurrence of subscripts, the element
notation follows in parentheses.

Type(Length)
Displays the parent column’s or parent field’s data type. The length of the data is displayed in
parentheses immediately following the data type for CHAR, CH, VCHAR, VC, GRPH, VGRPH,
DEC, FIXPIC, National data types only.

Unicode Db2 character data types are identified as CH(x), VC(x) or LV(x) with a suffix of U16 or
U-8. Unicode character data from an MVS file is identified as N(x) U-16. See Figure 56 for a
sample screen.

See Table 8 for more information about data types displayed in this column.

1. If a Db2 column is a distinct type (UDT) File-AID/RDX displays the built-

in column type only.
2. Column types CLOB, BLOB, DBCLOB, ROWID, VARBINARY, or XML
cannot be part of an application relationship.

Table 8. Data Type Values

Data Type Value
CHAR or CH Fixed-length character strings less than or equal to 254 characters.
VCHAR or VC Variable-length character strings less than or equal to the field length specified when the column
is created. Maximum allowable field length is 4056 characters for 4k pages and 32,714 characters
for 32k pages.
LVCHAR or LV Variable-length character strings less than or equal to 4056 characters for 4k pages and 32,714
characters for 32k pages.
GRPH Fixed-length graphic strings less than or equal to 127 characters.
VGRPH Variable-length graphic strings less than or equal to the field length specified when the column is
created. Maximum allowable field length is 2028 characters for 4k pages and 16,357 characters
for 32k pages.
LVGRPH Variable-length graphic strings less than or equal to 2028 characters for 4k pages and 16,357
characters for 32k pages.
SMALLINT Fixed-length, binary integers in the range of -32,768 to +32,767, requiring two bytes of storage.
INTEGER Fixed-length, binary integers in the range of -2,146,483,648 to +2,147,483,467, requiring four
bytes of storage.
BIGINT Fixed-length, binary integers in the range of -9223372036854775808 to
9223372036854775807, requiring eight bytes of storage.
DEC Fixed-length, decimal numbers in the range of -10E15 to +10E15.
DECFLOAT Decimal Floating Point can be either DECFLOAT(16) or DECFLOAT(34) representing either 16 or
34 significant digits. The range of a DECFLOAT(16) number is 10-383 to 10+384 and the range of
a DECFLOAT(34) number is 10-6143 to 10+6144. A DECFLOAT(16) field occupies 8 bytes and a
DECFLOAT(34) occupies 16 bytes.
148 File-AID/RDX Reference

Table 8. Data Type Values (Continued)

Data Type Value
REAL Fixed-length, single-precision, floating-point numbers in the approximate range of 5.4E-79 to
7.2E+75.
DOUBLE Fixed-length, double-precision, floating-point numbers in the approximate range of 5.4E-79 to
7.2E+75.
DATE A three-part value (year, month, day) whose format is determined by DB2.
TIME A three-part value (hour, minute, second) whose format is determined by DB2.
TMSTMP(n) TIMESTAMP: A seven-part value (year, month, day, hour, minute, second, and precision) whose
format is YYYY-MM-DD-HH.MM.SS.TTTTTTTTTTTT. The precision value (TTTTTTTTTTTT) is
variable length and has 0 to 12 digits (up to picosecond) with a default of 6 (microsecond).
TMSTMP(n) specifies the scale (length) with n = 0 through 12. For DB2 Versions prior to Version
10, the length is always 6.
TMESTZ(n) TIMESTAMP WITH TIME ZONE: An eight-part value (year, month, day, hour, minute, second,
precision, time zone) whose format is YYYY-MM-DD-HH.MM.SS.TTTTTTTTTTTT±HH:MM. The
precision value (TTTTTTTTTTTT) is variable length and has 0 to 12 digits (up to picosecond) with
a default of 6 (microsecond). The time zone is the difference in hours and minutes between local
time and UTC. The range of the hour offset is -12 to +14, and the minute offset is 00 to 59. The
time zone is specified in the format ±th.tm, with values ranging from -12.59 to +14.00. TMESTZ(n)
specifies the scale (length) with n = 0 through 12. DB2 Version 10 and higher only.
CLOB A character large object (CLOB) is a varying-length string with a maximum length of 2 147 483
647 bytes (2 gigabytes minus 1 byte).
DBCLOB A double-byte character large object (DBCLOB) is a varying-length string with a maximum length
of 1 073 741 823 double-byte characters.
XML A data type for storage of well formed XML documents.
BLOB A binary large object (BLOB) is a varying-length string with a maximum length of 2 147 483 647
bytes (2 gigabytes minus 1 byte).
BINARY BINARY is a fixed length binary string which extends the support for binary strings beyond BLOBs.
Length attribute must between 1 and 255 inclusive.
VARBINARY VARBINARY is a variable length binary string which extends the support for binary strings beyond
BLOBs. Length attribute must between 1 and 32704.
ROWID Row identifier. A value that uniquely identifies a row. If a table contains a large object it must also
have a ROWID column.
HEXADEC Fixed length string, supported as a string only.
FLTPIC Fixed length character string representing a floating point value.
FIXPIC Fixed length character string representing a decimal or integer value.
N (National) Unicode data from an MVS file in COBOL is identified as PIC N or USAGE NATIONAL. This is UTF-
16, CCSID=1200. Identified as N(x) U-16.

Table 9 identifies the allowable column/field type mapping when building a column relationship.

Table 9. Column/Field Types Mapping

LVCHARor LV
VCHAR or VC
CHAR or CH

TO 
SMALLINT

DECFLOAT

HEXADEC
TMSTMP
TIMESTZ
INTEGER

National
DOUBLE
LVGRPH

BINARY
VGRPH

BIGINT

FLTPIC
FIXPIC
GRPH

DATE

FROM
TIME
REAL
DEC


CHAR or CH X X X X X X X X X X X X X X X X X
VCHAR or
X X X X X X X X X X X X X X X
VC
Relationship Facilitator 149

Table 9. Column/Field Types Mapping (Continued)

LVCHARor LV
VCHAR or VC
CHAR or CH
TO 

SMALLINT

DECFLOAT

HEXADEC
TMSTMP
TIMESTZ
INTEGER

National
DOUBLE
LVGRPH

BINARY
VGRPH

BIGINT

FLTPIC
FIXPIC
GRPH

DATE
FROM

TIME
REAL
DEC

LVCHAR or
X X X X X X X X X X X X X X X
LV
GRPH X
VGRPH X
LVGRPH X
SMALLINT X X X X X X X X X
INTEGER X X X X X X X X X
BIGINT X X X X X X X
DEC X X X X X X X X X
REAL X X X X X X
DOUBLE X X X X X X
DECFLOAT X X X X
DATE X X X X
TIME X X X X
TMSTMP X X X X X
TMESTZ X X X X X
BINARY X
HEXADEC X X X X
FLTPIC X
FIXPIC X X X X X X X X X
N (National) X X X X X X X X X X X X

Mapped Fields
Displays a value only for already defined relationships in the Parent portion. It lists

– the column/field number of the dependent column/field,

– the extended column information in parentheses (parent start position, length, dependent
start position, length) where applicable
– the dependent column/field name.

* AR Conditional *
The Mapped Fields heading is replaced with the * AR Conditional * heading after you have
defined a conditional application relationship with the COND command. The column displays a
value only for already defined relationships in the Parent portion. It lists the same information as
the Mapped Fields column:

– the column/field number of the dependent column/field,

– the extended column information in parentheses (parent start position, length, dependent
start position, length) where applicable
150 File-AID/RDX Reference

– the dependent column/field name.

Dependent Portion:
The Dependent portion of the Relationships screen contains the following information:

NMBR
Displays File-AID/RDX-generated sequence numbers that indicate the dependent
column/field/segment numbers to be used as input in the above parent CMD field to establish a
new relationship. This number also correlates to the dependent column/field/segment number in
the Mapped Fields values for defined relationships.

Dependent Columns/Fields/Root Segment

Displays the names of the Db2 columns, MVS layout fields, IMS root segment, or KEY File layout
fields in the dependent object. If an MVS field contains an occurrence of subscripts, the element
notations follows in parenthesis.

Type(Length)
Displays the dependent column’s or field’s data type. The length of the data is displayed in
parenthesis immediately following the data type for CHAR, CH, VCHAR, VC, GRPH, VGRPH,
DEC, FIXPIC, National data types only.

Unicode Db2 character data types are identified as CH(x), VC(x) or LV(x) with a suffix of U16 or
U-8. Unicode character data from an MVS file is identified as N(x) U-16. See Figure 56 for a
sample screen.

See Table 8 on page 147 for more information about data types displayed in this column. Table 9
identifies the allowable column/field type mapping when building a column relationship.

1. If a Db2 column is a distinct type (UDT) File-AID/RDX displays the built-in column
type only.
2. Column types CLOB, BLOB, DBCLOB, ROWID, VARBINARY, or XML cannot be part of
an application relationship.
3. BINARY columns in the parent and dependent objects must have the same length.

Line Commands
The following File-AID/RDX-specific line commands are valid on the Relationships screen:

number
Establishes an application relationship (AR) between a parent column/field and a dependent
column/field/root segment.

The panel names the number line command according to the object type of the dependent:

Column-Number when the dependent is a Db2 table.

Field-Number when the dependent is an MVS file or IMS segment layout.
Root Segment-Number when the dependent is an IMS database.
Relationship Facilitator 151

Enter a File-AID/RDX-generated column/field/segment number (listed in the dependent NMBR

column) in the parent CMD column next to the parent column/field for which you want to
establish a relationship.

For example, in Figure 65 on page 167 a Field-Number line command (1) has been entered to
relate the dependent field, SH-CUST-NUM to the parent column, CUSTOMER_NUMBER. When
you press Enter, the new relationship is established and the Column/Field Relationships screen is
redisplayed with the new relationship above the dashed line as shown in Figure 67 on page 168.

D (Delete)
Enter D in the CMD column to remove an existing column/field relationship from the
application relationship.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on the Relationships screen:

CANCEL (CAN)
Quits the Relationship Definition without saving any changes.

COND
Displays the Relationship Condition Definition panel where you can define a conditional test for
the current application relationship (AR). You must have already established a relationship
(mapped columns/fields) before you can issue the COND command.

SUGGEST (SUG)
Enter this command and File-AID/RDX will suggest a relationship when the parent and
dependent column or field name, type and length are identical. Same as if you had entered the
column or field number(s) manually for all identical column or field matches. You only need to
enter the SUGGEST command when you didn’t enable it in the previous “Add Relationships
Screen” or when you want File-AID/RDX to suggest matching pairs again.

Use the D line command to delete any suggested relationships you don’t want included. Use the
CANCEL primary command to abort the relationship definition.

Relationship Condition Definition

When you enter the COND primary command in the Column/Field Relationship screen, File-
AID/RDX displays the Selection Criteria Menu screen (see Figure 57 on page 152).

From this panel you can define the conditions (selection criteria) under which the defined AR will be
processed during extract execution. You always specify the test condition on the parent object of the
relationship. The process to define the Relationship Condition is similar to defining extract selection
criteria for MVS objects (see also MVS File Selection Criteria).

The Formatted Selection Criteria Screen includes the parent object’s column or field name, data
format, a relational operator, and data value field. The data format is displayed in MVS format
terminology for both MVS and Db2 objects.

Multiple criteria sets can be defined within the definition of a condition. As with other criteria,
conditions within the same set are treated as AND conditions and between sets are OR conditions.
152 File-AID/RDX Reference

The Relationship Condition will be saved as part of the application relationship in the Relationship
file and its associated Conditional AR Criteria file. The relationship type AR-C identifies that the
relationship includes selection criteria.

Selection Criteria Menu

The Selection Criteria Menu, shown in Figure 57, provides access to the selection criteria options and
formatted selection criteria specification.

Figure 57. Selection Criteria Menu

File-AID/RDX - Selection Criteria Menu - TEMPORARY ----------------------------

Option ===>
- Status -
1 OPTIONS - Enter selection criteria options default
2 FORMATTED - Edit formatted selection criteria 0 sets 






Use VIEW to display selection criteria summary
Use END to save selection criteria & return to Object Selection Criteria
Use CANCEL to cancel changes & return to Object Selection Criteria

The Selection Criteria screen contains the following fields

Option
Enter one of the following valid options:

1 Selection criteria options allow you to specify a particular starting point in the file and set
limits on the number of records processed. See Selection Criteria Options on page 153.
2 Create and edit formatted selection criteria, which allows you to select records based on
data within a field specified by a record layout. See Formatted Selection Criteria Screen on
page 157.

Status
Specifies the status of the temporary selection criteria:

OPTIONS
Reports whether the default options have been modified. Valid values are DEFAULT or NOT
DEFAULT.

FORMATTED
Specifies the number of sets of criteria that are specified. A set of selection criteria is defined
as a single expression that can lead to the selection of a record. A set may test for one
Relationship Facilitator 153

condition or several conditions. The conditions can be ANDed together and several
conditions separated by commas create nested OR conditions within a set.

Primary Commands
The following primary commands are valid on the Selection Criteria Menu:

CANCEL
Returns to the Relationships Screen — Field Relationships already defined and clears all selection
fields.

END
Saves the current selection criteria and exits the Selection Criteria Menu. The “Relationships
Screen” will display the * AR Conditional * status to identify that this application relationship
now includes conditional criteria.

VIEW
Displays the View Criteria screen, which summarizes the options and formatted selection criteria
sets into a scrollable display. See View Criteria.

View Criteria
The View Criteria screen, shown in Figure 58, summarizes the current selection criteria. It displays
selection criteria option settings and formatted selection criteria sets on a scrollable display. Use the
VIEW primary command on any selection criteria screen to display this screen. Use the END
command (PF3) to return to the previous screen.

Figure 58. View Criteria Screen

File-AID/RDX -------------------- View Criteria ----------- Row 1 to 20 of 35

Command ===> SCROLL ===> CSR
Use END to exit View Display 

******************************* TOP OF CRITERIA *****************************
DEFINE BLOCKS=SELECTION, 

DESCRIPTION1="Selection Criteria for Data Driven AR",

LAYOUT_DSNAME=, 
LAYOUT_MBRNAME=, 

INITIAL_SKIP=0, 
THEN_SELECT=1, 
THEN_SKIP=0, 

MAXIMUM_TO_SEARCH=ALL, 
MAXIMUM_TO_SELECT=ALL 

SELECT SET=1,LAYOUT=CUSTOMER_TABLE-TBL 
IF 
FIELD_NAME=CUSTOMER_NUMBER, 
POSITION=17,LENGTH=6,OPERATOR=LT, 
TYPE=T,VALUE=777777

Selection Criteria Options

The Selection Criteria Options screen, shown in Figure 59 on page 154, enables you to control record
selection based on starting record key, RBA, or RRN or record counts which determine how selection
154 File-AID/RDX Reference

processing is executed and when it stops. File-AID/RDX determines whether an individual parameter
is valid based on the access method of the processed file. For instance, File-AID/RDX allows you to
specify the processing direction when selecting records from a sequential or VSAM file.

Enter option 1 on the Selection Criteria Menu to display the Selection Criteria Options screen.
Selection criteria options can be combined with formatted selection criteria. If any formatted
selection criteria exist, they are applied after a record passes the selection criteria options selection
process.

Figure 59. Selection Criteria Options

File-AID/RDX ---------- Selection Criteria Options --------------------------

Command ===> 

Specify Selection Criteria Options:
Start at the following record key
(both blank for start of dataset)
Starting record key ===>
- OR - OR at the following RBA or RRN
Starting RBA or RRN ===> 

Initial records to skip ===> 0 then skip this many records 

Subsequent Selection Interval: then repeat the following
Records to select ===> 1 - select this many records
Records to skip ===> 0 - then skip this many records
until
Number of records to search ===> ALL you have read this many records 


SEQ/VSAM processing direction ===> F (F = Forward; B = Backward) 


Use ENTER to return to selection criteria menu

Specify Selection Criteria Options:

The Starting record key field and Starting RBA or RNN field are exclusive of each other.

Starting record key

Specify a generic or specific record key in a character or hexadecimal data format. This field
allows you to specify a random starting point for record selection in a VSAM KSDS file. Records
before the starting record key are not selected, regardless of matching formatted selection criteria.

To specify a hexadecimal record key, enter the value enclosed in single quotation marks ( ’ ) and
precede the quoted value with the letter X. For example, X’03E2’.

Starting RBA or RRN

Specify a generic or specific relative byte address (RBA) or relative record number (RRN).

This field allows you to specify a random starting point for record selection in a VSAM or BDAM
file. Records before the specified starting RBA or RRN are not selected, regardless of matching
formatted selection criteria.

For VSAM KSDS and VSAM ESDS files, enter a specific relative byte address. RBAs must be on a
record boundary. To specify a hexadecimal RBA, enter the value enclosed in single quotation
marks (’) and precede the quoted value with the letter X.

For VSAM RRDS or BDAM files, a relative record number (RRN) can be specified.
Relationship Facilitator 155

Initial records to skip

Specify a number of records for File-AID/RDX to skip before processing the file. Possible values
are any number from 0 (zero) through 999999. Use the 0 (zero) value to process all records.

Subsequent Selection Interval:

The values in the Records to select and Records to skip fields determine the record selection pattern
that File-AID/RDX uses to select records from a file until the value in the Number of records to search
or the Number of records to select field is reached.

Records to select
Specify the number of records for File-AID/RDX to retrieve from the file at a time. Possible values
are any number from 1 (one) through 999999. Selection criteria is applied after the record has
been retrieved. The default is 1 (one).

Records to skip
Specify the number of records for File-AID/RDX to skip after fulfilling the Records to select
parameter when processing the file. Possible values are any number from 0 (zero) through
999999. Use the 0 (zero) value for File-AID/RDX to process all remaining records. All skipped
records are not selected, regardless of the selection criteria specified.

Number of records to search

Specify a limit for the number of records File-AID/RDX reads and checks for matches to selection
criteria. The default for this parameter is ALL. Possible values are any number from 0 (zero)
through 999999. Use the 0 (zero) or ALL value to search the entire file.

This parameter can prevent excessive I/O processing when searching large files. If the file is
processed randomly (a KEY or RBA have been entered), this count begins with the first record
retrieved randomly.

SEQ/VSAM processing direction

Specify a processing direction for File-AID/RDX to read Sequential or VSAM files. Possible values
are F (forward) and B (backward). The default is F (forward).

This field specifies whether File-AID/RDX starts reading a Sequential or VSAM file at the
beginning or the end. File-AID/RDX ignores the B value in this field when used with files of other
access methods.

Figure 60 shows an example of the effect of selection criteria options.

156 File-AID/RDX Reference

Figure 60. Selection Criteria Options Example


Initial records to skip ===> 4 then skip this many records 

Subsequent Selection Interval: then repeat the following
Records to select ===> 2 - select this many records
Records to skip ===> 3 - then skip this many records
until
Number of records to search ===> 10 you have read this many records


Selected/Not Selected Records in the file
NS Record 1
NS 2
NS 3
NS 4
S Select 2 5 <=== Starting Record Number
S 6
NS Skip 3 7
NS 8
NS 9
S Select 2 10
S 11
NS Skip 3 12
NS 13
NS 14
S Select 2 15
S 16
NS Skip 3 17
NS 18
NS 19
S Select 2 20
S 21
NS Skip 3 22
NS 23
NS 24
S Select 2 25
S 26 <=== 10th Record Searched
NS 27
NS 28
NS 29
NS Not Searched 30
NS Because Limit 31
NS Has Been Reached 32
NS 33
NS 34
NS 35

When the values shown in Figure 61 are entered in the selection criteria options fields, all records in
the file pass this portion of the selection process and are processed by any specified formatted
selection criteria.

Figure 61. Selection Criteria Options Example. Default - Examines All Records

Initial records to skip ===> 0 then skip this many records 

Subsequent Selection Interval then repeat the following
Records to select ===> 1 - select this many records
Records to skip ===> 0 - then skip this many records
until
Number of records to search ===> ALL you have read this many records
Relationship Facilitator 157

Formatted Selection Criteria

The Formatted Selection Criteria screen, shown in Figure 62, allows you to specify selection of records
based on field values displayed with a record layout.

Select option 2 on the Selection Criteria Menu to display the Formatted Selection Criteria screen. If
you did not specify a record layout or XREF file prior to selecting option 2, File-AID/RDX displays the
Record Layout Specification screen, shown in Figure 62, for entry of the required information.

Figure 62. Formatted Selection Criteria Screen

File-AID/RDX --- Formatted Selection Criteria ---------------------------------

Command ===> SCROLL ===> CSR
CRITERIA NUMBER: 1 OF 1 EMPLOYEE-MASTER-FILE GBL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----+----1----+----2----+----3----+-
******************************* TOP OF DATA ********************************
5 EMP-NUMBER 5/AN
5 EMP-LAST-NAME 15/AN
5 EMP-FIRST-NAME 10/AN
5 EMP-MID-INIT 1/AN
5 FILLER 2/AN
5 EMP-TITLE 30/AN
5 EMP-PERSONAL-INFO SYNC 23/GRP
10 EMP-NATL-ID-NUMBER 9/NUM
10 FILLER 1/AN
10 EMP-DATE-OF-BIRTH 6/AN
10 EMP-DOB-REDEF REDEFINES EMP-DATE-OF-BIRTH
10 EMP-DOB-REDEF SYNC 6/GRP
15 EMP-DOB-MM 2/NUM
15 EMP-DOB-DD 2/NUM
15 EMP-DOB-YY 2/NUM
10 EMP-HIRE-DATE 6/AN
10 EMP-MARITAL-STATUS 1/AN
5 EMP-WITHOLD-INFO SYNC 15/GRP
10 EMP-LIFE-INS-WITHOLD-AMT 6/SNUM

The input fields in this screen are:

RO
Specify a relational operator. Possible values are:

EQ, = Equal to
NE, ¬ =, != Not equal to
GT, > Greater than
GE, > = Greater than or equal to
LT, < Less than
LE, < = Less than or equal to
CO Contains; scans the specified field for the presence of a data value. CO works on an
equal condition.
NC Not contains; scans the specified field for the absence of a data value. NC works on
a not equal condition.
BT Between; within a range of two values (endpoints inclusive). The value is greater than
or equal to the first endpoint and less than or equal to the last endpoint.
NB Not between; outside a range of two values (endpoints exclusive). The value is less
than the first endpoint or greater than the last endpoint.
VA Valid numeric or packed data based on the field format.
NV Not valid numeric or packed data based on the field format.
158 File-AID/RDX Reference

NO Bits are not ones (Mask data value only).

MX Bits are mixed, ones and zeros (Mask data value only).
FM Field mask. See Field Mask on page 165 for more information.

1. The CO and NC relational operators can be specified only for

alphanumeric fields (PIC X for COBOL; CHAR or PIC X for PL/I).
2. File-AID/RDX does not currently support selection criteria that use bit
or numeric fields that specify a leading and/or separate sign.

data value
For fields with relational operators other than BT and NB, you specify the field value to use in the
comparison. For relational operators BT and NB, specify your Data Value as two values separated
by a colon (:). The values may be hex strings, character strings, or numeric tests.

To compare an alphanumeric field to blanks (hexadecimal 40s), leave the data value column
blank.

Guidelines
To specify a formatted selection criterion, enter the relational operator and data value beside a field
on which you want to base the record selection. Leave the relational operator blank for fields not
involved in the selection criteria. Use the INPUT, INSERT, or REPEAT primary command to specify
multiple sets of formatted selection criteria. Add the keyword AND to those primary commands to
add an ANDed subset to the current criteria set.

In theory, you can create any number of sets of selection criteria. However, the actual number is
limited by available storage. Storage is primarily affected by the number of relational operators used
and the size of the fields being referenced. The number of ANDed subsets is limited to 255 for any
one set.

Multiple fields for a single criterion test are logically ANDed together, multiple AND subsets are
ANDed together, and multiple sets of criteria tests are logically ORed together.

Each ANDed Subset is processed as a part of the preceding Set as a group of conditions. An OR Set
represents a new group of conditions. Consider the following Sets:

SET 1
OR SET 2.1 (Subset 1 of Set 2)
AND SET 2.2 (Subset 2 of Set 2)
OR SET 3

This criteria will be processed as (SET 1) OR (SET 2.1 AND SET 2.2) OR SET 3.

Multiple data entries can be specified for one field by separating each entry with a comma. The
comma is interpreted as an OR expression. You can specify multiple data values for one field on one
selection screen. For example: RECORD-CODE EQ A,B,C is interpreted as the RECORD-CODE field
must be equal to A or B or C.

The syntax of the search data is important since File-AID/RDX interprets a comma as an OR
expression. In order to search for a comma as data, enclose the comma in double quotes (",").

For relational operators BT and NB, enter two values separated by a colon (for example, BT -
100:+100). In most cases, you will have sufficient space to enter the two values.
Relationship Facilitator 159

You can select records with an invalid field value by entering the NV relational operator. Records with
a valid field value can be selected by entering the VA relational operator. The VA and NV operators
can be used for packed decimal, and zoned decimal fields.

Relational operators CO and NC can be used to scan a field within each record for the presence or
absence of a particular value. The value for which you want to search is entered in the data value
column. Trailing blanks in the data value are ignored and not included in the search string. The CAPS
primary command controls whether File-AID/RDX does a case-sensitive search. When you enter CAPS
OFF, only text exactly matching the upper and lowercase characters is found (for example, SMITH
and Smith are different values). When you enter CAPS ON, File-AID/RDX treats upper, lower, and
mixed-case characters the same and matches any case combination of the specified characters.

Japanese DBCS Data

DBCS data is accepted as selection criteria data values for alphanumeric fields. For the relational
operators CO (contains) and NC (not contains), File-AID/RDX removes any leading or trailing shift
characters unless the value is enclosed in double quotes.

Sample Selection Sets

Figure 63. Formatted Selection Criteria Examples

File-AID/RDX --- Formatted Selection Criteria ---------------------------------

Command ===> SCROLL ===> CSR
CRITERIA NUMBER: 1 OF 2 EXAMPLE-FILE LAYOUT LENGTH: 3
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----+----1----+----2----+----3----+-
******************************* TOP OF DATA ********************************
5 FIELD-ONE 1/AN = A,B,C
5 FIELD-TWO 1/AN = D
5 FIELD-THREE 1/AN
***************************** BOTTOM OF DATA *******************************

File-AID/RDX --- Formatted Selection Criteria ---------------------------------

Command ===> SCROLL ===> CSR
CRITERIA NUMBER: 2 OF 2 EXAMPLE-FILE LAYOUT LENGTH: 3
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----+----1----+----2----+----3----+-
******************************* TOP OF DATA ********************************
5 FIELD-ONE 1/AN
5 FIELD-TWO 1/AN
5 FIELD-THREE 1/AN = E
***************************** BOTTOM OF DATA *******************************

The formatted conditions specified in Figure 60 translate into the following expression:

If ((A or B or C) and D) or E

which can also be stated as:

If (A and D) or (B and D) or (C and D) or E

Primary Commands
The following is a list of the primary commands that are valid on the Formatted Selection Criteria
screen.

ARRAY (AR)
Controls display of array declaration information for PL/I data.
160 File-AID/RDX Reference

ON

Displays an array definition line for each subscripted item in a record layout.

OFF

Does not display an array definition line.

ALL

Displays all occurrences separately with the subscript(s) and any criteria entered on a specific
occurrence will only be applied to that occurrence. This additional parameter is only valid
during Formatted Selection Criteria creation.

ANY

Displays a single entry for the occurrences and any criteria entered for the ANY occurrence
will be applied to all occurrences. The record will meet the Selection Criteria if any of the
occurrences meet the specified criteria. This additional parameter is only valid during
Formatted Selection Criteria creation. ANY is applied for initial display of Selection Criteria.

When applying 2 or more criteria in the same subset, all have to be true in
the same occurrence to be selected. 
When entered individually in different subsets, they don’t have to be true
in the same occurrence to be selected.

EVERY

Displays a single entry for the occurrences and any criteria entered for the EVERY occurrence
will be applied to all occurrences. The record will meet the Selection Criteria if all of the
occurrences meet the specified criteria. This additional parameter is only valid during
Formatted Selection Criteria creation.

Guidelines
• Use the PROFILE command to display the current ARRAY ON or OFF value. Only ON or
OFF are saved in the profile.

• The array line contains the name of the array followed by the word ARRAY and the
subscript bounds in standard PL/I format. If any of the subscripts are defined by a REFER
clause, additional lines that follow the ARRAY line describe each REFER variable.

• ANY, EVERY and ALL are available only in Formatted Selection Criteria.

• ANY, EVERY or ALL is applied per set or subset if any. Each set or subset may have a
different array setting.

• You cannot switch ANY, EVERY or ALL to another if the criteria is specified on any
occurrence field in a single set or single subset.

• In ANY or EVERY mode, the SHOW OFFSET command shows the offsets of the first
occurrence.

BACK
Positions the display to the previous criteria. Synonym for LEFT.

CANCEL (CAN)
Returns to main panel without saving current updates.
Relationship Facilitator 161

DELETE (DEL, D)
Delete a selection set or subset.

DISPLAY (DIS)
Specifies a display format.

MAXREFER

(for PL/I layouts only) Specify the maximum number of occurences to display. Omission of
the DISPLAY MAXREFER command causes PL/I Refers to default to 1 occurrence.

DOWN
Scrolls down.

END (E)
Terminates display of the Formatted Selection Criteria screen and returns to the Selection Criteria
Menu.

FORWARD (FWD)
Positions the display to the next criteria. Synonym for RIGHT.

INPUT/ INSERT (I)

Inputs/inserts a new formatted selection criteria set.

AND

Inserts an ANDed subset of selection criteria (the set counter displays “AND Set 1.2 of 1”)
after (default) or before the current criteria.

LEFT (L)
Positions the display to the previous criteria. Synonym for BACK.

LOCATE (LOC)
Scrolls directly to the specified record layout line.

OCCURS (OCC)
Controls the display of array declaration items.

ON

Displays an array definition line for each subscripted item in a record layout.

OFF

Does not display an array definition line.

162 File-AID/RDX Reference

ALL

Displays all occurrences separately with the subscript(s) and any criteria entered on a specific
occurrence will only be applied to that occurrence. This additional parameter is only valid
during Formatted Selection Criteria creation.

ANY

Displays a single entry for the occurrences and any criteria entered for the ANY occurrence
will be applied to all occurrences. The record will meet the Selection Criteria if any of the
occurrences meet the specified criteria. This additional parameter is only valid during
Formatted Selection Criteria creation. ANY is applied for initial display of Selection Criteria.

When applying 2 or more criteria in the same subset, all have to be true in
the same occurrence to be selected. 
When entered individually in different subsets, they don’t have to be true
in the same occurrence to be selected.

EVERY

Displays a single entry for the occurrences and any criteria entered for the EVERY occurrence
will be applied to all occurrences. The record will meet the Selection Criteria if all of the
occurrences meet the specified criteria. This additional parameter is only valid during
Formatted Selection Criteria creation.

Guidelines
• Use the PROFILE command to display the current OCCURS ON or OFF value. Only ON or
OFF are saved in the profile.

• The OCCURS line contains the name of the array followed by the word OCCURS and the
subscript bounds in standard COBOL format. If any of the subscripts are defined by a
REFER clause, additional lines that follow the ARRAY line describe each REFER variable.

• ANY, EVERY and ALL are available only in Formatted Selection Criteria.

• ANY, EVERY or ALL is applied per set or subset if any. Each set or subset may have a
different array setting.

• You cannot switch ANY, EVERY or ALL to another if the criteria is specified on any
occurrence field in a single set or single subset.

• In ANY or EVERY mode, the SHOW OFFSET command shows the offsets of the first
occurrence.

PROFILE (PROF)
Displays profile information lines.

REPEAT (R)
Causes a formatted selection criteria set, including any subsets, to be repeated (SET 3 of 3
increments to SET 4 of 4; AND SET 3.2 of 3 increases to AND SET 4.2 of 4).

AND

Repeats an ANDed subset of selection criteria. (the set counter displays “AND Set 1.2 of 1”)
after the current criteria.
Relationship Facilitator 163

RETURN
Returns to the Primary Option Menu.

RIGHT
Positions the display to the next criteria. Synonym for FORWARD.

UP
Scrolls up.

USE
Specifies another record layout for the current formatted selection criteria.

VIEW (V)
Displays the View Criteria screen which is a keyword summary of the current settings for options,
formatted, and unformatted selection criteria. See Figure 58 on page 153.

Selection Criteria Considerations When Data Fields May Be Nonexistent

When defining selection criteria with reference to fields where data might not exist in some records,
File-AID/RDX does not exclude those records from the selection test.

A positive selection operator, such as EQ (equal to), indicates to select the record for processing if the
condition is true.

A negative selection operator, such as NE (not equal to), indicates to select the record for processing if
the condition is false.

Therefore, when using a negative selection operator, File-AID/RDX can select records that don’t have
data in those fields.

A typical case of this is seen with fields that are specified in a record layout with OCCURS
DEPENDING ON. Some records may have several occurrences of the field, while other records may
have only one or none.

For example, consider a record layout called CUSTOMER, having a field called BALANCE defined with
up to 12 occurrences, one per month, depending on another field, called DURATION-OF-ACCOUNT.
The 12th occurrence will not exist for customers who have had accounts with the company for less
than a year.

Example:
Assume you have the following 3 records in your file:

Alice Alvarez has been a customer for 5 months and had monthly balances of 1000, 2000, 3000, 500,
and 0.

Bruce Bandler has been a customer for 3 months and had monthly balances of 1000, 2000, and 3000.

Carlos Cramer has been a customer for 5 months and had monthly balances of 1000, 2000, 3000, 0,
and 0.

The records look like this:

164 File-AID/RDX Reference

Alice Alvarez,05,1000,2000,3000,500,0
Bruce Bandler,03,1000,2000,3000
Carlos Cramer,05,1000,2000,3000,0,0

You specify: Select all records with BALANCE(4) NOT EQUAL TO 500

This is interpreted to mean: Select all records NOT having BALANCE(4) = 500

Records with nonexistent data in occurrence 4 will be included in the selection, and you get these
records:

Bruce Bandler,03,1000,2000,3000
Carlos Cramer,05,1000,2000,3000,0,0

Since Bruce Bandler does not have a balance for month 4, he does not have a balance that equals 500,
and his record is selected as being not equal to 500.

If you want to ensure that only one record is selected, include the the DURATION-OF-ACCOUNT
variable in the selection criteria:

Specify: Select all records with DURATION-OF-ACCOUNT >= 5 AND BALANCE(4) NOT EQUAL TO
500

This would ensure that records with nonexistent data for the fourth occurrence would not be
considered for selection. You would get only one record:

Carlos Cramer,05,1000,2000,3000,0,0

Selection Criteria Considerations: Using GT, LT, and BT with Arrays

For a data item that is not part of an array, specifying BETWEEN (BT) has the effect of selecting all
records where that data item is both Greater Than or Equal to the specified lower bound, AND
simultaneously Less Than or Equal to the specified upper bound. If you specify instead a pair of
conditions, Greater Than (GT) a lower bound, AND Less Than (LT) an upper bound, a data item must
meet both criteria in order to be selected. So for individual data items the effect is similar.

When Selecting data from arrays, the BETWEEN operator behaves the same way as it does for
individual data items. Use the BETWEEN (BT) operator when you want to select only records
containing data items that are simultaneously Greater Than or Equal to a specified lower bound and
Less Than or Equal to a specified upper bound.

However, when selecting data in arrays, do not try to select a set BETWEEN specified bounds by
specifying a combination of GT and LT.

When you specify GT and LT together for an array, you are really selecting two subsets: All records
having data items Less Than (LT) your upper bound AND all records having data items Greater Than
(GT) your lower bound. Generally this will include many more records than the set between the two
bounds.

Examples
Assume you have the following data records, containing an array with 5 occurrences of a 2-byte
numeric field:

Record 1: 05,05,05,05,05
Record 2: 02,04,06,08,10 
Record 3: 11,12,13,14,15

If you specify ANY with values BETWEEN 04 and 06, Records 1 and 2 will be selected.

If you specify ANY with values Greater Than 03 AND Less Than 07, all 3 records will be selected. The
first 2 records have data items with values Less Than 07, and all 3 records have data items with values
Greater Than 03.
Relationship Facilitator 165

Field Mask
The Field Mask Criteria screen, shown in Figure 64, is displayed when you enter the Field Mask (FM)
relational operator in the relational operator (RO) column on any of the File-AID/RDX Selection
Criteria screens.

Figure 64. Field Mask Criteria

File-AID/RDX --- Formatted Selection Criteria ------------------------------------

C Field Mask Criteria 
S 
- Command ===> 
* 
1 Field Name : ORD-TYPE 
Data Type : CHARACTER 
Field Length: 00008 
Mask Length : 008 

A field mask allows selected positions of a field to be processed. 
It always operates on the character representation of the field. 

Identify field positions to process: (Y = include; N = exclude) 
Field Mask: ----+--- 





END to continue 
* 



To ensure accurate Field Mask processing, the Field Mask (FM) relational
operator must be entered prior to entering any other relational operators.

Field Descriptions

Field Name
Name of the selected field as defined by the record layout.

Data Type
Data type of selected field as defined by the record layout.

Field Length
Length of data in selected field as defined by the record layout. This field cannot be overtyped,
when you are on the Field Mask Criteria screen.
166 File-AID/RDX Reference

Mask Length
Length of the mask. This field may be overtyped to shorten or lengthen the length of the data to
be masked. This is particularly useful when you want to mask all the elements of a group item.

You cannot override Mask Length for binary or packed/comp-3 fields.

Identify field positions to process: (Y = include; N = exclude)

Field Mask
A Field Mask enables processing of selected positions or part of a field. It always operates on
character representation of the field. Specify Y or N to include or exclude field positions to be
processed for masking.

Field Mask can be applied to both numeric and character fields.

Each mask position corresponds to a digit in the decimal value of the original field, when
masking numeric fields. The selected digits are passed as a single unsigned numeric display field
for the specified product function.

1. Signs (+,-) are excluded when masking numeric fields.

2. When a Db2 decimal type has an even length (ie, 12,0), the mask length is one
greater than the actual length (ie. 13). Ignore position 1 in the field mask and start
with position 2:

Field Mask: -YY-+----1---

When masking character fields, each mask position corresponds to the identical position in the
original field. The selected positions are passed as a single contiguous character field.

The original format will be replaced by MASK on the Formatted Criteria and Selection criteria
screens, when Field Mask is in effect.

Field masking is not currently supported for bit, floating point, DBCS, or
numeric fields that specify a leading and/or separate sign.

Primary Commands
The following primary commands are valid:

END
Saves the entered field mask parameters.

CANCEL
Discards the entries.
Relationship Facilitator 167

Building Column/Field Relationships

File-AID/RDX enables you to modify the relationship file by modifying existing application
relationships or creating new ones. To modify or create application relationships, you modify or
create column/field relationships on the Relationships screen. An application relationship can consist
of one or more column/field mappings.

The parent and dependent portions of the Relationships screen comprise two lists. These lists contain
names, data types, and lengths of columns or fields from the parent and dependent objects specified
in the preceding screen. Use these lists to build the relationships at the column/field level.

To build application relationships to be used with existing Db2 relationships,

you must be connected to the subsystem for which the existing relationships
are defined. You can specify a subsystem in the SSID field on the Add
Relationships Screen — DB2 to DB2 screen shown in Figure 48 on page 125.

To build column/field relationships:

1. Decide which parent and dependent columns or fields you want to be related. It is likely that
these will be columns or fields that your application recognizes as containing data values that are
used as an index into the corresponding object in the relationship.
2. Enter the number from the dependent NMBR column that corresponds to the dependent
column/field you chose in step 1 in the parent CMD column next to the name of the parent
column/field you chose in step 1. See Figure 65.

Refer to Table 9 on page 148 to see which data types can be paired to establish an application
relation. For other pairings File-AID/RDX displays an error message and will not establish the
relationship.

Figure 65. Relationships Screen — Creating a DB2 to MVS Relationship

File-AID/RDX ------- Column/Field Relationships --------------------------

Command ===> SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Field Number to Define Relationship D = Delete Relationship 

Parent: DB2-LOCATION.TSOID01.CUSTOMER_TABLE
Dependent: MVS-TSOID01.FARDX2.SAMP.SALEHIST
CMD Parent Columns Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
1___ CUSTOMER_NUMBER CHAR(6)
____ COMPANY_NAME CHAR(30)
____ ADDRESS CHAR(30)
____ CITY CHAR(25)
____ STATE CHAR(2)
____ ZIP_CODE CHAR(9)
NMBR Dependent fields Type(Length)
---- ------------------------------- ------------
1 SH-CUST-NO CHAR(6)
2 SH-ORD-NO CHAR(6)

RDXI753 I753 RDX was unable to find parent/child columns with the same name, 
type, and length. 

6 SH-ORD-LINE-NO DEC(5,0)

3. Press Enter.

If one or both parent and dependent fields in an MVS file contain subscripts, File-AID/RDX will
need to know which occurrence of subscript to use for the relationship. In that case, File-
AID/RDX continues with Specify MVS Field Subscripts on page 177.

When partial column mapping is allowed between the parent and dependent columns/fields, the
Extended Column Relationship Definition pop-up window is displayed as shown in Figure 66 on
168 File-AID/RDX Reference

page 168. See Extended Column Relationship Definition on page 169 for more information about
extended column relationships.

Figure 66. Extended Column Relationship Definition Window

File-AID/RDX ------- Column/Field Relationships -------------------------- 

Command ===> SCROLL ===> CSR 
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Field Number to Define Relationship D = Delete Relationship 

Extended Column Relationship Definition 

COMMAND ===> 


Enter Start Position and Length for a partial-column relationship definition. 

Parent Column: Dependent Column: 
Number : 1 Number : 1 
Name : CUSTOMER_NUMBER Name : SH-CUST-NO 
Type(Length): CHAR(6) Type(Length): CHAR(6) 



Start Position ===> 1 Start Position ===> 1 
Length ===> 6 

Enter CANCEL to end without defining the extended column relationship 


If partial column mapping is not applicable for the selected parent to dependent pairing the
relationship is established immediately. File-AID/RDX positions the name of the parent
column/field of the relationship you just created to the end of the list of established column
relationships as shown in Figure 67. Note that the new column relationship is located above the
dashed “End of Related Columns” line. In addition, the Mapped Fields value is filled with the
dependent column/field number that appeared in the NMBR column next to the dependent
column/field as well as any applicable extended column information in parentheses, followed by
the dependent column/field name.

Figure 67. Relationships Screen — New Db2 Column to MVS Field Relationship Established.

File-AID/RDX ------- Column/Field Relationships -------------------------- 

Command ===> SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Field Number to Define Relationship D = Delete Relationship

Parent: DB2-LOCATION.TSOID01.CUSTOMER_TABLE
Dependent: MVS-TSOID01.FARDX2.SAMP.SALEHIST
CMD Parent Columns Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
____ CUSTOMER_NUMBER CHAR(6) 1/SH-CUST-NO
- - - - - - - - - End of Related Columns - - - - - - - - -
____ CUSTOMER_NUMBER CHAR(6)
____ COMPANY_NAME CHAR(30)
____ ADDRESS CHAR(30)
____ CITY CHAR(25)
____ STATE CHAR(2)
____ ZIP_CODE CHAR(9)
NMBR Dependent fields Type(Length)
---- ------------------------------- ------------
1 SH-CUST-NO CHAR(6)
2 SH-ORD-NO CHAR(6)
3 SH-ORD_TYPE CHAR(8)
4 SH-DATE-SHIP CHAR(8)
5 SH-SHIP-CUST-NO CHAR(6)

4. Repeat steps 1-3 for all columns/fields that you want to include in the application relationship for
the pair of objects.
Relationship Facilitator 169

When you exit from this screen, File-AID/RDX writes a new or modified application relationship to
the relationship file. File-AID/RDX redisplays the Application Relationship Detail screen, where the
completed action is indicated in the Status column with the “Added” or “Modified” message.

Extended Column Relationship Definition

The Extended Column Relationship Definition pop-up window shown in Figure 68 is displayed when
you attempt to map two columns/fields containing character (CHAR or VCHAR) or graphic (GRPH or
VGRPH) data, or one column/field containing DECIMAL or FIXPIC and its parent or dependent CHAR
data.

Figure 68. Extended Column Relationship Definition Window

File-AID/RDX ------------- Column Relationships --------------------------

Command ===> SCROLL ===> CSR 
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Column Number to Define Relationship D = Delete Relationship 

Extended Column Relationship Definition 

COMMAND ===> 

Press ENTER without any changes for a full-column relationship. 
Enter Start Position and Length for a partial column relationship. 

Parent Column: Dependent Column: 
Number : 1 Number : 1 
Name : COL1 Name : COLA 
Type(Length): DEC(9,2) Type(Length): CHAR(15) 



Start Position ===> 1 Start Position ===> 1 
Length ===> 5 Length ===> 11 

Enter CANCEL to end without defining the extended column relationship 

Use this window to create partial-column/field relationships.

If the columns you want to map are the same length, the fields in this window are prefilled and the
following message is displayed:

Press ENTER without any changes for a full-column relationship

Complete this window and press Enter to proceed.

The left side of the body of this window contains fields that pertain to the 
parent column/field:

Number
Displays the number of the parent column/field.

Name
Displays the name of the parent column/field.
170 File-AID/RDX Reference

Type(Length)
Displays the type of data contained in the parent column/field. The length, in parentheses,
follows the data type. If an MVS field includes an occurrence of subscripts, the ARRAY SIZE and
MAX LENGTH values are also displayed, see Figure 80 on page 179 for an example.

Start Position
Specify the starting position of the string in the parent column/field that will comprise the
column/field relationship.

For DECIMAL columns/fields the Start Position value cannot be changed.

Length
Specify the length of the string contained in the parent column/field on which the column/field
relationship will be based.

For DECIMAL data types the Length value represents its internal byte length and cannot be
changed.

The right side of the body of this window contains fields that pertain to the dependent
column/field:

Number
Displays the number of the dependent column/field.

Name
Displays the name of the dependent column/field.

Type(Length)
Displays the type of data contained in the dependent column/field. The length, in parentheses,
follows the data type. If an MVS field includes an occurrence of subscripts, the ARRAY SIZE and
MAX LENGTH values are also displayed, see Figure 80 on page 179 for an example.

Start Position
Specify the starting position of the string in the dependent column/field that will comprise the
column/field relationship. If the right side does not display a Length field, the length of the
dependent column/field is determined by the length of the string in the corresponding parent
column/field.

For DECIMAL columns the Start Position value cannot be changed.

Length
(displays only for DECIMAL to CHAR relationships) Specify the length of the converted decimal
string in the dependent character column/field. The maximum length of a DECIMAL to CHAR
conversion is “precision + sign + decimal delimiter”. For example, maximum CHAR length for
DEC(9,2) is 11 (9 + 1 + 1).
Relationship Facilitator 171

Rules for DECIMAL/FIXPIC and CHARACTER Columns/Fields

File-AID/RDX handles DECIMAL and FIXPIC fields similarly when mapping or converting to or from
CHARACTER fields. Exceptions are noted in the following rules:

Mapping a DECIMAL/FIXPIC to a character column/field:

1. The DECIMAL/FIXPIC column/field is always mapped in its entirety. Start position and length
cannot be modified.
2. The CHARACTER column/field start position and length can be changed but cannot exceed the
maximum displayable length of the DECIMAL/FIXPIC column/field. For example, if decimal
parent format is DEC(9,2), the maximum map length of the dependent character column/field is
11 (9 plus 1 for the decimal point plus 1 for a possible minus sign).

Mapping a CHARACTER to a DECIMAL/FIXPIC column/field:

1. The DECIMAL/FIXPIC column/field is always mapped in its entirety. Start position and length
cannot be modified.
2. The CHARACTER column/field start position and length can be changed but cannot exceed the
maximum displayable length of the DECIMAL/FIXPIC column/field. For example, if
DECIMAL/FIXPIC parent format is DEC(9,2), the maximum map length of the dependent
CHARACTER column/field is 11 (9 plus 1 for the decimal point plus 1 for a possible minus sign).
3. The default parent CHARACTER column/field start position is 1.

Converting a DECIMAL/FIXPIC to a CHARACTER column/field:

1. The string values derived from DECIMAL/FIXPIC column values have these characteristics:
– Leading zeroes are suppressed
– Values less than 1:

DECIMAL: For values less than 1, a leading zero is inserted before the decimal point (or
comma), for example 0.25.

FIXPIC: For values less than 1, the leading zero is dropped before the decimal point (or
comma), for example .25.

– For values less than 0, a minus sign is the left most character in the returned string
– Values greater than 0:

DECIMAL: For values greater than 0, a plus sign is not returned

FIXPIC: For values greater than 0, if signed, a plus sign is returned; if not signed, a plus
sign is not returned

– Special characters, such as monetary symbols, are not returned

– Where the scale of the DECIMAL/FIXPIC column/field is zero, for example DEC(5,0), no
decimal point is in the returned string
2. DECIMAL only: Where the dependent CHARACTER column/field map length is less than the
returned character string, truncation occurs on the left of the returned string.

Converting a CHARACTER to a DECIMAL/FIXPIC column/field:

The string values to be converted to decimal values must comply with these constraints:

• The minus or plus sign must be the left most character of the string

• The placement of the decimal point in the string is interpreted, but the scale of the decimal value
is derived from the DECIMAL column/field definition. If, for example, the decimal definition is
DEC(9,2) and the string to be converted is 99.999, the last decimal position is truncated. Only
applies to FIXPIC if last digit is zero (0).
172 File-AID/RDX Reference

• If the string does not contain a decimal point and the scale is greater than zero, zeroes will be put
into the decimal positions of the decimal value. For example, character string 1234 would be
converted to 1234.000 for a DEC(7,3) column.
• The character string cannot contain values other than numeric values, sign or decimal delimiter
(point or comma)

Extended Column Relationships Examples

The following describes several situations in which the Extended Column Relationship Definition
window is displayed.

Example 1
Assume you have entered a column-number line command (as illustrated in Figure 69) to create a
Db2 to Db2 column relationship between two columns with data types of CHAR and lengths of 6.

Figure 69. Relationship Screen with column-number command

File-AID/RDX ------------- Column Relationships ---------------------------- 

Command ===> SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Column Number to Define Relationship D = Delete Relationship 

Parent: DB2-LOCATION.FRSAMP.CUSTOMER_TABLE
Dependent: DB2-LOCATION.FRSAMP.ORDER_TABLE
CMD Parent Columns Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
2___ CUSTOMER_NUMBER CHAR(6)
____ COMPANY_NAME CHAR(30)
____ ADDRESS CHAR(30)
____ CITY CHAR(25)
____ STATE CHAR(2)
____ ZIP_CODE CHAR(9)
____ COUNTRY CHAR(20)
NMBR Dependent Columns Type(Length)
---- ------------------------------- ------------
1 ORDER_NUMBER CHAR(6)
2 CUST_NUM CHAR(6)
3 SOC_SEC_NUM CHAR(11)
4 CREDIT_CARD_NUM CHAR(16)
5 ORD_TYPE CHAR(8)
6 ORD_DATE DATE


The Extended Column Relationship Definition pop-up window would be displayed as shown in
Figure 70 with default values for starting position and length prefilled.
Relationship Facilitator 173

Figure 70. Extended Column Relationship Definition Window

File-AID/RDX ------------- Column Relationships -----------------------------

Command ===> SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Column Number to Define Relationship D = Delete Relationship 

Extended Column Relationship Definition 

Command ===> Scroll ===> CSR 

Press ENTER without any changes for a full-column relationship 
Enter Start Position and Length for a partial-column relationship 

Parent Column: Dependent Column: 
Number : 1 Number : 1 
Name : CUSTOMER_NUMBER Name : CUST_NUM 
Type(Length): CHAR(6) Type(Length): CHAR(6) 



Start Position ===> 1 Start Position ===> 1 
Length ===> 6 

Enter CANCEL to end without defining the extended column relationship 

When you select parent and dependent columns with the same data type
and length, the Extended Column Relationship Definition window is
prefilled and the following message is displayed:

Press ENTER without any changes for a full-column relationship

Example 2
Assume you have entered a column-number line command (as illustrated in Figure 71) to create a
DB2 to KEY relationship (using root segment, not segment layout) between columns with data types
of CHAR and different lengths.

Figure 71. Column/Segment Relationships Screen with Segment-Number command

File-AID/RDX --------- Column/Segment Relationships ------------------------ 

Command ===> SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Root number to Define Relationship D = Delete Relationship 

Parent: DB2-LOCATION.FRSAMP.CUSTOMER_TABLE
Dependent: KEY-TSOID01.FISAMP.DBDLIB(PCUST)
CMD Parent Columns Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
1 ___ CUSTOMER_NUMBER CHAR(6)
____ COMPANY_NAME CHAR(30)
____ ADDRESS CHAR(30)
____ CITY CHAR(25)
____ STATE CHAR(2)
____ ZIP_CODE CHAR(9)
____ COUNTRY CHAR(20)
____ AREA_CODE CHAR(3)
____ TELEPHONE_NUM CHAR(7)
____ CONTACT_NAME CHAR(30)
____ CONTACT_TITLE CHAR(30)
____ CONTACT_ADDR CHAR(30)
NMBR Dependent Root segment Type(Length)
---- ------------------------------- ------------
1 CUST010 CHAR(6)
174 File-AID/RDX Reference

The Extended Column Relationship Definition pop-up window would be displayed as shown in
Figure 72 with default values for starting position and length prefilled.

Figure 72. Extended Column Relationship Definition Window

File-AID/RDX --------- Column/Segment Relationships ------------------------ 

Command ===> SCROLL ===> CSR 
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Root Number to Define Relationship D = Delete Relationship 

Extended Column Relationship Definition 

Command ===> Scroll ===> CSR 


Enter Start Position and Length for a partial column relationship. 

Parent Column: Dependent Column: 
Number : 1 Number : 1 
Name : CUSTOMER_NUMBER Name : CUST010 
Type(Length): CHAR(6) Type(Length): CHAR(6) 

MAX LENGTH 6 

Start Position ===> 1 Start Position ===> 1 
Length ===> 6 

Enter CANCEL to end without defining the extended column relationship 


Change the Dependent Root Segment’s Start Position to 5 and the Parent Column Length to 2. Figure
73 on page 174 indicates that the first two characters in the parent column and the last two
characters in the dependent root segment will make up the column/segment relationship.

Figure 73. Changed Dependent Start Position and Length

File-AID/RDX --------- Column/Segment Relationships ------------------------ 

Command ===> SCROLL ===> CSR 
Primary Command: CONDitional relationships, SUGgest Relationships 
Line Commands: Root Number to Define Relationship D = Delete Relationship 

Extended Column Relationship Definition 

Command ===> Scroll ===> CSR 


Enter Start Position and Length for a partial column relationship. 

Parent Column: Dependent Column: 
Number : 1 Number : 1 
Name : CUSTOMER_NUMBER Name : CUST010 
Type(Length): CHAR(6) Type(Length): CHAR(6) 

MAX LENGTH 6 

Start Position ===> 1 Start Position ===> 5 
Length ===> 2 

Enter CANCEL to end without defining the extended column relationship 


When you press Enter the Column/Segment Relationship screen reflects the desired relationship (see
Figure 74).
Relationship Facilitator 175

Figure 74. Partial Column/Segment Relation Established

File-AID/RDX --------- Column/Segment Relationships ------------------------

Command ===> SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Root Number to Define Relationship D = Delete Relationship

Parent: DB2-LOCATION.FRSAMP.CUSTOMER_TABLE
Dependent: KEY-TSOID01.FISAMP.DBDLIB(PCUST)
CMD Parent Columns Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
____ CUSTOMER_NUMBER CHAR(6) 1(1,2,5)/CUST010
- - - - - - - - - End of Related Columns - - - - - - - - -
____ CUSTOMER_NUMBER CHAR(6)
____ COMPANY_NAME CHAR(30)
____ ADDRESS CHAR(30)
____ CITY CHAR(25)
____ STATE CHAR(2)
____ ZIP_CODE CHAR(9)
____ COUNTRY CHAR(20)
____ AREA_CODE CHAR(3)
____ TELEPHONE_NUM CHAR(7)
____ CONTACT_NAME CHAR(30)
NMBR Dependent Root segment Type(Length)
---- ------------------------------- ------------
1 CUST010 CHAR(6)

Now the Mapped Fields value includes the extended column relationship information in parentheses
(1,2,5) where 1 is the parent starting position, 2 is the length, and 5 is the dependent starting
position.

Example 3
Assume you have entered a Field-Number line command (as illustrated in Figure 75) to create a DB2
to MVS relationship between a column with data type of DECIMAL and a field with data type CHAR.

Figure 75. Column/Field Relationships Screen Mapping DECIMAL to CHAR

File-AID/RDX ---------- Column/Field Relationships -------------------------

Command ===> SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Field Number to Define Relationship D = Delete Relationship 

Parent: DB2-LOCATION.FRSAMP.ORDER_TABLE
Dependent: MVS-FR.BASE.V2R0M0.SAMP.INVOICE
CMD Parent Columns Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
____ SOC_SEC_NUM CHAR(11)
____ CREDIT_CARD_NUM CHAR(16)
____ ORD_TYPE CHAR(8)
____ ORD_DATE DATE
____ ORD_STAT CHAR(8) 
10__ ORD_AMOUNT DEC(9,2)
____ ORD_DEPOSIT DEC(9,2)
NMBR Dependent fields Type(Length)
---- ------------------------------- ------------
8 IM-INVOICE-TOT DEC(9,2)
9 IM-SHIP-CHG DEC(7,2)
10 IM-SHIP-VIA CHAR(20)
11 IM-SHIP-CODE CHAR(4)
12 IM-SHIP-TO-CUST CHAR(6)
13 IM-ORDER-NO CHAR(6)


The Extended Column Relationship Definition pop-up window would be displayed as shown in
Figure 76 with default values for starting position and length prefilled:
176 File-AID/RDX Reference

Figure 76. Extended Column Relationship Definition Window with DECIMAL to CHAR

File-AID/RDX ---------- Column/Field Relationships ------------------------- 

Command ===> SCROLL ===> CSR 
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Field Number to Define Relationship D = Delete Relationship 

Extended Column Relationship Definition 

Command ===> Scroll ===> CSR 


Enter Start Position and Length for a partial column relationship. 

Parent Column: Dependent Column: 
Number : 6 Number : 10 
Name : ORD_AMOUNT Name : IM-SHIP-VIA 
Type(Length): DEC(9,2) Type(Length): CHAR(20) 



Start Position ===> 1 Start Position ===> 1 
Length ===> 11 

Enter CANCEL to end without defining the extended column relationship 

The values entered in the window in Figure 77 on page 176 indicate that the complete parent decimal
column and the last eleven characters in the dependent column (starting position 10, length 11) will
make up the column/field relationship.

Figure 77. Extended Column Relationship Definition Window after Modification

File-AID/RDX ---------- Column/Field Relationships ------------------------ 

Command ===> SCROLL ===> CSR 
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Field Number to Define Relationship D = Delete Relationship 

Extended Column Relationship Definition 

Command ===> Scroll ===> CSR 


Enter Start Position and Length for a partial column relationship. 

Parent Column: Dependent Column: 
Number : 6 Number : 10 
Name : ORD_AMOUNT Name : IM-SHIP-VIA 
Type(Length): DEC(9,2) Type(Length): CHAR(20) 



Start Position ===> 1 Start Position ===> 10 
Length ===> 11 

Enter CANCEL to end without defining the extended column relationship 


Press ENTER to complete the extended relationship definition.

Relationship Facilitator 177

Specify MVS Field Subscripts

The Specify MVS Field Subscripts pop-up window shown in Figure 78 is displayed when you attempt
to map two fields where one or both fields contain an occurrence of subscript. You then specify the
bounds of the array for each subscript. File-AID/RDX supports a maximum occurrence of a three
dimensional array.

Figure 78. Specify MVS Field Subscripts for Parent Field

Extended Field Relationship Definition 

File-AID/RDX Specify MVS Field Subscripts 
COMMAND ===> 


Parent : TSOID01.FASAMP.INVFILE 
Field Name: INV-WAREHOUSE 
Data Type: CHAR(3) 


Subscript 1 ===> (From 1 to 2) 






This window appears only if the selected parent field contains subscripts. Use it to specify the desired
value for up to three subscripts, where applicable.

Parent
Displays the name of the parent file.

Field Name
Displays the name of the parent field to be mapped.

Data Type
Displays the type of data contained in the field. The length, in parentheses, follows the data type.

Subscript 1
Specify the starting position of substring 1 in the parent field that will comprise the column/field
relationship.

Subscript 2
Specify the starting position of substring 2 in the parent field that will comprise the column/field
relationship.

Subscript 3
Specify the starting position of substring 3 in the parent field that will comprise the column/field
relationship.
178 File-AID/RDX Reference

After you press Enter, you continue either with the Dependent Field Subscripts window (Figure 79
on page 178), if the dependent field contains subscripts, or the Extended Field Relationship
Definition window (Figure 80 on page 179), if the parent and dependent field types qualify for
Extended Field Relationship Definition, or return directly to the Field/Column Relationship
screen (see Figure 81 on page 179) when the relationship definition is completed.

Figure 79. Specify MVS FIeld Subscripts for Dependent Field

Extended Field Relationship Definition 

File-AID/RDX Specify MVS Field Subscripts 
COMMAND ===> 


Dependent : TSOID01.FASAMP.INVFILE 
Field Name: INV-STATUS 
Data Type: CHAR(6) 


Subscript 1 ===> (From 1 to 2) 






Use this window to specify the desired value for up to three subscripts, if applicable, for the
dependent field.

Dependent
Displays the name of the dependent file.

Field Name
Displays the name of the dependent field to be mapped.

Data Type
Displays the type of data contained in the field. The length, in parentheses, follows the data type.

Subscript 1
Specify the starting position of substring 1 in the parent or dependent field that will comprise the
column/field relationship.

Subscript 2
Specify the starting position of substring 2 in the parent or dependent field that will comprise the
column/field relationship.

Subscript 3
Specify the starting position of substring 3 in the parent or dependent field that will comprise the
column/field relationship.
Relationship Facilitator 179

After you press Enter, you continue either with the Extended Field Relationship Definition window
(Figure 80 on page 179), if the parent and dependent field types qualify for Extended Field
Relationship Definition, or return directly to the Field/Column Relationship screen (see Figure 81 on
page 179) when the relationship definition is completed.

Figure 80. Extended Field Relationship Definition with Field Subscripts Defined

File-AID/RDX ------------- Field Relationships -----------------------------

Command ===> SCROLL ===> CSR 
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Field Number to Define Relationship D = Delete Relationship 

Extended Field Relationship Definition 

Command ===> Scroll ===> CSR 


Enter Start Position and Length for a partial-column relationship. 

Parent Field: Dependent Field: 
Number : 5 Number : 6 
Name : INV-WAREHOUSE(1) Name : INV-STATUS(1) 
Type(Length): CHAR(3) Type(Length): CHAR(6) 
ARRAY SIZE(2) ARRAY SIZE(2) 
MAX LENGTH 3 

Start Position ===> 1 Start Position ===> 1 
Length ===> 3 

Enter CANCEL to end without defining the extended column relationship 


See Extended Column Relationship Definition on page 169 for a description of the fields. Note that
the Type(Length) field now also includes the array size and maximum length of the related elements.

Upon completion, File-AID/RDX displays the defined relationship in the Field Relationships screen as
shown in Figure 81.

Figure 81. Extended Field Relationship with Defined Subscripted Relationship

File-AID/RDX -------- Field Relationships ----------------------------------

COMMAND ===> SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands: Field Number to Define Relationship D = Delete Relationship

Parent: MVS-TSOID01.FASAMP.INVFILE
Dependent: MVS-TSOID01.FASAMP.INVFILE
CMD Parent fields Type(Length) Mapped fields
---- ------------------------------- ------------ -----------------------------
____ 5/INV-WAREHOUSE(1) CHAR(3) 6(1,3,1)/INV-STATUS(1)
- - - - - - - - - End of Related Columns - - - - - - - - - 
____ INV-PART-NO CHAR(15) 
____ INV-DESCRIPTION CHAR(40) 
____ INV-UNIT-OF-MEASURE CHAR(2) 
____ INV-UNIT-PRICE DEC(7,2) 
____ INV-WAREHOUSE(2) CHAR(3) 
NMBR Dependent fields Type(Length) 
---- ------------------------------- ------------ 
1 INV-PART-NO CHAR(15) 
2 INV-DESCRIPTION CHAR(40) 
3 INV-UNIT-OF-MEASURE CHAR(2) 
4 INV-UNIT-PRICE DEC(7,2) 
5 INV-WAREHOUSE(2) CHAR(3) 

See Relationships on page 144 for a description of the fields. Note that the element notation for the
parent is enclosed in parentheses following the parent field name, while the element notation for the
dependent is enclosed in parentheses following the dependent name in the Mapped Fields area.
180 File-AID/RDX Reference

Allocate Relationship File

The Allocate Relationship File screen shown in Figure 82 is displayed when you

• Select Option A, ALLOCATE, from the DB2 Relationship Facilitator or MVS Relationship
Facilitator menu.

Use this screen to create a new Relationship file in addition to the one(s) created during the
installation of File-AID/RDX.

Figure 82. Allocate Relationship File

File-AID/RDX ----------- Allocate Relationship File ---------------------

Command ===> 

New VSAM Component names:
Cluster ===> 'FRSAMP.R44.RELATION'
Data Component LLQ ===> DATA 
Index Component LLQ ===> INDEX 
Data component . . : 'FRSAMP.R44.RELATION.NEW.DATA' 
Index component . .: 'FRSAMP.R44.RELATION.NEW.INDEX' 

Specify SMS Class Information:
Storage ===> S Data ===> Management ===> T 

Space Allocation: DATA Component KSDS INDEX Component (Blank for default)
Volume serial ===> ===> 
Units ===> TRK ===> (TRKs; CYLs; RECs; K; M)
Primary ===> 1 ===> (Amount in above units)
Secondary ===> 1 ===> (Amount in above units)


When parameters are complete, use END to continue.

Use this screen to allocate the new Relationship file that File-AID/RDX uses as a repository to store
the RI and AR relationship definition so you can extract related data.

Press END (PF3) to allocate the SMS file, or use the CANCEL command to cancel the allocation. When
allocation is complete, File-AID/RDX displays a message: FILE ALLOCATED in the upper-right corner
of the screen.

After allocating a new Relationship file, you can use Option L, Batch RI Load, from the DB2
Relationship Facilitator to load Db2 RI information from a Db2 subsystem (see Batch RI Load on page
182).

New VSAM Component Names

Cluster
Specify the name of the VSAM cluster for the Relationship file to be allocated. If you don’t use
quotes around the name, File-AID/RDX will add your TSO ID as the prefix.

Data component LLQ

Low level qualifier for the data component. You may overtype this field, if your installation uses
a different data component LLQ.
Relationship Facilitator 181

Index component LLQ

Low level qualifier for the index component. You may overtype this field, if your installation uses
a different index component LLQ.

Data component
Displays the name of the data component as it will be allocated. It reflects the new cluster name
and low level qualifier after you press Enter.

Index component
Displays the name of the index component as it will be allocated. It reflects the new cluster name
and low level qualifier after you press Enter.

If a long cluster name results in data and index component names longer
than 44 characters, the cluster name portion in front of the component LLQ
is truncated.

Specify SMS Class Information

Storage
Specify the SMS storage class to use for the allocation of the file. The storage class describes the
hardware requirements of the file.

Data
Specify the SMS data class to use for the allocation of the file. The data class describes the
attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.

Management
Specify the SMS management class to use for the allocation of the file. The management class
describes the migration, backup, and retention for the file.

Space Allocation
Specify the space allocation values for the data and index components. Leave fields blank for
defaults.

Volume serial
Specify the volume serial of the direct access device that contains the file.

Space units
Specify one of the following storage unit types depending on how the file size is expressed:

TRK - Tracks
CYL - Cylinders
K - Kilobytes
182 File-AID/RDX Reference

M - Megabytes
REC - Records

Primary quantity
Specify the primary allocation quantity as specified in the space units field.

Secondary quantity
Specify the secondary allocation quantity as specified in the space units field.

Batch RI Load
The Batch RI Load screen shown in Figure 83 on page 182 is displayed when you

• Select Option L, Batch RI Load, from the DB2 Relationship Facilitator.

Use this screen to initiate a batch job that updates your Relationship file with referential integrity
relationships (RI) for the specified Db2 subsystem.

Figure 83. Batch RI Load

File-AID/RDX ---------------- Batch RI Load --------------- Row 1 to 1 of 1 

COMMAND ===> SCROLL ===> CSR

Primary Commands: JCL view, GO to submit job 
Line Commands: D Delete 

Specify Batch Parameters: 
Relationship File Name ===> 'TSOID01.FRSMP491.RELATION' 

SSID ===> DSN Sysout Class ===> * 

Filter List (optional):
Cmd Complete CREATOR ID 
- --------------------------------------------------- 
' 
******************************* Bottom of data ********************************






On this screen you specify the Relationship file to be updated as well as the Db2 subsystem from
which to load RI. Optionally, you can specify a list of Creator IDs to limit the relationships to only
those that match the Creator IDs.

Enter GO to submit the job or enter JCL to review the JCL before submitting.

After you enter GO, File-AID/RDX displays the message: JOB SUBMITTED and returns to the DB2
Relationship Facilitator menu.
Relationship Facilitator 183

Specify Batch Parameters:

Relationship File Name

Specify the name of the Relationship file to be updated. If you don’t use quotes around the name,
File-AID/RDX will add your TSO ID as the prefix.

SSID
Specify the subsystem ID of the Db2 subsystem from where you want to load RI.

Sysout Class
Specify the desired sysout class according to your site requirements (* is the default).

Filter List (optional):

Optionally, you can specify a list of Creator IDs to limit the relationships to be updated to only those
that match the specified Creator IDs.

CMD
Enter valid line command (D). Note that the character ' indicates that the line is in Insert mode,
ready for you to type in a Creator ID.

Complete CREATOR ID
Specify one Creator ID per line. Creator ID must be a complete ID. This field is scrollable
(left/right) and subject to the EXPAND command to facilitate long Creator IDs. When you press
Enter, a new line opens allowing you to enter an additional Creator ID.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

JCL
View the JCL for the Load RI utility (see also Figure 84 on page 184). File-AID/RDX shows the
Generated JCL panel where you review and modify the JCL. Enter the SUBMIT command to
submit the Load RI job.

GO (G)
Submits this Load RI request without displaying the JCL. Before issuing the GO command, make
sure you have specified the desired relationship file and Db2 subsystem. File-AID/RDX will also
issue a message upon completion of the job.

Line Command
The following File-AID/RDX-specific line command is valid on this screen:
184 File-AID/RDX Reference

D (Delete)
Deletes the selected Creator ID from the list of Creator IDs.

Background Information
The RI load batch jobs update the relationship file (a VSAM-KSDS) with current referential integrity
information by performing the following steps:

1. Delete all referential integrity relationships (RI) for the subsystem specified from the relationship
file.
2. Gather new RI information, including non-enforced RI, from the Db2 catalog.
3. Copy the new RI information to the relationship file.

The RI load batch job does not modify the Db2 catalog.

The RI load batch job should be executed initially by the person responsible for installing File-
AID/RDX. It can be executed periodically to refresh RI relationships in the relationship file. This is
advantageous after structure changes, such as new or changed foreign keys, new or changed primary
keys, and new tables.

To achieve the most efficient results, execute this job against a Db2 subsystem that contains single
occurrences of tables. Usually, production, system test, and acceptance Db2 subsystems have single
copies of tables. Conversely, test subsystems usually have many copies of tables and, therefore, would
not be good Db2 subsystems against which to run the RI load batch job.

The referential integrity relationships that are loaded into the relationship file can be used as model
definitions to generate a related table extract.

To ensure that a complete group of RI and AR related tables is extracted, specify the subsystem where
application relationships were or are to be generated for tables using File-AID/RDX Relationship
Facilitator option 3 - Add AR on page 89.

Figure 84 on page 184 shows a sample JCL.

Figure 84. RI load Batch Job JCL

//RIUPssid EXEC PGM=XFREXEC, REGION=4096K,PARM=(FR,1,B)

//STEPLIB DD DSN=File-AID-Customized-load-library,DISP=SHR
// DD DSN=File-AID-Target-load-library
// DD DSN=Db2-load-library
//SYSOUT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=* 
//RDXSQLCD DD SYSOUT=* 
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,DISP=SHR
//RDXPARMS DD *
RELDSN ‘relationship-file’
CREATOR creator id
TBNAME table name
GO
CREATOR creator id
TBNAME table name
GO

XFREXEC is the File-AID/RDX program name.

Relationship Facilitator 185

The parameter information in the PARM field in the EXEC statement must have the following format:

Parameter Default Value Length Description

Product FR 2 FR : File-AID/RDX
Option 1 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required:

DD Statement Description
Customized and Target File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load
STEPLIB
library.
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed SQL error information from Db2.
RDXMLIB The library containing File-AID/RDX messages.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
RELDSN -- The File-AID/RDX relationship file to be updated. 
CREATOR -- Creator ID to limit relationships to be updated. (Optional)
RDXPARMS TBNAME -- Table name to limit relationships to be updated; only valid if CREATOR is used.
(Optional)
GO -- executes update for the specified CREATOR; allows multiple update runs.

Return Codes
An execution return code (RC) appears in the output listing. For return codes 4, 8, and 16, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return
Description
Code
0 Job ran to completion.
4 Job ran to completion with warning messages issued.
8 Job may have ended prematurely. Dataset or Security related error.
16 Severe error, job aborted.

Error Messages
As referential integrity information is loaded in the relationship file, error messages appear in the
output listing. The following error messages can be ignored. They refer to the Db2 catalog tables,
which do not always conform with the rules of referential integrity.

An error occurred loading the following relationship:

Relname: DSNAT
E170 The parent table does not have a primary index. 

An error occurred loading the following relationship:
Relname: DSNVT
E171 Unable to determine the foreign key for the dependent table.

The first time you run the refresh job, the following error message is generated because the file is
empty. It can be ignored.

LSCX557 **** WARNING **** ERRNO = ENFOUND

Generated in AFOPEN called from line 103 of KOPEN(KOPEN)
Uninitialized VSAM file cannot be opened for input.
Interrupted while: Opening file "ddn:RDXRELDS" 
186 File-AID/RDX Reference

Print Relationship File

The Print Relationships function enables you to generate a formatted report containing the contents
of a relationship file. You can print the report or write the report to a file.

Formatted Relationship Report Screen

The Formatted Relationship Report screen shown in Figure 85 is displayed when you select Option P
in the DB2 Relationship Facilitator or MVS Relationship Facilitator menu. You also access this screen
when selecting Option 8, Print from the RDX Utilities Menu.

Figure 85. Formatted Relationship Report Screen

File-AID/RDX --------- Formatted Relationship Report ------------------------- 

Command ===> 

Specify Relationship File:
File Name ===> FRSAMP.RELATION

Use this screen to specify the relationship file for which you want to generate a report.

The body of the Formatted Relationship Report screen consists of the following field:

File Name
Specify the name of the relationship file for which you want to generate a formatted report.

Print Options Screen

The Print Options screen shown in Figure 86 on page 186 is displayed when you complete the
Formatted Relationship Report screen and press Enter.

Figure 86. Print Options Screen

File-AID/RDX ----------------- Print Options --------------------------------- 

Command ===> 

Maximum lines per page ===> 55 (20-99) 

Specify Print Options:
Printer Destination ===> LOCAL
Sysout Class ===> R
- OR -
"TO" Print file ===>
VOLSER ===>
Disposition ===> (NEW, OLD, or MOD) 

If disposition is NEW, specify the following allocation parameters:
Generic Unit ===> SYSDA
Block Size ===> 141 (DSORG=PS,RECFM=VBA,LRECL=137)
Space Units ===> TRK (BLK, TRK, OR CYL)
Primary QTY ===> 10 (In above units)
Secondary QTY ===> 2 (In above units) 

ENTER to view JCL



Relationship Facilitator 187

Use this screen to specify whether you want to route the report to a printer or a file. If you route the
report to a file, use this screen to specify a file and its characteristics.

Maximum lines per page

Specify the maximum number of lines to be printed on each page. The value specified must be in
the range 20-99.

If you want to route the report to a printer, specify appropriate values in the following two fields:

Printer Destination
Specify the destination printer.

SYSOUT Class
Specify the SYSOUT class.

If you want to route the report to a file, specify the appropriate values in the following fields:

“TO” Print file

Specify the name of the file to which the report will be written.

VOLSER
If the file specified in TO Print file is non-cataloged or new, specify the volume serial number of
the file. For non-cataloged files, a volume serial number is required. For new files, a volume serial
number is optional.

Disposition
Specify the disposition of the TO Print file. You can write to existing files with a disposition of
OLD or MOD. Specify a disposition of NEW to create a new sequential file.

If you specify NEW in the Disposition field, you must specify the following allocation
parameters:

Generic Unit
Specify the device type on which the new file will reside. The names of these devices are
installation dependent.

Block Size
Specify the block size for the new file.

Space Units
Specify whether space for the new file will be allocated in blocks (BLK), tracks (TRK), or cylinders
(CYL).
188 File-AID/RDX Reference

Primary QTY
Specify the initial number of space units that will be allocated for the new file.

Secondary QTY
Specify the number of space units that will be allocated for each secondary extent.

Edit Print JCL

The ISPF/PDF Edit screen shown in Figure 87 is displayed when you pressed Enter on the Print
Options screen.

Figure 87. ISPF/PDF EDIT Screen — File-AID/RDX-generated JCL

VIEW - File-AID/RDX Generated JCL COLUMNS 000 000 

Command ===> SCROLL ===> CSR
You are now viewing the JCL that has been generated to perform the
required function. Change this JCL as desired before submitting. 



****** ***************************** Top of Data ******************************
000001 //*Your Jobcard information
000002 //*
000003 //*
000004 //* XFRJRD00
000005 //*********************************************************************
000006 //* PRINT FORMATTED REPORT
000007 //*********************************************************************
000008 //RELPRINT EXEC PGM=XFRPRINT
000009 //STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ170.CXVJLOAD
000010 // DD DISP=SHR,DSN=CPWR.MXVJ170.SXVJLOAD
000011 //SYSUDUMP DD SYSOUT=*
000012 //SYSTERM DD SYSOUT=*
000014 //SYSOUT DD SYSOUT=*
000013 //SYSPRINT DD SYSOUT=(A),DEST=LOCAL,HOLD=YES 
000015 //RDXPARMS DD *
000016 LINES 55


Use this screen to edit and/or submit the print JCL generated by File-AID/RDX. If you want to save
this JCL, use the ISPF/PDF CREATE or REPLACE command before you exit the panel. Otherwise, File-
AID/RDX deletes this file.

Submit this JCL to perform the print.

Relationship File - Related Objects Report

The Relationship File - Related Objects Report shown in Figure 88 on page 189 is a summary of the
relationships contained in the relationship file you specified on the Formatted Relationship Report
screen. The report is organized such that for each object involved in a relationship you can see
information about the object and its direct relationships.
Relationship Facilitator 189

Figure 88. Relationship File - Related Objects Report

File-AID/RDX 17.2 Relationship File - Related Objects Report PAGE 1

DATE 2009-09-06 
Relationship File. . : 'TSOID01.FRSAMP.RELATION' TIME 16:01:00

Type Parent to Dependent Relationships 
---- ------------------------------------------------------------------------------------------------------------------------------
Parent. . .: D-LOCATION.TSOID01.ACT 
RI Dependent: D-LOCATION.TSOID01.PROJACT 
RELNAME: RPAA 
Columns: Parent = ACTNO SMALLINT Dependent = ACTNO SMALLINT
Parent. . .: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.DEPT_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128 
RI Dependent: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.DEPT_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128 
RELNAME: RDD______A_________B_________C_________D_________E_________F_________G_________H_________I_________J_________K__
_____L_____128 
Columns: Parent = DEPTNO___A_________B________30 CHAR(3) Dependent = ADMRDEPT_A_________B________30 CHAR(3) 

AR Dependent: I-FR.IXPSAMP.DBDLIB(PORDR) 
RELNAME: CUSTOMER-ORDER RELATION KEY 
Columns: Parent = DEPTNO___A_________B________30 CHAR(1,3) Dependent = ORDR01 CHAR(1,3) 

Parent. . .: D-DSNLOCAT.FARDX.CONTACT_TABLE 
AR-C Relationship Condition: 
SELECT SET=1,LAYOUT=CONTACT_TABLE-TBL 
IF 
FIELD_NAME=STATE, 
POSITION=130,LENGTH=2,OPERATOR=EQ, 
TYPE=T,VALUE=CA 

Dependent: D-DSNLOCAT.FARDX.CUSTOMER_TABLE 
RELNAME: CONDITIONAL AR 
Columns: Parent = CUSTOMER_NUMBER CHAR(6) Dependent = CUSTOMER_NUMBER CHAR(6)

Parent. . .: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
RI Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE 
RELNAME: CONTCUST 
Columns: Parent = CUSTOMER_NUMBER CHAR(6) Dependent = CUSTOMER_NUMBER CHAR(6) 

AR Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
RELNAME: CUSTOMER-ORDER RELATIONSHIP 
Columns: Parent = CUSTOMER_NUMBER CHAR(6) Dependent = CUST_NUM CHAR(6)

File-AID/RDX 17.2 Relationship File - Related Objects Report PAGE 2
DATE 2009-09-06 
Relationship File. . : 'TSOID01.FRSAMP.RELATION' TIME 16:01:00

Type Dependent to Parent Relationships 
---- ------------------------------------------------------------------------------------------------------------------------------
Dependent .: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.PROJ_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128 
RI Parent: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.DEPT_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128 

Dependent .: D-DSNLOCAT.FRSAMP.CONTACT_TABLE 
RI Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 

Dependent .: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE 
RI Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 

Dependent .: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE 
RI Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 

Dependent .: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
AR Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 

Dependent .: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
AR Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 

Dependent .: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE 
RI Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 

Dependent .: I-FR.IXPSAMP.DBDLIB(PORDR) 
AR Parent: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.DEPT_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128 

Dependent .: M-TSOID01.FRSAMP.CONTACTT 
AR Parent: M-TSOID01.FRSAMP.CUSTOMER 

Dependent .: M-TSOID01.FRSAMP.ORDERLIN 
AR Parent: M-TSOID01.FRSAMP.ORDERTAB 

Dependent .: M-TSOID01.FRSAMP.ORDERLIN 
AR Parent: M-TSOID01.FRSAMP.PART_TABLE 

190 File-AID/RDX Reference

The report groups related objects. In the first part, the groups are made up with the parent object
listed first, followed by all of its dependent (child) objects. In the second part, the groups are made
up with the dependent object listed first, followed by all of its parent objects. If an object is listed
more than once in a group as a parent or child, it reflects the number of relationships that exist
between those objects. The groups are listed in alphabetical order.

The Formatted Relationship Report consists of the following fields:

Type
Displays the type of relationship that exists between the parent and dependent object.

RI Referential Integrity relationship

AR Application Relationship
AR-C User-defined conditional (data driven) application relationship. Created and
maintained by the user. The relationship condition (selection criteria) is printed
following the parent information of the relationship.

Parent
Name of the parent object. Db2 long object names are wrapped within the column.

Dependent
Name of the dependent object. Db2 long object names are wrapped within the column.

The parent and dependent object names are preceded by their object type:

D- Db2 object
M- MVS object
I- IMS and Output Key file (dependent only)

RELNAME or Description
Displays the RELNAME for RI relationships or the defined description for application
relationships (AR).

Columns
Displays the related parent and dependent columns with their column type and length.
 191

Extract
Overview
Option 2, Extract, enables you to extract data from one or more related objects (Db2 tables or views
and/or MVS files), including Db2 referential integrity-related data and user-defined application-
related data that are loaded in the specified File-AID/RDX relationship file. Should your extract
request include relations to an Output Key file or external IMS related data, File-AID/RDX generates
an Output Key file. For IMS Output Key files, File-AID/RDX also allows a File-AID for IMS Extract to be
executed as a step following the File-AID/RDX extract using the IMS key file. Or you can use the
resulting key file separately with File-AID for IMS to extract the IMS related data.

File-AID/RDX enables you to control the scope and depth of your extract by specifying extract
criteria, including which relationships to exclude from the extract, how many rows to extract, and
what selection criteria should be applied to the Db2 tables and/or MVS files to be extracted. You may
define multiple selection criteria sets to be saved in the extract request file. Thus, you can create
complex criteria and store the related extracted records in a single extract file. Furthermore, you can
specify an Input Key file as additional selection criteria for the Db2 or MVS driving object during the
extract process.

The Extract function consists of an interactive definition phase and an execution phase.

The interactive phase takes place online. In preparation of the execution phase, it allows you to
specify information about the following:

• Driving object
• Relationship file
• Navigation, sampling, and selection criteria
• Extract file, Extract Request file
• Input Key and Output Key files
• Data Privacy options
• Unrelated objects
• Checkpoint/Resumption

Your current profile provides default values for all new extract requests. It also controls the starting
panel for the interactive phase and its flow. Refer to Profiles and Global Defaults for more detail on
how to select and set up your profiles.

Of course, you can also create new extract requests from previously saved ones or simply repeat old
requests without any changes.

In addition, File-AID/RDX builds JCL that you can edit and save before you submit it for execution.
You can also create a single request member that combines the extract and the load specifications. See
Continue With Load on page 351 and Load for more information about how to create a combined
batch job.

Normally, the execution phase takes place in batch mode. Your installation may also permit
interactive (online) execution of the extract, however, you should consider it for short extracts only.
During the execution phase, File-AID/RDX can copy the extracted data to any of the following
destinations:

• a new or existing sequential file;

192 File-AID/RDX Reference

• a new or existing member in a new or existing PDS

The maximum data record length (LRECL) that can be extracted into the extract file is
32,748 (max. of 32,756 minus 4 bytes RDX data, minus 4 bytes VB data).
File-AID/RDX will issue a message when an object file has a longer LRECL, but allow
you to start the extract. However, when a record to be extracted exceeds 32,748, the
extract will fail.

Extract processing has been enhanced to utilize Db2 for z/OS Multi-row fetch feature providing
potential reduction in CPU time, Service Units and improved performance. When extracting from
tables with LOB or XML column types, multi-row fetch processing will not be used unless these
columns are excluded from the extract.

File-AID/RDX produces reports that summarize the extract results at the end of the execution phase.

Determining Which Rows Will Be Extracted

A File-AID/RDX extract file represents a subset of related and unrelated Db2 and MVS data. The
related data is related by referential integrity (RI) relationships and user-defined application
relationships (AR) as defined in the relationship file. In order for File-AID/RDX to include the
relationships that you want in the extract, you must specify an object that is the starting point for
those relationships. Throughout the File-AID/RDX documentation, this object is referred to as the
driving object.

After you specify a driving object, you determine the scope of the extract.

Selecting a Driving Object

In choosing a driving object, it is important to have an understanding of the data you want to
extract.

For example, assume a DBA wants to create a test environment consisting of a subset of data from the
production system. In this case, the DBA might select an object central to the system or the object
most often accessed by programs. In particular, assume that the Db2 tables in Figure 89 represent the
tables in an order entry system. Because the ORDER_TABLE is central to the order entry system, the
DBA would probably select the ORDER_TABLE as the driving object.

For another example, assume that an applications programmer has a problem with the data in a
specific Db2 table and wants to duplicate the conditions under which the problem occurs. The
programmer would select the problem table as the driving object to extract data from and then
extract data from objects related to it. In particular, assume that there is a problem with order
number data from the ORDER_TABLE. The programmer would select ORDER_TABLE as the driving
object because that is where the problem data resides. The result would be an extract including data
from the problem ORDER_TABLE and other related data.
Extract 193

Figure 89. Sample Tables and Relationships

Determining the Scope of the Extract

File-AID/RDX extracts rows based on the list of relationships displayed on the Extract Scope -
Relationship View screen. The displayed relationships are the relationships File-AID/RDX uses in the
extract process. You determine which rows, or records, will be extracted by selecting the Navigation
Controls and by excluding relationships or objects from the list. The Navigation Controls can be
applied, globally or on an individual object or relationship basis.

Navigation Controls

Example:

Consider six related objects: ORDER_TABLE, CUSTOMER_TABLE, CONTACT_TABLE,

ORDER_LINE_TABLE, PART_TABLE, and SUPPLIER_TABLE.

• CUSTOMER_TABLE is the parent of ORDER_TABLE and CONTACT_TABLE, because all records in

all three tables contain a customer number column.

• ORDER_TABLE is the parent of ORDER_LINE_TABLE, because all records in both tables contain an
order number column.

• PART_TABLE is the parent of ORDER_LINE_TABLE and SUPPLIER_TABLE, because all records in all
three tables contain a part number column.

Let ORDER_TABLE be the driving object.

The following demonstrates the progressive nature of the navigation controls applied globally:

Direct descendant path = Y (see Figure 90):

Definition
Extract selected rows from the driving object and all of the dependents of the driving object and
their dependents.
194 File-AID/RDX Reference

1. The ORDER_TABLE - ORDER_LINE_TABLE relationship can only be navigated via the direct
descendant path. All rows that are part of the original selection from the driving object will
choose this path and extract the related records from ORDER_LINE_TABLE.

When your profile has navigation criteria Direct set to C or P (see also Direct on page
58), all other Extract Navigation Criteria parameters are disabled and cannot be
modified during the extract specification. With Direct set to C, in this example it
means, only the related records from ORDER_LINE_TABLE will be extracted and the
extract stops here.

Figure 90. Global Navigation Controls - Direct = Y

Parent path = Y (Direct: Y Parent: Y Sibling: N Indirect: N) (see Figure 91):

Definition
Extract the parents of all extracted data to maintain the integrity of the extracted data.

2. The CUSTOMER_TABLE - ORDER_TABLE relationship will be navigated via the parent path. All
rows that are part of the original selection from the driving object will choose this path.
3. The PART_TABLE - ORDER_LINE_TABLE relationship will be navigated via the parent path. All
rows that are extracted from ORDER_LINE_TABLE (Step 1) will choose this path.

When your profile has navigation criteria Direct set to P (see also Direct on
page 58), in this example it means that the extract stops here after
extracting the parents from CUSTOMER_TABLE - ORDER_TABLE and
PART_TABLE - ORDER_LINE_TABLE.
Extract 195

Figure 91. Global Navigation Controls - Direct = Y, Parent = Y=

Siblings path = Y (Direct: Y Parent: Y Sibling: Y Indirect: N) (see Figure 92):

Definition
Extract other dependents of the extracted parents from the same relationships.

4. The CUSTOMER_TABLE - ORDER_TABLE relationship will be navigated via the sibling path. All
rows that were part of the parent selection (step 2) will choose this path (get all orders for this
customer).
5. The PART_TABLE - ORDER_LINE_TABLE relationship will be navigated via the sibling path. All
rows that part of the parent selection (step 3) will choose this path (get all order line entries for
this part number).
6. The ORDER_TABLE - ORDER_LINE_TABLE relationship is now also navigated via the parent path.
All rows extracted from the PART_TABLE - ORDER_LINE_TABLE relationship will choose this path
(get all order parents for this ORDER_LINE entry).
196 File-AID/RDX Reference

Figure 92. Global Navigation Controls - Direct = Y, Parent = Y, Sibling = Y=

Indirect path = Y (Direct: Y Parent: Y Sibling: Y Indirect: Y) (see Figure 93):

Definition
Extract other dependents of the extracted parents from other relationships.

7. The CUSTOMER_TABLE - CONTACT_TABLE relationship will be navigated via the indirect path.
All rows that were part of the parent selection (step 2) will choose this path (get all contact
entries for this customer).
8. The PART_TABLE - SUPPLIER_TABLE relationship will be navigated via the indirect path. All rows
that were part of the parent selection (step 3) will choose this path (get all supplier entries for this
part number).
9. The ORDER_TABLE - ORDER_LINE_TABLE relationship will be navigated via the indirect path. All
rows that were part of the sibling selection (step 4) will choose this path (get all ORDER_LINE
entries for this order).
Extract 197

Figure 93. Global Navigation Controls - Direct = Y, Parent = Y, Sibling = Y, Indirect = Y

In addition, you can manually exclude objects and relationships from the list using the X (exclude)
line command and EXCLUDE primary command on the Extract Scope - Object View and “Extract
Scope - Relationship” screens (see Figure 130 on page 256 through Figure on page 276). When
excluding an object, all relationships involving that object are excluded.

Sampling Controls
Sampling controls regulate how many qualifying records are to be extracted. They can be set globally
for all objects and relationships or individually for each object or relationship.

Maximum Total Rows/Records From All Objects

The extract is stopped when the number of records extracted matches this limit. No limit (*) is
the default.

Action when maximum count is reached

What happens after the maximum row count is reached will differ depending on the setting of
the quiesce action specified on the extract scope panel. If the quiesce action is set to STOP, no
further rows will be extracted from the object. If it is set to QUIESCE, rows that are extracted via
parent path navigation will continue to be extracted but direct, indirect and sibling rows will
not.

Quiesce means to stop all downward navigation and just get the parents for any rows already
extracted. The quiesce option will allow the extract to stop at a logical breaking point where the
integrity of the extracted data is maintained.

Cycle Count

There are three ways to set cycle count in the extract scope:

1. Global

The global cycle count limits the number of times an object can be visited during an
extract.

2. Relationship Level
198 File-AID/RDX Reference

The cycle count can be set for each individual relationship in the extract. Cycle count
limits the number of times a relationship can be visited during an extract. The direct
path will always be navigated only once and navigation on the parent path will not be
counted.

There is no way to know how many rows will be extracted in a cycle; any chase keys
ready to be extracted via the relationship being processed will be included in the same
cycle. It is intended to be used simply as a way to limit the amount of data selected.

3. Object Level

The cycle count can be set for each individual object in the extract.

When entered for an object, it limits the number of times an object can be visited during
an extract regardless of the number of relationships.

Maximum Rows/Records From An Individual Object Or Relationship (MaxRow)

Once the maximum number of records for an object or relationship has been reached, no more
records from that object or relationship will be extracted. No limit (*) is the default.

Sampling criteria is being expanded to the relationship level. Cycle count, maxrows and
dependents-per-parents can now be specified for each relationship. The sampling criteria
specified on the object view and the relationship view will be used together at extract time.

Maxrows specified at the object level applies to all paths leading to the object; all rows selected
via direct, indirect, parent and sibling are included in the maxrows count.

Maxrows specified at the relationship level applies to all paths leading down from the object; all
records selected via direct, indirect and sibling are included in the maxrows count. Parent path
navigation of the relationship is not included because it will extract rows from a different object.

When maxrow is specified at both a relationship and an object level the relationship maxrow
value is processed first. If the count has not been exceeded the row is passed on to check against
maxrow specified at the object.

What happens after the maxrow count is reached will differ depending on the setting of the
quiesce action specified on the extract scope panel. If the quiesce action is set to stop, no further
rows will be extracted from the object. If it is set to quiesce, rows that are extracted via parent
path navigation will continue to be extracted but direct, indirect and sibling rows will not.

Nth Row

NTH allows rows that are eligible for selection to be skipped and not be extracted. It is a select 1
of x value; an NTH value of 3 will result in rows 1 and 4 to be extracted.

When NTH is specified at the object level it applies to all relationships leading from the object.
NTH causes every x number of rows to be selected.

Dependents-Per-Parent

Determines the maximum number of dependent records to be extracted for each parent record
extracted. An asterisk (*) indicates that File-AID/RDX will extract all dependent records. A value
of 2, for example, specifies to select no more than 2 dependent ORDER records for each extracted
parent CUSTOMER record. For KEY relationships, this field is not applicable.
Extract 199

Using Relationship Definitions Across Db2 Subsystems

The relationship file contains information about referential integrity relationships and application-
defined relationships. When File-AID/RDX searches for relationship information, it conducts the
search based on the names of the tables in the relationships. When File-AID/RDX cannot find an
exact match in the relationship dataset, it continues looking for definitions that match the table
name only. Since it does not use the location, subsystem, or creator name, File-AID/RDX can use
relationship information from any subsystem for any other subsystem. As a result, you do not have to
define relationships for tables in your subsystem, but rather you can copy data to your subsystem
based on a relationship from another subsystem.

Data Disguise does not support this function. If the extract request is to be disguised, make
sure that disguise criteria has been defined for the new Db2 objects as data disguise
criteria is defined for Db2 objects using the three part object name location.creator.object
and their relationships must be defined in the relationship file.

The following scenario illustrates the process of how to extract data from one subsystem using
relationship information from a second subsystem to populate tables in a third subsystem. In Table
10, there are three different subsystems (PROD, TEST, and ACCEPT). Each entry in the columns
represents the name of a table.

Table 10. Db2 Subsystems

PROD ACCEPT TEST
P.CUSTOMER A.CUSTOMER T.CUSTOMER
P.ORDER A.ORDER T.ORDER

There is a relationship definition for the pair of tables CUSTOMER and ORDER in the production
subsystem, called PROD in the example, but none in the acceptance subsystem. You want to use this
relationship information as the model to extract data from the CUSTOMER and ORDER tables
residing in the acceptance subsystem (ACCEPT) to populate the CUSTOMER and ORDER tables in
the test subsystem (TEST).

To perform this extract:

1. specify A.CUSTOMER to drive the extract process.

Figure 94. Driving Object - DB2

File-AID/RDX ------------- DB2 Driving Object -------------------------------

Command ===> 

Primary commands: MVS object, REFerence, REQuest 

Specify table to drive extract process: 
SSID ===> ACPT
Location ===> LOCATION (* or pattern for selection list)
Creator ===> A (* or pattern for selection list)
Table Name ===> CUSTOMER (* or pattern for selection list)

Relationship Information:

2. select the P.CUSTOMER relationship definition, if more than one relationship definition exists
for the Table Name value (CUSTOMER).
200 File-AID/RDX Reference

Figure 95. Relationship Listing

File-AID/RDX ------------- DB2 Driving Object ------------------------------- 

Command ===> 
Relationship Listing 
Primary Comma Row 1 to 3 of 3 
Command ===> SCROLL ===> CSR 
Specify table 
SSID Multiple relationships exist for object: CUSTOMER 
Location 
Creator Enter 'S' to select relationship definition for extract 
Table Name 
CMD Object SSID 
Relationship --- -------------------------------------------------- ---- 
File Name o _ LOCATION.Z.CUSTOMER DVLP 
S LOCATION.P.CUSTOMER PROD 
_ LOCATION.T.CUSTOMER TEST 
********************** Bottom of data *********************** 


3. specify the P.CUSTOMER to P.ORDER relationship definitions from the PROD subsystem as the
extract criteria for the tables in the ACCEPT subsystem and exclude the other relationships.

Figure 96. Relationship Navigation Criteria

File-AID/RDX ------- Relationship Navigation Criteria ---------- Row 1 from 5 

Command ===> Scroll ===> PAGE 

Primary Commands: EXclude/Unex, Change, Find, Hide, FILter, CHEck, SIze, SOrt 
VIew, STATus, SAMple, NAVigation, VALidate, GRaphic, REPort 
Line Commands: X = Exclude U = Unexclude I = Info 
Driving Object: A.CUSTOMER 
SSID: ACPT Location: LOCATION Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
X001 A.CUSTOMER Y - - - 
A.CONTACT CONTCUST 
0002 A.CUSTOMER Y - - - 
A.ORDER Customer to Order AR 
X003 A.ORDER Y - - - 
A.ORDER_LINE ORDLORD 
X004 A.PART - Y N - 
A.ORDER_LINE ORDLPRT 
X005 A.PART - - - N 
A.SUPPLIER SUPPPART 
******************************* Bottom of data ********************************

4. specify T as Creator ID and TEST as subsystem ID for the tables into which to load the extracted
data (the target tables).

The Load Object Specification screen is not the next screen in the actual
dialog. It is, however, representative of the next step for the purpose of this
example.
Extract 201

Figure 97. Load Object Specification

File-AID/RDX --------------- Load Object Specification ------------------------ .

Command ===>

Specify Target DB2 Environment: 
SSID ===> TEST 
Location ===> 
DB2 Load Method ===> SQL (SQL = SQL Insert Statement;
DB2 = IBM DB2 Batch Load Utility)

Specify Object Name Modifiers: (/ entry to apply modification)
/ DB2 Creator ===> T (Creator for ALL DB2 objects)
_ DB2 Index name prefix ===> 
_ DB2 Index name suffix ===> 
_ MVS high level qualifier ===> TSOID01 (HLQ for ALL MVS objects)
_ MVS file name suffix ===> NEW 

_ Revert to source names ===> (D = DB2 objects; 
M = MVS objects; B= Both)


5. File-AID/RDX uses the relationship information for CUSTOMER to ORDER from the PROD
subsystem. It extracts data from the ACCEPT subsystem using the PROD relationship
information. It populates the CUSTOMER and ORDER tables in the TEST subsystem with the
extracted data. See Figure 98 on page 201 for a diagram illustrating the use of relationships across
subsystems.

Figure 98. Extracting Data From Subsystem ACCEPT Based on Relationships in Subsystem PROD
202 File-AID/RDX Reference

Stopping/Resuming Batch Extract Execution

File-AID/RDX provides the ability to identify a checkpoint in an extract request that will stop the
execution of the extract in a controlled manner. Stop a checkpoint enabled extract at a pre-
determined checkpoint or any time during execution with a z/OS MODIFY command (see Stop
Extract Execution with z/OS Operator MODIFY Command). In all cases, processing on the object
currently being extracted will complete before the checkpoint is taken and a controlled stop occurs.
After the controlled stop, submit the extract request again to resume the extract execution from the
checkpoint.

Use this functionality when you anticipate a long running extract that might not complete within
your site’s constraints or when executing complex related extracts.

Refer to Checkpoint/Resumption on page 347 for more information.

Stop Extract Execution with z/OS Operator MODIFY Command

To stop the execution of an extract in a controlled manner without a pre-determined checkpoint,
enable Checkpoint/Resumption and specify the Checkpoint Data File for the extract request. Then,
during extract execution, use the z/OS MODIFY command with parameter NOW.

The MODIFY command requires proper OPERATOR authority.

The verb MODIFY can be abbreviated, F.

Syntax:

F jobname,NOW

If you cancel an extract without Checkpoint/Resumption Enabled, the

extract will be incomplete and will not be usable for extract resumption or
load.

Cloning Extract Requests

The cloning an extract request functionality allows you to create an extract request on one subsystem
or MVS environment and then easily modify it to run on a different subsystem or MVS environment
which has the same objects but with different names.

Once you have saved an extract request you can use it again to extract data from the same or another
Db2 subsystem. You just use the M line command in the Extract Reference List or the Request File
Member List Screen and specify the Db2 subsystem, if the request includes Db2 objects, as illustrated
in Figure 112 on page 227. You can further modify or “clone” the request by specifying new object
names. The same extract criteria will be applied on the specified Db2 subsystem or MVS environment,
using the same relationships, extract options, and selection criteria.

If there are no Disguise rules created for the new object names, the Disguise
rules for the original objects will be applied.

Support for Db2 XML and LOB Data Type

If any of the objects to be extracted include an XML and/or LOB column, File-AID/RDX will extract
all data from the XML and/or LOB column(s), maintaining their proper format. The extracted XML
Extract 203

and/or LOB data will be masked. Note that an Input Key File and Selection Criteria cannot reference
an XML and/or LOB column.

Disguise Criteria cannot be created on XML and/or LOB columns when using DCF (see also Using
File-AID/RDX with File-AID/Data Solutions (Using DCF) on page 604).

XML and/or CLOB column data in extracts can only be disguised with Dynamic Privacy Rules
(Disguise Option 2, DPR). Dynamic Privacy Rules must be defined with the File-AID Data Privacy
component of the Topaz Workbench (see also Using File-AID/RDX with File-AID Data Privacy (Using
DPR) on page 603). Disguising DBCLOB columns is not supported.

You can load extracted data from XML and/or LOB columns to a target table using either SQL Insert
or Db2 Load options. When loading an extract disguised with DCF, be aware that the extracted XML
and/or LOB data is not disguised and will be loaded unmasked in its proper format.

Support for Db2 Temporal Tables

Temporal Table support requires Db2 Version 10 Release 1 or higher, Temporal View support requires
Db2 Version 11 Release 1 or higher. You can specify business and/or system time periods to extract
data from Temporal Tables (see SELECT FROM Temporal Table on page 252). Image copy extracts do
not include Temporal Table support.

Support for Db2 Archive Tables

In File-AID/RDX table lists, Archive Table Type ‘R’ is identified as Type ARCHV. You can extract data
from Db2 Archive Tables like normal tables. Refer to Support for Db2 Archive Tables on page 412 for
considerations when loading extracted data from Archive Tables.

GDG Considerations
Based on the relationships defined, the related objects can be either a single generation if a GDS is
specified or multiple generations if a GDG base is specified. Object names display in the same format
used to create the relationship. For relative GDSs, the extract file contains their relative as well as
their absolute file names.

When using relative generation, the dataset associated with the generation specified must exist or the
object will be excluded from the extract, as is standard behavior for all missing objects.

When a GDS is extracted, each generation is treated as a separate object and will have a different
object number. At load time, each generation can be loaded to a different dataset.

When a GDG base is extracted, all generations are processed together and will be assigned a single
object number. At load time all the generations are part of the same object.

File-AID/RDX does not support extracting from and loading to tape datasets.

Download File-AID/RDX Extract Data to the Workstation Environment

Use another Compuware product, File-AID/EX, to transfer data extracted with File-AID/RDX and
convert data between like or unlike data stores, between EBCDIC and ASCII, and between more than
60 different file and database formats.

To prepare File-AID/RDX extract data for File-AID/EX:

204 File-AID/RDX Reference

• specify that File-AID/RDX create a COBOL Record Layout File during the extract (see also Create
layouts on page 344)

• do not select the compress option for the extract or decompress the file beforehand (see also
Compress on page 339)

• sort the extract file using sample JCL provided in the sample file
‘hlq.CPWR.MXVJ170.SXVJSAMP(FAEXSORT)’

Refer to the File-AID/EX documentation for transfer procedures.

Extract Driving Object - Single Panel

When your profile specifies that your initial extract panel is the Single Panel Extract (refer to First
extract panel on page 62) the first extract panel is either the Extract - DB2 Driving Object or the
Extract - MVS Driving Object panel depending on your profile’s driving object type setting (Default
driving object type on page 62) when you

• Select Option 2, Extract, from the File-AID/RDX Primary Option Menu

The single panel extract is intended to be used for extracts that don’t require customization of the
relationship information or extract methods. You just need to specify the driving object, the extract
file for the extract output, and the File-AID/RDX relationship file. Optionally, you may specify
selection criteria for the driving object. All other extract options will be applied as specified in your
current profile.

Then you simply enter the GO command and File-AID/RDX submits this extract job.

Extract requests submitted with the Single Panel Extract function will NOT
be saved permanently and, consequently, NOT be added to the Extract
Reference List (see also Extract Reference List on page 213).

Extract - DB2 Driving Object

The Extract - DB2 Driving Object screen shown in Figure 99 is displayed when your profile specifies
that the driving object for an extract is a Db2 table, or you enter the DB2 command in the Extract -
MVS Driving Object screen.

Use this screen to specify a Db2 table to drive the extract.

Extract 205

Figure 99. Extract - DB2 Driving Object

File-AID/RDX ----------- Extract - DB2 Driving Object ----------------------

OPTION ===> Scroll ===> CSR
TSOID01 Profile: FRSAMPQK
Primary commands: MVS driving object, EDIT JCL, GO to submit job

Specify table to drive extract process from:
SSID ===> DSN 
Location ===> (* or pattern for selection list)
Creator ===> FRSAMP (* or pattern for selection list)
Table Name ===> (* or pattern for selection list)

Specify Extract Options:
Edit Object Selection Criteria ===> N (Y = Yes; N = No) *Defined*
Maximum Rows to Select ===> (* for all rows) 
Use Uncomitted Read ===> (Y = Yes; N = No)
Extract IMPLICITLY HIDDEN columns ===> N (Y = Yes; N = No) 
SELECT FROM Temporal Table ===> (Y = Yes; N = No) *None*
Specify Extract "TO" File Information: 
File name ===> FRSAMP.EXTRACT 
Format Unicode Data ===> (1 = Extract as Unicode; 2 = Convert Unicode)
Edit Data Privacy Spec ===> (Y = Yes; N = No) *DCF*

Relationship Information:
File name or pattern ===> 'TSOID01.FRSAMP.RELATION' 

The *Current Values* indicators to the right of certain extract option fields are display fields only
and are updated upon return from each of the extract options to reflect the current status and value
for the option.

The body of this screen consists of the following fields:

Specify Table To Drive Extract Process From Area:

Use the fields in this area to specify the Db2 table for which you want to retrieve relationship
information from the relationship file so you can extract related data. When specifying patterns in
the fields, File-AID/RDX searches the relationship file and presents selection lists.

SSID
Displays the current Db2 subsystem ID as specified in your profile. Type over this field to connect
to a new Db2 subsystem. If you leave the Location field blank, the table you specify to drive the
extract must exist in the Db2 subsystem displayed here.

Location
Specify the location ID of the table you want to drive the extract if it resides in a remote Db2
subsystem. The location you enter must be defined in the Db2 system catalog table,
SYSIBM.LOCATIONS.

Leave this field blank if the table you want to drive the extract is in the Db2 subsystem in the
SSID field.

The Extract from Image Copy option is not available when extracting from
a remote location. (see also Extract from Image Copy on page 251).
206 File-AID/RDX Reference

Creator
Specify the authorization ID of the owner of the table, view, synonym, or alias that you want to
drive the extract process. You can enter a pattern in this field. Valid pattern characters are %, _,
and * (see Pattern Characters on page 27). If you specify a pattern, File-AID/RDX searches the Db2
catalog and displays matches in a Table List pop-up window.

Table Name
Specify the name of the table, view, alias, or synonym that you want to drive the extract process.
For more information about how File-AID/RDX supports view, aliases, and synonyms in Extract,
see Use of Db2 Views on page 208 and Use of Aliases and Synonyms on page 223. Also refer to
Relationship Listing Window for Db2 Objects on page 224 for more information on how File-
AID/RDX determines what relationship definition to use for the driving object.

You can enter a pattern in this field. Valid pattern characters are %, _, and * (see Pattern
Characters on page 27). If you specify a pattern, File-AID/RDX searches the Db2 catalog and
displays matches in a Table List pop-up window.

Specify Extract Options Area:

Edit Object Selection Criteria

Enter Yes so you can specify selection criteria for the driving table. File-AID/RDX will display the
DB2 Object Selection Criteria screen (refer to Figure 158 on page 305) when you press Enter. Enter
No to extract all rows from the driving table.

Current Values displays *Defined* if selection criteria has already been defined.

Maximum Rows to Select

Specify the maximum number of rows you want to extract from the driving object. Enter an
asterisk (*) to retrieve all rows that meet selection criteria. This value is applied after the selection
criteria for the driving object has been applied.

Use Uncommitted Reads

Specify whether File-AID/RDX should extract data from Db2 objects that include Uncommitted
Reads or not.

The field is prefilled with the specified UNCOMMITTED_READ_DEFAULT configuration

parameter value (Yes or No) of the Db2 Environment PARMLIB member or with the current
profile value (Yes or No) if UNCOMMITTED_READ_DEFAULT is set to blank (default, see also
UNCOMMITTED_READ_DEFAULT in the File-AID Advanced Configuration Guide).

Extract IMPLICITLY HIDDEN columns

Specify whether File-AID/RDX should extract data from Db2 columns that are defined as
IMPLICITLY HIDDEN. When this option is set to Y, the resulting File-AID/RDX extract file will
include the data from IMPLICITLY HIDDEN columns.
Extract 207

SELECT FROM Temporal Table

Enter Yes if you want to specify or modify a time-period and date/timestamps for Temporal Tables
or Temporal Views. File-AID/RDX will display the SELECT FROM Temporal Table screen (refer to
Figure 129 on page 253) when you press Enter. Temporal table support requires Db2 Version 10 or
more recent. Starting with Db2 Version 11, temporal support allows period specifications and
period clauses to be specified for views. The same rules apply for views as do for tables.

Enter No (default) if you don’t want to display the SELECT FROM Temporal Table screen.

The status *Defined* displays if a SELECT FROM Temporal Table statement has already been
defined, otherwise *None* displays.

If you want to extract data from temporal tables or views without a SELECT FROM Temporal
Table statement, make sure *None* displays. To change the status from *Defined* to *None*,
enter Yes in the SELECT FROM Temporal Table field, then set the Use System Time and Use
Business Time to No in the SELECT FROM Temporal Table screen (refer to Figure 129 on page
253).

1. When the *Defined* status displays and the extract request includes one or more
temporal tables or views, File-AID/RDX will include the SELECT FROM Temporal Table
statement even if the SELECT FROM Temporal Table field is set to N.
The SELECT FROM Temporal Table statement is only generated for each Temporal
Table or Temporal View in the extract request.
2. Whenever the selection is based on SYSTEM_TIME, it is possible that some rows come
from the base table and some from the history table.
3. The *Defined* status is saved for this extract.
4. The SELECT FROM Temporal Table field will be reset to its default (No, *None*) when
you exit the extract - DB2 Driving Object screen.

Specify Extract "TO" File Information Area:

Use this area to specify the following extract output information:

Extract File name

Specify the name of the file to which data will be extracted. Include the member name (in
parentheses) when the file is a PDS. See Extract File on page 44 and File-AID/RDX Extract File on
page 377 for more information on the extract file. If you specify a pattern, select a sequential file
from the “Catalog Utility File List” (see Figure 121 on page 236) after you entered one of the
primary commands. Remember, File-AID/RDX will not prompt for a member.

Format Unicode Data

Specify whether data extracted from Db2 tables with Unicode encoding is written to the extract
file in Unicode or EBCDIC format (see also profile value DB2 Format on page 60).

1 Unicode option will write the data using Unicode encoding.

2 Compatibility format will maintain the conversion to EBCDIC encoding used in
previous releases.

Edit Data Privacy Spec

Specify whether you want to change the current data privacy specifications. When data privacy
has been specified, File-AID/RDX will disguise the extracted data as part of the extract batch job
208 File-AID/RDX Reference

according to the disguise criteria defined in the Disguise Control file (DCF) or in the Dynamic
Privacy Rules Project (DPR). When you enter Y, File-AID/RDX will display the Data Privacy
Specification screen (refer to Figure 177 on page 341) so you can change the current setting.

Current Values displays *DCF*, *DPR*, or *None* for the selected disguise option.

Relationship Information Area:

Use this area to specify the following relationship information:

File name or pattern

Specify the name of the file that contains the referential integrity and application relationship
information you want to use for the extract process. If you specify a pattern, select a file from the
“Catalog Utility File List” (see Figure 121 on page 236).

If you leave this field blank, File-AID/RDX will perform a single table extract.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

EDIT (E)
Displays the JCL for this extract request. File-AID/RDX shows the Generated JCL panel where you
review and modify the extract JCL.

GO (G)
Submits this extract request. Before issuing the GO command, make sure you have completed all
the extract information. File-AID/RDX will also issue a message upon completion of the job.

MENU
Switches from this panel to the full Extract Menu. Only valid when profile setting Display Extract
Menu on page 62 is set to Y.

MVS (M)
Switches from this panel to the single panel Extract - MVS Driving Object prefilled with the
applicable information from your current profile. Refer to Extract - MVS Driving Object on page
210.

Use of Db2 Views

File-AID/RDX supports views of Db2 tables in the Extract function. If you specify a view as the
driving table, File-AID/RDX lists relationships defined for the view, not the underlying base table.
Extract 209

File-AID/RDX then extracts data from the view specified as the driving table/view and from all tables
and views related to the driving table/view.

1. Extracting from complex views may create unloadable data. Specifying

the base table(s) is recommended.
2. The Extract from Image Copy option is not available for views.

Use of Aliases and Synonyms

File-AID/RDX supports aliases and synonyms of tables in the Extract function. If you specify an alias
or synonym as a driving table, File-AID/RDX lists relationships associated with the base table and
extracts from the base tables.
210 File-AID/RDX Reference

Extract - MVS Driving Object

The Extract - MVS Driving Object screen shown in Figure 100 on page 210 is displayed when your
profile specifies that the driving object for an extract is an MVS file, or you enter the MVS command
in the Extract - DB2 Driving Object screen.

Use this screen to specify the name of the MVS file for which you want to extract related data.

Figure 100. Extract - MVS Driving Object

File-AID/RDX ----------- Extract - MVS Driving Object ----------------------

OPTION ===> SITE Profile: RDXQUICK

Primary Commands: DB2 driving object, Edit JCL, Go to submit job 

Specify file to drive the extract process from: 
File ===> FRSAMP.ORDERTAB 

Optional File Information: 
Record layout usage ===> (S = Single; X = XREF) 
Record layout file ===> 
Member name ===> (Blank or pattern for member list) 
XREF file ===> 
Member name ===> (Blank or pattern for member list) 

Specify Extract Options:
Edit Object Selection Criteria ===> N (Y = Yes; N = No) *Defined*

Specify Extract "TO" File Information: 
File Name ===> FRSAMP.EXTRACTM 
Edit Data Privacy Spec ===> (Y = Yes; N = No) *DCF*

Relationship information stored in: 
File Name ===> FRSAMP.RELATION 

The *Current Values* indicators to the right of certain extract option fields are display fields only
and are updated upon return from each of the extract options to reflect the current status and value
for the option.

The body of this screen consists of the following fields:

Specify File To Drive The Extract Process From Area

Use the fields in this area to specify the MVS file for which you want to retrieve relationship
information from the relationship file so you can extract related data. When specifying patterns in
the fields, File-AID/RDX searches the relationship file and presents selection lists.

File
Specify the MVS file name of the object from which you want to extract related data. To view a
list of files, specify a pattern. Valid pattern character is * (see Pattern Characters on page 27). If
you specify a pattern, the “Catalog Utility File List” shown in Figure 121 on page 236 is
displayed.

If the specified file name is not found in the relationship file File-AID/RDX displays the
Relationship Listing Window - No Relationships on page 235 where you can decide whether to
continue with a single object extract or start a new extract request.

File-AID/RDX supports extracting from Sequential (PS) files greater than

65,535 tracks (DSNTYPE=LARGE) when the MVS Operating System also
supports them.
Extract 211

Optional File Information Area

The following fields are not needed when the selected MVS file is found in the relationship file.
However, if the driving object file name is not in the relationship file, you must specify the layout
information when continuing with a single object extract.

Record layout usage

Indicate whether a single record layout (usage "S"), or an XREF (usage "X") had been used to
define the selection criteria. Only needed when no relationships have been defined for the MVS
file.

Record layout file

Specify the record layout file for the MVS object from which you want to extract related data. To
view a list of layout files, specify a pattern. Valid pattern character is * (see Pattern Characters on
page 27). If you specify a pattern, select a file from the “Catalog Utility File List” as shown in
Figure 121 on page 236.

Member name
Specify the member of the record layout file that contains the layout information for the MVS
object. Leave blank or use a pattern to narrow the search.

XREF file
Only needed if layout usage is X. Specify the XREF file name for the MVS object from which you
want to extract related data. Valid pattern character is * (see Pattern Characters on page 27). If
you specify a pattern, select a file from the “Catalog Utility File List” as shown in Figure 121 on
page 236.

Member name
Specify the member of the XREF file that contains the layout information for the MVS object.
Leave blank or use a pattern to narrow the search, see also Figure 123 on page 238.

Specify Extract Options Area

Edit Object Selection criteria

Enter Yes so you can specify selection criteria for the driving object. File-AID/RDX will display
Selection Criteria Menu screen (refer to Figure 162 on page 312) when you press Enter. Enter No
to extract all rows from the driving object.

Current Values displays *Defined* if selection criteria has already been defined.

Specify Extract "TO" File Information Area:

Use this area to specify the file to which File-AID/RDX will copy the extracted data and whether data
privacy rules should be applied.
212 File-AID/RDX Reference

File name
Specify the name of the file to which data will be extracted. You must include the member name
(in parentheses) when the file is a PDS. See Extract File on page 44 and File-AID/RDX Extract File
on page 377 for more information. If you specify a pattern, select a sequential file from the
“Catalog Utility File List” (see Figure 121 on page 236) after you entered one of the primary
commands. Remember, File-AID/RDX will not prompt for a member.

Edit Data Privacy Spec

Specify whether you want to change the current data privacy specifications. When data privacy
has been specified, File-AID/RDX will disguise the extracted data as part of the extract batch job
according to the disguise criteria defined in the Disguise Control file (DCF) or in the Dynamic
Privacy Rules Project (DPR). When you enter Y, File-AID/RDX will display the Data Privacy
Specification screen (refer to Figure 177 on page 341).

Current Values displays *DCF*, *DPR*, or *None* for the selected disguise option.

Relationship information stored in Area

File name
Specify the name of the file that contains the referential integrity and application relationship
information you want to use for the extract process. If you specify a pattern, select a file from the
“Catalog Utility File List” (see Figure 121 on page 236).

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

DB2 (D)
Switches from this panel to the single panel Extract - DB2 Driving Object prefilled with the
applicable information from the current profile. Refer to Extract - DB2 Driving Object on page
204.

EDIT (E)
Displays the JCL for this extract request. File-AID/RDX shows the Generated JCL panel where you
review and modify the extract JCL.

GO (G)
Submits this extract request. Before issuing the GO command, make sure you have completed all
the extract information. File-AID/RDX will also issue a message upon completion of the job.

MENU
Switches from this panel to the full Extract Menu. Only valid when profile setting Display Extract
Menu on page 62 is set to Y.
Extract 213

Extract Reference List

The Extract Reference List screen shown in Figure 101 is displayed when you

• Select Option 2, Extract, from the File-AID/RDX Primary Option Menu and your profile set it as
the first extract panel;
or
• Enter the REFERENCE command on an “Extract Menu” panel

Use this screen to select an extract request from the list or start a new extract request. File-AID/RDX
adds an extract request to the list whenever a request is saved from the Extract Menu. Extract requests
that originate from the “Single Panel Extract” function are not saved to a request file and thus not
included in the Extract Reference List.

If your reference list is empty, File-AID/RDX will display the Request File Member List screen,
listing the members of the request file specified in your profile, or if none is in your profile,
display either the DB2 Driving Object or MVS Driving Object screen so you can create a
new extract request.

The reference list is stored in your personal USER profile. If your USER profile file
(‘userid.midlevlqualifier.PROFILE’) does not exist, File-AID/RDX will create your USER profile
when you are saving an extract or load request.

You can also create a new extract request with the NEW command, or open a saved extract request
file with the REQUEST command. Use the REQUEST command to open extract criteria files created
with File-AID/RDX prior to Release 3.0.

Refer to Option G—Global User Defaults on page 82 for how to set the maximum number of list
entries for the reference list.

You may specify multiple line commands at a time. All line commands are processed before any
primary commands. When processing multiple commands File-AID/RDX displays a message like
“Processing line command 2 of 4” whenever it starts processing the next line command after the first.

Figure 101. Extract Reference List

File-AID/RDX ------------- ------- Row 1 to 6 of 6 

Extract Reference List
Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go C = Change Selection & Go S = Select M = Modify
I = Info D = Delete from list L = Lock U = Unlock

Request Extract File Name RT L YY/MM/DD
-------- ----------------------------------------------------- -- - -------- 
_ MVSSAMP TSOID01.FRSAMP.REQUEST E 11/01/03
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT E 01/02/18
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM E 01/02/04
_ TSOID01.FRSAMP.EXTRACT EL L 01/02/01
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT E 01/01/31
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2(EXTCUST) EL L 00/12/24
_ MVORDR TSOID01.FRSAMP.EXTRACT.ORDER E 99/08/24
******************************* Bottom of data ********************************

The lower part of the screen displays a listing of your recently referenced extract requests. Use one of
the line commands to either resubmit one of the extract requests or model a new request after it.

Request
Name of the extract request (member name in the saved extract request file or extract criteria
file). A blank entry means the request was saved to a sequential file.
214 File-AID/RDX Reference

Extract File Name

Name of the file containing the extracted data. If saved to a PDS the member name is displayed in
parentheses.

RT
Request Type. Identifies the extract request type:

Extract only request.

EL

Extract and Continue with Load request.

L
Locked Entry. Identifies whether the request is locked in the reference list or whether it is
allowed to roll off.

blank

not protected from roll over.

Locked in reference list; entry will not roll off the list.

YY/MM/DD
Date when the extract request was last saved or executed. The list entries are ordered with the
most recent date placed on top of the list.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

If the extract request has Checkpoint/Resumption Enabled, the Checkpoint

Confirmation window (see Checkpoint/Resumption Confirmation Windows
on page 349) asks whether to continue the extract request before
submitting when issuing either the C, G, or V line commands.

C (Change selection criteria & Go)

Repeat this extract request with new selection criteria for the driving object. File-AID/RDX then
displays the Driving Object Selection Criteria screen. After you specify the new selection criteria,
File-AID/RDX will submit the extract request.

D (Delete from list)

Removes this extract request from the extract reference list, but does not delete the member from
the extract request file itself.
Extract 215

G (Go)
Submits this extract request without any changes.

I (Info)
Displays the Request Details screen, which provides more comprehensive information about the
extract request. See Figure 102 for an example.

Figure 102. Request Details

File-AID/RDX ---------------- Request Details -------------------------------

Command ===>

Request Information: 
Request File Name . : TSOID01.FRSAMP.REQUEST 
Member Name . . . . : MVSSAMP 
Request Type . . . . : EXTRACT 
Description . . . . : MVS 
Reference Date . . . : 2011/01/03 Reference Time: 00:00:07 

Driving Object Information: 
SSID . . . . . . . . : 
Name . . . . . . . . : MVS - TSOID01.FRSAMP.ORDERTAB 

Extract Information: 
Extract File Name . : TSOID01.FRSAMP.OUT 
Summary File Name . : TSOID01.FRSAMP.TAPECNTL 
Disguise Control File: 
Repository Name: 
Project Name: 
Extract Date . . . . : 2011/01/03 Extract Time : 12:00:01 

Relationship Information: 
File Name . . . . . : TSOID01.FRSAMP.RELATION 

L (Lock)
Protects this entry from rolling off the extract reference list.

M (Modify)
Selects this extract request, displays the Modify Extract Request panel for you to change or
“clone” an existing extract request. See also Modify Extract Request on page 227.

S (Select)
Selects this extract request and displays the Extract Menu prefilled with all the information from
this request. See also Extract Menu on page 239.

If your profile specifies not to display the Extract Menu, File-AID/RDX will
submit the request immediately.

V (View JCL)
Displays the JCL for this extract request. File-AID/RDX shows the ISPF/PDF EDIT Screen—File-
AID/RDX-generated JCL panel (page 354) where you review and modify the extract JCL.
216 File-AID/RDX Reference

U (Unlock)
Does not protect this entry from rolling off the extract reference list.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

DETAIL (D)
Expands the one-line display for each request into a two-line display. The additional line shows
the request description. See Figure 103 for an example. Detail is a toggle switch so enter Detail
again to return to the original format.

Figure 103. Extract Reference List - DETAIL Screen

File-AID/RDX ------------- Extract Reference List--------- Row 1 to 6 of 6

Command ===> Scroll ===> CSR 

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go C = Change Selection & Go S = Select M = Modify
I = Info D = Delete from list L = Lock U = Unlock

Request Extract File Name RT L YY/MM/DD
-------- ----------------------------------------------------- -- - --------
_ MVSSAMP TSOID01.FRSAMP.EXTRACT E 11/01/03
Description: MVS 
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT E 04/02/18
Description: This extract uses Acct number 
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM E 04/02/04
Description: DB2-FR.PRODUCT_CONTRACT 
_ TSOID01.FRSAMP.EXTRACT EL L 04/02/01
Description: This extract selects region 10 
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT E 04/01/31
Description: MVS-FRSAMP.CUSTOMER 
_ MVORDR TSOID01.FRSAMP.EXTRACT.ORDER E 99/08/24
Description: MVS-FRSAMP.ORDER 
******************************* Bottom of data ********************************

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.

Find looks for matches in the request detail information for each list entry. When a match is
found and is not visible in the displayed row, use the I (info) line command to display the detail
information.

NEW (N)
Starts a new extract request based on your current profile. File-AID/RDX displays either the DB2
or MVS Driving Object screen as set in your profile (see Figure 99 or Figure 100).

You can also include one of the optional parameters, DB2 or MVS, to display the respective
Driving Object screen.

REQUEST (REQ)
Opens a saved extract request file. You also use the REQuest command to open extract criteria
files created with File-AID/RDX prior to Release 3.0. Refer to Figure 99 for more information.
Extract 217

File-AID/RDX opens the request file specified in your current profile or prompts for the file name
when none is in your profile.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 104 for an example. Size is a toggle switch, so enter Size again to return to the
original format.

Figure 104. Extract Reference List - Size Screen

File-AID/RDX ------------- Extract Reference List --------- Row 1 to 6 of 6

Command ===> SCROLL ===> CSR 
Request Extract File Name RT L YY/MM/DD
_ MVSSAMP TSOID01.FRSAMP.REQUEST E 11/01/03
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT E 04/02/18
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM E 04/02/04
_ TSOID01.FRSAMP.EXTRACT EL L 04/02/01
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT E 04/01/31
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2(EXTCUST) EL L 03/12/24
_ MVORDR TSOID01.FRSAMP.EXTRACT.ORDEER E 03/08/24
****************************** Bottom of data ********************************
218 File-AID/RDX Reference

Request File Member List

The Request File Member List Screen shown in Figure 105 is displayed when you

• Select Option 2, Extract, from the File-AID/RDX Primary Option Menu and your profile set it as
the first extract panel;
or
• Enter the REQuest command in an extract panel

File-AID/RDX will also display the Request File Member List Screen, when
your profile lists the Extract Reference List as the first extract panel, but the
list is empty and your profile includes an extract request file.

This screen displays the member list of the specified request file or an extract criteria file created with
File-AID/RDX prior to Release 3.0. Use one of the line commands to select a member for your extract
request.

Figure 105. Request File Member List Screen

File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8

Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, REFerence
Line commands: G = Go C = Change Selection & Go S = Select M = Modify SSID
D = Delete R = Rename

Request File ===> FRSAMP.EXTCRIT 

Member Description Changed
-------- -------------------------------------------------- ---------- 
_ DB2VSAM db2 to vsam extract 2004/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 2004/08/13 
_ MIKE1 Member List 2004/05/10 
_ NODB2 mcust with db2 deleted 2004/01/25 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 2004/08/30
_ PART1 Member List 2003/02/11
_ SELCUST test select customer 2002/01/28 
_ TESTA test saving the criteria 2001/04/12
******************************* Bottom of data ********************************

Request File
The request file name comes from your current profile. If your profile does not include a request
file, File-AID/RDX will prompt for one. Enter a new file name to change to a different saved
request file or extract criteria file and File-AID/RDX will display its member list.

Clear the field and File-AID/RDX displays the Extract Reference List (page 213).

The lower part of the screen displays a listing of the file’s members.

Member
Member name in the request file or extract criteria file. The member names are displayed in
alphabetical order.
Extract 219

Description
Text that was entered in the Description field when the extract request was created. If you left the
field blank, File-AID/RDX sets the description to the driving object type and name.

Changed
Date when the member was last saved.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

If the extract request has Checkpoint/Resumption Enabled, the Checkpoint

Confirmation window (Checkpoint/Resumption Confirmation Windows on
page 349) asks whether to continue the extract request before submitting
when issuing either the C, G, or V line commands.

C (Change selection criteria & Go)

Repeats this extract request with new selection criteria for the driving object. File-AID/RDX then
displays the Object Selection Criteria (page 301). After you specify the new selection criteria, File-
AID/RDX will submit the extract request.

D (Delete)
Delete this member from the request file. Displays the Delete Confirmation window (Figure 106).

Figure 106. Delete Confirmation window

Delete Confirmation 
COMMAND ===> 

Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 

Member to be Deleted: TESTA 


ENTER to confirm delete 
END to return to Request File Member List 



G (Go)
Submits this extract request without any changes.

M (Modify)
Selects this extract request, displays the Modify Extract Request panel for you to change or
“clone” an existing extract request. See also Modify Extract Request on page 227.

R (Rename)
Rename the request member. The Rename Confirmation window (Figure 107) allows you to enter
a new name for the request file member.
220 File-AID/RDX Reference

Figure 107. Rename Confirmation window

Rename Confirmation 
COMMAND ===> 

Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 

Member to be Renamed: TESTA 
New Member name ===> 


ENTER to confirm rename 
END to return to Request File Member List 



S (Select)
Selects this extract request and displays the Extract Menu prefilled with all the information from
this request. See also Extract Menu on page 239.

V (View JCL)
Displays the JCL for this extract request. File-AID/RDX shows the ISPF/PDF EDIT Screen—File-
AID/RDX-generated JCL panel (page 354) where you review and modify the extract JCL.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

FIND (F)
Searches the member list for the specified string and scrolls the list to display the first matching
entry at the top of the displayed entries. Use RFind to repeat the search.

NEW (N)
Starts a new extract request based on your current profile. File-AID/RDX displays either the DB2
or MVS Driving Object screen as set in your profile (see Figure 99 or Figure 100).

You can also include one of the optional parameters, DB2 or MVS, to display the respective
Driving Object screen.

REFERENCE (REF)
Displays your Extract Reference List panel. Refer to Figure 101 on page 213 for more information.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 108 for an example. Size is a toggle switch so enter Size again to return to the
original format.
Extract 221

Figure 108. Request File Member List - Size Screen

File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8 

Command ===> Scroll ===> CSR
Member Description Changed
_ DB2VSAM db2 to vsam extract 2001/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 2001/08/13 
_ MIKE1 Member List 2002/05/10 
_ NODB2 mcust with db2 deleted 2001/01/25 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 2001/08/30
_ PART1 Member List 2002/02/11
_ SELCUST test select customer 1999/01/28 
_ TESTA test saving the criteria 2001/04/12
******************************* Bottom of data ********************************

Extract Requests from Releases prior to Release 4.0

File-AID/RDX accepts extract requests created with an earlier release of File-AID/RDX than Release
4.0.

When selecting such a request with the S or M line command, File-AID/RDX will convert the request
to the new Release 4.0 format. For example, File-AID/RDX will set the navigation and sampling
controls to approximate the old extract method (OPTIMUM, STANDARD, MOST, or DETAILED).
However, the extract results may differ as an exact conversion may not be possible.

Table 11. Conversion of Old Extract Methods

Navigation OPTIMUM MOST STANDARD DETAILEDa
Controls
Direct Y Y Y *
Parents Y Y Y *
Siblings N Y N *
Indirect N Y Y *

a. For Detailed, the controls are converted as specified per individ-

ual relationship

Other new extract features will default to the values specified in the current profile or current session.

In the Extract Menu review the resulting conversion before submitting the extract request. Pay
particular attention to Sampling Controls like

• Maximum Rows from an object,

• Dependents-per-parent
• Extract every n th row for Db2 objects

and Navigation Control settings for

• Sibling paths
• Indirect Dependent paths
• Many to many relationships

Sampling Controls have been moved from the Selection Criteria to the Extract Scope Object View and
Relationship Sampling Criteria panels.

When submitting a pre-Release 4.0 request directly for batch execution, for
example with the G (Go) or C (Change and Go) line command (page 214
or page 219), the request will be converted and executed using a temporary
request file.
222 File-AID/RDX Reference

DB2 Driving Object

The DB2 Driving Object screen shown in Figure 109 is displayed when you enter the NEW command
in the Extract Reference List or the Request File Member List screens and your profile specifies that
the driving object is a Db2 object, or you enter the DB2 command in the MVS Driving Object screen.

Use this screen to specify a Db2 object to drive the extract.

Figure 109. DB2 Driving Object

File-AID/RDX ------------- DB2 Driving Object -------------------------------

Command ===> 

Primary commands: MVS driving object 

Specify table to drive extract process from: 
SSID ===> DSN 
Location ===> (* or pattern for selection list)
Creator ===> FRSAMP (* or pattern for selection list)
Table Name ===> * (* or pattern for selection list)

Relationship Information:
File name or pattern ===> 'TSOID01.FRSAMP.RELATION' 

NOTE: For single object extract leave relationship file blank

ENTER to continue

After entering the information for the new Db2 driving object, press ENTER to proceed to the Extract
Menu.

The body of this screen consists of the following fields:

Specify Table To Drive Extract Process Area

Use the fields in this area to specify the Db2 table for which you want to retrieve relationship
information from the relationship file so you can extract related data. When specifying patterns in
the fields, File-AID/RDX searches the relationship file and presents selection lists.

SSID
Displays the current Db2 subsystem ID. Type over this field to connect to a new Db2 subsystem.
If you leave the Location field blank, the table you specify to drive the extract must exist in the
Db2 subsystem displayed here.

Location
Specify the location of the table you want to drive the extract if it resides in a remote Db2
subsystem. The location you enter must be defined in the Db2 system catalog table,
SYSIBM.LOCATIONS.

Leave this field blank if the table you want to drive the extract is in the Db2 subsystem in the
SSID field.

The Extract from Image Copy option is not available when extracting from
a remote location (see also Extract from Image Copy on page 251).
Extract 223

Creator
Specify the authorization ID of the owner of the table, view, synonym, or alias that you want to
drive the extract process. You can enter a pattern in this field. Valid pattern characters are %, _,
and * (see Pattern Characters on page 27). If you specify a pattern, File-AID/RDX searches the Db2
catalog and displays matches in a Table List pop-up window.

Table Name
Specify the name of the table, view, alias, or synonym that you want to drive the extract process.
For more information about how File-AID/RDX supports views, aliases, and synonyms in Extract,
see Use of Db2 Views on page 208 and Use of Aliases and Synonyms on page 223.

You can enter a pattern in this field. Valid pattern characters are %, _, and * (see Pattern
Characters on page 27). If you specify a pattern, File-AID/RDX searches the Db2 catalog and
displays matches in a Table List pop-up window.

Relationship Information:

File name or pattern

Specify the name of the file that contains the referential integrity and application relationship
information you want to use for the extract process. To view a list of files, specify a pattern. Valid
pattern character is * (see Pattern Characters on page 27). If you specify a pattern, select a file
from the “Catalog Utility File List” as shown in Figure 121 on page 236.

When you leave this relationship file field blank, File-AID/RDX will create a single object extract.

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:

MVS (M)
Switches to the MVS Driving Object panel prefilled with the applicable information from your
profile. Refer to MVS Driving Object on page 233.

Use of Db2 Views

File-AID/RDX supports views of Db2 tables in the Extract function. If you specify a view as the
driving table, File-AID/RDX lists relationships defined for the view, not the underlying base table.
File-AID/RDX then extracts data from the view specified as the driving table/view and from all tables
and views related to the driving table/view.

1. Extracting from complex views may create unloadable data. Specifying

the base table(s) is recommended.
2. The Extract from Image Copy option is not available for views.

Use of Aliases and Synonyms

File-AID/RDX supports aliases and synonyms of tables in the Extract function. If you specify an alias
or synonym as a driving table, File-AID/RDX lists relationships associated with the base table and
extracts from the base tables.
224 File-AID/RDX Reference

Relationship Listing Window for Db2 Objects

When you are creating a NEW extract request, File-AID/RDX searches the relationship file for
relationship definitions that match the Object Name name you specified as the driving object. For
Db2 objects, if the exact match cannot be found in the relationship file, File-AID/RDX searches for
other existing relationship definitions that could be applied for the extract. File-AID/RDX only uses
the Table name portion of driving object in searching for relationship definitions. If one or more
relationship definitions match the specified Table Name, File-AID/RDX displays the Relationship
Listing window.

In the case of Db2 objects, the Relationship Listing window provides a list of objects that have
relationships defined in the File-AID/RDX relationship file. You can use the relationship definitions
from any given set of objects to extract data from another set of objects that contain the same kind of
data. When you select a relationship with a creator other than the creator specified for the driving
table, the relationships defined for the driving table may differ from those of the selected table. If
File-AID/RDX’s relationship validation routine cannot detect the proper relations in the Relationship
file it will issue a warning (see Check Extract Warning on page 285).

For example, you could use relationship definitions for the production subsystem to extract data
from a similarly related set of tables that reside on the acceptance subsystem as long as no
relationships have been defined for the driving table on the acceptance subsystem. Use this screen to
select the table for which there exists a relationship definition that you want to use to extract data
from a set of tables.

If File-AID/RDX finds a single table that matches both the table name and
creator, it bypasses the Relationship Listing window.

Figure 110. Relationship Listing Window—Multiple Relationship Definitions

File-AID/RDX Driving Object - DB2 

Command ===> 
Relationship Listing 
Primary Comma Row 1 to 6 of 6 
Command ===> SCROLL ===> CSR 
Specify table 
SSID Multiple relationships exist for object: EMP 
Location 
Creator Enter 'S' to select relationship definition for extract 
Table Name 
CMD Object SSID 
Relationship --- -------------------------------------------------- ---- 
File Name o _ LOCATION.CWS029.EMP DSNG 
_ LOCATION.CWS037.EMP DSN 
_ LOCATION.CWX0023.EMP DSN 
_ LOCATION.CWX0039.EMP DSN 
_ LOCATION.CWX0230.EMP DSN 
_ LOCATION.CWX0330.EMP DSN 

If there are more valid relationships than will fit in this window, you can scroll the list of
relationships up and down using standard scrolling commands. See Scrolling on page 31 for more
information.

The screen heading lines contain screen title, row indicator, COMMAND field, and scroll amount
input field.

The body of this scrollable window consists of the following fields:

Extract 225

CMD
Enter the S line command in this field to select the relationship definition to use in the Extract
process. The S line command selects the relationship definition of the selected object for the
driving object.

Object
Displays a list of objects that have relationship definitions in the relationship file that match the
value you specified in the Table Name field on the Driving Object - DB2 screen.

The creator of the table you specified to drive the extract is part of this list when RI and/or
application relationships have been defined for it in the relationship file.

SSID
Displays the subsystem ID of each table on the list.

No Relationships Exist
If File-AID/RDX does not find any tables that match the specified driving table, it displays a message
in the Relationship Listing window that indicates no relationships are defined in the relationship file
for the driving table. Press Enter to continue with a single table extract. Or, enter the END command
and specify a different relationship file, or different driving object. Or use Option 1, Relationships,
to load referential integrity relationships from the Db2 catalog or to generate AR relationships,
respectively.

Partially Matching Relationship Panel for Db2 Objects

If File-AID/RDX only finds a single partially matching relationship, it displays the Partially Matching
Relationship panel where it displays the information for the specified driving table next to the
partially matched information in the relationship file.

Figure 111. Partially Matching Relationship

File-AID/RDX --------- Partially Matching Relationship ----------------------- 

Command ===> Scroll ===> CSR 

A single partial matching relationship was found: 
Entered Match 
SSID : D801 D801 
Location : D801CW01 D801CW01 
Creator : FARDX FRSAMP 
Table Name : ORDER_TABLE ORDER_TABLE 

Do you wish to continue with: _ 
1 - Single table extract 
2 - Partially matching relationship) 

Press ENTER to continue 
Enter END to terminate processing 


The body of this scrollable window consists of the following fields:

226 File-AID/RDX Reference

SSID
Entered: Displays the subsystem ID of the specified driving table.

Match: Displays the subsystem ID of the matching table in the relationship file.

Location
Entered: Displays the remote location ID of the specified driving table.

Match: Displays the remote location ID of the matching table in the relationship file.

Creator
Entered: Displays the creator ID of the specified driving table.

Match: Displays the creator ID of the matching table in the relationship file.

Table
Entered: Displays the table name of the specified driving table.

Match: Displays the table name of the matching table in the relationship file.

Do you wish to continue with

Enter either 1 or 2.

1: Single table extract. The resulting extract will NOT extract any related data.

2: Partially matching relationship. The resulting extract will extract any related data as defined
for the matching table in the relationship file. Any related objects that are missing will be
excluded from the extract.

Press Enter to continue with the extract.

Or, enter the END command and specify a different relationship file, or different driving object. Or
use Option 1, Relationships, to load referential integrity relationships from the Db2 catalog or to
generate AR relationships, respectively.
Extract 227

Modify Extract Request

The Modify Extract Request screen shown in Figure 112 is displayed when you enter the M line
command in the Extract Reference List or the Request File Member List screens.

Use this screen to modify or “clone” an existing extract request by changing the Db2 subsystem and
object names from which you want to extract related data from and apply the relationships and
criteria as specified in the selected extract request.

The “cloning” functionality allows you to create an extract request on one Db2 subsystem or MVS
environment and then easily modify it to run on a different subsystem or MVS environment which
has the same objects but with different names.

When you modify a saved extract request, File-AID/RDX displays the list of all object names in the
request, including all related and unrelated Db2 and MVS objects along with any supporting files.
Now you can specify new names for the listed objects defined in the extract request and save the
request with a new file name.

File-AID/RDX does not verify the modified object names until the “cloned”
request is executed as the intention is to allow the new request to be sent to
a remote system and the remote objects may currently not be available for
validation.

Disguise Considerations
If there is no Disguise Criteria defined for the modified object name, File-AID/RDX applies the
Disguise Criteria defined for the original object name. Of course, if there is Disguise Criteria defined
for the modified object name, File-AID/RDX will use that and not the criteria defined for the original
object.

Figure 112. Modify Extract Request

File-AID/RDX ------------- Modify Extract Request ---------------------------

Option ===> 

Current Extract process from: 
SSID . . . . . .: DSN 
Location. . . . .: 

Enter new DB2 Subsystem ID: 
SSID ===> 
Location ===> 

Modify Object names ===> N (Y = Yes; N = No) 

ENTER to continue 

Enter the information for the new Db2 subsystem, if your extract request includes Db2 objects,
specify whether you also want to modify the object names in your extract request, then press ENTER
to continue.

The body of this screen consists of the following fields:

Current Extract Process From Area

These fields display the Db2 subsystem ID and remote location ID as saved in the selected extract
request.
228 File-AID/RDX Reference

SSID
Displays the Db2 subsystem ID. Blank if no Db2 objects are included.

Location
Displays the remote location ID of the Db2 subsystem.

Enter New DB2 Subsystem ID Area

Use the fields in this area to specify a new Db2 subsystem and remote location ID for the new extract
request.

SSID
Prefilled with the Db2 subsystem ID of the original extract request. Type over this field to specify
a different Db2 subsystem for the modified request.

Location
Specify the remote location name of the Db2 subsystem. If you specify a different SSID from the
original request, you must also specify its remote location name here.

The Extract from Image Copy option is not available when extracting from
a remote location. (see also Extract from Image Copy on page 251).

Modify Object names

Specify whether you want to modify the object names in your extract request or not.

Enter Y (Yes) to modify object names in the request. File-AID/RDX displays the Modify
Extract Request - Object Names panel (Figure 113) listing all object names you can modify for
the “cloned” request.

Enter N (No - default) if you do not want to modify object names in the request.

Modify Extract Request - Object Names

The Modify Extract Request - Object Names screen shown in Figure 113 is displayed when you enter a
Y in the Modify Object names field of the Modify Extract Request screen.
Extract 229

Figure 113. Modify Extract Request - Object Names

File-AID/RDX ------ Modify Extract Request - Object Names Row 1 to 13 of 13 

Option ===> 

Primary Commands: Change, Detail, Find, Size 
Line Commands: R = Restore 

SSID: DSN Location: 
Object Name Object Type 
--------------------------------------------- ------------------------------ 
_ TSOID01.FRSAMP.EXTPDS EXTRACT FILE NAME 
_ TSOID01.FRSAMP.EXTCRIT2 REQUEST FILE NAME 
_ TSOID01.FRSAMP.RELATION RELATIONSHIP FILE NAME 
_ TSOID01.VAR1M0.PROFILE PROFILE FILE NAME 
_ TSOID01.FRSAMP.DISGUISE DISGUISE CONTROL FILE NAME 
_ FRSAMP.ORDER_TABLE DB2 TABLE NAME 
_ FRSAMP.CUSTOMER_TABLE DB2 TABLE NAME 
_ FRSAMP.CONTACT_TABLE DB2 TABLE NAME 
_ TSOID01.FRSAMP.CUSTOMER FILE OBJECT NAME 
_ TSOID01.FRSAMP.LAYOUTS(CUSTOMER) MVS LAYOUT FILE 
_ FRSAMP.ORDER_LINE_TABLE DB2 TABLE NAME 
_ FRSAMP.PART_TABLE DB2 TABLE NAME 
_ FRSAMP.SUPPLIER_TABLE DB2 TABLE NAME 
******************************* Bottom of data ********************************

File-AID/RDX displays the list of all object names in the request, including all related and unrelated
Db2 and MVS objects along with any supporting files. Now you can specify new names for the listed
objects defined in the extract request. File-AID/RDX does not verify the modified object names until
the “cloned” request is executed. When you have modified all the object names you wanted
modified, enter the END command to save the “cloned” extract request.

SSID
Displays the Db2 subsystem ID. Blank if no Db2 objects are included.

Location
Displays the remote location ID of the Db2 subsystem.

Object Name
Lists all object names in the extract request file that you can modify. You can manually overtype
the old name with the new name or you can use the CHANGE primary command to make global
changes.

Object Type
Identifies the kind of object the object name represents in the extract request file. The list
includes all objects to be extracted as well as all supporting files.

Supporting files are all MVS files referenced within the request; this includes the following files

• Layouts
• XREF
• Input (External) Key File
• Output Key File
• Extract File
• Extract Request File
• Disguise Control File (DCF)
230 File-AID/RDX Reference

• Profile dataset
• Relationship File
• XREF and Layout datasets for generated layouts
• DBDLIBs
• IMS Extract JCL dataset

Line Command
The following File-AID/RDX-specific line command is valid on this screen:

R (Restore original name)

Restores the original object name for the selected object.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

CHANGE (C)
Change allows global changes to be made to the object names in the extract request file. When
entered, specify the values to change in the CHANGE Command Window - Modify Extract
Request. File-AID/RDX will change all matching strings in the listed object names.

CHANGE Command Window

When you enter the CHANGE command, File-AID/RDX displays the CHANGE Command
Window - Modify Extract Requestas shown in Figure 114.

Figure 114. CHANGE Command Window - Modify Extract Request



File-AID/RDX -------------- CHANGE COMMAND ------------------- 
Command ===> 

Change ALL occurrences of "from string" value to "to string" 
From string ===> 
To string ===> 

END to process and return 




Enter the Change ‘From string’ and the Change ‘To string’ values you want to change globally for
all objects. Then press END to execute the CHANGE command. File-AID/RDX will change all
matching strings in the listed object names.

From string
Enter the current From (old) string you want to change to the To (new) string in the object
name list.
Extract 231

To string
Enter the To (new) string you want to replace the From (old) string with in the specified
object name list.

DETAIL (D)
Expands the one-line display for each object name into a two-line display. The top line displays
the new object name while the indented additional line shows the original object name. See
Figure 115 for an example. Detail is a toggle switch so enter Detail again to return to the original
format.

Figure 115. Modify Object Names - DETAIL Screen

File-AID/RDX ------------- Modify Object Names------------ Row 1 to 7 of 13 

Option ===> Scroll ===> PAGE

Primary Commands: Change, Detail, Find, Size 
Line Commands: R = Restore 

SSID: D801 Location: 
New Object Name / Original Object Name 
---------------------------------------------------------------------------- 
_ TSOID01.FRSAMP.EXTPDS 
TSOID01.FRSAMP.EXTPDS 
_ TSOID01.FRSAMP.EXTCRIT2 
TSOID01.FRSAMP.EXTCRIT2 
_ TSOID01.FRSAMP.RELATION 
TSOID01.FRSAMP.RELATION 
_ TSOID01.VAR1M0.PROFILE 
TSOID01.VAR1M0.PROFILE 
TSOID01 FRSAMP DISGUISE

FIND (F)
Displays the FIND COMMAND window where you enter the alphanumeric string you want to
search for. File-AID/RDX searches the list of object names for the first occurence of the specified
string and scrolls the list to display the first matching entry at the top of the displayed entries.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 104 for an example. Size is a toggle switch, so enter Size again to return to the
original format.

Figure 116. Extract Reference List - Size Screen

File-AID/RDX ------ Modify Extract Request - Object Names Row 1 to 13 of 13 

Option ===> 

Object Name Object Type 
--------------------------------------------- ------------------------------ 
_ TSOID01.FRSAMP.EXTPDS EXTRACT FILE NAME 
_ TSOID01.FRSAMP.EXTCRIT2 REQUEST FILE NAME 
_ TSOID01.FRSAMP.RELATION RELATIONSHIP FILE NAME 
_ TSOID01.VAR1M0.PROFILE PROFILE FILE NAME 
_ TSOID01.FRSAMP.DISGUISE DISGUISE CONTROL FILE NAME 
_ FRSAMP.ORDER_TABLE DB2 TABLE NAME 
_ FRSAMP.CUSTOMER_TABLE DB2 TABLE NAME 
_ FRSAMP.CONTACT_TABLE DB2 TABLE NAME 
_ TSOID01.FRSAMP.CUSTOMER FILE OBJECT NAME 
_ TSOID01.FRSAMP.LAYOUTS(CUSTOMER) MVS LAYOUT FILE 
_ FRSAMP.ORDER_LINE_TABLE DB2 TABLE NAME 
_ FRSAMP.PART_TABLE DB2 TABLE NAME 
232 File-AID/RDX Reference

When you have modified all the object names you wanted modified, enter the END command to save
the “cloned” extract request.

Save Cloned Extract Request

The Save Extract Request screen shown in Figure 117 is displayed when you enter the END command
in either the Modify Extract Request or Modify Extract Request - Object Names screen.

Figure 117. Save Cloned Extract Request

File-AID/RDX --------------- Save Extract Request ---------------------------

COMMAND ===> 

Specify Extract Request File Information: 
File name ===> 
Member ===> 
Description ===> 

NOTE: Extract Request includes Relationship and Selection Criteria
CANCEL To Cancel Save Request 
END to process and return 

Use this screen to save the cloned extract request.

Press Enter to process the file information. The saved request will also appear in your Extract
Reference List (see Extract Reference List on page 213).

The body of the Save Cloned Extract Request window consists of the following fields:

File Name
Specify the name of the file where you want to save the extract request. It is prefilled with the
new object name for the extract request file you specified in the Modify Extract Request - Object
Names screen. You can save the request to existing files. Existing files must conform to the format
outlined for the extract request file in File-AID/RDX Extract/Load/Delete Request File on page
368.

If you specify a new file, you must specify the following allocation parameters in the Create New
File screen (Figure 175 on page 334).

Pre-Release 4.3 extract/load request files have fixed or fixed-blocked

(RECFM=F or RECFM=FB) record format. When saving a Pre-Release 4.3
request file, File-AID/RDX will issue an invalid format message. Specify a new
name to save the request file in variable-blocked (RECFM=VB) format.

Member
If the file is partitioned, specify the name of the member to contain the extract criteria.

Description
Enter a short description of the extract criteria. This description is displayed in the Extract Menu
and the Extract Reference List. Using this description is a helpful way to document your extract
criteria.
Extract 233

SAVE Confirmation
When saving an Extract, Load, or delete request File-AID/RDX checks to see if the member already
exists. If the member already exists, the Save Confirmation window (Figure 118) displays:

Figure 118. Save Confirmation window


File-AID/RDX -------------------- Save Confirmation --------------------
Command ===> 

The Following member exists and will be replaced: 
Request File . . . .: 'TSOID01.FRSAMP.EXTCRIT' 
Member to be saved : MVSKEY 

ENTER to confirm Save and replace existing member 
END return to Save Request enter a different member name 



Press Enter to confirm overwriting the existing file or member name. Press End to cancel the Save
request and return to the Save Extract Request panel where you can enter another file or member
name.

MVS Driving Object

The MVS Driving Object screen shown in Figure 119 is displayed when you enter the NEW command
in the Extract Reference List or the Request File Member List Screen screens and your profile specifies
that the driving object is an MVS file, or you enter the MVS command in the DB2 Driving Object
screen.

Use this screen to specify the name of the MVS file for which you want to extract related data. All
fields are prefilled with information from your current profile.

Figure 119. MVS Driving Object

File-AID/RDX ------------- MVS Driving Object-------------------------------

Option ===> 

Primary Commands: DB2 driving object 

File to drive the extract process from: 
File name ===> 

Optional File Information: 
Record layout usage ===> (S = Single; X = XREF) 
Record layout file ===> 
Member name ===> 
XREF file ===> XREF 
Member name ===> 

Relationship Information: 
File name or pattern ===> 'TSOID01.FRSAMP.RELATION' 

NOTE: For single object extract leave relationship file blank 


After entering or viewing the driving object information, press ENTER to proceed to the Extract
Menu.
234 File-AID/RDX Reference

File To Drive Extract Process From Area

Use the File Name field in this area to specify the MVS file for which you want to retrieve relationship
information from the relationship file so you can extract related data. When specifying patterns in
the fields, File-AID/RDX presents selection lists and then searches the relationship file.

File name
Specify the MVS file name of the object from which you want to extract related data. To view a
list of files, specify a pattern. Valid pattern character is * (see Pattern Characters on page 27). If
you specify a pattern, select a file from the “Catalog Utility File List” as shown in Figure 121 on
page 236.

If the file name is found in the relationship file, File-AID/RDX uses the layout information as
stored in the relationship file, not as entered in the Optional File Information fields.

If the MVS file is not in the relationship file, File-AID/RDX will ask you whether to continue with
a single object extract or restart your extract request (see Figure 120 on page 235).

File-AID/RDX supports extracting from Sequential (PS) files greater than

65,535 tracks (DSNTYPE=LARGE) when the MVS Operating System also
supports them.

Optional File Information Area

The following fields are not needed when the selected MVS file is found in the relationship file.
However, if the driving object file name is not in the relationship file, you must specify the layout
information when continuing with a single object extract.

Record layout usage

Indicate whether a single record layout (usage "S"), or an XREF (usage "X") had been used to
define the selection criteria. Only needed when no relationships have been defined for the MVS
file.

Record layout file

Specify the record layout file for the MVS object from which you want to extract related data. To
view a list of layout files, specify a pattern. Valid pattern character is * (see Pattern Characters on
page 27). If you specify a pattern, select a file from the “Catalog Utility File List” as shown in
Figure 121 on page 236.

Member name
Specify the member of the record layout file that contains the layout information for the MVS
object. Leave blank or use a pattern to narrow the search.

XREF file
Only needed if layout usage is X. Specify the XREF file name for the MVS object from which you
want to extract related data. Valid pattern character is * (see Pattern Characters on page 27). If
you specify a pattern, select a file from the “Catalog Utility File List” as shown in Figure 121 on
page 236.
Extract 235

Member name
Specify the member of the XREF file that contains the layout information for the MVS object.
Leave blank or use a pattern to narrow the search, see also Figure 123 on page 238.

Relationship Information:

File name or pattern

Specify the name of the file that contains the application relationship information you want to
use for the extract process. To view a list of files, specify a pattern. Valid pattern character is * (see
Pattern Characters on page 27). If you specify a pattern, select a file from the “Catalog Utility File
List” as shown in Figure 121 on page 236.

When you leave this relationship file field blank, File-AID/RDX will create a single object extract.

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:

DB2 (D)
Switches to the DB2 Driving Object panel prefilled with the applicable information from your
profile. Refer to DB2 Driving Object on page 222.

Relationship Listing Window—No Relationships

If the file name you specified as the driving object is not found in the relationship file, File-AID/RDX
will ask you whether to continue with a single object extract or restart your extract request (see Figure
120 on page 235).

Figure 120. Relationship Listing Window - No Relationships

File-AID/RDX ------------- MVS Driving Object -------------------------------

Option ===> 
Relationship Listing 
Primary Commands: D 
Command ===> 
File to drive the e 
File name No relationships exist for: 
'TSOID01.FRSMP.ORDERTAB' 
Optional File Infor 
Record layout usa Press ENTER to process a single table extract 
Record layout fil Enter END to terminate processing 
Member name 
XREF file 
Member name ===> (Blank or pattern for member list) 

Relationship Information: 
File name or pattern ===> 'TSOID01.FRSAMP.RELATION' 

If you press ENTER for a single object extract, File-AID/RDX will use the optional file information you
specified on the MVS Driving Object panel.

MVS Catalog Utility File List

When specifying a pattern in any of the file name fields in the MVS Driving Object panel, File-
AID/RDX searches the MVS catalog and displays any matches. Select the file name you want to place
in the applicable field with the S line command. The message in the top line indicates for which field
the list is displayed:

• Select File (driving object or relationship file)

236 File-AID/RDX Reference

• Select Record Layout

• Select XREF file

Figure 121. MVS Catalog Utility File List (for Pattern FR*.ORDERTAB)

File-Aid/RDX ------------- Catalog Utility File List ------------- Select File 

Command ===> SCROLL ===> CSR 
----- D A T A S E T N A M E -------------- 
TSOID01.FRKFL.ORDERTAB NON-VSAM MIGRAT 
TSOID01.FRKFL.ORDERTAB.DATA NON-VSAM MIGRAT 
TSOID01.FRKFL.ORDERTAB.INDEX NON-VSAM MIGRAT 
S TSOID01.FRSAMP.ORDERTAB CLUSTER PRD981 
TSOID01.FRSMP.ORDERTAB CLUSTER PRD908 
TSOID01.FRSMP1.ORDERTAB CLUSTER PRD970 
TSOID01 FRSMP2 ORDERTAB NON VSAM MIGRAT

Field Descriptions

Dataset Name
File names that match the entered file name pattern.

Type
Catalog entry type. Types that may be displayed include: CLUSTER, DATA, INDEX, ALT INDEX,
PATH, NON-VSAM, GDG BASE, USER CTLG, ALIAS, and PAGESPACE.

Volume
Volume on which the file is stored. Multi-volume files are identified by the + (plus sign)
following the Volume field.

PDS Processing Options

A PDS Processing Options screen, as shown in Figure 122, is displayed when the file name on the
MVS Driving Object screen refers to a partitioned dataset (PDS). It is used to specify member selection
values to choose members based on a name mask, name range, the userid for last modification, and
creation and modification date ranges.

To display a nonselective member list, leave all member selection options blank on the PDS
Processing Options screen and press Enter.
Extract 237

Figure 122. PDS Processing Options Screen

File-Aid/RDX ----------------- PDS Processing Options ------------------------

Command ===> 


Layout File: TSOID01.FRSAMP.LAYOUTS 







Specify Member Selection Options (Blank for All Members) 
Member name mask ===> 
Member name range ===> to ===> 
Last modified userid ===> to ===> 
Creation date ===> to ===> (YY/MM/DD) 
Modification date ===> to ===> (YY/MM/DD) 



Use ENTER to continue, END to return to file specification screen 


Field Descriptions
The following list describes all PDS processing options that File-AID/RDX can present.

Member name mask

Specify a member name mask to select a subset of members based on the mask criteria. A pattern
member name or mask consists of explicit characters or a combination of explicit and pattern
characters.

Member name range

Specify a member name range to select a subset of members based on the characters in the
member name. The endpoint member names (FROM and TO) can be complete or partial and are
included in the member list when found. Pattern characters are not allowed.

If the FROM member field is blank and a TO member is specified, File-AID/RDX selects the
members less than or equal to the TO member padded with high values.

If a FROM member field is specified and the TO member is blank, File-AID/RDX selects members
greater than or equal to the FROM member padded with low values.

Entering the same characters in the FROM and TO fields selects all members beginning with
those characters.

Last modified userid

Specify a user identification range to select a subset of members based on the user ID that last
updated and saved a member. This information is a PDS statistic that is stored in the directory.

The endpoint userids (FROM and TO) can be complete or partial and are included in the member
list when found. Pattern characters are not allowed. As with member name range, the FROM field
is padded with low values and the TO field is padded with high values.

Members without PDS statistics, because they were not created (STATS OFF) or the statistics were
deleted, are not selected.
238 File-AID/RDX Reference

Creation date
Specify a creation date range to select a subset of members based on their creation date(s). This is
a PDS statistic that is stored in its directory.

The endpoint (FROM and TO) dates can be complete or partial and are included in the member
list when found. Leading zeros are required when specifying the year, month, and day.

If the FROM date field is blank and a TO date is specified, File-AID selects all members created on
or before the specified TO date.

If a FROM member date is specified and the TO date is blank, File-AID selects all members created
on or after the specified FROM date.

Entering the same dates in the FROM and TO fields selects members created only on that date.
The two-character year is assumed between 1960 and 2059. Partial creation dates are treated
positionally (YY/MM/DD) and are padded with default values.

For example, if you enter blanks the default FROM value becomes 60/01/01 and the TO value
becomes 59/12/31. If you enter 85, the defaults are 85/01/01 and 85/12/31. If you enter 85/09,
the defaults are 85/09/01 and 85/09/30.

Members without PDS statistics, because they were not created (STATS OFF) or the statistics were
deleted, are not selected.

Modification date
Specify a modification date range to select a subset of members based on the last modified
date(s). This is a PDS statistic that is stored in its directory. The last modified date is updated with
the current date each time a member is updated and saved.

See the description of the Creation date field for more information on specifying a modification
range. The specifications are identical.

Members without PDS statistics, because they were not created (STATS OFF) or the statistics were
deleted, are not selected.

XREF Select Member List

The XREF Select Member List screen, shown in Figure 123, is displayed when a blank or a pattern is
specified in the Member field for the XREF file name. The list may be scrolled using LOCATE
commands (LOC mem) or scrolling commands (such as UP and DOWN).

Select the desired XREF member with the S line command.

Figure 123. XREF Select Member List Screen

File-Aid/RDX - XREF Select - TSOID01.FRSAMP.XREF ------------ Row 1 to 5 of 5 

Command ===> SCROLL ===> PAGE 
S NAME DESCRIPTION TYPE CHANGED ID 
ADVMST4 FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
A020815 FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
RETEST1 FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
TEDS646 FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
S USERNEW FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
******************************* Bottom of data ********************************
Extract 239

Extract Criteria
File-AID/RDX enables you to control the scope and depth of the extract process by allowing you to
define extract criteria. Extract criteria includes information about

• navigation controls

• sampling controls

• selection criteria

Navigation controls apply to the list of relationships defined for the driving object. They determine
how File-AID/RDX chases the relationships and whether or not to extract direct dependents, parent
records, sibling or indirect dependents. The navigation controls can be set globally or individually.
You also can exclude objects or relationships manually from the extract to further define the scope of
the extract.

Sampling controls can limit the number of records to be extracted from each relationship or object,
specify the number of records to skip, or specify the maximum number of records to extract from all
objects. The controls also include cycle count and what action to take when the maximum counts
have been reached.

Selection criteria can be specified for any object in the extract. It consists of conditions that
individual columns or fields must meet. File-AID/RDX extracts only records that contain values that
meet these conditions. For complex extracts, you can define multiple selection criteria sets.

You can save extract criteria in an extract request file so you can use it at a later time. See
Extract/Load/Delete Request File on page 44 and File-AID/RDX Extract/Load/Delete Request File on
page 368 for more information about the Extract Request File.

When using an extract criteria file created with an earlier release of File-AID/RDX than Release
4.0, File-AID/RDX will set the navigation and sampling controls to approximate the extract
method (OPTIMUM, STANDARD, MOST, or DETAILED). However, the extract results may
differ as there are also differences in sampling controls. The option to extract records outside
the selection criteria to satisfy AR/RI relationships is no longer supported. Selection criteria is
now always enforced in a downward direction.

Extract Menu
After you selected an extract request from either the Extract Reference List or the Request File
Member List Screen or whenever you enter the MENU command within the extract option File-
AID/RDX displays the Extract Menu as shown in Figure 124.

You profile’s selected extract flow (see Panel Customization on page 62)
might not show the Extract Menu initially. Just issue the MENU command
to display it from any of the extract option panels.

The Extract Menu provides a quick overview of your current extract request and its status fields are
immediately updated upon return from its suboptions. This allows you to selectively access any of the
options or to submit the extract request when all extract criteria are to your liking.

After completing all extract specifications, simply select Option 14 - Submit JCL and File-AID/RDX
submits this extract job.
240 File-AID/RDX Reference

Figure 124. Extract Menu

File-AID/RDX ------------------ Extract Menu --------------------------------

Option ===> Scroll ===> CSR
SITE Profile: RDXMENU
Primary commands: menu-number, ALL, REFerence, REQuest, MODE SSID: DSN
Line commands: S or / to create flow through selected options.

Description ===> DB2-FRSAMP.ORDER_TABLE 

_ 1 Driving Object DB2-FRSAMP.ORDER_TABLE 
/ 2 Extract Scope and Dep=Y, Par=Y, Sib=N, Ind=N, Cycles=1
Detailed Extract Views 3 of 5 Relationships Active
/ 3 Unrelated Objects None
_ 4 Input Key File None
/ 5 Selection Criteria None
_ 6 Output Key Files Attention
/ 7 Extract File TSOID01.FRSAMP.EXTRACT 
_ 8 Data Privacy DISGUISED DCF: TSOID01.FRSAMP.DISGUISE
_ 9 Supporting Files Layouts=N, Xref=N, Topaz Visualizer File=N
_ 10 Checkpoint/Resumption None
_ 11 Continue with Load No
_ 12 Save Extract Request Request has not been saved 
_ 13 View JCL 
_ 14 Submit JCL 


The top of this screen consists of the following field:

USER Profile or SITE Profile

Displays the name of the current profile that provides the profile settings for this extract request.
To change the profile, return to the File-AID/RDX Primary Option Menu.

SSID
Displays the current Db2 subsystem ID you are connected to. Only displays when File-AID/RDX is
installed with the Db2 option and the current extract request includes one or more Db2 objects.

Description
Displays a short description for the current extract request. If you are modifying a previous
request it is prefilled. When creating a new request, File-AID/RDX fills this description field with
the name and object type of the driving object. Using this description is a helpful way to
document your extract criteria. To change the description select Option 12- Save Extract Request.

Extract Menu Options

Enter the option number (1 - 11) to select the desired option or enter ALL to step through all options
in sequence. Alternatively, you may also select one or more options with the S or / line command.

The Current Values column are display fields only and are updated upon return from each of the
extract menu options to reflect the current status and value for the option. A status of Attention is
displayed when the option requires further attention, before the extract request can be submitted.

1 - Driving Object
Displays either the DB2 Driving Object on page 222 or MVS Driving Object on page 233 panel
depending on the driving object’s object type. The MVS panel also includes layout and XREF
information.
Extract 241

Current Values shows the full name of driving object for this extract request.

2 - Extract Scope and Detailed Extract Views

Displays the Extract Scope Screen where you specify global navigation and sampling controls.
From this screen you access the Extract Scope Detailed View panels where you can specify the
navigation and sampling controls for individual objects and relationships from the extract.

Current Values shows the settings of the global navigation and the global Cycles sampling
controls. On the second line, Current Values displays how many of the driving object’s
relationships are active (included) for the extract, and that an extract from Db2 Image Copy has
been requested.

3 - Unrelated Objects
Displays the Unrelated Object Definition panel when unrelated objects have yet to be added for
the extract request or the Unrelated Object Specification panel when unrelated objects are
already part of the extract request.

Current Values displays None or the number of unrelated Db2 or MVS objects in the request.

4 - Input Key File

Displays the Input Key File Specification panel where you can identify whether the extract uses a
key file as selection criteria input for the driving object. The driving object can be a Db2 or MVS
object. Input Key File used to be called External Key File in previous releases.

Current Values displays None or the name of the Input Key file.

5 - Selection Criteria
Displays the Object Selection Criteria panel where you can specify selection criteria for any of the
objects included in the extract request.

Current Values displays None or Specified (but not) for Driving Object.

Option 10- Checkpoint/Resumption is not available when the extract

request includes multiple selection criteria sets (see also 10-
Checkpoint/Resumption on page 242).

6 - Output Key Files

If the extract request includes relationships to an Output Key File (see IMS and Output Key Files
on page 124), File-AID/RDX displays the Output Key File Definition panel where you specify the
Output Key file for each KEY relationship. If the Output Key files are for IMS data, you can also
specify that the File-AID for IMS extract using the Output Key files is to be executed as a step
following the File-AID/RDX extract.

Current Values displays the message “There are no Output Key files defined” or “n of n Key Files”
or “n of n Key Files - Execute n IMS Extract”.
242 File-AID/RDX Reference

7 - Extract File
Specify the output file for your extract request on the Extract File Specification Screen. File-
AID/RDX will store all extracted records in this file.

Current Values displays the name of the extract file.

8 - Data Privacy
Select the Data Privacy option in the Data Privacy Specification screen, if you also want the
extracted data disguised by applying the disguise criteria rules as defined in the DCF: Disguise
Control File or the DPR: Dynamic Privacy Rules Project.

Current Values displays None, the name of the DCF: Disguise Control File, or the DPR:
Dynamic Privacy Rules Project.

The DISGUISED indicator is displayed when data in the extract file is to be disguised.

9 - Supporting Files
Optionally, you can request in the Supporting File Specification screen that File-AID/RDX creates
a record layout file for all Db2 objects included in the extract, a File-AID/MVS XREF for the
extract file, and/or a Topaz Extract Visualizer file (also known as the File-AID/RDX Extract
Mainframe Trace file).

Current Values displays Layouts=n, Xref=n, Topaz Visualizer File=n, where n is either N or Y.

10- Checkpoint/Resumption
Specify whether you want to enable Checkpoint/Resumption for your extract request. With
Checkpoint/Resumption enabled you can stop and resume the extract after a specified extract
step number, a specified time interval, or a z/OS Operator command. When you select this
option, File-AID/RDX presents the Checkpoint/Resumption panel where you identify your
checkpoint options and datasets.

Use this functionality when you anticipate a long running extract that might not be completed
within your site’s constraints or when you want to tune highly complex extracts.

After you submit an extract request with Checkpoint/Resumption Enabled and the extract
completed up to the checkpoint, the extract is ready to be continued. When submitting the
extract request again, File-AID/RDX prompts you to continue the extract execution from the
checkpoint or cancel the resumption (see also Checkpoint/Resumption Confirmation Windows).

If you don’t resume the extract, the partial extract file is NOT USABLE as it lacks important trailer
records.

Current Values displays None or Checkpoint/Resumption Enabled.

1. Option 10- Checkpoint/Resumption is not available for interactive (online) extract

execution (see also MODE on page 244.)
2. Option 10- Checkpoint/Resumption is not available when the extract request includes
the Continue With Load option (see also 11- Continue with Load).
3. Option 10- Checkpoint/Resumption is not available when the extract request includes
multiple selection criteria sets (see also 5 - Selection Criteria on page 241).
4. When specifying both Checkpoint/Resumption and Data Privacy Specification, you
must save the Extract Request (see Save Extract Request on page 352) before
submitting it. Refer to Checkpoint/Resumption on page 347 for more detail).
Extract 243

11- Continue with Load

Specify whether the extract request should be a combined extract and load (YES) or just an
extract. When you select this option, File-AID/RDX presents the Continue With Load Menu
where you identify all your load options and parameters.

Current Values displays Yes or No.

1. If the current value is set to Yes, but you no longer want your extract to continue with
load, simply type No over the Yes and press Enter. The current value will change to No
and will be display only again.
2. Option 11- Continue with Load is not available for interactive (online) extract execution
(see also MODE on page 244.)
3. Option 11- Continue with Load is not available when Option 10-
Checkpoint/Resumption has been enabled (see also 10- Checkpoint/Resumption.)
4. The ALL primary command does not select the Continue With Load option (see also
ALL on page 244.)

12- Save Extract Request

Specify whether to save this extract request in a file. File-AID/RDX presents the Save Extract
Request panel where you identify the extract request file to save your request to. Once you save
your extract request it will be added to the Extract Reference List at that time.

Current Values displays Request has not been saved or the name of the extract request file.

Make sure to save the request just before selecting Option 14 - Submit JCL in order to save
the request as it will be submitted. If you make changes to the extract request after saving
the request, the changes will not be saved in the request file, only in the temporary extract
criteria.

13 - View JCL
Select this option to view the JCL for this extract request. File-AID/RDX shows the ISPF/PDF EDIT
Screen—File-AID/RDX-generated JCL panel where you review and modify the extract JCL.

Current Values displays the status Unavailable when some required items for the extract request
are still missing or incomplete. Revisit some or all extract menu options and provide acceptable
extract criteria.

Option 13 - View JCL switches to Option “13 - View REXX” when the MODE primary
command has set the execute extract mode to (see Figure 125 on page 244). INTERACTIVE
(online) extract is a configuration option and is only available if specifically installed at your
site (see ALLOW_EXTRACTS_TO_RUN_ONLINE in the File-AID Advanced Configuration
Guide).

14 - Submit JCL
Submits the JCL for this extract request. Watch for the message that the job has been submitted
and later for the completion message.
244 File-AID/RDX Reference

Current Values displays the status Unavailable when some required items for the extract request
are still missing or incomplete. Revisit some or all extract menu options and provide acceptable
extract criteria.

Option 14 - Submit JCL switches to Option “14 - Execute REXX” when the MODE primary
command has set the execute extract mode to INTERACTIVE (see Figure 125 on page 244).
INTERACTIVE (online) extract is a configuration option and is only available if specifically
installed at your site (see ALLOW_EXTRACTS_TO_RUN_ONLINE in the File-AID Advanced
Configuration Guide).

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

ALL
Selects all available extract menu options for you to step through in sequence. ALL does not
include options 11- Continue with Load and 14 - Submit JCL. To submit the extract JCL, select
option 14 - Submit JCL separately or enter the SUBMIT command in the View JCL panel.

MODE
Enter the MODE command in the Command field to enable execution of the extract request
interactively (online). Extract Menu options 13 - View JCL and 14 - Submit JCL will change to “12
- View REXX” and “13 - Execute REXX” (see Figure 125) to show that the extract will be executed
interactively when selecting Option “13 - Execute Rexx”. MODE acts as a toggle switch.

1. INTERACTIVE (online) extract is a configuration option and is only available if specifically

installed at your site (see ALLOW_EXTRACTS_TO_RUN_ONLINE in the File-AID Advanced
Configuration Guide).
2. The following options are not available for interactive execution:
a. Checkpoint/Resumption (see also Checkpoint/Resumption on page 347).
b. Extract from Image Copy (see also Extract from Image Copy on page 251).
c. Disguise Extract File (see also Disguise Extract File on page 341).
d. Output to Topaz Extract Visualizer file (see also Specify Topaz Extract Visualizer File)
3. If the extract file is a GDS, it must already exist, therefore (0) or (-n) are valid while (+n)
is not allowed.

Figure 125. Extract Menu - Interactive Extract Mode

_ 8 Data Privacy DCF: TSOID01.FRSAMP.DISGUISE

_ 9 Supporting Files Layouts=N, Xref=N, Topaz Visualizer File=N
_ 10 Checkpoint/Resumption None
_ 11 Continue with Load No
_ 12 Save Extract Request Request has not been saved 
_ 13 View REXX 
_ 14 Execute REXX *** INTERACTIVE EXTRACT MODE ACTIVE *** 


REFERENCE (REF)
Returns to your Extract Reference List (page 213) to start a new extract request.
Extract 245

REQUEST (REQ)
Returns to a saved extract request file. You also use the REQUEST command to open extract
criteria files created with File-AID/RDX prior to Release 3.0. Refer to Request File Member List on
page 218 for more information.

Make sure to save the request just before selecting Option 12- Save Extract
Request in order to save the request as it will be submitted. If you make
changes to the extract request after saving the request, the changes will not
be saved in the request file, only in the temporary extract criteria.

Driving Object - DB2

The Driving Object - DB2 screen shown in Figure 126 is displayed when you select Option 1 - Driving
Object from the Extract Menu.

All fields are display only.

Use this screen to view the driving object for the current extract request.

Figure 126. Driving Object - DB2

File-AID/RDX ------------- DB2 Driving Object -------------------------------

Command ===> 


Table to drive extract process
SSID ===> DSN 
Location ===> Location (* or pattern for selection list)
Creator ===> FRSAMP (* or pattern for selection list)
Table Name ===> ORDER_TABLE (* or pattern for selection list)

Relationship Information:
File name ===> 'TSOID01.FRSAMP.RELATION' 

After viewing the driving object information, press END to return to the Extract Menu.

The body of this screen consists of the following fields:

Table To Drive Extract Process Area

SSID
Displays the Db2 subsystem ID for the extract.

Location
Displays the location of the table you want to drive the extract.

Creator
Displays the authorization ID of the owner of the table, view, synonym, or alias that you want to
drive the extract process.
246 File-AID/RDX Reference

Table Name
Displays the name of the table, view, alias, or synonym that you want to drive the extract
process.

Specify Relationship Information:

Relationship File
Displays the name of the file that contains the referential integrity and application relationship
information used for the current extract request.

Driving Object - MVS

The Driving Object - MVS screen shown in Figure 127 is displayed when you select Option 1 - Driving
Object from the Extract Menu and the driving object type is MVS.

All fields are display only.

Use this screen to view the name of the MVS file for which you want to extract related data.

Figure 127. Driving Object - MVS

File-AID/RDX ------------- MVS Driving Object -------------------------------

Command ===> 

File to drive extract process from:
File Name ===> FRSAMP.ORDERTAB

Optional File Information: 
Record layout usage ===> S 
Record layout file ===> FRSAMP.LAYOUTS 
Member name ===> ORDERTAB 
XREF file name ===> 
Member name ===> 

Specify Relationship Information:
File name ===> 'TSOID01.FRSAMP.RELATION'

After viewing the driving object information, press END to return to the Extract Menu.

File To Drive Extract Process From Area

File name
Displays the MVS file name of the driving object from which you want to extract related data.

Optional File Information Area

The following fields are filled in from information stored in the relationship file for the selected MVS
file.

Record layout usage

Indicates whether a single record layout (usage "S"), or an XREF (usage "X") had been used to
define the selection criteria.
Extract 247

Record layout file

Displays the name of the record layout file for the MVS object from which you want to extract
related data.

Member name
Displays the member of the record layout file that contains the layout information for the MVS
object.

XREF file name

Only displays if layout usage is X. Displays the XREF file name for the MVS object from which
you want to extract related data.

Member name
Displays the member of the XREF file that contains the layout information for the MVS object.

Specify Relationship Information:

Relationship File
Displays the name of the file that contains the application relationship information you want to
use for the extract process.

Extract Scope
The Extract Scope Screen shown in Figure 128 on page 248 is displayed when you select Option 2 -
Extract Scope and Detailed Extract Views from the Extract Menu.

If you are performing a single object extract (where there are no Db2-
defined RI or user-defined application relationships in the relationship file
that match the driving object), the Extract Navigation Criteria fields are not
accessible.

When your profile has navigation criteria Direct set to C or P (see also Direct on page 58), a message
displays alerting you that the relationship tree for this extract request has been built using the
profile’s navigation criteria. The resulting relationship listing may be different than that resulting
from navigation criteria Direct Y or N.
248 File-AID/RDX Reference

Figure 128. Extract Scope Screen

File-AID/RDX ------------------ Extract Scope ---------------------------------

Command ===> 

Driving Object: TSOID01.FRSAMP.ORDERTAB 

Extract Navigation Criteria: 
Direct ===> Y ( Y = Yes, N = No)
Parents ===> Y 
Siblings ===> N 
Indirect ===> N 
Extract scope detail view ===> O ( O = Object, R = Relationship, N = None) 
Extract Options: 
Cycle count ===> 1 ( * for no maximum) 
Maximum total rows/records from all objects ===> * ( * for no maximum) 
Action when maximum count is reached ===> Q ( Q = Quiesce, S = Stop) 
Extract from DB2 using Uncommitted Reads ===> N ( Y = Yes, N = No) 
Extract IMPLICITLY HIDDEN columns ===> N ( Y = Yes, N = No) 
Extract from DB2 image copy ===> N ( Y = Yes, N = No) 
SELECT FROM Temporal Table ===> N *None*
Scope Summary Counts: 
3 of 5 Relationships Active
Related DB2 objects..: 3 of 6 included 
Related MVS objects..: 0 of 0 included 
Output Key Files.....: 0 of 0 included 


Use this screen to specify the way that File-AID/RDX chases the object relationships and what
sampling methods it applies during extract processing. This controls the amount of data that can be
extracted. Appendix , presents examples for the global extract navigation settings.

You specify how File-AID/RDX should navigate through the related objects with the Navigation
Criteria. You can set the navigation and sampling controls globally and then fine tune them
individually on an object or relationship basis. Your current profile determines the default settings.

Driving Object
Displays the name of the driving object from which you want to extract related data.

Extract Navigation Criteria

Navigation criteria determines the extend of how File-AID/RDX chases the related objects from
the driving object. On this panel, you specify the Navigation Criteria globally, for all included
objects and relationships. In the Detail View panels you may then determine the navigation on
an individual object or relationship level.

When your profile has navigation criteria Direct set to C or P (see also Direct
on page 58), all Extract Navigation Criteria fields are protected and cannot
be modified during the extract specification. The Description of the Direct
field will then also display the respective status, either ** Children only
or ** Direct Plus.

To specify the global navigation criteria, specify Yes or No for each of the four navigation
switches:

Direct
Extract all of the dependents of the driving object and their dependents.

Any object that is reached by navigating downward from the driving object is a direct
descendant so any relationship on this downward navigation has a valid direct descendant
Extract 249

path. Only the rows initially selected from the driving object will be sent down this path so
the direct descendant path will be navigated only once.

Extract the dependents of the driving object and their dependents (default).

Do NOT extract the dependents of the driving object and their dependents.

(All Children only) This option can only be set or changed in the profile (see Direct on
page 58). Extract the dependents of the driving object and all of their dependents only.
This option ignores all other Navigational Control Options (DPSI) settings and cannot
be modified during the extract specification.

Using the C method to extract data and only its dependent data can lead to extracted
data that is not loadable because of referential integrity issues due to the omitted related
parent data. This can be useful for extracting specific data that is then used for a purge
procedure.

(Plus) This option can only be set or changed in the profile (see Direct on page 58).
Extract all of the direct relationships of the driving object, i.e. all of its parents and first
level dependents only. "Plus" means resolve all objects’ parents until there are no more
parents to return. This option ignores all other Navigational Control Options (DPSI)
settings and cannot be modified during the extract specification.

The C and P settings for Direct can only be set in the profile. The profile
settings are used to build the relationship tree with its related objects when
starting an extract specification.

Parents
Extract the parents of all extracted data to maintain the integrity of the extracted data.

Any object that is on the upward navigation from a selected object has a valid parent path.
This does not mean that every relationship has a valid parent path; navigation has to be
possible in an upward direction for the parent path to be valid.

Siblings
Extract other dependents of the extracted parents from the same relationships.

Parent paths are always paired with sibling paths. Whenever a row is sent up the parent path
it is possible to come back down the same relationship to get the sibling rows.

Consider a relationship between ORDER and CUSTOMER where a row has been selected from
ORDER. The CUSTOMER for that order will be extracted by navigating the parent path. The
sibling path would allow all of the rest of the orders for that same customer to be extracted.

Parent/sibling special case:

A many to many application relationship presents a special case where it is possible to have a
parent and sibling path defined for a relationship that does not meet the parent criteria
specified above. Every many to many relationship has a parent and sibling path.
250 File-AID/RDX Reference

Indirect
Extract other dependents of the extracted parents from other relationships.

The indirect descendant path includes two different situations. First, it is the downward
navigation from any object reached in an upward direction.

Second, it is downward navigation from the driving object and its direct descendents for all
rows other than the original selection from the driving object. For an indirect descendant
path to be valid on the same relationship as a direct descendant path there has to be a parent
path that leads back to the driving object or one of its parents; in effect, another path to the
object.

The indirect descendant paths represent downward navigation for objects reached via the
parent path. The downward navigation for the relationship that was navigated via the parent
path is a sibling path and is not an indirect descendant path. All the other relationships that
lead down from an object are valid indirect descendant paths.

This is not to say that a relationship can't have both a sibling path and an indirect
descendant path; this is possible when there are multiple parent paths leading to the same
object. If the object is on the direct descendant path it is possible to have all three downward
navigation paths marked as valid.

The status (Modified) identifies global settings that have been modified
individually with the navigation controls of the Relationship Navigation
Criteria screen or by the Accept primary or line command of the Check
Extract Warning screen.

Extract Scope Detail View

Specify whether you want to view the list of relationships or list of related objects. Set to R or O
to view the related objects and their relationships in more detail. In the detail panels, you may
apply extract and navigation controls to individual relationships or objects.

None does not display either of the detail view panels.

Object displays the Extract Scope - Object View panel, listing all objects related to the driving
object from which to extract data. See Extract Scope - Object View on page 256 for more
information.

Relationship displays the Relationship Criteria panel, listing all the relationships associated
with the driving object from which to extract data. See Relationship Criteria on page 265 for
more information.

The Relationship View options are not accessible for a single object extract.

Extract Options
Use these fields to limit the number of records to be extracted in this request. These options also
apply to all unrelated objects included in the extract.
Extract 251

Cycle Count
Specify the maximum number of cycles for all relationships leading from the object. Cycle count
limits the number of times an object can be visited during an extract. This global setting for the
Cycle Count can be modified for each individual relationship (see Cycle on page 274).

Maximum Total Rows/Records From All Objects

Specify the maximum number of rows or records to be extracted from all related objects. Once
the limit is reached the extract will terminate regardless of how many relationships have been
chased. Enter an asterisk (*) to set no limit.

Action When Maximum Count Is Reached

Specify how the extract should terminate when the maximum count has been reached:

Quiesce resolves all orphan records after maximum count has been reached. (May result in
more records than the maximum count.)

Stop does not resolve possible orphan records. (May extract dependent records without their
parents).

Extract from DB2 using Uncommitted Reads

Specify whether File-AID/RDX should extract data from Db2 objects that include Uncommitted
Reads or not.

The field is prefilled with the specified UNCOMMITTED_READ_DEFAULT configuration

parameter value (Yes or No) of the Db2 Environment PARMLIB member or with the current
profile value (Yes or No) if UNCOMMITTED_READ_DEFAULT is set to blank (default, see also
UNCOMMITTED_READ_DEFAULT in the File-AID Advanced Configuration Guide).

Extract IMPLICITLY HIDDEN columns

Specify whether File-AID/RDX should extract data from Db2 columns that are defined as
IMPLICITLY HIDDEN. When this option is set to Y, the resulting File-AID/RDX extract file will
include the data from IMPLICITLY HIDDEN columns.

Extract from Image Copy

Specify whether File-AID/RDX should extract data from Db2 Image Copy datasets or not. This
option is only available if your site installation set the product parameter variable UIMGCPY to
Yes. Refer to ALLOW_EXTRACT_FROM_DB2_IMAGE_COPY in the File-AID Advanced
Configuration Guide.

File-AID/RDX will extract related data from the most recent, full Db2 Image Copy(s) for the
applicable tablespace(s). For partitioned tablespaces, File-AID/RDX will only extract from an
image copy dataset that includes all partitions.
252 File-AID/RDX Reference

An image copy dataset must exist and be in the MVS catalog for each Db2 table in the extract
request or the extract will terminate.

You must have one of the following authorization privileges to extract data from Db2 Image
Copy:

• RECOVERDB privilege for the database

• DBADM, or DBCTRL authority for the database
• SYSCTRL or SYSADM authority

File-AID/RDX will extract from the regular Db2 tables.

The Extract from Image Copy option requires executing File-AID/RDX from
an authorized library. Furthermore, the Extract from Image Copy option is
not available:

• for Db2 views.

• for interactive execution (see also MODE on page 244).
• when extracting from a remote location (see also Location on page 222).

SELECT FROM Temporal Table

Enter Yes if you want to specify or modify a time-period and date/timestamps for Temporal Tables
or Temporal Views. File-AID/RDX will display the SELECT FROM Temporal Table screen (refer to
Figure 129 on page 253) when you press Enter. Temporal table support requires Db2 Version 10 or
more recent. Starting with Db2 Version 11, temporal support allows period specifications and
period clauses to be specified for views. The same rules apply for views as do for tables.

Enter No (default) if you don’t want to display the SELECT FROM Temporal Table screen.

The status *Defined* displays if a SELECT FROM Temporal Table statement has already been
defined, otherwise *None* displays.

If you want to extract data from temporal tables or views without a SELECT FROM Temporal
Table statement, make sure *None* displays. To change the status from *Defined* to *None*,
enter Yes in the SELECT FROM Temporal Table field, then set the Use System Time and Use
Business Time to No in the SELECT FROM Temporal Table screen (refer to Figure 129 on page
253).

1. When the *Defined* status displays and the extract request includes one or more
temporal tables or views, File-AID/RDX will include the SELECT FROM Temporal Table
statement even if the SELECT FROM Temporal Table field is set to No.
The SELECT FROM Temporal Table statement is only generated for each Temporal
Table or Temporal View in the extract request.
2. Whenever the selection is based on SYSTEM_TIME, it is possible that some rows come
from the base table and some from the history table.
3. The *Defined* status is saved with the extract request.
4. The SELECT FROM Temporal Table field will be reset to its default (No, *None*) when
you exit the extract menu. It will be set to *Defined* when when you return the
extract menu with an extract request that includes the *Defined* status.

Scope Summary Counts

The following fields display how many objects and relationships will be included in the extract based
on the specified navigation and sampling criteria.
Extract 253

Relationships Active
Displays how many relationships will be used to extract data from the related objects.

Related DB2 objects

Displays how many related Db2 objects will be accessed to extract data from.

Related MVS objects

Displays how many related MVS objects will be accessed to extract data from.

Output Key Files

Displays how many Output Key files File-AID/RDX will create for this extract request.

SELECT FROM Temporal Table

The SELECT FROM Temporal Table window displays when you enter Y in the SELECT FROM Temporal
Table field. It allows you to construct the SELECT FROM statement to be used for a temporal table (or
view starting with Db2 Version 11) to be browsed (System Period and Business Period) or edited
(Business Period only).

Figure 129. SELECT FROM Temporal Table

File-AID/RDX ----------------- Extract Scope --------------------------------

COMMAND ===> 

Driving Object: FRSAMP.ORDER_TABLE 
SELECT FROM Temporal Table -----------------------+
Ext COMMAND ===> 
D 
P SELECT FOR SYSTEM TIME: 
S Use System Time ===> N (Y = Yes, N = No) 
I Time Period ===> (1 = AS OF, 2 = FROM, 3 = BETWEEN) 
E Timestamp 1 ===> 
Ext Timestamp 2 ===> 
C (Example format: YYYY-MM-DD-hh.mm.ss or 
M CURRENT TIMESTAMP) 
A 
E SELECT FOR BUSINESS TIME: 
E Use Business Time ===> N (Y = Yes, N = No) 
E Time Period ===> (1 = AS OF, 2 = FROM, 3 = BETWEEN) 
E Date/Timestamp 1 ===> 
Sco Date/Timestamp 2 ===> 
(Example format: YYYY-MM-DD or YYYY-MM-DD-hh.mm.ss or 
CURRENT DATE/TIMESTAMP) 



A temporal table records the period of time when a row is valid. Db2 supports two types of periods,
the application period (BUSINESS_TIME) and the system period (SYSTEM_TIME).

System Period

The system period consists of a pair of columns with system-maintained values that indicate the
period of time when a row is valid. The system period is meaningful because you can define system-
period data versioning on a table that has this period. System-period data versioning specifies that
old rows are archived into another table. The table that contains the current active rows of a table is
called the system-period temporal table. The table that contains the archived rows is called the
history table (Table Type=H). You can delete the rows from the history table when those rows are no
longer needed, if you have the proper authorization.
254 File-AID/RDX Reference

When you define a base table to use system-period data versioning, or when you define system-period
data versioning on an existing table, you must create a history table, specify a name for the history
table, and create a tablespace to hold that table. You define system-period data versioning by issuing
the ALTER TABLE ADD VERSIONING statement with the USE HISTORY TABLE clause.

Business (Application) Period

A business (application) period consists of a pair of columns with application-maintained values that
indicate the period of time when a row is valid. A table with only a business period is called an
application-period temporal table.

Bitemporal Table

A bitemporal table is both a system-period temporal table and an application-period temporal table.
You can use a bitemporal table to keep application period information and system-based historical
information. Therefore, you have a lot of flexibility in how you query data based on periods of time.

For each System Time and Business Time, specify the time period to be used to select rows from a
temporal table.

Use System Time

Specify Yes if the table includes System Time and you want to select rows from the specified
period.

Time period
Select the period method you want to specify for System Time:

AS OF creates the AS OF ... period statement to select valid rows as of a certain point in time.
This option requires you to also specify a value for Date/Timestamp 1. Example statement:

FROM table FOR SYSTEM_TIME AS OF TIMESTAMP('2012-03-16-00.00.01')

FROM creates the FROM ... TO ... period statement to select valid rows from a certain time to
a certain time. FROM is inclusive, TO is exclusive. That means, the specified start time is
included in the period but the specified end time is not. This option requires you to also
specify a value for Timestamp 1 (start time) and Timestamp 2 (end time). Example statement:

FROM table FOR SYSTEM_TIME FROM TIMESTAMP('2011-03-16-00.00.01')

TO TIMESTAMP('2012-03-16-00.00.01')

BETWEEN creates the BETWEEN ... AND ... period statement to select valid rows from a
certain time to a certain time. BETWEEN and AND are inclusive. That means, that both the
specified start time and end time are included in the period. This option requires you to also
specify a value for Timestamp 1 (start time) and Timestamp 2 (end time). Example statement:

FROM table FOR SYSTEM_TIME BETWEEN TIMESTAMP('2011-03-16-00.00.01')

AND TIMESTAMP('2012-03-16-00.00.01')

Timestamp 1
specify the corresponding start timestamp for the selected system time period.
Extract 255

Timestamp 2
specify the corresponding end timestamp for the selected system time period. Only required for
FROM and BETWEEN periods.

Use Business Time

Specify Yes if the table includes Business Time and you want to select rows from the specified
period.

Time period
Select the period method you want to specify for Business Time:

AS OF creates the AS OF ... period statement to select valid rows as of a certain point in time.
This option requires you to also specify a value for Date/Timestamp 1. Example statement:

FROM table FOR BUSINESS_TIME AS OF DATE('2011-03-16')

FROM creates the FROM ... TO ... period statement to select valid rows from a certain time to
a certain time. FROM is inclusive, TO is exclusive. That means, the specified start time is
included in the period but the specified end time is not. This option requires you to also
specify a value for Date/Timestamp 1 (start time) and Date/Timestamp 2 (end time). Example
statement:

FROM table FOR BUSINESS_TIME FROM DATE('2011-03-16') TO CURRENT DATE

BETWEEN creates the BETWEEN ... AND ... period statement to select valid rows from a
certain time to a certain time. BETWEEN and AND are inclusive. That means, that both the
specified start time and end time are included in the period. This option requires you to also
specify a value for Date/Timestamp 1 (start time) and Date/Timestamp 2 (end time). Example
statement:

FROM table FOR BUSINESS_TIME BETWEEN DATE('2011-03-16') AND 

CURRENT DATE

Date/Timestamp 1
specify the corresponding start date/time for the selected business time period.

Date/Timestamp 2
specify the corresponding end date/time for the selected business time period. Only required
for FROM and BETWEEN periods.

If the arguments for business Date/Timestamp 1/2 include only date information, the time
information in the result value is all zeros. This means that date value of '2000-10-31' will
result in a TIMESTAMP of '2000-10-31-00.00.00'. This could result in different rows being
returned than if a user entered '2000-10-31-23.59.59'.
256 File-AID/RDX Reference

Extract Scope - Object View

The Extract Scope - Object View screen shown in Figure 130 is displayed when you specify O in the
Extract Scope Detail View field of the Extract Scope Screen (Figure 128 on page 248) or the VIEW
primary command (page 272) from any of the Relationship Criteria screens.

Figure 130. Extract Scope - Object View

File-AID/RDX ------- Extract Scope - Object View ----------- Row 1 to 6 of 6 

Command ===> Scroll ===> PAGE 

Primary Commands: EXclude/Unex, Change, Find, Hide, VIew, CHEck, Size, REPort 
Line Commands: X = Exclude A = All R = Relationship View 
: U = Unexclude P = Passthru L = Lock 
Driving Object: TSOID01.FRSAMP.ORDERTAB 
SSID: Location: . Sampling Criteria 
Object Name Cycle MaxRow Nth Status L 
---------------------------------------------- ----- ------ --- ---------- - 
_ 'TSOID01.FRSAMP.CONTACTT' * * * N 
_ 'TSOID01.FRSAMP.CUSTOMER' * * * N 
_ 'TSOID01.FRSAMP.ORDERLIN' * * * N 
_ 'TSOID01.FRSAMP.ORDERTAB' * * * N 
_ 'TSOID01.FRSAMP.PARTTABL' * * * N 
_ 'TSOID01.FRSAMP.SUPPLIER' * * * N 
******************************* Bottom of data ******************************** 

Use this screen to specify which, if any, objects to exclude from the extract process and the maximum
number of rows/records that you want extracted from each object. In addition, you can request to
view the relationships for a specific object.

This screen displays a list of all the objects in alphabetical order that are part of the extract request,
including all objects related to the driving object based on the relationships defined in the
relationship file as well as all unrelated objects.

Initially, all objects are displayed. Use the HIDE command to display only select object types.

If there are more objects on this list than will fit on this screen, you can scroll the list up and down
using standard scrolling commands. See Scrolling on page 31 for more information about scrolling.

Fixed Display Area

In addition to the screen title, the Command field, and the scroll amount input field, the top area of
the screen contains

– the driving object for which these related objects were retrieved
– the Db2 subsystem and remote location ID where all related Db2 objects reside
– a message indicating the hide/filter status of the display

Scrollable Display Area

This screen areas displays a list of the objects related to the driving object containing the following
columns:

CMD
Enter line commands in this column. See Line Commands on page 258 for information about
valid commands for this screen.

Object Name
Displays the name of the related or unrelated object included in the extract request. For Db2
objects, the creator.tablename is displayed here.
Extract 257

Sampling Criteria
Displays the status of the three sampling criteria for each object. You can change each individual
setting simply by typing over a new value or use the CHANGE primary command to globally
change the sampling criteria fields.

Cycle
The cycle count can be set for each individual object in the extract.

When entered for an object, it limits the number of times an object can be visited during the
extract regardless of the number of relationships.

Max Rows
Specify the maximum number of rows to extract via downward navigation (direct, indirect
and sibling) of this object. The Max Rows profile value applies to each relationship and each
object. The relationship Max Rows values is processed first; if the count does not exceed the
limit, the record is passed on to check against the object Max Rows value.

NTH
(n th record) Specify how many of the eligible records to be extracted should be skipped and
not be extract (a value of 3 would extract records 1 and 4).

L
Lock Table; indicates whether or not the Db2 object (table) will be locked during extract. Use the
L line command to change the lock status for an individual table.

The L column is only displayed when you have entered the FUNCTION
LOCK primary command. The FUNCTION LOCK primary command is only
valid if File-AID/RDX was configured at installation to allow locking tables
during extract.

Status
Displays one of the following messages:

Message Explanation
All This object will have all of its records extracted, and File-AID/RDX will not chase
any of its relationships. This status is the result of the A (All) line command
(page 258).
Excl Miss This object is excluded from the current extract process because the object
does not exist.
Excl Scope This object is excluded from the current extract process. This status is the result
of a navigation setting or cascading EXCLUDE or ALL command.
Excl User This object is excluded from the current extract process. This status is the result
of the EXCLUDE primary or line command.
Passthru This object will not have any of its records extracted, but File-AID/RDX will
chase all of its relationships. This status is the result of the L (Lock Table) on
page 258 line command.
Selected Indicates that this object has been selected for relationship view with the R line
command.
258 File-AID/RDX Reference

Message Explanation
Unrelated Indicates that this is an unrelated object that has been added with Option 3 -
Unrelated Objects, for this extract request.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

A (All)
Extract all data from this object regardless of the relationships from and to this object and do not
chase any relationships associated with this object. The A line command acts as a toggle switch:
enter it once to set the status, enter it again to remove it.

The A (All) and P (Passthru) line commands are mutually exclusive. You must
remove one before you can set the other.

L (Lock Table)
Indicate whether or not a Db2 table will be locked during extract. See also primary command
FUNCTION LOCK on page 262 that controls whether the L column displays and the L line
command is valid. The FUNCTION LOCK command is not available if File-AID/RDX was
configured at installation to prevent locking tables during extract. In this case, the L column will
not be displayed. The L line command acts as a toggle switch, enter it once and it will set the
status to Locked. Enter L a second time, and the Locked status is removed.

L locks a table while File-AID/RDX extracts rows from it. This prevents other users from accessing
and updating the table until the extract process is complete.

When you set the Db2 table status to Locked, File-AID/RDX issues the following SQL:

LOCK TABLE XXXXXX IN EXCLUSIVE MODE

If you lock a table that resides in a segmented tablespace, only the table is locked. If you lock a
table that resides in a partitioned tablespace, all of the partitions are locked. If you lock a table
that resides in a simple tablespace, all tables in the tablespace are locked.

P (Passthru)
Don’t extract any data from this object, but process all relationships as if records based on the
relationship would have been extracted. The P line command acts as a toggle switch: enter it
once to set the status, enter it again to remove it.

The A (All) and P (Passthru) line commands are mutually exclusive. You must
remove one before you can set the other.

R (Relationship View)
Mark this object to be included in the Relationship View when the VIEW primary command is
entered.
Extract 259

U (Unexclude)
Selects a previously excluded object (using EXCLUDE primary or line command) to be included
in the extract. Remember, you cannot unexclude an excluded object when its link to the driving
object is through another, still excluded relationship. See also X (Exclude).

When the excluded status for an object has been set by a navigation control,
it can only be unexcluded with a navigation control, not with the Unexclude
line command.

X (Exclude)
Excludes an object from the extract.

You cannot exclude the driving object.

When you exclude an object, other relationships or objects might also be excluded as a result. This
occurs when you exclude a relationship and either of the objects in the excluded relationship is a
parent or dependent in another relationship that cannot be linked back to the driving object in
any other way. For example, assume three relationships exist as shown below and ORDER_TABLE
is the driving object.

Parent Object Dependent Object

ORDER_TABLE ORDER_LINE_TABLE
ORDER_LINE_TABLE PART_TABLE
PART_TABLE SUPPLIER_TABLE

When the PART_TABLE object is excluded, the SUPPLIER_TABLE object will also be excluded as
well as the ORDER_LINE_TABLE to PART_TABLE relationship.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

CHANGE (C)
Change allows global changes to be made to the sampling criteria on a column-by-column basis.
When the CHANGE command is entered with one of the available parameters CYC=n,
MAXROW=n, or NTH=n, all values for the specified parameter are changed to the new value n.
When entered without parameters, specify the values to change in the CHANGE Command
Window - Object View Sampling Criteria.

CHANGE Command Window

When you enter the CHANGE command without parameters, File-AID/RDX will display the CHANGE
Command Window - Object View Sampling Criteriaas shown in Figure 131.
260 File-AID/RDX Reference

Figure 131. CHANGE Command Window - Object View Sampling Criteria



File-AID/RDX -------------- CHANGE COMMAND ------------------- 
Command ===> 

Change ALL occurrences of "from string" value to "to string" 
From string ===> 
To string ===> 

Act on the following fields: Primary command: 
Cycle ===> N ( Y = Yes, N = No) Change CYCle=n 
MaxRow ===> N Change MAXROW=n 
Nth ===> N Change NTH=n 
Lock ===> N Change Lock=Y/N 

END to process and return 

***NOTE: Change will be applied to all qualified objects,
even those that are excluded or hidden. 

Enter the Change ‘From string’ and the Change ‘To string’ values and select the sampling criteria
types you want to change globally for all objects. Then press END to execute the CHANGE
command.

From string

Enter the current From (old) string you want to change to the To (new) string in the sampling
criteria.

To string

Enter the To (new) string you want to replace the From (old) string with in the specified
sampling criteria.

Cycle

Enter Y to apply the change to all matching Cycle values. Enter N if the change is not to be
applied to the Cycle sampling criteria.

MaxRow

Enter Y to apply the change to all matching MaxRow values. Enter N if the change is not to
be applied to the MaxRow sampling criteria.

Nth

Enter Y to apply the change to all matching Nth values. Enter N if the change is not to be
applied to the Nth sampling criteria.

Lock

Enter Y to apply the change to all matching Lock values. Enter N if the change is not to be
applied to the Lock Db2 Table column.

Lock is only displayed when you have entered the FUNCTION LOCK primary
command. The FUNCTION LOCK primary command is only valid if File-
AID/RDX was configured at installation to allow locking tables during
extract.
Extract 261

CHECK (CHE)
Use the CHECK command to verify the extract paths after you made navigation changes. When
the path integrity validation processing is complete, the results are displayed in the Check
Extract Warning screen (Figure 148 on page 285) where you can resolve or ignore the findings.
File-AID/RDX executes the CHECK command whenever it returns from the Extract Scope Detail
View panels.

CHECK is not valid when when the extract request is built with relationships
in the Direct Plus or All Children Only mode (see Direct on page 248).

EXCLUDE (EX or X)
The EXCLUDE command allows to exclude all objects or all objects of a specified object type to
be excluded from the extract. EXCLUDE without parameter displays the Exclude Command
Window (see Figure 132).

Use this command in conjunction with the U (Unexclude) line command or UNEXCLUDE
primary command when you have a long list of relationships displayed and you want to include
only a few relationships in the extract.

Enter the EXCLUDE ALL command to exclude all objects in the list displayed on the Extract
Scope - Object View screen from the extract.

The other parameters DB2 and MVS limit the EXCLUDE command to one of the two object types.

EXCLUDE Command Window

When you enter the EXCLUDE command without parameters, File-AID/RDX displays the Exclude
Command Window as shown in Figure 132. Select the object types you want to exclude from the
extract, and optionally, hide from the display.

Figure 132. Exclude Command Window



File-AID/RDX -------------- Exclude Command ------------------- 
Command ===> 

Object Types to Exclude: 
DB2 objects ===> N ( Y = Yes, N = No EXclude DB2 
MVS objects ===> N E = Exclude and hide) EXclude MVS 

END to process and return 



Select the object types to exclude, then press END to exit the window.

DB2 objects

Enter Y to exclude all Db2 objects/relationships. Enter E to exclude and hide all Db2
objects/relationships. Enter N if you don’t want to exclude all Db2 objects/relationships from
the extract. N does not unexclude excluded objects, use the UNEXCLUDE primary or line
command.

MVS objects
262 File-AID/RDX Reference

Enter Y to exclude all MVS objects/relationships. Enter E to exclude and hide all MVS
objects/relationships. Enter N if you don’t want to exclude all MVS objects/relationships
from the extract. N does not unexclude excluded objects, use the UNEXCLUDE primary or
line command.

FIND (F)
Searches the object list for the specified string and scrolls the list to display the first matching
entry at the top of the displayed entries. Use RFind to repeat the search.

FUNCTION LOCK
Enables the “Lock Table during Extract” function for all Db2 objects. The Extract Scope - Object
View panel will display and enable the L line command and display the L status column. See also
L (Lock Table) on page 258. FUNCTION LOCK is a toggle switch so enter FUNCTION LOCK again
to return to the original format.

The FUNCTION LOCK primary command is only valid if File-AID/RDX was

configured at installation to allow locking tables during extract.

HIDE (H)
The HIDE command allows less data to be displayed. Included or excluded objects can be hidden
from the display so that the remaining content is more meaningful. Use the RESET command to
return all hidden objects to the display.

HIDE Command Window

When you enter the HIDE command, File-AID/RDX will pop up the Hide Command Window as
shown in Figure 137. Select the object status types you want to hide from the display.

Figure 133. Hide Command Window



File-AID/RDX --------------- HIDE COMMAND -------------------- 
Command ===> 

Object Status to Hide: Primary Command: 
Included ===> N Hide INclude 
Excluded ===> N Hide EXclude 

END to process and return 



Select the object status types to hide or redisplay, then press END to exit the window.

Included

Enter Y to hide all objects/relationships that are included in the extract. Enter N to display all
objects/relationships that are included in the extract.

Excluded
Extract 263

Enter Y to hide all objects/relationships that are excluded from the extract. Enter N to display
all objects/relationships that are excluded from the extract.

NAVIGATION (NAV)
The NAVIGATION command takes you directly to the Relationship Navigation Criteria screen
(see Figure 142 on page 277).

REPORT (REP)
Prints the logical contents of the display. This report includes all of the displayable lines
formatted like the current view.

RESET (RES)
Use the RESET command to return all hidden objects to the display.

SAMPLE (SAM)
The SAMPLE command takes you directly to the Relationship Sampling Criteria screen (see Figure
140 on page 273).

SIZE (SI)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. SIze is a toggle switch so enter SIze again to return to the original display format.

STATUS (STAT)
The STATUS command takes you directly to the Relationship Criteria screen (see Figure 135 on
page 265).

UNEXCLUDE (U)
The UNEXCLUDE command allows you to unexclude all objects or all objects of a specified
object type to be included in the extract. UNEXCLUDE without parameter displays the
Unexclude Command Window (see Figure 134).

Use this command in conjunction with the X (eXclude) line command or EXCLUDE primary
command when you have a long list of objects displayed and you want to reverse a previous
EXCLUDE command to include objects in the extract again.

Enter the UNEXCLUDE ALL command to undo a previous EXCLUDE command for all objects in
the list displayed on the Extract Scope - Object View screen from the extract.

The optional parameters DB2 and MVS limit the UNEXCLUDE command to one of the two object
types.

UNEXCLUDE Command Window

When you enter the UNEXCLUDE command without parameters, File-AID/RDX displays the
Unexclude Command Window as shown in Figure 134. Select the object types you want to
include in the extract again (reverse a previous EXCLUDE line or primary command).
264 File-AID/RDX Reference

Figure 134. Unexclude Command Window



File-AID/RDX -------------- Unexclude Command ------------------- 
Command ===> 

Object Types to Unexclude: 
DB2 objects ===> N ( Y = Yes, N = No ) UNEXclude DB2 
MVS objects ===> N UNEXclude MVS 

END to process and return 



Select the object types to unexclude, then press END to exit the window.

DB2 objects

Enter Y to unexclude all Db2 objects. Enter N if you don’t want to unexclude all Db2 objects.
N does not exclude included objects, use the EXCLUDE primary or line command.

MVS objects

Enter Y to unexclude all MVS objects. Enter N if you don’t want to unexclude all MVS objects
from the extract. N does not exclude included objects, use the EXCLUDE primary or line
command.

VIEW (VI)
The VIEW command allows you to easily switch between the object and relationship views. The
optional parameters SAMPLE, STATUS (default) and NAVIGATION can be used to go directly to
the corresponding format of the relationship view. You can also enter these parameters as stand-
alone primary commands although they are not included on the primary command line for the
object view but will be processed if entered.

Extract Scope - Relationship Criteria

The Relationship Criteria screen shown in Figure 135 is displayed when you specify R in the Extract
Scope Detail View field of the Extract Scope Screen (Figure 128 on page 248) or enter the VIEW
STATUS primary command in the Extract Scope - Object View (Figure 130 on page 256) or any of the
Relationship Criteria screens.
Extract 265

Figure 135. Relationship Criteria

File-AID/RDX ------------ Relationship Criteria ----------- Row 1 to 7 of 12 

Command ===> Scroll ===> PAGE 

Primary Commands: EXclude/Unex, Find, Hide, FILter, CHEck, SIze, SOrt, VIew 
STATus, SAMple, NAVigation, VALidate, GRaphic, REPort 
Line Commands: X = Exclude U = Unexclude I = Info 
Driving Object: FRSAMP.ORDER_TABLE 
SSID: DSN Location: DSNLOCAT 
Seq Object Name Status/Description 
---- ---------------------------------------------- ------------------------ 
0001 FRSAMP.CUSTOMER_TABLE Inactive 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE 
FRSAMP.ORDER_TABLE CUSTOMER-ORDER RELATIONS 
0003 FRSAMP.ORDER_TABLE 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE Inactive 
FRSAMP.SUPPLIER_TABLE SUPPPART 
0006 FRSAMP.SUPPLIER_TABLE Excl Scope 
'TSOID01.FRSAMP.SUPPLIER' 
0007 'TSOID01.FRSAMP.CUSTOMER' Inactive 
'TSOID01.FRSAMP.CONTACTT'

This screen displays a list of referential integrity (RI) and application (AR) relationships defined in the
relationship file for the driving object.

A sequence number allows positioning directly to a specific relationship and makes it easier to see the
panel changes when scrolling. The sequence number field is also the line command field.

The Relationship Name in the Status field for the dependent object makes it easier to tell the
difference between multiple relationships between the same objects.

Use this screen to specify which, if any, relationships to exclude from the extract process and how
many rows from dependent objects to extract from those relationships not excluded. In addition, you
can request information about a specific relationship.

If there are more relationships on this list than will fit on this screen, you can scroll the list up and
down using standard scrolling commands. See Scrolling on page 31 for more information about
scrolling.

Fixed Display Area

In addition to the screen title, the COMMAND field, and the scroll amount input field, the top area
of the screen contains

– a message indicating how many relationships were retrieved for display

– a message indicating the driving object for which these relationships were retrieved,
including the Db2 subsystem and location IDs
– a message indicating the hide/filter status of the display

Scrollable Display Area

This screen area displays a list of referential integrity and application relationships containing the
following columns:

Seq
The Sequence column displays the sequence number for the listed relationships for the current
extract request. Enter line commands in this column. See Line Commands on page 258 for
information about valid commands for this screen.
266 File-AID/RDX Reference

Object Name (Parent)

Displays the name of the object defined as the parent in a relationship in the upper row (the row
with the Seq number).

Object Name (Dependent)

Displays the name of the object defined as the dependent in a relationship in the lower row,
under its parent.

Status
Displays one of the following messages in the upper row:

Message Explanation
Excl All This relationship is excluded from the current extract process as one of the
related objects is marked to extract all of its records and not chase any of its
relationships. This status is the result of the A (All) line command (page 258)
on the Extract Scope - Object View screen.
Excl Miss This relationship is excluded from the current extract process because at least
one of the related objects does not exist.
Excl Scope This relationship, with navigation (DPSI) settings of “----”, is excluded as the
result of another relationship’s DPSI settings that make it impossible for the
extract to navigate to this relationship. Any changes you make to this
relationship directly have no affect on the extract. This includes changes to the
sampling criteria and the DPSI settings as well.
Inactive A relationship with one or more DPSI switches set to “N”. but none to “Y”, is
considered inactive, but still within the scope of the extract as its DPSI settings
can be changed.

Note that in Object View, an object is marked excluded when all of its
relationships are marked inactive.
Excl User This relationship is excluded from the current extract process. This status is the
result of the EXCLUDE primary or line command.
KEY Undef For this relationship you still need to define an Output Key file with Extract
Menu Option 6 - Output Key Files or exclude this relationship from the current
extract process, before you can continue.
KEY Def An output key file has been defined for this KEY relationship.
KEY Deleted The output key file definition for this KEY relationship has been deleted.

Relationship Name

The lower, second Status row for each relationship displays the relationship name (Db2 RI
RELNAME or the relationship description for application relationships).

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

I (Relationship Information)
Invokes the Relationship Information window. See Relationship Information Window on page
284 for information about the Relationship Information window.
Extract 267

U (Unexclude)
Selects a previously excluded relationship to be included in the extract. Remember, you cannot
undo an excluded relationship when its link to the driving object is through another, still
excluded relationship. See also X (Exclude).

When the excluded status for a relationship has been set by a navigation
control, it can only be undone with a navigation control, not with the
Unexclude line command.

X (Exclude)
Excludes a relationship from the extract. When you exclude a relationship, other relationships
might also be excluded as a result. This occurs when you exclude a relationship and either of the
objects in the excluded relationship is a parent or dependent in another relationship that cannot
be linked back to the driving object in any other way. For example, assume three relationships
exist as shown below and ORDER_TABLE is the driving object.

Parent Object Dependent Object

ORDER_TABLE ORDER_LINE_TABLE
ORDER_LINE_TABLE PART_TABLE
PART_TABLE SUPPLIER_TABLE

When the ORDER_LINE_TABLE to PART_TABLE relationship is excluded, the PART_TABLE to

SUPPLIER_TABLE relationship will also be excluded.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

CHECK (CHE)
Use the CHECK command to verify the extract paths after you made navigation changes. When
the path integrity validation processing is complete, the results are displayed in the Check
Extract Warning screen (Figure 148 on page 285) where you can resolve or ignore the findings.
File-AID/RDX executes the CHECK command whenever it returns from the Extract Scope Detail
View panels.

CHECK is not valid when when the extract request is built with relationships
in the Direct Plus or All Children Only mode (see Direct on page 248).

EXCLUDE (EX or X)
The EXCLUDE command allows to exclude all relationships or all relationships of a specified
object type to be excluded from the extract. EXCLUDE without parameter displays the Exclude
Command Window - Relationship View (see Figure 136).

Use this command in conjunction with the U (Unexclude) line command or UNEXCLUDE
primary command when you have a long list of relationships displayed and you want to include
only a few relationships in the extract.

Enter the EXCLUDE ALL command to exclude all relationships in the list displayed on the
Relationship Criteria screens from the extract.
268 File-AID/RDX Reference

The other parameters DB2, KEY, and MVS limit the EXCLUDE command to one of the three
object types.

EXCLUDE Command Window

When you enter the EXCLUDE command without parameters, File-AID/RDX displays the Exclude
Command Window - Relationship View as shown in Figure 136. Select the object types you want
to exclude from the extract, and optionally, hide from the display.

Figure 136. Exclude Command Window - Relationship View


File-AID/RDX -------------- EXclude Command -------------------
Command ===> 

Relationships with object types to be excluded 
DB2 objects ===> N ( Y = Yes, N = No EXclude DB2 
MVS objects ===> N E = Exclude and hide) EXclude MVS 
KEY files ===> N EXclude KEY 

END to process and return 



Select the object types to exclude, then press END to exit the window.

DB2 objects

Enter Y to exclude all relationships involving Db2 objects. Enter E to exclude and hide all
relationships involving Db2 objects. Enter N if you don’t want to exclude all relationships
involving Db2 objects from the extract. N does not unexclude excluded relationships, use the
UNEXCLUDE primary or line command.

MVS objects

Enter Y to exclude all relationships involving MVS objects. Enter E to exclude and hide all
relationships involving MVS objects. Enter N if you don’t want to exclude all relationships
involving MVS objects from the extract. N does not unexclude excluded relationships, use
the UNEXCLUDE primary or line command.

KEY files

Enter Y to exclude all relationships involving KEY files. Enter E to exclude and hide all
relationships involving KEY files. Enter N if you don’t want to exclude all relationships
involving KEY files from the extract. N does not unexclude excluded relationships, use the
UNEXCLUDE primary or line command.

If a KEY output file is not to be produced for an extract, the relationship

which defines the KEY file must be excluded from the extract.

FILTER (FIL)
The FILTER command restricts the relationships being displayed to the relationships for the
object(s) that contain the specified object name string. Any relationship where the specified
object is either a parent or a child will be displayed. The FILTER command can be issued to build
a display that contains the relationships for multiple objects by choosing the option to retain the
currently filtered list. For example, you could issue the FILTER command to display the
relationships for PROJ resulting in a display of only the PROJ relationships. Then issue FILTER
Extract 269

again, this time requesting the relationships for EMP and specifying to retain the currently
filtered list. The resulting display will contain all relationships for PROJ and EMP. This is the
same functionality available from the object view when the R line command is issued for
multiple objects prior to the VIEW command.

FILTER Command Window

When you enter the FILTER command, File-AID/RDX will display the Filter Command Window as
shown in Figure 137. Enter the object for which you want to display all relationships, and specify
the other filtered list options.

Figure 137. Filter Command Window


Filter Command 
Command ===> 
Display only the relationships where the object name 
contains the following string:

Object Name Field ===> 
Include Creator Name ===> 

Retain Current Filtered List ===> N (Y = Yes, N = No) 

END to process and return 



Specify the object name and filtered list options.

Object Name Field

Enter the name of the object for which to display all relationships.

File-AID/RDX will display all relationships for the object(s) that contain the specified object
name string.

Include Creator Name

Specify whether the displayed relationships for Db2 objects should also include the objects’
creator name.

Retain Current Filtered List

Enter Y to add the specified object to the current list of displayed relationships. Enter N to
clear the current filtered list and display only the relationships for the specified object.

FIND (F)
Searches the list of displayed relationships for the specified string and scrolls the list to display
the first matching entry at the top of the displayed entries. Use RFind to repeat the search.

GRAPHIC (GR)
Enter the GRAPHIC command to invoke the Graphical Relationship Display screen and show RI
and application relationships for the driving object. See Graphical Relationship Display on page
281 for more information on the Graphical Relationship Display screen. There are no operands
associated with this command.
270 File-AID/RDX Reference

HIDE (H)
The HIDE command allows less data to be displayed. With the parameters INcluded and
EXcluded you can hide relationships from the display so that the remaining content is more
meaningful. Hide without a parameter displays the Hide Command Window as shown in Figure
138. Use the RESET command to return all hidden objects to the display.

HIDE Command Window

When you enter the HIDE command without a parameter, File-AID/RDX displays the Hide
Command Window as shown in Figure 138. Select the object status types you want to hide from
the display.

Figure 138. Hide Command Window



File-AID/RDX --------------- HIDE COMMAND -------------------- 
Command ===> 

Object Status to Hide: Primary Command: 
Included ===> N Hide INclude 
Excluded ===> N Hide EXclude 

END to process and return 


Select the object status types to hide or redisplay, then press END to exit the window.

Included

Enter Y to hide all objects/relationships that are included in the extract. Enter N to display all
objects/relationships that are included in the extract.

Excluded

Enter Y to hide all objects/relationships that are excluded from the extract. Enter N to display
all objects/relationships that are excluded from the extract.

NAVIGATION (NAV)
The NAVIGATION command takes you directly to the NAVIGATION format of the relationship
view (see Figure 142 on page 277).

REPORT (REP)
Prints the logical contents of the display. This report includes all of the displayable lines
formatted like the current view.

RESET (RES)
Use the RESET command to return all hidden objects to the display.

SAMPLE (SAM)
The SAMPLE command takes you directly to the SAMPLE format of the relationship view.
Extract 271

SIZE (SI)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. Size is a toggle switch so enter Size again to return to the original format.

SORT (SO)
Sorts the displayed list of relationships by the specified sequence (column) name. Valid SORT
sequences are:

SEQ

(sequence number)

PAR

(parent object name)

DEP

(dependent object name)

ST

(status)

DESC

(description)

STATUS (STAT)
The STATUS command switches the display to the Relationship Criteria view.

UNEXCLUDE (U)
The UNEXCLUDE command allows you to unexclude all relationships or all relationships of a
specified object type to be included in the extract. UNEXCLUDE without parameter displays the
Unexclude Command Window - Relationship View (see Figure 139).

Use this command in conjunction with the X (eXclude) line command or EXCLUDE primary
command when you have a long list of relationships displayed and you want to reverse a
previous EXCLUDE command to include objects in the extract again.

Enter the UNEXCLUDE ALL command to undo a previous EXCLUDE command for all objects in
the list displayed on the Relationship Criteria screens from the extract.

The optional parameters DB2, KEY, and MVS limit the UNEXCLUDE command to one of the three
object types.

UNEXCLUDE Command Window

When you enter the UNEXCLUDE command without parameters, File-AID/RDX displays the
Unexclude Command Window - Relationship View as shown in Figure 139. Select the object
types you want to include in the extract again (reverse a previous EXCLUDE line or primary
command).
272 File-AID/RDX Reference

Figure 139. Unexclude Command Window - Relationship View


File-AID/RDX -------------- Unexclude Command ------------------- 
Command ===> 

Object Types to Unexclude: 
DB2 objects ===> N ( Y = Yes, N = No ) UNEXclude DB2 
MVS objects ===> N UNEXclude MVS 
KEY files ===> N UNEXclude KEY 

END to process and return 



Select the object types to unexclude, then press END to exit the window.

DB2 objects

Enter Y to unexclude all relationships involving Db2 objects. Enter N if you don’t want to
unexclude all relationships involving Db2 objects. N does not exclude included relationships,
use the EXCLUDE primary or line command.

MVS objects

Enter Y to unexclude all relationships involving MVS objects. Enter N if you don’t want to
unexclude all relationships involving MVS objects from the extract. N does not exclude
included relationships, use the EXCLUDE primary or line command.

KEY files

Enter Y to unexclude all relationships involving KEY files. Enter N if you don’t want to
unexclude all relationships involving KEY files from the extract. N does not exclude included
relationships, use the EXCLUDE primary or line command.

If a KEY output file is not to be produced for an extract, the relationship

which defines the KEY file must be excluded from the extract.

VALIDATE (VAL)
The VALIDATE command validates all relationships in the current extract request against the
relationship file. The message “No changes” informs you that all relationships have been
successfully validated. If there are inconsistencies, the Update Saved Request Window reports the
validation results and gives you the opportunity to update the saved request or reload the request
as last saved. Refer to Update Saved Request Window on page 287 for more information.

VALIDATE corresponds to RDX Utilities Option 1, Update Saved Extract Requests, except that it
executes online and only on the current request.

VALIDATE is not valid when the extract request is built with relationships in
the Direct Plus or All Children Only mode (see Direct on page 248).

VIEW (VI)
The VIEW command allows you to easily switch between the object and relationship views. VIEW
without any parameter displays the Extract Scope - Object View screen. VIEW with one of the
Extract 273

parameters SAMPLE, STATUS and NAVIGATION displays the corresponding format of the
relationship view.

Extract Scope - Relationship Sampling Criteria

The Relationship Sampling Criteria screen shown in Figure 140 is displayed when you enter the VIEW
STATUS primary command in the Extract Scope - Object View (Figure 130 on page 256) or any of the
Relationship Criteria screens.

Figure 140. Relationship Sampling Criteria

File-AID/RDX -------- Relationship Sampling Criteria --------- Row 1 from 12 

Command ===> Scroll ===> CSR 

Primary Commands: EXclude/Unex, Change, Find, Hide, FILter, CHEck, SIze, SOrt 
VIew, STATus, SAMple, NAVigation, VALidate, GRaphic, REPort 
Line Commands: X = Exclude U = Unexclude I = Info 
Driving Object: FRSAMP.ORDER_TABLE 
SSID: DSN Location: DSNLOCAT Sampling Criteria 
Seq Object Name Cycle MaxRow Dep Status 
---- ---------------------------------------------- ----- ------ --- ----------
0001 FRSAMP.CUSTOMER_TABLE * * * Inactive
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE * * * 
FRSAMP.ORDER_TABLE CUSTOMER-ORDER RELATIONS 
0003 FRSAMP.ORDER_TABLE * * * 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE * * * 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE * * * Inactive 
FRSAMP.SUPPLIER_TABLE SUPPPART 
0006 FRSAMP.SUPPLIER_TABLE * * * Excl Scope
'TSOID01.FRSAMP.SUPPLIER' 
0007 'TSOID01.FRSAMP.CUSTOMER' * * * Inactive 
'TSOID01.FRSAMP.CONTACTT'

Use this screen to specify which, if any, relationships to exclude from the extract process and how
many rows from dependent objects to extract from those relationships not excluded. In addition, you
can request information about a specific relationship.

This screen displays a list of referential integrity (RI) and application (AR) relationships defined in the
relationship file for the driving object and the sampling criteria setting for each individual
relationship.

If there are more relationships on this list than will fit on this screen, you can scroll the list up and
down using standard scrolling commands. See Scrolling on page 31 for more information about
scrolling.

Fixed Display Area

In addition to the screen title, the Command field, and the scroll amount input field, the top area of
the screen contains

– a message indicating how many relationships were retrieved for display

– a message indicating the driving object for which these relationships were retrieved
– Db2 subsystem ID and remote location ID if the extract includes Db2 objects

Scrollable Display Area

This screen areas displays a list of referential integrity and application relationships containing the
following columns:
274 File-AID/RDX Reference

Seq
The SEQuence column displays the sequence number for the listed relationships for the current
extract request. Enter line commands in this column. See Line Commands on page 258 for
information about valid commands for this screen.

Object Name (Parent)

Displays the name of the object defined as the parent in a relationship in the upper row (the row
with the SEQ number).

Object Name (Dependent)

Displays the name of the object defined as the dependent in a relationship in the lower row,
under its parent.

Sampling Criteria
Displays the status of the three sampling criteria settings for each relationship. Initially, the
sampling criteria are set globally as specified in your current extract profile. You can change each
individual setting simply by typing over a new value or use the CHANGE primary command to
globally change the sampling criteria fields.

Cycle

Specify the maximum number of cycles for each individual relationship. Cycle count limits
the number of times a relationship is visited during an extract.

Max Rows

Specify the maximum number of rows to extract via downward navigation (direct, indirect
and sibling) of this relationship. The Max Rows profile value applies to each relationship and
each object. The relationship Max Rows value is processed first; if the count does not exceed
the limit, the record is passed on to check against the object Max Rows value.

Dep

(Dependents-per-parent) Enter the maximum number of dependent records to be extracted

for each parent record extracted. An asterisk (*) indicates that File-AID/RDX will extract all
dependent records. A value of 2, for example, specifies to select no more than 2 dependent
ORDER records for each extracted parent CUSTOMER record. For KEY relationships, this field
is not applicable.

Status
Displays one of the following messages in the upper row:

Message Explanation
Excl All This relationship is excluded from the current extract process as one of the
related objects is marked to extract all of its records and not chase any of its
relationships. This status is the result of the A (All) line command (page 258)
on the Extract Scope - Object View screen.
Excl Miss This relationship is excluded from the current extract process because at least
one of the related objects does not exist.
Extract 275

Excl Scope This relationship, with navigation (DPSI) settings of “----”, is excluded as the
result of another relationship’s DPSI settings that make it impossible for the
extract to navigate to this relationship. Any changes you make to this
relationship directly have no affect on the extract. This includes changes to the
sampling criteria and the DPSI settings as well.
Inactive A relationship with one or more DPSI switches set to “N”. but none to “Y”, is
considered inactive, but still within the scope of the extract as its DPSI settings
can be changed.

Note that in Object View, an object is marked excluded when all of its
relationships are marked inactive.
Excl User This relationship is excluded from the current extract process. This status is the
result of the EXCLUDE primary or line command.
KEY Undef For this relationship you still need to define an output key file with Extract
Menu Option 6 - Output Key Files or exclude this relationship from the current
extract process, before you can continue.
KEY Def An output key file has been defined for this KEY relationship.
KEY Deleted The output key file definition for this KEY relationship has been deleted.

Relationship Name

The lower, second Status row for each relationship displays the relationship name (Db2 RI
RELNAME or the relationship description for application relationships).

Line Commands
See Line Commands on page 266 for the description of the available line commands.

Primary Commands
See Primary Commands on page 267 for the description of the available primary commands not listed
here.

CHANGE (C)
Change allows global changes to be made to the sampling criteria on a column-by-column basis.
When the CHANGE command is entered with one of the available parameters CYC=n,
MAXROW=n, or DEP=n, all values are changed to the new value n. When entered without
parameters, specify the values to change in the CHANGE Command Window - Relationship
Sampling Criteria.

CHANGE Command Window

When you enter the CHANGE command without parameters, File-AID/RDX will pop up the
CHANGE Command Window - Relationship Sampling Criteria as shown in Figure 141.
276 File-AID/RDX Reference

Figure 141. CHANGE Command Window - Relationship Sampling Criteria



File-AID/RDX -------------- CHANGE COMMAND ------------------- 
Command ===> 

Change ALL occurrences of "from string" value to "to string" 
From string ===> 
To string ===> 

Act on the following fields: Primary command: 
Cycle ===> N ( Y = Yes, N = No) Change CYCle=n 
MaxRow ===> N Change MAXROW=n 
Dep ===> N Change DEP=n 


END to process and return 

***NOTE: Change will be applied to all qualified objects,
even those that are excluded or hidden. 

Enter the Change ‘from string’ and the Change ‘to string’ values and select the sampling criteria
types you want to change globally for all relationships.

From string

Enter the current From (old) string you want to change to the To (new) string in the sampling
criteria.

To string

Enter the to (new) string you want to replace the from (old) string with in the specified
sampling criteria.

Cycle

Enter Y to apply the change to all matching Cycle values. Enter N if the change is not to be
applied to the Cycle sampling criteria.

MaxRow

Enter Y to apply the change to all matching MaxRow values. Enter N if the change is not to
be applied to the MaxRow sampling criteria.

DEP

Enter Y to apply the change to all matching Dependents-per-parent values. Enter N if the
change is not to be applied to the Dependents-per-parent sampling criteria.

Extract Scope - Relationship Navigation Criteria

The Relationship Navigation Criteria screen shown in Figure 142 is displayed when you enter the
VIEW NAVIGATION primary command in the Extract Scope - Object View (Figure 130 on page 256) or
any of the Relationship Criteria screens.
Extract 277

Figure 142. Relationship Navigation Criteria

File-AID/RDX ------- Relationship Navigation Criteria --------- Row 1 from 12 

Command ===> Scroll ===> CSR 

Primary Commands: EXclude/Unex, Change, Find, Hide, FILter, CHEck, SIze, SOrt 
VIew, STATus, SAMple, NAVigation, VALidate, GRaphic, REPort 
Line Commands: X = Exclude U = Unexclude I = Info 
Driving Object: FRSAMP.ORDER_TABLE 
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - - - N Inactive 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y N - 
FRSAMP.ORDER_TABLE CUSTOMER-ORDER RELATIONS 
0003 FRSAMP.ORDER_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE - Y N - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE - - - N Inactive 
FRSAMP.SUPPLIER_TABLE SUPPPART 
0006 FRSAMP.SUPPLIER_TABLE - - - - Excl Scope 
'TSOID01.FRSAMP.SUPPLIER' 
0007 'TSOID01.FRSAMP.CUSTOMER' - - - N Inactive 
'TSOID01.FRSAMP.CONTACTT'

Use this screen to specify which, if any, relationships to exclude from the extract process and how
many rows from dependent objects to extract from those relationships not excluded. In addition, you
can request information about a specific relationship.

This screen displays a list of referential integrity (RI) and application (AR) relationships defined in the
relationship file for the driving object and the navigation criteria setting for each individual
relationship.

If there are more relationships on this list than will fit on this screen, you can scroll the list up and
down using standard scrolling commands. See Scrolling on page 31 for more information about
scrolling.

Fixed Display Area

In addition to the screen title, the COMMAND field, and the scroll amount input field, the top area
of the screen contains

– a message indicating how many relationships were retrieved for display

– a message indicating the driving object for which these relationships were retrieved

Scrollable Display Area

This screen areas displays a list of referential integrity and application relationships containing the
following columns:

Seq
Enter line commands in this sequence column. The sequence number represents File-AID/RDX
internal sequencing of the applicable relationships for the driving object. See Line Commands on
page 258 for information about valid commands for this screen.

Parent/
Displays the name of the object defined as the parent in a relationship in the upper row (the row
with the Seq input field).
278 File-AID/RDX Reference

/Dependent
Displays the name of the object defined as the dependent in a relationship in the lower row,
under its parent.

Navigation Criteria
Here you specify the Navigation Criteria on an individual relationship basis. Initially, they are set
as specified globally on the Extract Scope Screen and cascade through all relationships starting
with the driving object.

A dash (-) in one of the navigation settings indicates that it is not meaningful for this
relationship. You cannot change the dash unless the navigation setting of a higher relationship
changes it to a Y or N.

When your profile has navigation criteria Direct set to C or P (see also Direct
on page 58), all Extract Navigation Criteria fields are protected and cannot
be modified during the extract specification.

To change a setting, type over the displayed value (Y or N) for each relationship:

Dir

(Direct) Y = Extract all of the dependents of the driving object and their dependents. 
N = Don’t extract any of the dependents of the driving object and their dependents.

Par

(Parent) Y = Extract parents of all extracted data to maintain the integrity of the extracted
data.

N = Don’t extract any of the parents of this relationship.

Sib

(Sibling) Y = Extract other dependents of the extracted parents from the same relationships.

N = Don’t extract any of the siblings of this relationship.

Ind

(Indirect) Y = Extract other dependents of the extracted parents from other relationships.

N = Don’t extract any of the indirect dependents of this relationship.

Status
Displays one of the following messages:

Message Explanation
Excl All This relationship is excluded from the current extract process as one of the
related objects is marked to extract all of its records and not chase any of its
relationships. This status is the result of the A (All) line command (page 258)
on the Extract Scope - Object View screen.
Excl Miss This relationship is excluded from the current extract process because at least
one of the related objects does not exist.
Extract 279

Message Explanation
Excl Scope This relationship, with navigation (DPSI) settings of “----”, is excluded as the
result of another relationship’s DPSI settings that make it impossible for the
extract to navigate to this relationship. Any changes you make to this
relationship directly have no affect on the extract. This includes changes to the
sampling criteria and the DPSI settings as well.
Inactive A relationship with one or more DPSI switches set to “N”, but none to “Y”, is
considered inactive, but still within the scope of the extract as its DPSI settings
can be changed.

Note that in Object View, an object is marked excluded when all of its
relationships are marked inactive.
Excl User This relationship is excluded from the current extract process. This status is the
result of the EXCLUDE primary or line command.
KEY Undef For this relationship you still need to define an output key file with Extract
Menu Option 6 - Output Key Files or exclude this relationship from the current
extract process, before you can continue.
KEY Def An output key file has been defined for this KEY relationship.
KEY Deleted The output key file definition for this KEY relationship has been deleted.

Relationship Name

The lower, second Status row for each relationship displays the relationship name (Db2 RI
RELNAME or the relationship description for application relationships).

Line Commands
See Line Commands on page 266 for the description of the available line commands.

Primary Commands
See Primary Commands on page 267 for the description of the available primary commands not listed
here.

CHANGE (C)
Change allows global changes to be made to the navigation criteria on a column-by-column
basis. When the CHANGE command is entered with one of the available parameters DIR=Y or
DIR=N, PAR=Y or PAR=N, SIB=Y or SIB=N, IND=Y or IND=N, the navigation values for all
relationships are changed accordingly. When entered without parameters, specify the navigation
controls to change in the CHANGE Command Window - Relationship Navigation Criteria.

CHANGE Command Window

When you enter the CHANGE command without parameters, File-AID/RDX will display the
CHANGE Command Window - Relationship Navigation Criteria as shown in Figure 143.
280 File-AID/RDX Reference

Figure 143. CHANGE Command Window - Relationship Navigation Criteria



File-AID/RDX -------------- CHANGE COMMAND ------------------------ 
Command ===> 

Extract Navigation Criteria: Primary command: 
Direct ===> Y ( Y = Yes, N = No) Change DIRect=Y/N 
Parents ===> Y Change PARent=Y/N 
Siblings ===> N Change SIBling=Y/N 
Indirect ===> N Change InDirect=Y/N

END to process and return 

***NOTE: Change will be applied to all qualified objects,
even those that are excluded or hidden.


Enter either Y or N for the Navigation criteria settings you want to change globally for all
relationships.

Direct

Y = Extract all of the dependents of the driving object and their dependents. 
N = Don’t extract any of the dependents of the driving object and their dependents.

Parents

Y = Extract the parent records of all extracted data to maintain the integrity of the extracted
data.

Sibling

Y = Extract other dependents of the extracted parents from the same relationships.

Indirect

Y = Extract other dependents of the extracted parents from other relationships.

Extract 281

Graphical Relationship Display

The Graphical Relationship Display screen shown in Figure 144 is displayed when you enter the
GRAPHIC command in one of the three Relationship Criteria screens.

Figure 144. Graphical Relationship Display Screen

File-AID/RDX ----- Graphical Relationship Display ---------- Row 1 to 18 of 23 

COMMAND ===> SCROLL ===> CSR 

TAB to Object and press ENTER for an Option List 
* Denotes the object is involved in additional relationships 

MVS-'TSOID01.FARDX2.SAMP.ZIPCODE' 
| 
|__ DB2-CUSTOMER_TABLE 
| 
|__ MVS-'TSOID01.FARDX2.SAMP.CREDIT' 
| 
|__ DB2-CONTACT_TABLE 
| 
|__ MVS-'TSOID01.FARDX2.SAMP.SALEHIST' 
| 
|__ MVS-'TSOID01.FARDX2.SAMP.INVOICE' 
| 
|__ DB2-ORDER_TABLE 
| 
|__ DB2-ORDER_LINE_TABLE * 


DB2-PART_TABLE 
| 
|__ DB2-ORDER_LINE_TABLE * 
| 
|__ DB2-SUPPLIER_TABLE 

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:

CREATOR
Enter the CREATOR primary command in the graphical relationship display and all Db2 objects
will include their Creator ID. This command acts as a toggle command, thus, when entering the
command again, Db2 objects will include their Creator ID only when there is more than one
object with the same name.

This screen displays a graphical representation of the relationships in which the driving object is
involved. Read the Graphical Relationship Display as follows:

• Objects are identified by their:

– Object type, either DB2, MVS, or KEY
– Object name
• DB2 objects include the table or view name. The Creator name is displayed only if
necessary to have a unique name or when you enter the CREATOR primary command
(see CREATORprimary command).
• MVS objects include the fully qualified file name (quoted).
• KEY objects include the fully qualified KEY record layout file or IMS database file name
(quoted).
• Relationships are arranged such that each object that has no parents is at the top of a group. Each
group consists of an object that has no parents, its dependents, their dependents, etc. File-
AID/RDX displays one group of relationships for each object that has no parents. For example, in
Figure 144, MVS-'FARDX.V2R0M0.FRSAMP.ZIPCODE' and DB2-PART_TABLE have no parents.
282 File-AID/RDX Reference

They are at the top of their groups, respectively. There is one group displayed for MVS-
'FARDX.V2R0M0.FRSAMP.ZIPCODE' and one group displayed for DB2-PART_TABLE

For situations involving cyclical relationships, File-AID/RDX puts the object

for which the most detailed dependent display can be shown at the top of
the group.

• The driving object is highlighted. 

In Figure 144, MVS-'FARDX.V2R0M0.FRSAMP.CREDIT' is the driving object and is therefore
highlighted.
• Relationships are displayed as lines that connect the boxes. Lines start at the bottom of parent
objects and end at the left side of dependent objects. 
In Figure 144 on page 281, MVS-'FARDX.V2R0M0.FRSAMP.ZIPCODE' is a parent of DB2-
CUSTOMER_TABLE. DB2-CUSTOMER_TABLE itself is a parent of MVS-
'FARDX.V2R0M0.FRSAMP.CREDIT' and four other objects.
• Relationships that have been excluded from the extract are denoted by an X to the left of the
dependent object name. In Figure 144 on page 281, the occurrence of 
DB2-ORDER_LINE_TABLE under DB2-PART_TABLE has an X to the left of it. This denotes the
exclusion of the PART_TABLE—ORDER_LINE_TABLE relationship from the extract.
• Objects that are displayed more than once are denoted by an asterisk (*). In Figure 144 on page
281, DB2-ORDER_LINE_TABLE is displayed with an asterisk next to it because it is displayed
twice (once as a dependent of DB2-ORDER_TABLE and again as a dependent of DB2-
PART_TABLE).

You can scroll up, down, left, and right to see information that does not fit on a single screen.

Use the TAB key to move the cursor from object name to object name. When the cursor is next to an
object name, you can press ENTER to display a list of options available as shown in Figure 145. In
addition, you can enter the I line command to display the Relationship Information pop-up window.
See I (Relationship Information) on page 283 for more information about the I line command.

Figure 145. Graphical Relationship Display with Option List

File-AID/RDX ----- Graphical Relationship Display ---------- Row 1 to 18 of 23 

COMMAND ===> SCROLL ===> CSR 

TAB to Object and press ENTER for an Option List 
* Denotes the object is involved in additional relationships 

MVS-'TSOID01.FARDX2.SAMP.ZIPCODE' 
| 
|__ DB2-CUSTOMER_TABLE 
Option List for: MVS-'TSOID01.FARDX2.SAMP.CREDIT' 
Row 1 to 3 of 3 
COMMAND ===> 

Enter "S" to select an option 

CMD Description 
--- ----------------------------------------------------------------- 
_ Display Relationship Information(I) 
_ Go to expanded view of dependents 
_ Go to dependent of MVS-'TSOID01.FARDX2.SAMP.SALEHIST' 
***************************** Bottom of data ***************************** 




To select an option from the Option List, type an S in the CMD column next to an option and press
Enter.

The options in the Option List are as follows:

Extract 283

Display Relationship Information (I)

Displays the Relationship Information pop-up window. See Relationship Information Window on
page 284 for more information.

Exclude Relationships (X)

Excludes the relationship on which the cursor is positioned. When you exclude a relationship,
other relationships might also be excluded as a result. This occurs when you exclude a
relationship and either of the tables in the excluded relationship is a parent or dependent in
another relationship that cannot be linked back to the driving object in any other way.

Undo Excluded Relationships (U)

Selects the previously excluded relationship on which the cursor is positioned to be included in
the extract.

Go to expanded view of dependents

Scrolls the display such that the first occurrence of the selected table is positioned at the top of
the display. The first occurrence of a given table in the Graphical Relationship Display has an
expanded display of its dependents (if it has any). Subsequent occurrences of a given object do
not repeat the expanded display.

In Figure 145 on page 282, for example, if the cursor was positioned on the occurrence of
ORDER_LINE_TABLE under PART_TABLE, selecting Go to expanded view of dependents would
position the first occurrence of ORDER_LINE_TABLE at the top of the display. The occurrence of
ORDER_LINE_TABLE under ORDER_TABLE would display any dependents if ORDER_LINE_TABLE
had any.

Go to dependent of objectname
Scrolls the display such that the occurrence of the selected object that is a dependent of
objectname is at the top of the display. Use this option to determine where the object is a
dependent in other relationships.

For example, if the cursor was positioned on the second occurrence of ORDER_LINE_TABLE when
you pressed ENTER, the following entry would be displayed:

Go to dependent of ORDER_TABLE

Selecting this entry would position the occurrence of ORDER_LINE-TABLE under ORDER_TABLE
at the top of the display. If ORDER_LINE_TABLE had additional parents, there would be an entry
on the Option List for each parent.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen. Enter these commands
when the cursor is positioned next to a table name.

I (Relationship Information)
Displays the Relationship Information pop-up window. See Relationship Information Window on
page 284 for more information about the Relationship Information window.
284 File-AID/RDX Reference

U (Unexclude)
Selects previously excluded relationships to be included in the extract.

X (Exclude)
Excludes a relationship from the extract. When you exclude a relationship, other relationships
might also be excluded as a result. This occurs when you exclude a relationship and either of the
objects in the excluded relationship is a parent or dependent in another relationship that cannot
be linked back to the driving object in any other way. For example, assume three relationships
exist as shown below and ORDER_TABLE is the driving object.

Parent Dependent
ORDER_TABLE ORDER_LINE_TABLE
ORDER_LINE_TABLE PART_TABLE
PART_TABLE SUPPLIER_TABLE

When the ORDER_LINE_TABLE to PART_TABLE relationship is excluded, the PART_TABLE to

SUPPLIER_TABLE relationship will also be excluded.

Relationship Information Window

The Relationship Information window shown in Figure 146 through Figure 147 is displayed when
you enter the I line command on the Extract Scope - Object View screen. Depending on whether you
choose an RI or AR relationship (indicated in the Type field on the Relationship Criteria screen), File-
AID/RDX displays the RI or AR version of the pop-up window. Refer to Relationship Information
Screen on page 107 for a description of the fields in this window.

When you select an RI relationship with a status message, the Relationship Information window is
displayed as shown in Figure 146.

Figure 146. Relationship Information Window — RI Relationship Information

File-AID/RDX Relationship Information DB2 Row 1 to 2 of 2

COMMAND ===> SCROLL ===> CSR 

Parent Name: LOCATION.FRSAMP.ORDER_TABLE Type: DB2 



Dependent Name: LOCATION.FRSAMP.ORDER_LINE_TABLE Type: DB2 



Relationship Details:
Description: RI - ORDLORD
Status:
Created: 1997-08-26 16.03.11.035661 User: TSOID01
Last Modified 1997-08-26 16.03.11.035661 User: TSOID01
Parent Columns /Type(Length) Dependent Columns /Type(Length)
----------------------------------------- ---------------------------------
ORDER_NUMBER ORDER_NUM
CHAR(6) CHAR(6)
*** End Of Columns *** *** End Of Columns ***

When you select an AR relationship, the Relationship Information window is displayed as shown in
Figure 147.
Extract 285

Figure 147. Relationship Information Screen—MVS to DB2 Application Relationship Information

File-AID/RDX Relationship Information DB2 ROW 1 TO 2 OF 2

COMMAND ===> SCROLL ===> CSR

Parent Name: ’FARDX.V2R0M0.FRSAMP.ZIPCODE’ Type: MVS
Layout Dataset: FARDX.V2R0M0.FRSAMP.LAYOUT Mbr: SMPZIP
XREF Dataset: Mbr:
01 Level Name:
Dependent Name: LOCATION.TSOID01.CUSTOMER_TABLE Type: DB2 



Relationship Details:
Description: AR - ZIPCODE TO CUSTOMER
Status:
Created: User:
Last Modified User:
Parent Fields /Type(Length) Dependent Columns /Type(Length)
----------------------------------------- ------------------------------------
PARENT-KEY CHILD-KEY
INTEGER INTEGER
*** End Of Fields *** *** End Of Columns ***

Use the END primary command to return to the Relationship Criteria screen.

Check Extract Warning

When the CHECK extract path routine (see primary command CHECK (CHE) on page 267) finds a
possibly problematic path, File-AID/RDX displays the Check Extract Warning shown in Figure 148.

Review the findings and use the Accept and Ignore primary and line commands to ACCEPT or
IGNORE the suggestions.

Once the problematic relationship(s) have been ignored or accepted, and

you exited this window, File-AID/RDX retains your choices and you must
enter the CHECK primary command to change the resulting status.

Figure 148. Check Extract Warning

File-AID/RDX ------------ Check Extract Warning ------------ Row 1 to 1 of 1 

Command ===> Scroll ===> PAGE 

Primary Commands: Accept, Ignore, VIew (END = Ignore) 
Line Commands: A = Accept path I = Ignore path 
Driving Object: FRSAMP.ORDER_TABLE 
SSID: DSN Location: DSNLOCAT 
Object Name Status 
---------------------------------------------- ------------------------- 
_ FRSAMP.CUSTOMER_TABLE Excl User 
FRSAMP.ORDER_TABLE Parent path required 
******************************* Bottom of data ********************************

Object Name (Parent)

Displays the name of the object defined as the parent in a relationship in the upper row (the row
with the line command input field).
286 File-AID/RDX Reference

Object Name (Dependent)

Displays the name of the object defined as the dependent in a relationship in the lower row,
under its parent.

Status
Displays one of the navigation status messages as described on page 278.

The lower, second Status row for each relationship displays the check extract path status:

Message Explanation
Parent path This relationship is required to ensure that extracted dependent records
required maintain relational integrity. If ignored, extracted orphan records might not be
loadable without their corresponding parent records.
Parent path
Because the excluded object is missing you cannot include it with the ACCEPT
required - Excl
line or primary command.
Miss
Relational error You marked this relationship with the IGNORE line or primary command and
ignored it will remain excluded for the extract.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

ACCEPT (A)
Accept all suggested relationships to be included in the extract. When you press Enter, you return
to the previous Extract Scope Detailed View screen where you entered the CHECK command or
the Extract Scope screen when you exited the “Extract Scope Detailed View” screens.

IGNORE (I)
Ignore all suggested relationships, they will not be included in the extract and their status
changes to “Relational error ignored”. You can still use the Accept Path line command to change
the status individually or enter the ACCEPT primary command.

VIEW (VI)
The VIEW command allows you to easily switch between the object and relationship views.
SAMPLE, STATUS and NAVIGATION can be used to go directly to the corresponding format of the
relationship view.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

A (Accept Path)
Accept an individual relationship to be included in the extract.
Extract 287

I (Ignore Path)
Ignore an individual relationship, it will not be included in the extract and its status changes to
“Relational error ignored”. You can still use the Accept Path line command to change the status
individually or enter the ACCEPT primary command.

Update Saved Request Window

When you view a previously saved extract request and enter the VALIDATE command (VALIDATE
(VAL) on page 272) in the Relationship Criteria screens and the validation routine finds one or more
inconsistencies File-AID/RDX displays the Update Saved Request Window (see Figure 149).

Figure 149. Relationship Listing — Update Saved Request Window

File-AID/RDX ------- Relationship Navigation Criteria ---------- Row 1 from 3 

Update Saved Request 
Command ===> SCR Row 1 to 11 of 22 

Use END to replace the original request with the updated request 
CANCEL to revert to the original request 

Original Request: TSOID01.FRSAMP45.EXTCRIT(GDGWSEL) 

Message Action/Description 
-------- ----------------------------------------------------------------- 
RDXEE210 A relationship in the request is no longer in the relati 
onship dataset. 
RDXEE198 Parent. . .:MVS-TSOID01.GDG.BASE(0) 
RDXEE199 Dependent:MVS-TSOID01.GDG.BASE(-1) 
RDXEE210 A relationship in the request is no longer in the relati 
onship dataset. 
RDXEE198 Parent. . .:MVS-TSOID01.GDG.BASE(0) 
RDXEE199 Dependent:MVS-TSOID01.GDG.BASE(-3) 
RDXEE210 A relationship in the request is no longer in the relati 
onship dataset. 
RDXEE198 Parent. . .:MVS-TSOID01.GDG.BASE(0) 



Review the results of the validation and decide whether to update the extract request with the new
information from the relationship file and continue with the extract request or whether to cancel the
update and reload the request as you last saved it.

VALIDATE corresponds to RDX Utilities Option 1, Update Saved Extract Requests, except that it
executes online and only on a single request. Refer to Update Saved Extract Requests on page 692 for
more information on updating an extract request with current relationship information.

Primary Commands
The following File-AID/RDX-specific primary commands are valid in this window:

END
Updates and saves the extract request with the new information from the relationship file.
288 File-AID/RDX Reference

CANCEL
Cancels the update of the extract request and reloads the request as you last saved it.

When cancelling the update you lose all changes made to the request since
the last SAVE.

Unrelated Object Definition

The Unrelated Object Definition screen shown in Figure 150 is displayed when you select Option 3 -
Unrelated Objects on the Extract Menu and your extract request doesn’t include any unrelated
objects. It is also displayed when you enter the A line command in the Unrelated Object
Specification screen.

Figure 150. Unrelated Object Definition

File-AID/RDX ---------- Unrelated Object Definition -------------------------

Command ===> 
* No unrelated objects defined *

Object Type ===> M (DB2 or MVS) 

Specify DB2 Table for Object:
SSID ===> DSN (* or pattern for selection list)
Location ===> LOCATION (* or pattern for selection list)
Creator ===> TSOID01 (* or pattern for selection list)
Table Name ===> DEPT (* or pattern for selection list)

Specify MVS file for Object:
File name ===> ’TSOID01.FRSAMP.CUSTOMER’
Record layout usage ===> (S = Single; X = XREF;)
Record layout dataset ===> ’TSOID01.FRSAMP.LAYOUT’
Member name ===> (Blank or pattern for member list)
XREF file name ===>
Member name ===> (Blank or pattern for member list)
I/O Exit Name ===>

ENTER to add

Use this screen to add an object, Db2 table or MVS file, to the set of objects to be extracted. Press
Enter to add an object to the list of unrelated objects and stay on this screen. Enter END after you
added all unrelated objects and the Unrelated Object Specification screen (Figure 152 on page 292)
will display the list of all the unrelated objects for this extract request.

The body of the Unrelated Object Definition screen consists of the following fields:

Object Type
Specify the object type of the unrelated object you want to include in the current extract set.

DB2 Db2 table

MVS MVS file

Specify DB2 Table for Object Area

Use the fields in this area to specify the unrelated Db2 table to be added to the extract set. When
specifying patterns in the fields, File-AID/RDX presents the Add Unrelated DB2 Object window
shown in Figure 151 to assist in finding the desired table(s).
Extract 289

SSID
Enter the Db2 subsystem ID where the unrelated table to be extracted resides. This field is
prefilled and protected when other Db2 tables are already part of the extract set. All Db2 tables in
an extract must reside in the same subsystem. 
As long as your extract request does not include Db2 objects the Db2 subsystem ID from your
current profile is prefilled, but the field is not protected.

Location
Enter the Db2 remote location ID where the unrelated table to be extracted resides. This field is
prefilled and protected when other Db2 tables are already part of the extract set. All Db2 tables in
an extract must reside in the same subsystem.

Creator
Specify the authorization ID of the owner of the Db2 table to be added to the extract set.

Table Name
Specify the name of the unrelated table or view you want to add to the extract set.

Enter an asterisk (*) or pattern in the Creator or Table Name fields to select
one or multiple Db2 objects from a list (see Add Unrelated DB2 Object).

Specify MVS File for Object Area

Use the fields in this area to specify the unrelated MVS file you want to include in the extract set.
When specifying patterns in the fields, File-AID/RDX presents selection lists.

File name
Specify the MVS file name of the unrelated object. To complete the specification of the MVS
object you must also specify its record layout information.

Record layout usage

Indicate whether a single record layout (usage "S"), or an XREF (usage "X") is to be used to define
the selection criteria.
You must also supply a Record Layout file and member (Usage=S) or an XREF file and member
(Usage=X).

Record layout file

Specify the record layout file for the unrelated MVS object to be added to the extract set.

Member name
Specify the member of the record layout file that contains the layout information for the
unrelated MVS object. Leave blank or use a pattern to select a member from a list.
290 File-AID/RDX Reference

XREF file name

Only needed if layout usage is X. Specify the XREF file name for the unrelated MVS object to be
added to the extract set.

Member name
Specify the member of the XREF file that contains the layout information for the unrelated MVS
object. Leave blank or use a pattern to select a member from a list.

I/O Exit Name

Specify the I/O Exit Name for the unrelated MVS object.

You only need to fill in this field when you want File-AID/RDX to use an IO exit routine when
accessing the above MVS file.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

END
If unrelated objects have been added, END displays the Unrelated Object Specification screen,
which lists all unrelated objects to be extracted. If none were added you would return to the
Extract Menu.

MENU
Returns to the Extract Menu.

SQLID
Enter the SQLID primary command to change the current Db2 SQLID. Enter the SQLID command
without an operand to change the current SQLID to match the current userid. Use the new-sqlid
operand to specify any SQLID. See also Default SQLID on page 61.

Add Unrelated DB2 Object

The Add Unrelated DB2 Object window shown in Figure 151 is displayed whenever you enter an
asterisk (*) or pattern in the DB2 Creator or DB2 Table Name fields of the Unrelated Object Definition
panel. It displays the results of your Db2 object filter search and allows you to select all, none, or
individual objects to be included in the extract request as unrelated objects.

Use this window to select the Db2 objects you want to include as unrelated objects.
Extract 291

Figure 151. Add Unrelated DB2 Object

Fi Add Unrelated DB2 Object 

CO Row 1 to 13 of 18 
Command ===> SCROLL ===> CSR 
Primary Commands: ALL, Find 
Ob Line Commands: S = Select 

Sp Select objects and press END to process 
S tion list) 
L Object Name tion list) 
C ----------------------------------------------- tion list) 
T _ FARDX.CONTACT_TABLE tion list) 
_ FARDX.CUSTOMER_TABLE 
_ FARDX.CUSTOMER_1 
Sp _ FARDX.ORDER_LINE_TABLE 
F _ FARDX.ORDER_TABLE 
R _ FARDX.PART_TABLE 
R _ FARDX.PICX_PIC9 
M _ FARDX.SUPPLIER_TABLE mber list) 
X _ FARDX0.EDPMATTRIBUTE 
M _ FARDX0.EDPMAUATTRIBUTE mber list) 
I _ FARDX0.EDPMAUMETADATA 
_ FARDX0.EDPMAUOBJECT 
_ FARDX0.EDPMAUOBJSECURITY 


After selecting all desired Db2 objects to be included in the unrelated object list, press END to
proceed to the Unrelated Object Specification. If you press END without selecting any objects, you
return to the Unrelated Object Definition panel.

Object Name
Identifies the names of the Db2 objects that match the specified object filter.

Line Commands
The following File-AID/RDX-specific line command is valid:

S (Select)
Selects and marks this object to be included in the unrelated object list. Blank out the S marker
for individual objects you don’t want included in the unrelated object list. Use in conjunction
with the ALL primary command to mark your selections.

Primary Commands
The following File-AID/RDX-specific primary commands are valid:

ALL
Selects and marks all objects listed in the preview to be included in the unrelated object list.
Blank out the S marker for individual objects you don’t want included in the unrelated object
list. Use in conjunction with the S line command to mark your selections.

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.
292 File-AID/RDX Reference

Unrelated Object Specification

The Unrelated Object Specification screen shown in Figure 152 is displayed when you select Option 3
- Unrelated Objects on the Extract Menu and your extract request already includes one or more
unrelated objects or after you added unrelated objects in the Unrelated Object Definition screen.

Figure 152. Unrelated Object Specification

File-AID/RDX --------- Unrelated Object Specification ------ Row 1 to 2 of 2 

Command ===> Scroll===>
CSR


Primary Commands: MENU
Line commands: A = Add Object M = Modify MVS Object
R = Remove U = Undo Remove

CMD Object Name Type Status
--- ------------------------------------------------- ---- ------------------ 
_ LOCATION.FRSAMP.EMP DB2
_ LOCATION.FADB2.ORDER_1 DB2
******************************* Bottom of data ********************************


This screen lists all unrelated objects that are to be extracted with the current extract request. Here
you can use line commands to add objects or remove them from the list. Enter MENU or END to
return to the Extract Menu.

To add sampling criteria to unrelated objects, go to Extract Scope - Object View on page 256, to add
selection criteria, go to Object Selection Criteria on page 301.

The scrollable area has the following columns:

CMD
Specify whether you want to

• modify the layout information for an MVS object (M line command)

• add an unrelated object (A line command)
• remove an unrelated object (R line command)
• reverse removing an unrelated object (U line command)

Object Name
Displays a list of the unrelated objects from which data is to be extracted.

Type
Displays the object type of the unrelated object.

DB2 Db2 table.

MVS MVS file.
Extract 293

Status
Displays the status of the objects to be extracted. If the status message indicates an error, you
must correct the error before proceeding with the extract.

Message Explanation
Added The unrelated object has been added to the extract set.
Object not found The object does not exist.
Removed The unrelated object has been marked as remove pending with the
R (Remove) line command and will not be extracted when you
END out of the panel. You can reverse the Removed status with the
U (Undo Remove) line command or the CANCEL primary
command.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

A (Add)
Adds an unrelated object to the extract set. When you enter the A line command, File-AID/RDX
displays the Unrelated Object Definition screen where you can specify either an MVS file or a
Db2 table, see Figure 150 on page 288.

M (Modify)
Use this command to change the record layout or XREF information for an MVS object. See
Figure 153.

R (Remove)
Removes the unrelated object from the extract set.

U (Undo Remove)
Reverses removing the unrelated object from the extract set.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

MENU
Switches from this panel to the full Extract Menu.
294 File-AID/RDX Reference

Modify Unrelated MVS Object Definition

The Modify Unrelated MVS Object Definition screen shown in Figure 153 is displayed after you
entered the M (Modify) line command for an unrelated MVS object in the Unrelated Object
Specification screen.

Use this screen to modify the record layout and/or XREF information for the selected MVS file.

Figure 153. Modify Unrelated MVS Object Definition

File-AID/RDX ---- Modify Unrelated MVS Object Definition --------------------


Command ===> 

Specify MVS File for Object: 
File Name..............: 'TSOID01.FRSAMP.CONTACTT' 
Record layout usage ===> S (S = Single; X = XREF) 
Record layout File ===> 'TSOID01.FRSAMP.LAYOUTS' 
Member name ===> CONTACTT (Blank or pattern for member list) 
XREF File name ===> 
Member name ===> (Blank or pattern for member list) 
I/O exit name ===> 

After modifying or viewing the MVS object information, press END to return to the Unrelated Object
Specification screen.

Specify MVS File for Object Area

You can change the object definition for the selected unrelated MVS file from which you want to
extract data. When specifying patterns in the fields, File-AID/RDX presents selection lists.

File name
Displays the file name of the unrelated MVS file from which you want to extract data.

Record layout usage

Indicate whether a single record layout (usage "S"), or an XREF (usage "X") had been used to
define the selection criteria. Only needed when no relationships have been defined for the MVS
file.

Record layout file

Specify the record layout file for the MVS object from which you want to extract data. To view a
list of layout files, specify a pattern. Valid pattern character is * (see Pattern Characters on page
27). If you specify a pattern, the MVS Catalog Utility File List window shown in Figure 121 on
page 236 is displayed if defined relationships match.

Member name
Specify the member of the record layout file that contains the layout information for the MVS
object. Leave blank or use a pattern to narrow the search.
Extract 295

XREF file name

Only needed if layout usage is X. Specify the XREF file name for the MVS object from which you
want to extract data. Valid pattern character is * (see Pattern Characters on page 27). If you
specify a pattern, the MVS Catalog Utility File List window shown in Figure 121 on page 236 is
displayed if defined relationships match.

Member name
Specify the member of the XREF file that contains the layout information for the MVS object.
Leave blank or use a pattern to narrow the search.

I/O Exit Name

Specify the I/O Exit Name for the unrelated MVS file you want File-AID/RDX to use when
accessing the MVS file.

Input Key File Specification

The Input Key File Specification screen shown in Figure 154 displays when you select Option 4 -
Input Key File on the Extract Menu.

You can specify an Input Key File for either a Db2 or MVS driving object.

When an Input Key File is defined against an MVS object with an XREF, you
must select a single layout to use when extracting from the driving object.
The selected layout will be used for all records on the file; XREF processing
will not be invoked against the driving object.

Figure 154. Input Key File Specification

File-AID/RDX --------- Input Key File Specification -------------------------

Command ===> 

Driving Object: LOCATION.FRSAMP.PART_TABLE

Specify Input Key File Information: 
Extract Driven by Input Key File ===> N ( Yes or No ) 
File Name ===> 
Member ===> 

Specify Delimited File Information: 
Delimited ===> NO ( Yes or No )
Quotation Marks ===> 1 (1 = Single, 2 = Double) 
Column Delimiter ===> , 
Quotes on Character Data ===> YES (Yes or No) 
Quotes on Numeric Data ===> NO (Yes or No) 

If you are not using an Input Key File as input to the selection criteria for the driving object, simply
enter No (default) for the Extract Driven by Input Key File field and press END to return to the Extract
Menu.
296 File-AID/RDX Reference

If, however, you intend to use an Input Key File as input criteria for the driving object, you must
enter Yes for the Extract Driven by Input Key File field, enter the key file’s file name and specify the
key file’s format (standard Db2 or delimited). Then press Enter to continue.

The Input Key file can only have data in three formats: CHARACTER, BINARY,
and DECIMAL. For DECIMAL, the length can only be specified in bytes and
the number of decimal places is implied to be 0.

The Output Key files produced from the KEY relationships (see also Output Key Files on page 330) can
be used as Input (External) Key files within other File-AID/RDX extracts.

This functionality provides solutions for the following:

1. Split the Extract

Some large extracts can be broken up an into multiple jobs so that independent legs of the related
objects can be extracted concurrently. The use of a KEY relationship provides a technique to
accomplish this.

One extract request can be defined to extract the higher level related objects and produce Output
Key files for each independent leg of the related set. Once that Extract has been run the Output
Key files can then be used an Input Keys files for other extracts.

You must ensure that the relationships in the subsequent extracts are really independent and do
not require additional rows to be extracted from objects in the original extract. Also, since the
Driving object for the subsequent extracts would be a dependent object from the first extract, the
DPSI switches (see Extract Navigation Criteria on page 248) for the parent path of these
relationships should be set to N.

2. Unequal Column Lengths

When column lengths are unequal in a relationship, File-AID/RDX logic forces a tablespace scan
due to the unequal column lengths. For example, in a situation where the dependent value
always had trailing blanks and the parent value did not, KEY file generation could be used for this
relationship. Then, in the resulting Output Key file the parent value could be padded with blanks
and the Output Key file could be used as the Input Key file which would allow for an index scan
to be used.

The body of the Key File Specification screen consists of the following fields:

Specify Input Key File Information Area

Extract Driven by Input Key File

Specify Yes only when you are using an Input (external) Key File as selection input criteria for the
driving object. No is the default.

File Name
Specify the name of the file containing the keys you want to use as input criteria for the driving
object.

The key file must be in sequential or PDS format.

Extract 297

Member
If the file is partitioned, specify the name of the member that contains the key data.

Specify Delimited File Information Area

Delimited
Specify whether the key file’s format is Standard Db2 (No, default) or Delimited (Yes). Yes will
continue with the Input Key File - Delimited screen as shown in Figure 156 on page 300. No will
continue with the Input Key File - Positional screen as shown in Figure 155 on page 298.

The extract will fail if you specify the wrong format.

Review the delimited file format options currently set by File-AID/RDX. Compare them to the
actual delimited key file and modify the format options as needed.

Quotation Marks
Specify which quotation marks, single (’) or double (") are used in the key file. Enter a 1 for single
quotation mark. Enter a 2 for double quotation mark.

Column Delimiter
Specify which character is used as the column delimiter. The column delimiter marks the end of
the previous and the beginning of the next column. Any displayable character, including blank
character, is acceptable.

Quotes on Character Data

Specify whether character data is enclosed by quotation marks. When set to Yes, File-AID/RDX
expects character data to look like "JONES","MARY". Numbers containing special characters, for
example date fields, are considered character data. For example, if set to Yes the date field could
look like this "1995-09-29". When set to No the data in the key file would look like this:
JONES,MARY or 1995-09-29.

Quotes on Numeric Data

Specify whether numeric data is enclosed by quotation marks. When set to Yes, the numeric data
in the key file should look like "12345","6789". When set to No, File-AID/RDX expects numeric
data to look like 12345,6789.

Input Key File - Positional

When you specify a non-delimited, standard Db2 format Input Key File as selection criteria for the
driving object, the Input Key File - Positional screen is displayed as shown in Figure 155.

Enter the key information for the applicable column(s) and press END to exit this screen.
298 File-AID/RDX Reference

Figure 155. Input Key File - Positional

File-AID/RDX --------- Input Key File - Positional --------------------------

Command ===> SCROLL ===> CSR

Driving Object: LOCATION.FRSAMP.ORDER_TABLE 

Display Input Key File ===> B ( N = No; B = Browse; E = Edit) 
Key-Format Codes available 1 = Display, 2 = Packed Decimal, 3 = Binary

Column Name Type(Length) Key-Postion Key-Length Key-Format 
-------------------- ------------------ ----------- ---------- ---------- 
ORDER_NUMBER CHAR(6) 
CUST_NUM CHAR(6) 
SOC_SEC_NUM CHAR(11)
CREDIT_CARD_NUM CHAR(16)
ORD_TYPE CHAR(8) 
ORD_DATE DATE 
ORD_STAT CHAR(8) 
ORD_AMOUNT DEC(9,2) 
ORD_DEPOSIT DEC(9,2) 
ORD_LINE_COUNT INTEGER 
SHIP_CODE CHAR(2) 
SHIP_DATE DATE 
ORD_DESCRIPTION VCHAR(100) 
** End of Columns ** 

Display Input Key File

Specify whether you want to view or edit the contents of the key file you specified as selection
input for the driving object. You may want to browse or edit the key file to verify the key file’s
content.

N Don’t browse or edit the key file.

B File-AID/RDX will show you the contents of the key file in browse mode. Use the
standard UP, DOWN, LEFT, or RIGHT scrolling commands to view the file. Press End
to exit the browse mode.
E File-AID/RDX will show you the contents of the key file in edit mode. Use the
standard ISPF Edit commands to edit the file. Press End to exit the edit mode.

Column Name
Displays the names of the columns in the driving object.

Type(Length)
Displays the data type of each column in the driving object. See Table 13 on page 306 for more
information about Db2 data types.

Key File Options

When you want to use the values of a key file as selection input (WHERE EQUAL TO) for a column of
the driving object, you must enter all three fields of the Key File Options. For example, you intend to
extract all rows in the Db2 driving table where column CUST_NUM equals the value(s) of the
corresponding column in the key file. In the key file, the value to use starts in Key-Position 7, has a
Key-Length of 6, and Key-Format 1 (Display). File-AID/RDX will open the key file, take the values it
finds from position 7 to 12 for all records, and extracts all rows matching the key values.

Distinct (UDT), large object (CLOB, BLOB, or DBCLOB) and ROWID columns
are not eligible for key file selection.
Extract 299

Key-Position
Specify the starting position of the selection value in the key file that contains selection criteria
values for the corresponding column of the driving object.

Key-Length
Specify the length of the selection value in the key file that contains selection criteria values for
the corresponding column of the driving object. See Table 12 for the allowable lengths for each
key file format.

Key-Format
Enter the Key File Format Code that represents the non-delimited key file’s column type format.
The valid codes are listed in the upper section of the screen. They are

1 Display format.
2 Packed Decimal format.
3 Binary format. Valid only for Db2 INTEGER and
SMALL_INTEGER column types.

When key file options are entered, File-AID/RDX checks that format and length are compatible
with the Db2 column type and length.

Table 12 lists the maximum key file lengths allowed for each key file format and the
corresponding Db2 column type.

Table 12. Maximum Key File Lengths

Db2 Column Length - Length - Packed Length - Binary
Type Display Format 1 Decimal Format 2 Format 3
CHAR <= Db2 column length <= (Db2 column length)/2 Not allowed
SMALL INTEGER <=6 <=3 =2
INTEGER <=11 <=6 =4
DECIMAL <=Precision+2 <=(Precision+1)/2 Not allowed

Input Key File - Delimited

When you specify a delimited format Input Key File as selection criteria for the driving object, the
Input Key File - Delimited screen is displayed as shown in Figure 156.

Enter the key field number for the applicable column(s) and press END to exit this screen.
300 File-AID/RDX Reference

Figure 156. Input Key File - Delimited

File-AID/RDX -------- Input Key File - Delimited ----------------------------

Command ===> SCROLL ===> CSR 

Driving Object: LOCATION.FRSAMP.ORDER_TABLE 

Display Input Key File ===> B ( N = No; B = Browse; E = Edit) 

Column Name Type(Length) Field-Number in delimited file 
-------------------- ------------------ ------------------------------ 
ORDER_NUMBER CHAR(6) 
CUST_NUM CHAR(6) 
SOC_SEC_NUM CHAR(11)
CREDIT_CARD_NUM CHAR(16)
ORD_TYPE CHAR(8) 
ORD_DATE DATE 
ORD_STAT CHAR(8) 
ORD_AMOUNT DEC(9,2) 
ORD_DEPOSIT DEC(9,2) 
ORD_LINE_COUNT INTEGER 
SHIP_CODE CHAR(2) 
SHIP_DATE DATE 
ORD_DESCRIPTION VCHAR(100) 
** End of Columns ** 

Display Input Key File

Specify whether you want to view or edit the contents of the key file you specified as selection
input for the driving object. You may want to browse or edit the key file to verify the key file’s
content.

N Don’t browse or edit the key file.

B File-AID/RDX will show you the contents of the key file in browse mode. Use the
standard UP, DOWN, LEFT, or RIGHT scrolling commands to view the file. Press End
to exit the browse mode.
E File-AID/RDX will show you the contents of the key file in edit mode. Use the
standard ISPF Edit commands to edit the file. Press End to exit the edit mode.

Column Name
Displays the names of the columns in the driving object.

Type(Length)
Displays the data type of each column in the driving object. See Table 13 on page 306 for more
information about Db2 data types.

Field Number in Delimited File

When using a delimited Input Key file you specify the field number from the key file that
contains selection criteria values for the corresponding column(s) of the driving object. For
example, you want to extract all rows in the Db2 driving object where column ORDER_NUMBER
equals the value(s) of Field 2 in the delimited key file.

Distinct (UDT), large object (CLOB, BLOB, or DBCLOB) and ROWID columns
are not eligible for key file selection.
Extract 301

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

CANCEL (CAN)
Enter the CANCEL command to return to the Selection Criteria Specification screen without
saving any changes. There are no operands associated with this command.

END
Verifies the SQL syntax and returns you to the Selection Criteria Specification screen. There are
no operands associated with this command.

UDTSWAP (UDTS)
Swaps the display for distinct type columns from UDT name to the built-in data type and length
and vice versa. There are no operands associated with this command.

UDTTYPE (UDT)
Lists all distinct data types (UDTs) that are part of the extract. The list displays the schema, UDT
name, and the built-in data type and length. There are no operands associated with this
command.

Object Selection Criteria

The Object Selection Criteria screen shown in Figure 157 is displayed when you select Option 5 -
Selection Criteria on the Extract Menu.

Figure 157. Object Selection Criteria

File-AID/RDX ------------ Object Selection Criteria ---------------------------

Command ===> SCROLL ===> CSR

Primary Commands: INSert, BACK, FORward, DEL, SOrt
Line Commands : S = Add/Update Criteria D = Delete Criteria 
Driving Object: FRSAMP.ORDER_TABLE 
SSID: DSN Location: LOCATION Set 1 of 1 

CMD Object Name Status
--- ----------------------------------------------- --------------------
_ FRSAMP.ORDER_TABLE Driving
_ FRSAMP.CONTACT_TABLE Object Excluded
_ FRSAMP.CUSTOMER_TABLE
_ FRSAMP.ORDER_LINE_TABLE
_ FRSAMP.PART_TABLE
_ FRSAMP.SUPPLIER_TABLE Object Excluded
_ 'TSOID01.FRSAMP.CUSTOMER' Unrelated with Criteria
** End of List **

Use this screen to perform the following tasks:

• Define one or more selection criteria sets for this extract.

• View or modify the list of objects from which File-AID/RDX will extract data.
• Select objects for which you want to specify or delete selection criteria.

This screen lists all objects that are part of the extract, including all unrelated objects specified with
Option 3 - Unrelated Objects in the Extract Menu and all excluded objects. If there are more objects
302 File-AID/RDX Reference

on this list than will fit on this screen, you can scroll the list up and down using standard scrolling
commands. See Scrolling on page 31 for more information about scrolling.

In addition to the screen title, the Command field, and the scroll amount input field, the top area of
the screen contains

– the name of driving object for the extract request

– Db2 subsystem ID and remote location ID if the extract includes Db2 objects

The body of this screen consists of:

SET 1 of 1
This message indicates which selection criteria set of the extract request you are currently
viewing, defining, or modifying. For example, set 1 of 6 means that the current set is set one out
of a total of 6 sets. To switch to another set, or insert, or delete a set, use one of the set primary
commands BACK, FORWARD, INSERT, REPEAT, or DELETE.

Option 10- Checkpoint/Resumption is not available when the extract

request includes multiple selection criteria sets (see also 10-
Checkpoint/Resumption on page 242).

CMD
Specify whether you want to

• add or modify selection criteria (S line command), or

• delete selection criteria (D line command) for a given object

Object Name
Displays a list of objects from which data is to be extracted. When you use existing extract
criteria with Db2 tables this column contains the creators associated with the tables listed in the
extract criteria file. Otherwise, this column contains the creator associated with the object
driving the extract.

Status
Displays the status of the objects to be extracted. The following messages are informational:

Message Explanation
Driving Indicates the object selected to drive the extract.
Driving with Indicates that selection criteria has been specified for the driving
Criteria Spec object.
Criteria Specified Indicates that selection criteria has been specified for the object.
Object Excluded The object has been excluded from the extract request.
All object Indicates a related object with status ALL.
All object with Indicates that selection criteria has been specified for the related
Criteria object with status ALL.
Unrelated Object Indicates an unrelated object that has been added with option 3 -
Unrelated Objects, for this extract request.
Unrelated with Indicates that selection criteria has been specified for the unrelated
Criteria object.
Extract 303

The following messages indicate errors. You must correct these errors before proceeding with the
extract.

Message Explanation
Col Mis xxxx The named column is part of the RI or application relationship, but
does not exist in the object you want to extract.
Object not found The object does not exist.
Col Len xxxx The column length for the specified column in the relationship file
or extract criteria file is not the same as in the table you want to
extract.
Col Typ xxxx The column type for the specified column in the relationship file or
extract criteria file is not the same as in the table you want to
extract.
Selection Criteria
The selection criteria specified does not match the object.
Invalid

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

D (Delete)
Deletes existing selection criteria for the specified object.

S (Select)
Use this command to create new selection criteria or update existing selection criteria.

– When the object is a Db2 table, S invokes the DB2 Object Selection Criteria screen (see Figure
158 on page 305).
– Invokes the MVS File Selection Criteria screen when specified for an MVS file (see Figure 162
on page 312).

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

BACK (BA)
Displays the previous selection criteria set in a criteria file (see also Object Selection Criteria on
page 301). There are no operands associated with this command.

DELETE
Deletes the current selection criteria set in a criteria file. Valid only on the Selection Criteria
Specification Screen when defining or modifying multiple selection criteria sets (see Object
Selection Criteria on page 301). There are no operands associated with this command.

END
Returns to the previous screen. Any newly specified selection criteria will not be saved. There are
no operands associated with this command.
304 File-AID/RDX Reference

FORWARD (FOR)
Displays the next selection criteria set in a criteria file. Valid only on the Selection Criteria
Specification Screen when defining or modifying multiple selection criteria sets (see Object
Selection Criteria on page 301). There are no operands associated with this command.

INSERT (INS)
Inserts a new selection criteria set after the currently displayed set in a criteria file. The new set’s
id number equals the current set’s number incremented by 1. Example: current id = 3 of 5, id of
inserted set= 4 of 6. Any following set id numbers in the criteria file are of course incremented
accordingly, for example 4 of 5 becomes 5 of 6, 5 of 5 becomes 6 of 6. Valid only on the Selection
Criteria Specification Screen when defining or modifying multiple selection criteria sets (see
Object Selection Criteria on page 301). There are no operands associated with this command.

REPEAT (REP)
Repeats (duplicates) the current selection criteria set after the currently displayed set in a criteria
file. The new set’s id number equals the current set’s number incremented by 1. Example: current
id = 1 of 5, id of inserted set= 2 of 6. Any following set id numbers in the criteria file are of course
incremented accordingly, for example 2 of 5 becomes 3 of 6, 3 of 5 becomes 4 of 6, etc.. Valid
only on the Selection Criteria Specification Screen when defining or modifying multiple selection
criteria sets (see Object Selection Criteria on page 301). There are no operands associated with
this command.

SORT (SO)
Sorts the displayed list of object names by the specified sequence (column) name. Valid SORT
sequences are:

(Object Name)

ST

(Status)

Object Selection Criteria

The DB2 Object Selection Criteria screen shown in Figure 158 is displayed when you select a Db2
object.
Extract 305

Figure 158. DB2 Object Selection Criteria

File-AID/RDX --------- DB2 Object Selection Criteria ------------------------

Command ===> SCROLL ===> CSR 
Set 1 of 1 
Specify selection criteria for table FRSAMP.ORDER_TABLE 


Column Name Type(Length) Where More: > 
-------------------- ------------------ ----+---10----+---20----+---30---- 
ORDER_NUMBER CHAR(6) 
CUST_NUM CHAR(6) 
SOC_SEC_NUM CHAR(11)
CREDIT_CARD_NUM CHAR(16)
ORD_TYPE CHAR(8) 
ORD_DATE DATE 
ORD_STAT CHAR(8) 
ORD_AMOUNT DEC(9,2) 
ORD_DEPOSIT DEC(9,2) 
ORD_LINE_COUNT INTEGER 
SHIP_CODE CHAR(2) 
SHIP_DATE DATE 
ORD_DESCRIPTION VCHAR(100) 

Use the DB2 Object Selection Criteria screen to generate a Db2 SQL SELECT statement to select rows
to extract from the Db2 object based on column values.

You can scroll the lower portion of this screen up and down if there are more column names on the
list than will fit on the screen. In addition, you can scroll left and right if the values in the Where
field exceed the screen width. See Scrolling on page 31 for more information about scrolling.

Column Name
Displays the names of the columns in the Db2 object.

Type(Length)
Displays the data type of each column in the table. The length of the data is displayed in
parentheses immediately following the data type for CHAR, CH, VCHAR, VC, GRPH, VGRPH,
DEC, FIXPIC, National data types only.

Unicode Db2 character data types are identified as CH(x), VC(x) or LV(x) with a suffix of U16 or
U-8.

See Table 13 for more information about Db2 data types.

1. Distinct type (UDT) columns show either their built-in data types or their UDT names,
depending on the status of the UDTSWAP primary command. To switch the display
status enter the UDTSWAP command.
2. To view a list of all UDTs that are part of the extract issue the UDTTYPE command.
3. When entering a WHERE clause for a UDT column you must enter the appropriate
CAST function manually. Example:

=CAST('A01' AS TSOID01.DEPARTMENT)

4. Column types CLOB, BLOB, DBCLOB, ROWID, BINARY, VARBINARY, or XML are not
eligible for WHERE clauses.
306 File-AID/RDX Reference

Table 13. Data Type Values

Data Type Value
CHAR or CH Fixed-length character strings less than or equal to 254 characters.
VCHAR or Variable-length character strings less than or equal to the field length specified when the column is
VC created. Maximum allowable field length is 4056 characters for 4k pages and 32,714 characters for 32k
pages.
LVCHAR or Variable-length character strings less than or equal to 4056 characters for 4k pages and 32,714 characters
LV for 32k pages.
GRPH Fixed-length graphic strings less than or equal to 127 characters.
VGRPH Variable-length graphic strings less than or equal to the field length specified when the column is created.
Maximum allowable field length is 2028 characters for 4k pages and 16,357 characters for 32k pages.
LVGRPH Variable-length graphic strings less than or equal to 2028 characters for 4k pages and 16,357 characters
for 32k pages.
SMALLINT Fixed-length, binary integers in the range of -32,768 to +32,767, requiring two bytes of storage.
INTEGER Fixed-length, binary integers in the range of -2,146,483,648 to +2,147,483,467, requiring four bytes of
storage.
BIGINT Fixed-length, binary integers in the range of -9223372036854775808 to9223372036854775807,
requiring eight bytes of storage.
DEC Fixed-length, decimal numbers in the range of -10E15 to +10E15.
DECFLOAT Decimal Floating Point can be either DECFLOAT(16) or DECFLOAT(34) representing either 16 or 34
significant digits. The range of a DECFLOAT(16) number is 10-383 to 10+384 and the range of a
DECFLOAT(34) number is 10-6143 to 10+6144. A DECFLOAT(16) field occupies 8 bytes and a
DECFLOAT(34) occupies 16 bytes.
REAL Fixed-length, single-precision, floating-point numbers in the approximate range of 5.4E-79 to 7.2E+75.
DOUBLE Fixed-length, double-precision, floating-point numbers in the approximate range of 5.4E-79 to 7.2E+75.
DATE A three-part value (year, month, day) whose format is determined by Db2.
TIME A three-part value (hour, minute, second) whose format is determined by Db2.
TMSTMP(n) TIMESTAMP: A seven-part value (year, month, day, hour, minute, second, and precision) whose format
is YYYY-MM-DD-HH.MM.SS.TTTTTTTTTTTT. The precision value (TTTTTTTTTTTT) is variable length and
has 0 to 12 digits (up to picosecond) with a default of 6 (microsecond). TMSTMP(n) specifies the scale
(length) with n = 0 through 12. For Db2 Versions prior to Version 10, the length is always 6.
TMESTZ(n) TIMESTAMP WITH TIME ZONE: An eight-part value (year, month, day, hour, minute, second, precision,
time zone) whose format is YYYY-MM-DD-HH.MM.SS.TTTTTTTTTTTT±HH:MM. The precision value
(TTTTTTTTTTTT) is variable length and has 0 to 12 digits (up to picosecond) with a default of 6
(microsecond). The time zone is the difference in hours and minutes between local time and UTC. The
range of the hour offset is -12 to +14, and the minute offset is 00 to 59. The time zone is specified in the
format ±th.tm, with values ranging from -12.59 to +14.00. TMESTZ(n) specifies the scale (length) with
n = 0 through 12. Db2 Version 10 and higher only.
CLOB A character large object (CLOB) is a varying-length string with a maximum length of 2 147 483 647 bytes
(2 gigabytes minus 1 byte).
DBCLOB A double-byte character large object (DBCLOB) is a varying-length string with a maximum length of 1
073 741 823 double-byte characters.
XML A data type for storage of well formed XML documents.
BLOB A binary large object (BLOB) is a varying-length string with a maximum length of 2 147 483 647 bytes
(2 gigabytes minus 1 byte).
BINARY BINARY is a fixed length binary string which extends the support for binary strings beyond BLOBs. Length
attribute must between 1 and 255 inclusive.
VARBINARY VARBINARY is a variable length binary string which extends the support for binary strings beyond BLOBs.
Length attribute must between 1 and 32704.
Extract 307

Table 13. Data Type Values (Continued)

Data Type Value
ROWID Row identifier. A value that uniquely identifies a row. If a table contains a large object it must also have a
ROWID column.

Where
Specify values of up to 255 characters in length to limit the rows extracted from the Db2 object.
You can scroll this field left and right.

For the same column you cannot specify both a value in the Where field and
key file selections. They are mutually exclusive.

The Where column is analogous to the predicate specified in the WHERE clause in an SQL
SELECT statement. The following operators are valid in the Where column:

Operator Description Operator Description

> is greater than > is not greater than
< is less than < is not less than
= is equal to IS NULL has a null value
 = or <> is not equal to LIKE searches for a pattern
>= is greater than or equal to IN in a list of values
<= is less than or equal to BETWEEN within a range of values

AND is implied as the logical operator between columns when multiple columns have WHERE
values specified. Specify OR to override the implied AND. Use NOT to negate BETWEEN, LIKE,
NULL, and IN operators.

Enter the WHERE clause information as you would in an SQL SELECT statement.
308 File-AID/RDX Reference

Use parentheses to indicate the order of operations.

1. When entering a WHERE clause for a UDT column you must enter the appropriate CAST
function manually.
2. Column types CLOB, BLOB, DBCLOB, ROWID, BINARY, VARBINARY, or XML are not eligible
for WHERE clauses.
3. When using OR with two or more columns File-AID/RDX generates the correct SQL but
may not redisplay the selection template (see Figure 160 on page 310). Use the SQL
command to view the SQL and use parentheses to indicate the order of operations.

When Extract from Image Copy is set to Yes the selection conditions are limited to the valid
predicates and labeled-duration-expressions in the WHEN clause of the UNLOAD statement
(refer to “Chapter 2-27. UNLOAD” in the DB2 Universal Database for OS/390 and z/OS: Utility
Guide and Reference, Copyright IBM Corp. 1983, 2001.) Accordingly, some of the functions not
supported are:
• Views
• Casting
• Built-in functions
• Column functions
• User Defined Functions
• Arithmetic Expressions outside of those supported with CURRENT_DATE and
CURRENT_TIMESTAMP
• Exists predicate
• Subselects
• Quantified predicate

Examples:

– To select rows having a numeric column value between 9 and 20, specify:

BETWEEN 9 AND 20

– To select rows having a string, “SMITH,” anywhere in the column, specify:

LIKE '%SMITH%'

If you want to extract a specific row, Compuware recommends the following:

• Use the equals (=) operator and be as specific as possible when entering values in the
Where field.
• Specify values for columns that are part of an index.

Specifying Mixed Strings When Using DBCS

You can use mixed strings to specify values in the Where field on the Selection Criteria screen.

Use the following syntax for CHAR, VCHAR, and LVCHAR string:

= ’ sbcs-string > dbcs-string < sbcs-string ’

where,

= any valid operator (see Where on page 307 for a list of valid operators)
’(apostrophe) delimiter
> Db2 shift out character
< Db2 shift out character
sbcs-string DBCS data
dbcs-string DBCS data

Use the following syntax for GRPH, VGRPH, and LVGRPH strings:
Extract 309

=G' > dbcs-string <'

where,

= any valid operator (see Where on page 307 for a list of valid operators)
G constant
’(apostrophe) delimiter
> Db2 shift out character
< Db2 shift out character
dbcs-string DBCS data

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

CANCEL (CAN)
Enter the CANCEL command to return to the Object Selection Criteria screen without saving any
changes. There are no operands associated with this command.

CAPS
Enter the CAPS command to toggle caps mode on and off.

END
Verifies the SQL syntax and returns you to the Selection Criteria Specification screen. There are
no operands associated with this command.

SQL
Invokes the SQL Edit screen. This screen enables you to edit or specify the selection criteria in its
SQL format. See SQL Edit on page 311 for more information about editing your selection criteria
in its SQL format. There are no operands associated with this command.

UDTSWAP (UDTS)
Swaps the display for distinct type columns from UDT name to the built-in data type and length
and vice versa. There are no operands associated with this command.

UDTTYPE (UDT)
Lists all distinct data types (UDTs) that are part of the extract. The list displays the schema, UDT
name, and the built-in data type and length. There are no operands associated with this
command.

Distinct Data Types for This Extract

The Distinct Data Types for This Extract window shown in Figure 159 is displayed when you enter the
UDTTYPE command on the Selection Criteria screen.
310 File-AID/RDX Reference

Figure 159. Distinct Data Types for This Extract Window


File-AID/RDX ----------- DB2 Object Selection Criteria -----------------------
COMMAND ===> Distinct Data Types for This Extract LL ===> CSR
SET 1 of 1 File-AID/RDX Row 1 to 1 of 1 
Driving Obje COMMAND ===> SCROLL ===> CSR 
Max rows f 
Select eve Schema Type Base Data Type 
Extract ro -------- ------------------ ------------------ of No) 
Display Ex TSOID01 DEPARTMENT CHAR(3) E = Edit) 
Column Nam **************** Bottom of data ***************** More: > 
---------- -+---30----
DEPTNO 
DEPTNAME 
MGRNO 
ADMRDEPT DEPARTMENT 
LOCATION CHAR(16) 
RID CHAR(4) 
TSTAMP TMSTMP(6) 
** End of Columns ** 

This window displays the list of all UDTs (distinct data types) that are included in the tables to be
extracted. Use the END command to close the window.

Schema
Identifies the UDT’s schema ID.

Type
Identifies the name of the distinct type.

Base Data Type

Displays the built-in data type for the UDT.

Undisplayable Criteria Specified

If you specify an existing extract request containing an SQL SELECT statement that cannot be
displayed in this format, the Selection Criteria screen is displayed as shown in Figure 160. Use the
SQL command to view or modify the SQL SELECT statement.

Figure 160. Object Selection Criteria Screen — Undisplayable Criteria Specified

File-AID/RDX ----------- DB2 Object Selection Criteria ----------------------

Command ===> 

Specify selection criteria for table LOCATION.FRSAMP.ORDER_TABLE 


Column Name Type(Length) Where 
-------------------- ------------ ----+---10----+---20----+---30---- 
The existing selection criteria is in error or cannot be displayed in 
this format. To view or edit the criteria, enter the SQL command. To 
use the criteria, specify option above and enter the END command. 


Extract 311

SQL Edit
The SQL Edit screen shown in Figure 161 is an ISPF EDIT session on the SQL source generated by File-
AID/RDX using the values you specified on the Selection Criteria screen. It is displayed when you
enter the SQL command in the COMMAND field on the Selection Criteria screen and press Enter.

Only the WHERE clause of the SQL statement is displayed as it is the only part of the SQL statement
that can be modified for selection criteria.

Use this screen to view or modify SQL source. This can occur when you change the SQL source in the
extract criteria file from outside of File-AID/RDX.

Figure 161. SQL Edit Screen

EDIT - File-AID/RDX Generated SQL --------------------------- COLUMNS 000 000

COMMAND ===> SCROLL ===> CSR
*NOTE*
*NOTE* All Columns will be extracted FROM FRSAMP.PART_TABLE
*NOTE*
****** ***************************** TOP OF DATA ******************************
000001 WHERE PART_NUMBER > 'PP0000' 
000002 OR PART_NUMBER = 'BB4545' 
000003 AND EFFECT_DATE = CURRENT_DATE
****** *************************** BOTTOM OF DATA *****************************

The body of the SQL Edit screen consists of a scrollable data editing area.

Line Commands
ISPF edit line commands are valid on the panel.

Primary Commands
ISPF primary commands are valid on this panel.

MVS File Selection Criteria

When you enter the S line command to specify selection criteria for an MVS object in the Object
Selection Criteria screen as shown in Figure 157 on page 301. File-AID/RDX continues with the
Selection Criteria Menu - TEMPORARY and allows you to specify the selection criteria to be applied to
the selected MVS object. The selection criteria will limit the records to be extracted from the object to
those that meet the criteria.

The Temporary Selection Criteria function allows you to create sets of criteria that File-AID/RDX uses
to select records in a data file for processing.

File-AID/RDX provides selection criteria options and formatted selection criteria. The selection
criteria options allow you to specify:

• Where to begin record selection

• How to continue (selection intervals)
• When to stop
• Processing direction.

The selection criteria options can be combined with formatted selection criteria.

Formatted selection criteria allow you to select records based on data within a field as specified by a
record layout.

Temporary selection criteria are valid only for the duration of the extract function. Temporary
selection criteria are not stored for future use unless you explicitly save the Extract Request file (see
312 File-AID/RDX Reference

Output Key File Definition on page 332). When you finish creating the temporary selection criteria,
they are applied and you continue with the Extract utility.

The next section in this chapter discusses the screen presentation order and navigation commands
available for Selection Criteria.

Selection Criteria Menu

The Selection Criteria Menu, shown in Figure 162, provides access to the selection criteria options
and formatted selection criteria specification.

Figure 162. Selection Criteria Menu

File-AID/RDX - Selection Criteria Menu - TEMPORARY ----------------------------

Option ===>
- Status -
1 OPTIONS - Enter selection criteria options default
2 FORMATTED - Edit formatted selection criteria 0 sets 






Use VIEW to display selection criteria summary
Use END to save selection criteria & return to Object Selection Criteria
Use CANCEL to cancel changes & return to Object Selection Criteria

The Selection Criteria screen contains the following fields

Option
Enter one of the following valid options:

Selection criteria options allow you to specify a particular starting point in the file and set
limits on the number of records processed. See Selection Criteria Options on page 314.

Create and edit formatted selection criteria, which allows you to select records based on data
within a field specified by a record layout. See Formatted Selection Criteria Screen on page
317.

Status
Specifies the status of the temporary selection criteria:

OPTIONS
Reports whether the default options have been modified. Valid values are DEFAULT or NOT
DEFAULT.

FORMATTED
Specifies the number of sets of criteria that are specified. A set of selection criteria is defined
as a single expression that can lead to the selection of a record. A set may test for one
Extract 313

condition or several conditions. The conditions can be ANDed together and several
conditions separated by commas create nested OR conditions within a set.

Primary Commands
The following primary commands are valid on the Selection Criteria Menu:

CANCEL
Returns to the Object Selection Criteria and clears all selection fields.

END
Saves the current selection criteria display and exits the Selection Criteria Menu without clearing
the selection fields.

VIEW
Displays the View Criteria screen, which summarizes the options and formatted selection criteria
sets into a scrollable display. See View Criteria on page 313.

View Criteria
The View Criteria screen, shown in Figure 163, summarizes the current selection criteria. It displays
selection criteria option settings and formatted selection criteria sets on a scrollable display. Use the
VIEW primary command on any selection criteria screen to display this screen. Use the END
command (PF3) to return to the previous screen.

Figure 163. View Criteria Screen

File-AID/RDX -------------------- View Criteria ----------- Row 1 to 20 of 35

Command ===> SCROLL ===> CSR
Use END to exit View Display 

******************************* TOP OF CRITERIA *****************************
DEFINE BLOCKS=SELECTION, 

DESCRIPTION1="Selection Criteria for Data Driven AR",

LAYOUT_DSNAME=, 
LAYOUT_MBRNAME=, 

INITIAL_SKIP=0, 
THEN_SELECT=1, 
THEN_SKIP=0, 

MAXIMUM_TO_SEARCH=ALL, 
MAXIMUM_TO_SELECT=ALL 

SELECT SET=1,LAYOUT=CUSTOMER_TABLE-TBL 
IF 
FIELD_NAME=CUSTOMER_NUMBER, 
POSITION=17,LENGTH=6,OPERATOR=LT, 
TYPE=T,VALUE=777777

Selection Criteria Options

The Selection Criteria Options screen, shown in Figure 164 on page 314, enables you to control
record selection based on starting record key, RBA, or RRN or record counts which determine how
selection processing is executed and when it stops. File-AID/RDX determines whether an individual
314 File-AID/RDX Reference

parameter is valid based on the access method of the processed file. For instance, File-AID/RDX allows
you to specify the processing direction when selecting records from a sequential or VSAM file.

Enter option 1 on the Selection Criteria Menu to display the Selection Criteria Options screen.
Selection criteria options can be combined with formatted selection criteria. If any formatted
selection criteria exist, they are applied after a record passes the selection criteria options selection
process.

Figure 164. Selection Criteria Options

File-AID/RDX ---------- Selection Criteria Options --------------------------

Command ===> 

Specify Selection Criteria Options:
Start at the following record key
(both blank for start of dataset)
Starting record key ===>
- OR - OR at the following RBA or RRN
Starting RBA or RRN ===> 

Initial records to skip ===> 0 then skip this many records 

Subsequent Selection Interval: then repeat the following
Records to select ===> 1 - select this many records
Records to skip ===> 0 - then skip this many records
until
Number of records to search ===> ALL you have read this many records 


SEQ/VSAM processing direction ===> F (F = Forward; B = Backward) 


Use ENTER to return to selection criteria menu

Specify Selection Criteria Options:

The Starting record key field and Starting RBA or RNN field are exclusive of each other.

Starting record key

Specify a generic or specific record key in a character or hexadecimal data format. This field
allows you to specify a random starting point for record selection in a VSAM KSDS file. Records
before the starting record key are not selected, regardless of matching formatted selection criteria.

To specify a hexadecimal record key, enter the value enclosed in single quotation marks ( ’ ) and
precede the quoted value with the letter X. For example, X’03E2’.

Starting RBA or RRN

Specify a generic or specific relative byte address (RBA) or relative record number (RRN).

This field allows you to specify a random starting point for record selection in a VSAM or BDAM
file. Records before the specified starting RBA or RRN are not selected, regardless of matching
formatted selection criteria.

For VSAM KSDS and VSAM ESDS files, enter a specific relative byte address. RBAs must be on a
record boundary. To specify a hexadecimal RBA, enter the value enclosed in single quotation
marks (’) and precede the quoted value with the letter X.

For VSAM RRDS or BDAM files, a relative record number (RRN) can be specified.
Extract 315

Initial records to skip

Specify a number of records for File-AID/RDX to skip before processing the file. Possible values
are any number from 0 (zero) through 999999. Use the 0 (zero) value to process all records.

Subsequent Selection Interval:

The values in the Records to select and Records to skip fields determine the record selection pattern
that File-AID/RDX uses to select records from a file until the value in the Number of records to search
or the Number of records to select field is reached.

Records to select
Specify the number of records for File-AID/RDX to retrieve from the file at a time. Possible values
are any number from 1 (one) through 999999. Selection criteria is applied after the record has
been retrieved. The default is 1 (one).

Records to skip
Specify the number of records for File-AID/RDX to skip after fulfilling the Records to select
parameter when processing the file. Possible values are any number from 0 (zero) through
999999. Use the 0 (zero) value for File-AID/RDX to process all remaining records. All skipped
records are not selected, regardless of the selection criteria specified.

Number of records to search

Specify a limit for the number of records File-AID/RDX reads and checks for matches to selection
criteria. The default for this parameter is ALL. Possible values are any number from 0 (zero)
through 999999. Use the 0 (zero) or ALL value to search the entire file.

This parameter can prevent excessive I/O processing when searching large files. If the file is
processed randomly (a KEY or RBA have been entered), this count begins with the first record
retrieved randomly.

SEQ/VSAM processing direction

Specify a processing direction for File-AID/RDX to read Sequential or VSAM files. Possible values
are F (forward) and B (backward). The default is F (forward).

This field specifies whether File-AID/RDX starts reading a Sequential or VSAM file at the
beginning or the end. File-AID/RDX ignores the B value in this field when used with files of other
access methods.

Figure 165 shows an example of the effect of selection criteria options.

316 File-AID/RDX Reference

Figure 165. Selection Criteria Options Example


Initial records to skip ===> 4 then skip this many records 

Subsequent Selection Interval: then repeat the following
Records to select ===> 2 - select this many records
Records to skip ===> 3 - then skip this many records
until
Number of records to search ===> 10 you have read this many records


Selected/Not Selected Records in the file
NS Record 1
NS 2
NS 3
NS 4
S Select 2 5 <=== Starting Record Number
S 6
NS Skip 3 7
NS 8
NS 9
S Select 2 10
S 11
NS Skip 3 12
NS 13
NS 14
S Select 2 15
S 16
NS Skip 3 17
NS 18
NS 19
S Select 2 20
S 21
NS Skip 3 22
NS 23
NS 24
S Select 2 25
S 26 <=== 10th Record Searched
NS 27
NS 28
NS 29
NS Not Searched 30
NS Because Limit 31
NS Has Been Reached 32
NS 33
NS 34
NS 35

When the values shown in Figure 166 are entered in the selection criteria options fields, all records in
the file pass this portion of the selection process and are processed by any specified formatted
selection criteria.

Figure 166. Selection Criteria Options Example. Default - Examines All Records

Initial records to skip ===> 0 then skip this many records 

Subsequent Selection Interval then repeat the following
Records to select ===> 1 - select this many records
Records to skip ===> 0 - then skip this many records
until
Number of records to search ===> ALL you have read this many records

Formatted Selection Criteria

The Formatted Selection Criteria screen, shown in Figure 167, allows you to specify selection of
records based on field values displayed with a record layout.
Extract 317

Select option 2 on the Selection Criteria Menu to display the Formatted Selection Criteria screen. If
you did not specify a record layout or XREF file prior to selecting option 2, File-AID/RDX displays the
Record Layout Specification screen, shown in Figure 170 on page 328, for entry of the required
information.

Figure 167. Formatted Selection Criteria Screen

File-AID/RDX --- Formatted Selection Criteria ---------------------------------

Command ===> SCROLL ===> CSR
CRITERIA NUMBER: 1 OF 1 EMPLOYEE-MASTER-FILE GBL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----+----1----+----2----+----3----+-
******************************* TOP OF DATA ********************************
5 EMP-NUMBER 5/AN
5 EMP-LAST-NAME 15/AN
5 EMP-FIRST-NAME 10/AN
5 EMP-MID-INIT 1/AN
5 FILLER 2/AN
5 EMP-TITLE 30/AN
5 EMP-PERSONAL-INFO SYNC 23/GRP
10 EMP-NATL-ID-NUMBER 9/NUM
10 FILLER 1/AN
10 EMP-DATE-OF-BIRTH 6/AN
10 EMP-DOB-REDEF REDEFINES EMP-DATE-OF-BIRTH
10 EMP-DOB-REDEF SYNC 6/GRP
15 EMP-DOB-MM 2/NUM
15 EMP-DOB-DD 2/NUM
15 EMP-DOB-YY 2/NUM
10 EMP-HIRE-DATE 6/AN
10 EMP-MARITAL-STATUS 1/AN
5 EMP-WITHOLD-INFO SYNC 15/GRP
10 EMP-LIFE-INS-WITHOLD-AMT 6/SNUM

The input fields in this screen are:

RO
Specify a relational operator. Possible values are:

EQ, = Equal to
NE, ¬ =, != Not equal to
GT, > Greater than
GE, > = Greater than or equal to
LT, < Less than
LE, < = Less than or equal to
CO Contains; scans the specified field for the presence of a data value. CO works on an
equal condition.
NC Not contains; scans the specified field for the absence of a data value. NC works on
a not equal condition.
BT Between; within a range of two values (endpoints inclusive). The value is greater than
or equal to the first endpoint and less than or equal to the last endpoint.
NB Not between; outside a range of two values (endpoints exclusive). The value is less
than the first endpoint or greater than the last endpoint.
VA Valid numeric or packed data based on the field format.
NO Bits are not ones (Mask data value only).
MX Bits are mixed, ones and zeros (Mask data value only).
NV Not valid numeric or packed data based on the field format.
FM Field mask. See Field Mask on page 326 for more information.
318 File-AID/RDX Reference

1. The CO and NC relational operators can be specified only for

alphanumeric fields (PIC X for COBOL; CHAR or PIC X for PL/I).
2. File-AID/RDX does not currently support selection criteria that use bit
or numeric fields that specify a leading and/or separate sign.

data value
For fields with relational operators other than BT and NB, you specify the field value to use in the
comparison. For relational operators BT and NB, specify your Data Value as two values separated
by a colon (:). The values may be hex strings, character strings, or numeric tests.

To compare an alphanumeric field to blanks (hexadecimal 40s), leave the data value column
blank.

Guidelines
To specify a formatted selection criterion, enter the relational operator and data value beside a field
on which you want to base the record selection. Leave the relational operator blank for fields not
involved in the selection criteria. Use the INPUT, INSERT, or REPEAT primary command to specify
multiple sets of formatted selection criteria. Add the keyword AND to those primary commands to
add an ANDed subset to the current criteria set.

In theory, you can create any number of sets of selection criteria. However, the actual number is
limited by available storage. Storage is primarily affected by the number of relational operators used
and the size of the fields being referenced. The number of ANDed subsets is limited to 255 for any
one set.

Multiple fields for a single criterion test are logically ANDed together, multiple AND subsets are
ANDed together, and multiple sets of criteria tests are logically ORed together.

Each ANDed Subset is processed as a part of the preceding Set as a group of conditions. An OR Set
represents a new group of conditions. Consider the following Sets:

SET 1
OR SET 2.1 (Subset 1 of Set 2)
AND SET 2.2 (Subset 2 of Set 2)
OR SET 3

This criteria will be processed as (SET 1) OR (SET 2.1 AND SET 2.2) OR SET 3.

Multiple data entries can be specified for one field by separating each entry with a comma. The
comma is interpreted as an OR expression. You can specify multiple data values for one field on one
selection screen. For example: RECORD-CODE EQ A,B,C is interpreted as the RECORD-CODE field
must be equal to A or B or C.

The syntax of the search data is important since File-AID/RDX interprets a comma as an OR
expression. In order to search for a comma as data, enclose the comma in double quotes (",").

For relational operators BT and NB, enter two values separated by a colon (for example, BT -
100:+100). In most cases, you will have sufficient space to enter the two values.

You can select records with an invalid field value by entering the NV relational operator. Records with
a valid field value can be selected by entering the VA relational operator. The VA and NV operators
can be used for packed decimal, and zoned decimal fields.

Relational operators CO and NC can be used to scan a field within each record for the presence or
absence of a particular value. The value for which you want to search is entered in the data value
column. Trailing blanks in the data value are ignored and not included in the search string. The CAPS
Extract 319

primary command controls whether File-AID/RDX does a case-sensitive search. When you enter CAPS
OFF, only text exactly matching the upper and lowercase characters is found (for example, SMITH
and Smith are different values). When you enter CAPS ON, File-AID/RDX treats upper, lower, and
mixed-case characters the same and matches any case combination of the specified characters.

Japanese DBCS Data

DBCS data is accepted as selection criteria data values for alphanumeric fields. For the relational
operators CO (contains) and NC (not contains), File-AID/RDX removes any leading or trailing shift
characters unless the value is enclosed in double quotes.

Sample Selection Sets

Figure 168. Formatted Selection Criteria Examples

File-AID/RDX --- Formatted Selection Criteria ---------------------------------

Command ===> SCROLL ===> CSR
CRITERIA NUMBER: 1 OF 2 EXAMPLE-FILE LAYOUT LENGTH: 3
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----+----1----+----2----+----3----+-
******************************* TOP OF DATA ********************************
5 FIELD-ONE 1/AN = A,B,C
5 FIELD-TWO 1/AN = D
5 FIELD-THREE 1/AN
***************************** BOTTOM OF DATA *******************************

File-AID/RDX --- Formatted Selection Criteria ---------------------------------

Command ===> SCROLL ===> CSR
CRITERIA NUMBER: 2 OF 2 EXAMPLE-FILE LAYOUT LENGTH: 3
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----+----1----+----2----+----3----+-
******************************* TOP OF DATA ********************************
5 FIELD-ONE 1/AN
5 FIELD-TWO 1/AN
5 FIELD-THREE 1/AN = E
***************************** BOTTOM OF DATA *******************************

The formatted conditions specified in Figure 168 translate into the following expression:

If ((A or B or C) and D) or E

which can also be stated as:

If (A and D) or (B and D) or (C and D) or E

Primary Commands
The following is a list of the primary commands that are valid on the Formatted Selection Criteria
screen.

ALIGN (AL)
Controls display of ALIGNED/UNALIGNED term for PL/I data.

ARRAY (AR)
Controls display of array declaration information for PL/I data.

ON

Displays an array definition line for each subscripted item in a record layout.
320 File-AID/RDX Reference

OFF

Does not display an array definition line.

ALL

Displays all occurrences separately with the subscript(s) and any criteria entered on a specific
occurrence will only be applied to that occurrence. This additional parameter is only valid
during Formatted Selection Criteria creation.

ANY

Displays a single entry for the occurrences and any criteria entered for the ANY occurrence
will be applied to all occurrences. The record will meet the Selection Criteria if any of the
occurrences meet the specified criteria. This additional parameter is only valid during
Formatted Selection Criteria creation. ANY is applied for initial display of Selection Criteria.

When applying 2 or more criteria in the same subset, all have to be true in
the same occurrence to be selected. 
When entered individually in different subsets, they don’t have to be true
in the same occurrence to be selected.

EVERY

Displays a single entry for the occurrences and any criteria entered for the EVERY occurrence
will be applied to all occurrences. The record will meet the Selection Criteria if all of the
occurrences meet the specified criteria. This additional parameter is only valid during
Formatted Selection Criteria creation.

Guidelines
• Use the PROFILE command to display the current ARRAY ON or OFF value. Only ON or
OFF are saved in the profile.

• The array line contains the name of the array followed by the word ARRAY and the
subscript bounds in standard PL/I format. If any of the subscripts are defined by a REFER
clause, additional lines that follow the ARRAY line describe each REFER variable.

• ANY, EVERY and ALL are available only in Formatted Selection Criteria.

• ANY, EVERY or ALL is applied per set or subset if any. Each set or subset may have a
different array setting.

• You cannot switch ANY, EVERY or ALL to another if the criteria is specified on any
occurrence field in a single set or single subset.

• In ANY or EVERY mode, the SHOW OFFSET command shows the offsets of the first
occurrence.

BACK
Positions the display to the previous criteria. Synonym for LEFT.

CANCEL (CAN)
Returns to main panel without saving current updates.
Extract 321

CAPS
Sets caps mode. CAPS ON is not case-sensitive in the search to match the selection criteria.
Specify CAPS OFF for a case-sensitive search. This command is valid only on a new criteria
display.

COMPLEX (CMPLX)
Controls display of COMPLEX terms for PL/I data.

DELETE (DEL, D)
Delete a selection set or subset.

DISPLAY (DIS)
Specifies a display format.

MAXREFER

(for PL/I layouts only) Specify the maximum number of occurences to display. Omission of
the DISPLAY MAXREFER command causes PL/I Refers to default to 1 occurrence.

DOWN
Scrolls down.

END (E)
Terminates display of the Formatted Selection Criteria screen and returns to the Selection Criteria
Menu.

FILLER (FILL)
Controls display of FILLER fields.

FORWARD (FWD)
Positions the display to the next criteria. Synonym for RIGHT.

GROUP
Controls the display of occurrences of group-level items.

INPUT/ INSERT (I)

Inputs/inserts a new formatted selection criteria set.

AND

Inserts an ANDed subset of selection criteria (the set counter displays “AND Set 1.2 of 1”)
after (default) or before the current criteria.
322 File-AID/RDX Reference

LEFT (L)
Positions the display to the previous criteria. Synonym for BACK.

LOCATE (LOC)
Scrolls directly to the specified record layout line.

LR (Locate Record)
Positions the display to the specified criteria number.

OCCURS (OCC)
Controls the display of array declaration items.

ON

Displays an array definition line for each subscripted item in a record layout.

OFF

Does not display an array definition line.

ALL

Displays all occurrences separately with the subscript(s) and any criteria entered on a specific
occurrence will only be applied to that occurrence. This additional parameter is only valid
during Formatted Selection Criteria creation.

ANY

Displays a single entry for the occurrences and any criteria entered for the ANY occurrence
will be applied to all occurrences. The record will meet the Selection Criteria if any of the
occurrences meet the specified criteria. This additional parameter is only valid during
Formatted Selection Criteria creation. ANY is applied for initial display of Selection Criteria.

When applying 2 or more criteria in the same subset, all have to be true in
the same occurrence to be selected. 
When entered individually in different subsets, they don’t have to be true
in the same occurrence to be selected.

EVERY

Displays a single entry for the occurrences and any criteria entered for the EVERY occurrence
will be applied to all occurrences. The record will meet the Selection Criteria if all of the
occurrences meet the specified criteria. This additional parameter is only valid during
Formatted Selection Criteria creation.

Guidelines
• Use the PROFILE command to display the current OCCURS ON or OFF value. Only ON or
OFF are saved in the profile.

• The OCCURS line contains the name of the array followed by the word OCCURS and the
subscript bounds in standard COBOL format. If any of the subscripts are defined by a
REFER clause, additional lines that follow the ARRAY line describe each REFER variable.

• ANY, EVERY and ALL are available only in Formatted Selection Criteria.
Extract 323

• ANY, EVERY or ALL is applied per set or subset if any. Each set or subset may have a
different array setting.

• You cannot switch ANY, EVERY or ALL to another if the criteria is specified on any
occurrence field in a single set or single subset.

• In ANY or EVERY mode, the SHOW OFFSET command shows the offsets of the first
occurrence.

OFFSET
Displays field offsets.

OPT (O, 1)
Displays the Selection Criteria Options screen.

PROFILE (PROF)
Displays profile information lines.

REFLNG
Controls the display of BIT/CHAR REFER field length reference lines for PL/I data.

REPEAT (R)
Causes a formatted selection criteria set, including any subsets, to be repeated (SET 3 of 3
increments to SET 4 of 4; AND SET 3.2 of 3 increases to AND SET 4.2 of 4).

AND

Repeats an ANDed subset of selection criteria. (the set counter displays “AND Set 1.2 of 1”)
after the current criteria.

RETURN
Returns to the Primary Option Menu.

RIGHT
Positions the display to the next criteria. Synonym for FORWARD.

SHOW (SH)
Displays LEVEL, NUMBER, FORMAT, OFFSET, or PICTURE information for the selection fields.

SYNC
Controls the display of the SYNC term for fields in a COBOL record layout.
324 File-AID/RDX Reference

UP
Scrolls up.

USE
Specifies another record layout for the current formatted selection criteria.

VIEW (V)
Displays the View Criteria screen which is a keyword summary of the current settings for options,
formatted, and unformatted selection criteria. See Figure 163 on page 313.

ZERO (Z)
Controls the display of leading zeros in the numeric

Selection Criteria Considerations When Data Fields May Be Nonexistent

When defining selection criteria with reference to fields where data might not exist in some records,
File-AID/RDX does not exclude those records from the selection test.

A positive selection operator, such as EQ (equal to), indicates to select the record for processing if the
condition is true.

A negative selection operator, such as NE (not equal to), indicates to select the record for processing if
the condition is false.

Therefore, when using a negative selection operator, File-AID/RDX can select records that don’t have
data in those fields.

A typical case of this is seen with fields that are specified in a record layout with OCCURS
DEPENDING ON. Some records may have several occurrences of the field, while other records may
have only one or none.

For example, consider a record layout called CUSTOMER, having a field called BALANCE defined with
up to 12 occurrences, one per month, depending on another field, called DURATION-OF-ACCOUNT.
The 12th occurrence will not exist for customers who have had accounts with the company for less
than a year.

Example:
Assume you have the following 3 records in your file:

Alice Alvarez has been a customer for 5 months and had monthly balances of 1000, 2000, 3000, 500,
and 0.

Bruce Bandler has been a customer for 3 months and had monthly balances of 1000, 2000, and 3000.

Carlos Cramer has been a customer for 5 months and had monthly balances of 1000, 2000, 3000, 0,
and 0.

The records look like this:

Alice Alvarez,05,1000,2000,3000,500,0
Bruce Bandler,03,1000,2000,3000
Carlos Cramer,05,1000,2000,3000,0,0

You specify: Select all records with BALANCE(4) NOT EQUAL TO 500
Extract 325

This is interpreted to mean: Select all records NOT having BALANCE(4) = 500

Records with nonexistent data in occurrence 4 will be included in the selection, and you get these
records:

Bruce Bandler,03,1000,2000,3000
Carlos Cramer,05,1000,2000,3000,0,0

Since Bruce Bandler does not have a balance for month 4, he does not have a balance that equals 500,
and his record is selected as being not equal to 500.

If you want to ensure that only one record is selected, include the DURATION-OF-ACCOUNT variable
in the selection criteria:

Specify: Select all records with DURATION-OF-ACCOUNT >= 5 AND BALANCE(4) NOT EQUAL TO
500

This would ensure that records with nonexistent data for the fourth occurrence would not be
considered for selection. You would get only one record:

Carlos Cramer,05,1000,2000,3000,0,0

Selection Criteria Considerations: Using GT, LT, and BT with Arrays

For a data item that is not part of an array, specifying BETWEEN (BT) has the effect of selecting all
records where that data item is both Greater Than or Equal to the specified lower bound, AND
simultaneously Less Than or Equal to the specified upper bound. If you specify instead a pair of
conditions, Greater Than (GT) a lower bound, AND Less Than (LT) an upper bound, a data item must
meet both criteria in order to be selected. So for individual data items the effect is similar.

When Selecting data from arrays, the BETWEEN operator behaves the same way as it does for
individual data items. Use the BETWEEN (BT) operator when you want to select only records
containing data items that are simultaneously Greater Than or Equal to a specified lower bound and
Less Than or Equal to a specified upper bound.

However, when selecting data in arrays, do not try to select a set BETWEEN specified bounds by
specifying a combination of GT and LT.

When you specify GT and LT together for an array, you are really selecting two subsets: All records
having data items Less Than (LT) your upper bound AND all records having data items Greater Than
(GT) your lower bound. Generally this will include many more records than the set between the two
bounds.

Examples
Assume you have the following data records, containing an array with 5 occurrences of a 2-byte
numeric field:

Record 1: 05,05,05,05,05
Record 2: 02,04,06,08,10 
Record 3: 11,12,13,14,15

If you specify ANY with values BETWEEN 04 and 06, Records 1 and 2 will be selected.

If you specify ANY with values Greater Than 03 AND Less Than 07, all 3 records will be selected. The
first 2 records have data items with values Less Than 07, and all 3 records have data items with values
Greater Than 03.
326 File-AID/RDX Reference

Field Mask
The Field Mask Criteria screen, shown in Figure 169 on page 326, is displayed when you enter the
Field Mask (FM) relational operator in the relational operator (RO) column on any of the File-
AID/RDX Selection Criteria screens.

Figure 169. Field Mask Criteria

File-AID/RDX --- Formatted Selection Criteria ------------------------------------

C Field Mask Criteria 
S 
- Command ===> 
* 
1 Field Name : ORD-TYPE 
Data Type : CHARACTER 
Field Length: 00008 
Mask Length : 008 

A field mask allows selected positions of a field to be processed. 
It always operates on the character representation of the field. 

Identify field positions to process: (Y = include; N = exclude) 
Field Mask: ----+--- 





END to continue 
* 



To ensure accurate Field Mask processing, the Field Mask (FM) relational
operator must be entered prior to entering any other relational operators.

Field Descriptions

Field Name
Name of the selected field as defined by the record layout.

Data Type
Data type of selected field as defined by the record layout.

Field Length
Length of data in selected field as defined by the record layout. This field cannot be overtyped,
when you are on the Field Mask Criteria screen.
Extract 327

Mask Length
Length of the mask. This field may be overtyped to shorten or lengthen the length of the data to
be masked. This is particularly useful when you want to mask all the elements of a group item.

You cannot override Mask Length for binary or packed/comp-3 fields.

Identify field positions to process: (Y = include; N = exclude)

Field Mask
A Field Mask enables processing of selected positions or part of a field. It always operates on
character representation of the field. Specify Y or N to include or exclude field positions to be
processed for masking.

Field Mask can be applied to both numeric and character fields.

Each mask position corresponds to a digit in the decimal value of the original field, when
masking numeric fields. The selected digits are passed as a single unsigned numeric display field
for the specified product function.

Signs (+,-) are excluded when masking numeric fields.

When masking character fields, each mask position corresponds to the identical position in the
original field. The selected positions are passed as a single contiguous character field.

The original format will be replaced by MASK on the Formatted Criteria and Selection criteria
screens, when Field Mask is in effect.

Field masking is not currently supported for bit, floating point, DBCS, or
numeric fields that specify a leading and/or separate sign.

Primary Commands
The following primary commands are valid:

END
Saves the entered field mask parameters.

CANCEL
Discards the entries.
328 File-AID/RDX Reference

Selection Criteria Record Layout Specification

File-AID/RDX displays the Record Layout Specification screen, shown in Figure 170 on page 328,
when a record layout or XREF file was not specified prior to selecting option 2, formatted selection
criteria. Specify record layout or XREF information and press Enter to continue. Use the END primary
command (PF3) to return to the Selection Criteria Menu.

Figure 170. Record Layout Specification Screen

File-AID/RDX ---------- Record Layout Specification --------------------------

Command ===> 

Specify Record Layout and XREF Information:
Record layout usage ===> S (S = Single; X = XREF) 

Record layout dataset ===> FASAMP.LAYOUTS
Member name ===> (Blank or pattern for member list) 

XREF dataset name ===> FASAMP.XREF
Member name ===> (Blank or pattern for member list)

Selection Criteria for XREFs and Multiple Record Type Files

Specify an X in the Record layout usage field and XREF file information on the Selection Criteria - File
Specification screen to create new or edit existing formatted selection criteria for multiple record type
files. XREFs are used to specify selection criteria for multiple record type files and segmented records.
The record layout XREFs allow you to identify the record type(s) for which you want to specify
formatted record selection criteria.

The Display XREF screen, shown in Figure 171, lists each layout defined in the specified XREF. It is
displayed when the data file you are selecting from contains more than one type of record and each
record type requires a different record layout (Record layout usage = X).

Each data file record is classified into a record type category based on certain field values within the
record. In File-AID/RDX, these field values and their record layouts are associated when the XREF is
defined.

Figure 171. Display XREF Screen

File-AID/RDX --- Display XREF - SEGFILE --------------------- ROW 1 TO 6 OF 6

COMMAND ===> SCROLL ===> CSR
XR113- Selection by Record ID: Enter S or SF for formatted
Member list description ===> SEGFILE XREF__________________ 

Long ===> FILE CONTAINS INS-BASE FOLLOWED BY ANY NUMBER OF ADDITIONAL___
Description ===> TRAILER SEGMENTS IN ANY ORDER - BOAT CAR BUSINESS ETC.________

Cmd Member Beginning Data-Name Description Status
--- ---------- ------------------------------ ---------------- ----------------
__ SEGRECS INS-BASE-FILE BASE
__ SEGRECS CLI-BOAT-DATA SEGMENT
__ SEGRECS CLI-BUSINESS-DATA SEGMENT
__ SEGRECS CLI-CAR-DATA SEGMENT
__ SEGRECS CLI-HOME-DATA SEGMENT
__ SEGRECS CLI-LIFE-DATA SEGMENT
************************** END OF SELECTION CRITERIA **************************

Cmd
Use the S (Select) or SF (Select Formatted) line command to specify the record layout you want to
use.
Extract 329

If you select a SEGMENT, the BASE associated with that segment is also implicitly selected. The
fields associated with layout selection are automatically set and locked and flagged with a criteria
value of RECORD TYPE FIELD.

With segmented records, File-AID/RDX selects only the records where the
requested segment immediately follows the base segment.

Member
Name of the record layout member.

Beginning Data-Name
Displays the starting dataname of the record layout.

Description
Short Description of the record layout entered by user when the XREF is created.

Status
Usage status of the layout (BASE, DEFAULT, or SEGMENT) as defined in the XREF.

After you select a layout on the Display XREF screen, press Enter to display the Formatted Selection
Criteria screen (S or SF).

Use the END command (PF3) to terminate the function and return to the Selection Criteria Menu.

Use the CANCEL command to terminate the function and return to the Selection Criteria - File
Specification screen. Use the RETURN command (PF4) to return to the File-AID/RDX Primary Option
Menu without specifying any criteria.

Primary Commands
The following primary commands are valid on the Display XREF screen:

CANCEL
Terminates the selection criteria specification.

DOWN
Scrolls toward the end of a record layout.

END
Terminates the selection criteria specification.

RETURN
Returns to the File-AID/RDX Primary Option Menu.
330 File-AID/RDX Reference

UP
Scrolls toward the top of a record layout.

On the Formatted Selection screen the record layout fields that contain the record type are protected
and the intensified message, RECORD TYPE FIELD, is displayed in the data column, as shown in
Figure 172. The record type field is treated as if you had entered the appropriate relational operator
and the corresponding record type value(s).

Figure 172. Formatted Selection Criteria Screen. For Multiple Record Type Files.

File-AID/RDX --- Formatted Selection Criteria ---------------------------

COMMAND ===> SCROLL ===>
CRITERIA NUMBER: 1 OF 1 ORDER-LINE-DATA-PO LAYOUT LENGTH:
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----+----1----+----2----+----3-
******************************* TOP OF DATA *****************************
5 RECORD-LENGTH 2/BI 0
5 ORDER-NO 6/AN
5 ORDER-LINE-KEY SYNC 2/GRP
7 LINE-NUMBER 2/AN
5 ORDER-TYPE 2/AN ** RECORD TYPE FIELD **
5 LINE-STATUS 7/AN
5 PART-NO 6/AN
5 DESCRIPTION 30/AN

Once you select a record type for formatted selection criteria, the records matching this record type
are selected even if you do not enter any other field criteria. On the Formatted Selection Criteria
screen, use the DELETE primary command to unselect a record type. Use the VIEW command to
check which XREF record types are active.

Output Key Files

When you select Option 6 - Output Key Files from the Extract Menu and your extract request includes
only one dependent KEY relationships, the Output Key File Definition panel Figure 174 displays.

When you select Option 6 - Output Key Files from the Extract Menu and your extract request includes
more than one dependent KEY relationships, the Output Key Files screen (Figure 173) displays.

Output Key File Layout

If the relationship was defined using a DBD, the DBD name will be included. If the relationship was
defined only using a layout, the layout name will appear. The extracted key value begins in column
10.
Table 14. Output Key File Layout
Field Starting Column Ending Column Description
IMS Segment  Name of the IMS segment, if the relationship was
or defined using a DBD, or the name of the layout
1 8
Layout Name member used to define the relationship. Left
justified.
Filler 9 9 Filler
Key Value 10 n The extracted key value.

Output Key Files List

The Output Key Files screen (Figure 173) displays when you select Option 6 - Output Key Files from
the Extract Menu and your extract request includes more than one dependent KEY relationships.

For each KEY relationship, it lists the related IMS database(s) and record or segment layouts for the
extract as specified during the relationship definition (see Specify Method to Define Output Key File
Extract 331

Relationship Area on page 131). You must define an Output Key File for each KEY relationship with a
status of KEY Undefined before the extract process can continue. File-AID/RDX will store the
extracted keys in the specified file for later extract with File-AID for IMS or as an Input Key File for
another File-AID/RDX extract. You can also specify that the File-AID for IMS extract using the output
key files is to be executed as a step following the File-AID/RDX extract.

Figure 173. Output Key Files

File-AID/RDX ------------- Output Key Files ----------------- Row 1 to 3 of 3

Command ===> Scroll ===> PAGE

Line commands: S = Define or update output key file I = Information 


IMS DBD Layout Output Key File Name Status 
-------- -------- ----------------------------------------- ----------------
_ PORDR ORDR010 KEY Undefined 
_ PCUST 'TSOID01.PCUST.KEYS' KEY Defined 
_ ORDERTAB 'TSOID01.PORDR.KEYS' KEY Defined 
******************************* Bottom of data ********************************

On this screen select an IMS DBD or segment layout to specify the Output Key File to which File-
AID/RDX will copy the key values for the selected KEY relation.

Press END to return to the Extract Menu.

The body of the Output Key Files panel consists of the following fields:

Cmd
Use the S (Select) or I (Information) line command to specify or view the KEY relationship
information.

IMS DBD
Member name of the DBD library (KEY method 2 and 3).

Layout
Member name of the record or segment layout (KEY method 1 and 3).

Output Key File Name

Lists the name of the file to which the extracted key values will be saved.

Status
Displays one of the following messages:

Message Explanation
KEY Undefined For this KEY relationship you still need to define a key file with the S line
command, or exclude the relation from the current extract process, before you
can continue.
KEY Defined A key file has been defined for this KEY relationship.
KEY Deleted The key file definition for this KEY relationship has been deleted.
332 File-AID/RDX Reference

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

I (Relationship Information)
Invokes the Relationship Information pop-up window. See Relationship Information Window on
page 284 for information about the Relationship Information window.

S (Select)
Use the S line command for all listed KEY relationships with a status of Undefined. It brings up
the Output Key File Definition window as shown in Figure 174, so you can define an output key
file. After File-AID/RDX has completed the extract the output key file then includes all of the
output keys for this Output Key file relationship. This file can then be used by File-AID for IMS to
extract IMS data. It can also by used by File-AID/RDX as an Input Key file for another extract.

Output Key File Definition

The Output Key File Definition panel Figure 174 displays when you enter the S line command for an
Output Key File on the Output Key Files screen or when you select Option 6 - Output Key Files from
the Extract Menu and your extract request only includes one KEY relationship. You must define an
Output Key File for all included relationships with a status of Undefined before the extract process
can continue. File-AID/RDX will store the extracted keys in the specified Output Key File.

File-AID/RDX also allows a File-AID for IMS extract to be executed as a step following the File-
AID/RDX extract.

The JCL for the extract job must have been created within File-AID for IMS and saved to a dataset. The
File-AID for IMS extract must have been defined to use Key values in the same format as the Output
Key File produced by File-AID/RDX.

Figure 174. Output Key File Definition

File-AID/RDX ------------ Output Key File Definition ------------------------

Command ===> 

Parent Object . . .: 'TSOID01.FRSAMP.ORDERTAB'

Record Layout File.: 'TSOID01.FISAMP.COBOLLIB(ORDR010)'
Member Name . . . .: 
DBD Library . . . .: PORDR 
DBD Member . . . .: 'TSOID01.FISAMP.DBDLIB' 

Specify Output Key File Information: 
File Name ===> 
Member ===> (Blank or pattern for member list) 
Disposition ===> NEW (NEW, OLD, SHR) 

Specify File-AID for IMS Extract JCL Information: 
Extract IMS ===> N (Y=Yes, N=No) 
File Name ===> 
Member ===> (Blank or pattern for member list) 

Use this screen to specify the Output Key File to which File-AID/RDX will copy the key values for the
selected KEY relation. The resulting Output Key File can then be used as an Input Key File for another
File-AID/RDX extract or by File-AID for IMS to extract the related IMS data. File-AID/RDX calculates
and displays the required LRECL value. The file’s blocksize value must be compatible with the
precalculated LRECL. You can also specify that the File-AID for IMS extract is to be executed as a step
following the File-AID/RDX extract.
Extract 333

Press Enter after completing this window.

The body of the Output Key File Definition panel consists of the following fields:

Parent Object
Displays the name of the object defined as the parent in a relationship.

Record Layout File

Dataset name of the record or segment layout file specified during the KEY relationship
definition.

Member
Member name of the record or segment layout file.

DBD Library
Displays the name of the dependent DBD library, if specified.

DBD Member
Displays the member name of the dependent root segment.

Specify Output Key File Information

File Name
Specify the name of the file to which the extracted key values will be saved.

Member
If the file you specified in File Name is partitioned (must be PDSE), you can enter a member
name. If you leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-
up window containing a list of members that match the specified pattern. The only valid pattern
character is an asterisk (*). You can create new members by entering the name of the new member
in the Member field.

Disposition
Specify the disposition of the record layout file. You can save to existing files with a disposition
of OLD. Specify a disposition of NEW to create a new file.

If you specify NEW in the Disposition field, you must specify the following allocation
parameters in the Create New File panel.

Key files must be written to new or existing sequential datasets, or existing

PDSEs. Allocating a new PDSE is not supported.
334 File-AID/RDX Reference

Specify File-AID for IMS Extract JCL Information

Extract IMS
Specify Y (Yes) when you want the File-AID for IMS extract to be executed as a step following the
File-AID/RDX extract. The JCL for the extract job must have already been created within File-AID
for IMS and saved to a file. The file containing the File-AID for IMS extract JCL must have a
disposition of OLD.

Specify N (No - default) when you don’t want to include the File-AID for IMS extract JCL in the
File-AID/RDX extract.

File Name
Specify the name of the file that contains the File-AID for IMS extract JCL.

Member
If the file you specified in File Name is partitioned, you can enter a member name. If you leave
this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*).

Allocate New SMS File

The Create New File panel (Figure 175) displays when you specify NEW in the Disposition field in
the Output Key File Definition or any other panel where you can specify a new file. On this panel,
File-AID/RDX allocates SMS-controlled Sequential, PDS, and PDSE files.

This option is displayed only when SMS is installed at your site.

Figure 175. Create New File

File-AID/RDX ---------------- Create New File -------------------------------

Command ===> 

File name: TSOID01.IMSPPART.KEYFILE 

Management Class ===> (Blank for default)
Storage Class ===> (Blank for default)
Generic unit ===> SYSDA 
Volume serial ===> (Blank for default if unit entered)
Data Class ===> (Blank for default)
Space units ===> TRKS (BLK; TRK; CYL)
Primary quantity ===> 5 (In above units)
Secondary quantity ===> 5 (In above units)
Directory blk ===> 5 (Use 0 for sequential file)
Record Format ===> FB (Required for Output Key file)
Record length ===> 15 (Required LRECL for Output Key file)
Block size ===> 
Dataset name type ===> (LIBRARY, PDS, BASIC,
EXTREQ, EXTPREF or blank)
Extended Attributes ===> (NO, OPT or blank) 
Number of Volumes ===> (2:59, or blank)

When parameters are complete, use END to continue.
Extract 335

Use this screen to specify allocation values for a new file to be created by File-AID/RDX.

Depending on the type of file, File-AID/RDX calculates some of the allocation values and locks those
fields from input. For example, when creating a new extract request file, the Record format (VB) and
Record length (1004) fields are locked and their prefilled values cannot be changed.

Press END (PF3) to allocate the SMS file, or use the CANCEL command to cancel the allocation. When
allocation is complete, File-AID/RDX displays a message: FILE ALLOCATED in the upper-right corner
of the screen.

The message “The file will be allocated during execution of the batch job”
appears for files that don’t need to be allocated until execution of the batch
job.

File Name
Displays the name of the file to be allocated.

Management Class
Specify the SMS management class to use for the allocation of the file. The management class
describes the migration, backup, and retention for the file.

Storage Class
Specify the SMS storage class to use for the allocation of the file. The storage class describes the
hardware requirements of the file.

Generic Unit
Specify the device type on which the new file will reside. The names of these devices are
installation dependent.

Volume serial
Specify the volume serial of the direct access device that contains the file.

Data Class
Specify the SMS data class to use for the allocation of the file. The data class describes the
attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.

Space units
Specify one of the following storage unit types depending on how the file size is expressed:

TRK - Tracks
CYL - Cylinders
BLK - Blocks
KB - Kilobytes
MB - Megabytes
336 File-AID/RDX Reference

Primary quantity
Specify the primary allocation quantity as specified in the space units field.

Secondary quantity
Specify the secondary allocation quantity as specified in the space units field.

Directory quantity
For a PDS, specify the number of directory blocks. For a Sequential file, specify zero (0).

Record format
Specify a value with a combination of the following codes (F, V, or U is required):

F - Fixed length
V - Variable length
U - Undefined format
B - Blocked
A - ANSI printer control characters
M - Machine code printer control characters
S - For Sequential files only: Standard for F or spanned for V
T - Track-overflow feature

Record length
Specify a logical record length, in bytes, of the records to be stored in the file. File-AID/RDX
validates this value with the record format and block size.

Block size
Specify the physical record length, in bytes, of the blocks to be stored in the file. File-AID/RDX
validates this value with the record format and record length.

Dataset name type

Specify the type of the dataset you wish to create. The type must be one of these:

LIBRARY

Allocates a Partitioned Dataset Extended (PDSE). This type of partitioned dataset has
unlimited directory blocks and reuses its own space. PDSE libraries do not need to be
compressed.

PDS

Allocates a standard Partitioned Dataset (PDS).

EXTREQ

Indicates that an extended dataset is required.

EXTPREF

Indicates that an extended dataset is preferred.

Extract 337

BASIC

Indicates that neither an extended nor a large format sequential dataset is to be allocated.

blank

Allocates a partitioned or sequential dataset based on the dataset characteristics entered.

Extended Attributes
Specify one of the following extended attributes:

NO

Dataset cannot have extended attributes or reside in EAS.

OPT

Dataset can have extended attributes and reside in EAS.

blank

Use default based on data type.

Number of Volumes
Specify the number of volumes requested for this dataset (2 to 59), or leave this field blank
for a single volume allocation.
338 File-AID/RDX Reference

Extract File Specification

The Extract File Specification screen shown in Figure 176 is displayed when you select Option 7 -
Extract File from the Extract Menu.

Figure 176. Extract File Specification Screen

File-AID/RDX ------------- Extract File Specification -------------------------

Command ===> 

Specify Extract "TO" File Information:
File name ===> FRSAMP.EXTRACT.NEW 
Member ===> (Blank or pattern for member list)
VOLSER ===> 
Disposition ===> (NEW, OLD, SHR)

Extract File Format: 
Compress ===> N (N = No; V = VARCHAR; C = Compress)
DB2 Format ===> 1 (1 = Unicode; 2 = Convert Unicode)

Capture create DDL during extract for:
Views ===> N Alias ===> N Synonyms ===> N ( Y = Yes; N = No)


Use this screen to specify information about the file to which File-AID/RDX will copy extracted data.

Specify Extract “TO” File Information

File Name
Specify the name of the file to which data will be extracted. See Extract File on page 44 and File-
AID/RDX Extract File on page 377 for more information on the extract file.

1. File-AID/RDX will dynamically reallocate a sequential extract file to adjust to the needed
space. Dynamic reallocation is only available for sequential files (DSORG=PS).
2. File-AID/RDX supports extracting from and loading to Sequential (PS) files greater than
65,535 tracks (DSNTYPE=LARGE) when the MVS Operating System also supports them. 
Allocation of a datasets with DSNTYPE=LARGE is not supported. If the Extract File is to be
defined as DSNTYPE=LARGE, it can be pre-allocated.
3. When the specified extract output is to tape or cartridge, File-AID/RDX automatically
creates a summary file on DASD. The name of the summary file is the one specified in your
profile or, if none is specified there, it is the name of the extract file with SUMMARY
appended or a truncated form of the extract file name with SUMMARY as to not exceed 44
characters. If the summary file exists, File-AID/RDX will update (overwrite) its content. Refer
to Extract Summary File on page 45 for more information.

Member
If the file you specified in File Name is partitioned, you can enter a member name. If you leave
this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*). You can create new members by entering the name of the new member in the
Member field.
Extract 339

VOLSER
If the file specified in File Name is non-cataloged or new, specify the volume serial number of the
file. For non-cataloged files, a volume serial number is required. For new files, a volume serial
number is optional.

Disposition
Specify the disposition of the extract "to" file. You can extract to existing files with a disposition
of OLD. Existing files must conform to the format outlined for the extract file in File-AID/RDX
Extract File on page 377. Specify a disposition of NEW to create a new sequential file.

If you specify NEW in the Disposition field, you must specify the following allocation
parameters in the Create New File screen (Figure 175 on page 334).

Extract File Format

Compress
Specify one of the compress options for the extracted data in the extract file:

N File-AID/RDX won’t compress the extracted data. Recommended when extract

file is also to be used outside of File-AID/RDX.
V VARCHAR compression only affects VARCHAR, LONGVAR, VARGRAPHIC, and
LONGVARGRAPHIC columns of Db2 objects; it will not apply to MVS objects. The
VARCHAR compression option only writes the actual data within each VARCHAR
column without padding the records with trailing blanks; the length of a
VARCHAR column will vary for each row based on the data within the row.
VARCHAR data written to the Extract file using VARCHAR compression will be
readable since only the trailing blanks will be dropped.

File-AID/RDX recognizes these compressed extract files as valid input files for all
functions: Load, Delete, and Disguise.
C Compress; The extracted data will be compressed to reduce the file size and
preserve disk space. The entire data record is compressed. This technique
provides the greatest amount of data compression. File-AID/RDX recognizes these
compressed extract files as valid input files for all functions: Load, Delete, and
Disguise.

If you intend to use a compressed extract file outside of File-AID/RDX, for example to
load the extract file via File-AID/EX or manipulate it with File-AID/Data Solutions, you
must decompress it beforehand. Use the Decompress utility provided with the Extract
File Compress Utility on page 715 to decompress a compressed extract file.

DB2 Format
Specify whether data extracted from Db2 tables with Unicode encoding is written to the extract
file in Unicode or EBCDIC format (see also profile value DB2 Format on page 60).

1 Unicode option will write the data using Unicode encoding.

2 Compatibility format will maintain the EBCDIC encoding used in previous
releases.
340 File-AID/RDX Reference

Capture create DDL during extract for

File-AID/RDX always captures the DDL for the tables it extracts related data from as well as the
corresponding indexes, tablespaces, and databases. Capturing the DDL for these additional objects
(views, alias, and synonyms) will require additional Db2 resources and may increase the total extract
time.

Views
Specify whether the extract file should include all the Db2 DDL Create View statements necessary
for File-AID/RDX to also create the Db2 views when performing a load using this extract file.
Note that DDL statements for creating views from a view will not be included.

Yes Extracts all Db2 Create View DDL statements for the Db2 tables from which data
is being extracted.
No File-AID/RDX won’t include Db2 DDL Create View statements in this extract file.

Alias
Specify whether the extract file should include all the Db2 DDL Create Alias statements necessary
for File-AID/RDX to also create Aliases when performing a load using this extract file.

Yes Extracts all Db2 Create Alias DDL statements for the Db2 objects from which data
is being extracted.
No File-AID/RDX won’t include Db2 DDL Create Alias statements in this extract file.

Synonyms
Specify whether the extract file should include all the Db2 DDL Create Synonym statements
necessary for File-AID/RDX to also create synonyms when performing a load using this extract
file.

Yes Extracts all Db2 Create Synonym DDL statements for the Db2 objects from which
data is being extracted.
No File-AID/RDX won’t include Db2 DDL Create Synonym statements in this extract
file.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

END
Returns to the Extract Menu. There are no operands associated with this command.
Extract 341

Data Privacy Specification

The Data Privacy Specification screen shown in Figure 177 is displayed when you select Option 8 -
Data Privacy from the Extract Menu.

Figure 177. Data Privacy Specification

File-AID/RDX ------------- Data Privacy Specification -------------------------

Command ===> 

Select Disguise Method for Extract File:
Disguise Extract File ===> 3 ( 1 = Use DCF; 2 = Use DPR; 3 = No)
DCF: Control File ===> 'TSOID01.FRSAMP.DISGUISE' 
DPR: Repository Name ===> 
Project Name ===> 

Retain pre-disguise file ===> Y ( Y = Yes; N = No)

Create Audit Trail ===> N ( Y = Yes; N = No)
Audit Trail prefix ===>

Use this screen to specify data privacy information for this extract request.

Select Disguise Method for Extract File

Disguise Extract File

Specify whether File-AID/RDX should disguise the extracted data as part of the extract batch job
or not. When set to 1 (DCF) or 2 (DPR), all extracted objects which have disguise criteria defined
in the Disguise Control file (DCF) or in the Dynamic Privacy Rules Project (DPR) will be
disguised.

1 Use DCF. Disguise the extracted data using a disguise control file (DCF). This
option requires installation of Compuware’s File-AID/Data Solutions. 
Before submitting an extract request with the DCF data disguise option, you must
have defined the disguise criteria using Option 5, Data Disguise (see Data
Privacy).
When returning to the Extract Menu, the DISGUISED indicator in front of the
extract file is displayed.
2 Use DPR. Disguise the extracted data using a Dynamic Privacy Rules Project (DPR).
This option requires installation of Compuware’s File-AID/Data Solutions and the
File-AID Data Privacy plugin of the Topaz Workbench.
Before submitting an extract request with the DPR data privacy option, you must
have defined the Dynamic Privacy Rules Project using File-AID Data Privacy.
When returning to the Extract Menu, the DISGUISED indicator in front of the
extract file is displayed.

Note: Before submitting the job, be sure to specify a region size large enough to
run Java (REGION=0M is suggested, 200M is the minimum) in your jobcard (see
also View JCL on page 354).
3 No Disguise. The extracted data will not be disguised.

DCF: Control File

Specify the name of Disguise Control File that contains the disguise criteria for this extract.
Required for Disguise Selection option 1. Disguise Control Files can be created in Option 5, Data
Disguise (refer to Allocate Disguise Control File on page 670). The disguise criteria is specified
using Option 5, Data Disguise (refer to 1 - Criteria on page 610).
342 File-AID/RDX Reference

Hints

• Before you submit the disguise job, make sure that the Disguise Control File includes the
desired disguise criteria for the objects included in the extract file.

• It is also recommended that the relationship information in both the extract and
Disguise Control File matches.

• Also, when using disguise rules with complex criteria, the object that you used to define
the criteria originally must be included (not excluded) in the extract file or the disguise
may not be successful.

• For related disguise rules, always define the criteria on the object that contains all of the
different unique values (including orphans) to be extracted.

DPR: Repository Name

Specify the name of the Privacy Rules Repository to be used with Disguise Selection option 2 for
this extract.

Specify the full repository name (up to 128 characters). Or enter an asterisk (*) by itself for a list
of all repositories. Then select the desired repository from the list (see Privacy Repository List on
page 74).

This field is prefilled with your current profile’s value (see DPR: Repository Name on page 73) or
global default value (see Option G—Global User Defaults).

DPR: Project Name

Specify the name of the Dynamic Privacy Rules Project to be used with Disguise Selection option
2 for this extract. Dynamic Privacy Rules are created with the File-AID Data Privacy component of
the Topaz Workbench. The Dynamic Privacy Rules Project keeps track of how to apply the privacy
rules to which extracted data element. This option requires installation of Compuware’s File-
AID/Data Solutions and File-AID Data Privacy.

Specify the full project name (up to 128 characters) or a pattern ending with an asterisk (*) for a
list of matching projects. Asterisk (*) by itself lists all projects. Then select the desired project
from the list (see Privacy Project List on page 74).

This field is prefilled with your current profile’s value (see DPR: Project Name on page 73).

The specified project must exist in the repository you specified in the DPR:
Repository Name field or the message 'Project not found' is
displayed.

Retain pre-disguise file

Specify whether or not to retain the extract work file before data is disguised. The extract work
file is always in a masked format to prevent access to the undisguised data.

Yes Retain the extract work file before data is disguised.

No Don’t retain the extract work file before data is disguised.

The extract and the disguise are run as separate job steps. By saving the undisguised file you can
rerun the disguise without having to rerun the extract. The disguise may need to be rerun because
it failed due to an error in the disguise criteria, insufficient unique replacement values or because
Extract 343

the disguise criteria did not produce the expected results. To rerun a failed disguise, use Option
5.2, DCF: Disguise Existing Extract on page 664.

The name assigned to the pre-disguise extract file will use the standard RDX routine to generate a
"temporary" name. The name will be the user PREFIX, the mid-level qualifier from the Profile, the
word "EXTRACT" and finally the current date and time fields (i.e. D050128.T055709).

Create Audit Trail

Specify whether or not the File-AID/Data Solutions disguise process should produce an audit trail
report for each object whose data is subject to be disguised.

Yes Create audit trail reports using File-AID/Data Solutions audit trail exits. Note that
the File-AID/Data Solutions audit trail exits determine if a report is created and
what is reported.
No Don’t create audit trail reports.

Audit Trail file prefix

Specify the prefix for the File-AID/Data Solutions audit trail reports for this extract. Prefix plus
USERID can be up to 14 positions, the remainder of the dataset name will follow the above
mentioned naming convention. If prefix is blank, only the USERID will be used. Any value
specified will be appended to the USERID. Precede the prefix value with a single quote (‘) to use
the value without the USERID.

Supporting File Specification

The Supporting File Specification screen shown in Figure 178 is displayed when you select Option 9 -
Supporting Files from the Extract Menu.

Figure 178. Supporting File Specification

File-AID/RDX Supporting File Specification 

COMMAND ===> 

Specify DB2 Object Record Layout Information: 
Create layouts ===> Y (Y = Yes; N = No) 
Language ===> 1 (1 = COBOL, 2 = PLI, 3 = FA COBOL) 
File name ===> FRSAMP.MVS.LAYOUTS.NEW 
Member ===> EXTRACT1 (Blank or pattern for member list) 
Disposition ===> NEW (NEW, SHR) 

Specify File-AID/MVS XREF for File-AID/RDX Extract File Information:
Create XREF ===> Y (Y = Yes; N = No) 
File name ===> FRSAMP.MVS.XREF.NEW 
Member ===> EXTRACT1 (Blank or pattern for member list) 
Disposition ===> NEW (NEW, SHR) 

Specify Topaz Extract Visualizer File:
Create file ===> Y (Y = Yes; N = No) 
File name ===> 
Member ===> (Blank or pattern for member list) 
Disposition ===> SHR (NEW, SHR) 

NOTE: Allocating a Topaz file allows for Extract Visualization
within the Data Visualizer component of Topaz Workbench.

Use this screen to specify what, if any, supporting files should be produced for the extract:

• Db2 record layout file to which File-AID/RDX will copy the record layouts for all objects to be
extracted.
• XREF file for the data elements (D records) of the extract file.
344 File-AID/RDX Reference

• Topaz Extract Visualizer file to visually analyze extract execution with the Data Visualizer
component of the Topaz Workbench.

Specify DB2 Object Record Layout File Information:

Create layouts
Specify whether or not to create a COBOL, PL/I, or FA COBOL record layout file for the extracted
Db2 objects when File-AID/RDX performs the extract. Creating a record layout allows you, for
example, to download the extracted data with File-AID/EX at a later time, or view and compare
extract files with File-AID/MVS.

When you ask File-AID/RDX to create only a record layout (Create XREF =
NO) for MVS objects, the resulting layout is only for the complete extracted
record, not the fields within the record.

Language
Specify whether the record layout will be in COBOL (1), PL/I (2), or FA COBOL (3) format.

1 Create a COBOL record layout.

2 Create a PL/I record layout.
3 Create a FA COBOL record layout.
FA COBOL (3) creates a File-AID COBOL layout with special type VAR for Db2 column
type VCHAR or VC (see also Table 13 on page 306), for example when the FIRSTNME
column is defined to Db2 as VARCHAR(12), with FA COBOL it will be generated as
10 FIRSTNME PIC X(12) VAR . Use option 3, FA COBOL when you need to define
disguise criteria for Db2 tables with column type VARCHAR.

File Name
Specify the name of the file to which the record layout will be saved.

When also creating an XREF for the extract file and your extract includes MVS objects enter the
existing source layout file name, the one used when you defined the relationships. If you specify
a different layout file, be sure to copy the layout members from the source layout file into the
new record layout file before using the XREF file with File-AID/MVS or File-AID/Data Solutions to
access the extract file. The XREF expects all layout members in the same layout file.

Member
If the file you specified in File Name is partitioned, you can enter a member name. If you leave
this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*). You can create new members by entering the name of the new member in the
Member field.

Disposition
Specify the disposition of the record layout file. You can save to existing files with a disposition
of SHR. Specify a disposition of NEW to create a new PDS or sequential file.
Extract 345

If you specify NEW in the Disposition field, you must specify the allocation parameters in the
Create New File screen (Figure 175 on page 334).

Specify File-AID/MVS XREF for File-AID/RDX Extract File Information:

Create XREF
Specify whether or not to create a File-AID/MVS XREF (record layout cross reference) file when
File-AID/RDX performs the extract. File-AID/RDX will create the record layout cross reference for
the data elements (D records) of the extract file.

For Db2 objects, the generated XREF member will point to the detail field level layout created
with the Create Record Layout function.

For MVS objects, the generated XREF member will point to the detail field level layout that will
be left in-place in its source layout file, as specified during the relationship definition.

Creating an XREF allows you, for example, to use File-AID/Data Solutions and modify, or
disguise, the data in the extract file before loading the extracted data to a target subsystem.

Yes Create the XREF. You must also Specify YES in the Creat layouts for Db2 objects
field to create an XREF even if the extract does not include any Db2 objects.
No Don’t create an XREF (record layout cross reference).

When your extract includes MVS objects and you ask File-AID/RDX to create XREF
and layout information, File-AID/RDX will create the XREF, but not a layout for the
MVS data. The XREF points to the source layout as specified when the relationship
had been defined.

File Name
Specify the name of the file to which the record layout cross reference (XREF) will be saved.

Member
The XREF file you specified in File Name must be partitioned. Enter a member name. If you leave
this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*). You can create new members by entering the name of the new member in the
Member field.

Disposition
Specify the disposition of the file. You can save to existing files with a disposition of SHR. Specify
a disposition of NEW to create a new PDS.

If you specify NEW in the Disposition field, you must specify the allocation parameters in the
Create New File screen (Figure 175 on page 334).

Specify Topaz Extract Visualizer File

Use the following fields to specify file information about the Topaz Extract Visualizer file (also known
as the File-AID/RDX Extract Mainframe Trace file). File-AID/RDX will capture statistics (TPT trace)
during extract job execution and save them along with the extract request information to the
specified file. The Data Visualizer component of the Topaz Workbench can use this file to produce a
graphical display with detailed information about extract processing. The insight provided by the
346 File-AID/RDX Reference

Topaz Extract Visualizer allows you to see where time is spent during long-running extracts,
highlighting areas for improvement. You gain a better understanding of complex related extracts,
extract requests, and relationship repositories.

Output to Topaz Extract Visualizer file requires batch extract execution.

INTERACTIVE (online) extract does not create a Topaz Extract Visualizer file
(see also MODE on page 244).

Create file
Specify whether or not to create a Topaz Extract Visualizer file when File-AID/RDX performs the
extract. The file will contain the extract request information as well as the extract execution
information.

Yes Create the Topaz Extract Visualizer file.

No Don’t create a Topaz Extract Visualizer file.

File Name
Specify the name of the file to which the extract request and extract execution information to be
used with the Topaz Extract Visualizer will be saved. The file may be a PDS, PDSE or a sequential
file.

Member
Enter a member name if you specify a PDS or PDSE for the Topaz Extract Visualizer file. If you
leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*). You can create new members by entering the name of the new member in the
Member field.

Disposition
Specify the disposition of the file. You can write to existing files with a disposition of SHR.
Existing files must conform to the format for the Topaz Extract Visualizer file. Specify a
disposition of NEW to create a new file.

If you specify NEW in the Disposition field, you must specify the allocation parameters in the
Create New File screen (Figure 175 on page 334).

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

END
Saves your input and returns to the Extract File Specification Screen. There are no operands
associated with this command.
Extract 347

Checkpoint/Resumption
The Checkpoint/Resumption screen shown in Figure 179 is displayed when you select Option 10-
Checkpoint/Resumption from the Extract Menu.

1. The Checkpoint/Resumption option is not available for

• interactive execution (see also MODE on page 244)
• extract requests with multiple selection criteria sets (see also Option 5 -
Selection Criteria on page 241)
• extract requests with Option 11- Continue with Load.
2. When specifying both Checkpoint/Resumption and Data Privacy Specification, you must
save the Extract Request (see Save Extract Request on page 352) before submitting it.
You must use the same Extract Request file for the Extract Checkpoint and Extract
Resumption jobs (see Checkpoint/Resumption Confirmation Windows on page 349). The
pre-disguise extract file generated during the extract with Data Privacy process
('hlq.EXTRACT.Dyymmdd.Thhmmss’) must also be retained when Checkpoint/Resumption
is specified; it will only be deleted after the resumption completed the whole extract
process and retention is not specified (see alsoRetain Pre-Disguise File on page 72).

Figure 179. Checkpoint/Resumption

File-AID/RDX ---------------- Checkpoint/Resumption ----------------

COMMAND ===> 

Enable Checkpoint/Resumption ===> N (Y = Yes, N = No)

Specify Checkpoint Data File (Required): 
File name ===> 
Member ===> (Blank or pattern for member list) 
Disposition ===> NEW (NEW, OLD) 

Specify Checkpoint Control Options: 
After Elapsed Time In Minutes ===> 
After Extract Step Number ===> 

Specify Checkpoint Control File: 
File name ===> 
Member ===> (Blank or pattern for member list) 
Disposition ===> NEW (NEW, OLD) 

To use the Operator Modify command during extract execution for a 
controlled shutdown with resumption, enable Checkpoint/Resumption and
specify the Checkpoint Data File. 


Enabling checkpoint processing and specifying a checkpoint in your extract request will stop the
extract execution in a controlled manner when the checkpoint (a specified extract step number or a
specified time interval) is reached or when the z/OS Operator Modify command is issued (see also
Stop Extract Execution with z/OS Operator MODIFY Command on page 202). In all cases, processing
on the object currently being extracted will complete before the checkpoint is taken and a controlled
stop occurs. You will then be able to resume and complete the extract from the checkpoint.

The TPT Trace (DD Name TPTPRINT) includes the following statement when the extract execution
was stopped at a specified checkpoint:

Checkpoint taken. Terminate=Y, Write trailers=N, Write reports=N

Enable Checkpoint/Resumption
Specify Y (Yes) when you want to turn on checkpoint processing for this extract request. N (No) is
the default and will not enable checkpoint processing.
348 File-AID/RDX Reference

Specify Checkpoint Data File

The Checkpoint Data file (see also Checkpoint Data File on page 397) stores the File-AID/RDX
internal control blocks, chase keys, key trees, etc., that are required for resumption of the extract at a
later point.

The Extract file and the Checkpoint Data file are logically related to each
other and must be unique. Compuware recommends to define a separate
Checkpoint Data file or member for each extract that has
Checkpoint/Resumption Enabled.

File Name
Specify the name of the Checkpoint Data file. This file can be a PDS, PDSE, or sequential file.

Member
If the file you specified in File Name is a PDS or PDSE, you can enter a member name. If you
leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*). You can create new members by entering the name of the new member in the
Member field.

Disposition
Specify the disposition of the Checkpoint Data file. You can save to an existing file with a
disposition of OLD, replacing any content with the new content. Specify a disposition of NEW to
create a new PDS/PDSE or sequential file.

If you specify NEW in the Disposition field, you must specify the allocation parameters in the
Create New File screen (Figure 175 on page 334). The file will not be created until extract
execution time.

Specify When to Checkpoint

There are two ways to specify a checkpoint. If you specify both, the first encountered will initiate the
controlled execution stop. If neither checkpoint is reached during execution, the extract completes
normally.

After Elapsed Time In Minutes

Specify the minutes of elapsed execution time (clock time) after which File-AID/RDX will initiate
the controlled execution stop.

After Extract Step Number

Specify the extract step number (based on the TPT Trace steps) after which File-AID/RDX will
initiate the controlled execution stop. The Extract step number field can store up to 5 digits.

Specify Checkpoint Control File

The Checkpoint Control file (see also Checkpoint Control File on page 397) stores the 'When to
Checkpoint' information as specified on this panel and is required when specifying a value in either
of the After Elapsed Time In Minutes or After Extract Step Number fields.
Extract 349

File Name
Specify the name of the Checkpoint Control file. This file can be a PDS, PDSE, or sequential file.

Member
If the file you specified in File Name is a PDS or PDSE, you can enter a member name. If you
leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up window
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*). You can create new members by entering the name of the new member in the
Member field.

Disposition
Specify the disposition of the Checkpoint Control file. You can save to an existing file with a
disposition of OLD, replacing any content with the new content. Specify a disposition of NEW to
create a new PDS/PDSE or sequential file.

If you specify NEW in the Disposition field, you must specify the allocation parameters in the
Create New File screen (Figure 175 on page 334).

The extract request must be saved in order to use Checkpoint/Resumption.

If you make changes, you must re-save the request.

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:

END
Saves your input, returns to the Extract Menu and sets the current value for
Checkpoint/Resumption accordingly (see 10- Checkpoint/Resumption on page 242).

Checkpoint/Resumption Confirmation Windows

When Checkpoint/Resumption is enabled for an extract request, File-AID/RDX displays confirmation
windows when submitting the request with Option 13 - View JCL on page 243, 14 - Submit JCL on
page 243, or the G (Go), C (Change selection criteria & Go), or V (View JCL) line command (page 214
or page 219).

When submitting the request for the first time, or the Checkpoint Data file for the request is empty,
File-AID/RDX displays the Checkpoint Processing - Confirmation Window (Figure 180 on page 350)
where you confirm checkpoint processing or cancel this extract execution request.

Yes Continue the extract execution with Checkpoint Processing enabled.

No Cancel the extract execution.
350 File-AID/RDX Reference

Figure 180. Checkpoint Processing - Confirmation Window

File-AID/RDX ------------------ Extract Menu

--------------------------------
Option ===> 14 Scroll ===> CSR 
Profile: RDXMENU 
Pr e File-AID/RDX Checkpoint Processing SSID: DSN 
Command ===> ons. 

De This extract contains checkpoint processing. 

_ If the checkpoint criteria is met the extract will 
_ terminate. cles=1 

_ Do you want to continue ===> (Y/N) 
_ 
_ 

When submitting the request after the extract had been stopped at a checkpoint or with the z/OS
Operator Modify command and the Checkpoint Data file for the request contains resumption data,
File-AID/RDX displays the Checkpoint Processing - Resumption Confirmation Window (Figure 181)
where you confirm to resume the stopped extract or cancel the resumption. If you cancel the
resumption through this window, the contents of Checkpoint Data file will be cleared and the extract
starts from the beginning.

Yes Resume the extract execution from the Resumption Checkpoint.

No Clears the contents of the Checkpoint Data file and starts the extract from the
beginning. If Checkpoint Processing is still enabled, execution will stop when
the checkpoint is reached.

Figure 181. Checkpoint Processing - Resumption Confirmation Window

File-AID/RDX ------------------ Extract Menu

--------------------------------
Option ===> 14 Scroll ===> CSR 
ofile: RDXMENU 
Pr File-AID/RDX Checkpoint Processing SSID: DSN 
Command ===> . 

De This extract request calls for checkpoint processing. 

_ You are about to resume a previously terminated 
_ extract. If you don't want to resume you can start s=1 
the extract from the beginning. 
_ 
_ Resume the process from the checkpoint ===> (Y/N) 
_ 
fined 
_ 
Extract 351

Continue With Load

The Continue With Load screen shown in Figure 182 is displayed when you select Option 11-
Continue with Load from the Extract Menu. It creates a batch job to extract the data with an ESR
(Execute Saved Request) step that submits the load portion after the extract is successful.

The Continue With Load option is not available for interactive execution (see
also MODE on page 244) or when Checkpoint/Resumption is enabled (see
also 10- Checkpoint/Resumption on page 242).

Figure 182. Continue With Load

File-AID/RDX ------------- Continue With Load Menu

--------------------------
COMMAND ===> SITE Profile: RDXMENU 

Primary commands: menu-number, ALL 
Line commands: S or / to create flow through selected options. 

Extract File name ===> FRSAMP.EXTRACT 
Description ===> DB2-FRSAMP.PART_TABLE 

Current Values 
_ 1 Load Object Specifications SSID=DSN, Load Method=DB2 Load 
_ 2 Source/Target Mapping 0 of 6 Objects are excluded 
_ 3 Target Environment Create: Tables=6 + DB TS, Files=0 
_ 4 Existing Data Options 
_ 5 Insert Processing Options 
6 Save Load Request Unavailable 
_ 7 View JCL Unavailable 
_ 8 Submit JCL Unavailable 

The Extract File name and Description fields are protected as it is the extract file of the current extract
request.

Refer to Load Menu on page 422 for a description of the Checkpoint/Resumption menu options.

The options to save the load request, view and submit the JCL are not
available as they are provided on the Extract Menu.

Primary Commands

The REFERENCE and REQUEST primary commands are not available in the
Continue With Load menu.

The following File-AID/RDX-specific primary commands are valid on this screen:

ALL
Selects all continue with load options for you to step through in sequence.

END
Saves your input, returns to the Extract Menu and sets the current value for Continue With Load
to Yes (see 11- Continue with Load on page 243).
352 File-AID/RDX Reference

Save Extract Request

The Save Extract Request screen shown in Figure 183 is displayed when you select Option 12- Save
Extract Request, from the Extract Menu.

Figure 183. Save Extract Request

File-AID/RDX --------------- Save Extract Request ---------------------------

COMMAND ===> 

Specify Extract Request File Information: 
File name ===> 
Member ===> 
Description ===> 

NOTE: Extract Request includes Relationship and Selection Criteria
CANCEL To Cancel Save Request 
END to process and return 

Use this screen to save the current extract request information.

Make sure to select Option 12- Save Extract Request, from the Extract Menu just
before Option 13 in order to save the request as it will be submitted. If you make
changes to the extract request after saving the request, the changes will not be saved
in the request file, only in the temporary extract criteria.

Press Enter to process the file information. The saved request will also appear in your Extract
Reference List (see Extract Reference List on page 213).

The body of the Save Extract Request window consists of the following fields:

File Name
Specify the name of the file where you want to save the extract request. You can save the request
to existing files. Existing files must conform to the format outlined for the extract request file in
File-AID/RDX Extract/Load/Delete Request File on page 368.

If you specify a new file, you must specify the following allocation parameters in the Create New
File screen (Figure 175 on page 334).

Pre-Release 4.3 extract/load request files have fixed or fixed-blocked

(RECFM=F or RECFM=FB) record format. When saving a Pre-Release 4.3
request file, File-AID/RDX will issue an invalid format message. Specify a new
name to save the request file in variable-blocked (RECFM=VB) format.

Member
If the file is partitioned, specify the name of the member to contain the extract criteria.

Description
Enter a short description of the extract criteria. This description is displayed in the Extract Menu
and the Extract Reference List. Using this description is a helpful way to document your extract
criteria.
Extract 353

SAVE Confirmation
When saving an Extract or Load request File-AID/RDX checks to see if the member already exists. If
the member already exists, the Save Confirmation window (Figure 184 on page 353) displays:

Figure 184. Save Confirmation window


File-AID/RDX -------------------- Save Confirmation --------------------
Command ===> 

The Following member exists and will be replaced: 
Request File . . . .: 'TSOID01.FRSAMP.EXTCRIT' 
Member to be saved : MVSKEY 

ENTER to confirm Save and replace existing member 
END return to Save Request enter a different member name 



Press Enter to confirm overwriting the existing file or member name. Press End to cancel the Save
request and return to the Save Extract Request panel where you can enter another file or member
name.
354 File-AID/RDX Reference

View JCL
The ISPF/PDF Edit screen shown in Figure 185 is displayed when you select Option 13 - View JCL,
from the Extract Menu.

Figure 185. ISPF/PDF EDIT Screen—File-AID/RDX-generated JCL

EDIT - File-AID/RDX Generated JCL COLUMNS 001 072

Command ===> SCROLL ===> CSR
You are now viewing the JCL that File-AID/RDX has generated to perform
the required function. Change this JCL as desired before submitting. 

****** ***************************** TOP OF DATA ******************************
000001 //TSOID01 JOB ('XXXXXXX.0XXX'),
000002 // 'INSTALL FR 17.2',
000003 // MSGCLASS=X,NOTIFY=TSOID01,CLASS=A
000004 //* XFRJXTRT
000005 //EXDRV EXEC PGM=XFREXEC,REGION=8192K,MEMLIMIT=4G,
000006 // PARM=(FR,2,B)
000007 //STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ170.CXVJLOAD
000008 // DD DISP=SHR,DSN=CPWR.MXVJ170.SXVJLOAD
000009 // DD DSN=DSNA10.SDSNEXIT,DISP=SHR
000010 // DD DSN=DSNA10.SDSNLOAD,DISP=SHR
000011 //RDXMLIB DD DSN=CPWR.MXVJ170.SXVJMENU,DISP=SHR
000012 //RDXEC DD DSN=TSOID01.RDX.EXTCRIT.D130314.T155100,
000013 // DISP=SHR
000014 //EXTRACT DD DSN=TSOID01.FDSAMP.EXTRPDS(CUSTOMER), 
000015 // DISP=OLD 
000016 //EXTPARMS DD DSN=TSOID01.RDX.PARMS.D130314.T155100, 
000017 // DISP=SHR 
000018 //* 

Use this screen to view or edit the extract JCL generated by File-AID/RDX. Use the SUBMIT command
to submit the extract request for execution. If you want to save this JCL, use the ISPF/PDF CREATE or
REPLACE command before you exit the panel. If you did not save the extract request with Option
12- Save Extract Request, File-AID/RDX deletes the temporary extract criteria work file after extract
execution.

1. If your extract request includes disguising the extracted data, see also Set Incomplete
Disguise Continuation Indicator on page 668 to determine whether you want to change the
default disguise EXEC parameter.
2. You receive the informational message “I321 RDX CNTL PDSE's not deleted, ISPF SUBMIT or
CREATE command issued during VIEW of JCL” to remind you that some extract work files
were not deleted and to clean up the extract work files when you don’t need them any
longer.
3. When disguising the extract with File-AID Data Privacy defined Dynamic Privacy Rules (DPR),
specify a region size large enough to run Java (REGION=0M is suggested, 200M is the
minimum) in your jobcard. See also Disguise Extract File on page 341, option 2, Use DPR.
4. The FARULES DD identifies the Privacy Rules Repository name and Dynamic Privacy Rules
Project ID. 
The FARULES DD may be allocated to a sequential file or a member of a PDS. The record
length must be fixed 80 bytes.

XVJPRINT Execution Log Output

File-AID Data Privacy jobs now write execution information to XVJPRINT DD (instead of SYSPRINT
DD). If XVJPRINT DD does not exist in your JCL, File-AID will dynamically allocate XVJPRINT.

If you want the execution log output sent to a file, point XVJPRINT DD at a file (instead of
SYSOUT=*). This file must be allocated with RECFM=FBA, LRECL=133.
Extract 355

Optional Data Privacy Report Output Written to a File

If you want the Data Privacy Report information written to a fixed layout sequential file and/or to a
CSV (Comma Separated Values) file, manually add the appropriate DD statement to the File-AID Data
Privacy job.

1. When disguising multiple objects, the disposition of the file pointed at by

DPRSTAT1 or DPRSTAT2 must be "MOD". If it is "OLD", only the columns of the last
object will be found in the file.
2. This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

DPRSTAT1 DD (Fixed Layout Sequential File)

When you add a DPRSTAT1 DD to a File-AID Data Privacy job and it points at a file defined as
RECFM=FB,LRECL=2737, at end of job, the file will have the report information for each column
written out as a single record containing all the same report information but in a formatted fixed
layout sequential file.

Example:

//DPRSTAT1 DD DSN=fixed_layout_sequential_file, 
// DISP=MOD

or for a new file:

//DPRSTAT1 DD DSN=fixed_layout_sequential_file, 
// DCB=(RECFM=FB,LRECL=2737,DSORG=PS), 
// SPACE=(TRK,(1,2),RLSE), 
// UNIT=SYSDA, 
// DISP=(NEW,CATLG,CATLG)

Record Layout for Output File

To view the output file in formatted mode you can use File-AID/MVS Browse or Edit with the
following COBOL record layout describing a record in the output file:

01 DPR-STATISTICS. 
15 DPR-COLUMN-NUMBER PIC 9(9) COMP.
15 DPR-NUMBER-CHANGED PIC 9(9) COMP.
15 DPR-NUMBER-INVALID PIC 9(9) COMP.
15 DPR-COLUMN-NAME PIC X(128). 
15 DPR-RULE-NAME PIC X(512). 
15 DPR-RULE-DESCRIPTION PIC X(512). 
15 DPR-LAYOUT PIC X(1573).

DPRSTAT2 DD (CSV)
When you add a DPRSTAT2 DD to a File-AID Data Privacy job and it points at a CSV (Comma
Separated Values) file defined as RECFM=VB,LRECL=2751, at end of job, the file will have the report
information for each column written out as a single record containing all the same report
information but they will be Comma Separated Value (CSV) records.

Example:

//DPRSTAT2 DD DSN=CSV_file, 
// DISP=MOD

or for a new file:

356 File-AID/RDX Reference

//DPRSTAT2 DD DSN=CSV_file, 
// DCB=(RECFM=VB,LRECL=2751,DSORG=PS), 
// SPACE=(TRK,(1,2),RLSE), 
// UNIT=SYSDA, 
// DISP=(NEW,CATLG,CATLG)

Optional Source Data Identifiers (SDIs) Override During Execution

File-AID/RDX now allows you to replace, during execution of a DPR project, Source Data Identifiers
(SDIs) defined in the File-AID Data Privacy project.

To override SDIs, manually add the following DD statement to the JCL:

//DPRSDI DD DISP=SHR,DSN=u.data.mysdis

where the existing dataset u.data.mysdis contains the definitions of SDIs that will be used for this
execution.

If the DPRSDI DD is defined in JCL, all SDIs defined in the project will be ignored and replaced with
definitions provided in the override dataset.

If the specified override file does not exist, Message UNABLE TO OPEN
DPRSDI FILE is issued and processing stops with a RC=8.

Override File Format

Replacement SDIs can be defined either in XML or in JSON format. The tags in XML and names in
name/value pairs in JSON correspond to SDI properties that can be defined through the Compuware
Workbench User Interface. Refer to the Source Data Identifier Overrides topic in the Compuware Workbench
File-AID Data Privacy User Guide for more information.

Override Data Privacy Environment Parameters

If you need to, you can override the Data Privacy Environment parameters listed in Table 15
(established with your site’s File-AID Data Privacy Environment parameters (refer to File-AID Data
Privacy Environment in the File-AID Advanced Configuration Guide).

Table 15. Data Privacy Environment Parameter Overrides

Parameter DD statement
JAVA_VIRTUAL_MACHINE_PATH 
FAJPATH
(z/OS UNIX Path Name for Java Virtual Machine (JVM))
JAVAOPNn
FAJOPTS
(Java (JVM) Options)
FILEAID_SERVICES_USER_EXECUTION_PORT
FAIPADDR
(File-AID Data Privacy IP address and execution port)
FILEAID_RULES_ENGINE_PATH
(z/OS UNIX Path Name for File-AID Rules Engine (FARE), FAEXPATH
formerly Common Disguise Engine (CDE))

To do so, insert any of these FAJPATH, FAJOPTS, FAIPADDR, and FAEXPATH DD statements as needed.
For example:

//FAIPADDR DD * 
127.372.322.101:4180
/* 
//FAJPATH DD * 
/usr/lpp/java/J7.1_64.bld111513/
/*
Extract 357

It is also possible to specify more than one debug parameter inline. For example:

//FADEBUG DD *
Level=FINER 
Filename=/u/userid/
/*

Override Execution Parameter in a Data Privacy Project

In order to override an execution parameter (public variable or translate table) in a Data Privacy
Project, add a DPRPARMS DD statement to your JCL. This DD can point to a file or a PDS member
containing the override values (maximum record length is 512 bytes). The override values can also be
specified inline. Specify override values in the following way:

executionParm=overrideValue

The execution parameter must have been defined in the Topaz Workbench user interface for the
project.

Example:
Your DPR project ‘project1’ includes:

• 2 translate tables, ‘Title table’ and ‘Titles for HR dept’ (Figure 186)

– The source table for ‘Title table’ is file ‘ABC.TRANS’.

• 2 public variables, ‘scramvar’ and ‘altscram‘ (Figure 187 on page 358)

– The initial value for ‘scramvar’ is string ‘123abc’.

• 2 execution parameters, ‘Parameter1’ identifies the translate table ‘Title table’ and
‘Param2Variable’ identifies variable ‘scramvar’ (Figure 188 on page 359).

At execution time, however, you want to override the defined execution parameters for translate
table ‘Title table’ with the new translate table ‘ABC.NEWTRANS’ and the initial value of variable
‘altscram‘ with the new string ‘789xyz’. The new translate table must have the same characteristics as
the original one.

To do so, insert the following DPRPARMS DD statement in the JCL (inline example):

//DPRPARMS DD * 
Parameter1=ABC . NEWTRANS
Param2Variable=789xyz
/*
358 File-AID/RDX Reference

Figure 186. Manage Translate Tables

Figure 187. Process Variables

Extract 359

Figure 188. Manage Execution Parameters

Execution Parameter List of Values

If the execution parameter variable type is either a String List or Numeric List, you can also override
the list of values.

Specify a list of values in the following way:

executionParm=LIST(X)=overrideValueXoverrideValueXoverrideValue

The X variable inside the =LIST( )= parentheses defines the delimiter for the list of values. The
delimiter can be any character. Connect each overridevalue with the defined delimiter.

For example, insert the following DPRPARMS DD statement in the JCL (inline example) to override
the values of the String List named STATE (* is the defined delimiter):

//DPRPARMS DD * 
STATE=LIST(*)=MI*OH*RI*CA*MO*IN
/*

Multiple Origins for a Data Privacy Rule

Normally, when a Data Privacy Rule is applied to a related field, one object 1 in the relationship
thread is chosen as the “origin”. For every record in the origin, the Data Privacy Rule is applied to the
related field and the BEFORE and AFTER values are saved. For every record in a “non-origin”, the Data
Privacy Rule is not applied. Rather, the appropriate AFTER value is retrieved from where it was saved.
This guarantees relationship integrity.

This methodology is efficient and sufficient in most scenarios, but there are some scenarios where no
single origin contains all of the values required by the non-origins. When this occurs, it is possible to
direct File-AID to use all objects that contain the necessary fields referenced by the Data Privacy Rule
as origins. This directive is specified by adding to your JCL:

1. An object is a Db2 table, an MVS file, or an IMS segment.

360 File-AID/RDX Reference

//MULTISRC DD DUMMY

The use of multiple origins degrades job execution performance, so it is not

recommended as a default behavior.

Special Instructions for Oracle Translate Table

If your Data Privacy job uses Data Translation with an Oracle Translate Table and your File-AID Data
Privacy Environment parameters do not include the following JAVA options (refer to File-AID Data
Privacy Environment in the File-AID Advanced Configuration Guide), insert the following FAJOPTS DD
statement after the FARULES DD statement:

//FAJOPTS DD * 
-verbose:sizes
-Dfile.encoding=UTF-8
-Dlog.encoding=IBM1047

If the JAVA options in the File-AID Data Privacy Environment parameters include other site specific
JAVA options, also add them to the FAJOPTS DD statement before submitting the job.

Adding the above FAJOPTS DD statement will override the JAVA options in the File-AID Data Privacy
Environment parameters and make it possible to run an Oracle translation while the log will be
generated in EBCDIC.

An indicator that you need to make this JCL change is when the Data Privacy job ended with the
following error:

Method execPrivacyRules failed (RC=8) at line nnn in file EXECDPR.C.

However, this general message is not conclusive. Your error log file should have something like the
following:

Throwable occurred: java.sql.SQLException: Internal - Unexpected value 

at oracle.jdbc.driver.T4CTTIoauthenticate.processRPA(T4CTTIoauthenticate.java:516) 
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:295) 
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) 
at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate.java:390) 
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:356) 
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:531) 
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:221) 
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32) 
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:503) 
at java.sql.DriverManager.getConnection(DriverManager.java:322) 
at java.sql.DriverManager.getConnection(DriverManager.java:358) 

If you see the above, then you need to insert the FAJOPTS DD statement.

Redirect File-AID/Data Solutions Report (Data Disguise with DCF only)

When using a Disguise Control File (DCF) to disguise extracted data, you can choose to redirect the
disguise report output produced by File-AID/Data Solutions to FADSPRNT DD by simply adding it to
the JCL in the disguise step. The FADSPRNT DD can point at a file or at SYSOUT. When it points at a
file and multiple objects are being disguised, use DISP=MOD.

Since the use of FADSPRNT splits the File-AID/Data Solutions report output away from the File-
AID/RDX report output, FADSPRNT and SYSPRINT must be looked at together to get a complete
picture of the job.

Control Card Cleanup

The last step, CLEANEXT, in the extract jobs deletes the File-AID/RDX EXTPARMS parameter file.
Whether step CLEANEXT is commented out or executed is determined by the global job option
Delete in-stream data datasets at EOJ (page 83). If the job option is set to NO, File-AID/RDX
Extract 361

EXTPARMS parameter files created in the extract jobs will NOT be deleted. Keeping the datasets until
all steps run successfully allows for the restarting of the JCL at any step.

Periodically, you may want to manually delete the EXTPARMS parameter files that are no longer
needed for saved jobs to be resubmitted.

View REXX
The ISPF/PDF Edit screen shown in Figure 189 is displayed when you select Option 12, from the
Extract Menu and the Execute Extract online status has been set to ON with the MODE primary
command.

Figure 189. ISPF/PDF EDIT Screen—File-AID/RDX Generated REXX

VIEW - File-AID/RDX Generated REXX COLUMNS 001 072

Command ===> SCROLL ===> CSR
You are now viewiing the REXX that File-AID/RDX has generated to perform
the required function. 



****** ***************************** Top of Data ******************************
000001 /* REXX */ 
000002 /* TRACE R */ 
000003 MSG_STAT = MSG("OFF") 
000004 ADDRESS TSO 
000005 'FREE FI(DFSPARM)' 
000006 'FREE FI(SYSOUT)' 
000007 'FREE FI(RDXEC) ' 
000008 'FREE FI(RDXMLIB) '
000009 'FREE FI(EXTRACT) '
000010 'FREE FI(X37MSG)' 
000011 'FREE FI(PROGRESS)'
000012 'FREE FI(REPORT) ' 
000013 'FREE FI(RDXSQLCD)'
000014 'FREE FI(SYSTERM) '
000015 'FREE FI(SYSPRINT)'
000016 'FREE FI(TPTPRINT)'

Use this screen to view or edit the extract REXX statements generated by File-AID/RDX. If you want
to save these Rexx statements, use the ISPF/PDF CREATE or REPLACE command before exiting this
panel. Otherwise, File-AID/RDX deletes this file after extract execution.

Submit JCL
Select Option 14 - Submit JCL, from the Extract Menu after you have completed specifying all your
extract options, selection criteria, and output files to submit your extract request to perform the
extract.

You will receive a confirmation message that your job has been submitted.

Execute Rexx
When the Execute Extract Interactively (online) status has been set to ON with the MODE primary
command, select Option 13, from the Extract Menu after you have completed specifying all your
extract options, selection criteria, and output files to execute your extract request to perform the
interactive extract.

You can then follow the extract execution online. Status messages inform you about the progress. The
extract is complete when you receive a completion message.
362 File-AID/RDX Reference

Interactive Extract Execution

When the Execute Extract Interactively (online) status has been set to ON with the MODE primary
command, and you selected Option 13 from the Extract Menu you can follow the extract execution
interactively. Extracted row count messages inform you about the progress (see Figure 190 on page
362).

Press the ESC key to terminate the interactive extract. If you terminate the execution
before the completion message your extract file will not be loadable as it is incomplete
and lacking extract information and data. You also may need to manually delete any
working files created during the extract execution.

Figure 190. Interactive Extract Execution

File-AID/RDX -------- Online Load Processing Status------ Row 1 to 12 of 12 

Option ===> 

Hit ATTN to terminate Load Processing 

Load Object Row Count Time 
---------------------------------------------- --------- ---------- 
FRSAMP.ORDER_TABLE 3 11:24:51 
FRSAMP.ORDER_LINE_TABLE 5 11:24:51 
FRSAMP.PART_TABLE 5 11:24:51 
FRSAMP.SUPPLIER_TABLE 7 11:24:51 
FRSAMP.ORDER_TABLE 3 11:24:52 
FRSAMP.CUSTOMER_TABLE 1 11:24:52 
FRSAMP.ORDER_LINE_TABLE 3 11:24:52 
FRSAMP.PART_TABLE 3 11:24:52 
FRSAMP.SUPPLIER_TABLE 2 11:24:52 
FRSAMP.ORDER_TABLE 1 11:24:53 
FRSAMP.CUSTOMER_TABLE 1 11:24:53 
FRSAMP.CONTACT_TABLE 1 11:24:53 
******************************* Bottom of data ********************************




Interactive Extract Reports

The extract is complete when the extract reports display (see Figure 191). Use standard scrolling
commands to view the reports. Return to the Extract Menu with the END command.
Extract 363

Figure 191. Interactive Extract Reports

Menu Utilities Compilers Help 

-------------------------------------------------------------------------------
BROWSE TSOID01.RDX.EXTRACT.OUTPUT Line 00000021 Col 001 080 
Command ===> Scroll ===> CSR 
1File-AID/RDX 17.2 Extract Progress Report PAGE 1
DATE 2016-04-12
TIME 11.38.30

Extract File: TSOID01.FRSAMP.EXTRACT 
Member: EXCLD 

Extract Object Row Count Time 
---------------------------------------------- --------- ---------- 
FRSAMP.ORDER_TABLE 33 11:43:17 
FRSAMP.ORDER_LINE_TABLE 49 11:43:18 
FRSAMP.PART_TABLE 28 11:43:19 
FRSAMP.CUSTOMER_TABLE 15 11:43:19 
1File-AID/RDX 17.2 Relationship Criteria Report 


0Location: LOCATION 
0Relationships for object: FRSAMP.ORDER_TABLE Ext
0 
Parent Object Dependent Object 
364 File-AID/RDX Reference

Miscellaneous Extract Topics

This section provides information about the following topics:

• Extract JCL
• Db2 Privileges
• File-AID/RDX Extract/Load/Delete Request File
• File-AID/RDX Extract File
• Record Layout and File-AID/MVS XREF JCL
• File-AID/RDX Record Layout File
• File-AID/MVS XREF File
• Topaz Extract Visualizer File
Extract 365

Extract JCL
The extract JCL shown in Figure 192 on page 365 performs the batch portion of the extract process
and generates the appropriate reports. The extract JCL can be coded and executed separately in a
batch job. In addition, File-AID/RDX can automatically generate the JCL through the online extract
screens.

Figure 192. Extract JCL

//EXDRV EXEC PGM=XFREXEC,REGION=8192K,MEMLIMIT=4G,

// PARM=(FR,2,B)
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//RDXEC DD DSN=extract-criteria-file(member),DISP=SHR
//EXTRACT DD DSN=extract-to-file-name,DISP=SHR
//EXTPARMS DD DSN=extract-parms-file,DISP=SHR
//*
//DDxxx DD DSN=file-name-of-MVS-object-xxx,DISP=(SHR)
//LAYxxx DD DSN=layout-file-name-for-MVS-object-xxx,DISP=(SHR)
//XREFxxx DD DSN=XREF-file-name-for-MVS-object-xxx,DISP=(SHR)
//KEYxxxxx DD DSN=output key file-name,DISP=OLD
//SORTWK01 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SORTWK02 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SORTWK03 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//DFSPARM DD UNIT=SYSDA, 
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=8000,DSORG=PS),
// SPACE=(TRK,(1,1),RLSE), 
// DISP=(NEW,DELETE,DELETE) 
//* 
//X37MSG DD SYSOUT=(*)
//PROGRESS DD SYSOUT=(*)
//REPORT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//IXRPT DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//TPTPRINT DD SYSOUT=(*)
//CHKPTCTL DD DSN=checkpoint control file, 
// DISP=SHR 
//CHKPT DD DSN=checkpoint data file, 
// DISP=SHR 
//VISUALIZ DD DSN=file-name-of-Topaz Extract Visualizer file, 
// DISP=(NEW,CATLG,CATLG), 
// DCB=(RECFM=VBA,LRECL=27962,BLKSIZE=27966), 
// SPACE=(CYL,(10,2,10)), 
// UNIT=SYSDA 
//SYSOUT DD SYSOUT=(*)
//SORTLST DD SYSOUT=(*)
//IDCAMLST DD SYSOUT=(*)
//SYSUDUMP DD SYSOUT=(*)
//DPARMS DD *
CYL
1
1
//* 
//CLEANEXT EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 XFRJCLXT 
//SYSPRINT DD SYSOUT=*
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE extract-parms-file,
SET MAXCC=0
SET LASTCC=0
//* 
//* /*XFRJCLXT*/

XFREXEC is the File-AID/RDX program name.

366 File-AID/RDX Reference

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 16:

Table 16. EXEC Statement PARM Field—Extract Step

Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option 2 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

Extract from Db2 Image Copy

For an extract from Db2 Image Copy the program name is XFRIMAGE and requires that the File-
AID/RDX load library be authorized.

File-AID/RDX Release 17.02 does not support executing XFRIMAGE with JCL
parameters generated by prior releases of File-AID/RDX. It is recommended
that the JCL for Extract from Db2 Image Copy be generated in File-AID/RDX
Release 17.02.

Figure 193. Extract JCL XFRIMAGE Parm statement

//EXDRV EXEC PGM=XFRIMAGE,REGION=8192K,MEMLIMIT=4G,

// PARM=(FR,2,B)

The parameter information in the PARM field in the EXEC statement must have the following format:

Table 17. EXEC Statement PARM Field—Extract Step for Image Copy
Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option 2 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

DD statements
The following DD statements are required for extract:
Table 18. DD Statements—Extract
DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD) and Db2 load libraries
RDXMLIB Library containing File-AID/RDX messages.
RDXEC Library containing the File-AID/RDX extract criteria (only required if extract criteria is
being applied).
EXTRACT File to which extracted data is written.
EXTPARMS File containing the extract parameters (see EXTPARMS File on page 367).
DDxxx File name of the MVS object xxx; only applicable when extracting MVS objects.
LAYxxx File name of layout file for the MVS object xxx; when extracting MVS objects.
KEYxxxxx File name of the defined Output Key file; when extracting KEY relationships.
XREFxxx File name of XREF file for the MVS object xxx; when extracting MVS objects.
SYSOUT Output class for SORT utility.
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSTERM Output class for runtime errors.
Extract 367

Table 18. DD Statements—Extract (Continued)

DD Statement Description
SYSPRINT Standard output stream.
SYSIN Control card used by File-AID/RDX to sort data during the extract process.
SORTWK01
SORTWK02 Work files required by the SORT utility.
SORTWK03
X37MSG
REPORT
Output class for error messages and reports.
PROGRESS
IXRPT
TPTPRINT Standard output stream for extract diagnostics.
CHKPTCTL Optional Checkpoint Control File.
CHKPT Optional Checkpoint Data File.
VISUALIZ File name of the optional Topaz Extract Visualizer file.
IDCAMLST Parameters for temporary extract files for XML and MVS objects.
DPARMS Space allocation parameters for temporary extract files.

Note: File-AID/RDX will dynamically reallocate temporary work files, key tree and
chase key files only when running extracts using 64 bit memory (above the bar)
processing support. See also parameter
EXTENDED_ADDRESSING_AREA_IN_GIGABYTES in the File-AID Advanced
Configuration Guide.

EXTPARMS File
The EXTPARMS file contains the relevant parameters to execute File-AID/RDX programs. Each
program function, Extract, Load, Disguise, etc. generates different parameters that are necessary for
that function to run correctly. Do NOT change any of the parameters in the EXTPARMS file, unless
instructed to do so by Compuware customer support for diagnostic purposes. The TEST mode
indicator (N or Y) is used for debugging purposes.

Return Codes
An execution return code (RC) appears in the output listing. For return codes other than 0, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return Code Description

0 Job ran to completion.
4 Job ran to completion, warnings issued.
8 Job completed with error.
16 Severe error, job aborted.

Db2 Privileges
During extract, the SELECT privilege is required for all tables included in the extract. The plan being
used to execute File-AID/RDX requires the SELECT privilege for the Db2 system catalog tables.

You must have one of the following authorization privileges to extract data from Db2 Image Copy:

• RECOVERDB privilege for the database

• DBADM, or DBCTRL authority for the database
• SYSCTRL or SYSADM authority
368 File-AID/RDX Reference

File-AID/RDX Extract/Load/Delete Request File

The Extract/Load/Delete Request file contains records that reflect the values you specified in the
during the interactive phase of the extract, load, or delete process. The Extract/Load/Delete Request
file evolved from the Extract Criteria file from earlier versions of File-AID/RDX.

Figure 194 on page 369 shows a sample request file. Note that in the figure the reserved spaces for
Db2 creator ID and table names (up to 128 spaces for each) have been reduced to fit into this figure.
When viewing the request file online, use the RIGHT and LEFT scroll commands to view the Db2
object names at the end of the records.

The request file has the following characteristics:

File organization Either partitioned or sequential (DSORG=PO or DSORG=PS)

Record format Variable-blocked (RECFM=VB)
Logical record length Maximum LRECL determined by File-AID/RDX (default is 1004)

Pre-Release 4.3 extract/load request files have fixed or fixed-blocked

(RECFM=F or RECFM=FB) record format (see also Save Extract Request on
page 352).

The first two bytes of each record contains either blanks or “--.” Records with blanks in positions 1
and 2 are processed by SPUFI. Records that start with the characters “--” are considered comments by
SPUFI and are, therefore, ignored.

The third and fourth bytes of each record contain the record’s type.
Figure 194. Sample Extract/Load Request File

Extract
--00FILE-AID/RDXVERSION 17 RELEASE 02 MOD 00 SUB 26 EP
--401 NN00037Y
--281 TSOID01.FRSAMP.EXTRACT OLD -
--291SYSDA TRK0010005000VB 027994027998
--282 TSOID01.FRSAMP.EXTCRIT2 PCUST NOLD -
--27DESCRIPTION: DB2-FRSAMP.ORDER_TABLE
--292SYSDA TRK0004004010FB 000080000000
--286 TSOID01.FRSAMP.RELATION OLD -
--296 CYL
--287 TSOID01.RDX.PROFILE OLD -
--297 CYL
--28B TSOID01.FRSAMP.DISGUISE OLD -
--29B CYL
--56DRIVING: LOCK =N D701DD701CW01 FRSAMP ORDER_TABLE
--14 C=* M=* N=* X=N P=NONE I=Y 001/001
--57MODEL: D801DD801CW01 FRSAMP ORDER_TABLE
--70 DISG=3 RETAIN=Y AUDIT=N PREFIX=KFL 8
--56RELATED: LOCK =N D701DD701CW01 FRSAMP CUSTOMER_TABLE
--15 C=* M=* N=* X=N P=NONE U=N I=Y 001/001
--56RELATED: LOCK =N D701DD701CW01 FRSAMP CONTACT_TABLE
--15 C=* M=* N=* X=Y4 P=NONE U=N I=Y 001/001
--56RELATED: LOCK =N D701DD701CW01 FRSAMP ORDER_LINE_TABLE
--15 C=* M=* N=* X=N P=NONE U=N I=Y 001/001
--56RELATED: LOCK =N D701DD701CW01 FRSAMP PART_TABLE
--15 C=* M=* N=* X=N P=NONE U=N I=Y 001/001
--56RELATED: LOCK =N D701DD701CW01 FRSAMP SUPPLIER_TABLE
--15 C=* M=* N=* X=Y4 P=NONE U=N I=Y 001/001
--06CHASE ALL RELS: Y
--07DPSI=YYNN C=* M=* MAX=Q UR=Y IMAGE=N F2 V=N A=N S=N COMPRESS=N KT_EMEM=E CK_EMEM=E KT_DEGR=9 GH=Y
--52P D 0 D701CW01 FRSAMP CUSTOMER_TABLE FRSAMP
--53D7017100
--52D D 0 D701CW01 FRSAMP ORDER_TABLE
--53D7017100
--13DPSI=-YN- C=* M=* D=* X=N E=NN A
--16MISCDB2:2005-07-14 10.11.36 TSOID01
--50SOURCE COLUMN=CUSTOMER_NUMBER TYPE=CHARACTER LENGTH= 00006
--51OFFSET= 00000SUB1=00000SUB2=00000SUB3=00000NOSUB=00000PREC=00000SCALE=00000
--50TARGET COLUMN=CUST_NUM TYPE=CHARACTER LENGTH= 00006
--51OFFSET= 00000SUB1=00000SUB2=00000SUB3=00000NOSUB=00000PREC=00000SCALE=00000
--52P D 1 D701CW01 FRSAMP CUSTOMER_TABLE FRSAMP
--53D7017100
--52D D 1 D701CW01 FRSAMP CONTACT_TABLE
--53D7017100
--13DPSI=---N C=* M=* D=* X=N E= RCONTCUST
--16MISCDB2:2005-07-08-09.39.50.880402 2005-07-08-09.39.50.880402
--50SOURCE COLUMN=CUSTOMER_NUMBER TYPE=CHARACTER LENGTH= 00006
--51OFFSET= 00000SUB1=00000SUB2=00000SUB3=00000NOSUB=00000PREC=00000SCALE=00000
--50TARGET COLUMN=CUSTOMER_NUMBER TYPE=CHARACTER LENGTH= 00006
--51OFFSET= 00000SUB1=00000SUB2=00000SUB3=00000NOSUB=00000PREC=00000SCALE=00000
--52P D 2 D701CW01 FRSAMP CUSTOMER_TABLE FRSAMP
--53D7017100
--52D I 2 IX.FISAMP.DBDLIB PCUST 
--13DPSI=YYNN C=* M=* D=* X=N E= A
--59C TSOID01.FRSAMP.CONDAR P0000001
--16MISCDB2:2005-07-14 10.13.52 TSOID01

369
370 File-AID/RDX Reference

A request file could contain the record types as listed in Table 19.

Table 19. File-AID/RDX Request File Record Types

Record Type Description
00 This record type indicates the version, release, modification level, subrelease of File-AID/RDX that created
the file. It also indicates the request type: E=extract, L=load, B=both extract and load, or D=delete,
whether it is a P=permanent (saved) or T=temporary request, and Y flags the request as Nonexecutable.
blank This record type contains the Db2 SELECT statement(s) generated by the DB2 Object Selection Criteria
screen. This record type has no record-type number associated with it.
40n This record type provides information whether the request includes an Input (external) Key file and/or
summary file, creates a record layout and/or XREF file, which layout language is to be used. It also
includes the CCSID of the terminal saving request, whether to use Db2 parallelism, whether to create a
Topaz Extract Visualizer file, and whether Checkpoint/Resumption is enabled. The third digit n specifies
the file type. See type 28 for a list of the file types.
28n This record type specifies file name and disposition information for the different files in the current
request. The third digit n specifies the file type:

n
1 = Extract file
2 = Request file
3 = Extract summary file
4 = Record layout file
5 = XREF file
6 = Relationship file
7 = Profile file
8 = Input (External) Key file
B = Disguise Control file (DCF)
D = Topaz Extract Visualizer file
E = Checkpoint Control file
F = Checkpoint Data file
Y = GDG file
27 This record type contains the request description (50 bytes).
29n This record type specifies file allocation information for the corresponding type 28 files in the current
request. The third digit n specifies the file type. See type 28 for a list of the file types.
56 56 DRIVING: This record type identifies the driving object type (D=DB2, M=MVS), and object name of
the driving object at the end of the record to accommodate long object names. For Db2 objects it also
includes the location and creator ID, each providing space for the maximum length. In addition, the type
56 record contains the value specified in the Lock Table field on the Extract Scope - Object View screen,
with FUNCTION LOCK enabled (see also L (Lock Table) on page 258 and FUNCTION LOCK on page 262)
and the Db2 subsystem ID.
54 This record type is only included if record type 56, 52P or 52D is an MVS object. It follows each MVS 56,
52P or 52D record to identify the object’s layout type (S=Single, X=XREF), layout file name, member
name, and IO exit name.
54A This record type is a continuation record for record type 54. It identifies the 01 level record name.
55 This record type is only included if the preceding record type 54 is an XREF type (54X). It follows each
54X or 54A record to identify the object’s XREF file name, and member name.
44 This record type identifies the location, subsystem, creator, and table name of the base table associated
with the view you specified as the driving table. This record type occurs only when you specify a view as
the driving table. When the 44 record type occurs, it follows the 56 Driving: record type and precedes
the 56 Related: record type.
18 This record type identifies the type and name of the Input (external) Key file specified as selection input
to the driving object. Valid types are Standard and Delimited. For delimited key files type 18 record
includes the delimiter options as specified during the selection criteria specification: 1 or 2 for single (1)
or double (2) quotation marks, the column delimiter (, is default), Y or N for quotes on character data,
and Y or N for quotes on numeric data. See also Input Key File Specification on page 295.
Extract 371

Table 19. File-AID/RDX Request File Record Types (Continued)

Record Type Description
14 Db2 Driving object only. This record type contains

• C= cycle limit for the object;

• M= maximum number of records to extract from this object;

• N= select every nth record from this object;

• X= object excluded status:

– N object not excluded;
– Y1 object excluded by user;
– Y2 object excluded by line command "A" (All);
– Y3 object excluded by object not found;
– Y4 object excluded by scope;

• P= Passthru status:
– ALL extract all records (line command "A");
PASSTHRU don’t extract records (line command "P");
– NONE extract related records as applicable;

• I= satisfy AR/RI indicator Y or N

• nnn/nnn Set number of Total Set number;

57 57 MODEL: This record type identifies the Db2 object that the driving object used for its relationships
even though no relationships were defined for the Db2 driving object.
70 Identifies the data disguise information for this extract request.

• DISG=disguise extract option 1 (DCF), 2 (DPR) or 3 (no)

• RETAIN= retain pre-disguise extract file Yes or No

• AUDIT= create data disguise audit trail files Yes or No

• PREFIX= identifies the prefix for the data disguise audit trail files
45 Identifies the File-AID Data Privacy Dynamic Privacy Rules Project name and ID as well as the Privacy Rules
Repository name for this extract request.
17 This record type contains the part of the SELECT statement generated by the key file selection input to
the driving object. It contains the Db2 column or MVS field name and the location and type of the
selection value in the key file. For delimited files, the INDSN parameter specifies the field number, for
standard files, it specifies the starting position, length, and type.
56 56RELATED: This record type identifies the object type (D=DB2, M=MVS), and object name of a related
object at the end of the record to accomodate long object names. For Db2 objects it also includes the
location and creator ID, each providing space for the maximum length. In addition, the type 56 record
contains the value specified in the Lock Table field on the Extract Scope - Object View screen, with
FUNCTION LOCK enabled (see also L (Lock Table) on page 258 and FUNCTION LOCK on page 262) and
the Db2 subsystem ID. A type 56 Related: record exists for every related object included in the extract.
372 File-AID/RDX Reference

Table 19. File-AID/RDX Request File Record Types (Continued)

Record Type Description
58 58Clone: This record type identifies the cloned objects. There can be many 58 record types listed per
request. They list the original and new names. The type of clone change is identified with a five digit
code XYnnn, where:

X is the major type:

G = global parameter 
U = object identification
S = SSID
L = location

Y is the minor type:

D = DSN change
N = object name
L = layout
X = XREF
I = IMS and Output key file
nnn only applies to major/minor type GD 
000 = Extract file
001 = Extract request file
002 = Extract summary file
003 = Extract Record layout file
004 = Extract XREF file
005 = Relationship file
006 = Profile file
007 = Input (External) Key file
008 = Disguised Extract file
009 = Disguise Criteria file
010 = Disguise Control file (DCF)
011 = Business Rules file
15 Db2 Non-Driving objects. This record type contains

• C= cycle limit for the object;

• M= maximum number of records to extract from this object;

• N= select every nth record from this object;

• X= object excluded status:

– N object not excluded;
– Y1 object excluded by user;
– Y2 object excluded by line command "A" (All);
– Y3 object excluded by object not found;
– Y4 object excluded by scope;

• P= Passthru status:
– ALL extract all records (line command "A");
PASSTHRU don’t extract records (line command "P");
– NONE extract related records as applicable;

• U= unrelated object Y or N

• I= satisfy AR/RI indicator Y or N

• nnn/nnn Set number out of Total Sets

Extract 373

Table 19. File-AID/RDX Request File Record Types (Continued)

Record Type Description
07 This record type contains global navigation and sampling controls as well as other extract options.

• DPSI= The status Y, N, or - (not relevant) is given for the global Navigation controls DPSI (Direct
Path, Parent Path, Sibling Path, and Indirect Path). Direct Path status can also be C for All Children
only and P for Plus (see also Direct on page 58).

• C= global cycle limit;

• M= maximum number of records to extract for entire execution;

• MAX= Q (Quiesce) or S (Stop);

• UR= uncommitted read (Y or N)

• IMAGE= image copy (Y or N)

• V= capture View DDL (Y or N)

• F= Db2 Format (1=Unicode, 2=Conversion to EBCDIC, default)

• A= capture Alias DDL (Y or N)

• S= capture Synonym DDL (Y or N)

• COMPRESS= compress extract file (C, V or N)

• KT_EMEM= key tree in 64 bit memory (E or blank)

• CK_EMEM= chase keys in 64 bit memory (E or blank)

• KT_DEGR= key tree usage degree n (1-9)

• GH= extract IMPLICITLY HIDDEN columns (Y or N)

09 This record type contains Temporal Table Business or System Time information.

• B or S Business Time or System Time

• D Dual (Bi-temporal)

• 1, 2, or 3 Time period: AS OF (1), FROM (2), or BETWEEN (3)

• Y active or N inactive

• Date/Timestamp 1

• Date/Timestamp 2

Table 20 lists the group of record types 52P or 11, 10, 52D or 12, 13, 16, 50S or 21, 50T or 22, 51, 53,
54, 30, 31, and 32 will be present for each relationship being processed, dependent also on the
respective object type.

Table 20. File-AID/RDX Request File Relationship Record Types

Record Type Description
52P This record type contains information about the source object that is related to the object described by
the type 52D record immediately following this type 52P record. The type 52P record identifies the
source object’s object type (D=DB2, M=MVS), File-AID/RDX generated unique object sequence number,
and fully qualified name at the end of the record to accommodate long object names. If the driving
object is a Db2 object, the creator ID of the relationship definition used (model creator ID) is also
included.
374 File-AID/RDX Reference

Table 20. File-AID/RDX Request File Relationship Record Types (Continued)

Record Type Description
53 This record type exists only if record type 52P or 52D is a Db2 object. It follows each Db2 52P or 52D
record to identify the Db2 object’s subsystem, DBMS version, release, modification level, and delimiter
identifier.
52D This record type contains information about the target object that is related to the object described by
the type 52P record immediately preceding this type 52D record. The type 52D record identifies the
target object’s object type (D=DB2, I=KEY, M=MVS), File-AID/RDX generated unique object sequence
number, and fully qualified name at the end of the record to accommodate long object names.
13 This record type contains the individual navigation and sampling controls for each relationship as well
as other extract options.

• DPSI= The status Y, N, or - (not relevant) is given for the Navigation controls DPSI (Direct Path,
Parent Path, Sibling Path, and Indirect Path) for each relationship.

• C= cycle limit for the relationship;

• M= maximum number of records to extract for this relationship;

• D= select n dependents from this parent;

• X= relationship excluded status:

– N relationship not excluded;
– Y1 relationship excluded by user;
– Y2 relationship excluded by line command "A" (All);
– Y3 relationship excluded by object not found;
– Y4 relationship excluded by scope;

• E=YY check extract validation status:

– Y_ (first Y) possible RI violation;
– _Y (second Y) ignore parent missing;

• A or R identifies relationship type:

– A application relationship (AR);
– R Db2 RI;

• The remaining characters identify either the RELNAME (8 bytes) if the relationship is Db2 RI, or the
relationship description for AR.
59C This record type identifies a conditional application relationship (AR-C) and includes the name of the
conditional AR Criteria dataset and parent criteria member name (Pnnnnnnn).
16 This record type contains the relationship’s creation and last modified time, date, and user ID.

A group of record types 50Source and 50Target (old 21 and 22, or 30 to 32) will be present for each
pair of source and target columns in the relationship as listed in Table 21.

Table 21. File-AID/RDX Request File Source and Target Record Types
Record Type Description
50 Source column. This record type contains information about the source object column or field that
participates in a column/field relationship with the target object column/field described by the type
50Target column immediately following the type 51 record for the source column/field. The type
50Source column record identifies the source object’s column/field name, data type, and length.
51 This record type is a continuation record for all type 50 records. The type 51 record identifies the
column/field offset, values for subscripts 1, 2, and 3, the total number of subscripts (0, 1, 2, or 3),
precision, and scale defined for the relationship.
Extract 375

Table 21. File-AID/RDX Request File Source and Target Record Types (Continued)
Record Type Description
50 Target column. This record type contains information about the target object column or field that
participates in a column/field relationship with the source object column/field described by the type
50Source column immediately preceding the type 51 record for the source column/field. The type
50Target column record identifies the target object’s column/field name, data type, and length. It is
always followed by a 51 record type to specify the column/field values for offset and subscripts.
31 This record type contains the relationship description for this KEY relationship.
32 This record type contains the name of the extract Output Key File for this KEY relationship. It also includes
the dataset name containing the JCL for the File-AID for IMS extract if it is to be executed as a step
following the File-AID/RDX extract.
33 This record type contains the Output Key File dataset details.

Load/Delete Request Record Types

A request file could also contain these different load or delete request record types listed in Table 22.

Table 22. File-AID/RDX Load/Delete Request File Record Types

Record Type Description
60n This record type specifies the extract file type for the load in the current request. The third digit n specifies
the file type:
n
1 = Extract file
2 = Extract summary file (tape control file)
3 = Request file
4 = Discard file
61 This record type contains the following global load parameters: 
Db2 load option S=SQL Insert, D=Db2 load utility;
Automatic Space Calculation (MVS only);
Commit interval:
Discard options;
Db2 Lock and Log options;
Image copy;
Repair
Auto create only
62 This record type contains the Target Object Names.
63 This record type contains the source to target Column Mapping information.
64 This record type contains the index auto create information.
65 This record type contains the index detail information.
66 This record type contains the discard file information.
67 This record type contains the partitioned index limitkey value information.
68 This record type contains the Db2 Alias, Synonyms, and View information.
69 This record type contains the Db2 Target Database information.
70 This record type contains the Db2 Target Tablespace information (obsolete, replaced with record type
73).
71 This record type contains the DSATT information for MVS objects.
72 This record type contains the Index detail specifications information for MVS objects.
73 This record type contains the Db2 Target Tablespace information.
376 File-AID/RDX Reference

Obsolete Record Types

An extract criteria file saved with an earlier File-AID/RDX Release than 4.0 could contain the
following record types. When processed with File-AID/RDX Release 17.02 or later, these record types
will be replaced by their corresponding Release 17.02 record types.

Table 23. Obsolete Record Types

Record Type Description
01 This record type contains the value specified in the Maximum rows to select from Driving object
field on the Selection Criteria Specification screen. For multiple selection criteria sets, the set number is
located on the right, for example 001/003 (set# out of total sets).
02 This record type contains the request description.
03 This record type contains the value specified in the Maximum rows from all tables field on the Extract
Scope Screen screen.
08 The Max Cycles record type corresponds to the values specified in the Cycle Control window. It lists the
number of allowed extract cycles and whether orphan records are acceptable (Get Parents of
Orphans:N) or (Get Parents of Orphans:Y).
02 This record type contains the value specified in the Select every nth row from driving table field on
the Selection Criteria screen. This record type exists only in extract criteria files created using File-
AID/RDX version 1.1 and earlier and will be replaced by record type 14 when saving the extract criteria
with a current release of File-AID/RDX.
04 This record type exists only in extract criteria files created using File-AID/RDX version 1.6 and earlier.
When saving the selection criteria with File-AID/RDX version 2.0 and later it will be replaced with type
56 record.

This record type identifies the location, subsystem, creator, and table name associated with the driving
table. In addition, the type 04 record contains the value specified in the Lock Table field on the Selection
Criteria Specification screen.

If you specified a view as the driving table, this record type identifies the location, subsystem, creator,
and view name associated with the view. Record type 44 identifies the location, subsystem, creator, and
the view’s base table name.
05 This record type exists only in extract criteria files created using File-AID/RDX version 1.6 and earlier.
When saving the selection criteria with File-AID/RDX version 2.0 and later it will be replaced with type
56 record.

This record type identifies the location, subsystem, creator, and table name associated with a related
table. In addition, the type 05 record contains the value specified in the Lock Table field on the Selection
Criteria Specification screen. A type 05 record exists for every related table included in the extract.
06 This record type corresponds to the value specified in the Display all relationships field on the Extract
Specification screen in File-AID/RDX versions prior to 3.0.
11 This record type exists only in extract criteria files created using File-AID/RDX version 1.6 and earlier.
When saving the extract criteria with File-AID/RDX version 2.0 and later it will be replaced with type 52P
and 53 records.

This record type contains information about the source table that is related to the table described by the
type 10 or 12 record immediately following this type 11 record. The type 11 record identifies the source
table’s location; subsystem; creator; table name; and DBMS version, release, and modification level.
10 This record type exists only in extract criteria files created using File-AID/RDX version 1.6 and earlier.
When saving the extract criteria with the File-AID/RDX version 2.0 and later it will be replaced with type
52D records.

This record type identifies the target IMS database (DBDLIB) and the target member that is related to
the table described by the type 11 record immediately preceding this type 10 record.
12 This record type exists only in extract criteria files created using File-AID/RDX version 1.6 and earlier.
When saving the extract criteria with File-AID/RDX version 2.0 and later it will be replaced with type 52D
and 53 records.
Extract 377

Table 23. Obsolete Record Types (Continued)

Record Type Description
21 This record type exists only in extract criteria files created using File-AID/RDX version 1.6 and earlier.
When saving the extract criteria with File-AID/RDX version 2.0 and later it will be replaced with type
50Source Column records.

This record type contains information about the source table column that participates in a column
relationship with the target table column described by the type 22 record immediately following this
type 21 record. The type 21 record identifies the source table column’s name, data type, length, and
offset, if any.
22 This record type exists only in extract criteria files created using File-AID/RDX version 1.6 and earlier.
When saving the extract criteria with File-AID/RDX version 2.0 and later it will be replaced with type
50Target Column records.

This record type contains information about the target table column that participates in a column
relationship with the source table column described by the type 21 record immediately preceding this
type 22 record. The type 22 record identifies the target table column’s name, data type, length, and
offset, if any.
30 This record type exists only in extract criteria files created using File-AID/RDX version 1.6 and earlier.
When saving the extract criteria with File-AID/RDX version 2.0 and later it will be replaced with type
50Target Column records.

This record type contains information about the IMS target root segment that participates in a column
relationship with the source table column described by the type 21 record immediately preceding this
type 30 record. The type 30 record identifies the IMS target root segment’s name, data type, length, and
offset, if any.

File-AID/RDX Extract File

During the extract process, File-AID/RDX writes all extracted data to the extract file. This is the file
that File-AID/RDX uses in the load process to load all or only selected data.

In order to increase data security the File-AID/RDX extract file no longer includes DDL statements in
readable form. The Db2 source environment information is now captured in a masked format.

The extract file has the following characteristics:

File organization
Partitioned (DSORG=PO) or sequential (DSORG=PS)

Record format
Variable-blocked (RECFM=VB)

Logical record length

Maximum LRECL determined by File-AID/RDX (default = 27994)

File-AID/RDX will dynamically reallocate a sequential extract file to adjust

to the needed space. Dynamic reallocation is only available for sequential
files (DSORG=PS).

The first four bytes at the beginning of each record indicate the record’s type and the corresponding
header record.
378 File-AID/RDX Reference

After a successful extract is performed, the extract file contains the following types of records:

• product record 0; • relationship records R;

• header record H; • data records D;
• Db2 create records C; • Db2 XML/LOB data records x;
• MVS file create records E; • order records O;
• map records M; • trailer records T.

Product Record — 0
The product record indicates the release of File-AID/RDX used to create the file. This is always the
first record in the file. It also includes the DBMS type and version, Db2 image copy, sort, and
compress indicators (C = compress all data, V = compress only Db2 variable column data, or blank =
no compression), date format, data status (E = Encrypted (Masked), D = Disguised), as well as the
Autocreate disabled?, D record supplement indicators, Db2 extract format Unicode or Conversion,
and extract IMPLICITLY HIDDEN columns indicator. The format of the product record is shown in
Figure 195 on page 378.

Figure 195. Product Record Layout

01 PRODUCT-RECORD.
05 RCD-TYPE PIC X(1) VALUE '0'.
05 RCD-TYPE-NO PIC X(3) VALUE '000'.
05 PROD-LIT PIC X(13) VALUE 'File-AID/RDX'.
05 VERSION PIC X(2) VALUE '04'.
05 PERIOD1 PIC X(1) VALUE '.'.
05 RELEASE PIC X(2) VALUE '07'.
05 PERIOD2 PIC X(1) VALUE '.'.
05 MOD PIC X(2) VALUE '00'.
05 PERIOD3 PIC X(1) VALUE '.'.
05 SUBRELEASE PIC X(2) VALUE '00'.
05 FILLER PIC X(1).
05 TIMESTAMP PIC X(26).
05 DEC_IND PIC X(1).
05 FILLER PIC X(1).
05 DBMS-TYPE PIC X(8).
05 DBMS-VERSION PIC X(8).
05 FILLER PIC X(1).
05 IMAGE-COPY PIC X(1) VALUE_’Y’_or’N’
05 SORT_IND PIC X(1) VALUE_’Y’_or’N’
05 COMPRESS-IND PIC X(1) VALUE_’C’ or’V’
05 DATE_FORMAT PIC X(4)_VALUE_’ISO’,‘USA’,’JIS’,’LOC’,’EUR’, or ‘ISOM’
05 DATA_STATUS PIC X(1) VALUE_’E’ or’D’
05 AUTOC_DISABL PIC X(1) VALUE_’Y’
05 D_REC_SUPPLM PIC X(1) VALUE_’Y’_or’N’
05 DB2_FORMAT PIC X(1) VALUE_’1’_or’2’
05 GET_HIDDEN PIC X(1) VALUE_’Y’_or’N’

Header Record — H
A header record will be present for each object included in the extract process. The format of the
header record is shown in Figure 196.
Extract 379

Figure 196. Header Record Layout

01 HEADER-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'H'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 SUBSYS PIC X(4).
05 OBJECT_TYP PIC X(1).
05 OBJECT_NAME PIC X(52).
10 LOCATION PIC X(16).
10 CREATOR PIC X(8).
10 TBNAME PIC X(18).
10 FILLER PIC X(10).
05 RI-DEP-IND PIC X(1).
05 FILLER PIC X(1).
05 BPOOL PIC X(9).
05 FILLER PIC X(2).
05 SUPPL_SW PIC X(1)
05 CCSID PIC X(5)
05 OBJECT_NAME_LONG PIC X(272).
10 LOCATION PIC X(16).
10 CREATOR PIC X(128).
10 TBNAME PIC X(128).
05 ORIG_OBJ_NAME PIC X(272).
10 LOCATION PIC X(16).
10 CREATOR PIC X(128).
10 TBNAME PIC X(128).

The following is an explanation of the fields contained in the header layout:

RCD-TYPE
A value of ’H’ will be present in this field. The value ’H’ indicates that this is a header record.

RCD-TYPE-NO
A three-digit alphanumeric ID that identifies the record in the file. This field is referenced by
create records and data records that contain the same three-digit alphanumeric ID in the RCD-
TYPE-NO field.

SUBSYS
The Db2 subsystem on which the table name identified in the CREATOR and TBNAME field
exists. Blank for MVS objects.

OBJECT_TYPE
Identifies the object type: D = DB2, M = MVS.

OBJECT_NAME
Identifies the object name. If object type is M the full MVS file name is listed. If object type is D
the location, creator and table names are listed instead:

LOCATION The location at which the Db2 table name identified in the CREATOR and
TBNAME fields exists.
CREATOR The authorization ID of the owner of the table in the TBNAME field (blank,
if Db2 long object name).
TBNAME The name of the table to which this header record corresponds (blank, if
Db2 long object name).
380 File-AID/RDX Reference

RI-DEP-IND
A value of 'Y' indicates that the Db2 table identified by the CREATOR and TBNAME fields is a
dependent in a Db2 RI relationship.

BPOOL
Buffer pool where creator.tbname resides. Only used when table contains either LVCHAR or
LVGRPH columns.

SUPPL_SW
If the D record supplement indicator is set to Y, the D record also includes a record number that
ensures that data extracted from an MVS file without an index but with an XREF, will be loaded
to the target in the sequence in which they were read.

CCSID
Identifies the CCSID for an MVS object.

OBJECT_NAME_LONG
Identifies the object name; if object type is M the full MVS file name is listed; if object type is D
the location, creator and table names are listed instead:

LOCATION The location at which the Db2 table name identified in the CREATOR and
TBNAME fields exists.
CREATOR The authorization ID of the owner of the table in the TBNAME field.
TBNAME The name of the table to which this header record corresponds.

ORIG_OBJ_NAME
Identifies the original object name if the extract request has been cloned. If object type is M the
full MVS file name is listed; if object type is D the location, creator and table names are listed
instead:

LOCATION The location at which the Db2 table name identified in the CREATOR and
TBNAME fields exists.
CREATOR The authorization ID of the owner of the table in the TBNAME field.
TBNAME The name of the table to which this header record corresponds.

Base Table Record — B

(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
A base table record will be present for each Db2 view included in the extract process. Each base table
record will share a record-type number with a header record. Together, the header and base table
records provide information about the view and its base table. The format of the base table record is
shown in Figure 197.
Extract 381

Figure 197. Base Table Record Layout

01 BASE-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'B'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 SUBSYS PIC X(4).
05 LOCATION PIC X(16).
05 CREATOR PIC X(8).
05 TBNAME PIC X(18).
05 RI-DEP-IND PIC X(1).
05 FILLER PIC X(1).
05 BPOOL PIC X(9).

The following is an explanation of the fields contained in the base table record layout:

RCD-TYPE
A value of ’B’ will be present in this field. The value ’B’ indicates that this is a base table record.

RCD-TYPE-NO
A three-digit number that identifies the record in the file. This field is referenced by create
records and data records that contain the same three-digit number in the RCD-TYPE-NO field.

SUBSYS
The Db2 subsystem on which the table name identified in the CREATOR and TBNAME field
exists.

LOCATION
The location at which the table name identified in the CREATOR and TBNAME fields exists.

CREATOR
The authorization ID of the owner of the table in the TBNAME field.

TBNAME
The name of the table to which this base table record corresponds.

RI-DEP-IND
A value of ’Y’ indicates that the table identified by the CREATOR and TBNAME fields is a
dependent in a Db2 RI relationship.

BPOOL
Buffer pool where creator.tbname resides. Only used when table contains either LVCHAR or
LVGRPH columns.
382 File-AID/RDX Reference

Database Create Record — F

(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The database create record is generated when your extract includes Db2 objects. It contains Db2 DDL
statements related to the extracted Db2 objects. The format of the create record is shown in Figure
198.

Figure 198. Database Create Record Layout

01 CREATE-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'F'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 CREATE-TEXT PIC X(76).

The following is an explanation of the fields contained in the database create record layout:

RCD-TYPE
A value of 'F' will be present in this field. The value 'F' indicates that this is a database create
record.

RCD-TYPE-NO
A three-digit sequence number that keeps track of the number of databases in the extract. For
example, a value of '002' indicates it is the second database in the extract.

CREATE-TEXT
Contains the Db2 DDL required to create or alter databases.

Tablespace Create Record — G

(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The tablespace create record is generated when your extract includes Db2 objects. It contains Db2
DDL statements captured during extract processing to create and alter tablespaces that File-AID/RDX
uses to generate load JCL. The format of the create record is shown in Figure 199.

Figure 199. Tablespace Create Record Layout

01 CREATE-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'G'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 CREATE-TEXT PIC X(76).

The following is an explanation of the fields contained in the tablespace create record layout:

RCD-TYPE
A value of 'G' will be present in this field. The value 'G' indicates that this is a tablespace create
record.
Extract 383

RCD-TYPE-NO
A three-digit sequence number that keeps track of the number of tablespaces in the extract. For
example, a value of '002' indicates it is the second tablespace in the extract.

CREATE-TEXT
Contains the Db2 DDL required to create or alter tablespaces.

Db2 Source Environment Record — C

The Db2 Source Environment record is generated when you extract records from a Db2 object. It
contains Db2 catalog information captured during extract processing to create and alter Db2 objects
that File-AID/RDX uses to generate load JCL. The format of the Db2 Source Environment record is
shown in Figure 200.

In order to increase data security the File-AID/RDX extract file no longer includes DDL statements in
readable form. The Db2 source environment information is now captured in a masked format.

Figure 200. Db2 Source Environment Record Layout

01 CREATE-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'C'.
05 RCD-TYPE-NO PIC X(3) VALUE '001'.
05 CREATE-ATTR BIN X(..).

The following is an explanation of the fields contained in the Db2 Source Environment record layout:

RCD-TYPE
A value of 'C' will be present in this field. The value 'C' indicates that this is a Db2 Source
Environment record.

RCD-TYPE-NO
A value of '001' will be present in this field. The value '001' indicates that this is a Db2 Source
Environment record.

CREATE-ATTR
Contains the Db2 Source Environment information for the extracted Db2 object in a masked
format.

MVS File Create Record — E

The MVS File create record is generated for each extracted MVS object. It contains file allocation and
filed mapping information captured during extract processing to create and alter objects that File-
AID/RDX uses during the load process to support autocreate. The format of the MVS file create record
is shown in Figure 201.
384 File-AID/RDX Reference

Figure 201. MVS File Create Record Layout

01 CREATE-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'E'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 CREATE-ATTR BIN X(..).

The following is an explanation of the fields contained in the MVS file create record layout:

RCD-TYPE
A value of 'E' will be present in this field. The value 'E' indicates that this is a MVS file create
record.

RCD-TYPE-NO
A three-digit alphanumeric ID that corresponds to the header record number indicating the
object to which this record corresponds. For example, if a value of '002' is present, look at record
type 'H002' to determine the object to which this record corresponds.

CREATE-ATTR
Contains the binary records for allocation information for the file, alternate indexes information,
path definitions, and map data. All data is related to the object identified in the corresponding
'Hnnn' record.

View Create Record — V

(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The view create record is generated when you specify YES in the Views field in the Extract File
Specification Screen (Figure 176 on page 338) to capture all create view DDL related to the extracted
Db2 objects. The format of the create record is shown in Figure 202.

Figure 202. View Create Record Layout

01 CREATE-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'V'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 CREATE-TEXT PIC X(76).

The following is an explanation of the fields contained in the view create record layout:

RCD-TYPE
A value of 'V' will be present in this field. The value 'V' indicates that this is a view create record.

RCD-TYPE-NO
A three-digit alphanumeric that corresponds to the header record number indicating the view to
which this record corresponds. For example, if a value of '002' is present, look at record type
'H002' to determine the view to which this record corresponds.
Extract 385

CREATE-TEXT
Contains the Db2 DDL required to create views. All DDL is related to the view identified in the
corresponding 'Hnnn' record.

Alias Create Record — A

(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The alias create record is generated when you specify YES in the Alias field in the Extract File
Specification Screen (Figure 176 on page 338) to capture all create alias DDL related to the extracted
Db2 objects. The format of the create record is shown in Figure 203.

Figure 203. Alias Create Record Layout

01 CREATE-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'A'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 CREATE-TEXT PIC X(76).

The following is an explanation of the fields contained in the alias create record layout:

RCD-TYPE
A value of 'A' will be present in this field. The value 'A' indicates that this is a alias create record.

RCD-TYPE-NO
A three-digit sequence number that keeps track of the number of aliases in the extract. For
example, a value of '002' indicates it is the second alias in the extract.

CREATE-TEXT
Contains the Db2 DDL required to create or alter aliases.

Synonym Create Record — S

(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The create record is generated when you specify YES in the Synonyms field in the Extract File
Specification Screen (Figure 176 on page 338) to capture all create synonym DDL related to the
extracted Db2 objects. The format of the create record is shown in Figure 204.

Figure 204. Synonym Create Record Layout

01 CREATE-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'S'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 CREATE-TEXT PIC X(76).

The following is an explanation of the fields contained in the synonym create record layout:

RCD-TYPE
A value of 'S' will be present in this field. The value 'S' indicates that this is a synonym create
record.
386 File-AID/RDX Reference

RCD-TYPE-NO
A three-digit sequence number that keeps track of the number of synonyms in the extract. For
example, a value of '002' indicates it is the second synonym in the extract.

CREATE-TEXT
Contains the Db2 DDL required to create or alter synonyms. All DDL is related to the table
identified in the corresponding ’Hnnn’ record.

Map Record — M
(Obsolete - only applies to extracts created with File-AID/RDX Release 2.5.1 or earlier.) The map
record is only generated when you specify NO in the Capture Table and Index DDL for the LOAD
Auto Create feature field in the LOAD Related Processing Options pop-up window. The map record is
similar to the create record except that the map record is only used during load processing for
column mapping. The format of the map record is shown in Figure 205 on page 386.

Figure 205. Map Record Layout

01 MAP-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'M'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 MAP-TEXT PIC X(76).

The following is an explanation of the fields contained in the map record layout:

RCD-TYPE
A value of 'M' will be present in this field. The value 'M' indicates that this is a map record.

RCD-TYPE-NO
A three-digit number that corresponds to the header record number indicating to which table
this record corresponds. For example, if a value of '002' is present, look at record type 'H002' to
determine to which table this record corresponds.

MAP-TEXT
Contains the Db2 DDL used during load processing for column mapping. All DDL is related to
the table identified in the corresponding 'Hnnn' record.

Relationship Record — R
The relationship record is generated when your extract includes related objects. It contains the
relationship information for the related objects when the extract was created. File-AID/RDX uses this
information when disguising the extract using the File-AID Data Privacy plugin of the Topaz
Workbench. The format of the relationship record is shown in Figure 206.

In order to increase data security of the File-AID/RDX extract file the relationship information is not
in readable form.
Extract 387

Figure 206. Relationship Record Layout

01 RELATIONSHIP-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'R'.
05 RCD-TYPE-NO PIC X(3) VALUE '001'.
05 CREATE-ATTR BIN X(..).

The following is an explanation of the fields contained in the relationship record layout:

RCD-TYPE
A value of 'R' will be present in this field. The value 'R' indicates that this is a relationship record.

RCD-TYPE-NO
A value of '001' will be present in this field. The value '001' indicates that this is a relationship
record.

CREATE-ATTR
Contains the relationship information for the extracted Db2 objects in a masked format.

Data Record — D
The data record contains the actual data extracted from Db2 and MVS objects. The format of the data
record is shown in Figure 207.

Figure 207. Data Record Layout

01 DATA-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'D'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 ROW-DATA PIC X.

The following is an explanation of the fields contained in the data record layout:

RCD-TYPE
A value of 'D' will be present in this field. The value 'D' indicates that this is a data record.

RCD-TYPE-NO
A three-digit alphanumeric that corresponds to the header record number, indicating the table
from which this record was extracted. For example, if a value of '002' was present, look at record
type 'H002' to determine the table from which this record was extracted.

ROW-DATA
Contains the contents of the row. The length of this field depends on the length of the row. Data
records are in compressed form if the extract file was created with the compression option (see
also Compress on page 339).
388 File-AID/RDX Reference

If the D record supplement indicator in the product record (see Product Record — 0 on page 378)
is set to Y, the D record also includes a record number that ensures that data extracted from an
MVS file without an index but with an XREF, will be loaded to the target in the sequence in
which they were read.

XML/LOB Data Record — x

The XML/LOB data record contains the actual XML or LOB data extracted from Db2 objects. The
format of the XML/LOB data record is shown in Figure 208.

Figure 208. XML/LOB Data Record Layout

01 DATA-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'x'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 ROW-DATA PIC X.

The following is an explanation of the fields contained in the XML/LOB data record layout:

RCD-TYPE
A value of 'x' will be present in this field. The value 'x' indicates that this is a XML or LOB data
record.

RCD-TYPE-NO
A three-digit alphanumeric ID that corresponds to the header record number, indicating the table
from which this record was extracted. For example, if a value of '002' was present, look at record
type 'H002' to determine the table from which this record was extracted.

ROW-DATA
Contains the contents of the row. The length of this field depends on the length of the row.
XML/LOB data records are in a masked format to provide data security.

Order Record — O
The order records are used to record the order in which objects were extracted. The format of the data
record is shown in Figure 209.

Figure 209. Order Record Layout

01 ORDER-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'O'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 NBR_ENTS PIC S9(9) COMP.

The following is an explanation of the fields contained in the order record layout:

RCD-TYPE
A value of 'O' will be present in this field. The value 'O' indicates that this is an order record.
Extract 389

RCD-TYPE-NO
A three-digit alphanumeric that corresponds to the header record number, indicating the table
from which this record was extracted. For example, if a value of '002' was present, look at record
type 'H002' to determine the object from which this record was extracted.

NBR_ENTS
The first ‘O’ record and the last ‘O’ record identify the total number of ‘O’ records in this extract
in binary.

Trailer Record — T
A trailer record will be present for each header record in the extract. The format of the trailer record is
shown in Figure 210.

Figure 210. Trailer Record Layout

01 TRAILER-RECORD.
05 RCD-TYPE PIC X(1) VALUE 'T'.
05 RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
05 SUBSYSTEM PIC X(4).
05 OBJECT_NAME PIC X(52).
10 LOCATION PIC X(16).
10 CREATOR PIC X(8).
10 TABLE-NAME PIC X(18).
10 FILLER PIC X(10).
05 ROW-COUNT PIC X(8).
05 OBJECT_TYP PIC X(1).
05 RCD_LENGTH PIC X(8). 
05 NUM_PARTITIONS PIC X(1) VALUE 'Y'.
05 PARTKEYCOLNUM PIC X(1) VALUE 'Y'.
05 SECURITY_LABEL PIC X(1) VALUE 'Y'.
05 SPLIT_ROWS PIC X(1) VALUE 'Y'.
05 FILLER PIC X(9).
05 OBJNAME_DB2V8 PIC X(272).
10 LOCATION PIC X(16).
10 CREATOR PIC X(128).
10 TABLE-NAME PIC X(128).
05 XML_TOT PIC S9(09) COMP-5.
05 XML_MAX PIC S9(09) COMP-5.

The following is an explanation of the fields contained in the trailer record layout:

RCD-TYPE
A value of 'T' will be present. The value 'T' indicates that this is a trailer record.

RCD-TYPE-NO
A three-digit alphanumeric that corresponds to the header record number, indicating the object
to which this record refers. For example, if a value of '002' was present, look at record type 'H002'
to determine the object to which this record refers.

SUBSYSTEM
The Db2 subsystem in which the object corresponding to this record exists. Blank for MVS
objects.
390 File-AID/RDX Reference

OBJECT_NAME
Identifies the object name; if object type is M the full MVS file name is listed; if object type is D
the location, creator and table names are listed instead:

LOCATION The location at which the table corresponding to this record exists.
CREATOR The authorization ID of the owner of the table corresponding to this
record (blank, if Db2 long object name).
TABLE-NAME The name of the table to which this record corresponds (blank, if Db2
long object name).
FILLER Filler.

ROW-COUNT
The number of rows extracted from the table that corresponds to this record.

OBJECT_TYPE
Identifies the object type: D = DB2, M = MVS.

RCD_LENGTH
The maximum record length extracted from the object that corresponds to this record.

OBJ_SIZE
The number of bytes (Kilobytes?) per object extracted from the object that corresponds to this
record.

NUM_PARTITIONS
If the number of tablespace partitions is greater than 254, this indicator is set to Y (Autocreate
disabled).

PARTKEYCOLNUM
If table controlled partitioning is used, this indicator is set to Y (Autocreate disabled).

SECURITY_LABEL
If the security_label is R, this indicator is set to Y (Autocreate disabled).

SPLIT_ROWS
If split rows is enabled, this indicator is set to Y (Autocreate disabled).
Extract 391

OBJNAME_DB2V8
Identifies the object name in its full length; if object type is M the full MVS file name is listed; if
object type is D the location, creator and table names are listed instead:

LOCATION The location at which the table corresponding to this record exists.
CREATOR The authorization ID of the owner of the table corresponding to this
record (up to 128 characters).
TABLE-NAME The name of the table to which this record corresponds (up to 128
characters).

XML_TOT
Total length in Kilobytes (in binary format) of all XML or LOB columns for the table that
corresponds to this record.

XML_MAX
Maximum size in Kilobytes (in binary format) of an XML or LOB value for the table that
corresponds to this record.

Work files
During an extract, File-AID/RDX creates some work files that it deletes after extract execution.

The work files have the following format::

userid.prefix.*.Dnnnnnn.Tnnnnnn.suffix

Where prefix is set by the profile variable File Prefix (see File Prefix on page 81), and * is either
EXTCRIT or PARMS, and suffix is set by the profile variable File Suffix (see File Suffix on page 81).

Periodically, you may want to manually delete any left-over work files from incomplete extracts that
are no longer needed.

Record Layout and File-AID/MVS XREF JCL

The JCL shown in Figure 211 is added to the extract JCL (see Extract JCL on page 365) when you
specify for File-AID/RDX to create a record layout file or a record layout file and a File-AID/MVS XREF
(record layout cross reference) file in Extract File Specification Screen on page 338.

Figure 211. Record Layout JCL

//EXFLC EXEC PGM=XFREXEC,REGION=8192K,MEMLIMIT=4G,

// PARM=(FR,N,B)
//STEPLIB DD DSN=Combined-File-AID/RDX-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID/RDX-message-library,DISP=SHR
//EXTPARMS DD DSN=extract-parms-file,DISP=SHR
//EXTRACT DD DSN=extract-to-file-name,
// DISP=old or new or SHR
//CLAYOUT DD DSN=record-layout-file-name,
// DISP=old or new or SHR
//XREF001 DD DSN=XREF-file-name,
// DISP=old or new or SHR
//*
//SYSOUT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*) 

XFREXEC is the File-AID/RDX program name.

392 File-AID/RDX Reference

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 16:

Table 24. EXEC Statement PARM Field—Extract Step

Parameter Default Value Length Description
Product FR 2 File-AID/RDX
Option N 1 File-AID/RDX option number.
B
Operating Mode B 1
Batch

The following DD statements are required for record layout:

Table 25. DD Statements—Record Layout

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD)
RDXMLIB File-AID/RDX message library
EXTPARMS File containing the extract parameters (see EXTPARMS File on page 367).
EXTRACT File to which extracted data is written.
CLAYOUT 
PLAYOUT File to which COBOL, PL/I, or FA COBOL record layout is written.
FLAYOUT
XREF001 File to which the record layout cross reference (XREF) for the extract file is written.
SYSOUT Output class.
SYSTERM Output class for runtime errors.
SYSPRINT Standard output stream.

Return Codes
An execution return code (RC) appears in the output listing. For return codes other than 0, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return Code Description

0 Job ran to completion.
4 Job ran to completion, warnings issued.
8 Job completed with error.
16 Severe error, job aborted.

File-AID/RDX Record Layout File

During the record layout generation process, File-AID/RDX writes to the record layout file.

The record layout file has the following characteristics:

File organization
Partitioned (DSORG=PO) or sequential (DSORG=PS)

Record format
Fixed-blocked (RECFM=FB)
Extract 393

Logical record length

80

If you specify a new file (DISP=NEW), the file organization can be sequential or partitioned.

The record layout file includes the layout for all extracted objects, either in COBOL, PL/I, or FA
COBOL format.

1. When you ask File-AID/RDX to create only a record layout (Create XREF = NO) for MVS
objects, the resulting layout is only for the complete extracted record, not the fields
within the record (see layout for object FARDX.SAMP.OBJA.KSDS shown in Figure 215 on
page 396).
2. When the record layout is requested together with an XREF for the extract file, record
layouts are only created for all Db2 objects. For MVS objects, the XREF points to the
source layout, the one used when the relationship was defined. The XREF assumes that
it is the layout file specified with the Create Record Layout function (see MVS File Create
Record — E on page 383). Also, the generated record layout includes a default layout for
all non-data records (see Figure 213 on page 394 and Figure 215 on page 396).

Sample COBOL Record Layout

Figure 212 shows a sample COBOL record layout. It identifies each object by its name and lists null
indicators and column/field names with column/field type and length. When you requested to only
create a record layout (Create XREF=NO), the layout includes the extract record ID (Dnnn).

Figure 212. Sample COBOL Record Layout (Create XREF=NO)

****************************************************************
* COBOL RECORD LAYOUT FOR FRSAMP ORDER_TABLE *
******************************************************************
01 FRSAMP-ORDER-TABLE. 
05 RECORD-ID-D002 PIC X(4).
05 NULL-INDICATORS. 
10 ORD-STAT PIC S9(4) COMP. 
10 ORD-AMOUNT PIC S9(4) COMP. 
10 ORD-DEPOSIT PIC S9(4) COMP. 
10 SHIP-CODE PIC S9(4) COMP. 
10 SHIP-DATE PIC S9(4) COMP. 
10 ORD-DESCRIPTION PIC S9(4) COMP. 
05 COBOL-ORDER-TABLE. 
10 ORDER-NUMBER PIC X(6). 
10 CUST-NUM PIC X(6). 
10 SOC-SEC-NUM PIC X(11). 
10 CREDIT-CARD-NUM PIC X(16). 
10 ORD-TYPE PIC X(8). 
10 ORD-DATE PIC X(10). 
10 ORD-STAT PIC X(8). 
10 ORD-AMOUNT PIC S9(7)V9(2) COMP-3. 
10 ORD-DEPOSIT PIC S9(7)V9(2) COMP-3. 
10 ORD-LINE-COUNT PIC S9(9) COMP.
10 SHIP-CODE PIC X(2). 
10 SHIP-DATE PIC X(10). 
10 ORD-DESCRIPTION. 
49 LENGTH PIC S9(4) COMP.
49 TEXT PIC X(100). 

Sample PL/I Record Layout

Figure 213 shows a sample PL/I record layout. It identifies each object by its name and lists null
indicators and column/field names with column/field type and length. When you requested to create
394 File-AID/RDX Reference

a record layout and XREF (Create XREF=YES), the layout file includes a default layout for all non-data
records.

Figure 213. Sample PL/I Record Layout (created with XREF=YES)

/******************************************************************/
/* PLI RECORD LAYOUT FOR TABLE TSOID01 CUSTOMER_TABLE */
/******************************************************************/
DCL 1 TSOID01_CUSTOMER_TABLE UNALIGNED,
5 NULL_INDICATORS UNALIGNED,
10 CONTACT_TITLE_NULL BIN FIXED(15),
10 CONTACT_ADDR_NULL BIN FIXED(15),
10 CONTACT_CITY_NULL BIN FIXED(15),
10 CONTACT_STATE_NULL BIN FIXED(15),
10 CONTACT_ZIP_NULL BIN FIXED(15),
10 CONTACT_COUNTRY_NULL BIN FIXED(15),
10 CONTACT_AREA_CD_NULL BIN FIXED(15),
10 CONTACT_TELEPHONE_NULL BIN FIXED(15),
5 PLI_CUSTOMER_TABLE UNALIGNED,
10 CUSTOMER_NUMBER CHAR(6),
10 COMPANY_NAME CHAR(30),
10 ADDRESS CHAR(30),
10 CITY CHAR(25),
10 STATE CHAR(2),
10 ZIP_CODE CHAR(9),
10 COUNTRY CHAR(20),
10 AREA_CODE CHAR(3),
10 TELEPHONE_NUM CHAR(7),
10 CONTACT_NAME CHAR(30),
10 CONTACT_TITLE CHAR(30),
10 CONTACT_ADDR CHAR(30),
10 CONTACT_CITY CHAR(25),
10 CONTACT_STATE CHAR(2),
10 CONTACT_ZIP CHAR(9),
10 CONTACT_COUNTRY CHAR(10),
10 CONTACT_AREA_CD CHAR(3),
10 CONTACT_TELEPHONE CHAR(7);
/********************************************************************/
/* PLI RECORD LAYOUT FOR */
/* OBJECT: NON-DATA-RECORDS */
/* LAYOUT DSN: NOT.APPLICABLE */
/* LAYOUT MEMBER: DEFAULT */
/* 01 LEVEL NAME: OBJECT_DFLT */
/********************************************************************/
DCL 1 OBJECT_DFLT,
5 RECORD_ID_DFLT_DATA CHAR(27958);

Sample FA COBOL Record Layout

Figure 214 on page 395 shows a sample FA COBOL record layout. It identifies each object by its name
and lists null indicators and column/field names with column/field type and length. When you
requested to only create a record layout (Create XREF=NO), the layout includes the extract record ID
(Dnnn).

FA COBOL creates a File-AID COBOL layout with special type VAR for Db2 column type VCHAR or
VC, for example when the ORD-DESCRIPTION column is defined to Db2 as VARCHAR(100), with FA
COBOL it will be generated as 
10 ORD-DESCRIPTION PIC X(100) VAR . Use FA COBOL layout format when you need to define
disguise criteria for Db2 tables with column type VCHAR or VC.
Extract 395

Figure 214. Sample FA COBOL Record Layout (Create XREF=NO)

****************************************************************
* COBOL RECORD LAYOUT FOR FRSAMP ORDER_TABLE *
******************************************************************
01 FRSAMP-ORDER-TABLE. 
05 RECORD-ID-D002 PIC X(4).
05 NULL-INDICATORS. 
10 ORD-STAT PIC S9(4) COMP. 
10 ORD-AMOUNT PIC S9(4) COMP. 
10 ORD-DEPOSIT PIC S9(4) COMP. 
10 SHIP-CODE PIC S9(4) COMP. 
10 SHIP-DATE PIC S9(4) COMP. 
10 ORD-DESCRIPTION PIC S9(4) COMP. 
05 COBOL-ORDER-TABLE. 
10 ORDER-NUMBER PIC X(6). 
10 CUST-NUM PIC X(6). 
10 SOC-SEC-NUM PIC X(11). 
10 CREDIT-CARD-NUM PIC X(16). 
10 ORD-TYPE PIC X(8). 
10 ORD-DATE PIC X(10). 
10 ORD-STAT PIC X(8). 
10 ORD-AMOUNT PIC S9(7)V9(2) COMP-3. 
10 ORD-DEPOSIT PIC S9(7)V9(2) COMP-3. 
10 ORD-LINE-COUNT PIC S9(9) COMP.
10 SHIP-CODE PIC X(2). 
10 SHIP-DATE PIC X(10). 
10 ORD-DESCRIPTION PIC X(100) VAR.

File-AID/MVS XREF File

During the XREF generation process, File-AID/RDX writes to the record layout cross reference
information for the extract file into the specified File-AID/MVS XREF file.

The XREF file has the following characteristics:

File organization
Partitioned (DSORG=PO)

Record format
Variable-blocked (RECFM=VB)

Logical record length

300

The XREF file includes the record layout cross reference information for all extracted objects.

Sample XREF for Extract File

Figure 215 on page 396 shows a sample XREF output. It identifies the record layout cross references
for the extracted data records in the extract file.
396 File-AID/RDX Reference

Figure 215. Sample XREF for Db2 and MVS objects

/*
/* CAUTION: If manually editing this member, STATS must be OFF
/* when saving it. Statistics will overlay information in the
/* directory entry needed by File-AID when loading Selection
/* Criteria and XREFs, rendering the member unusable.
/*
/* COMPUWARE assumes no liability for results of using members
/* that have been edited manually.
/*
DEFINEBLOCKS=XREF, 

DESCRIPTION ="FILE-AID/RDX GENERATED XREF", 

LAYOUT_DSNAME=TSOID01.LAYOUT.PLI,
LAYOUT_FILLER=4 

SELECT SET=1,LAYOUT=FRSAMP_CUSTOMER_TABLE,
LAYOUT_MBRNAME=PLIXREF,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D007 

SELECT SET=1,LAYOUT=FRSAMP_CONTACT_TABLE,
LAYOUT_MBRNAME=PLIXREF,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D008 

SELECT SET=1,LAYOUT=PROD001_PART_TABLE,
LAYOUT_MBRNAME=PARTTABL,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D001 

SELECT SET=1,LAYOUT=PROD001_SUPPLIER_TABLE,
LAYOUT_MBRNAME=SUPPLIER,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D002 

SELECT SET=1,LAYOUT=PROD001_CUSTOMER_TABLE,
LAYOUT_MBRNAME=CUSTOMER,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D003 

SELECT SET=1,LAYOUT=PROD001_ORDER_TABLE,
LAYOUT_MBRNAME=ORDERTAB,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D004 

SELECT SET=1,LAYOUT=PROD001_ORDER_LINE_TABLE,
LAYOUT_MBRNAME=ORDERLIN,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D005 

SELECT SET=1,LAYOUT=PROD001_CONTACT_TABLE,
LAYOUT_MBRNAME=CONTACTT,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D006 

SELECT SET=1,LAYOUT=OBJECT_DFLT,
LAYOUT_MBRNAME=PLIXREF,
LAYOUT_TYPE=DEFAULT 
Extract 397

Topaz Extract Visualizer File

When Create the Topaz Extract Visualizer file is set to Y (see Specify Topaz Extract Visualizer File on
page 345) for an extract request, File-AID/RDX captures statistics (TPT trace) during extract job
execution and saves them to the specified file along with the extract request information.

The Topaz Extract Visualizer file has the following characteristics:

File organization
Partitioned (DSORG=PO) or sequential (DSORG=PS)

Record format
Variable-blocked (RECFM=VBA)

Logical record length

27962

The Data Visualizer component of the Topaz Workbench can use this file to produce a graphical
display with detailed information about extract processing.

Checkpoint Data File

When Enable Checkpoint/Resumption is set to Y (see Checkpoint/Resumption on page 347) for an
extract request, File-AID/RDX captures the File-AID/RDX internal control blocks, chase keys, key
trees, etc., that are required for resumption of the extract at a later point in the Checkpoint Data file.

The Checkpoint Data file has the following characteristics:

File organization
Partitioned (DSORG=PO) or sequential (DSORG=PS)

Record format
Variable-blocked (RECFM=VB)

Logical record length

27962

Checkpoint Control File

When Enable Checkpoint/Resumption is set to Y (see Checkpoint/Resumption on page 347) for an
extract request and Checkpoint Control options are specified, File-AID/RDX stores the Checkpoint
Control options in the Checkpoint Control file.

The Checkpoint Control file has the following characteristics:

398 File-AID/RDX Reference

File organization
Partitioned (DSORG=PO) or sequential (DSORG=PS)

Record format
Variable-blocked (RECFM=VB)

Logical record length

300
Extract 399

Extract Reports
After the extract job is submitted and executed, an extract report is printed. This report consists of
the following parts:

• Extract Progress Report

• Relationship Navigation and Sampling Report
• Relationship Navigation and Sampling Excluded Object Report
• Object Sampling and Selection Criteria Report
• Object Sampling and Selection Criteria Excluded Object Report
• Extract Summary Report
• Summary of Objects with Zero Rows Extracted
• Create Record Layout Report
• DB2 Index Report

Extract Progress Report

The Extract Progress Report shown in Figure 216 displays which objects are being accessed during the
extract and includes the number of rows (records) extracted for each object.

Figure 216. Extract Progress Report

File-Aid/RDX 17.02.00 Extract Progress Report PAGE 1

DATE 2014-09-02
Extract File. . : TSOID01.R42.EXTRACT(Member) TIME 09.01.06
Extract Request : TSOID01.RDX.EXTCRIT.D050815.T090104 SSID DSN
Driving Object. : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___ 

Time Rows Extracted Object 
-------- ---------- --------------------------------------------------------------------------------------------------------------
09:01:07 25 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_
____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____
7____+____8____+____9____+___10____+___11____+___12____+___ 
09:01:08 18 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_
____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____
7____+____8____+____9____+___10____+___11____+___12____+___ 
09:01:08 3 M-TSOID01.FASAMP.EMPMAST 
09:01:09 8 D-DSNLOCAT.TSOID01.DEPT 
09:01:09 1 D-DSNLOCAT.TSOID01.DEPT 


The Extract Progress Report displays the extract progress for each object. It includes the following
information:

Time
Shows the time when the progress report for this object was written.

Rows
The number of rows (records) extracted from the current object so far. The update interval can be
set with the User Parm "Table Progress Row Count" (see also Option 0—Profile on page 49). In this
example the progress row count parameter was set at 25.

Extracted Object
The name of the object from which data has been extracted so far.
400 File-AID/RDX Reference

Relationship Navigation and Sampling Report

The Relationship Navigation and Sampling Report shown in Figure 217 contains the relationship
criteria specified for the extract that produced the report.

Figure 217. Relationship Navigation and Sampling Report

File-AID/RDX 17.02.00 Relationship Navigation and Sampling Report PAGE 1

DATE 2014-09-02
Extract File. . : TSOID01.FR44.EXTRACT(Member) TIME 09.01.06
Extract Request : TSOID01.RDX.EXTCRIT.D050815.T090104 SSID DSN
Relationships : TSOID01.FR44.RELATION
Driving Object. : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___ 

Status D P S I Cycle MaxRows Deps Relationship 
---------- - - - - ------ ------- ----- ------------------------------------------------------------------------------------------- 
- Y N - * * * RI RELNAME: DESCRIPTION___+____2____+____3____+____4____+____5____+____6____+____7____+___
_8____+____9_____+___10____+___11____+___12____+___
Parent: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____
6____+____7____+____8____+____9_____+___10____+___11____+___12____+___.TABLE
____1____+____2____+____3____+____4____+____5____+____6____+____7____+____8_
___+____9____+___10____+___11____+___12____+___ 
Dependent: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____
6____+____7____+____8____+____9_____+___10____+___11____+___12____+___.TABLE
____1____+____2____+____3____+____4____+____5____+____6____+____7____+____8_
___+____9____+___10____+___11____+___12____+___ 
Y Y N - * * * RI RELNAME: RDD 
Parent: D-DSNLOCAT.TSOID01.DEPT 
Dependent: D-DSNLOCAT.TSOID01.DEPT 

Y - - N * * * AR Desc: 
Parent: D-DSNLOCAT.TSOID01.EMP 
Dependent: M- TSOID01.FASAMP.EMPMAST 

Y Y N N * * * RI RELNAME: EMP 
Parent: D-DSNLOCAT.TSOID01.EMP 
Dependent: D-DSNLOCAT.TSOID01.EMPPROJACT 

Y Y N N * * * RI RELNAME: EMPPROJ 
Parent: D-DSNLOCAT.TSOID01.EMP 
Dependent: D-DSNLOCAT.TSOID01.PROJ 

- Y N - * * * AR Desc: This is the AR description 
Parent: D-DSNLOCAT.TSOID01.EMP 
Dependent: D-DSNLOCAT.TSOID01.DEPT 

Y - - N * * * AR Desc: 
Parent: D-DSNLOCAT.TSOID01.EMP 
Dependent: D-DSNLOCAT.TSOID01.CONTACT_TABLE 

Y Y N N * * * AR Desc: 
Parent: D-DSNLOCAT.TSOID01.EMP 
Dependent: D-DSNLOCAT.TSOID01.DEPT 

* * * END OF REPORT * * *

This report shows the name of the extract file, extract request file, relationship file, driving object,
input key file (if specified), and a list of the referential integrity and application relationships used in
the extract process. In addition, the Db2 subsystem ID or its remote location ID is shown.

This report does not include any excluded objects. Excluded objects are listed separately in the
Relationship Navigation and Sampling Excluded Object Report.

For each relationship listed, the following information is shown:

Status
Displays the Excluded status for each relationship excluded from the current extract process.
Extract 401

Navigation Information:

D (Direct)
Y = Extract all of the dependents of the driving object and their dependents. 
N = Don’t extract any of the dependents of the driving object and their dependents. 
- (dash) = Not meaningful for this relationship, it’s not the driving object or a direct dependent.

P (Parent)
Y = Extract parents of all extracted data to maintain the integrity of the extracted data.

S (Sibling)
Y = Extract other dependents of the extracted parents from the same relationships.

I (Indirect)
Y = Extract other dependents of the extracted parents from other relationships.

Sampling Information:

Cycle
The maximum number of cycles for all relationships leading from the object. Cycle count limits
the number of times a relationship is visited during an extract.

Max Rows
The maximum number of rows to extract via downward navigation (direct, indirect and sibling)
of this relationship.

Deps
The maximum number of dependent records to be extracted for each parent record extracted. An
asterisk (*) indicates that File-AID/RDX extracted all dependent records. This value is used only
when extract processing proceeds from a parent object to a dependent object.

Relationship Information:

Type
The kind of relationship that exists between each pair of corresponding tables.

RI Db2-defined referential integrity relationship

AR User-defined application relationship

RELNAME or Desc
Displays the RELNAME for RI relationships or the defined description for application
relationships (AR).
402 File-AID/RDX Reference

Parent
The name of the object defined as the parent in an RI or application relationship.

Dependent
The name of the object defined as the dependent (child) in an RI or application relationship.

Layout
The name of the record layout file defined in a KEY relationship.

Relationship Navigation and Sampling Excluded Object Report

This report is the same report as the Relationship Navigation and Sampling Report but it includes
only the excluded objects.

Figure 218. Relationship Navigation and Sampling Excluded Object Report

File-AID/RDX 17.02.00 Relationship Navigation and Sampling Excluded Object Report PAGE 1
DATE 2014-09-02
Extract File. . : TSOID01.FR44.EXTRACT(Member) TIME 09.01.06
Extract Request : TSOID01.RDX.EXTCRIT.D050815.T090104 SSID DSN
Relationships : TSOID01.FR44.RELATION
Driving Object. : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___ 

Status D P S I Cycle MaxRows Deps Relationship 
---------- - - - - ------ ------- ----- ------------------------------------------------------------------------------------------- 
Excl User - - - - * * * AR Desc: 
Parent: D-DSNLOCAT.TSOID01.EMP 
Dependent: D-DSNLOCAT.TSOID01.DEPT 

* * * END OF REPORT * * *

Refer to Relationship Navigation and Sampling Report for the description of the report fields.

Object Sampling and Selection Criteria Report

The Object Sampling and Selection Criteria Report shown in Figure 219 on page 403 contains the
selection criteria specified for the extract that produced the report.
Extract 403

Figure 219. Object Sampling and Selection Criteria Report

File-AID/RDX 17.02.00 Object Sampling and Selection Criteria Report PAGE 1

DATE 2014-09-02
Extract File. . . : TSOID01.FR44.EXTRACT(Member) TIME 09.01.06
Extract Request .: TSOID01.RDX.EXTCRIT.D050815.T090104 SSID DSN
Relationships : TSOID01.FR44.RELATION
Driving Object. . : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9___
__+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7___
_+____8____+____9____+___10____+___11____+___12____+___ 
Input Keys File: TSOID01.R43.KEYS(EMPKEYS)
---------------------------------------------------- Extract Scope Information -----------------------------------------------------
Cycle count. . . . . . . . . . . . . . . . . . . : * (* for no maximum)
Maximum total rows/objects from all objects. . . : *
Action when maximum rows/records count is reached: QUIESCE
Extract from DB2 using Uncommitted Reads. . . . .: YES
Extract IMPLICITLY HIDDEN columns. . . . . . . . : NO 
Extract from Image Copy. . . . . . . . . . . . . : NO 
Temporal Parameters: 
Temporal Table Present . . . . . . . . . . . . . : D 
Use Business Time. . . . . . . . . . . . . . . . : Y 
Type of Business Time Criteria . . . . . . . . . : AS OF 
Business Start . . . . . . . . . . . . . . . . . : 2011-07-23 
Business End . . . . . . . . . . . . . . . . . . : 
Use System Time. . . . . . . . . . . . . . . . . : Y 
Type of System Time Criteria . . . . . . . . . . : AS OF 
System Start . . . . . . . . . . . . . . . . . . : 2011-07-23-00.00.01 
System End . . . . . . . . . . . . . . . . . . . : 
------------------------------------------------ Criteria Set 1 of 2 - Object Information -------------------------------------------
Status Cycle MaxRows NTH Object Criteria
---------- ------ ------- ---- -----------------------------------------------------------------------------------------------------
* * * D-DSNLOCAT.TSOID01.EMP 
SQL: SELECT * FROM TSOID01.EMP 
WHERE EMPNO > '000001' 

* * * M-TSOID01.FASAMP.EMPMAST
Layout. . . .: TSOID01.FASAMP.LAYOUTS(EMPLOYEE)
01 Level Name: EMPLOYEE-MASTER-FILE

* * * D-DSNLOCAT.TSOID01.PROJ 

* * * D-DSNLOCAT.TSOID01.PROJACT 

* * * D-DSNLOCAT.TSOID01.EMPPROJACT 

* * * D-DSNLOCAT.TSOID01.DEPT 
SQL: SELECT * FROM TSOID01.DEPT
WHERE DEPTNO < 'ZZZ' 

* * * D-DSNLOCAT.TSOID01.CUSTOMER_TABLE 

* * * D-DSNLOCAT.TSOID01.CONTACT_TABLE 


------------------------------------------------ Criteria Set 2 of 2 - Object Information -------------------------------------------
Status Cycle MaxRows NTH Object Criteria
---------- ------ ------- ---- -----------------------------------------------------------------------------------------------------
* * * D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8__
__+____9_____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5_
___+____6____+____7____+____8____+____9____+___10____+___11____+___12____+___ 
----+----1----+----2----+----3----+----4----+----5----+----6----+----7-- 
SQL: SELECT * FROM CREATOR__1____+____2____+____3____+____4____+____5____+___
_6____+____7____+____8____+____9_____+___10____+___11____+___12____+___.
TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7__
_+____8____+____9____+___10____+___11____+___12____+___ 

* * * M-TSOID01.FASAMP.EMPMAST
Layout. . . .: TSOID01.FASAMP.LAYOUTS(EMPLOYEE)
01 Level Name: EMPLOYEE-MASTER-FILE

Selection criteria used for the object: 

DEFINE BLOCKS=SELECTION, 

LAYOUT_DSNAME=TSOID01.FASAMP.LAYOUTS, 
LAYOUT_MBRNAME=EMPDUP, 

INITIAL_SKIP=0, 
THEN_SELECT=1, 
THEN_SKIP=0, 

MAXIMUM_TO_SEARCH=ALL, 
MAXIMUM_TO_SELECT=ALL 

SELECT SET=1,LAYOUT=EMPLOYEE-MASTER-FILE 
IF 
FIELD_NAME=EMP-MID-INIT, 
POSITION=31,LENGTH=1,OPERATOR=EQ, 
TYPE=T,VALUE=R 


This report does not include any excluded objects. Excluded objects are listed separately in the Object
Sampling and Selection Criteria Excluded Object Report.
404 File-AID/RDX Reference

This report consists of three parts. The first part shows the following:

• The name of the extract file. If the extract file is a PDS, the member name is also displayed.
• The Db2 subsystem ID and the Db2 remote location ID.
• The name of the extract request file. If the extract request file is a PDS, the member name is also
displayed.
• The name of the relationship file.
• The name of the extract’s driving object.
• The name of the Input (External) Keys File, if one is used for the extract.

The second part shows the values specified for the following extract scope parameters:

• The global cycle count.

• The total number of rows (records) to extract from all objects.
• Action when maximum rows/records count is reached: QUIESCE or STOP.
• Extract from Db2 using Uncommitted Reads indicator.
• Extract IMPLICITLY HIDDEN columns.
• Extract from Db2 Image Copy indicator.
• The defined temporal table parameters, if specified for the extract. Temporal Table Present
identifies the temporal table type: B=Business Time, S=System Time,or D=both, Business and
System Time.

The third part shows a list of the criteria sets in the extract including the following for each set:

• Object status, ALL or PASSTHRU, as applicable.

• Cycle count for the object.
• The total number of rows (records) to extract from the object.
• The value specified in the Select every nth row from object field.
• Object name.
• Record layout name, if object is an MVS file.
• 01 Level name, if object is an MVS file.
• Any SELECT statement generated for the object.

Object Sampling and Selection Criteria Excluded Object Report

The Object Sampling and Selection Criteria Excluded Object Report shown in Figure 220 on page 405
contains the excluded objects, including exclusion reason, for the extract that produced the report.
Extract 405

Figure 220. Object Sampling and Selection Criteria Excluded Object Report

File-AID/RDX 17.02.00 Object Sampling and Selection Criteria Excluded Object Report PAGE 1
DATE 2014-09-02
Extract File. . . : TSOID01.FR44.EXTRACT(Member) TIME 09.01.06
Extract Request .: TSOID01.RDX.EXTCRIT.D050815.T090104 SSID DSN
Relationships : TSOID01.FR44.RELATION
Driving Object. . : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9___
__+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7___
_+____8____+____9____+___10____+___11____+___12____+___ 
Input Keys File: TSOID01.R43.KEYS(EMPKEYS)
---------------------------------------------------- Extract Scope Information -----------------------------------------------------
Cycle count. . . . . . . . . . . . . . . . . . . : * (* for no maximum)
Maximum total rows/objects from all objects. . . : *
Action when maximum rows/records count is reached: QUIESCE
Extract from DB2 using Uncommitted Reads. . . . .: YES
Extract IMPLICITLY HIDDEN columns. . . . . . . . : NO 
Extract from Image Copy. . . . . . . . . . . . . : NO 
Temporal Parameters: 
Temporal Table Present . . . . . . . . . . . . . : D 
Use Business Time. . . . . . . . . . . . . . . . : Y 
Type of Business Time Criteria . . . . . . . . . : AS OF 
Business Start . . . . . . . . . . . . . . . . . : 2011-07-23 
Business End . . . . . . . . . . . . . . . . . . : 
Use System Time. . . . . . . . . . . . . . . . . : Y 
Type of System Time Criteria . . . . . . . . . . : AS OF 
System Start . . . . . . . . . . . . . . . . . . : 2011-07-23-00.00.01 
System End . . . . . . . . . . . . . . . . . . . : 
------------------------------------------------ Criteria Set 1 of 2 - Object Information -------------------------------------------
Status Cycle MaxRows NTH Object Criteria
---------- ------ ------- ---- -----------------------------------------------------------------------------------------------------
* * * D-DSNLOCAT.TSOID01.ACT 
***** This object was excluded from extract by the user ***** 
* * * M-TSOID01.FASAMP.EMPLOYEE
***** This object was excluded from extract due to extract scope ***** 
Layout. . . .: TSOID01.FASAMP.LAYOUTS(EMPLOYEE)
01 Level Name: EMPLOYEE-MASTER-FILE
------------------------------------------------ Criteria Set 2 of 2 - Object Information -------------------------------------------
Status Cycle MaxRows NTH Object Criteria
---------- ------ ------- ---- -----------------------------------------------------------------------------------------------------
* * * M-TSOID01.FASAMP.EMPMAST
***** This object was excluded from extract by the user ***** 
* * * M-TSOID01.FASAMP.EMPLOYEE
***** This object was excluded from extract due to extract scope ***** 
Layout. . . .: TSOID01.FASAMP.LAYOUTS(EMPLOYEE)
01 Level Name: EMPLOYEE-MASTER-FILE

* * * END OF REPORT * * *

Refer to Object Sampling and Selection Criteria Report for the description of the report fields.
406 File-AID/RDX Reference

Extract Summary Report

The Extract Summary Report shown in Figure 221 summarizes the results of the extract.

Figure 221. Extract Summary Report

File-AID/RDX 17.02.00 Extract Summary Report PAGE 1

DATE 2014-09-02
Extract File. . : TSOID01.FR44.EXTRACT(Member) TIME 09.01.06
Extract Request : TSOID01.RDX.EXTCRIT.D050815.T090104 SSID DSN
Compression Type: Variable field
Driving Object. : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___ 

ID Rows Extracted Objects and Relationships 
---- ---------- -------------------------------------------------------------------------------------------------------------------
D001 24 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____+
___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+____
8____+____9____+___10____+___11____+___12____+___ 
*** Maximum row/record count has been met for this object *** 

D002 3 M-TSOID01.FASAMP.EMPMAST 
99,999,999 Rows from relationship Parent: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5__
__+___ _6____+____7____+____8____+____9_____+___10____+___11____+___1
2____+___.TABLE____1____+____2____+____3____+____4____+____5____+____
6____+____7____+____8____+____9____+___10____+___11____+___12____+___ 
Dependent: M-TSOID01.FASAMP.EMPMAST 

D006 9 D-DSNLOCAT.TSOID01.DEPT
1 Rows from relationship Parent: D-DSNLOCAT.TSOID01.DEPT 
Dependent: D-DSNLOCAT.TSOID01.DEPT 
8 Rows from relationship Parent: D-DSNLOCAT.TSOID01.EMP 
Dependent: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5__ 
__+___ _6____+____7____+____8____+____9_____+___10____+___11____+___1
2____+___.TABLE____1____+____2____+____3____+____4____+____5____+____
6____+____7____+____8____+____9____+___10____+___11____+___12____+___ 
***** 36 TOTAL rows extracted from 8 objects ***** 

* * * END OF REPORT * * *

The Extract Summary Report consists of two parts. The first part shows the following:

• The name of the extract file. If the extract file is a PDS, the member name is also displayed.
• The Db2 subsystem ID and the Db2 remote location ID.
• The name of the extract request file. If the extract request file is a PDS, the member name is also
displayed.
• The compression type.
• The name of the extract’s driving object.
• The name of the Input (External) Keys File, if one is used for the extract.
• The view/base table summary, if Db2 views are part of the extract.

The second part of the report shows the following statistics for each object from which data was
extracted.

ID
The extract object ID (Dnnn) of the object from which data was extracted.

Rows
The number of rows extracted from the object listed in the Extracted Objects and Relationships
column.

Extracted Objects and Relationships

Lists the name of the object from which data was extracted along with the following information:
Extract 407

n Rows From Relationship: Parent/Dependent

Shows the number of rows extracted from each relationship from which data was extracted
for each extracted object.

Parent Displays the name of the parent object for the relationship on this line.
Dependent Displays the name of the dependent object corresponding to the above
parent object.

n Rows Keys written to Output Key File

Shows the number of keys written to the specified Output Key File for each extracted object.
The reported number includes duplicates which will be removed from the final Output Key
File. Only applicable if the extracted object has a dependent KEY relationship.

Additional Messages
Lists any additional extract message that applies to the extracted object. Possible Messages
include:

*** Selection Criteria applied ***

** Maximum row/record count has been met for this object ***
Info: Key not found - 000040

nnnnn Total Rows Extracted from n objects

This entry is the total number of rows or records extracted for this extract. It also shows the total
number of objects in this extract.

Summary of Objects with Zero Rows Extracted

The Summary of Objects with Zero Rows Extracted list all the objects from which zero rows (records)
were extracted.

Figure 222. Summary of Objects with Zero Rows Extracted

File-AID/RDX 17.02.00 Summary of Objects with Zero Rows Extracted PAGE 1

DATE 2014-09-02
Extract File. . : TSOID01.FR44.EXTRACT(Member) TIME 09.01.06
Extract Request : TSOID01.RDX.EXTCRIT.D050815.T090104 SSID DSN
Compression Type: Variable field
Driving Object. : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___ 

ID Rows Extracted Objects and Relationships 
---- ---------- -------------------------------------------------------------------------------------------------------------------
D003 0 D-DSNLOCAT.TSOID01.PROJ 

D004 0 D-DSNLOCAT.TSOID01.PROJACT 

D005 0 D-DSNLOCAT.TSOID01.EMPPROJACT 

D007 0 D-DSNLOCAT.TSOID01.CUSTOMER_TABLE 

D008 0 D-DSNLOCAT.TSOID01.CONTACT_TABLE 

***** 5 objects had zero rows extracted.

* * * END OF REPORT * * *


Refer to Extract Summary Report for the description of the report fields.
408 File-AID/RDX Reference

n objects had zero rows extracted

This message shows how many objects in this extract had zero rows or records extracted.

Create Record Layout Report

The Create Record Layout Report shown in Figure 223 summarizes for which objects File-AID/RDX
created record layouts during the extract. When applicable, it also lists the names of the created
layout and XREF files.

Figure 223. Create Record Layout Report

File-AID/RDX 17.2 Create Record Layout Report PAGE 1 

DATE 2014-09-02
Extract File. . : TSOID01.FRSAMP.EXTRACT TIME 16.40.48 

Record Layout Output File: TSOID01.FRSAMP2.LAYOUTS(LAYOUT1) 
XREF Output File. . . . .: TSOID01.FRSAMP.XREF(LAYOUT1 ) 

ID COBOL Formatted Record Layouts were created for the following DB2 Objects 
---- ------------------------------------------------------------------------------------------------------------------------------
E001 D-LOCATION.FRSAMP.PART_TABLE 
E002 D-LOCATION.FRSAMP.SUPPLIER_TABLE 
E003 D-LOCATION.FRSAMP.CUSTOMER_TABLE 
E004 D-LOCATION.FRSAMP.ORDER_TABLE 
E005 D-LOCATION.FRSAMP.ORDER_LINE_TABLE 
E006 D-LOCATION.FRSAMP.CONTACT_TABLE 
* * * END OF REPORT * * *

DB2 Index Report

The DB2 Index Report shown in Figure 224 should be empty when an extract runs well. When File-
AID/RDX recognizes that Db2 index utilization could be improved, it summarizes which if any Db2
indexes were available and used during an extract with Db2 objects. It contains information about
the index configuration that can be used to improve the performance of an extract by adding or
changing an index.

This report does not address the situation where an index is damaged
(advisory REORG pending).

The report includes:

• Name of the object

• Table cardinality and number of indexes

• Relationship information (RELNAME or AR description)

• Relationship columns

• Index used for SQL SELECT statement generation (if an index exists)

• Description of issues associated with the index

• Action suggested
Extract 409

Figure 224. DB2 Index Report

Index Report 

Index info for table: DSN8910.PROJ 
table cardinality = 20 number of indexes 2 
Dependent in relationship (name): RPP 
Relationship columns are: 
MAJPROJ 
Index definition used for SQL generation is no index available, no acceptable index 
Possible usage = tscan only, version: 
Action suggested: create an index using the relationship columns if a TSCAN is to be avoided.
It is suggested that a column with high cardinality be the first column of the index. 

Index info for table: DSN8910.PROJACT 
table cardinality = 77 number of indexes 1 
Dependent in relationship (name): RPAP 
Relationship columns are: 
PROJNO 
Index definition used for SQL generation is DSN8910.XPROJAC1, index cardinality: 77 unique 
Possible usage = high level partial, relationship cardinality = 86, version: 2 
All relationship columns are included in the index (high order columns) but there are 
columns after the relationship columns that reduce the effectiveness of the index. 
Index info for table: DSN8910.EMPPROJACT 
table cardinality = 74 number of indexes 2 
Dependent in relationship (name): REPAPA 
Relationship columns are: 
PROJNO 
ACTNO 
EMSTDATE 
Index definition used for SQL generation is DSN8910.XEMPPROJACT1, index cardinality: 74 unique 
Possible usage = high level partial, relationship cardinality = 27, version: 2 
All relationship columns are included in the index (high order columns) but there are 
columns after the relationship columns that reduce the effectiveness of the index. 

RDX Hybrid Scan

The DB2 Index Report includes a RDX Hybrid Scan section (Figure 225) when either situation is
detected:

• Presence of a column in the index that cannot be used for the particular relationship being
traversed. This makes any subsequent columns in the index unusable.”

• Unmatched relationship column.

Figure 225. DB2 Index Report with Hybrid Scan

RDX "hybrid" scan is possible. This is caused when an index is available but at least
one relationship column is not properly positioned in the index. 
FK_LCBS_SPEC_YR cardinality = 5 match 
FK_LCBS_SPEC_JUL cardinality = 100 match 
FK_LCBS_SPEC_ACC cardinality = 154 match 
FK_LCBS_SPEC_SEQ cardinality = 800 match 
FK_LCBS_SPEC_SUF cardinality = 8 match 
FK_LAB_TYPE_CD cardinality = 1 not matched 
FK_POS_LAB_CD cardinality = 60 not matched 
This index is missing 1 relationship columns. 
410 File-AID/RDX Reference
 411

Load
Overview
This chapter describes Option 3, Load. The Load option is used to load data from the File-AID/RDX
extract DASD or tape file into multiple related objects. The objects can be MVS files and/or Db2
tables. The Load option consists of an interactive phase and an execution phase.

Before you can load an extract file on tape you must specify an extract
summary file, previously known as an extract tape control file (see Extract
File Specification on page 419).

The interactive phase takes place online and consists of a File-AID/RDX Load menu that allows you to
provide information about the following:

• The DASD or tape file from which to load data.

• The target objects.
• Db2 LOAD or SQL Insert processing options.

Using this information, File-AID/RDX builds a series of steps to be performed during the execution
phase. You can then edit and save the load JCL created by File-AID/RDX before you submit it. Your
installation may also permit interactive (online) execution of the load.

In addition, you can create a single request member combining extract and load specifications. See
Extract and Checkpoint/Resumption on page 347 for more information about combining extract and
load specifications.

During the execution phase, you can load data into objects that contain data or load it into empty
objects. When loading into Db2 objects you have the choice of using either IBM’s Db2 LOAD utility
or SQL INSERT processing.

Target objects that do not exist can be created automatically as long as their create information was
obtained during the extract.

You can delete all existing data before loading, replace existing rows with records from the extract
file, or leave existing rows intact, only adding rows to the object. You can perform column-to-column
mapping to insert or load data to objects that are defined differently from the extracted objects.

File-AID/RDX verifies user authority before performing certain operations. See Db2 Privileges on page
547 for more information.

Support for Db2 XML and LOB Data Type

You can load extracted data from XML and/or LOB columns to target objects using either SQL Insert
or Db2 Load options. When loading an extract disguised with DCF (see also Using File-AID/RDX with
File-AID/Data Solutions (Using DCF) on page 604), be aware that the extracted XML and/or LOB data
is not disguised and will be loaded unmasked in its proper format.

Support for Db2 Temporal Tables

Temporal Table support requires Db2 Version 10 Release 1 or higher. You can load extracted data from
Temporal Tables to existing target Temporal Tables using Db2 Load Method only. You can specify
412 File-AID/RDX Reference

whether File-AID/RDX generates the PERIODOVERRIDE clause when loading data to SYSTEM
TEMPORAL tables (see Preserve Temporal on page 427).

Support for Db2 Archive Tables

In File-AID/RDX table lists, Archive Table Type ‘R’ is identified as Type ARCHV. You can load
extracted data from Archive Tables to existing target Archive Tables using SQL Insert Method (see
DB2 Load Method on page 426) only.

1. The Load Auto Create feature does not support Archive tables.
2. Using the DB2 Load option with an archive-enabled table is not
supported.

GDG Considerations
The name displayed for the source object is the absolute generation of the GDS extracted. File-
AID/RDX generates relative generation numbers for objects in the target environment, keeping the
generations in the same order as they were in the source environment. You may overtype the
generated name with a different name. The target object can be a GDS with either a relative or
absolute generation or it can be a regular non-GDG dataset. Specifying the GDG base without a
version is invalid for a Target object.

File-AID/RDX does not support extracting from and loading to tape datasets.

Load Reference List

The Load Reference List screen shown in Figure 226 on page 413 is displayed when your profile set it
as the first load panel and you

• Select Option 3, Load, from the File-AID/RDX Primary Option Menu

or
• Enter the REFERENCE command on a load panel

The reference lists for Load and Delete share the same entries. Delete requests are not eligible for load
processing.

Use this screen to select a load request from the list or start a new load request. File-AID/RDX adds a
load request to the list when a request is saved from the Load Menu. In addition, whenever you have
successfully executed an extract, File-AID/RDX places an entry with the extract file name into the
load reference list. However, extracts that originate from the “Single Panel Extract” function are not
included in the Load Reference List.

You can also create a new load request with the NEW command, or open a saved load request file
with the REQUEST command.

If your reference list is empty, File-AID/RDX will display the Request File Member List screen,
listing the members of the request file specified in your profile, or if none is in your profile,
display the Extract File Specification screen so you can create a new load request.

The reference list is stored in your personal USER profile. If your USER profile file
(‘userid.midlevlqualifier.PROFILE’) does not exist, File-AID/RDX will create your USER profile
when you are saving an extract or load request.
Load 413

Refer to Option G—Global User Defaults on page 82 for how to set the maximum number of list
entries for the reference list.

You may specify multiple line commands at a time. All line commands are processed before any
primary commands. When processing multiple commands File-AID/RDX displays a message like
“Processing line command 2 of 4” whenever it starts processing the next line command after the first.

Figure 226. Load Reference List

File-AID/RDX -------------- Load Reference List ----------- Row 1 to 5 of 5

Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go S = Select
I = Info D = Delete from list L = Lock U = Unlock 

Request Extract File Name RT L YY/MM/DD
-------- ------------------------------------------------------ -- - --------
_ TSOID01.FRSAMP.CUSTDB.EXTRACT 10/02/02
_ TSOID01.FRSAMP.EXTRACT L L 10/02/01
_ TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST) 09/01/24
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2 EL L 09/01/14
_ TEST2 TSOID01.FRSAMP.TEST2.EXTRACT L L 09/01/04
******************************* Bottom of data ********************************


The lower part of the screen displays a listing of your recently referenced load requests. Use one of
the line command to either resubmit one of the requests or model a new request after it.

Request
Name of the load request (member name in the saved load request file). A blank entry means the
request was saved to a sequential file or that it is an automatic entry after executing an extract.

Extract File Name

Name of the file containing the extracted data. If saved to a PDS the member name is displayed in
parentheses.

RT
Request Type. Identifies the extract request type:

EL

Extract and Continue with Load request. When selected in the Load Reference List only the
load will be performed.

Load only request.

L
Locked Entry. Identifies whether the request is locked in the reference list or whether it is
allowed to roll off.

blank

not protected from roll over.

414 File-AID/RDX Reference

Locked in reference list; entry will not roll off the list.

YY/MM/DD
Date when the load request was last saved or the extract was completed. The list entries are
ordered with the most recent date placed on top of the list.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

D (Delete from list)

Removes this request from the load reference list.

G (Go)
Submits this load request without any changes. File-AID/RDX validates the request before
submitting the JCL for the load request.

I (Info)
Displays the Request Details screen, which provides more comprehensive information about the
load request. See Figure 227 for an example.

Figure 227. Request Details

File-AID/RDX ---------------- Request Details -------------------------------

Command ===>

Request Information: 
Request File Name : TSOID01.FRSAMP.REQUEST 
Member Name . . . : TEST2 
Request Type . . . : LOAD 
Description . . . : FRSAMP Delete request test 2 
Reference Date . . : 2009/01/04 Reference Time: 00:00:07 

Driving Object Information: 
SSID . . . . . . . : 
Name . . . . . . . : 

Extract Information: 
Extract File Name : TSOID01.FRSAMP.TEST2.EXTRACT 
Summary File Name : 
Disguise Control File: 
Repository Name: 
Project Name: 
Extract Date . . . : 2009/01/04 Extract Time : 00:00:07 

Relationship Information: 
File Name . . . . : TSOID01.FRSAMP.RELATION 

L (Lock)
Protects this entry from rolling off the load reference list.
Load 415

S (Select)
Selects this load request and displays the Load Menu prefilled with all the information from this
request.

U (Unlock)
Does not protect this entry from rolling off the load reference list.

V (View JCL)
Displays the JCL for this load request. File-AID/RDX shows the Generated JCL panel where you
review and modify the load JCL.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

DETAIL (D)
Expands the one-line display for each request into a two-line display. The additional line shows
the request description. See Figure 228 for an example. Detail is a toggle switch so enter Detail
again to return to the original format.

Figure 228. Load Reference List - DETAIL Screen

File-AID/RDX -------------- Load Reference List ----------- Row 1 to 5 of 5

Command ===> Scroll ===> CSR 

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go S = Select
I = Info D = Delete from list L = Lock U = Unlock 

Request Extract File Name RT L YY/MM/DD
-------- ----------------------------------------------------- -- - --------
_ TSOID01.FRSAMP.CUSTDB.EXTRACT 02/02/02
Description: DB2-TSOID01.CUSTOMER 
_ TSOID01.FRSAMP.EXTRACT L L 02/02/01
Description: DB2-FRSAMP.CUSTOMER 
_ TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST) 02/01/24
Description: MVS-TSOID01.CUSTOMER 
_ DIEBLD TSOID01.CUST.EXTRACT.NODB2 EL 02/01/31
Description: Auto create all files and load 
_ TEST2 TSOID01.FRSAMP.TEST2.EXTRACT L L 09/01/04
Description: DB2-FRSAMP.ORDER
******************************* Bottom of data ********************************

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.

Find looks for matches in the request detail information for each list entry. When a match is
found and is not visible in the displayed row, use the I (info) line command to display the detail
information.
416 File-AID/RDX Reference

NEW (N)
Starts a new load request from an existing extract file. Use the NEW command to open extract
files created with File-AID/RDX prior to Release 3.0.

REQUEST (REQ)
Opens a saved extract or load request file. Refer to Request File Member List on page 416 for more
information.

File-AID/RDX uses the default value as specified in your current profile. If your profile doesn’t
include a request file, File-AID/RDX prompts for one.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 229 for an example. SIZE is a toggle switch so enter SIZE again to return to the
original format.

Figure 229. Load Reference List - SIZE Screen

File-AID/RDX ------------- Load Reference List --------- Row 1 to 6 of 6

Command ===> Scroll ===> CSR 
Request--Extract File Name-------------------------------------RT-L-YY/MM/DD
_ TSOID01.FRSAMP.CUSTDB.EXTRACT 02/02/02
_ TSOID01.FRSAMP.EXTRACT L L 02/02/01
_ TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST) 02/01/24
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2 EL L 02/01/14
_ TEST2 TSOID01.FRSAMP.TEST2.EXTRACT L L 02/01/04
****************************** Bottom of data ********************************

Request File Member List

The Request File Member List Screen shown in Figure 230 on page 417 is displayed when you

• Select Option 3, Load, from the File-AID/RDX Primary Option Menu and your profile set it as the
first load panel
or
• Enter the REQUEST primary command on a load panel

This screen displays the member list of a saved extract or load request file. Use one of the line
commands to select a member for your load request.
Load 417

If you select a member that does not contain valid load request information, File-AID/RDX will issue
a message. Select a different member or issue the NEW or REFERENCE command to start another load
request.

If you want to load from an extract file created prior to Release 3.0, use the
NEW command to initiate a new load request. Then you specify the name
of the extract file.

Figure 230. Request File Member List Screen

File-AID/RDX ------------ Request File Member List ------- Row 1 to 8 of 8 

Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, REFerence
Line commands: G = Go S = Select, D = Delete R = Rename

Request File ===> FRSAMP.EXTCRIT 

Member Description Changed
-------- -------------------------------------------------- ---------- 
_ DB2VSAM db2 to vsam extract 2004/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 2004/08/13 
_ MIKE1 Member List 2004/05/10 
_ NODB2 mcust with db2 deleted 2004/01/25 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 2004/08/30
_ PART1 Member List 2003/02/11
_ SELCUST test select customer 2002/01/28 
_ TESTA test saving the criteria 2001/04/12
******************************* Bottom of data ********************************

Request File
If you didn’t specify a name with the REQUEST command, the request file name comes from your
current profile. Enter a new file name to change to a different saved request file and File-
AID/RDX will display its member list.

The lower part of the screen displays a listing of the file’s members.

Member
Member name in the saved extract request file. The member names are displayed in alphabetical
order.

Description
Text that was entered in the Description field when the extract or load request was created. If you
left the field blank File-AID/RDX sets the description to the driving object type and name.

Changed
Date when the member was last saved.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
418 File-AID/RDX Reference

D (Delete)
Delete this member from the request file. Displays the Delete Confirmation window (Figure 231).

Figure 231. Delete Confirmation window

Delete Confirmation 
COMMAND ===> 

Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 

Member to be Deleted: TESTA 


ENTER to confirm delete 
END to return to Request File Member List 



G (Go)
Submits this load request without any changes. File-AID/RDX validates the request before
submitting the JCL for the load request.

R
Rename the request member. The Rename Confirmation window (Figure 232 on page 418) allows
you to enter a new name for the request file member.

Figure 232. Rename Confirmation window

Rename Confirmation 
COMMAND ===> 

Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 

Member to be Renamed: TESTA 
New Member name ===> 


ENTER to confirm rename 
END to return to Request File Member List 



S (Select)
Selects this load request and displays the Load Menu prefilled with all the information from this
request.

V (View JCL)
Displays the JCL for this load request. File-AID/RDX shows the Generated JCL panel where you
review and modify the load JCL.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
Load 419

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFIND to repeat the search.

NEW (N)
Starts a new load request from an existing extract file (see Extract File Specification on page 419).

REFERENCE
opens your Load Reference List file. Refer to Figure 226 on page 413 for more information.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 233 for an example. SIZE is a toggle switch so enter SIZE again to return to the
original format.

Figure 233. Request File Member List - SIZE Screen

File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8 

Command ===> Scroll ===> CSR
Member Description 
_ DB2VSAM db2 to vsam extract 
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 
_ MIKE1 Member List 
_ NODB2 mcust with db2 deleted 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 
_ PART1 Member List 
_ SELCUST test select customer 
_ TESTA test saving the criteria 
******************************* Bottom of data ********************************

Extract File Specification

The Extract File Specification screen shown in Figure 234 is displayed when you

• Enter the NEW command in either the Load Reference List or the Request File Member List
Screen
420 File-AID/RDX Reference

Figure 234. Extract File Specification

File-AID/RDX ----------- Extract File Specification

-------------------------
Command ===> 


Please specify an Extract File or a pattern name (in order to select an 
Extract File from a list). 

Extract File ===> FRSAMP.EXTRACT 





* * * * When the Extract File is on TAPE, a Summary File is REQUIRED. * * * * 
* * * * When the Extract File is on DISK, a Summary File is OPTIONAL. * * * * 

Summary File usage ===> N (N = None; E = Existing; C = Create; U = Update) 
Summary File ===> 

Note: Creating or updating a Summary File requires the submission of 
a BATCH job. Upon completion of this batch job, the Summary File 
will be available for your use.

Use this screen to specify the name of the extract file from which you want to load data and
optionally, the summary file. Press ENTER to continue to the Load Menu (Summary File usage = N or
E), Create New File (Summary File usage = C), or the ISPF/PDF EDIT Screen (Summary File usage = U).

Extract File
Specify the name of the File-AID/RDX extract file from which you want to load data. An asterisk
(*) or pattern displays a selection list. The extract file must be in the format that File-AID/RDX
creates during extract. See Extract File on page 44 and File-AID/RDX Extract File on page 377 for
information about the format of the extract file.

Summary File usage

Specify whether your load request should utilize the summary file. The summary file is required
for extract files on tape or cartridge, it’s optional for extract files on disk. Starting with Release
4.8 of File-AID/RDX, a summary file is created automatically during the extract to tape process
(see Specify Extract “TO” File Information on page 338). For a multi-volume disk extract file, a
summary file can speed up processing as it contains the header and trailer information for the
extract.

N None - Specify N when the extract file is on disk and a summary file is not needed.
E Existing - Specify E when the summary file for this particular extract file already exists.
File-AID/RDX continues with the Load Menu.
C Create - Specify C when you want File-AID/RDX to create the summary file for the above
extract file. File-AID/RDX then starts a batch job that extracts header and trailer
information from the extract file. After the batch job to create the summary file has
finished, you can continue the load request for this extract file.

File-AID/RDX will display the Create New File screen (see Figure 175 on page 334) to
allocate the new file.
U Update - Specify U when you want File-AID/RDX to update an existing summary file for
the above extract file. File-AID/RDX then starts a batch job that extracts header and trailer
information from the extract file. After the batch job to update the summary file has
finished, you can continue the load request for this extract file.
Load 421

Summary File
Specify the name for the summary file (previously known as tape control file) that contains the
information for the above extract file that’s stored on tape, cartridge, or disk. The summary file is
required for extract files on tape or cartridge, it’s optional for extract files on disk. If your extract
file is a multi-volume file, a summary file can speed up processing as it contains the header and
trailer information for the extract. An asterisk (*) or pattern displays a selection list.

The summary file is the same for both Load and Delete processes. Therefore,
you may use a summary file created with the DELETE Option for loading
data based on the same extract tape file.

Edit JCL for Summary File

The ISPF/PDF EDIT Screen shown in Figure 235 is displayed when you select to have File-AID/RDX
create or update the summary file on the Extract File Specification screen.

Figure 235. ISPF/PDF EDIT Screen

VIEW - File-AID/RDX Generated JCL --------------------------- COLUMNS 001 072

COMMAND ===> SCROLL ===> CSR
You are now editing the JCL that File-AID/RDX has generated to perform
the required function. Change this JCL as desired before submitting. 



000004 //* XFRJSUMM
000005 //*--------------------------------------------------------------------
000006 //* THIS STEP WILL BUILD A SUMMARY FILE BY READING THE HEADER RECORDS 
000007 //* AND TRAILER RECORDS OF YOUR EXTRACT FILE. 
000008 //* 
000009 //SUMMARY EXEC PGM=XFREXEC,REGION=4096K,
000010 // PARM=(FR,A,B)
000011 //STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ170.CXVJLOAD, 
000012 // DD DISP=SHR,DSN=CPWR.MXVJ170.SXVJLOAD 
000013 //RDXMLIB DD DSN=CPWR.MXVJ170.CXVJMENU,DISP=SHR
000014 //EXTPARMS DD DSN=TSOID01.RDX.PARMS.1300827.T094308,DISP=SHR
000015 //EXTRACT DD DSN=TSOID01.FRSAMP.EXTRACT,
000016 // DISP=SHR
000017 //*
000018 //CONTROL DD DSN=TSOID01.RDX.SUMMARY,
000019 // DCB=(RECFM=VB,LRECL=32756,BLKSIZE=32760),
000020 // DISP=(NEW,CATLG,DELETE),

Use this screen to edit and submit the extract summary JCL generated by File-AID/RDX.

If you want to save this JCL, use the ISPF/PDF CREATE or REPLACE command before you exit this
screen. Otherwise, File-AID/RDX deletes this file.

Submit this JCL to create the summary file with the extract header and trailer information. File-
AID/RDX will return to the Load Reference List or Request File Member List Screen where you entered
the NEW command.
422 File-AID/RDX Reference

Load Menu
After you selected a load request from either the Load Reference List or the Request File Member List,
completed the Extract File Specification, or whenever you enter the MENU command within the load
option, File-AID/RDX displays the Load Menu as shown in Figure 236.

Your profile’s selected load flow (see Panel Customization on page 70) might
not show the Load Menu initially. Just issue the MENU command to display
it from any of the load option panels.

The Load Menu provides a quick overview of your current load request and its status fields are
immediately updated upon return from its suboptions. This allows you to selectively access any of the
options or to submit the load request when all load options are set to your liking.

After completing all load specifications, simply select Option 8 and File-AID/RDX submits this load
job.

Figure 236. Load Menu

File-AID/RDX -------------------- Load Menu ---------------------------------

Option ===> SITE Profile: RDXMENU 

Primary commands: menu-number, ALL, REFerence, REQuest, MODE, SAVE
Line commands: S or / to create flow through selected options.

Extract file name ===> TSOID01.FRSAMP.EXTRACT 
Description ===> 

Current Values
_ 1 Load Object Specifications SSID=DSN, Load method=DB2
_ 2 Source to Target Mapping 0 of 6 Objects are excluded
_ 3 Target Environment Create: Tables=6 + DB TS, Files=1
_ 4 Existing Data Options DB2=Global setting, MVS=By object
_ 5 Insert Processing Options Log requested 
_ 6 Save Load Request TSOID01.EXTCRIT(member) 
_ 7 View JCL 
_ 8 Submit JCL 





The top of this screen consists of the following fields:

Extract File Name

Name of the file that contains the extracted related data to be loaded.

Description
Displays the description text for the current load request as entered with the Save Load Request
option. Using this description is a helpful way to document your load request.
Load 423

Load Menu Options

Enter the option number (1 - 8) to select the desired option or enter ALL to step through all options
in sequence. Alternatively, you may also select one or more options with the S or / line command.

Options 6, 7, and 8 are not available for the “Continue With Load” Extract
option (see also Checkpoint/Resumption on page 347).

The Current Values are display fields only and are updated upon return from each of the load menu
options to reflect the current status and value for the option.

1 - Load Object Specifications

Displays the Load Object Specifications where you can specify Db2 target information such as
Db2 subsystem, location, load method, and preserve temporal information, and global object
name modifiers for Db2 Creator, Db2 Index name pre- and suffix, MVS high-level qualifier and
MVS file name suffix. The option to revert to source names undoes all applied object name
modifiers without having to exit the Load function.

Current Values shows the target SSID (Db2 subsystem ID) for all Db2 objects that are part of this
load request as well as the load method (Db2 load utility or SQL INSERT statements).

2 - Source to Target Mapping

Displays the Source to Target Mapping panel where you invoke the process of mapping columns
between source and target objects. From this panel you also can modify information about the
target objects (creator, and tables for Db2 objects; fully qualified file names for MVS objects) to
which data in the extract file will be loaded. In the list of objects you can mark objects to be
excluded from the load process.

MVS file with I/O exit: If you want to load an MVS file using an I/O exit,
you must select the MVS file in the Source to Target Mapping panel to
invoke the exit.

Current Values shows how many objects have been excluded from the load process.

3 - Target Environment
Displays the Target Environment panel that lists all target objects to be loaded including those
that don’t exist yet but will be created using the create information from the extract file. For
objects to be created you can then edit the create information to fit your specific target
environment. Optionally, you can size the objects to be created based on the extract data as
opposed to the original source create information.

Current Values displays the number of MVS and Db2 target objects to be created.

4 - Existing Data Options

Displays the Existing Data Options panel where you specify what to do with the existing data of
the target objects, whether to delete all records, or replace existing records.

Current Values displays the specified options.

424 File-AID/RDX Reference

5 - Processing Options
Displays the Processing Options panel where you can specify Db2 load as well as discard
processing options.

Current Values displays the specified option.

6 - Save Load Request

Specify whether to save this load request in a file. File-AID/RDX presents the Save Load Request
panel where you identify the load request file to save your request to.

Current Values displays None or the name of the load request file.

7 - View JCL
Select this option to view the JCL for this load request. File-AID/RDX shows the Generated JCL
panel where you review and modify the load JCL.

Option 7 - View JCL switches to Option “7 - View REXX” when the MODE
primary command has set the execute load mode to INTERACTIVE (online)
(see Figure 237). Interactive load execution is an installation option and is
only available if specifically installed at your site.

8 - Submit JCL
Submits the JCL for this load request. Watch for the message that the job has been submitted and
later for the completion message.

Option 8 - Submit JCL switches to Option “8 - Execute REXX” when the

MODE primary command has set the execute load mode to INTERACTIVE
(online) (see Figure 237). Interactive load execution is an installation option
and is only available if specifically installed at your site.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

ALL
Selects all available load menu options for you to step through in sequence. ALL does not include
option 8 - Submit JCL. To submit the load JCL, select option 8 - Submit JCL separately or enter
the SUBMIT command in the View JCL panel.

MODE
Enter the MODE command in the Command field to enable execution of the load request
interactively (online). Load Menu options 7 - View JCL and 8 - Submit JCL will change to “7 -
View REXX” and “8 - Execute REXX” (see Figure 237) to show that the load will be executed
interactively when selecting Option “8 - Execute REXX”. MODE acts as a toggle switch.
Load 425

MODE command is only valid when variable “ALLOW_LOADS_TO_RUN_ONLINE=” is set to Y

(see ALLOW_LOADS_TO_RUN_ONLINE of the File-AID Advanced Configuration Guide).

1. INTERACTIVE (online) load is an installation option and is only available

if specifically installed at your site.
2. Interactive mode is not allowed with Db2 Load Utility.
3. Interactive mode is not allowed for an extract with Continue with Load.

Figure 237. Load Menu - ONLINE Mode

_ 4 Existing Data Options DB2=Global setting, MVS=By object

_ 5 Insert Processing Options Log requested 
_ 6 Save Load Request TSOID01.EXTCRIT(member) 
_ 7 View REXX 
_ 8 Execute REXX *** INTERACTIVE_LOAD MODE ACTIVE *** 


REFERENCE (REF)
Returns to your load reference list file to start another load request. Refer to Figure 226 on page
413 for more information.

REQUEST (REQ)
Returns to a saved load request file to start another load request. Refer to Figure 230 on page 417
for more information.

The REF and REQ commands are not available for the “Continue With Load”
Extract option.

SQLID
Enter the SQLID primary command to change or view the Db2 SQLID for the current load
session. Each load session starts with the default SQLID as specified in the load profile (see also
Default SQLID on page 65). In the Set SQLID window, enter the desired SQLID. USER is a valid
entry and changes the SQLID to match the current userid. If you blank out the SQLID, it defaults
to the SQLID as specified in the load profile.

Load Object Specifications

The Load Object Specifications screen shown in Figure 238 is displayed when you select Option 1
from the Load Menu.
426 File-AID/RDX Reference

Figure 238. Load Object Specifications

File-AID/RDX --------------- Load Object Specification ------------------------

Command ===> 

Specify Target DB2 Environment: 
SSID ===> DSN 
Location ===> DSNLOCAT
DB2 Load Method ===> DB2 (SQL = SQL Insert Statement;
DB2 = IBM DB2 Batch Load Utility)
Preserve Temporal ===> N Retain original temporal time data?
(Y/N) 
Specify Object Name Modifiers: (/ entry to apply modification)
_ DB2 Creator ===> TSOID01 (Creator for ALL DB2 objects)
_ DB2 Index name prefix ===> 
_ DB2 Index name suffix ===> 
_ MVS high level qualifier ===> TSOID01 (HLQ for ALL MVS objects)
_ MVS file name suffix ===> NEW 

_ Revert to source names ===> (D = DB2 objects; 
M = MVS objects; 
B= Both)


Use this screen to specify information about the objects (location, subsystem, creator, tables, and
index name modifier for Db2 objects, high level qualifier and file name modifier for MVS objects) to
which data from the extract file will be loaded. You also specify which load method (Db2 load utility
or SQL Insert) to use for the load of Db2 data.

Specify Target DB2 Environment Area

SSID
Specify the name of the Db2 subsystem to which Db2 data will be loaded. If you leave the
Location field blank, the tables you specify to be loaded must exist in the Db2 subsystem
displayed in this field.

Location
Specify the location of the tables you want to load if they are in a remote Db2 subsystem. The
location you enter must be defined in the Db2 system catalog table SYSIBM.LOCATIONS. You
must use the SQL Insert Load Option to use the remote location.

Leave this field blank if the tables you want to load reside in the Db2 subsystem displayed in the
target SSID field.

DB2 Load Method

Specify whether you want to load Db2 data using SQL INSERT statements or the IBM Db2 Batch
Load Utility. See also SQL Insert and Db2 Load Utility Load Options on page 429.

SQL

Perform the load using SQL INSERT statements. This option allows you to update rows if they
already exist.

DB2
Load 427

Perform the load using the IBM Db2 Batch Load Utility.

Interactive mode is not allowed with Db2 Load Utility.

Preserve Temporal
Specify whether to generate the PERIODOVERRIDE clause when Db2 loads data to SYSTEM
TEMPORAL tables.

For all SYSTEM TEMPORAL tables in this load, preserve the contents of the source base and
history table regarding the versioning timestamp columns, ignoring the GENERATE ALWAYS
clause.

For all SYSTEM TEMPORAL tables in this load, adhere to the GENERATE ALWAYS clause on
the versioning timestamp columns, consequently updating those columns as the rows are
loaded.

DB2 Load Method (see DB2 Load Method on page 426) must be set to Db2
for Temporal Table support.

Specify Object Name Modifiers

The following fields allow you to apply global object name modifiers.

Initially, these modifiers are set as specified in your profile or load request file and have already been
applied to the current load request. In order to change to new modifier values, type the new modifier
value, then enter the / (slash) in front of the field(s) to select the desired modifier(s). The selected
modifiers are applied when you enter the END command, after the Revert to source names option, if
also selected.

DB2 Creator
Specify the authorization ID of the owner of the Db2 target tables. The value in this field defaults
to the last value used or entered in your current profile. If you enter a value in this target DB2
Creator field, File-AID/RDX globally updates all DB2 Target table entries with this value. To
retain the creator ID from the extract file do not select (slash) this field, but slash the Revert to
source names option.

The Db2 load utility does NOT support enclosing lowercase creator IDs with
quotes.

DB2 Index name prefix

Specify the prefix to be added to the index names in the target environment. Leave blank if you
don’t want to specify a prefix.
428 File-AID/RDX Reference

DB2 Index name suffix

Specify the suffix to be added to the index names in the target environment. Leave blank if you
don’t want to specify a suffix.

If an index were named XDEPT1, adding a prefix of T would make the new index name
T_XDEPT1, adding a suffix of T would make it XDEPT1_T, adding both prefix and suffix would
make it T_XDEPT1_T.

Do not select (slash) the prefix or suffix field but select (slash) the Revert to source names option
to preserve the index names as extracted.

MVS high level qualifier

Specify the high level qualifier for the MVS target files. The value in this field defaults to the last
value used or entered in your current profile. If you enter a value in this target high level qualifier
field, File-AID/RDX globally updates all MVS target file name entries with this value. To retain the
high level qualifier as specified in the extract file do not select (slash) this field but slash the
Revert to source names option.

MVS file name suffix

Specify the suffix you want to add when creating MVS files in the target environment.

If a file were named FRSAMP.PARTTABL, adding a suffix of TEST would make the new file name
FRSAMP.PARTTABL.TEST.

Do not select (slash) the MVS suffix field but slash the Revert to source names option to retain
the file name as specified in the extract file.

Remember that the pre- and suffix modifiers are added to the current values,
so also select Revert to source names to change previously applied pre- and
suffixes. File-AID/RDX will remove the previously applied pre- and suffixes
and then add the new ones.

Revert to source names

Specify which object types should have all their target object names reverted to the names as
specified in the extract file:

(MVS objects only) File-AID/RDX reverts all MVS object names to the source names as
specified in the extract file.

(Db2 objects only) File-AID/RDX reverts all Db2 object names to the source names as
specified in the extract file.

(Both Db2 and MVS objects) File-AID/RDX reverts all object names to the source names as
specified in the extract file.

When Revert to source names is slashed all object names of the specified object type(s) revert to
the extracted (source) names. If any other modifier items are slashed they will be applied after the
source revert.
Load 429

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

SQLID
Enter the SQLID primary command to change or view the Db2 SQLID for the current load
session. Each load session starts with the default SQLID as specified in the load profile (see also
Default SQLID on page 65). In the Set SQLID window, enter the desired SQLID. USER is a valid
entry and changes the SQLID to match the current userid. If you blank out the SQLID, it defaults
to the SQLID as specified in the load profile.

SQL Insert and Db2 Load Utility Load Options

File-AID/RDX enables you to specify whether the load is performed using SQL INSERT statements or
the Db2 Load utility. You can use either method to load data to new tables, empty tables, or tables
that contain data. Either method allows you to delete all existing rows or add rows to tables that
contain data.

Use SQL Insert when any of the following are true:

• You want to be able to update existing rows.

• You have limited Db2 authorities. SQL Insert requires only INSERT, UPDATE, and possibly
DELETE privileges.
• You want to insert data into single table views.
• You want to insert data into tables at remote locations.
• Tables must be available for other applications to access when File-AID/RDX is loading data.
• You want to insert data into tables or views for lowercase creator IDs enclosed with quotes.

Use Db2 LOAD when any of the following are true:

• You have a large quantity of data to load and require a faster method for loading the data.
• You want to load to tables in a cyclical relationship.
• You want to load to TEMPORAL tables.

Source to Target Mapping

The Source to Target Mapping screen shown in Figure 239 is displayed when you select Option 2 from
the Load Menu.

Figure 239. Source to Target Mapping

File-AID/RDX ----------- Source to Target Mapping ----------------------------

Command ===> SCROLL ===> PAGE 

Primary Commands : Change, EXclude, Unexclude
Line Commands : X = Exclude U = Unexclude S = select for column mapping 

Extract File: TSOID01.FRSAMP.EXTRACT 

CMD Source / Target Type Status 
--- ---------------------------------------------------- ----- ---------------- 
_ 'FR.FRSAMP.INVOICE' FILE 
'FR.FRSAMP.INVOICE' 
_ FRSAMP.SUPPLIER_TABLE TABLE Objects differ 
TSOID01.SUPPLIER_TABLE 
_ FRSAMP.CUSTOMER_TABLE TABLE 
TSOID01.CUSTOMER_TABLE 
430 File-AID/RDX Reference

Use this screen to invoke the process of mapping columns between source and target objects. In this
list of objects you can also mark objects to be excluded from the load process. On this screen you can
also modify the target object names to which data in the extract file will be loaded.

After you complete this screen, use the END command to return to the Load Menu.

Upper Portion
The upper portion of this screen consists of the following fields:

Extract File
Displays the name of the file from which data will be loaded.

Lower Portion
If there are more target objects than can be listed on this screen, you can scroll the lower portion of
the screen up and down using standard scrolling commands. See Scrolling on page 31 for more
information.

The lower portion of this screen consists of the following fields:

CMD
Enter the S (Select) line command in this column to invoke the Column Mapping where you to
map source columns/fields to target columns/fields. See S (Select) on page 432 for more
information on the S line command. See Column Mapping on page 441 for more information on
the Column Mapping screen.

Enter the X (Exclude) line command for each object you want to exclude from the current load
(see X (Exclude) on page 432.

Enter the U (Unexclude) line command for each excluded object you want to include again in the
load process. (see U (Unexclude) on page 432).

Source
Displays the fully qualified name of each source object from which data was extracted. The
Source line is for display purposes only.

Target
Displays the names of the objects to be loaded with the data extracted from the source objects.
The target object names are prefilled based on the values specified on the Load Object
Specifications or Target Environment panels.

You can change the target names by

– modifying the values on the Load Object Specifications or Target Environment panels
– issuing the CHANGE command
– typing over each individual name in this column

To load data into a Db2 View:

First, you must have specified the SQL Db2 Load Option in the Load Object Specifications screen,
then you can enter the Db2 view name of the Target table, if you prefer to load the table using its
Load 431

view. The target view must already exist in the Target Environment. 
If the view does not exist, File-AID/RDX will create the view as a table.

The Db2 load utility does NOT support enclosing lowercase creator IDs with
quotes.

If you specify an object that does not currently exist, File-AID/RDX displays the message “Object
not found” in the Status column and will create it based on the extracted data. See Target
Environment Screen on page 451 for more information about the Target Environment option.

Type
The object type is indicated in the next column

• TABLE (Db2 table or view)

• FILE (MVS file)
• VSAM (VSAM cluster)
• IAM ($IAM cluster)

Status
Displays the status of target objects. File-AID/RDX can display any one of the messages listed in
Table 26. When there are multiple messages for an object, only the first is displayed.

Table 26. Target Objects Status Messages

Message Explanation
Object not found Indicates that the target object does not exist.
View not found Indicates that the view specified as a target table does not exist in the target
subsystem.

Note: For single table views, File-AID/RDX will create the view as a table. 
If you want to load using the view, create the target base table and view manually
before you can continue the load process. For the load to be successful the view
must be a single table view.
Objects differ Indicates that the source object and target object have columns or fields that have
different names, data types, or lengths; or, the MVS objects have different file
attributes, such as record lengths. Use the S (Select) line command to invoke the
Column/Field Mapping screen to map differing source and target columns/fields.
See S (Select) on page 432 for more information about the S line command. See
Column Mapping on page 441 for more information about the Column/Field
Mapping screen.
obj not fnd-DTD Indicates that the target table does not exist, yet matching distinct types (same
schema.name) do exist, however, their definitions (built-in types) differ from the
source UDTs. Use the S (Select) line command to invoke the Column Mapping
screen to map differing source and target columns. See S (Select) on page 432 for
more information about the S line command. See Column Mapping on page 441
for more information about the Column/Field Mapping screen.
obj not fnd-DTU Indicates that the target object does not exist, and the target system does not
support UDTs. File-AID/RDX will create a table using the UDTs built-in data types.
Use the S (Select) line command to invoke the Column Mapping screen to map
differing source and target columns. See S (Select) on page 432 for more
information about the S line command. See Column Mapping on page 441 for
more information about the Column/Field Mapping screen.
432 File-AID/RDX Reference

Table 26. Target Objects Status Messages (Continued)

Message Explanation
Tbls differ-DTU Indicates that the source object has columns with distinct data types (UDT), while
the target system does not support distinct data types. Use the S (Select) line
command to invoke the Column Mapping screen to map differing source and
target columns. See S (Select) on page 432 for more information about the S line
command. See Column Mapping on page 441 for more information about the
Column/Field Mapping screen.
Objects Mapped Indicates that for this pair of objects one or more columns or fields have been
mapped during this load session with the Column/Field mapping screen.
Excluded Indicates that for this pair of objects has been excluded from the load process.
Not Chg Indicates that the CHANGE command was not executed for this object as it would
have resulted in an invalid object name.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

S (Select)
The S (Select) line command invokes the Column Mapping (for Db2 tables) or Field Mapping (for
MVS objects) screen for the objects corresponding to the line on which you entered the
command. Use this command in the following situations:

• Source and target objects have columns or fields that have different names, lengths, or
data types.;
• Columns or fields were added to the target object or removed from the source object.;
• Source and target objects match, but source columns or fields need to be mapped to
different target columns or fields.
• You want to load default values for certain fields to protect sensitive data.

See Column Mapping on page 441 and Field Mapping on page 438 for more information about
the Column or Field Mapping screen, respectively.

X (Exclude)
Enter the X (Exclude) line command for each object you want to exclude from the current load.

Excluding tables from the Load process may compromise the referential
integrity of the tables involved. Negative SQL Codes may be returned if
tables are being created during the Load and RI relations exist.

U (Unexclude)
Enter the U (Unexclude) line command for each excluded object you want to include again in the
load process.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
Load 433

CHANGE (C)
The CHANGE command allows you to globally update the target names for Db2 tables or MVS
files. In the Change Command Window, specify the ‘from string’ and ‘to string’.

Change Command Window

When you enter the CHANGE command, File-AID/RDX displays the CHANGE Command
Window as shown in Figure 240. Enter the Change ‘from string’ and the Change ‘to string’ values,
then press END. File-AID/RDX will then change all matching strings in the target object names to
the new names.

Figure 240. Change Command Window



File-AID/RDX -------------- CHANGE COMMAND ------------------- 
Command ===> 

Change ALL occurrences of "from string" value to "to string" 
From string ===> 
To string ===> 


Press END to process, 



From string

Enter the current ‘From string’ (old) you want to replace in the object names.

To string

Enter the ‘To string’ (new) you want to replace the object names.

EXCLUDE (EX)
Enter the EXCLUDE command in the COMMAND field to exclude source/target objects from the
load. Use this command in conjunction with the U (Unexclude) line command or UNEXCLUDE
primary command when you have a long list of source/target objects displayed and you want to
include only a few source/target objects in the load.

File-AID/RDX preserves the hierarchy of the objects when excluding and unexcluding them. A
lower object cannot be unexcluded as long as its higher object is excluded. 
Example: You exclude all Db2 objects with the EXCLUDE primary command which also excludes
all databases, tablespaces, tables, and indexes, etc. Before you can unexclude a table with the
U line command, you must unexclude its database and tablespace with the U line command in
the Target Environment Screen as they are not displayed in this Source to Target Mapping screen
(see also EXCLUDE (EX) on page 456 and U (Unexclude) on page 463).

Valid parameters for EXCLUDE are:

DB2 MVS
INDEX VSAM
ALIAS AIX
SYNONYM PATH
VIEW NONVSAM
434 File-AID/RDX Reference

When entered without a parameter, EXCLUDE displays the Exclude Command Window. See
Figure 252 for an example.

Exclude Command Window

When you enter the EXCLUDE command without parameters, File-AID/RDX will display the
Exclude Command Window as shown in Figure 252. Select the object status types and object
types you want to exclude from the load.

Figure 241. Exclude Command Window

File-AID/RDX ------------------- Exclude Command --------------------------

Command ===> 

Objects Types to Exclude: Primary Commands:
All DB2 objects ===> Y (Y = Yes; N = No ; EXCLUDE DB2
Indexes ===> N E = EXCLUDE AND HIDE) EXCLUDE INDEX 
Aliases ===> N EXCLUDE ALIAS 
Synonym ===> N EXCLUDE SYNONYM 
Views ===> N EXCLUDE VIEW 

All MVS objects ===> N (Y = Yes; N = No ; EXCLUDE MVS 
VSAM ===> N E = EXCLUDE AND HIDE) EXCLUDE VSAM 
VSAM AIX ===> N EXCLUDE AIX 
VSAM PATH ===> N EXCLUDE PATH 
NON-VSAM ===> N EXCLUDE NONVSAM 


ENTER to process, END to return 

Select the object status and/or object types to exclude, then press END to exit the window.

Object Types to Exclude

All DB2 objects

Enter Y to exclude all Db2 objects from the load, including databases and tablespaces.

Enter E to exclude all Db2 objects from the load, including databases and tablespaces and
hide them from the display.

Enter N and all Db2 objects will not be excluded.

The exclude settings for the following Db2 object types are only activated
when Exclude All DB2 objects is set to N.

Indexes

Enter Y to exclude all Db2 indexes. Enter N to unexclude all Db2 indexes.

Aliases

Enter Y to exclude all Db2 aliases. Enter N to unexclude all Db2 aliases.

Synonyms

Enter Y to exclude all Db2 synonyms. Enter N to unexclude all Db2 synonyms.

Views

Enter Y to exclude all Db2 views. Enter N to unexclude all Db2 views.

All MVS objects

Load 435

Enter Y to exclude all MVS objects from the load.

Enter E to exclude all MVS objects from the load, including databases and tablespaces and
hide them from the display.

Enter N and all MVS objects will not be excluded.

The exclude settings for the following MVS object types are only activated
when Exclude All MVS objects is set to N.

VSAM

Enter Y to exclude all VSAM files. Enter N to unexclude all VSAM files.

VSAM AIX

Enter Y to exclude all VSAM alternate indexes. Enter N to unexclude all VSAM alternate
indexes.

VSAM PATH

Enter Y to exclude all VSAM paths. Enter N to unexclude all VSAM paths.

Non-VSAM

Enter Y to exclude all sequential (non-VSAM) files. Enter N to unexclude all sequential files.

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:

UNEXCLUDE (U)
Enter the UNEXCLUDE command in the COMMAND field to include all excluded source/target
objects in the load again. Use this command in conjunction with the X (Exclude) line command
or EXCLUDE primary command.

The optional parameters DB2, IMS, and MVS limit the UNEXCLUDE command to one of the
three object types.

File Mapping Specifications

The File Mapping Specifications screen shown in Figure 242 is displayed after you entered the S line
command for an MVS object in the previous screen, Source to Target Mapping on page 429.
436 File-AID/RDX Reference

Figure 242. File Mapping Specifications

File-AID/RDX ----------- File Mapping Specifications ------------------------

Command ===> 

Source Files Used: ’FR.FRSAMP.INVOICE’
Record Layout File ===> ’FR.FRSAMP.LAYOUT’
Record Layout Member ===> SMPINV
Record Layout Usage ===> S
XREF File ===>
XREF member ===>
IO Exit Name ===> 

Target File: ’FR.FRSAMP.INVOICE’ 

Specify the Target Record Layout Information
Record Layout File ===> ’FR.FRSAMP.LAYOUT’
Record Layout Member ===> SMPINV
Record Layout Usage ===> S
XREF File ===>
XREF member ===>
IO Exit Name ===>

Use this screen to specify the target record layout information so you can manually map the source
fields to the target fields. Press ENTER after you have specified the target file record layout
information.

Source Files Used Area

The upper portion contains the record layout information for the source file as found in the extract
file. The fields are for display only and cannot be changed.

Source Files Used

Displays the MVS file name of the source object.

Record layout file

Displays the record layout file that was used to extract data from the source MVS file.

Member name
Displays the member of the record layout file that was used to extract data from the source MVS
file.

Record layout usage

Indicates whether a single record layout (usage "S"), or an XREF (usage "X") was used when the
data was extracted.

XREF file name

Only displayed if layout usage is X. Identifies the XREF file name that was used to extract data
from the source MVS file.
Load 437

Member name
Displays the member of the XREF file that was used to extract data from the source MVS file.

I/O Exit Name

Displays the I/O Exit Name that was used to extract data from the source MVS file.

Target File Area

The lower portion allows you to specify the record layout information for the target file that you
want to use to map the source and target fields. The fields are prefilled with the record layout
information included in the extract file for the source file.

The specified target record layout information must already exist for File-AID/RDX to continue with
field mapping. If the target record layout information does not exist, File-AID/RDX will not allow
manual field mapping.

Target File
Displays the MVS file name of the target object as specified on the previous screen, Source to
Target Mapping on page 429.

Record layout file

Specify the record layout file to be used by File-AID/RDX to map the fields of the source MVS file
to the target file.

Member name
Specify the member name of the record layout file to be used by File-AID/RDX to map the fields
of the source MVS file to the target file.

Record layout usage

Specify whether a single record layout (usage "S"), or an XREF (usage "X") is to be used when
mapping the source fields to the target fields.

XREF file name

Must be specified if layout usage is X. Specify the XREF file name to be used to map source fields
to target fields.

Member name
Specify the member of the XREF file to be used to map source fields to target fields.

I/O Exit Name

Specify the I/O Exit Name that is to be used to map the source fields to the target fields.
438 File-AID/RDX Reference

Field Mapping
The Field Mapping screen shown in Figure 243 is displayed after you completed the File Mapping
Specifications screen. It is the MVS equivalent for the DB2 Column Mapping screen, see also Column
Mapping on page 441.

Figure 243. Field Mapping

File-AID/RDX Field Mapping

Command ===> SCROLL ===> CSR
Line Commands:
Use Field number to map columns S - Specify Literal Default Values
Blank - For field default value 

Source: FR.FRSAMP.INVOICE
CMD Parent Fields Type(Length)
---- ------------------------------- ------------------------------------------
1 IM-INV-NO FIXPIC(6)
2 IM-REC-TYPE CHAR(1)
3 FILLER CHAR(5)
4 IM-CUST-NO CHAR(6)
5 IM-BILL-CUST-NO CHAR(6)
TARGET: TSOID01.SAMP.INVOICE
CMD TARGET Fields Type(Length)
---- ------------------------------- ------------
___1 IM-INV-NO FIXPIC(6)
___2 IM-REC-TYPE CHAR(1)
__17 FILLER CHAR(5)
___4 IM-CUST-NO CHAR(6)
___5 IM-BILL-CUST-NO CHAR(6)

Use this screen to map fields between files in the following situations:

• Source and target objects have fields that have different names, lengths, or data types.;
• Fields were added to the target object or removed from the source object.;
• Source and target objects match, but source fields need to be mapped to different target fields.
• You want to load default literal values for certain fields to protect sensitive data.

See Column/Field Mapping Rules on page 448 for more detailed information about field to field
mapping.

The body of the Field Mapping screen consists of two portions: a source portion and a target portion.

Source Portion
The upper portion of this screen represents the source information and contains the following fields:

Source
Displays the full name of the source object from which data was extracted.

CMD
Displays File-AID/RDX-generated sequence numbers that indicate the source field numbers to be
used as input in the below target CMD field to map the source field to a target field.

Source Fields
Displays the names of the fields in the MVS source file.
Load 439

Type(Length)
Displays the source field’s data type. The length of the data is displayed in parentheses
immediately following the data type for CHAR, CH, VCHAR, VC, GRPH, VGRPH, DEC, FIXPIC,
National data types only.

Unicode Db2 character data types are identified as CH(x), VC(x) or LV(x) with a suffix of U16 or
U-8. Unicode character data from an MVS file is identified as N(x) U-16.

See Table 27 for more information about data types displayed in this column.

Table 27. Data Type Values

Data Type Value
CHAR or CH Fixed-length character strings less than or equal to 254 characters.
VCHAR or VC Variable-length character strings less than or equal to the field length specified when the column
is created. Maximum allowable field length is 4056 characters for 4k pages and 32,714 characters
for 32k pages.
LVCHAR or LV Variable-length character strings less than or equal to 4056 characters for 4k pages and 32,714
characters for 32k pages.
GRPH Fixed-length graphic strings less than or equal to 127 characters.
VGRPH Variable-length graphic strings less than or equal to the field length specified when the column is
created. Maximum allowable field length is 2028 characters for 4k pages and 16,357 characters
for 32k pages.
LVGRPH Variable-length graphic strings less than or equal to 2028 characters for 4k pages and 16,357
characters for 32k pages.
SMALLINT Fixed-length, binary integers in the range of -32,768 to +32,767, requiring two bytes of storage.
INTEGER Fixed-length, binary integers in the range of -2,146,483,648 to +2,147,483,467, requiring four
bytes of storage.
BIGINT Fixed-length, binary integers in the range of -9223372036854775808 to
9223372036854775807, requiring eight bytes of storage.
DEC Fixed-length, decimal numbers in the range of -10E15 to +10E15.
DECFLOAT Decimal Floating Point can be either DECFLOAT(16) or DECFLOAT(34) representing either 16 or
34 significant digits. The range of a DECFLOAT(16) number is 10-383 to 10+384 and the range of
a DECFLOAT(34) number is 10-6143 to 10+6144. A DECFLOAT(16) field occupies 8 bytes and a
DECFLOAT(34) occupies 16 bytes.
REAL Fixed-length, single-precision, floating-point numbers in the approximate range of 5.4E-79 to
7.2E+75.
DOUBLE Fixed-length, double-precision, floating-point numbers in the approximate range of 5.4E-79 to
7.2E+75.
DATE A three-part value (year, month, day) whose format is determined by DB2.
TIME A three-part value (hour, minute, second) whose format is determined by DB2.
TMSTMP(n) TIMESTAMP: A seven-part value (year, month, day, hour, minute, second, and precision) whose
format is YYYY-MM-DD-HH.MM.SS.TTTTTTTTTTTT. The precision value (TTTTTTTTTTTT) is
variable length and has 0 to 12 digits (up to picosecond) with a default of 6 (microsecond).
TMSTMP(n) specifies the scale (length) with n = 0 through 12. For DB2 Versions prior to Version
10, the length is always 6.
TMESTZ(n) TIMESTAMP WITH TIME ZONE: An eight-part value (year, month, day, hour, minute, second,
precision, time zone) whose format is YYYY-MM-DD-HH.MM.SS.TTTTTTTTTTTT±HH:MM. The
precision value (TTTTTTTTTTTT) is variable length and has 0 to 12 digits (up to picosecond) with
a default of 6 (microsecond). The time zone is the difference in hours and minutes between local
time and UTC. The range of the hour offset is -12 to +14, and the minute offset is 00 to 59. The
time zone is specified in the format ±th.tm, with values ranging from -12.59 to +14.00. TMESTZ(n)
specifies the scale (length) with n = 0 through 12. DB2 Version 10 and higher only.
440 File-AID/RDX Reference

Table 27. Data Type Values (Continued)

Data Type Value
CLOB A character large object (CLOB) is a varying-length string with a maximum length of 2 147 483
647 bytes (2 gigabytes minus 1 byte).
DBCLOB A double-byte character large object (DBCLOB) is a varying-length string with a maximum length
of 1 073 741 823 double-byte characters.
XML A data type for storage of well formed XML documents.
BLOB A binary large object (BLOB) is a varying-length string with a maximum length of 2 147 483 647
bytes (2 gigabytes minus 1 byte).
BINARY BINARY is a fixed length binary string which extends the support for binary strings beyond BLOBs.
Length attribute must between 1 and 255 inclusive.
VARBINARY VARBINARY is a variable length binary string which extends the support for binary strings beyond
BLOBs. Length attribute must between 1 and 32704.
ROWID Row identifier. A value that uniquely identifies a row. If a table contains a large object it must also
have a ROWID column.
HEXADEC Fixed length string, supported as a string only.
FLTPIC Fixed length character string representing a floating point value.
FIXPIC Fixed length character string representing a decimal or integer value.
N (National) Unicode data from an MVS file in COBOL is identified as PIC N or USAGE NATIONAL. This is UTF-
16, CCSID=1200. Identified as N(x) U-16.

Target Portion
The target portion of the Field Mapping screen contains the following information:

TARGET
Displays the full name of the target object to be loaded with the extracted data.

CMD
Enter a field number in the CMD column next to a target field name to map a source field to that
target field. If source and target fields’ names, data types, and lengths match, File-AID/RDX
prefills the CMD fields automatically.

Blank out this field or leave this field blank if you want default values assigned to the target field
when the record is inserted or loaded.

Enter the number (Lnn) of an existing literal definition to assign it directly to a target field, or
enter the S line command to access the Default Value Definition screen (see Figure 245 on page
445). Most likely, you will use literal definitions when the extracted file does not contain any
values for a particular field or you want to mask certain fields to protect sensitive data.

See Column/Field Mapping Rules on page 448 for more information about rules that govern field
mapping.

Target Fields
Displays a list of fields contained in the target file.
Load 441

Type(Length)
Displays the data type and length for each target field.

Primary Commands

CANCEL
Terminates the Field Mapping screen and returns you to the Source to Target Mapping without
saving your mapping selections. There are no operands associated with this command.

END
Terminates the Field Mapping screen and returns you to the Source to Target Mapping with your
specified field mappings intact. There are no operands associated with this command.

Line Commands
The following line commands are valid on this screen:

Field-number
Indicates which source field will be mapped to a particular target field. Enter a File-AID/RDX-
generated field number (from the source CMD column) into the target CMD column next to the
target field to which you want to map the source field.

S (Select)
Indicates that you want to set every record to be loaded of the selected field to a literal value.
When you press Enter, File-AID/RDX displays the Default Value Definition screen so you can
specify the desired value (see Default Value Definition on page 444). The literal can be up to 50
bytes long.

Lnn (Literal Definition Number)

Enter a previously defined literal definition number when you know that it contains the desired
literal value for the selected column. In that case, File-AID/RDX skips Default Value Definition
screen. To view or change the literal value, use the S line command instead. (see Default Value
Definition on page 444).

Column Mapping
The Column Mapping screen shown in Figure 244 is displayed when you enter the S (Select) line
command for a pair of Db2 tables on the Source to Target Mapping.
442 File-AID/RDX Reference

Figure 244. Column Mapping

File-AID/RDX ----------------- Column Mapping -------------------------------

Command ===> SCROLL ===> CSR
SSID: DSN
Source Table: Target Table:
TSOID01.CUSTOMER_TABLE TSOID02.CUSTOMER_TABLE 

Line Commands:
Use Column Number to map columns S - Specify/display column values
Blank - For column default value 

Column
Number Source Columns Type(Length) CMD Target Columns Type(Length)
------- ------------------ ------------ --- ------------------ ------------
1 CUSTOMER_NAME CHAR(6) ___ CUSTOMER_NAME CHAR(6)
2 LOCATION_ID CHAR(2) __2 LOCATION_ID CHAR(2)
3 COMPANY_NAME CHAR(30) __3 COMPANY_NAME CHAR(30)
4 CARE_OF CHAR(30) ___ CARE_OF CHAR(30)
5 ADDRESS CHAR(30) ___ ADDRESS CHAR(30)
6 CITY CHAR(25) ___ CITY CHAR(25)
7 STATE CHAR(2) ___ STATE CHAR(2)
8 ZIP_CODE CHAR(9) ___ ZIP_CODE CHAR(9)

Use this screen to map columns between Db2 tables in the following situations:

• Source and target tables have columns that have different names, lengths, or data types.;
• Columns were added to the target table or removed from the source table.;
• Source and target tables match, but source columns need to be mapped to different target
columns.
• You want to load Db2 default values for certain fields to protect sensitive data.
• You want to load default literal values for certain fields to protect sensitive data.

See Column/Field Mapping Rules on page 448 for more detailed information about column to
column mapping.

The body of this screen consists of an upper portion and a lower portion:

Upper Portion
The upper portion of this screen consists of the following fields:

Source Table
Displays the table name from which data was extracted. When loading from a remote location,
the table name is in three parts (location.creator.table). Source columns are listed in the Source
Columns field.

Target Table
Displays the name of the table to be loaded. When loading to a remote location, the table name
is in three parts (location.creator.table). Target columns are listed in the Target Columns field.

Lower Portion
The lower portion of this screen consists of the following columns:
Load 443

Column Number
Displays a list of File-AID/RDX-generated column numbers that correspond to the columns in the
source table. Enter these numbers in the CMD column to map source columns to target columns.

A column without a column number indicates that it is not eligible for

column mapping, for example columns with Large Object Type (CLOB,
BLOB, DBCLOB) and/or ROWID.

Source Columns
Displays a list of the columns contained in the source table.

Type(Length)
Displays the data type and length for each source column (see also Table 27 on page 439).

CMD
Enter a column number in the CMD column next to a target column name to map a source
column to that target column. If source and target columns’ names, data types, and lengths
match, File-AID/RDX fills in this field automatically.

Blank out this field or leave this field blank if you want default values assigned to the target
column when the row is inserted or loaded.

Enter the number (Lnn) of an existing literal definition to assign it directly to a target column, or
enter the S line command to access the Default Value Definition screen (SQL Load Option only,
see Figure 245 on page 445). Most likely, you will use literal definitions when the extracted table
does not contain any values for a particular column or you want to mask certain column fields to
protect sensitive data.

See Column/Field Mapping Rules on page 448 for more information about rules that govern
column mapping.

Target Columns
Displays a list of columns contained in the target table.

Type(Length)
Displays the data type and length for each target column.

1. If a Db2 column is a distinct type (UDT) File-AID/RDX displays either

its name or its built-in column type. Use the UDTSWAP command to
switch the displayed type.
2. Columns with Large Object Type (CLOB, BLOB, DBCLOB) and/or
ROWID column types are not eligible for mapping.
3. BINARY columns must have the same length.
444 File-AID/RDX Reference

Primary Commands

CANCEL (CAN)
Terminates the Column Mapping screen and returns you to the Object Load Specification screen
without mapping columns. There are no operands associated with this command.

END
Terminates the Column Mapping screen and returns you to the Object Load Specification screen
with column mappings intact. There are no operands associated with this command.

UDTSWAP (UDTS)
Swaps the display for distinct type columns from UDT name to the built-in data type and length
and vice versa.

Line Commands
The following line command is valid on this screen:

column-number
Indicates which source column will be mapped to a particular target column. Enter a File-
AID/RDX-generated column number (from the Column Number column) in the CMD column
next to the target column to which you want to map a source column.

S (Select)
SQL Load Option only. Indicates that you want to set every row to be loaded of the selected
column to a literal value. When you press Enter, File-AID/RDX displays the Default Value
Definition screen so you can specify the desired value (see Default Value Definition on page 444).
The literal can be up to 50 bytes long.

Lnn (Literal Definition Number)

SQL Load Option only. Enter a previously defined literal definition number when you know that
it contains the desired literal value for the selected column. In that case, File-AID/RDX skips
Default Value Definition screen. To view or change the literal value, use the S line command
instead. (see Default Value Definition on page 444).

Default Value Definition

The Default Value Definition screen shown in Figure 245 displays when you enter the S (Select) line
command for a Db2 target column or MVS target field in either the Column or Field Mapping screen.
Load 445

Figure 245. Default Value Definition

File-AID/RDX ------------- Default Value Definition --------- ROW 1 TO 4 OF 4

Command ===> SCROLL ===> CSR 

Target Column Name: CITY
Target Column Type: CHAR(25) 

Line Commands:
S - Select an existing definition D - Delete an existing definition
A - Add a new definition U - Update an existing definition 

CMD Number Type(Length) Value
--- ------ ------------ ---------------------------------------------------
_ L01 CHAR(25) FARMINGTON HILLS
_ L02 DEC(9,2) 600.00
_ L03 CHAR(9) 48334-2564
_ L04 VCHAR(12) MISSING
******************************* BOTTOM OF DATA *******************************

This screen shows all existing literal definitions. Using the line commands you can Add, Delete, or
Update literal definitions. When the desired literal definition has been defined, Select it so the literal
value will be used for the listed target column.

The body of this screen consists of an upper portion and a lower portion:

Upper Portion
The upper portion of this screen consists of the following fields:

Target Column Name

Displays the column or field name for which the literal definition is to be applied.

Target Column Type

Displays the data type and length for the target column or field.

Lower Portion
The lower portion of this screen consists of the following columns:

CMD
Enter a line command in the CMD column next to a literal definition. See Line Commands for a
description of the available commands.

Number
Displays the number of the literal definition. Literal numbers are assigned automatically when
creating the definition with the Add command. The letter L identifies the number as a literal
definition. You can define up to 99 literals.

Type(Length)
Displays the data type and length of the literal definition. The literal’s data type and length must
match the target column’s type and length (see also Column/Field Mapping Rules on page 448).
446 File-AID/RDX Reference

Value
Displays the contents of the literal definition. Use the LEFT and RIGHT scroll commands to view
values larger than the display width.

Primary Commands

CANCEL (CAN)
Terminates the Default Value Definition screen and returns you to the Column or Field Mapping
screen. There are no operands associated with this command.

END
Terminates the Default Value Definition screen and returns you to the Column or Field Mapping
screen with the selected literal definition assigned to the column or field. There are no operands
associated with this command.

Line Commands
The following line commands are valid on this screen:

S (Select)
Selects the current literal definition. When you press Enter File-AID/RDX returns to the Column
or Field Mapping screen and assigns the selected literal definition to the target column/field. The
literal value has to fit the target column/field’s type and cannot exceed its length. The defined
literal can now be mapped to any other Target Column/Field by its Column/Field Number. See
also Figure 248 on page 450.

A (Add)
Creates a new literal definition and pops up the Default Value Specification window (see Figure
246 on page 447). File-AID/RDX creates the number automatically. The number is always
preceded by the letter L, identifying it as a literal definition. The Type and Length fields are
preset to the same values as the target column/field type and length. Enter the desired value and
press Enter to finish the literal definition.

D (Delete)
Deletes an existing literal definition. When you enter the D line command File-AID/RDX pops up
the Delete Value Confirmation window (see Figure 247 on page 448). Answer YES to continue
your delete request, or enter NO to cancel the delete operation. If the value to be deleted is
currently mapped to a target column/field, Delete will remove the definition and all of its
mappings.

U (Update)
Allows you to modify an existing literal definition. It pops up the Default Value Specification
window (see Figure 246 on page 447) with the current values prefilled. Change the value as
desired and press Enter to change the literal definition.
Load 447

Default Value Specification

The Default Value Specification window shown in Figure 246 pops up when you enter either the A
(add) or U (update) line command for a literal definition in the Default Value Definition screen.

Figure 246. Default Value Specification

File-AID/RDX ------------- Default Value Definition --------- ROW 1 TO 4 OF 4 

Command ===> SCROLL ===> CSR 
Default Value Specification 
Target Co 
Target Co Command ===> 

Line Comm Number: L05 
S - Sel 
A - Add Type ===> INTEGER 
Length ===> 
CMD Numb Value ===> 
--- ---- 
_ L01 
_ L02 DEC(9,2) 600.00 
_ L03 CHAR(9) 48334-2564 
A L04 VCHAR(12) MISSING 
******************************* BOTTOM OF DATA ******************************* 


This window lets you add or modify the value for a literal definition. If you update the definition, the
current values are prefilled. When creating a new definition the Value field is blank.

Enter END after you completed the value specification to save the value specification and return to
the Default Value Definition screen.

The body of this window consists of:

Number
Displays the number of the literal definition. Literal numbers are assigned automatically when
creating the definition with the Add command. You can define up to 99 literals.

Type
Displays the column data type of the literal definition. If you add a new definition, the target
column’s data type is prefilled. Change the data type as needed. See also Table 27 on page 439.
When you assign the literal to a target column, the type must be compatible with the target
column’s type and length.

Length
Displays the column length of the literal definition. When you assign the literal to a target
column, the length must be compatible with the target column’s type and length (see also
Column/Field Mapping Rules on page 448). Change the length as needed.

Value
Enter or change the contents of the literal definition. When you assign the literal to a target
column, the value must be compatible with the target column’s type and length (see also
Column/Field Mapping Rules on page 448).
448 File-AID/RDX Reference

Delete Literal Confirmation

When you enter the D (delete) line command for a literal definition in the Default Value Definition
screen, File-AID/RDX displays a confirmation window as shown in Figure 247.

Figure 247. Delete Value Confirmation

File-AID/RDX ------------- Default Value Definition --------- ROW 1 TO 4 OF 4 

Command ===> SCROLL ===> CSR 
Default Value Specification 
Target Co 
Target Co Command ===> 

Line Comm Number: L05 
S - Sel 
A - Add Type ===> CHAR 
Length ===> 9 
CMD Numb Value ===> 48334-2564 
--- ---- 
_ L01 
_ L02 
D L03 E387 END to DELETE this value or CANCEL to cancel this action - 
_ L04 
******************************* BOTTOM OF DATA ******************************* 

The Delete Value Confirmation window warns you about the consequences of deleting a literal
definition and gives you the opportunity to cancel your delete request. Enter either END or CANCEL
command.

CANCEL
Cancels the deletion

END
Continues the delete operation.

Column/Field Mapping Rules

File-AID/RDX enables you to map Db2 columns or MVS fields of different types and lengths. The
following sections outline the rules that govern column/field mapping.

Data Type Compatibility

File-AID/RDX enables you to map a column or field containing one type of data to a column
containing a different type of data. Table 28 outlines which data types are compatible.

Table 28. Column/Field Mapping Data Type Compatibility

Target Data Types
Source Data
LVCHAR or LV
VCHAR or VC

N (National)

Types
CHAR or CH

DECFLOAT
SMALLINT

HEXADEC
TMSTMP
INTEGER

DOUBLE
LVGRPH

TMESTZ
BINARY
BIGINT
VGRPH

FLTPIC
FIXPIC
GRPH

DATE
TIME
REAL
DEC

CHAR or CH X X X X
VCHAR or VC X X X X
LVCHAR or
X X X X
LV
Load 449

Table 28. Column/Field Mapping Data Type Compatibility (Continued)

Target Data Types
Source Data

LVCHAR or LV
VCHAR or VC

N (National)
Types

CHAR or CH

DECFLOAT
SMALLINT

HEXADEC
TMSTMP
INTEGER

DOUBLE
LVGRPH

TMESTZ
BINARY
BIGINT
VGRPH

FLTPIC
FIXPIC
GRPH

DATE
TIME
REAL
DEC
GRPH X X X
VGRPH X X X
LVGRPH X X X
SMALLINT X X X X
INTEGER X X X X
BIGINT X X X X
DEC X X X Xa X X X
REAL X X X
DOUBLE X X X
DECFLOAT X X X
DATE X
TIME X
TMSTMP X X X X
TMESTZ X X X
BINARY X
FLTPIC X
FIXPIC X
HEXADEC X
N (National) X

a. For Db2 Utility load, the precision and scale of the target must match the source

Character and Graphic Data

For character data (CHAR, VCHAR, and LVCHAR) and graphic data (GRPH, VGRPH, and LVGRPH),
the following applies:

• If the length of the source column is greater than the length of the target column/field, data is
truncated on the right to a length equal to the target column/field.
• If the length of the source column/field is less than the length of the target column/field, the
data is padded on the right with blanks.

Numeric Data
For numeric data (SMALLINT, INTEGER, BIGINT, DECIMAL, DECFLOAT, and FLOAT) the source data
value must not be greater than the defined target data type. If the source data value is greater, then
the columns cannot be mapped. Table 29 lists the numeric data Type Value Ranges.

Table 29. Numeric Data Type Value Ranges

Data Type Value Range
SMALLINT -32768 to +32767
INTEGER -2,147,483,648 to +2,147,483,647
450 File-AID/RDX Reference

Table 29. Numeric Data Type Value Ranges (Continued)

Data Type Value Range
BIGINT -9223372036854775808 to 9223372036854775807
DEC -999999999999999 to +999999999999999
DECFLOAT(16) 10-383 to 10+384
DECFLOAT(34) 10-6143 to 10+6144
FLOAT 5.4E-79 to 7.2E+75

Miscellaneous Rules
In addition to the rules regarding data type and column length, the following miscellaneous rules
apply:

• If you are using the Db2 LOAD Utility and a column for which the CMD field is blank is defined
as NOT NULL, File-AID/RDX will display an error message to notify you to use the SQL INSERT
option.
• Unmapped columns/fields from the source table that do not exist in the target object are not
loaded.
• Submitting existing load JCL with load control tables that include IDENTITY columns does not
require column remapping even when additional columns have been added to the target table.
• Any additional columns added to the target table will require default values to be defined to Db2.
• If you leave the CMD field blank and the target column is defined as NOT NULL WITH DEFAULT,
File-AID/RDX will use the Db2 default.
• If you leave the CMD field blank and the target column is defined as NULL, the default is NULL.
• If you are using the Db2 LOAD Utility and a source column that allows NULLs matches a target
column that does not, File-AID/RDX will not automatically map the two columns.
• If you are using the Db2 LOAD Utility and a target column is defined as NOT NULL, you must
map a source column to it.

Column Mapping Example

The Column Mapping screen shown in Figure 248 is displayed after you selected some literals and
matched some Db2 source columns with Db2 target columns.

Figure 248. Db2 Column Mapping Screen After Some Column Assignments

File-AID/RDX ----------------- Column Mapping -------------------------------

Command ===> SCROLL ===> PAGE
SSID: DSN
Source Table: Target Table:
TSOID01.BASE_EMPLOYEE TSOID02.EMPLOYEE_ADD

Line Commands:
Use Column Number to map columns S - Specify default column value
Blank - For column default value 

Column
Number Source Columns Type(Length) CMD Target Columns Type(Length)
------- ------------------ ------------ --- ------------------ ------------
1 EMPNO CHAR(6) ___ EMPLOYEE_NUMBER CHAR(6)
2 FIRSTNAME VCHAR(12) __2 FIRSTNAME VCHAR(12)
3 LASTNAME VCHAR(15) L04 MIDNAME VCHAR(12)
4 HIREDATE DATE __3 LASTNAME VCHAR(15)
___ SEX CHAR(1)
___ BIRTHDATE DATE
* End of Columns * ___ PHONENO CHAR(4)
__4 HIREDATE DATE
L05 BONUS INTEGER
Load 451

In the example shown in Figure 248 the extracted source table has four (4) columns. The literal
definitions L04 and L05 were added during the current column mapping session. They can be
assigned to more than one target column. Columns 2, 3, and 4 were matched automatically to the
target columns with the same name, type and length.

The target table will be loaded with data from the

• Source columns 2, 3, and 4

• Literal definitions L04 and L05

See Column/Field Mapping Rules on page 448 for more detailed information about column to
column mapping.

Target Environment Screen

The Target Environment screen shown in Figure 249 is displayed when you select Option 3 from the
Load Menu. It displays all extracted objects as they will be loaded in the target environment. That
includes all changes to object names you made in Options 1 and 2 of the Load Menu. If the objects
don’t exist in the target environment, File-AID/RDX will create them as long as you have
authorization to create them. For Db2 objects, File-AID/RDX also requires that the extract file
includes the DDL captured during extract processing.

Initially, all objects are displayed. You may use the HIDE command to control which objects are
hidden from the display.

Figure 249. Target Environment

File-AID/RDX -------------- Target Environment ----------- Row 1 to 11 of 19

Command ===> Scroll ===> CSR
** RESET to remove filter **
Primary Commands: EXclude, SHow, Change, Find, REFRESH, Hide, Size, Print 
Line Commands: S = Select I = Info X = Exclude U = Undo Exclude 

Automatic space calculation ===> B (N = No; M = MVS; D = DB2; B = Both)
Create target environment only ===> N (N = No; Y = Yes)

Extract File: TSOID01.FRSAMP.EXTRACT 
SSID: DSN Location: LOCATION
Type Object Name SHOW Status C
--------- ---------------------------------------------- -------- -------- -
_ DATABASE TSOID04DB 
_ TBLSPACE CONTACTR Y
_ TABLE TSOID01.CONTACT_TABLE Y
_ INDX TSOID01.CONT_IDX Y
_ VIEW TSOID01.CONTACT_VIEW Y
_ TBLSPACE CUST1VBL 
_ TABLE TSOID01.CUSTOMER_TABLE 
_ TBLSPACE **IMPLICIT** 
_ TABLE TSOID01.ORDER_LINE_TABLE Y
_ INDX TSOID01.ORDL_IDX Y
_ VIEW TSOID01.ORDER_LINE_VIEW Y

For Db2 objects, use this screen to specify and modify the Db2 database, tablespace, and storage
group information for the Db2 tables and indexes to be loaded based on the extracted data. See
452 File-AID/RDX Reference

Generating CREATE DDL on page 463 for more information on how File-AID/RDX creates new Db2
tables.

1. File-AID/RDX only creates Db2 objects for which the complete DDL information
has been captured in the extract file.
2. If the extract file includes data extracted from Db2 views, File-AID/RDX will load
the view data into a target view only if the view already exists. If the target view
does NOT exist, File-AID/RDX will create the view as a Db2 table based on the
extracted CREATE VIEW DDL, without an index.
3. The auto-create feature of Load does not support creating Temporal Tables.
4. The auto-create feature of Load does not support creating multi-volume
datasets for any MVS dataset type.

For VSAM objects, use this screen to specify an alternate index, if the source MVS object has one. You
also have the choice to exclude non-primary indexes. File-AID/RDX does not support alternate
indexes for IAM files.

After completing the target environment information, press END to return to the Load Menu.

During the execution phase of the Load function, File-AID/RDX will attempt to create the object(s)
that are marked for creation as specified on this screen.

Global Settings
The upper portion of this screen allows you to specify settings that apply to all listed Db2 or MVS
objects.

Automatic Space Calculation

Specify whether you want File-AID/RDX to calculate the space allocation for new target objects
based on the extracted data or not. The calculated space will not exceed the space allocation of
the source. This field sets the status globally. You can also set the status for individual objects.
The plus (+) sign indicates that the status for one or more individual objects has been changed.

(No) The space allocation parameters for objects to be created will be the same as for the
source objects at their original creation.

(MVS objects only) File-AID/RDX will calculate the space allocation for new target MVS files
based on the extracted data.

(Db2 objects only) File-AID/RDX will calculate the space allocation for new target Db2
objects based on the extracted data.

(Both Db2 and MVS objects) File-AID/RDX will calculate the space allocation for new Db2
and MVS target objects based on the extracted data.

This field sets the status globally. You can also set the status for individual objects. The plus (+)
sign indicates that the status has been changed for one or more individual objects.

Automatic space calculation ===> B + (N = No; M = MVS; D = DB2; B = Both)

Load 453

Create Target Environment Only

Specify whether you want File-AID/RDX to only create the target objects or also load data into
the target objects.

(No) Loads the extracted data into the target objects.

(Yes) File-AID/RDX will only create the target objects without loading any of the extracted
data.

Lower Portion
The lower portion of this screen contains a list of Db2 and/or MVS objects in the target environment
corresponding to the extracted (source) objects. If there are more entries on the list than will fit in
the screen, you can scroll the fields in the lower portion of the screen up and down using standard
scrolling commands (see Scrolling on page 31).

Db2 objects to be loaded are listed in hierarchal and alphabetical order, starting with the database,
listing all tablespaces within that database, and all tables in the tablespace. If a table is to be created,
it also lists all indexes, views, aliases, and synonyms for the table.

Objects are only listed if they already exist in the target environment or the
extract file contains their create DDL (see also Capture create DDL during
extract for on page 340).

CMD
Enter the line commands in this column to edit the individual target objects.

Type
The object type is indicated in the next column:

– DATABASE indicates a Db2 database

– TBLSPACE indicates a Db2 tablespace
– TABLE indicates a Db2 table
– TABLE_SYS indicates a Db2 SYSTEM TEMPORAL table
– TABLE_BUS indicates a Db2 BUSINESS TEMPORAL table
– TABLE_BIT indicates a Db2 BI-TEMPORAL table
– TABLE_PAR indicates a Db2 partitioned table
– FILE indicates an MVS sequential file, including GDG types
– VSAM indicates an MVS VSAM KSDS file
– IAM indicates an IAM (Innovation Access Method) file
– AIX indicates an alternate index for an MVS object
– PATH indicates a VSAM Path

The following object types are only displayed if their corresponding table is marked to be created:

– INDX indicates a secondary index for a Db2 table

– IX_REQ indicates a required primary index for a Db2 table
– IX_PAR indicates a partitioned index for a Db2 table
– IX_P_REQ indicates a required partitioned index, either a primary, clustering, or index with
UniqueRule of 'C' or 'R'. Indexes with UniqueRule of 'C' are required to enforce constraints
and Indexes with a UniqueRule of 'R' are required for RI.
– IX_P indicates a secondary partitioned index for a Db2 table
454 File-AID/RDX Reference

– IX_DPSI indicates a data partitioned secondary index for a Db2 table

When creating an index: If the source is index-controlled, File-AID/RDX will

create with table- controlled partitioning.

– VIEW indicates a view for a Db2 table

– ALIAS indicates an alias for a Db2 table
– SYNONYM indicates a synonym for a Db2 table

Object Name
Displays the fully qualified name of the object to be loaded. If it is a Db2 table it includes the
creator ID of the owner of the table.

You can modify the entries in this column directly. Simply type the new name over the one
displayed or use the S line command. You can also modify the target object name in the Source to
Target Mapping screen (Load Option 2). There, you can modify the value in the Target field.

For Tablespace names only:

Do NOT Blank out the name of a tablespace to create the tablespace implicitly, instead select the
table with the S line command and blank out the Tablespace field in the Create DB2 Table panel.
File-AID/RDX generates DDL to create the tablespace implicitly as long as only one table is
associated with the tablespace. The current SQLID must have the proper Db2 authority to create
the tablespace in the execution phase.
**IMPLICT** also indicates that the extracted tablespace was derived from an implicit creation.

For Database names only:
File-AID/RDX does not support implicit Database creation; providing a Database name will
continue to be a requirement for Create Tablespace and Create Table.

SHOW
Displays the result of the SHOW primary command. Depending on the specified parameter, the
column name changes to and displays the associated Db2 DATABASE, STOGROUP, or
TABLESPACE for the appropriate Db2 objects. See SHOW on page 460 for the command
description and Figure 255 on page 462 for an example. This column is blank until you enter a
SHOW command.

Status
Displays a status message for the object to be loaded. See Table 26 for a list of possible messages
not listed in Table 30. When there are multiple messages for an object, only the first is displayed

Table 30. Object Status Messages

Message Explanation
N/A Indicates that the status of an object in the Target Environment has been
changed within another object specification. Use the REFRESH command
to redisplay the list in the correct new hierarchy.
Removed Indicates that an object in the Target Environment has been renamed to
an existing one that is already listed elsewhere on the panel. Use the
REFRESH command to redisplay the list in the correct new hierarchy.
XML CON. The XML conflict status indicates that the object to be created includes
an XML column. The creation of objects with an XML column is not
supported. Exclude the object or specify an existing object to continue
the load process.
Load 455

C
(Create Object) Displays a Y to indicate that the object will be created during the load process.
Blank indicates that the object already exists, or is an implicit tablespace.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

CHANGE (C)
The CHANGE command allows you to globally update the object names displayed in the list.
Specify the change’ from string’ and change ‘to string’ in the CHANGE Command Window.

CHANGE Command Window

When you enter the CHANGE command, File-AID/RDX displays the CHANGE Command
Window as shown in Figure 250. Enter the Change ‘from string’ and the Change ‘to string’ values
you want to change globally for all displayed object names, then press END to execute the change
and exit the window.

Figure 250. CHANGE Command Window



File-AID/RDX -------------- CHANGE COMMAND ------------------- 
Command ===> 

Change ALL occurrences of "from string" value to "to string" 
From string ===> 
To string ===> 


Press END to process, 



When the SHOW STOGROUP is in effect and you enter the CHANGE command, File-AID/RDX
displays the CHANGE Command Window as shown in Figure 251. Enter the Change ‘from string’
and the Change ‘to string’ values you want to change globally. In Field to Change, specify what
fields the change should act on, either O for all displayed object names, or S for stogroup names.
Then press END to execute the change and exit the window.

Figure 251. CHANGE Command Window with Stogroup Option



File-AID/RDX -------------- CHANGE COMMAND ------------------- 
Command ===> 

Change ALL occurrences of "from string" value to "to string" 
From string ===> 
To string ===> 

Field to change ===> O (O = Object Name; S = Stogroup Name) 

Press END to process, 


456 File-AID/RDX Reference

END
The END command returns to the Load Menu. There are no operands associated with this
command.

EXCLUDE (EX)
Enter the EXCLUDE command in the COMMAND line to exclude select target objects in the
displayed list. Use this command in conjunction with the U (Unexclude) line command or
UNEXCLUDE primary command when you have a long list of target objects displayed and you
want to include only a few target objects in the load.

File-AID/RDX preserves the hierarchy of the objects when excluding and unexcluding them.
A lower object cannot be unexcluded as long as its higher object is excluded. 
Example: You exclude all Db2 objects with the EXCLUDE primary command which also
excludes all databases, tablespaces, tables, and indexes, etc. Before you can unexclude a table
with the U line command, you must unexclude its database and tablespace with the U line
command.

Excluding objects may compromise the load process.

Valid parameters for EXCLUDE are:

DB2 MVS
INDEX VSAM
ALIAS AIX
SYNONYM PATH
VIEW NONVSAM

When entered without a parameter, EXCLUDE displays the Exclude Command Window. See
Figure 252 for an example.

Exclude Command Window

When you enter the EXCLUDE command without parameters, File-AID/RDX will display the
Exclude Command Window as shown in Figure 252. Select the object status types and object
types you want to exclude from the load.
Load 457

Figure 252. Exclude Command Window

File-AID/RDX ------------------- Exclude Command --------------------------

Command ===> 

Objects Types to Exclude: Primary Commands:
All DB2 objects ===> Y (Y = Yes; N = No ; EXCLUDE DB2
Indexes ===> N E = EXCLUDE AND HIDE) EXCLUDE INDEX 
Aliases ===> N EXCLUDE ALIAS 
Synonym ===> N EXCLUDE SYNONYM 
Views ===> N EXCLUDE VIEW 

All MVS objects ===> N (Y = Yes; N = No ; EXCLUDE MVS 
VSAM ===> N E = EXCLUDE AND HIDE) EXCLUDE VSAM 
VSAM AIX ===> N EXCLUDE AIX 
VSAM PATH ===> N EXCLUDE PATH 
NON-VSAM ===> N EXCLUDE NONVSAM 


ENTER to process, END to return 


Select the object status and/or object types to exclude, then press END to exit the window.

Object Types to Exclude

All DB2 objects

Enter Y to exclude all Db2 objects from the load. Enter N and all Db2 objects will not be
excluded.

The exclude settings for the following Db2 object types are only activated
when Exclude All DB2 objects is set to N.

Indexes

Enter Y to exclude all Db2 indexes. Enter N to unexclude all Db2 indexes.

Aliases

Enter Y to exclude all Db2 aliases. Enter N to unexclude all Db2 aliases.

Synonyms

Enter Y to exclude all Db2 synonyms. Enter N to unexclude all Db2 synonyms.

Views

Enter Y to exclude all Db2 views. Enter N to unexclude all Db2 views.

All MVS objects

Enter Y to exclude all MVS objects from the load. Enter N and all MVS objects will not be
excluded.

The exclude settings for the following MVS object types are only activated
when Exclude All MVS objects is set to N.

VSAM

Enter Y to exclude all VSAM files. Enter N to unexclude all VSAM files.
458 File-AID/RDX Reference

VSAM AIX

Enter Y to exclude all VSAM alternate indexes. Enter N to unexclude all VSAM alternate
indexes.

VSAM PATH

Enter Y to exclude all VSAM paths. Enter N to unexclude all VSAM paths.

Non-VSAM

Enter Y to exclude all sequential (non-VSAM) files. Enter N to unexclude all sequential files.

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.

HIDE (H)
Use the HIDE command to control which object types to hide from the displayed list. See also
RESET (RES) on page 460.

Valid parameters for HIDE and RESET are:

AC (AutoCreate) EXCLude
EXISTing ERR
DB2 TABle
INDex VSAM
ALIas AIX
SYNonym PATH
VIew NONVsam
TS (TableSpace)

When entered without a parameter, HIDE displays the Hide Command Window. See Figure 253
for an example.

HIDE Command Window

When you enter the HIDE command without parameter, File-AID/RDX will display the Hide
Command Window as shown in Figure 253. Select the object status types and/or object types you
want to hide from the display.
Load 459

Figure 253. Hide Command Window

File-AID/RDX ---------------------- HIDE COMMAND ------------------------------

Command ===> 

Allow objects with errors to be hidden? ===> N ( Y = Yes, N = No)

By Object Status: Primary Commands:
Auto-create objects ===> N ( Y = Yes, N = No) HIde Auto Create
Existing objects ===> Y HIde EXISTing
Excluded objects ===> Y HIde EXCLude 

By Object Type: 
Databases ===> N ( Y = Yes, N = No, R = Restore) HIde DataBase
Tablespaces ===> N HIde TableSpace
Tables ===> N HIde TABle 
Indexes ===> N ( Y = Yes, N = No) HIde INDex 
Aliases ===> N HIde ALIas 
Synonym ===> N HIde SYNonym 
Views ===> N HIde VIew 

VSAM ===> N ( Y = Yes, N = No, R = Restore) HIde VSAM 
VSAM AIX ===> N ( Y = Yes, N = No) HIde AIX 
VSAM PATH ===> N HIde PATH 
Non-VSAM ===> N HIde NONVsam 

Select the object status and/or object types to hide or redisplay, then press END to exit the
window.

Allow objects with errors to be hidden?

Enter Y to hide all objects that are marked with a special error status. Enter N to (re)display
all objects that are marked with a special error status.

By Object Status

Auto-create objects

Enter Y to hide all objects that File-AID/RDX will create during the load. Enter N to
(re)display all objects to be created.

Existing objects

Enter Y to hide all objects that already exist in the target environment. Enter N to (re)display
all existing objects.

Excluded objects

Enter Y to hide all objects that are excluded from the load. Enter N to (re)display all excluded
objects.

By Object Type

Databases

Enter Y to hide all Db2 databases. Enter N to (re)display all Db2 databases. Enter R (restore)
to redisplay only those hidden databases whose lower level objects are not hidden.

Tablespaces

Enter Y to hide all Db2 tablespaces. Enter N to (re)display all Db2 tablespaces. Enter R
(restore) to redisplay only those hidden tablespaces whose lower level objects are not hidden.

Tables
460 File-AID/RDX Reference

Enter Y to hide all Db2 tables. Enter N to (re)display all Db2 tables. Enter R (restore) to
redisplay only those hidden tables whose lower level objects are not hidden.

Indexes

Enter Y to hide all Db2 indexes. Enter N to (re)display all Db2 indexes.

Aliases

Enter Y to hide all Db2 aliases. Enter N to (re)display all Db2 aliases.

Synonyms

Enter Y to hide all Db2 synonyms. Enter N to (re)display all Db2 synonyms.

Views

Enter Y to hide all Db2 views. Enter N to (re)display all Db2 views.

VSAM

Enter Y to hide all VSAM files. Enter N to (re)display all VSAM files. Enter R (restore) to
redisplay only those hidden VSAM files whose lower level objects are not hidden.

VSAM AIX

Enter Y to hide all VSAM alternate indexes. Enter N to (re)display all VSAM alternate indexes.

VSAM PATH

Enter Y to hide all VSAM paths. Enter N to (re)display all VSAM paths.

Non-VSAM

Enter Y to hide all sequential (non-VSAM) files. Enter N to (re)display all sequential files.

REFRESH (R)
Refreshes the list of objects of the Target Environment screen (Figure 249 on page 451). Use the
REFRESH command after changes to the listed objects have an influence on the hierarchal and
alphabetical order of the display.

REPORT (REP)
Prints the logical contents of the display. This report includes all of the displayable lines
formatted like the current view.

RESET (RES)
Use the RESET command to return all hidden objects to the display. See also HIDE (H) on page
458 for a list of parameters.

SHOW
The SHOW command alters the contents of the SHOW column in the Target Environment screen
(Figure 249 on page 451). Depending on the specified parameter, the SHOW column can display
the associated database, tablespace or stogroup information for the appropriate Db2 objects in
the list. SHOW without a parameter displays the Show Command Window.
Load 461

Valid parameters for SHOW are:

NOne
STgroup
DB (DataBase)
TS (TableSpace)

SHOW Command Window

When you enter the SHOW command without parameters, File-AID/RDX displays the Show
Command Window as shown in Figure 254. Specify the parameter you want to display in the
SHOW column. None is the initial setting.

Figure 254. Show Command Window



File-AID/RDX ------------- SHOW COMMAND ---------------------- 
Command ===> 


Data to display Primary Command: 
in SHOW column ===> N ( N = None; SHow None 
S = Stogroup; SHow Stogroup 
D = Database; SHow DB 
T = Tablespace) SHow TS 




Specify which Db2 information you want to display in the SHOW column, then press END to exit
the window.

Data to display in SHOW column

N

(None) Clears or leaves the SHOW column empty.

(Stogroup) Displays the name of the Db2 storage group associated with the listed Db2
table or index.

(Database) Displays the name of the Db2 database associated with the listed Db2 table or
tablespace.

(Tablespace) Displays the name of the Db2 tablespace associated with the listed Db2
table.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 255 for an example. SIZE is a toggle switch so enter SIZE again to return to the
original format.
462 File-AID/RDX Reference

Figure 255. Target Environment - SIZE Screen with SHOW DATABASE

File-AID/RDX --------------- Target Environment ---------- Row 1 from 25 

Command ===> Scroll ===> CSR 
Type Object Name ** FILTERED LIST ** DATABASE Status C 
--------- ---------------------------------------------- -------- -------- - 
_ DATABASE FRTESTDB 
_ TBLSPACE CONTACTR FRTESTDB Y 
_ TABLE FRSAMP.CONTACT_TABLE FRTESTDB Y 
_ TBLSPACE CUSTOMER FRTESTDB 
_ TABLE FRSAMP.CUSTOMER_TABLE FRTESTDB 
_ TBLSPACE **IMPLICIT** FRTESTDB 
_ TABLE FRSAMP.ORDER_LINE_TABLE FRTESTDB Y 
_ TBLSPACE ORDERRTA FRTESTDB 
_ TABLE FRSAMP.ORDER_TABLE FRTESTDB 
_ TBLSPACE PARTRTAB FRTESTDB Y 
_ TABLE FRSAMP.PART_TABLE FRTESTDB Y 
_ TBLSPACE SUPPLIER FRTESTDB Y 
_ TABLE FRSAMP.SUPPLIER_TABLE FRTESTDB Y 
******************************* Bottom of data ********************************

UNEXCLUDE (UNEX)
Enter the UNEXCLUDE command in the Command line to include all excluded source/target
objects in the load again. Use this command in conjunction with the X (Exclude) line command
or EXCLUDE primary command when you have a long list of source/target objects displayed and
you want to reverse previous exclude commands.

See also EXCLUDE (EX) on page 456 for a list of parameters.

When entered without a parameter, UNEXCLUDE displays the “Unexclude Command Window”.
The window displays the same object types as the “Exclude Command Window”. See Figure 252
for an example.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

E (Edit)
(Obsolete, replaced by the S line command) Enter the E (Edit) line command for each object you
want to view or change. Depending on the object, File-AID/RDX will invoke the appropriate
Create/Edit screen.

I (Information)
The I (Information) line command display the statements that will be used to create the object.
For Db2 objects that will be the DDL, for MVS VSAM objects it will be the IDCAMS DEFINE, and
for non-VSAM it will be the DD statement. I is only valid for objects marked to be created.

S (Select)
Enter the S (Select) line command for each object you want to view or change. Depending on the
object, File-AID/RDX will invoke the appropriate Create/Edit screen.
Load 463

X (Exclude)
Enter the X (Exclude) line command for each object you want to exclude from the current load
request. Primary indexes may not be excluded.

Excluding objects may compromise the load process.

U (Unexclude)
Enter the U (Unexclude) line command for each excluded object you want to include again in the
Auto Create process.

Generating CREATE DDL

When DDL has been captured during extract for Db2 objects, File-AID/RDX generates DDL that
matches the source objects and puts it in the load JCL (member DB2CREAT in the control card PDSE).
This DDL is used to create new target objects during load. When building DDL, File-AID/RDX uses
certain information from the extracted tables as follows:

• Column information is used unaltered. File-AID/RDX does not create Distinct types (UDTs). If the
source UDT does not exist in the target system, File-AID/RDX will create the columns using only
the UDT’s built-in data type.
• FIELDPROC and VALIDPROC information is used in the CREATE DDL unaltered.
• Primary key information is used unaltered. File-AID/RDX generates an index that reflects the
primary key.
• The table name is modified to reflect the table name specified on the Target Environment screen.
• The IN statement is modified to reflect the database and tablespace specified on the Target
Environment screen.
• EDITPROC and OBID statements are not used to build the CREATE DDL.

File-AID/RDX saves foreign key information from extracted tables and adds it to new tables using
ALTER statements after the new tables have been created.

For all indexes for all tables in the extract file, File-AID/RDX uses certain information as follows:

• The index creator name is modified to match the table creator name specified on the Target
Environment screen.
• Column and cluster information is used unaltered.
• Partition information is used if the tablespace associated with the new table is partitioned.
Otherwise, partition information is ignored.
• The ON statement is modified to reflect the table name specified on the Target Environment
screen.
• USING information is used unaltered.
• USING information is not used to build the CREATE DDL.

After File-AID/RDX successfully creates all the tables and indexes, it executes ALTER statements to
add referential constraints. Constraints are added only to tables that are part of the load. Constraints
added to tables within the load are used unaltered.

Create/Edit Db2 Database

The Create Database screen shown in Figure 256 is displayed when you enter the S (Select) line
command on a Db2 database in the Target Environment screen. This screen lets you modify the
create database information from the extract file to your new target environment.
464 File-AID/RDX Reference

Figure 256. Create Database

File-AID/RDX ---------------- Create Database -------------------------------

Command ===> 

Source Object: SSID: DSN Location: DSNLOCATION
Database. . . : FRSAMPDB 

Target Object: SSID: DSN Location: DSNLOCATION

Database ===> FRSAMPDB 
STOGROUP ===> STG003 
BUFFERPOOL ===> BP0 
INDEXBP ===> BP0

Use this screen to update the target Db2 database information. After you view or modify the database
information, press END to return to the Target Environment screen.

When loading from an extract file created with a Release earlier than 4.0, the
database must already exist in the target environment.

Source Object

SSID
Displays the Db2 subsystem ID as specified in the extract file.

Location
Displays the remote Db2 location name as specified in the extract file.

Database
Displays the name of the source Db2 database as specified in the extract file.

Target Object

SSID
Displays the Db2 subsystem ID of the Target Environment.

Location
Displays the remote Db2 location name of the Target Environment.

Database
Specify the name of the Db2 database of the Target Environment. If the database does not exist in
the Target Environment, File-AID/RDX will create it during the load process.
Load 465

This field is prefilled with the database name specified in your current profile or, if none is in the
profile, with the database specified in the extract file. If you are using a saved load request, this
field is prefilled with the database specified in the load request.

For Database names only:

File-AID/RDX does not support implicit Database creation; providing a
Database name will continue to be a requirement for Create Tablespace and
Create Table.

STOGROUP
Specify the Db2 storage group in which the database resides. The storage group must already
exist. This field is prefilled with the storage group value specified in your profile or the extracted
storage group value.

BUFFERPOOL
Specify the Db2 buffer pool name associated with the database. This field is prefilled with the
extracted value.

INDEXBP
Specify the Db2 index buffer pool name associated with the database. This field is prefilled with
the extracted value.

Create/Edit Db2 Tablespace

The Create Tablespace screen shown in Figure 257 is displayed when you enter the S (Select) line
command on a Db2 tablespace in the Target Environment screen. This screen lets you modify the
create tablespace information from the extract file to your new target environment.

Figure 257. Create Tablespace

File-AID/RDX ---------------- Create Tablespace -------------------------------

Command ===> 

Primary Commands: PARTition, LimitKey 

Source Object: SSID: DSN Location: DSNLOCATION
Database. . . : FRSAMPDB 
Tablespace . : DEPTTS 
TS Type . : Partitioned NUMPARTS. . : 4

Target Object: SSID: DSN Location: DSNLOCATION
Database ===> FRSAMPDB 
Tablespace ===> DEPTTS 
TS Type ===> Partitioned NUMPARTS.===> 4

Automatic Space calculation ===> Y ( N = No; Y = Yes; M =Manual) 

STOGROUP ===> STOG003 BUFFERPOOL ===> BP0 
PROQTY(K) ===> 5 FREEPAGE ===> 0 
SECQTY(K) ===> 5 PCTFREE ===> 5 
466 File-AID/RDX Reference

Use this screen to update the Db2 tablespace information. After you view or modify the tablespace
information, press END to return to the Target Environment.

When loading from an extract file created with a Release earlier than 4.0, the
tablespace must already exist in the target database, or use the implicit
tablespace function.

Source Object

SSID
Displays the Db2 subsystem ID as specified in the extract file.

Location
Displays the remote Db2 location name as specified in the extract file.

Database
Displays the name of the source Db2 database as specified in the extract file.

Tablespace
Displays the name of the Db2 tablespace as specified in the extract file.

TS Type
Displays the tablespace type as specified in the extract file. See also Table 31. Valid types are:

Simple

Simple tablespace (No partitions).

Partitioned

Partitioned tablespace. The number of partitions are shown in the NUMPARTS field.

Segmented

Segmented tablespace. The segment size is shown in the SEGSIZE field.

Universal Table Space Range-partitioned

(Identifies a range-partitioned universal tablespace (UTS). Both, the number of partitions

and the segment size are shown in the NUMPARTS and SEGSIZE fields respectively.

Universal Table Space Partitioned-by-growth

Identifies a partition-by-growth universal tablespace (UTS). Both, the maximum number

of partitions and the segment size are shown in the MAXPARTITIONS and SEGSIZE
fields respectively.

NUMPARTS
Displays the number of partitions as specified in the extract file.
Load 467

MAXPARTITIONS
Displays the maximum number of partitions for a partition-by-growth universal tablespace (UTS)
as specified in the extract file. The MAXPARTITIONS field displays in place of the NUMPARTS
field for a partition-by-growth universal tablespace.

SEGSIZE
Displays the segment size of the tablespace, if the tablespace is segmented.

Target Object

SSID
Displays the Db2 subsystem ID of the Target Environment.

Location
Displays the remote Db2 location name of the Target Environment.

Database
Displays the name of the Db2 database of the Target Environment. You can only change it to an
existing database or one to be created that is in the Target Environment list. To use a new
database name please specify at the database level.

Tablespace
Specify the name of the Db2 tablespace of the Target Environment. If the tablespace does not
exist in the Target Environment, File-AID/RDX will create it during the load process.

Do NOT Blank out the name of a tablespace to create the tablespace

implicitly, instead select the table with the S line command in the Target
Environment panel and blank out the Tablespace field in the Create DB2
Table panel.

TS Type
Displays the tablespace type as specified in the extract file. See also Table 32. Valid types are:

Simple

Simple tablespace (No partitions).

Partitioned

Partitioned tablespace. The number of partitions are shown in the NUMPARTS field. You
can change the number of partitions in the NUMPARTS field. To change the partition
attributes, issue the PART primary command.

Segmented

Segmented tablespace. The segment size is shown in the SEGSIZE field. You can change
the segment size in the SEGSIZE field.
468 File-AID/RDX Reference

Universal Table Space Range-partitioned

Specifies a range-partitioned universal tablespace (UTS). Both, the number of partitions

and the segment size can be changed in the NUMPARTS and SEGSIZE fields respectively.
Either the NUMPARTS and SEGSIZE value or both values can be changed to zero for the
target environment; this causes the type of tablespace to be different in the target
environment than it was in the source environment. If NUMPARTS is set to zero but
SEGSIZE is not, the new tablespace will be segmented. If SEGSIZE is set to zero but
NUMPARTS is not, the new tablespace will be partitioned. If both NUMPARTS and
SEGSIZE are set to zero, the new tablespace will be segmented with the default SEGSIZE of
4.

File-AID/RDX does not support creating a UTS - Range-partitioned

tablespace if the original source tablespace was not UTS - Range-partitioned
tablespace.

Universal Table Space Partitioned-by-growth

Specifies a partition-by-growth universal tablespace (UTS). Both, the maximum number

of partitions and the segment size can be specified in the MAXPARTITIONS and
SEGSIZE fields respectively. Either the MAXPARTITIONS and SEGSIZE value or both
values can be changed to zero for the target environment; this causes the type of
tablespace to be different in the target environment than it was in the source
environment. If MAXPARTITIONS is set to zero but SEGSIZE is not, the new tablespace
will be segmented. If SEGSIZE is set to zero but MAXPARTITIONS is not, this result in a
partitioned-by-growth tablespace with a default SEGSIZE of 4. If both MAXPARTITIONS
and SEGSIZE are set to zero, the new tablespace will be segmented with the default
SEGSIZE of 4.

File-AID/RDX does not support creating a UTS - Partitioned-by-growth tablespace if the

original tablespace was not UTS - Partitioned-by-growth tablespace. 
Partition-by-growth tablespaces may be created implicitly when a Tablespace is not
specified on the Create DB2 Table screen.

NUMPARTS
If this is to be a partitioned tablespace, enter the number of partitions. This field is protected as
long as the target tablespace is an existing one. Once you change the target tablespace to a non-
existing one, you can then enter the desired number of partitions. This field MUST NOT BE
BLANK OR ZERO before attempting to define the partitions using the PARTITION command.

MAXPARTITIONS
Specify the maximum number of partitions for a partition-by-growth universal tablespace (UTS).
The actual maximum partition size allowed is dependent on the DSSIZE and Page size defined for
the Tablespace. The MAXPARTITIONS field displays in place of the NUMPARTS field for a
partition-by-growth universal tablespace.

SEGSIZE
If this is to be a segmented tablespace, enter the desired segment size. This field MUST NOT BE
BLANK OR ZERO before attempting to define the partitions using the PARTITION command.
Load 469

Automatic Space Calculation

Specify whether you want File-AID/RDX to calculate the space allocation for the new target
tablespace based on the extracted data or not. The calculated space will not exceed the space
allocation of the source. It overrides the status set with the Automatic Space Calculation field in
the Target Environment screen. This field is protected when selecting implicit tablespace
creation. When this field displays an M, it indicates that the space allocation values have been
entered manually which overrides the automatic space calculation.

Automatic Space calculation ===> M ( N = No; Y = Yes ; M =Manual )

STOGROUP
Specify the Db2 storage group in which the new tablespace will reside. The storage group must
already exist. This field is prefilled with your profile’s value or the extracted value, if the profile
value is blank.

PRIQTY(K)
Primary Quantity. Specify the number of storage units allocated for the file in which your
tablespace is to reside.

SECQTY(K)
Secondary Quantity. Specify how much more space should be allocated for the file if it exceeds
the primary quantity.

BUFFERPOOL
Specify the Db2 buffer pool name associated with the tablespace. This field is prefilled with the
extracted value.

FREEPAGE
Specify how often the system should leave a free page when the tablespace is updated.

PCTFREE
Specify how much of each page to leave free when the tablespace is updated.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

PARTITION (PART)
Displays the Tablespace Partition Definition screen which lets you define the attributes for each
tablespace partition.

LimitKey (LK)
Displays the Limit Key Definition screen (Figure 261 on page 477) which lets you define the limit
key value for each logical partition, if the tablespace is partitioned.
470 File-AID/RDX Reference

Valid Tablespace Types

Table 31 shows what types of tablespaces are created in each Db2 Version.

Table 31. Valid Tablespace Types

Tablespace Type V7 V8 V9
Simple CRTS a
CRTS Use if it exists but cannot
CRTBb implicit TS CRTB implicit TS create a new one
Segmented CRTS (segsize=4)
CRTS SEGSIZE
CRTS SEGSIZE CRTS SEGSIZE
CRTB implicit TS (Db2
Install option)
Partitioned CRTS NUMPARTS CRTS NUMPARTS CRTS NUMPARTS
Universal Tablespace - CRTS NUMPARTS
N/A N/A
Range partitioned SEGSIZE
Universal Tablespace - CRTS MAXPARTITIONS
Partition by Growth SEGSIZE
CRTB implicit TS
N/A N/A
PARTITION BY SIZE
CRTB implicit TS (Db2
Install option)

a. CRTS = Create Tablespace

b. CRTB = Create Table

Valid Tablespace Type Changes

Table 32 shows what changes are valid for changing the type of tablespace.

Table 32. Valid Tablespace Type Changes

Target Tablespace - Auto-create
UTS - UTS -
Db2 Source
Simple Segmented Partitioned Range- Partitioned-
Version Tablespace
partitioned by-growth
V7 V8 Simple V8 V9
V8 V9
All Segmented
SEGSIZE=0 SEGSIZE=0
V8 V9 Change
All Partitioned
NUMPARTS=0 NUMPARTS=0 NUMPARTS
V9
NUMPARTS=0
UTS - SEGSIZE=0 V8 = Error Change
CRTB
V9 Range-  V9 NUMPARTS
implicit TS
partitioned V9 SEGSIZE=0 and SEGSIZE
NUMPARTS=0
SEGSIZE=n
V8 = Error
V9
MAXPARTITIO
V9 Change CRTB
UTS - NS=0
SEGSIZE=0 MAXPAR- implicit TS
V9 Partitioned- SEGSIZE=0
TITIONS and
by-growth V9
SEGSIZE
MAXPARTITIO
NS=0
SEGSIZE=n
Load 471

Tablespace Partition Definition

The Tablespace Partition Definition screen shown in Figure 258 is displayed when you enter the
PARTITION primary command for a Db2 tablespace in the Create Tablespace screen. This screen lets
you specify or modify the tablespace partition information.

Figure 258. Tablespace Partition Definition

File-AID/RDX ------------ Tablespace Partition Definition -- Row 1 to 4 of 4 

Command ===> Scroll ===> CSR 

Primary commands: Change, Size 
Line commands: I = Insert; D = Delete; R = Repeat

Database .: FATSSSDB Target NUMPARTS. . : 200
Tablespace: CUSTOMER Source NUMPARTS. . : 4

Automatic space calculation ===> N (N = No; Y = Yes; M = Manual) 
Target - Calculated total primary space . : 
Source - Actual total primary space . . . : 40810 

*** Any partition not displayed will be defined the same as the MODEL *** 
PART STOGROUP PRIQTY SECQTY FREEPAGE PCTFREE 
___ 1 STG002 10 20 20 20 <-MODEL 
---- -------- ------- ------- -------- ------- --------------
___ 50 STG002 30 20 10 10 
___ 100 STG002 30 20 10 10 
___ 150 STG002 30 20 10 10 
___ 200 STG002 30 20 10 10 

******************************* Bottom of data ********************************

Use this screen to update the Db2 tablespace partition information. After you view or modify the
tablespace partition information, press END to return to the Create Tablespace screen.

Database
Displays the name of the Db2 database of the Target Environment where the tablespace will
reside.

Target NUMPARTS
Displays the number of partitions for the target tablespace.

Tablespace
Displays the name of the Db2 tablespace of the Target Environment for which you want to
specify partition information.

Source NUMPARTS
Displays the number of partitions as specified in the extract file.

Automatic Space Calculation

Specify whether you want File-AID/RDX to calculate the space allocation for the new target
tablespace partitions based on the extracted data or not. The calculated space will be distributed
472 File-AID/RDX Reference

equally over all partitions. It overrides the status set with the Automatic Space Calculation field
in the Target Environment screen.

Target - Calculated total primary space

Displays the total calculated space requirement for the new tablespace.

Source - Actual total primary space

Displays the total primary space allocation (at its original creation) of the tablespace from
which the data was extracted.

Partition Fields

By default, partition 1 is used as the model partition. If all partitions have the same values as the
model, no other partitions are displayed. Only partitions that are different from the model are
displayed in the scrollable area below the model partition. Use the line commands to insert, repeat,
or delete partitions that have different values than the model.

PART
For the model, it is the first partition of the source. In the list of differing partition definitions, it
displays the number of each partition that is different from the model partition.

STOGROUP
Specify the Db2 storage group in which the new tablespace partition will reside. The storage
group must already exist. This field is prefilled with the extracted storage group value.

PRIQTY(K)
Specify the number of storage units allocated for the file in which your tablespace partition is to
reside.

SECQTY(K)
Specify how much more space should be allocated for the file for the new tablespace partition if it
exceeds the primary quantity.

FREEPAGE
Specify how often the system should leave a free page when the tablespace partition is updated.

PCTFREE
Specify how much of each page to leave free when the tablespace partition is updated.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
Load 473

CHANGE (C)
The CHANGE command allows you to globally update the entry fields for the partition
definition. Specify the change ’from string’ and change ‘to string’ values in the CHANGE
Command Window - Partition Definition and select the fields to change.

CHANGE Command Window

When you enter the CHANGE command, File-AID/RDX will pop up the CHANGE Command
Window as shown in Figure 259. Enter the Change ‘from string’ and the Change ‘to string’ values
you want to change globally for all displayed partitions, then press END to execute the change
and exit the window.

Figure 259. CHANGE Command Window - Partition Definition



File-AID/RDX -------------- CHANGE COMMAND ------------------- 
Command ===> 

Change ALL occurrences of "from string" value to "to string" 
From string ===> 
To string ===> 

Act on the following fields: 
STOGROUP ===> N ( Y = Yes, N = No) 
PRIQTY(K) ===> N 
SECQTY(K) ===> N 
FREEPAGE ===> N 
PCTFREE ===> N 

ENDER to process and return 


SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 255 for an example. SIZE is a toggle switch so enter SIZE again to return to the
original format.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

I (Insert)
Enter the I (Insert) line command to insert a different partition definition after the current
partition. The inserted partition(s) are based on the model partition. To insert more than 1
partition, enter the number of partitions with the I line command (nnn = 1 - 999). Then modify
the partition values as required.

I
nnn
474 File-AID/RDX Reference

D (Delete)
Enter the D (Delete) line command to delete a partition definition in the list of different
partitions from the model. To delete more than 1 partition, enter the number of partitions with
the D line command (nnn = 1 - 999).

D
nnn

R (Repeat)
Enter the R (Repeat) line command to repeat a partition definition in the list of different
partitions from the model. To repeat a partition definition more than once, enter the number of
repetitions with the R line command (nnn = 1 - 999).

R
nnn
Create/Edit DB2 Table
The Create DB2 Table screen shown in Figure 260 is displayed when you enter the S (Select) line
command on a Db2 table in the Target Environment screen. This screen lets you modify the create
table information from the extract file to your new target environment.

Figure 260. Create DB2 Table

File-AID/RDX ---------------- Create DB2 Table ------------------------------

Command ===> 

Primary Commands: LimitKey 


Source Object: SSID: DSN Location: DSNLOCAT
Table: FRSAMP.ORDER_TABLE 
Partitioned . : Yes NUMPARTS: 4


Target Object: SSID: DSN Location: DSNLOCAT

Creator ===> TSOID01 
Table Name ===> ORDER_TABLE 
Database ===> FRSAMPDB 
Tablespace ===> ORDERRTA BLANK For Implicit Tablespace 
Partitioned . : Yes NUMPARTS: 4






Use this screen to update the Db2 table information for the Db2 table to be loaded. After you modify
the table information, press END to return to the Target Environment.

If the Db2 table, as specified on this screen, does not exist in the Target Environment, File-AID/RDX
will attempt to create and then load the Db2 table during the execution phase of the Load function.
Load 475

Source Object

SSID
Displays the Db2 subsystem ID of the “Source Environment” as specified in the extract file.

Location
Displays the remote Db2 location name of the “Source Environment”as specified in the extract
file.

Table Name
Displays the full Db2 source table name, including creator ID of the table, as specified in the
extract file.

Partitioned
Indicates whether the table is in a partitioned tablespace or not.

NUMPARTS
Displays the number of partitions.

MAXPARTITIONS
Displays the maximum number of partitions for a partition-by-growth universal tablespace (UTS).
The actual maximum partition size allowed is dependent on the DSSIZE and Page size defined for
the Tablespace. The MAXPARTITIONS field displays in place of the NUMPARTS field for a
partition-by-growth universal tablespace.

Target Object

SSID
Displays the Db2 subsystem ID of the Target Environment.

Location
Displays the remote Db2 location name of the Target Environment.

Creator
Specify the creator ID of the table. This field is prefilled with the target creator ID for Db2 objects
as specified in the Load Object Specifications or Source to Target Mapping screen.
476 File-AID/RDX Reference

Table Name
Specify the name of the table. This field is prefilled with the extracted table name or as specified
in the Source to Target Mapping screen.

When the source table is a Temporal Table, File-AID/RDX does not support
creating the target Temporal Table, instead, File-AID/RDX creates a regular
table. To load into a Temporal Table, it must already exist in the target
environment.

Database
Displays the name of the Db2 database where the table resides in the Target Environment. This
field is protected for tables that already exist in the target environment. If the target table does
not exist, you can change the database only to an existing database or one to be created that is in
the Target Environment list. To use a new database name please specify it at the database level.

Tablespace
Displays the name of the Db2 tablespace of the Target Environment for the table. This field is
protected for existing tables. If the target table does not exist, you can change the tablespace
field. If the tablespace does not exist in the Target Environment, File-AID/RDX will create it
during the load process.

Blank out the tablespace field and File-AID/RDX generates DDL to create the
tablespace implicitly as long as only one table is associated with the tablespace and it’s
a non-partitioned tablespace. The current SQLID must have the proper Db2 authority
to create the tablespace in the execution phase.

Partitioned
Indicates whether the table is in a partitioned tablespace or not. Must be No for implicit
tablespace.

NUMPARTS
Displays the number of partitions.

MAXPARTITIONS
Specify the maximum number of partitions for a partition-by-growth universal tablespace (UTS).
The actual maximum partition size allowed is dependent on the DSSIZE and Page size defined for
the Tablespace. The MAXPARTITIONS field displays in place of the NUMPARTS field for a
partition-by-growth universal tablespace.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

LimitKey (LK)
Displays the Limit Key Definition screen which lets you define the limit key value for each logical
partition, if the tablespace is partitioned.
Load 477

Limit Key Definition Window

When you enter the LimitKey primary command, File-AID/RDX displays the Limit Key Definition
screen as shown in Figure 261. File-AID/RDX provides initial default values that you can change
for each partition. In the Values field for each partition, enter the maximum key value, then press
END to execute the value definition and exit the window.

Figure 261. Limit Key Definition

File-AID/RDX ----------------- Limit Key Definition ------- Row 1 to 4 of 4 

Command ===> Scroll ===> CSR 

Primary commands: Size 

Index: TSOID01.XEMP_PARTTS41 Target NUMPARTS. . : 4
Table: TSOID01.EMPPART Source NUMPARTS. . : 4
Partitioning fields: PART,ASC 


PART Values 
---- -------------------------------------------------------------------------
1 '099999' 
2 '199999' 
3 '299999' 
4 '999999' 
******************************* Bottom of data ********************************






Index
Displays the Db2 index name only if LimitKey command was issued from the Create Index
screen.

Table
Displays the full Db2 object name, including creator ID of the table for which the limit key
information is to be defined.

Partitioning fields
Displays the Db2 column names that are used in the partitioned index/tablespace.
If the index has an expression (IX_EXTENSION_TYPE field in SYSINDEXES equals 'S'), the
expression(s) are listed here instead of the index columns.

Target NUMPARTS
Displays the number of partitions for the target tablespace.

Source NUMPARTS
Displays the number of partitions as specified in the extract file.
478 File-AID/RDX Reference

PART
Displays the number of each partition.

Values
Specify the limit key value for each partition. This is an expandable field to allow specifying a
value longer than a single line.

Primary Commands

The following File-AID/RDX-specific primary commands are valid on this screen:

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 255 for an example. SIZE is a toggle switch so enter SIZE again to return to the
original format.

Create/Edit Db2 Index

The Create Index screen shown in Figure 262 on page 478 is displayed when you enter the S (Select)
line command on a Db2 index in the Target Environment screen. This screen lets you modify the
create index information from the extract file to your new target environment.

Figure 262. Create Index

File-AID/RDX ------------------ Create Index ----------------------------------- 

Command ===> 

Primary Commands: PARTition, LimitKey 

Source Object: SSID: DSN Location: DSNLOCAT
Index name . . . .: FRSAMP.CONT_IDX 
Table name . . . .: FRSAMP.CONTACT_TABLE 
Index columns. . .: CUSTOMER_NUMBER,ASC/CONTACT_ID,ASC 
Index Type . . . .: Partitioning NUMPARTS: 4 


Target Object: SSID: DSN Location: DSNLOCAT
Table name . . . .: TSOID01.CONTACT_TABLE 
Index Creator ===> TSOID01 
Index name ===> CONT_IDX 
Index Type . . . .: Partitioning NUMPARTS: 4 

Automatic Space calculation ===> ( N = No; Y = Yes; M = Manual) 

STOGROUP ===> STG003 BUFFERPOOL ===> BP0 Partitioned . .: Yes
PROQTY(K) ===> 3 FREEPAGE ===> 0 
SECQTY(K) ===> 3 PCTFREE ===> 10 

Use this screen to update the Db2 index information for the Db2 table and index to be created. After
you modify the index information, press END to return to the Target Environment.

Source Object

SSID
Displays the Db2 subsystem ID of the extracted Db2 data.
Load 479

Location
Displays the remote Db2 location name of the extracted Db2 data.

Index name
Displays the Db2 index name as it appears in the extract file.

Table Name
Displays the full Db2 object name, including creator ID of the table for which the index
information was extracted.

Index columns
Displays the Db2 column names that are used in the index.
If the index has an expression (IX_EXTENSION_TYPE field in SYSINDEXES equals 'S'), the
expression(s) are listed here instead of the index columns.

Index Type
Displays the index type as specified in the extract file. Valid types are:

Non-Partitioned
Simple tablespace (No partitions).

Partitioning Index
Index-based partitioning. The number of partitions are shown in the NUMPARTS field.

Data Partitioned Secondary

Data partitioned secondary index. The number of partitions are shown in the
NUMPARTS field.

NUMPARTS
Displays the number of partitions.

Target Object

SSID
Displays the Db2 subsystem ID of the Target Environment.

Location
Displays the remote Db2 location name of the Target Environment.
480 File-AID/RDX Reference

Table Name
Displays the full Db2 object name, including creator ID of the table for which the index
information applies.

Index Creator
Specify the creator ID of the index. This field is prefilled with the target creator ID for Db2
objects as specified in the Load Object Specifications or Source to Target Mapping screen.

Index Name
Specify the name of the index. This field is prefilled with the extracted index name as specified or
modified in the Load Object Specifications screen.

Index Type
Displays the index type as specified in the extract file. Valid types are:

Non-Partitioned

Simple tablespace (No partitions).

Partitioning Index

Index-based partitioning. The number of partitions are shown in the NUMPARTS field.

Data Partitioned Secondary

Data partitioned secondary index. The number of partitions are shown in the
NUMPARTS field.

NUMPARTS
Displays the number of partitions.

Automatic Space Calculation

Displays whether you want File-AID/RDX to calculate the space allocation for new target index
based on the extracted data or not. The calculated space will not exceed the space allocation of
the source. It overrides the status set with the global Automatic Space Calculation field in the
Target Environment screen. When this field displays an M, it indicates that the space allocation
values have been entered manually which overrides the automatic space calculation.

Automatic Space calculation ===> M ( N = No; Y = Yes)

STOGROUP
Specify the Db2 storage group in which the new index will reside. The storage group must already
exist. This field is prefilled with the extracted storage group value.

PRIQTY
Number of kilobytes to be allocated for the file where your index will reside.
Load 481

SECQTY
Amount of space (in kilobytes) to be allocated for the file if it exceeds the primary quantity.

BUFFERPOOL
Specify the Db2 buffer pool name associated with the index. This field is prefilled with the
extracted value.

FREEPAGE
Specify the rate at which a page is left free when the index is loaded or reorganized.

PCTFREE
Specify the percentage of each page left free when the index is loaded or reorganized.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

PARTITION (PART)
Displays the Index Partition Definition screen which lets you define the attributes for each index
partition, if the tablespace is partitioned.

LimitKey (LK)
Displays the Limit Key Definition screen (Figure 261 on page 477) which lets you define the limit
key value for each logical partition, if the tablespace is partitioned.

Index Partition Definition

The Index Partition Definition screen shown in Figure 263 on page 482 is displayed when you enter
the PARTITION primary command for a Db2 index in the Create Index screen. This screen lets you
specify or modify the index partition information.
482 File-AID/RDX Reference

Figure 263. Index Partition Definition

File-AID/RDX ------------ Index Partition Definition ------- Row 1 to 4 of 4 

Command ===> Scroll ===> CSR 

Primary commands: Change, Size 
Line Commands: I = Insert; D = Delete; R = Repeat 

Index: TSOID01.CONT_IDX Target NUMPARTS: 200 
Table: TSOID01.CONTACT_TABLE Source NUMPARTS: 4

Automatic space calculation ===> (N = No; Y = Yes; M = Manual) 
Target - Calculated total primary space . : 
Source - Actual total primary space . . . : 58871 


*** Any partition not displayed will be defined the same as the MODEL *** 
PART STOGROUP PRIQTY SECQTY FREEPAGE PCTFREE 
___ 4 STG002 10 20 20 20 MODEL 
---- -------- ------- ------- -------- ------- --------------
___ 50 STG002 30 20 10 10 
___ 100 STG002 30 20 10 10 
___ 150 STG002 30 20 10 10 
___ 200 STG002 30 20 10 10 
******************************* Bottom of data ********************************

Use this screen to update the Db2 index partition information. After you view or modify the index
partition information, press END to return to the Create Index screen.

Index
Displays the name of the index.

Target NUMPARTS
Displays the number of partitions.

Table
Displays the full Db2 object name, including creator ID of the table for which the index
information applies.

Source NUMPARTS
Displays the number of partitions.

Automatic Space Calculation

Specify whether you want File-AID/RDX to calculate the space allocation for this new target
index based on the extracted data or not. The calculated space will be distributed equally over all
partitions. This setting overrides the global status set with the Automatic Space Calculation field
in the Target Environment screen.

Target - Calculated total primary space

Displays the total calculated space requirement for the new index.
Load 483

Source - Actual total primary space

Displays the total primary space allocation (at its original creation) of the index from which
the data was extracted.

Partition Fields

By default, partition 1 is used as the model partition. For table-controlled partitioning, the highest
partition of the source is used as the model partition. If all partitions have the same values as the
model, no other partitions are displayed. Only partitions that are different from the model are
displayed in the scrollable area below the model partition. Use the line commands to add or delete
partitions that have different values than the model.

PART
For the model, it displays the number of the source partition used for the model. In the list of
differing partition definitions, it displays the number of each partition that is different from the
model partition.

STOGROUP
Specify the Db2 storage group in which the new tablespace partition will reside. The storage
group must already exist. This field is prefilled with the extracted storage group value.

PRIQTY(K)
Specify the number of storage units allocated for the file in which your tablespace partition is to
reside.

SECQTY(K)
Specify how much more space should be allocated for the file for the new tablespace partition if it
exceeds the primary quantity.

FREEPAGE
Specify how often the system should leave a free page when the tablespace partition is updated.

PCTFREE
Specify how much of each page to leave free when the tablespace partition is updated.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

CHANGE (C)
The CHANGE command allows you to globally update the entry fields for the partition
definition. Specify the change’ from string’ and change ‘to string’ in the CHANGE Command
Window - Partition Definition and select the fields to change. See CHANGE Command Window
on page 473 for a description.
484 File-AID/RDX Reference

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 255 for an example. SIZE is a toggle switch so enter SIZE again to return to the
original format.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

I (Insert)
Enter the I (Insert) line command to insert a different partition after the current partition. The
inserted partition(s) are based on the model partition. To insert more than 1 partition, enter the
number of partitions with the I line command (nnn = 1 - 999). Then modify the partition values
as required.

I
nnn

D (Delete)
Enter the D (Delete) line command to delete a partition definition in the list of different
partitions from the model. To delete more than 1 partition, enter the number of partitions with
the D line command (nnn = 1 - 999).

D
nnn

R (Repeat)
Enter the R (Repeat) line command to repeat a partition definition in the list of different
partitions from the model. To repeat a partition definition more than once, enter the number of
repetitions with the R line command (nnn = 1 - 999).

R
nnn
Create/Edit Db2 Alias
The Create Alias screen shown in Figure 264 on page 485 is displayed when you enter the S (Select)
line command on a Db2 alias in the Target Environment screen. This screen lets you modify the
create alias information from the extract file to your new target environment.
Load 485

Figure 264. Create Alias

File-AID/RDX ------------------ Create Alias ---------------------------------

Command ===> 



Source Object: SSID: DSN Location: DSNLOCAT
Alias name : TSOID01.LOCALDEPT 
Table name : DSN8710.DEPT 


Target Object: SSID: DSN Location: DSNLOCAT
Table Name ...: TSOID01.DEPT 
Creator ===> TSOID01 
Alias name ===> LOCALDEPT 

Use this screen to update the Db2 alias information. After you view or modify the alias information,
press END to return to the Target Environment screen.

Source Object

SSID
Displays the Db2 subsystem ID of the “Source Environment”.

Location
Displays the remote Db2 location name of the “Source Environment”.

Alias name
Displays the alias name as extracted.

Table name
Displays the table name of the extracted alias name.

Target Object

SSID
Displays the Db2 subsystem ID of the Target Environment.

Location
Displays the remote Db2 location name of the Target Environment.

Table name
Displays the target table name for the alias.

Creator
Specify the creator name for the new alias name.
486 File-AID/RDX Reference

Alias name
Specify the name for the alias in the target environment.

Create/Edit Db2 Synonym

The Create Synonym screen shown in Figure 265 is displayed when you enter the S (Select) line
command on a Db2 synonym in the Target Environment screen. This screen lets you modify the
create synonym information from the extract file to your new target environment.

Figure 265. Create Synonym

File-AID/RDX ---------------- Create Synonym ---------------------------------

Command ===> 


Source Object: SSID: DSN Location: DSNLOCAT
SQLID : FRSAMP 
Synonym name : SYNCUSTOMER 
Table name : FRSAMP.CUSTOMER_TABLE 

Target Object: SSID: DSN Location: DSNLOCAT
Table Name ...: TSOID01.CUSTOMER_TABLE 
SQLID ===> TSOID01 
Synonym name ===> SYNCUSTOMER 


Use this screen to update the Db2 synonym information. After you view or modify the synonym
information, press END to return to the Target Environment.

Source Object

SSID
Displays the Db2 subsystem ID of the “Source Environment”.

Location
Displays the remote Db2 location name of the “Source Environment”.

SQLID
Displays the SQL ID as extracted for the synonym.

Synonym name
Displays the synonym name as extracted.

Table name
Displays the table name of the extracted synonym name.

Target Object

SSID
Displays the Db2 subsystem ID of the Target Environment.
Load 487

Location
Displays the remote Db2 location name of the Target Environment.

Table name
Displays the target table name for the synonym.

SQLID
Specify the creator name for the new synonym name.

Synonym name
Specify the name for the synonym in the target environment.

Create/Edit Db2 View (Simple)

The Create View screen shown in Figure 266 is displayed when you enter the S (Select) line command
on a simple Db2 view (single table view) in the Target Environment screen. This screen lets you
modify the create view information from the extract file to your new target environment.

Figure 266. Create View

File-AID/RDX ------------------ Create View ----------------------------------

Command ===> 



Source Object: SSID: DSN Location: DSNLOCAT
View name : FRSAMP.VCUSTOMER 
Table name : FRSAMP.CUSTOMER_TABLE 


Target Object: SSID: DSN Location: DSNLOCAT
Table Name ===> TSOID01.CUSTOMER_TABLE 
Creator ===> TSOID01 
View name ===> VCUSTOMER 

Use this screen to update the Db2 view information. After you view or modify the view information,
press END to return to the Target Environment.

Source Object

SSID
Displays the Db2 subsystem ID of the “Source Environment”.

Location
Displays the remote Db2 location name of the “Source Environment”.

View name
Displays the view name as extracted.
488 File-AID/RDX Reference

Table name
Displays the table name of the extracted view.

Target Object

SSID
Displays the Db2 subsystem ID of the Target Environment.

Location
Displays the remote Db2 location name of the Target Environment.

Table name
Displays the target table name for the view.

Creator
Specify the creator name for the new view name.

View name
Specify the name for the view in the target environment.

Create/Edit Db2 View (Complex)

The Create View (Complex) screen shown in Figure 267 is displayed when you enter the S (Select) line
command on a complex Db2 view (multiple table view) in the Target Environment screen. This
screen lets you modify the create view information from the extract file to your new target
environment.

Figure 267. Create View (Complex)

File-AID/RDX ------------------ Create View -----------------------------------

Command ===> 


Primary Commands: TABle 


Source Object: SSID: DSN Location: DSNLOCAT
View name : FRSAMP.COMP_VIEW 
Table name : ** MULTI TABLE VIEW ** 


Target Object: SSID: DSN Location: DSNLOCAT
Table Name ===> ** MULTI TABLE VIEW ** ** Use TABle Command ** 
Creator ===> TSOID01 
View name ===> COMP_VIEW 

Use this screen to update the Db2 view information. After you view or modify the view information,
press END to return to the Target Environment.
Load 489

Source Object

SSID
Displays the Db2 subsystem ID of the Target Environment.

Location
Displays the remote Db2 location name of the Target Environment.

View name
Displays the view name as extracted.

Table name
Blank, as there are more than one table.

Target Object

SSID
Displays the Db2 subsystem ID of the Target Environment.

Location
Displays the remote Db2 location name of the Target Environment.

Table name
Blank, as there are more than one table.

Creator
Specify the creator name for the new view name.

View name
Specify the name for the view in the target environment.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

TABLE (TAB)
Displays the “Tables Within View” screen which lists the tables that are part of the complex view.
490 File-AID/RDX Reference

Tables Within View

When you enter the TABLE command, File-AID/RDX will display the Tables Within View as shown in
Figure 268 on page 490.

Figure 268. Tables Within View

File-AID/RDX ------------- Tables Within View ------------ Row 1 to 2 of 2 

Command ===> Scroll ===> CSR

New View Information: 
Creator : TSOID01 
Index name: VDEPT 

Table Name 
----------------------------------------------------------------------------
TSOID01.DEPT 
TSOID01.EMP 


Review the list of tables for the complex view, then press END to exit the screen.

Create/Edit MVS File

The Create MVS File shown in Figure 269 is displayed when you enter the S (Select) line command on
a sequential MVS file in the Target Environment screen. This screen lets you modify the create MVS
file information from the extract file to your new target environment.

Figure 269. Create MVS File

File-AID/RDX ----------------- Create MVS File ------------------------------

Command ===> 

Source Object: 
File Name: TSOID02.FASAMP.EMPMAST'

Target Object:
File Name ===> 'TSOID01.FASAMP.EMPMAST' 

Auto Calculate Space ===> N (Y or N) 
Management Class ===> SAMPLE@S (Blank for default) 
Storage Class ===> STDDODFW (Blank for default) 
Generic unit ===> 
Volume serial ===> PRD936 (Blank for default) 
Data Class ===> (Blank for default) 
Space units ===> TRK (BLKs; TRKs; CYLs) 
Primary quantity ===> 1 (In above units) 
Secondary quantity ===> 1 (In above units) 
Record length ===> 198 
Block size ===> 0 


When parameters are complete, use END to continue. 



Use this screen to update the MVS file information to be loaded. After you modify the MVS file
information, press END to return to the Target Environment screen.

Source Object:

File Name
Displays the name of the MVS file as specified in the extract file.
Load 491

Target Object:

File Name
Displays the name of the MVS file as specified on the Target Environment screen. You can also
change the file name in this field.

Auto Calculate Space

Specify whether you want File-AID/RDX to calculate the space allocation for this new target MVS
file based on the extracted data or not. The calculated space will not exceed the space allocation
of the source. This setting overrides the global status set with the Automatic Space Calculation
field in the Target Environment screen. When this field displays an M, it indicates that the space
allocation values have been entered manually which overrides the automatic space calculation.

Autocalculate Space ===> M (Y or N)

Management Class
Specify the SMS management class to use for the allocation of the file. The management class
describes the migration, backup, and retention for the file.

Storage Class
Specify the SMS storage class to use for the allocation of the file. The storage class describes the
hardware requirements of the file.

Generic Unit
Specify the device type on which the new file will reside. The names of these devices are
installation dependent.

Volume serial
Specify the volume serial of the direct access device that contains the file.

Data Class
Specify the SMS data class to use for the allocation of the file. The data class describes the
attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.

Space units
Specify one of the following storage unit types depending on how the file size is expressed:

TRK - Tracks
CYL - Cylinders
BLK - Blocks
KB - Kilobytes
MB - Megabytes
492 File-AID/RDX Reference

Primary quantity
Specify the primary allocation quantity as specified in the space units field.

Secondary quantity
Specify the secondary allocation quantity as specified in the space units field.

Record length
Specify a logical record length, in bytes, of the records to be stored in the file. File-AID/RDX
validates this value with the record format and block size.

Block size
Specify the physical record length, in bytes, of the blocks to be stored in the file. File-AID/RDX
validates this value with the record format and record length.

File-AID/RDX supports loading to Sequential (PS) files greater than 65,535 tracks
(DSNTYPE=LARGE) when the MVS Operating System also supports them. 
Allocation of a datasets with DSNTYPE=LARGE will not be supported. Loading to a
DSNTYPE=LARGE file is supported as long as the target object exists. If the source object is
defined as DSNTYPE=LARGE and the Target object is to be auto-created, a warning message
will be issued to notify that the DSNTYPE=LARGE definition will be dropped.

Create/Edit VSAM CLUSTER

The Create VSAM CLUSTER shown in Figure 270 is displayed when you enter the S (Select) line
command on a VSAM or IAM cluster in the Target Environment screen. This screen lets you modify
the create cluster information from the extract file to your new target environment.

Figure 270. Create VSAM CLUSTER

File-AID/RDX --------------- Create VSAM CLUSTER ------------------------------

Command ===> 

Source Object: 

Cluster . . . .: 'TSOID01.FRSAMP.CUSTOMER' 

Target Object VSAM Component names: 
Cluster ===> 'TSOID03.FRSAMP.CUSTOMER' 
Data Component LLQ ===> DATA 
Index Component LLQ ===> INDEX 
Data component. . . . .: 'TSOID03.FRSAMP.CUSTOMER.DATA' 
Index component. . . . : 'TSOID03.FRSAMP.CUSTOMER.INDEX' 

Specify SMS Class Information: 
Storage ===> STDNOCSH DATA ===> Management ===> @NONSTD@ 

Automatic Space Calculation ===> N (Y or N) 
Space Allocation: DATA Component KSDS INDEX Component (Blank for default) 
Volume Serial ===> PRD908 ===> PRD908 
Space Units ===> TRK ===> TRK (TRKs; CYLs; RECs) 
Primary QTY ===> 5 ===> 1 (Amount in above unit) 
Secondary QTY ===> 5 ===> 1 (AMOUNT in above unit) 


Use this screen to update the VSAM cluster to be created. After you modify the cluster information,
press END to return to the Target Environment screen.
Load 493

During the execution phase of the Load function, File-AID/RDX will attempt to create the VSAM
cluster as specified on this screen.

Source Object:

Cluster
Displays the name of the cluster as specified in the extract file.

Target Object:

Cluster
Displays the name of the VSAM cluster as specified on the Target Environment screen. You can
also change the cluster name in this field.

Data component LLQ

Low level qualifier for the data component. You may overtype this field.

Index component LLQ

Low level qualifier for the index component. You may overtype this field.

Data component
Displays the name of the data component as it will be in the new target environment. It reflects
the new cluster name and low level qualifier.

Index component
Displays the name of the index component as it will be in the new target environment. It reflects
the new cluster name and low level qualifier.

If a long cluster name results in data and index component names longer
than 44 characters, the cluster name portion in front of the component LLQ
is truncated.

Specify SMS Class Information

If you are allocating an SMS file, specify or verify the following SMS allocation class information:

Storage
Specify the SMS storage class to use for the allocation of the file. The storage class describes the
hardware requirements of the file.

Data
Specify the SMS data class to use for the allocation of the file. The data class describes the
attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.
494 File-AID/RDX Reference

Management
Specify the SMS management class to use for the allocation of the file. The management class
describes the migration, backup, and retention for the file.

Any SMS file allocation problems are indicated with an IDCAMS Error
Message Display screen.

Space Allocation
Specify the required storage space for the file components in both the DATA Component and INDEX
Component columns. The default values are used when you leave these fields blank. The INDEX
component can be specified on a generic unit or volume that is different from the DATA component.

Automatic Space Calculation

Specify whether you want File-AID/RDX to calculate the space allocation for this new target
VSAM Cluster based on the extracted data or not. The calculated space will not exceed the space
allocation of the source. This setting overrides the global status set with the Automatic Space
Calculation field in the Target Environment screen. When this field displays an M, it indicates
that the space allocation values have been entered manually which overrides the automatic space
calculation.

Automatic Space Calculation ===> M (Y or N)

Volume serial
Specify the volume serial of the direct access device that contains the file.

When using SMS and allocating a non-SMS managed file, a Volume serial is required.

Units
Specify one of the following storage unit types depending on how the file size is expressed:

TRK - Tracks
CYL - Cylinders
REC - Records

Primary Qty
Specify the primary allocation quantity as specified in the space units field.

Secondary Qty
Specify the secondary allocation quantity as specified in the space units field.

Support of IAM File Types

Innovation Access Method (IAM) is a proprietary VSAM like access method provided by Innovation
Data Processing. File-AID/RDX provides full support for the IAM access method (IAM Version 9
Load 495

Release 1 and above). The IAM subsystem(s) must be fully operational and IDCAMS must support
IAM. IAM files are processed the same as their respective VSAM types (KSDS, ESDS) in all functions.

For File-AID/RDX to continue support of IAM (Innovation Access Method)

file types, apply the appropriate IAM version fix(es): IAM Version 9.1 fixes
P910005 and P910167, IAM Version 9.2 fix P920095, and IAM Version 9.3
fix P930003.

Data extracted from an IAM file in the source environment can also be loaded to a standard VSAM file
in the Target Environment as long as the target object exists. Data extracted from a VSAM file in the
source environment can be loaded to an IAM file in the Target Environment as long as the target
object exists.

IAM files exist as fixed or variable length files. Due to a constraint in the information available to
File-AID/RDX from the IAM Access Method, all files are currently handled as variable length files. If
the length is changed on an IAM file which is truly fixed, File-AID/RDX will display an error message.

File-AID/RDX does not support alternate indexes for IAM files.

Create/Edit VSAM AIX

The Create VSAM AIX screen shown in Figure 271 is displayed when you enter the S (Select) line
command on a VSAM alternate index in the Target Environment screen. This screen lets you modify
the create alternate index information from the extract file to your new target environment.

Figure 271. Create VSAM AIX

File-AID/RDX -------------------- Create VSAM AIX -------------------------- 

COMMAND ===> 

Base Cluster. . .: 'TSOID01.FRSAMP.CUSTOMER' 
Original AIX Name: 'TSOID01.FRSAMP.CUSTOMER.AIX'

New AIX Component names:
Cluster ===> 'TSOID01.FRSAMP.CUSTOMER.AIX'
Data component LLQ ===> DATA 
Index component LLQ ===> INDEX 

Data component : 'TSOID01.FRSAMP.CUSTOMER.DATA' 
Index component: 'TSOID01.FRSAMP.CUSTOMER.INDEX' 

Specify SMS Class Information:
Storage ===> STDNOCSH Data ===> Management ===> @NONSTD@ 

Space Allocation: 
DATA Component KSDS INDEX Component (Blank for default)
Volume serial ===> PRD973 ===> PRD973 
Space Units ===> TRK ===> TRK (BLK; TRK; CYL)
Primary Qty ===> 5 ===> 1 (Amount in above units)
Secondary Qty ===> 5 ===> 1 (Amount in above units)


Use this screen to update the VSAM alternate index information for the VSAM file and alternate
index to be created. After you modify the index information, press END to return to the Target
Environment screen.

During the execution phase of the Load function, File-AID/RDX will attempt to create the VSAM
alternate index as specified on this screen.

Base cluster
Displays the name of the extracted cluster to be indexed. VSAM requires that the base cluster of
an alternate index be defined as non-reusable.
496 File-AID/RDX Reference

Original AIX Name

Displays the fully qualified name of the extracted VSAM alternate index cluster.

New AIX Component Names

Cluster
Specify the fully qualified name of the new VSAM alternate index to be created. This field is
prefilled with the extracted name.

Data component LLQ

Low level qualifier for the data component. You may overtype this field.

Index component LLQ

Low level qualifier for the index component. You may overtype this field.

Data component
Displays the name of the data component as extracted.

Index component
Displays the name of the index component as extracted.

If a long cluster name results in data and index component names longer
than 44 characters, the cluster name portion in front of the component LLQ
is truncated.

Specify SMS Class Information

If you are allocating an SMS file, specify or verify the following SMS allocation class information:

Storage
Specify the SMS storage class to use for the allocation of the file. The storage class describes the
hardware requirements of the file.

Data
Specify the SMS data class to use for the allocation of the file. The data class describes the
attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.
Load 497

Management
Specify the SMS management class to use for the allocation of the file. The management class
describes the migration, backup, and retention for the file.

Any SMS file allocation problems are indicated with an IDCAMS Error
Message Display screen.

Space Allocation
Specify the required storage space for the file components in both the DATA Component and INDEX
Component columns. The default values are used when you leave these fields blank. The INDEX
component can be specified on a generic unit or volume that is different from the DATA component.

Volume serial
Specify the volume serial of the direct access device that contains the file.

When using SMS and allocating a non-SMS managed file, a Volume serial is required.

Units
Specify one of the following storage unit types depending on how the file size is expressed:

TRK - Tracks
CYL - Cylinders
BLK - Blocks

Primary Qty
Specify the primary allocation quantity as specified in the space units field.

Secondary Qty
Specify the secondary allocation quantity as specified in the space units field.

Create VSAM PATH

The Create VSAM PATH screen shown in Figure 272 is displayed when you enter the S (Select) line
command on a VSAM path in the Target Environment screen. This screen lets you modify the create
path information from the extract file to your new target environment.

Figure 272. Create VSAM PATH

File-AID/RDX ---------------------- Create VSAM PATH ------------------------- 

COMMAND ===> 

Base Cluster . . .: 'TSOID01.FRSAMP.CUSTOMER' 
Original PATH Name: 'TSOID01.FRSAMP.CUSTOMER.PATH'

New PATH name ===> 'TSOID01.FRSAMP.CUSTOMER.PATH'

498 File-AID/RDX Reference

Use this screen to update the VSAM path information for the VSAM file to be created. After you
modify the path information, press END to return to the Target Environment screen.

During the execution phase of the Load function, File-AID/RDX will attempt to create the VSAM path
as specified on this screen.

Base cluster
Displays the name of the extracted cluster.

Original PATH Name

Displays the fully qualified name of the extracted VSAM path.

New PATH Name

Specify the fully qualified name of the new VSAM path to be created. This field is prefilled with
the extracted path name.

Existing Data Options

The Existing Data Options screen shown in Figure 273 is displayed when you select Option 4 from
the Load Menu. The Existing Data Options screen displays the list of objects that will be loaded with
the data from the extract file.

Figure 273. Existing Data Options

File-AID/RDX ------------------ Existing Data Options -------------------------

Command ===> SCROLL ===> PAGE
Primary commands: Change

Extract File: TSOID01.FRSAMP.TEST3 
Insert/Load Option: SQL 

Record Del Replace Del/
Object Name Type Count All Matches Def
---------------------------------------------- ---- -------- --- ------- ----
TSOID01.CUSTOMER_TABLE DB2 3 NO YES NO
TSOID01.PART_TABLE DB2 8 NO YES NO
TSOID01.CONTACT_TABLE DB2 5 NO YES NO
TSOID01.ORDER_TABLE DB2 3 NO YES NO
TSOID01.ORDER_LINE DB2 10 NO YES NO
TSOID01.SUPPLIER_TABLE DB2 8 NO YES NO
** END OF LIST ** 

Use this screen to specify whether or not existing data should be deleted before objects are loaded
and whether or not rows with matching data (duplicate keys) should be replaced.

For MVS objects, you may also select the option to delete an existing target file and redefine it before
loading data.

The body of this screen consists of an upper portion and a lower portion.

Upper Portion
The upper portion of the screen consists of the following fields:
Load 499

Extract File Name

Displays the name of the file from which data will be loaded.

Db2 Processing Options Area

Insert/Load Option
Displays which Db2 load option you selected on the Load Object Specifications screen:

SQL

Perform the load using SQL INSERT statements. This option allows you to update rows if they
already exist.

DB2

Perform the load using the IBM Db2 Batch Load Utility.

Lower Portion
The lower portion of the screen consists of a list of objects that File-AID/RDX will load. If there are
more entries on the list than will fit on the screen, you can scroll the list up and down using standard
scrolling commands. See Scrolling on page 31 for more information.

Object Name
Displays the fully qualified name of the object to be loaded. If it is a Db2 object it includes the
creator ID of the owner of the table and index that will be loaded.

Type
The object type is indicated in the next column

– DB2
– File (MVS)

Record Count
Indicates the number of records (rows) to be loaded into each target object.

Del ALL
Specify whether File-AID/RDX should delete ALL of the data residing in the target objects before
it loads data from the extract file. For Db2 tables, Db2 delete rules are in effect.

Yes File-AID/RDX generates a step in the JCL to delete all rows from the specified object
before loading data.

You cannot specify Yes in this field for objects marked to be created; they do not exist
and, therefore, do not contain data.
No Indicates that the data is to be loaded into objects without deleting existing rows.

Note: When loading into a SYSTEM TEMPORAL table that already contains data, you
must consider potential data conflicts when NOT replacing all data in the table. The
conflicts can occur because of duplicate values in the three timestamp columns that are
part of SYSTEM TEMPORAL tables.
500 File-AID/RDX Reference

Replace Matches
When you are adding data to an object that is not empty and the INSERT operation fails because
the row or record already exists, specify whether or not it should be replaced.

Yes For MVS:

If the target object is indexed (KSDS), data from the extract file will replace existing data
in the target object.

For Db2:
If the target Db2 table has a unique index, data from the extract file will replace existing
data in the target table.
No For MVS:
If the target object is indexed and an existing target record has a unique key that
matches the data from the extract file, the data from the extract file will be discarded.

For Db2:
If the target table has a unique index and an existing target row has a unique key that
matches the data from the extract file, the data from the extract file will be discarded. If
the target table does not contain a unique index and rows to be loaded already exist, no
data will be discarded.

Del/Def
MVS files only. Specify whether File-AID/RDX should delete the target file and then redefine it
before it loads data from the extract file.

Yes File-AID/RDX generates a step in the JCL to delete the object and then create it
again before loading data.
No Appends data to the existing target object.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

END
The END command returns to the Load Menu.

CHANGE (C)
The CHANGE command allows you to globally change the value (YES or NO) for all selected
fields (Del All, Replace Matches, or Del/Def) displayed in the list. Specify the change’ from string’
and change ‘to string’ in the CHANGE Command Window.

When globally changing the Del/Def value to YES, File-AID/RDX changes only the values for MVS
objects as this field is protected for Db2 objects.

CHANGE Command Window

When you enter the CHANGE command, File-AID/RDX displays the CHANGE Command
Window as shown in Figure 274 on page 501. Enter the Change ‘from string’ and the Change ‘to
string’ values (either YES or NO) you want to change globally for all selected fields to act upon.
Select the fields (Y) the CHANGE command should be applied to, then press END to execute the
change and exit the window.
Load 501

Figure 274. CHANGE Command Window - Existing Data Options



File-AID/RDX -------------- CHANGE COMMAND ------------------- 
Command ===> 

Change ALL occurrences of "from string" value to "to string" 
From string ===> 
To string ===> 

Act on the following fields: 
Del All ===> N ( Y = Yes, N = No)
Replace Matches ===> N ( Y = Yes, N = No)
Del / Def ===> N ( Y = Yes, N = No)

CAN to cancel 
END to process and return to Load Options 



From string
Enter the current From (old) string, YES or NO, you want to change to the To (new) string in the
fields to act on.

To string
Enter the To (new) string, YES or NO, you want to replace the From (old) string with in the fields
to act on.

Del All
Enter Y if the global change is to be applied to the Del All field for all objects.

Replace Matches
Enter Y if the global change is to be applied to the Replace Matches field for all objects.

Del / Def
Enter Y if the global change is to be applied to the Del / Def field for all objects.

Processing Options
The Processing Options screen shown in Figure 275 is displayed when you select Option 5 from the
Load Menu.
502 File-AID/RDX Reference

Figure 275. Processing Options

File-AID/RDX ---------------- Processing Options ------------------------------

Command ===> 

Extract File: TSOID01.FRSAMP.EXTRACT 
Objects to Load: DB2 only 
DB2 Load Method: SQL Insert 


Specify DB2 Load Utility Options: 
Log Option ===> 4 (1 = Log; 2 = Image Copy; 
3 = Repair; 4 = Inline Image Copy) 


When DB2 SQL Insert and/or loading MVS objects, 
Specify Discard Processing Options: 
Save Discarded Rows ===> N (Y = YES; N = NO) 
Maximum Rows to Discard ===> * (* for no maximum) 
File for Discarded Rows ===> 


Specify DB2 SQL Insert Commit Interval: 
Commit Every Nth Row ===> 300 (1-2002) 


Use this screen to specify processing options for MVS files and Db2 tables to be loaded with the SQL
insert or Db2 load utility option.

When the load option is Db2, use this screen to specify whether or not you want Db2 logging in
effect during the load of the Db2 objects and whether or not existing data should be deleted before
Db2 tables and/or MVS file are loaded.

The upper part of this screen displays the following fields:

Extract File
Displays the name of the file from which data will be loaded.

Objects to Load
Displays whether the load includes Db2 only, or MVS only, or both Db2 and MVS objects.

DB2 Load Method

Displays which load method you selected in the Load Object Specifications screen (Figure 238 on
page 426), either SQL INSERT or IBM Db2 Batch Load Utility.

Specify DB2 Load Utility Options

Log Option
Specify which log option to use during the execution of the Db2 LOAD utility for the Db2
objects.

Log Db2 logging will occur during the load process.

2
Load 503

Image Copy Db2 logging of data will not occur during the load process. Db2 sets a COPY
PENDING restriction against the tablespace being loaded. An IMAGECOPY step is generated
to remove the COPY PENDING status.

Repair Db2 logging of data will not occur during the load process. Db2 sets a COPY
PENDING restriction against the tablespace being loaded. A REPAIR step is generated to set
NOCOPYPEND for the tablespace(s). To execute this utility, the privilege set of the process
must include one of the following:

• REPAIR privilege for the database

• DBADM or DBCTRL authority for the database
• SYSCTRL or SYSADM authority.

Inline Image Copy When “Delete All” is also set to ‘YES’ this option will invoke inline image
copy. Db2 logging of data will not occur during the load process. The tablespace into which
the data is being loaded will not be placed into a copy pending state.

If there are multiple tables in a tablespace then inline image copy is not used; instead an
IMAGECOPY step is generated to remove the COPY PENDING status.

Specify Discard Processing Options

Discard processing is available when the load includes MVS objects or Db2 objects with Load Method
Db2 SQL Insert.

Maximum Rows to Discard

Specify the maximum number of errors encountered before processing stops. Specify an asterisk
(*) for no maximum or a value greater than 0. Specify 1 if you want processing to stop if any
errors are encountered. Specify YES in the Save Discarded Rows field to save these rows for
future use. The discard file need not exist to specify a value in this field.

Save Discarded Rows

Specify whether or not to save rows, or records, that could not be inserted or updated.

Yes Save rows that cannot be inserted or updated in the discard file.
No Do not save rows that cannot be inserted or updated.

File for Discarded Rows

Specify the name of the file to which discarded rows will be saved. The discard file must be
sequential. If you specify YES in the Save Discarded Rows field and specify a file that does not
exist, File-AID/RDX will display the Create New File screen (see Figure 175 on page 334).

The discard file can be used as input to the load process if a previous load job was completed
normally, but rows were discarded. See SQL INSERT Load JCL on page 523.
504 File-AID/RDX Reference

Specify SQL Insert Processing Options

Commit Every Nth Row

Specify the number of rows File-AID/RDX should insert or update before it performs a Db2
COMMIT. This value must be less than or equal to the value specified for the Max Commit
Interval installation parameter.

Save Load Request

The Save Load Request screen shown in Figure 276 is displayed when you select Option 6, from the
Load Menu.

Figure 276. Save Load Request

File-AID/RDX ---------------- Save Load Request ----------------------------

COMMAND ===> 

Specify Load Request File Information: 
File name ===> FRSAMP.EXTCRIT 
Member ===> 
Description ===> 


Use this screen to save the current load request information.

Press Enter to process the file information. The saved request will also appear in your Load Reference
List (see Load Reference List on page 413).

The body of the Save Load Request screen consists of the following fields:

File Name
Specify the name of the file where you want to save the load request. You can save the request to
existing files. Existing files must conform to the format outlined for the request file in File-
AID/RDX Extract/Load/Delete Request File on page 368.

Pre-Release 4.3 extract/load request files have fixed or fixed-blocked

(RECFM=F or RECFM=FB) record format. When saving a Pre-Release 4.3
request file, File-AID/RDX will issue an invalid format message. Specify a new
name to save the request file in variable-blocked (RECFM=VB) format.

If you specify a new file, you must specify the following allocation parameters in the Create New
File screen (Figure 175 on page 334).

Member
If the file is partitioned, specify the name of the member to contain the load request.

Description
Enter a short description of the load request. This description is displayed in the Load Menu and
the Load Reference List. Using this description is a helpful way to document your load request.
Load 505

SAVE Confirmation
When saving an Extract or Load request File-AID/RDX checks to see if the member already exists. If
the member already exists, the Save Confirmation window (Figure 277 on page 505) displays:

Figure 277. Save Confirmation window

Save Confirmation
COMMAND ===> 

The following member exists and will be replaced: 
Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 
Member to be Deleted: TESTA 


ENTER to confirm Save and replace existing member 
END return to Save Request enter a different member name 



View JCL
The ISPF/PDF VIEW - File-AID/RDX Generated JCL screen shown in Figure 278 is displayed when you
select Option 7, from the Load Menu.

Figure 278. ISPF/PDF VIEW - File-AID/RDX Generated JCL


VIEW - File-AID/RDX Generated JCL --------------------------- COLUMNS 001 072 
COMMAND ===> SCROLL ===> CSR 
You are now editing the JCL that File-AID/RDX has generated to perform 
the required function. Change this JCL as desired before submitting. 

SYSIN data is contained in: TSOID01.RDX.FBCNTL.D060202.T115332
TSOID01.RDX.VBCNTL.D060202.T115332
000004 //* XFRJLOAD
000005 //*SQLID TSOID01 IS AUTHORIZED FOR ALL LOAD STEPS 
000006 //* XFRJSTRT
000007 //*------------------------------------------------------------------- 
000008 //* CLEAN1ST: - THIS STEP WILL ENSURE THAT ALL TEMPORARY FILES 
000009 //* USED IN THIS JOB ARE DELETED. 
000010 //* - THIS ALLOWS FOR KEEPING AND RERUNNING THE JOB EVEN IF 
000011 //* SUBSEQUENT STEPS FAIL. 
000012 //* - THIS JCL IS ALSO RESTARTABLE AT ANY STEP BY CODING 
000013 //* RESTART=XXXXXXXX ON THE JOBCARD. (XXXXXXXX = STEPNAME) 
000014 //*------------------------------------------------------------------- 
000015 //CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
000016 //SYSPRINT DD SYSOUT=* 
000017 //SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
000018 DELETE TSOID01.RDX.SPLIT002.D130424.T105223 
000019 DELETE TSOID01.RDX.SORT003.D130424.T105223 
000020 DELETE TSOID01.RDX.SPLIT003.D130424.T105223 

Use this screen to view and edit the load JCL generated by File-AID/RDX. Submit this JCL with the
SUBMIT command or select Option 8, Submit JCL, from the Load Menu to perform the load.

If you want to save this JCL, use the ISPF/PDF CREATE or REPLACE command before you exit this
screen. Otherwise, File-AID/RDX deletes this file and other temporary files, including the control card
PDSEs (prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix and prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix) (see also
Control Card Cleanup and CLEANCTL—File Cleanup (IEFBR14) - Optionalon page 509, page 523, and
page 535).

Control Card Cleanup

The last 2 steps, CLEANCTL and CLEANEXT, in the load and delete jobs delete the File-AID/RDX
control card PDSEs and EXTPARMS parameter files. Whether steps CLEANCTL and CLEANEXT are
commented out or executed is determined by the global job option Delete in-stream data datasets at
506 File-AID/RDX Reference

EOJ (page 83). If the job option is set to NO, File-AID/RDX control card PDSEs and EXTPARMS
parameter files created in the load and delete jobs will NOT be deleted. Keeping the datasets until all
steps run successfully allows for the restarting of the JCL at any step.

Periodically, you may want to manually delete the control card PDSEs and EXTPARMS parameter files
that are no longer needed for saved jobs to be resubmitted.

View REXX
The ISPF/PDF Edit screen shown in Figure 279 is displayed when you select Option 7, from the Load
Menu and the Execute Load interactively (online) status has been set to ON with the MODE primary
command.

Figure 279. ISPF/PDF EDIT Screen—File-AID/RDX Generated REXX

VIEW - File-AID/RDX Generated REXX COLUMNS 001 072

Command ===> SCROLL ===> CSR
You are now viewiing the REXX that File-AID/RDX has generated to perform
the required function. 

SYSIN data is contained in: TSOID01.RDX.FBCNTL.D060202.T115332
TSOID01.RDX.VBCNTL.D060202.T115332
****** ***************************** Top of Data ******************************
000001 /* REXX */ 
000002 /* TRACE R */ 
000003 MSG_STAT = MSG("OFF") 
000004 ADDRESS ISPEXEC 
000005 'LIBDEF ISPLLIB DATASET ID( ', 
000006 ' ''CPWR.MXVJ170.CXVJLOAD'', ', 
000007 ' ''DSNB10.DB01.SDSNEXIT'', ', 
000008 ' ''DSNB10.SDSNLOAD'', ', 
000009 ' ) UNCOND ' 
000010 ADDRESS TSO 'ALLOC FI(RDXMLIB) DA(''CPWR.MXVJ170.CXVJMENU'') SHR ' 
000011 ADDRESS TSO 
000012 'FREE FI(SYSOUT)' 
000013 'FREE FI(SYSPRINT)' 
000014 'FREE FI(SYSTERM)' 
000015 'FREE FI(RDXSQLCD)' 
000016 'FREE FI(UTPRINT)' 

Use this screen to view or edit the extract REXX statements generated by File-AID/RDX.

Submit JCL
Select Option 8, from the Load Menu after you have completed specifying all your load options and
are ready to submit your load request to perform the load.

You will receive a confirmation message that your job has been submitted.

Execute REXX
When the Execute Load Interactively (online) status has been set to ON with the MODE primary
command, select Option 8, from the Load Menu after you have completed specifying all your load
options to execute your load request to perform the interactive load.

Interactive Load Reports

The load execution is complete when the load reports display (see Figure 280). Use standard scrolling
commands to view the reports. Return to the Load Menu with the END command.
Load 507

Figure 280. Interactive Load Reports

Menu Utilities Compilers Help 

-------------------------------------------------------------------------------
BROWSE TSOID01.RDX.LOAD.REPORTS Line 00000000 Col 001 080 
Command ===> Scroll ===> CSR 
********************************* Top of Data **********************************
1File-AID/RDX 4.0 DB2 Table Create Report 


0 
0Table(s) Created Index(es) Created 
------------------------------- ------------------------------- 
TSOID01.CONTACT_TABLE TSOID01.CONT_IDX_X 
TSOID01.CUSTOMER_TABLE TSOID01.CUST_IDX_X 
TSOID01.ORDER_LINE_TABLE TSOID01.ORDL_IDX_X 
TSOID01.ORDER_TABLE TSOID01.ORD_IDX_X 
TSOID01.PART_TABLE TSOID01.PART_IDX_X 
TSOID01.SUPPLIER_TABLE TSOID01.SUPP_IDX_X 
0* * * END OF REPORT * * * 
1File-AID/RDX 4.0 Load Authority Report 


The SQLID has authority to perform all the job steps 
0 * * * END OF REPORT * * *
. . . . . . . . . . . . . . . . . . . . . . . . . . .

Control Card Cleanup

By default, the File-AID/RDX control card PDSEs created for the interactive load jobs will be deleted
after load execution.

The Load Process

This section describes the load process including:

• Db2 Batch Load Utility Load Job Steps;

• Db2 LOAD Utility Load JCL;
• SQL Insert Load Job Steps;
• SQL INSERT Load JCL;
• MVS Load Job Steps;
• MVS Load JCL.

Db2 Batch Load Utility Load Job Steps

This section describes the steps in the load job when you select the Db2 Batch Load Utility option
and your load includes Db2 tables.

Which of the steps described below File-AID/RDX includes in the load job
depends on:

• The processing options specified.

• The type or state of the tablespaces.

• Whether referential integrity relationships exist.

1. CREATE—Create New Tables and Indexes (XFREXEC)

This step creates any new tables and indexes that did not exist at the time of the interactive
phase of the Load function. The extract file being used must contain DDL for the tables and
indexes to be created.

See Generating CREATE DDL on page 463 for more information about how File-AID/RDX creates
new tables.
508 File-AID/RDX Reference

2. CLEAN1ST—File Cleanup (IDCAMS)

This step deletes any existing files that are to be created in this job. This enables you to keep and
rerun a JCL stream.

3. LDDRV—Load Driver (XFREXEC)

This step checks user authorizations for subsequent steps and separates the extract file into
multiple files, one file per table to be loaded.

Steps 4 through 7 are generated and executed for each table to be loaded.

4. DELTEnnn—Delete Rows (XFREXEC)

This step is generated when you request that data be deleted from a table before the load on the
Load Options screen and the table resides in a tablespace that contains multiple tables. If the
table to be loaded is the only table in the tablespace, the LOAD Utility parameter, REPLACE, is
used to delete rows from the table. This step deletes rows from a table before data is loaded.

If the table exists in a tablespace with multiple tables and the table has any dependents, File-
AID/RDX generates and executes an ALTER statement to drop foreign keys from dependent tables
prior to deleting rows. After deleting rows, File-AID/RDX generates and executes another ALTER
statement to recreate the foreign keys.

5. FIXDLnnn—IBM Db2 REPAIR Utility (DSNUTILB)

This step executes the REPAIR utility for tablespaces after all data has been deleted from tables in
a previous step.

A tablespace will be placed in copy pending status when a table is loaded with the LOG Option
parameter set to 3 (repair).

For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

6. SORTnnn—File Sort Utility (SORT) or ICETOOL Multiple File Sort

This step sorts a file containing the data to be loaded in the associated LOADnnn step.

The sort sequence is based on the clustering index for that table. If no clustering index exists, sort
sequence is based on the first defined unique index for that table. If no unique index exists, sort
sequence is based on the first-defined index for that table.

This step is generated and executed for each table to be loaded (SORT), or once for all files to be
loaded (ICETOOL).

7. LOADnnn—IBM Db2 LOAD Utility (DSNUTILB)

This step loads the data into a table from the sorted file generated in the SORT step. The RESUME
NO parameter is used when rows are to be deleted from a table. The RESUME YES parameter is
used when rows are not to be deleted from a table. The REPLACE parameter is used when rows are
to be deleted from a table and no other tables exist in the tablespace.

A return code of 4 may be acceptable. However, it is advisable to check any return code not equal
to 0. Any return code greater than 4 will stop subsequent steps from running.

For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

8. RPAIRnnn—IBM Db2 REPAIR Utility (DSNUTILB)

This step executes the REPAIR utility for required tablespaces. Required tablespaces are those
tablespaces that will be placed in copy pending or checking pending status by either the load or
delete steps and will be used by subsequent DELTE steps.

A tablespace containing a dependent table will be placed in check pending status when the
dependent table is loaded.
Load 509

A dependent table’s tablespace will be placed in check pending status when the dependent table’s
parent rows are deleted.

A tablespace will be placed in copy pending status when a table is loaded with the LOG Option
parameter set to 3 (repair).

For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

9. CHCKDATA—IBM Db2 CHECK Utility (DSNUTILB)

This step executes the CHECK DATA utility for all tablespaces that could possibly have a CHECK
PENDING restriction set by the IBM Db2 LOAD utility.

A return code of 4 may be acceptable. However, it may also indicate tablespaces are left in a
CHECK PENDING status. It is advisable to check the output from any return code not equal to 0.

For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

10. IMAGECPY—IBM Db2 COPY Utility (COPY)

This step invokes the COPY utility for all tablespaces included in the load if Log Option 1 (see
Specify DB2 Load Utility Options on page 502) is not specified in the Load Utility control cards.

For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

11. CLEANLST—File Cleanup (IDCAMS)

This step deletes all File-AID/RDX temporary files used in this job. Keeping these files until all
steps run successfully allows for the restarting of the JCL at any step.

12. CLEANCTL—File Cleanup (IEFBR14) - Optional

This step deletes the File-AID/RDX control card PDSEs. Whether step CLEANCTL is commented
out or executed is determined by the global job option Delete in-stream data datasets at EOJ (page
83). If the job option is set to NO, File-AID/RDX control card PDSEs created in the load and delete
jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows for the
restarting of the JCL at any step.

13. CLEANEXT—File Cleanup (IDCAMS) - Optional

This step deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is
commented out or executed is determined by the global job option Delete in-stream data datasets
at EOJ (page 83). If the job option is set to NO, File-AID/RDX EXTPARMS files created in the load
and delete jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows
for the restarting of the JCL at any step.

Db2 LOAD Utility Load JCL

You can code and submit the JCL on the following pages to execute the load process without
invoking the interactive portion of the Load option. The required parameter information and DD
statements for File-AID/RDX-specific steps are described following the JCL.
510 File-AID/RDX Reference

Figure 281. Db2 Load Utility Load JCL (continues on next page)

//* XFRJLOAD
//* XFRJCREA
//* --------------------------------------------------------------------
//* CREATE:- CREATE TABLES AND INDEXES
//* --------------------------------------------------------------------
//CREATE EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT), 
// PARM=(FR,7,B) 
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTRACT DD DSN=Extract file, 
// DISP=SHR 
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//SYSOUT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//SYSUDUMP DD SYSOUT=(*)
//TPTPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//SYSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DB2CREAT),
DISP=SHR
//*-------------------------------------------------------------------
//* DELTEnnn:- DELETE ALL ROWS FROM TABLE TSOID01.ORDER_TABLE
//*-------------------------------------------------------------------
//DELTEnnn EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT),
// PARM=(FR,4,B)
//*
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//RDXSQLCD DD SYSOUT=(*)
//SYSOUT DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//DLETEIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DELTEnnn),
// (DISP=SHR)
//* XFRJSTRT
//*-------------------------------------------------------------------
//* CLEAN1ST: - THIS STEP WILL ENSURE THAT ALL TEMPORARY FILES
//* USED IN THIS JOB ARE DELETED.
//* - THIS ALLOWS FOR KEEPING AND RERUNNING THE JOB EVEN IF
//* SUBSEQUENT STEPS FAIL.
//* - THIS JCL IS ALSO RESTARTABLE AT ANY STEP BY CODING
//* RESTART=XXXXXXXX ON THE JOBCARD. (XXXXXXXX = STEPNAME)
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-sort-control-file
DELETE File-AID-split-file
DELETE File-AID-check-file
DELETE File-AID-image-copy-file
SET MAXCC=0
SET LASTCC=0
/*
Load 511

Figure 282. Db2 Load Utility Load JCL (continues on next page)

//* --------------------------------------------------------------------
//* LDDRV:- LOAD DRIVER
//* THE FOLLOWING IS PERFORMED IN THIS STEP.
//* - CHECK USERS AUTHORITY TO RUN ALL THE STEPS.
//* - ENSURE TABLES EXIST.
//* - SPLIT EXTRACT FILE INTO SEPARATE LOAD FILES.
//* --------------------------------------------------------------------
//LDDRV EXEC PGM=XFREXEC,COND=(4,LT),REGION=8192K, 
// PARM=(FR,3,B)
//*
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTRACT DD DSN=extract-file,
// DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//* 
//CHCKDATA DD DSN=TSOID01.prefix.CHECK.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920),
// SPACE=(TRK,(1,1),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//*
//IMAGECPY DD DSN=TSOID01.prefix.IMAGECPY.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920),
// SPACE=(TRK,(1,1),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//* XFRJSTR1
//SPLITnnn DD DSN=TSOID01.prefix.SPLITnnn.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=VB,LRECL=302,BLKSIZE=0),
// SPACE=(TRK,(5,1),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//SRTCDnnn DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(SRTCDnnn),
// (DISP=SHR)
//SYSOUT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//SYSUDUMP DD SYSOUT=(*)
//TPTPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//SYSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DB2LCT),
// (DISP=SHR)
512 File-AID/RDX Reference

Figure 283. Db2 Load Utility Load JCL (continues on next page)

/* XFRJSORT
//*-------------------------------------------------------------------
//* SORTnnn:- SORT INPUT FILE FOR LOAD STEP LOADnnn
//*-------------------------------------------------------------------
//SORTnnn EXEC PGM=SORT,COND=(4,LT)
//*
//STEPLIB DD DSN=SYS1.SORTLIB,
// DISP=SHR
//SYSOUT DD SYSOUT=(*)
//DFSPARM DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(DFSPARM),
// (DISP=SHR)
//$ORTPARM DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix($ORTPARM),
// (DISP=SHR)
//SORTIN DD DSN=File-AID-split-file,
// DISP=(OLD,KEEP,KEEP)
//SORTOUT DD DSN=File-AID-sort-file
// DCB=(RECFM=VB,LRECL=302,BLKSIZE=0),
// SPACE=(TRK,(5,1),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//SORTWK01 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SORTWK02 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SORTWK03 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SYSIN DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(SRTCDnnn),
// DISP=SHR
//*-------------------------------------------------------------------
//* LOADnnn:- LOAD STEP FOR TABLE TSOID01.CUSTOMER_TABLE
//*-------------------------------------------------------------------
//LOADnnn EXEC PGM=DSNUTILB,PARM='DSN,TSOID01',
// REGION=8192K,COND=(4,LT)
//*
//STEPLIB DD DSN=DB2-load-library,DISP=SHR
//SORTOUT DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK01 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK02 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK03 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK04 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSUT1 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSERR DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSMAP DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSREC DD DISP=(OLD,KEEP,KEEP),
// DSN=File-AID-sort-file
//COPYnnn DD DSN=TSOID01.prefix.IMAGEnnn.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=VB,LRECL=27994,BLKSIZE=27998,DSORG=PS),
// SPACE=(27998,(20,10),RLSE),
// UNIT=SYSDA,VOL=SER=PRD900,
// DISP=(NEW,CATLG,DELETE) 
//SYSPRINT DD SYSOUT=(*)
//UTPRINT DD SYSOUT=(*)
//SYSIN DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(LOADnnn),
// (DISP=SHR)
/*
//*-------------------------------------------------------------------
//* CHCKDATA:- RUN CHECK DATA TO CHECK TABLESPACES FOR VIOLATIONS
//* OF REFERENTIAL CONSTRAINTS.
//* - CHECK DATA IS ONLY RUN AGAINST TABLESPACES THAT MAY
//* BE IN CHECK PENDING STATUS.
//* - THE "SCOPE ALL" PARAMETER IS USED.
//*-------------------------------------------------------------------
//CHCKDATA EXEC PGM=DSNUTILB,PARM='DSN,TSOID01',
// REGION=8192K,COND=(4,LT)
//*
//STEPLIB DD DSN=DB2-load-library,DISP=SHR
//SYSPRINT DD SYSOUT=(*)
//UTPRINT DD SYSOUT=(*)
//SORTOUT DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK01 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK02 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK03 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK04 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSUT1 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSERR DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSIN DD DSN=TSOID01.prefix.CHECK.Dnnnnnn.Tnnnnnn.suffix,
// DISP=(OLD,KEEP,KEEP)
//*
Load 513

Figure 284. Db2 Load Utility Load JCL



//*-------------------------------------------------------------------
//* IMAGECOPY:- THE COPY UTILITY IS RUN AGAINST TABLESPACES THAT HAVE
//* BEEN PLACED IN COPY PENDING STATUS.
//* - TABLESPACES ARE PLACED IN COPY PENDING BY SPECIFYING
//* "LOG NO" DURING THE LOAD PROCESS.
//* - A FULL IMAGECOPY WILL BE MADE.
//*-------------------------------------------------------------------
//IMAGECPY EXEC PGM=DSNUTILB,PARM='DSN,TSOID01',
// REGION=8192K,COND=(4,LT)
//*
//STEPLIB DD DSN=DB2-load-library,DISP=SHR
//SYSPRINT DD SYSOUT=(*)
//UTPRINT DD SYSOUT=(*)
//SORTOUT DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK01 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK02 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK03 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SORTWK04 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSUT1 DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//SYSERR DD UNIT=SYSDA,SPACE=(16384,(20,20),,,ROUND)
//COPYnnn DD DSN=TSOID01.prefix.IMAGEnnn.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=VB,LRECL=27994,BLKSIZE=27998,DSORG=PS),
// SPACE=(27998,(2,2),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//SYSIN DD DSN=TSOID01.prefix.IMAGECPY.Dnnnnnn.Tnnnnnn.suffix,
// DISP=(OLD,KEEP,KEEP)
//* XFRJLDND
//*-------------------------------------------------------------------
//* CLEANLST: - THIS STEP WILL PERFORM A DELETE OF ALL TEMPORARY
//* FILES USED IN THIS JOB.
//* - KEEPING THE FILES UNTIL ALL STEPS RUN SUCCESSFULLY
//* ALLOWS FOR THE RESTARTING OF THE JCL AT ANY STEP.
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-sort-control-file
DELETE File-AID-split-file
DELETE File-AID-check-file
DELETE File-AID-image-copy-file
SET MAXCC=0
SET LASTCC=0
/*
//*
//*------------------------------------------------------------------- 
//* CLEANCTL: - THIS STEP WILL PERFORM A DELETE OF THE TWO CNTL 
//* DATASETS USED BY THIS JOB FOR THE SYSIN DATA. 
//* - THE DATASETS ARE ONLY DELETED IF ALL THE PREVIOUS 
//* STEPS RUN SUCCESSFULLY; THIS ALLOWS FOR RESTARTING 
//* OF THE JOB AT ANY STEP. 
//*------------------------------------------------------------------- 
//* NOTE! - THIS STEP IS CONDITIONED ON AN OPTION ON THE GLOBAL 
//* OPTIONS SCREEN 
/*------------------------------------------------------------------- 
//CLEANCTL EXEC PGM=IEFBR14,COND=(4,LT) 
//* 
//DFBPDSE DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//DVBPDSE DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
/*------------------------------------------------------------------- 
//CLEANEXT EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 XFRJCLXT 
//SYSPRINT DD SYSOUT=*
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE extract-parms-file,
SET MAXCC=0
SET LASTCC=0
//* 
//* /*XFRJCLXT*/
//
514 File-AID/RDX Reference

CREATE Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.

The parameter information in the PARM field on the EXEC statement for the CREATE step must have
the following format:

Table 33. EXEC Statement PARM Field—CREATE Step

Default
Parameter Length Description
Value
Product FR 2 File-AID/RDX
Option 7 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the CREATE step:

Table 34. DD Statements—CREATE Step
DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTRACT File containing the extracted data.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSPRINT Standard output stream.
SYSTERM Output class for runtime errors.
TPTPRINT Standard output stream for optional diagnostics.
SYSIN DDL for tables and indexes to be created (see Figure 285).

Create DDL
Member DB2CREAT in the SYSIN control card PDSE contains the DDL for tables and indexes to be
created (see Figure 285)
Load 515

Figure 285. Db2 Create DDL (member DB2CREAT)

--CREATE TABLE/INDEX DDL FOR: TSOID02.CUSTOMER_TABLE

--
CREATE TABLE TSOID02.CUSTOMER_TABLE
(CUSTOMER_NUMBER CHAR(6) NOT NULL WITH DEFAULT,
COMPANY_NAME CHAR(30) NOT NULL WITH DEFAULT,
ADDRESS CHAR(30) NOT NULL WITH DEFAULT,
CITY CHAR(25) NOT NULL WITH DEFAULT,
STATE CHAR(2) NOT NULL WITH DEFAULT,
ZIP_CODE CHAR(9) NOT NULL WITH DEFAULT,
COUNTRY CHAR(20) NOT NULL WITH DEFAULT,
AREA_CODE CHAR(3) NOT NULL WITH DEFAULT,
TELEPHONE_NUM CHAR(7) NOT NULL WITH DEFAULT,
CONTACT_NAME CHAR(30) NOT NULL WITH DEFAULT,
CONTACT_TITLE CHAR(30),
CONTACT_ADDR CHAR(30),
CONTACT_CITY CHAR(25),
CONTACT_STATE CHAR(2),
CONTACT_ZIP CHAR(9),
CONTACT_COUNTRY CHAR(10),
CONTACT_AREA_CD CHAR(3),
CONTACT_TELEPHONE CHAR(7),
PRIMARY KEY (CUSTOMER_NUMBER)
) IN DATABASE TSOID01H;
--
CREATE UNIQUE INDEX TSOID02.CUST_IDX
ON TSOID02.CUSTOMER_TABLE
(CUSTOMER_NUMBER ASC)
CLUSTER
SUBPAGES 4
BUFFERPOOL BP0
C
--
--CREATE TABLE/INDEX DDL FOR: TSOID02.CONTACT_TABLE
--
CREATE TABLE TSOID02.CONTACT_TABLE
(CUSTOMER_NUMBER CHAR(6) NOT NULL WITH DEFAULT,
CONTACT_ID CHAR(2) NOT NULL WITH DEFAULT,
CONTACT_NAME CHAR(30) NOT NULL WITH DEFAULT,
TITLE CHAR(30),
CONTACT_CODE CHAR(4) NOT NULL WITH DEFAULT,
ADDRESS CHAR(30) NOT NULL WITH DEFAULT,
CITY CHAR(25) NOT NULL WITH DEFAULT,
STATE CHAR(2) NOT NULL WITH DEFAULT,
ZIP_CODE CHAR(9) NOT NULL WITH DEFAULT,
COUNTRY CHAR(20) NOT NULL WITH DEFAULT,
AREA_CODE CHAR(3) NOT NULL WITH DEFAULT,
TELEPHONE_NUM CHAR(7) NOT NULL WITH DEFAULT,
PRIMARY KEY (CUSTOMER_NUMBER,
CONTACT_ID)
) IN DATABASE TSOID01H;
--
CREATE UNIQUE INDEX TSOID02.CONT_IDX
ON TSOID02.CONTACT_TABLE
(CUSTOMER_NUMBER ASC,
CONTACT_ID ASC)
CLUSTER
SUBPAGES 4
BUFFERPOOL BP0
CLOSE YES;
--
--ALTER TO ADD FOREIGN KEYS TO ALL TABLES
--
ALTER TABLE TSOID02.CONTACT_TABLE
ADD FOREIGN KEY
(CUSTOMER_NUMBER)
REFERENCES TSOID02.CUSTOMER_TABLE
ON DELETE CASCADE;

LDDRV Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.
516 File-AID/RDX Reference

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 35:

Table 35. EXEC Statement PARM Field——LDDRV Step

Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option 3 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the LDDRV step:

Table 36. DD Statements—LDDRV Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTRACT File-AID/RDX extract file name.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367.
CHCKDATA Output file to which the CHECK utility control statements are written.
IMAGECPY Output file to which the COPY utility statements are written.
SPLITnnn Output file to which File-AID/RDX writes data for a single table from the extract file.
• One file for each table, where 001≤ nnn≤ 099.
• The LRECL and BLKSIZE parameters must be large enough to hold the
extracted records.
• The SPACE parameters must be large enough to hold all extracted records.
SRTCDnnn Control card used by File-AID/RDX to sort each split file before the data is loaded into a table.
• One member (SRTCDnnn) for each table in the control card PDSE.
• RECFM must be F or FB. LRECL must be 80.
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSPRINT Standard output stream.
SYSTERM Output class for runtime errors.
TPTPRINT Standard output stream for optional diagnostics.
SYSIN File-AID/RDX’s Load Control Table. Used to verify authorities and identify column mapping
details. See Load Control Table for more information.

Load Control Table

The Load Control Table (member DB2LCT in the SYSIN control card PDSE) contains information
about the source and target tables (see Figure 286 on page 517). It is the input (SYSIN) to the LDDRV
step.
Load 517

Figure 286. Db2 Load Control Table (DB2LCT)

*FR.17.02.00 ---------- D B 2 L O A D C O N T R O L T A B L E -------------

*
*
* SOURCE AND TARGET OBJECTS 
* ----------------------------------
SC: TSOID01
ST: CUSTOMER_TABLE
TI: DEL=R DEP=N ROW COUNT= 2001 NNN E REP=N 
TC: TSOID02
TT: CUSTOMER_TABLE
*
* TABLE CONTROL NUMBER
CN: 001
*
* NULL CCSID
* TARGET COLUMN NAME DEF SOURCE COLUMN NAME TYPE OFFSET OFFSET LENGTH TARGET SOURCE
*-------------------- --- -------------------- ---- ------ ------ ------ ------ ------
CUSTOMER_NUMBER N CUSTOMER_NUMBER C 16 6
COMPANY_NAME N COMPANY_NAME C 22 30
ADDRESS N ADDRESS C 52 30
CITY N CITY C 82 25
STATE N STATE C 107 2
ZIP_CODE N ZIP_CODE C 109 9
COUNTRY N COUNTRY C 118 20
AREA_CODE N AREA_CODE C 138 3
TELEPHONE_NUM N TELEPHONE_NUM C 141 7
CONTACT_NAME N CONTACT_NAME C 148 30
CONTACT_TITLE N CONTACT_TITLE C 178 0 30
CONTACT_ADDR N CONTACT_ADDR C 208 2 30
CONTACT_CITY N CONTACT_CITY C 238 4 25
CONTACT_STATE N CONTACT_STATE C 263 6 2
CONTACT_ZIP N CONTACT_ZIP C 265 8 9
CONTACT_COUNTRY N CONTACT_COUNTRY C 274 10 10
CONTACT_AREA_CD N CONTACT_AREA_CD C 284 12 3
CONTACT_TELEPHONE N CONTACT_TELEPHONE C 287 14 7
*
*
* SOURCE AND TARGET OBJECTS 
* ----------------------------------
SC: TSOID01
ST: CONTACT_TABLE
TI: DEL=R DEP=Y ROW COUNT= 1492 NNN E REP=N 
TC: TSOID02
TT: CONTACT_TABLE
*
* TABLE CONTROL NUMBER
CN: 002
*
* NULL CCSID
* TARGET COLUMN NAME DEF SOURCE COLUMN NAME TYPE OFFSET OFFSET LENGTH TARGET SOURCE
*-------------------- --- -------------------- ---- ------ ------ ------ ------ ------
CUSTOMER_NUMBER N CUSTOMER_NUMBER C 2 6
CONTACT_ID N CONTACT_ID C 8 2
CONTACT_NAME N CONTACT_NAME C 10 30
TITLE N TITLE C 40 0 30
CONTACT_CODE N CONTACT_CODE C 70 4
ADDRESS N ADDRESS C 74 30
CITY N CITY C 104 25
STATE N STATE C 129 2
ZIP_CODE N ZIP_CODE C 131 9
COUNTRY N COUNTRY C 140 20
AREA_CODE N AREA_CODE C 160 3
TELEPHONE_NUM N TELEPHONE_NUM C 163 7
*

Each source/target pair is identified by its table control number and for each, there are two tables.
The first table contains the following information:

Table 37. Load Control Table—Source and Target Table Information

Field Name Description
SC The source creator ID.
ST The source table; the table extracted from.
TI Target Information
518 File-AID/RDX Reference

Table 37. Load Control Table—Source and Target Table Information (Continued)
Field Name Description
DEL For T: tables only. Indicates whether or not rows should be deleted before the load is
executed.
Y Delete rows before loading using the DELTEnnn step.
N Do not delete rows before loading.
R Delete rows using LOAD utility’s REPLACE parameter.
DEP For TT: tables only. Indicates whether or not File-AID/RDX should attempt to replace (update)
existing rows from the target table with rows from the source table.
Y Yes
N No
ROW COUNT For T: tables only. Identifies the number of rows to be loaded into the target table.
N or Y Represents the D record supplement indicator (see also Product Record — 0 on page 378).
N or Y Represents the extract IMPLICITLY HIDDEN columns indicator (see also Extract IMPLICITLY
HIDDEN columns on page 251).
N, C or V Represents the compression indicator (see also Compress on page 339).
E or U Represents the encoding indicator (see also DB2 Format on page 339).
REP=N or Y Represents the replace matches indicator (see also Replace Matches on page 500).
TC The target creator ID.
TT The target table; the table to be loaded.
CN Table control number; corresponds to the Hnnn records in the extract file.

The second table contains the following column mapping information:

Table 38. Load Control Table—Column Mapping Information

Field Name Description
Target Column Name Contains a list of the names of the target columns. This information is taken from the extract
file and the Column Mapping screen. If you mapped any target columns to source columns
with different names, those mappings are reflected here.
Def Indicates whether the target column will contain its default value or nulls.
Y Yes – The column will contain the default value defined for it.
N No – The column will contain the value of the source column.
Source Column Name Contains a list of the names of the source columns. This information is taken from the extract
file.
Type Indicates the data type of the target columns. This information is taken from the extract file
and the Column Mapping screen.
Offset Indicates the offset of the source data in the extract file.
Null Offset Indicates the offset of null indicators for the source data in the extract file.
Length Indicates the length of the source columns. This information is taken from the extract file and
the Column Mapping screen.
CCSID Target Indicates the CCSID for the target column if it is Unicode encoded.
CCSID Source Indicates the CCSID for the source column if it is Unicode encoded.

DELTEnnn Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.
Load 519

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 35:

Table 39. EXEC Statement PARM Field—DELTEnnn Step

Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option 4 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the DELTEnnn step:

Table 40. DD Statements—DELTEnnn Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSOUT Output class for error messages and reports.
SYSPRINT Standard output stream.
SYSTERM Output class for runtime errors.
TPTPRINT Standard output stream for optional diagnostics.
DLETEIN File that contains the delete data information (member DELTEnnn in the control card PDSE).

FIXDLnnn
This step uses the standard Db2 REPAIR utility to repair a tablespace due to previous delete step. Refer
to the IBM Db2 Command and Utility Reference for a full description of how to set up this step.

SORTnnn Step DD Statements

This step uses your site’s SORT utility. The following DD statements are required for the SORT step:

Table 41. DD Statements—SORT Step

DD Statement Description
STEPLIB Your site’s SORT library.
SORTIN SPLIT file from the LDDRV step.
SORTOUT Output from the SORT.
SYSOUT Output class for messages and reports.
SORTWK01
SORTWK02 Work files required by the SORT utility.
SORTWK03
SYSIN File that will contain the SORT cards generated by the LDDRV step (member SRTCDnnn in the
SYSIN control card PDSE).
520 File-AID/RDX Reference

ICETOOL Step DD Statements

This optional step uses the ICETOOL utility. The following DD statements are required for the
ICETOOL step:

Table 42. DD Statements—ICETOOL Step

DD Statement Description
STEPLIB Your site’s SORT library.
DFSPARM Supplies DFSORT program control statements and EXEC statement PARM options.
$ORTPARM Supplies SYNCSORT program control statements and EXEC statement PARM options.
SYSOUT Output class for messages and reports.
TOOLMSG Messages from the ICETOOL utility.
DFSMSG Messages from the individual sorts.
CnnnCNTL File that will contain the SORT cards generated by the LDDRV step. Associated with each SnnnIN
DD.
SnnnIN SPLIT file from the LDDRV step. A unique DD generated for each split file to sort.
SnnnOUT Output from the SORT. A unique DD generated for each sort output file.
SORTWK01
SORTWK02 Work files required by the SORT utility.
SORTWK03
TOOLIN File that associates each CnnnCNTL, SnnnIN, and SnnnOUT DD for ICETOOL to sort.

LOADnnn
This step uses the standard Db2 LOAD utility.

The SYSREC DD must reference the OUTPUT file from the corresponding SORT step. Refer to the IBM
Db2 Command and Utility Reference for a full description of how to set up this step. The load data is
contained in member LOADnnn of the SYSIN control card PDSE (see Figure 287).
Load 521

Figure 287. SYSIN Load Data (member LOADnnn)

LOAD DATA
REPLACE
RESUME NO
COPYDDN COPYnnn
ENFORCE NO
LOG NO
INTO TABLE TSOID01.CUSTOMER_TABLE
(
CUSTOMER_NUMBER POSITION(17)
CHAR (6)
,
COMPANY_NAME POSITION(23)
CHAR (30)
,
ADDRESS POSITION(53)
CHAR (30)
,
CITY POSITION(83)
CHAR (25)
,
STATE POSITION(108)
CHAR (2)
,
ZIP_CODE POSITION(110)
CHAR (9)
,
COUNTRY POSITION(119)
CHAR (20)
,
AREA_CODE POSITION(139)
CHAR (3)
,
TELEPHONE_NUM POSITION(142)
CHAR (7)
,
CONTACT_NAME POSITION(149)
CHAR (30)
,
CONTACT_TITLE POSITION(179)
CHAR (30)
NULLIF (1:2) = X'FFFF',
CONTACT_ADDR POSITION(209)
CHAR (30)
NULLIF (3:4) = X'FFFF',
CONTACT_CITY POSITION(239)
CHAR (25)
NULLIF (5:6) = X'FFFF',
CONTACT_STATE POSITION(264)
CHAR (2)
NULLIF (7:8) = X'FFFF',
CONTACT_ZIP POSITION(266)
CHAR (9)
NULLIF (9:10) = X'FFFF',
CONTACT_COUNTRY POSITION(275)
CHAR (10)
NULLIF (11:12) = X'FFFF',
CONTACT_AREA_CD POSITION(285)
CHAR (3)
NULLIF (13:14) = X'FFFF',
CONTACT_TELEPHONE POSITION(288)
CHAR (7)
NULLIF (15:16) = X'FFFF'
)

RPAIRnnn
This step uses the standard Db2 REPAIR utility. Refer to the IBM Db2 Command and Utility Reference for
a full description of how to set up this step.

CHCKDATA
This step uses the standard Db2 CHECK utility.

The SYSIN DD must reference the same file referenced by the CHCKDATA DD in the LDDRV step.
Refer to the IBM Db2 Command and Utility Reference for a full description of how to set up this step.
522 File-AID/RDX Reference

IMAGECPY
This step uses the standard Db2 COPY utility.

The SYSIN DD must reference the same file referenced by the IMAGECPY DD in the LDDRV step.
Refer to the IBM Db2 Command and Utility Reference for a full description of how to set up this step.

COPYnnn
This step uses the Db2 Inline Image Copy utility. Refer to the IBM Db2 Command and Utility Reference
for a full description of how to set up this step.

Return Codes
An execution return code (RC) appears in the output listing.For return codes other than 0, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return Description
Code
0 Job ran to completion without error.
4 Job ran to completion without error, warnings issued.
8 Job ran with error. Subsequent job steps stopped.
16 Severe error, job aborted.

SQL Insert Load Job Steps

This section describes the steps in the load job when you select the SQL Insert option and your load
includes Db2 tables.

Which of the steps described below File-AID/RDX includes in the load job
depends on:

• The processing options specified.

• Whether referential integrity relationships exist.

1. CREATE—Create New Tables and Indexes (XFREXEC)

This step creates any new tables and indexes that did not exist at the time of the interactive
portion of the Load function. The extract file being used must contain DDL for the tables and
indexes to be created.

See Generating CREATE DDL on page 463 for more information about how File-AID/RDX creates
new tables.

2. CLEAN1ST—File Cleanup (IDCAMS)

This step deletes any existing files that are to be created in this job. This enables you to keep and
rerun a JCL stream.

3. LDDRV—Load Driver (XFREXEC)

This step checks user authorization for subsequent steps and separates the extract file into
multiple files, one file per table to be loaded.

4. SORTnnn—File Sort Utility (SORT) or ICETOOL Multiple File Sort

This step sorts file(s) containing the data to be loaded in the associated LDSQLIN step.
Load 523

The sort sequence is based on the clustering index for that table. If no clustering index exists, sort
sequence is based on the primary index for that table. If no primary index exists, sort sequence is
based on the first-defined index for that table.

This step is generated and executed for each table to be loaded (SORT), or once for all files to be
loaded (ICETOOL).

5. DELETE—Delete Rows (XFREXEC)

This step is generated when you specify Yes in the Delete ALL Existing Data field on the SQL
Insert Load Option screen. Db2 delete rules are in effect for this step.

6. LDSQLIN—SQL Insert (XFREXEC)

This step generates and executes the SQL INSERT and UPDATE statements to load data into tables
from the sorted files created in step 4. If you specified Yes in the Replace Matches field on the
Insert/Load Option screen and the target table contains a unique key, File-AID/RDX will replace
existing data in the target table with data from the extract file. If you specified No in the Replace
Matches field and the target table contains a unique key, File-AID/RDX will discard data that
already exists in the target table.

7. CLEANLST—File Cleanup (IDCAMS)

This step deletes all File-AID/RDX temporary files used in this job. Deleting these files in the last
job step enables the job to be restarted in any prior step.

8. CLEANCTL—File Cleanup (IEFBR14) - Optional

This step deletes the File-AID/RDX control card PDSEs. Whether step CLEANCTL is commented
out or executed is determined by the global job option Delete in-stream data datasets at EOJ (page
83). If the job option is set to NO, File-AID/RDX control card PDSEs created in the load and delete
jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows for the
restarting of the JCL at any step.

9. CLEANEXT—File Cleanup (IDCAMS) - Optional

This step deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is
commented out or executed is determined by the global job option Delete in-stream data datasets
at EOJ (page 83). If the job option is set to NO, File-AID/RDX EXTPARMS files created in the load
and delete jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows
for the restarting of the JCL at any step.

SQL INSERT Load JCL

You can code and submit the JCL on the following pages to execute the load process without
invoking the interactive phase of the Load function. The required parameter information and DD
statements for File-AID/RDX-specific steps are described following the JCL.
524 File-AID/RDX Reference

Figure 288. SQL Insert Load JCL (continues on next page)

//* --------------------------------------------------------------------
//* CREATE:- CREATE TABLES AND INDEXES.
//* --------------------------------------------------------------------
//CREATE EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT),
// PARM=(FR,7,B)
//*
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTRACT DD DSN=extract-file,
// DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//SYSOUT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//SYSUDUMP DD SYSOUT=(*)
//TPTPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//SYSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DB2CREAT),
DISP=SHR
//* XFRJSTRT
//*-------------------------------------------------------------------
//* CLEAN1ST: - THIS STEP WILL ENSURE THAT ALL TEMPORARY FILES
//* USED IN THIS JOB ARE DELETED.
//* - THIS ALLOWS FOR KEEPING AND RERUNNING THE JOB EVEN IF
//* SUBSEQUENT STEPS FAIL.
//* - THIS JCL IS ALSO RESTARTABLE AT ANY STEP BY CODING
//* RESTART=XXXXXXXX ON THE JOBCARD. (XXXXXXXX = STEPNAME)
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-split-file
SET MAXCC=0
SET LASTCC=0
/*
//* 
//* --------------------------------------------------------------------
//* LDDRV:- LOAD DRIVER
//* THE FOLLOWING IS PERFORMED IN THIS STEP.
//* - CHECK USERS AUTHORITY TO RUN ALL THE STEPS
//* - ENSURE TABLES EXIST.
//* - SPLIT EXTRACT FILE INTO SEPARATE LOAD FILES.
//* --------------------------------------------------------------------
//LDDRV EXEC PGM=XFREXEC,COND=(4,LT),REGION=8192K,
// PARM=(FR,3,B)
//*
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTRACT DD DSN=extract-file,
// DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//*
//DISCARDS DD DSN=File-AID-discard-file,
// DCB=(RECFM=VB,LRECL=302,BLKSIZE=306,DSORG=PS),
// SPACE=(TRK,(1,1),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//*
Load 525

Figure 289. SQL Insert Load JCL (continues on the next page)

//* XFRJSTR1
//SPLITnnn DD DSN=File-AID-split-file,
// DCB=(RECFM=VB,LRECL=302,BLKSIZE=0),
// SPACE=(TRK,(5,1),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//SRTCDnnn DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(SRTCDnnn),
// DISP=SHR
//SYSOUT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//SYSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DB2LCT),
// (DISP=SHR)
//*
//*-------------------------------------------------------------------
//* SORTnnn:- SORT INPUT FILE FOR TABLE TSOID01.CUSTOMER_TABLE
//*-------------------------------------------------------------------
//SORTnnn EXEC PGM=SORT,COND=(4,LT)
//*
//STEPLIB DD DSN=SYS1.SORTLIB,
// DISP=SHR
//SYSOUT DD SYSOUT=(*)
//DFSPARM DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(DFSPARM),
// (DISP=SHR)
//$ORTPARM DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix($ORTPARM),
// (DISP=SHR)
//SORTIN DD DSN=File-AID-split-file,
// DISP=(OLD,KEEP,KEEP)
//SORTOUT DD DSN=File-AID-sort-file,
// DCB=(RECFM=VB,LRECL=103,BLKSIZE=27998),
// SPACE=(27998,(2,2),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//SORTWK01 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SORTWK02 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SORTWK03 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SYSIN DD DSN=TSOID01.prefix.FBCNTS.Dnnnnnn.Tnnnnnn.suffix(SRTCDnnn),
// DISP=(OLD,KEEP,KEEP)
//*
//*-------------------------------------------------------------------
//* DELETE:- DELETE ROWS FROM SPECIFIED TABLES
//*-------------------------------------------------------------------
//DELETE EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT),
// PARM=(FR,6,B)
//*
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//SYSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DB2LCT),
// (DISP=SHR)
//DLRPT DD SYSOUT=(*)
//SYSOUT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//* 
526 File-AID/RDX Reference

Figure 290. SQL Insert Load JCL

//*-------------------------------------------------------------------
//* LOAD SQL INSERT:- LOAD TO TABLES USING SQL INSERT
//*-------------------------------------------------------------------
//LDSQLIN EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT),
// PARM=(FR,5,B)
//*
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//SYSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DB2LCT),
// (DISP=SHR)
//LOADIN DD DSN=TSOID01.prefix.SORTnnn.Dnnnnnn.Tnnnnnn.suffix,
// DISP=(OLD,KEEP,KEEP)
//XCPTNRPT DD SYSOUT=(*)
//TOTLSRPT DD SYSOUT=(*)
//COMMTRPT DD SYSOUT=(*)
//RDERRORS DD SYSOUT=(*)
//SYSOUT DD SYSOUT=(*)
//DISCARDS DD DSN=TSOID01.DISCARD,
// DISP=MOD
//SYSPRINT DD SYSOUT=(*)
//SYSUDUMP DD SYSOUT=(*)
//TPTPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//* XFRLDND
//*-------------------------------------------------------------------
//* CLEANLST: - THIS STEP WILL PERFORM A DELETE OF ALL TEMPORARY
//* FILES USED IN THIS JOB.
//* - KEEPING THE fileS UNTIL ALL STEPS RUN SUCCESSFULLY
//* ALLOWS FOR THE RESTARTING OF THE JCL AT ANY STEP.
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-split-file
SET MAXCC=0
SET LASTCC=0
/*
//* 
//*------------------------------------------------------------------- 
//* CLEANCTL: - THIS STEP WILL PERFORM A DELETE OF THE TWO CNTL 
//* DATASETS USED BY THIS JOB FOR THE SYSIN DATA. 
//* - THE DATASETS ARE ONLY DELETED IF ALL THE PREVIOUS 
//* STEPS RUN SUCCESSFULLY; THIS ALLOWS FOR RESTARTING 
//* OF THE JOB AT ANY STEP. 
//*------------------------------------------------------------------- 
//* NOTE! - THIS STEP IS CONDITIONED ON AN OPTION ON THE GLOBAL 
//* OPTIONS SCREEN 
/*------------------------------------------------------------------- 
//CLEANCTL EXEC PGM=IEFBR14,COND=(4,LT) 
//* 
//DFBPDSE DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//DVBPDSE DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//*------------------------------------------------------------------- 
//* CLEANCTL: - THIS STEP WILL PERFORM A DELETE OF THE EXTPARMS 
//* DATASETS USED BY THIS JOB FOR. 
//* - THE DATASETS ARE ONLY DELETED IF ALL THE PREVIOUS 
//* STEPS RUN SUCCESSFULLY; THIS ALLOWS FOR RESTARTING 
//* OF THE JOB AT ANY STEP. 
//*------------------------------------------------------------------- 
//* NOTE! - THIS STEP IS CONDITIONED ON AN OPTION ON THE GLOBAL 
//* OPTIONS SCREEN 
/*-------------------------------------------------------------------
//CLEANEXT EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 XFRJCLXT 
//SYSPRINT DD SYSOUT=*
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE extract-parms-file,
SET MAXCC=0
SET LASTCC=0
//* 
//* /*XFRJCLXT*/
//
Load 527

CREATE Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.

The parameter information in the PARM field on the EXEC statement for the CREATE step must have
the following format:

Table 43. EXEC Statement PARM Field—CREATE Step

Default
Parameter Length Description
Value
Product FR 2 File-AID/RDX
Option 7 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the CREATE step:

Table 44. DD Statements—CREATE Step
DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTRACT File containing the extracted data.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSPRINT Standard output stream.
SYSTERM Output class for runtime errors.
TPTPRINT Standard output stream for optional diagnostics.
SYSIN DDL for tables and indexes to be created (see Figure 291).

Create DDL
Member DB2CREAT in the SYSIN control card PDSE contains the DDL for tables and indexes to be
created (see Figure 291).
528 File-AID/RDX Reference

Figure 291. Create DDL (member DB2CREAT)

--
--CREATE TABLE/INDEX DDL FOR: TSOID02.CUSTOMER_TABLE
--
CREATE TABLE TSOID02.CUSTOMER_TABLE
(CUSTOMER_NUMBER CHAR(6) NOT NULL WITH DEFAULT,
COMPANY_NAME CHAR(30) NOT NULL WITH DEFAULT,
ADDRESS CHAR(30) NOT NULL WITH DEFAULT,
CITY CHAR(25) NOT NULL WITH DEFAULT,
STATE CHAR(2) NOT NULL WITH DEFAULT,
ZIP_CODE CHAR(9) NOT NULL WITH DEFAULT,
COUNTRY CHAR(20) NOT NULL WITH DEFAULT,
AREA_CODE CHAR(3) NOT NULL WITH DEFAULT,
TELEPHONE_NUM CHAR(7) NOT NULL WITH DEFAULT,
CONTACT_NAME CHAR(30) NOT NULL WITH DEFAULT,
CONTACT_TITLE CHAR(30),
CONTACT_ADDR CHAR(30),
CONTACT_CITY CHAR(25),
CONTACT_STATE CHAR(2),
CONTACT_ZIP CHAR(9),
CONTACT_COUNTRY CHAR(10),
CONTACT_AREA_CD CHAR(3),
CONTACT_TELEPHONE CHAR(7),
PRIMARY KEY (CUSTOMER_NUMBER)
) IN DATABASE TSOID01H;
--
CREATE UNIQUE INDEX TSOID02.CUST_IDX
ON TSOID02.CUSTOMER_TABLE
(CUSTOMER_NUMBER ASC)
CLUSTER
SUBPAGES 4
BUFFERPOOL BP0
CLOSE YES;
--
--CREATE TABLE/INDEX DDL FOR: TSOID02.CONTACT_TABLE
--
CREATE TABLE TSOID02.CONTACT_TABLE
(CUSTOMER_NUMBER CHAR(6) NOT NULL WITH DEFAULT,
CONTACT_ID CHAR(2) NOT NULL WITH DEFAULT,
CONTACT_NAME CHAR(30) NOT NULL WITH DEFAULT,
TITLE CHAR(30),
CONTACT_CODE CHAR(4) NOT NULL WITH DEFAULT,
ADDRESS CHAR(30) NOT NULL WITH DEFAULT,
CITY CHAR(25) NOT NULL WITH DEFAULT,
STATE CHAR(2) NOT NULL WITH DEFAULT,
ZIP_CODE CHAR(9) NOT NULL WITH DEFAULT,
COUNTRY CHAR(20) NOT NULL WITH DEFAULT,
AREA_CODE CHAR(3) NOT NULL WITH DEFAULT,
TELEPHONE_NUM CHAR(7) NOT NULL WITH DEFAULT,
PRIMARY KEY (CUSTOMER_NUMBER,
CONTACT_ID)
) IN DATABASE TSOID01H;
--
CREATE UNIQUE INDEX TSOID02.CONT_IDX
ON TSOID02.CONTACT_TABLE
(CUSTOMER_NUMBER ASC,
CONTACT_ID ASC)
CLUSTER
SUBPAGES 4
BUFFERPOOL BP0
CLOSE YES;
--
--ALTER TO ADD FOREIGN KEYS TO ALL TABLES
--
ALTER TABLE TSOID02.CONTACT_TABLE
ADD FOREIGN KEY
(CUSTOMER_NUMBER)
REFERENCES TSOID02.CUSTOMER_TABLE
ON DELETE CASCADE;

LDDRV Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.
Load 529

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 45:

Table 45. EXEC Statement PARM Field——LDDRV Step

Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option 3 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the LDDRV step:

Table 46. DD Statements—LDDRV Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTRACT File-AID/RDX extract file name.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
DISCARDS File-AID/RDX discard file.
SPLITnnn Output file to which File-AID/RDX writes data for a single table from the extract file.

• One file for each table, where 001 ≤ nnn≤ 099

• The LRECL and BLKSIZE parameters must be large enough to hold the extracted records.

• The SPACE parameters must be large enough to hold all extracted records.
SRTCDnnn Control card used by File-AID/RDX to sort each split file before the data is loaded into a table.
• One member (SRTCDnnn) for each table in the control card PDSE.
• RECFM must be F or FB. LRECL must be 80.
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSPRINT Standard output stream.
SYSTERM Output class for runtime errors.
TPTPRINT Standard output stream for optional diagnostics.
SYSIN File-AID/RDX’s Load Control Table (member DB2LCT). Used to verify authorities and identify
tables that need to be created. See Db2 Load Control Table for more information.

Db2 Load Control Table

The Load Control Table (member DB2LCT in the SYSIN control card PDSE) contains information
about the source and target tables (see Figure 292). It is the input (SYSIN) to the LDDRV step.
530 File-AID/RDX Reference

Figure 292. Load Control table (member DB2LCT)

*FR.17.02.00 F=2------- L O A D C O N T R O L T A B L E ---------------

*
*
* SOURCE AND TARGET OBJECTS 
* ---------------------------------- 
SC: FARDX 
ST: PART_TABLE 
TI: DEL=Y DEP=N ROW COUNT= 29 NNN E REP=N 
TC: FARDX 
TT: PART_TABLE 
* 
* TABLE CONTROL NUMBER 
CN: 001 
* 
* 
* NULL CCSID
* TARGET COLUMN NAME DEF SOURCE COLUMN NAME TYPE OFFSET OFFSET LENGTH TARGET SOURCE
*-------------------- --- -------------------- ---- ------ ------ ------ ------ ------
PART_NUMBER N PART_NUMBER C 14 6
PART_NAME N PART_NAME C 20 25
EFFECT_DATE N EFFECT_DATE DT 45 10 
EQUIVALENT_PART N EQUIVALENT_PART C 55 0 6
PURCH_PRICE N PURCH_PRICE D 61 2 9,2 
SETUP_COST N SETUP_COST D 66 4 9,2 
LABOR_COST N LABOR_COST D 71 6 9,2 
UNIT_OF_MEASURE N UNIT_OF_MEASURE C 76 8 2 
MATERIAL_COST N MATERIAL_COST D 78 10 9,2 
REWORK_COST N REWORK_COST D 83 12 9,2 
AVAILABILITY_IND N AVAILABILITY_IND C 88 1 
ENGR_DRAW_NUM N ENGR_DRAW_NUM C 89 6 
* 
* 
* SOURCE AND TARGET OBJECTS 
* ---------------------------------- 
SC: FARDX 
ST: ORDER_TABLE 
TI: DEL=Y DEP=N ROW COUNT= 35 NNN E REP=N 
TC: FARDX 
TT: ORDER_TABLE 
* 
* TABLE CONTROL NUMBER 
CN: 002 
* 
* NULL CCSID
* TARGET COLUMN NAME DEF SOURCE COLUMN NAME TYPE OFFSET OFFSET LENGTH TARGET SOURCE
*-------------------- --- -------------------- ---- ------ ------ ------ ------ ------
ORDER_NUMBER N ORDER_NUMBER C 12 6
CUST_NUM N CUST_NUM C 18 6
SOC_SEC_NUM N SOC_SEC_NUM C 24 11
CREDIT_CARD_NUM N CREDIT_CARD_NUM C 35 16
ORD_TYPE N ORD_TYPE C 51 8

Each source/target pair is identified by its table control number and for each, there are two tables.
The first table contains the following information:

Table 47. Db2 Load Control Table—Source and Target Table Information
Field Name Description
SC: The source table creator ID
ST: The source table name
TI: Table information
For TT: tables only. Indicates whether or not rows should be deleted before the load is executed.
DEL Y Delete rows before loading using the DELETE step.
N Do not delete rows before loading.
Load 531

Table 47. Db2 Load Control Table—Source and Target Table Information (Continued)
Field Name Description
For TT: tables only. Indicates whether or not File-AID/RDX should attempt to replace (update) existing
rows from the target table with rows from the source table.
DEP
Y Yes
N No
Row Count For TT: tables only. Identifies the number of rows to be loaded into the target table.
N or Y Represents the D record supplement indicator (see also Product Record — 0 on page 378).
Represents the extract IMPLICITLY HIDDEN columns indicator (see also Extract IMPLICITLY HIDDEN
N or Y
columns on page 251).
N, C or V Represents the compression indicator (see also Compress on page 339).
E or U Represents the encoding indicator (see also DB2 Format on page 339).
REP=N or Y Represents the replace matches indicator (see also Replace Matches on page 500).
TC: The target table creator ID
TT: The target table name
Table Control Number
Cnnn: The table control number has the prefix C for Create.

The second table contains the following column information:

Table 48. Load Control Table—Column Mapping Information

Field Name Description
Target / Contains a list of the target and source column names. the source column names are identified with
*Source an asterisk (*).This information is taken from the extract file and the Column Mapping screen. If you
Column Name mapped any target columns to source columns with different names, those mappings are reflected
here.
Def Indicates whether the target column will contain the default value, a literal default value, or nulls.
Y Yes - The column will contain the default value defined for it.
N No - The column will contain the value of the source column.
Literal - The column will contain the value of the literal definition (Lnn) assigned to it during
L
column mapping.
Type Indicates the data type of the target columns. This information is taken from the extract file and the
Column Mapping screen.
Offset Indicates the offset for the source data in the extract file.
Null Offset Indicates the offset for null indicators for the source data in the extract file.
Length Indicates the length of the source columns. This information is taken from the extract file and the
Column Mapping screen.
CCSID Target Indicates the CCSID for the target column if it is Unicode encoded.
CCSID Source Indicates the CCSID for the source column if it is Unicode encoded.

DELETE Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.
532 File-AID/RDX Reference

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 49:

Table 49. EXEC Statement PARM Field—DELTEnnn Step

Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option 6 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the DELETE step:

Table 50. DD Statements—DELETE Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
SYSIN File-AID/RDX’s Load Control Table. Used to verify authorities and identify tables that need to
have all data deleted. See Db2 Load Control Table for more information.
DLRPT Output class for File-AID/RDX Delete Report.
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSPRINT Standard output stream.
TPTPRINT Standard output stream for optional diagnostics.
SYSTERM Output class for runtime errors.

SORTnnn Step DD Statements

This step uses your site’s SORT utility. The following DD statements are required for the SORT step:

Table 51. DD Statements—SORT Step

DD Statement Description
STEPLIB Your site’s SORT library.
SORTIN SPLIT file from the LDDRV step.
SORTOUT Output from the SORT.
SYSOUT Output class for messages and reports.
SORTWK01
SORTWK02 Work files required by the SORT utility.
SORTWK03
SYSIN File-AID/RDX file that will contain the SORT cards generated by the LDDRV step.

ICETOOL Step DD Statements

This optional step uses the ICETOOL utility. The following DD statements are required for the
ICETOOL step:

Table 52. DD Statements—ICETOOL Step

DD Statement Description
STEPLIB Your site’s SORT library.
Load 533

Table 52. DD Statements—ICETOOL Step (Continued)

DD Statement Description
DFSPARM Supplies DFSORT program control statements and EXEC statement PARM options.
$ORTPARM Supplies SYNCSORT program control statements and EXEC statement PARM options.
SYSOUT Output class for messages and reports.
TOOLMSG Messages from the ICETOOL utility.
DFSMSG Messages from the individual sorts.
CnnnCNTL File that will contain the SORT cards generated by the LDDRV step. Associated with each SnnnIN
DD.
SnnnIN SPLIT file from the LDDRV step. A unique DD generated for each split file to sort.
SnnnOUT Output from the SORT. A unique DD generated for each sort output file.
SORTWK01
SORTWK02 Work files required by the SORT utility.
SORTWK03
TOOLIN File that associates each CnnnCNTL, SnnnIN, and SnnnOUT DD for ICETOOL to sort.

LDSQLIN Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 53:

Table 53. EXEC Statement PARM Field—DELTEnnn Step

Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option 5 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the LDSQLIN step:

Table 54. DD Statements—LDSQLIN Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
SYSIN File-AID/RDX’s Load Control Table. Used to verify authorities and identify tables that need to be
created. See Db2 Load Control Table for more information.
LOADIN Input file(s) generated during sort or split processing.
SYSOUT Output class for error messages and reports.
RDERRORS Output class for detailed SQL error information from Db2 and column mapping error
information from File-AID/RDX .
XCPTNRPT Output class for Insert Exception Report.
TOTLSRPT Output class for Load Summary Report.
COMMTRPT Output class for Commit Report.
DISCARDS File-AID/RDX discard file.
534 File-AID/RDX Reference

Table 54. DD Statements—LDSQLIN Step (Continued)

DD Statement Description
SYSPRINT Standard output stream.
TPTPRINT Standard output stream for optional diagnostics.
SYSTERM Output class for runtime errors.

SQL Insert Return Codes

An execution return code (RC) appears in the output listing.For return codes other than 0, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return
Description
Code
0 Job ran to completion without error.
4 Job ran to completion without error, warnings issued.
8 Job ran with error. Subsequent job steps stopped.
16 Severe error, job aborted.

MVS Load Job Steps

This section describes the steps in the load job when you include MVS objects in the load process.

1. VSAMALOC—Pre-allocate VSAM files for JES3 (IDCAMS)

2. VSAMCRTE—Delete and/or Define VSAM Files (IDCAMS)

This step creates any new VSAM clusters that did not exist at the time of the interactive portion
of the Load function.

This step also deletes the existing VSAM clusters if the Delete/Define load option was set to YES.

3. FILEDLTE—Delete Non VSAM files (IDCAMS)

This step deletes the existing non-VSAM files if the Delete/Define load option was set to YES.

4. FILEALLC—Allocates the Non-VSAM files that did not exist during the interactive load process or
that have been deleted when the Delete/Define option was set to YES. (IDCAMS)
5. CLEAN1ST—File Cleanup (IDCAMS)

This step deletes any existing files that are to be created in this job. This enables you to keep and
rerun a JCL stream.

6. LDDRV—Load Driver (XFREXEC)

This step checks user authorization for subsequent steps and separates the extract file into
multiple files, one file per object to be loaded.

7. SORTnnn—File Sort Utility (SORT) or ICETOOL Multiple File Sort

This step sorts a file containing the data to be loaded in the associated LDMVSIN step.
The sort sequence is based on the clustering index for that object. If no clustering index exists,
sort sequence is based on the primary index for that object. If no primary index exists, sort
sequence is based on the first-defined index for that object.

This step is generated and executed for each object to be loaded (SORT), or once for all files to be
loaded (ICETOOL).

8. LDMVSIN—MVS Insert (XFREXEC)

Load 535

This step generates and executes the DELETE and INSERT statements to load data into objects
from the sorted files created in step 4. If you specified YES in the Del All column for an object, all
data in that file will be deleted before the extracted data will be inserted.

If you specified Yes in the Replace Matches field on the Insert/Load Option screen and the target
object contains a unique key, File-AID/RDX will replace existing data in the target object with
data from the extract file. If you specified No in the Replace Matches field and the target object
contains a unique key, File-AID/RDX will discard data that already exists in the target object.

9. CLEANLST—File Cleanup (IDCAMS)

This step deletes all File-AID/RDX temporary files used in this job. Deleting these files in the last
job step enables the job to be restarted in any prior step.

10. CLEANCTL—File Cleanup (IEFBR14) - Optional

This step deletes the File-AID/RDX control card PDSEs. Whether step CLEANCTL is commented
out or executed is determined by the global job option Delete in-stream data datasets at EOJ (page
83). If the job option is set to NO, File-AID/RDX control card PDSEs created in the load and delete
jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows for the
restarting of the JCL at any step.

11. CLEANEXT—File Cleanup (IDCAMS) - Optional

This step deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is
commented out or executed is determined by the global job option Delete in-stream data datasets
at EOJ (page 83). If the job option is set to NO, File-AID/RDX EXTPARMS files created in the load
and delete jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows
for the restarting of the JCL at any step.

MVS Load JCL

The following pages contain the load JCL that is generated when the load process contains only MVS
files to be loaded. When Db2 and MVS objects are included, the JCL will also include the JCL for
either Db2 load or SQL insert option as described earlier. You can code and submit the JCL on the
following pages to execute the load process without invoking the interactive phase of the Load
function. The required parameter information and DD statements for File-AID/RDX-specific steps are
described following the JCL.
536 File-AID/RDX Reference

Figure 293. MVS Load JCL (continues on next page)

//* XFRJLOAD
//* -------------------------------------------------------------------- 
//* VSAMALOC - PRE-ALLOC VSAM FILES FOR JES3 
//* 
//* COPYRIGHT (C) 1994-2010 BY COMPUWARE CORPORATION, 
//* ALL RIGHTS RESERVED. 
//* -------------------------------------------------------------------- 
//* 
//VSAMALOC EXEC PGM=IDCAMS,COND=(4,LT) 
//DDnnn DD DSN=TSOID01.FRSAMP.PARTTABL, 
// DISP=(MOD,CATLG,KEEP), 
// UNIT=SYSDA, 
// SPACE=(TRK,(0)) 
//* --------------------------------------------------------------------
//* VSAMCRTE - DELETES AND / OR DEFINES VSAM FILES
//* --------------------------------------------------------------------
//VSAMCRTE EXEC PGM=IDCAMS,COND=(4,LT)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
//SYSIN DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(VSAMCRTE),
// DISP=SHR 
/*
//* --------------------------------------------------------------------
//* FILEALLC - ALLOCATES NON VSAM FILES
//* --------------------------------------------------------------------
//*
//FILEALLC EXEC PGM=IDCAMS,COND=(4,LT)
//*
//DDnnn DD DSN=TSOID02.C086.TEST.OBJC.SEQ,
// DCB=(RECFM=FB,LRECL=16,BLKSIZE=27984,DSORG=PS),
// SPACE=(TRK,(1,5),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,CATLG)
//* XFRJSTRT
//*-------------------------------------------------------------------
//* CLEAN1ST: - THIS STEP WILL ENSURE THAT ALL TEMPORARY FILES
//* USED IN THIS JOB ARE DELETED.
//* - THIS ALLOWS FOR KEEPING AND RERUNNING THE JOB EVEN IF
//* SUBSEQUENT STEPS FAIL.
//* - THIS JCL IS ALSO RESTARTABLE AT ANY STEP BY CODING
//* RESTART=XXXXXXXX ON THE JOBCARD. (XXXXXXXX = STEPNAME)
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-split-file
DELETE File-AID-sort-control-file
DELETE File-AID-MVS-info-file
SET MAXCC=0
SET LASTCC=0
/*
Load 537

Figure 294. MVS Load JCL (continues on the next page)

//* --------------------------------------------------------------------
//* LDDRV:- LOAD DRIVER
//* THE FOLLOWING IS PERFORMED IN THIS STEP.
//* - CHECK USERS DB2 AUTHORITY TO RUN ALL THE STEPS.
//* - ENSURE TABLES EXIST.
//* - SPLIT EXTRACT FILE INTO SEPARATE LOAD FILES.
//* --------------------------------------------------------------------
//LDDRV EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT),
// PARM=(FR,3,B)
//*
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTRACT DD DSN=extract-file,
// DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//*
//MVSINFO DD DSN=TSOID01.prefix.MVSIN.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920,DSORG=PS),
// SPACE=(TRK,(1,9),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//DDnnn DD DSN=TSOID02.C086.TEST.OBJC.SEQ,
// DISP=SHR
//*
//DISCARDS DD DSN=TSOID02.DISCARD.C86,
// DCB=(RECFM=VB,LRECL=309,BLKSIZE=27998,DSORG=PS),
// SPACE=(27998,(2,20),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//* XFRJSTR1
//SPLITnnn DD DSN=TSOID01.prefix.SPLITnnn.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=VB,LRECL=309,BLKSIZE=27998,DSORG=PS),
// SPACE=(27998,(1,9),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//SRTCDnnn DD DSN=TSOID01.prefix.SRTCDnnn.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=80,DSORG=PS,BUFNO=1),
// SPACE=(TRK,(1,9),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//SYSOUT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//MVSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(MVSLCT),
// DISP=SHR 
//* XFRJSORT
//*---------------------------------------------------------------------
//* SORTnnn:
//* - SORT INPUT FILE FOR TSOID02.C086.TEST.OBJD.KSDS
//*---------------------------------------------------------------------
//SORTnnn EXEC PGM=SORT,COND=(4,LT)
//*
//STEPLIB DD DSN=SYS1.SORTLIB,
// DISP=SHR
//SYSOUT DD SYSOUT=(*)

//DFSPARM DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(DFSPARM), 
// DISP=SHR 
//$ORTPARM DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix($ORTPARM), 
// DISP=SHR 
//SORTIN DD DSN=TSOID01.prefix.SPLIT003.Dnnnnnn.Tnnnnnn.suffix,
// DISP=(OLD,KEEP,KEEP)
//SORTOUT DD DSN=TSOID01.prefix.SORT003.Dnnnnnn.Tnnnnnn.suffix,
// DCB=(RECFM=VB,LRECL=309,BLKSIZE=27998,DSORG=PS),
// SPACE=(27998,(1,9),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
538 File-AID/RDX Reference

Figure 295. MVS Load JCL

//SORTWK01 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SORTWK02 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SORTWK03 DD UNIT=SYSDA,
// SPACE=(19069,(00003),,,ROUND),
// DISP=(NEW,DELETE,DELETE)
//SYSIN DD DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix(SRTCDnnn),
// DISP=(OLD,KEEP,KEEP)
//* XFRJMVSI
//*-------------------------------------------------------------------
//* LOAD MVS FILES
//*-------------------------------------------------------------------
//LDMVSIN EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT),
// PARM=(FR,C,B)
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//MVSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(MVSLCT),
// DISP=(OLD,KEEP,KEEP)
//LOADIN DD DSN=TSOID01.prefix.SPLITnnn.Dnnnnnn.Tnnnnnn.suffix,
// DISP=(OLD,KEEP,KEEP)
//DDnnn DD DSN=TSOID02.C086.TEST.OBJC.SEQ,
// DISP=(MOD,KEEP,KEEP)
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//XCPTNRPT DD SYSOUT=(*)
//TOTLSRPT DD SYSOUT=(*)
//COMMTRPT DD SYSOUT=(*)
//RDERRORS DD SYSOUT=(*)
//SYSOUT DD SYSOUT=(*)
//DISCARDS DD DSN=TSOID02.DISCARD.C86,
// DISP=MOD
//SYSPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//* XFRJLDND
//*-------------------------------------------------------------------
//* CLEANLST: - THIS STEP WILL PERFORM A DELETE OF ALL TEMPORARY
//* FILES USED IN THIS JOB.
//* - KEEPING THE FILES UNTIL ALL STEPS RUN SUCCESSFULLY
//* ALLOWS FOR THE RESTARTING OF THE JCL AT ANY STEP.
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-split-file
DELETE File-AID-sort-control-file
DELETE File-AID-MVS-info-file
SET MAXCC=0
SET LASTCC=0
/*
//* 
//*-------------------------------------------------------------------
//* CLEANCTL: - THIS STEP WILL PERFORM A DELETE OF THE TWO CNTL 
//* DATASETS USED BY THIS JOB FOR THE SYSIN DATA. 
//* - THE DATASETS ARE ONLY DELETED IF ALL THE PREVIOUS 
//* STEPS RUN SUCCESSFULLY; THIS ALLOWS FOR RESTARTING 
//* OF THE JOB AT ANY STEP. 
//*------------------------------------------------------------------- 
//* NOTE! - THIS STEP IS CONDITIONED ON AN OPTION ON THE GLOBAL 
//* OPTIONS SCREEN 
/*-------------------------------------------------------------------
//CLEANCTL EXEC PGM=IEFBR14,COND=(4,LT) 
//DFBPDSE DD DSN=DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//DVBPDSE DD DSN=DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//CLEANEXT EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 XFRJCLXT 
//SYSPRINT DD SYSOUT=*
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE extract-parms-file,
SET MAXCC=0
SET LASTCC=0
/* 
//* /*XFRJCLXT*/
Load 539

VSAMALOC
Pre-allocates VSAM files for JES3 (IDCAMS)

VSAMCRTE Step DD Statements

The following DD statements are required for the VSAMCRTE step:

Table 55. DD Statements—VSAMCRTE Step

DD Statement Description
SYSPRINT Standard output stream.
SYSIN File-AID/RDX’s Create control cards (member VSAMCRTE in the control card PDSE). Used to
verify authorities and identify objects that need to be created.

Figure 296. Sample VSAMCRTE control card (Member VSAMCRTE)

DELETE - 
TSOID02.C086.TEST.OBJD.KSDS
DEFINE CLUSTER -
(NAME(TSOID02.C086.TEST.OBJD.KSDS) -
BUFFERSPACE(37376) -
INDEXED -
KEYS(25 15) -
MANAGEMENTCLASS(@NONSTD@) -
OWNER(TSOID02) -
RECORDSIZE(50 150) -
SHAREOPTIONS(3 3) -
SPEED -
STORAGECLASS(STDNOCSH)) -
DATA(NAME(TSOID02.C086.TEST.OBJD.KSDS.DATA) -
TRACKS(15 5) -
CONTROLINTERVALSIZE(4096)) -
INDEX(NAME(TSOID02.C086.TEST.OBJD.KSDS.INDEX)
CONTROLINTERVALSIZE(1024))

FILEDLTE Step DD Statements

The following DD statements are required for the FILEDLTE step:

Table 56. DD Statements—FILEDLTE Step

DD Statement Description
SYSPRINT Standard output stream.
SYSIN File-AID/RDX’s Load Control Table. Used to verify authorities and identify objects that need to
be created.

FILEALLC Step DD Statements

The following DD statements are required for the FILEALLC step:

Table 57. DD Statements—FILEALLC Step

DD Statement Description
SYSPRINT Standard output stream.
SYSIN File-AID/RDX’s Load Control Table (member MVSLCT in the SYSIN control card PDSE). Used to
verify authorities and identify objects that need to be created. See also MVS Load Control Table.

LDDRV Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.
540 File-AID/RDX Reference

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 58:

Table 58. EXEC Statement PARM Field——LDDRV Step

Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option 3 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the LDDRV step:

Table 59. DD Statements—LDDRV Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTRACT File-AID/RDX extract file name.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
MVSINFO File-AID/RDX information for MVS files to be loaded.
DISCARDS File-AID/RDX discard file.
SPLITnnn Output file to which File-AID/RDX writes data for a single table from the extract file.

• One file for each object, where 001≤ nnn ≤ 099.

• The LRECL and BLKSIZE parameters must be large enough to hold the extracted records.

• The SPACE parameters must be large enough to hold all extracted records.
SRTCDnnn Control card used by File-AID/RDX to sort each split file before the data is loaded into an object.
• One member (SRTCDnnn) for each table in the control card PDSE.
• RECFM must be F or FB. LRECL must be 80.
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed error information.
SYSPRINT Standard output stream.
SYSTERM Output class for runtime errors.
TPTPRINT Standard output stream for optional diagnostics.
MVSIN File-AID/RDX’s Load Control Table (member MVSLCT in the MVSIN control card PDSE). Used to
verify authorities and identify objects that need to be created. See also MVS Load Control Table.

MVS Load Control Table

The MVS Load Control Table (member MVSLCT in the MVSIN control card PDSE) contains
information about the source and target objects. It is the input (MVSIN) for the LDDRV step.
Load 541

Figure 297. MVS Load Control Table (MVSLCT)

*FR.17.02.00 ---------- M V S L O A D C O N T R O L T A B L E ------------

*
*
* DATASET NAME DEL REP ROW COUNT I/O EXIT S
*- ---------------------------------------------- --- --- --------- -------- -
S: FARDX20.V2R1M0.TEST.OBJC.SEQ
T: TSOID02.C086.TEST.OBJC.SEQ N Y 5 N
*
* TABLE CONTROL NUMBER
C: 001
*
*============= TARGET =============== ============= SOURCE ===========
*COL DEF TYP OFFST LGTH P / S COL TYP OFFST LGTH P / S
*---- --- --- ----- ----- ----------- ---- --- ----- ----- -----------
*
* DATASET NAME DEL REP ROW COUNT I/O EXIT S
*- ---------------------------------------------- --- --- --------- -------- -

* TABLE CONTROL NUMBER
C: 002
*
*============= TARGET =============== ============= SOURCE ===========
*COL DEF TYP OFFST LGTH P / S COL TYP OFFST LGTH P / S
*---- --- --- ----- ----- ----------- ---- --- ----- ----- -----------
*
* DATASET NAME DEL REP ROW COUNT I/O EXIT S
*- ---------------------------------------------- --- --- --------- -------- -
S: FARDX20.V2R1M0.TEST.OBJD.KSDS
T: TSOID02.C086.TEST.OBJD.KSDS N Y 5 N
*
* TABLE CONTROL NUMBER
C: 003
*
*============= TARGET =============== ============= SOURCE ===========
*COL DEF TYP OFFST LGTH P / S COL TYP OFFST LGTH P / S
*---- --- --- ----- ----- ----------- ---- --- ----- ----- -----------
*
* DATASET NAME DEL REP ROW COUNT I/O EXIT S
*- ---------------------------------------------- --- --- --------- -------- -
S: FARDX20.V2R1M0.TEST.OBJA.SEQ
T: TSOID02.C086.TEST.OBJA.SEQ N Y 5 N
*
* TABLE CONTROL NUMBER
C: 004
*
*============= TARGET =============== ============= SOURCE ===========
*COL DEF TYP OFFST LGTH P / S COL TYP OFFST LGTH P / S
*---- --- --- ----- ----- ----------- ---- --- ----- ----- -----------
/*

Each source/target pair is identified by its object control number and for each, there are two tables.
The first table contains the following information:

Table 60. Load Control Table—Source and Target Object Information

Field Name Description
blank Indicates whether the file described by this line was extracted from or is to be loaded.
S The source file; the object extracted from.
T The target file; the object to be loaded.
Dataset name The name of the file described by this line.
542 File-AID/RDX Reference

Table 60. Load Control Table—Source and Target Object Information (Continued)
Field Name Description
DEL For T: files only. Indicates whether or not records should be deleted before the load is executed.
Y Delete records before loading.
N Do not delete records before loading.
Rep For T: files only. Indicates whether or not File-AID/RDX should attempt to replace (update) existing
records from the target file with records from the source file.
Y Yes
N No
Row Count For T: files only. Identifies the number of records to be loaded into the target file.
I/O Exit For T: files only. Identifies the use of I/O exit routines to load data into the target file.
S For T: files only. N or Y. Represents the D record supplement indicator (see also Product Record — 0 on
page 378).

The second table contains the following column information:

Table 61. Load Control Table—Field Mapping Information

Field Name Description
COL (Target) Contains a list of the target field numbers. This information is taken from the extract file and the Field
Mapping screen. If you mapped any target fields to source fields with different numbers, those
mappings are reflected here.
DEF Indicates whether the target column will contain the default value, a literal default value, or nulls.
Y Yes — The field will contain the default value defined for it.
N No — The field will contain the value of the source field.
Literal — The column will contain the value of the literal definition (Lnn) assigned to it
L
during field mapping.
TYP Indicates the data type of the target fields. This information is taken from the extract file and the Field
Mapping screen.
OFFST Indicates the offset for the target data.
LGTH Indicates the length of the target fields. This information is taken from the extract file and the Field
Mapping screen.
P /S Indicates the precision and scale for the target data in the extract file.
COL (Source) Contains a list of the source field numbers. This information is taken from the extract file.
TYP Indicates the data type of the source fields. This information is taken from the extract file and the Field
Mapping screen.
OFFST Indicates the offset for the source data in the extract file.
LGTH Indicates the length of the source fields. This information is taken from the extract file and the Field
Mapping screen.
P /S Indicates the precision and scale for the source data in the extract file.

LDMVSIN Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.
Load 543

The parameter information in the PARM field in the EXEC statement must have the format as shown
in Table 62:

Table 62. EXEC Statement PARM Field——LDDRV Step

Parameter Default Length Description
Value
Product FR 2 File-AID/RDX
Option C 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the LDMVSIN step:

Table 63. DD Statements—LDMVSIN Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
MVSIN File-AID/RDX’s MVS Load Control Table. Used to verify authorities and identify
objects that need to be created.
LOADIN Input file(s) generated during sort or split processing.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
SYSOUT Output class for error messages and reports.
RDERRORS Output class for detailed error information and field mapping error information
from File-AID/RDX.
XCPTNRPT Output class for Insert Exception Report.
TOTLSRPT Output class for Load Summary Report.
COMMTRPT Output class for Commit Report.
DISCARDS File-AID/RDX discard file.
SYSPRINT Standard output stream.
TPTPRINT Standard output stream for optional diagnostics.
SYSTERM Output class for runtime errors.

SORTnnn Step DD Statements

This step uses your site’s SORT utility. The following DD statements are required for the SORT step:

Table 64. DD Statements—SORT Step

DD Statement Description
STEPLIB Your site’s SORT library.
SORTIN SPLIT file from the LDDRV step.
SORTOUT Output from the SORT.
SYSOUT Output class for messages and reports.
SRTCD001
SRTCD002 Work files required by the SORT utility.
SRTCD003
SYSIN File that will contain the SORT cards generated by the LDDRV step.
544 File-AID/RDX Reference

ICETOOL Step DD Statements

This optional step uses the ICETOOL utility. The following DD statements are required for the
ICETOOL step:

Table 65. DD Statements—ICETOOL Step

DD Statement Description
STEPLIB Your site’s SORT library.
DFSPARM Supplies DFSORT program control statements and EXEC statement PARM options.
$ORTPARM Supplies SYNCSORT program control statements and EXEC statement PARM
options.
SYSOUT Output class for messages and reports.
TOOLMSG Messages from the ICETOOL utility.
DFSMSG Messages from the individual sorts.
CnnnCNTL File that will contain the SORT cards generated by the LDDRV step. Associated
with each SnnnIN DD.
SnnnIN SPLIT file from the LDDRV step. A unique DD generated for each split file to sort.
SnnnOUT Output from the SORT. A unique DD generated for each sort output file.
SORTWK01
SORTWK02 Work files required by the SORT utility.
SORTWK03
TOOLIN File that associates each CnnnCNTL, SnnnIN, and SnnnOUT DD for ICETOOL to
sort.

MVS Insert Return Codes

An execution return code (RC) appears in the output listing. For return codes other than 0, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return
Description
Code
0 Job ran to completion without error.
4 Job ran to completion without error, warnings issued.
8 Job ran with error. Subsequent job steps stopped.
16 Severe error, job aborted.

Miscellaneous Load Topics

This section contains information about the following topics:

• Tablespaces
• Restartability
• Reusing the Discard File
• Use of Views in Load
• Db2 Privileges
• Load Reports

Tablespaces
Tablespaces are affected during the File-AID/RDX Db2 load processing by the following:

• the Target Environment screen;

• whether a tablespace contains one or several tables (Db2 Load Utility only); and
Load 545

• whether a tablespace may or may not have been placed in CHECK PENDING or COPY PENDING
status by the Db2 Load Utility or the Delete step.

Target Environment Screen

If you specify a tablespace in the Target Environment screen, the tablespace must exist in the
specified database or the extract file must contain the DDL for the tablespace. File-AID/RDX generates
DDL to create the table in this tablespace.

If you leave the Tablespace field on the Target Environment screen blank, File-AID/RDX generates
DDL to create the tablespace implicitly. Implicit tablespace is not valid for multi-table or partitioned
tablespaces. The current SQLID must have the proper Db2 authority to create the tablespace in the
execution phase.

Single-Table and Multi-Table Tablespaces

When you select the Db2 Load Utility, File-AID/RDX processes tablespaces with a single table and
those with multiple tables differently.

Single-Table Tablespaces
When rows are to be deleted before loading a table in a tablespace with only one table, the LOAD
utility with the REPLACE parameter is used. Such a tablespace, therefore, does not require a separate
DELETE step or a RPAIRnnn step to reset the CHECK PENDING status.

Multi-Table Tablespaces
When rows are to be deleted before loading a table in a tablespace with more than one table, File-
AID/RDX generates a separate DELETE step. This DELETE step deletes rows only from the table you
specified for load.It does not affect other tables in the tablespace.

Some tablespaces may have been placed in CHECK PENDING status by the load or delete step.
Because tablespaces might be used in subsequent steps and cannot be in CHECK PENDING status, the
RPAIRnnn step generated by File-AID/RDX resets the CHECK PENDING status.

CHECK PENDING Status

The Load job ensures that all tablespaces that have had the CHECK PENDING status set are included
in the CHCKDATA step.

The CHECK utility step is generated as a step in the load JCL only if File-AID/RDX determines that
one or more tablespaces to be loaded might be given the CHECK PENDING restriction. The CHECK
utility control cards are generated in the LDDRV step of the load process. The SCOPE ALL parameter
is also used in this step.

COPY PENDING Status

The Load job ensures that all tablespaces with COPY PENDING status are included in the IMAGECPY
step.

It is possible for a table to be left in a COPY PENDING status if LOG OPTION 2 was used in the LOAD
utility. A Db2 Copy utility step is generated in the load JCL if you specified 2 in the Log Option field
on the Db2 Load Utility Load Options screen. The Copy utility control cards are generated in the
LDDRV step of the load process.

Restartability
File-AID/RDX enables you to restart a failed load job from any particular step except LOADDRV. If a
load job fails during the LOADDRV step, you must restart the load job from the CLEAN1ST step.

The procedure to restart the load job depends on whether you selected the Db2 Load Utility or SQL
Insert load option.
546 File-AID/RDX Reference

Db2 Load Utility

The JCL generated for the Db2 Load Utility load job is step-restartable. To restart a Db2 Load Utility
load job at a particular step:

1. Code the RESTART keyword parameter on the job card as follows:

RESTART=xxxxxxxx

where xxxxxxxx is the name of the step at which you want to restart the job.

2. Submit the JCL.

SQL Insert
The JCL generated for the SQL Insert load job is step-restartable. To restart an SQL Insert load job:

1. Code the RESTART keyword parameter on the job card as follows:

RESTART=xxxxxxxx

where xxxxxxxx is the name of the step at which you want to restart the job.

If the job failed before the LDSQLIN step skip to Step 5.

If the job failed during the LDSQLIN step, you must restart the job at the LDSQLIN step and then
continue with Step 2.

2. Examine the Commit Report. Find the last report entry value in the Restart Point column of the
Commit Report. This value has the following format:

'RESTART=yyyyyyyy/zzzzzzzz'

where yyyyyyyy is the number of rows committed and zzzzzzzz is the number of rows discarded.
File-AID/RDX uses these values to determine where processing should restart.

3. Edit the DD EXTPARMS dataset and modify the line containing RESTART
RESTART=00000000/00000000 with the values from step 2.
4. Determine whether or not the load job stopped because the maximum rows to discard limit was
reached. To do this, examine the load job output for File-AID/RDX error E336 or E187. These
errors indicate that the limit set by Max Rows to Discard parameter was reached. In this case,
increase the Max Rows to Discard parameter for the LDSQLIN step. Max Rows to Discard is the
fourteenth parameter in the LDSQLIN EXEC statement PARM field (directly preceding the Restart
Point Indicator).
5. Submit the JCL.

Reusing the Discard File

File-AID/RDX enables you to reuse the discard file as input to the load process when the load job was
completed normally, but rows were discarded.

Discarded records are written to the discard file when you specify YES in the Save Discarded Rows
field on the SQL Insert Processing Options screen. The discard file is modeled after the extract file
with similar attributes and contents, such as header, create, map, and data records. The discard data
records are those that have been discarded because of RI constraints, duplicate rows, etc.
Load 547

To reuse the discard file as input for the interactive phase of the Load function, you must step
through the interactive phase specifying the name of the discard file in the File Name field on the
Load Specifications screen.

If you reuse the discard file as input for the interactive phase, be sure to
specify a new discard file during the interactive phase.

Use of Views in Load

File-AID/RDX supports the use of views in the Load function. Support of views varies depending on
the load option selected (SQL Insert statements or Db2 Load utility).

Db2 load method SQL Insert:

• If you extracted from views:

– File-AID/RDX displays view names as target objects on the Column Mapping and Target
Environment screens
– File-AID/RDX creates the views as tables, if the views don't exist in the Target Environment
– The target view must be a single table view

• If you extracted from tables:

– You can type over target names with the name of an existing view
– The target view must be a single table view

If you are loading data to an existing table or view, any target columns that are not mapped to source
columns will be filled with default values.

Db2 load method Db2 Load:

• If you extracted from views:

– File-AID/RDX displays view names as target objects on the Column Mapping and Target
Environment screens
– File-AID/RDX creates the views as tables, if the views don't exist in the Target Environment
– The target view must be a single table view
– If the target views do exist in the Target Environment, you must change the load method to
SQL; File-AID/RDX will not allow loading into views with the Db2 load utility

Db2 Privileges
During the interactive portion of the load process, you specify the Db2 objects that are involved in
the load process.File-AID/RDX generates the JCL regardless of the user’s Db2 privileges. This enables a
user with limited Db2 privileges to generate the load JCL, while a user with more Db2 privileges, such
as a DBA, can submit the load JCL.

If you are unauthorized to use Db2 utilities, Compuware suggests using SQL Insert processing.

When generating the JCL, File-AID/RDX inserts comments regarding Db2 privileges at the beginning
of the JCL. These comments indicate that the current SQLID either has authorization for all load
steps, or lacks specific Db2 authority (see the example in Figure 298 on page 548).
548 File-AID/RDX Reference

Figure 298. Example of SQLID Authorization Error Comments in Load JCL

//*SQLID TSOID01 IS UNAUTHORIZED TO:

//* CREATE TABLE FR.PART_TABLE_1
//* ALTER DEPENDENTS OF TABLE FR.PART_TABLE_1
//* DELETE ROWS FROM TABLE FR.PART_TABLE_1
//* LOAD TO TABLE FR.PART_TABLE_1
//* RUN CHECK DATA ON TABLESPACE FRD23H.PARTRTAB
//* RUN CHECK DATA ON DEPENDENTS OF FR.PART_TABLE_1
//* ALTER TABLE FR.PART_TABLE_1

The execution phase of the load function, which actually executes the File-AID/RDX load JCL,
requires the user to have all relevant Db2 privileges. See The Load Process on page 507 for more
details regarding each step in the JCL.

Privileges Required for Load Steps

The privileges required for load steps varies depending on whether you use the Db2 LOAD utility or
SQL INSERT statements.

Privileges Required to Use the Db2 LOAD Utility

When you use the Db2 LOAD utility, the user who submits the batch JCL or the authorization ID of
the owner of the File-AID/RDX plan must have one of the privileges listed for each of the following
steps.

CREATE step

If creating new tables, one of the following privileges is required:

• SYSADM or SYSCTRL.
• DBADM, DBCTRL, DBMAINT for the database where the tables are to be created.
• CREATETAB privilege for the database where tables are to be created.
• USE OF an existing tablespace where tables are to be created.
• CREATETS privilege for the database where tables are to be created when implicitly creating a
tablespace. This indicates authority to use the database default STOGROUP and bufferpool.

LDDRV step

There are no Db2 privileges required for this step.

DELTE step

This step executes DELETE and ALTER statements. To execute this step one of the following privileges
is required:

• SYSADM.
• DBADM for the database where tables to be loaded exist.
• ALTER and DELETE privileges for the table to be deleted.
• If a table has dependents, ALTER privilege on the table to be deleted and on the dependents of
the table to be deleted.
• Ownership of the table and of dependent tables.

LOAD step

To execute the Db2 LOAD utility requires one of the following privileges:

• SYSCTRL or SYSADM.
• DBADM, DBCTRL or LOAD privilege for the database where tables are to be loaded.
• Ownership of the table.
Load 549

RPAIR step

To execute the Db2 REPAIR utility requires one of the following privileges:

• SYSCTRL or SYSADM.
• DBADM or DBCTRL privilege for the database.
• REPAIR privilege for the database.

CHCKDATA step

To execute the Db2 CHECK utility requires one of the following privileges:

• SYSCTRL, SYSADM, or SYSOPR.

• DBADM, DBCTRL, DBMAINT, or STATS privilege for the database where tablespaces to be checked
exist.

IMAGECPY step

To execute the Db2 COPY utility requires one of the following privileges:

• SYSCTRL or SYSADM.
• DBADM, DBCTRL, or DBMAINT privilege for the database.
• IMAGECPY privilege for the database.

Privileges Required to Use SQL INSERT Statements

When you use SQL INSERT statements, the user who submits the batch JCL or the authorization ID of
the owner of the File-AID/RDX plan must have one of the privileges listed for each of the following
steps.

CREATE step

If creating new tables, one of the following privileges is required:

• SYSADM or SYSCTRL.
• DBADM, DBCTRL, DBMAINT for the database where the tables are to be created.
• CREATETAB privilege for the database where tables are to be created.
• USE OF an existing tablespace where tables are to be created.
• CREATETS privilege for the database where tables are to be created when implicitly creating a
tablespace. This indicates authority to use the database default STOGROUP and bufferpool.

LDDRV step

There are no Db2 privileges required for this step.

DELETE step

To execute this step for a table requires one of the following privileges:

• DELETE privilege on the table to be deleted.

• Ownership of the table to be deleted.
• DBADM authority on the database containing the table to be deleted.
• SYSADM authority.

To execute this step for a view requires one of the following privileges:

• DELETE privilege on the view to be deleted.

• SYSADM authority.

LDSQLIN step

To execute SQL INSERT statements for a table requires one of the following privileges:
550 File-AID/RDX Reference

• INSERT privilege on the table to be inserted.

• Ownership of the table to be inserted.
• DBADM authority on the database containing the table to be inserted.
• SYSADM authority.

To execute SQL UPDATE statements for a table requires one of the following privileges:

• UPDATE privilege on the table to be updated.

• Ownership of the table to be updated.
• DBADM authority on the database containing the table to be updated.
• SYSADM authority.

To execute SQL INSERT statements for a view requires one of the following privileges:

• INSERT privilege on the view to be inserted.

• SYSADM authority.

To execute SQL UPDATE statements for a view requires one of the following privileges:

• UPDATE privilege on the view to be updated.

• SYSADM authority.

Load Reports
File-AID/RDX generates the reports described below during the load process:

SQL Insert - DB2 Authority Report

Contains information about the Db2 authority of the SQLID to be used for the load.

DB2 Load - DB2 Authority Report

Contains information about the Db2 authority of the SQLID to be used for the load.

Create DB2 Target Environment Report

Contains information about the Db2 tables to be created during the execution phase of the Load
function.

Pre-Load Summary Report

Contains a summary of the tables and rows to be loaded. This report is generated when you use
the Db2 Load Utility option.

SQL Insert: DB2 Totals Report

Contains information about rows inserted, updated, and discarded. This report is generated when
you use the SQL INSERT option.

MVS Load - MVS Totals Report

Contains information about records inserted, updated, and discarded. This report is generated
when you load MVS files.
Load 551

SQL Insert: DB2 Committed Rows Report

Contains information about how many times Db2 COMMITS were issued and how many rows
were affected. This report is generated when you use the SQL INSERT option.

SQL Insert - DB2 Delete Report

Contains information about rows deleted during load. This report is generated when you use the
SQL INSERT option.

DB2 Load - DB2 Delete Report

Contains information about rows deleted during load. This report is generated when you use the
Db2 Load option.

SQL Insert: DB2 Discard Report

Contains information about rows that were not inserted or updated during load. This report is
generated when you use the SQL INSERT option.

MVS Load: VSAM Discard Report

Contains information about records that were not inserted or updated during load. This report is
generated when your load includes VSAM objects.

SQL Insert - DB2 Authority Report

The SQL Insert - DB2 Authority Report shown in Figure 299 contains information about the authority
of a given SQLID.

Figure 299. SQL Insert - DB2 Authority Report

File-AID/RDX 17.2 SQL Insert - DB2 Authority Report PAGE 1

DATE 2005-08-15
Extract File. . : TSOID01.R42.EXTRACT(Member) TIME 12.01.53

SQLID. . . . . .: TSOID01

Objects With Errors 
------------------------------------------------------------------------------------------------------------------------------------
Error: E273 The SQLID does not have authority to execute SQL Insert
Target: D-FADB2.ORDER_1

Error: E273 The SQLID does not have authority to execute SQL Insert
Target: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6 ____+____7____+____8____+____9_____+___10___
_+___11____+___12____+___.TABLE____1____+____2__+____3____+___4____+____5____+____6____+____7____+____8____+____9____+___10_
___+___ 11____+___12____+___

* * END OF REPORT * * *

The header part of the report shows the following:

• The name of the extract file. If the extract file is a PDS, the member name is also displayed.
• The SQLID used for the load request.

The SQL Insert - DB2 Authority Report provides the following information:

Objects With Errors

Lists the errors and the name of the target object the error applies to.
552 File-AID/RDX Reference

Error
Lists the File-AID/RDX error message associated with the object in error.

Target
Lists the name of the target object the error applies to.

DB2 Load - DB2 Authority Report

The DB2 Load - DB2 Authority Report shown in Figure 300 contains information about the authority
of a given SQLID.

Figure 300. DB2 Load - DB2 Authority Report

File-AID/RDX 17.2 DB2 Load - DB2 Authority Report PAGE 1

DATE 2005-08-15
Extract File. . : TSOID01.R42.EXTRACT(Member) TIME 12.01.53

SQLID. . . . . .: TSOID01

Objects With Errors 
------------------------------------------------------------------------------------------------------------------------------------
Error: E273 The SQLID does not have authority to execute Load Utility
Target: D-FADB2.ORDER_1

Error: E273 The SQLID does not have authority to execute Load Utility
Target: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6 ____+____7____+____8____+____9_____+___10___
_+___11____+___12____+___.TABLE____1____+____2__+____3____+___4____+____5____+____6____+____7____+____8____+____9____+___10_
___+___ 11____+___12____+___

* * END OF REPORT * * *

The header part of the report shows the following:

• The name of the extract file. If the extract file is a PDS, the member name is also displayed.
• The SQLID used for the load request.

The DB2 Load - DB2 Authority Report provides the following information:

Objects With Errors

Lists the errors and the name of the target object the error applies to.

Error
Lists the File-AID/RDX error message associated with the object in error.

Target
Lists the name of the target object the error applies to.

Create DB2 Target Environment Report

The Create DB2 Target Environment Report shown in Figure 301 contains information about tables
created during the execution phase of the Load function.
Load 553

Figure 301. Create DB2 Target Environment Report

File-AID/RDX 17.2 Create DB2 Target Environment Report PAGE 1 

DATE 2005-08-15
Extract File. . : TSOID01.R42.EXTRACT(Member) TIME 12.01.53
SSID D810
Status Action Object Name 
---------- ----------------- ----------------------------------------------------------------------------------------------------
Successful CREATE DATABASE D-DSNLOCAT.PFHIAFDB

Successful CREATE TABLESPACE D-DSNLOCAT.PFHIAFTS

Successful CREATE TABLE D-DSNLOCAT.TSOID01.CONTACT_TABLE
Successful CREATE INDEX D-DSNLOCAT.TSOID01.CONTACT_IDX 

Successful CREATE TABLE D-DSNLOCAT.TSOID01.CUSTOMER_TABLE 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.CUSTOMER_IDX 

Successful CREATE TABLE D-DSNLOCAT.TSOID01.DEPT 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.XDEPT1 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.XDEPT2 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.XDEPT3 

Successful CREATE TABLE D-DSNLOCAT.TSOID01.EMP 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.XEMP1 
Failed CREATE INDEX D-DSNLOCAT.TSOID01.XEMP2 
Error: Eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee

Successful CREATE TABLE D-DSNLOCAT.TSOID01.EMPPROJACT 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.XEMPPROJACT1 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.XEMPPROJACT2 

Successful CREATE TABLE D-DSNLOCAT.TSOID01.PROJ 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.XPROJ1 
Successful CREATE INDEX D-DSNLOCAT.TSOID01.XPROJ2 

Successful CREATE TABLE D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8__
__+____9_____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5__
__+____6____+____7____+____8____+____9____+___10____+___11____+___12____+___ 
Successful CREATE INDEX D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8__
__+____9_____+___10____+___11____+___12____+___.INDEX____1____+____2____+____3____+___4____+____5__
__+____6____+____7____+____8____+____9____+___10____+___11____+___12____+___ 


Successful ALTER TABLE D-DSNLOCAT.TSOID01.CONTACT_TABLE 

Successful ALTER TABLE D-DSNLOCAT.TSOID01.DEPT 

Successful ALTER TABLE D-DSNLOCAT.TSOID01.DEPT 

Successful ALTER TABLE D-DSNLOCAT.TSOID01.EMPPROJACT 

Successful ALTER TABLE D-DSNLOCAT.TSOID01.EMPPROJACT 

Successful ALTER TABLE D-DSNLOCAT.TSOID01.PROJ 

* * * END OF REPORT * * *


The header part of the report shows the following:

• The name of the extract file. If the extract file is a PDS, the member name is also displayed.
• The Db2 subsystem ID.

The Create DB2 Target Environment Report lists all Db2 objects created for the load request with
status and action columns.

Status
A list of messages indicating the success or failure of the action. If status is failed, the error
message is listed in the following line.

Action
A list of Db2 operations taken for the Db2 object.

Object Name
A list of objects that were not created during the load.
554 File-AID/RDX Reference

Error
The File-AID/RDX error message associated with the object that was not created successfully.

Pre-Load Summary Report

The Pre-Load Summary Report shown in Figure 302 is a summary of the objects and records to be
loaded. This report is generated when you use the Db2 LOAD Utility option or load MVS objects. At
the end of the report, File-AID/RDX lists the total number of records loaded into n target objects as
well as how many objects had no records extracted.

Figure 302. Pre-Load Summary Report

File-AID/RDX 17.2 Pre-Load Summary Report PAGE 1

DATE 2005-08-15
Extract File. . : TSOID01.R42.EXTRACT(Member) TIME 12.01.53


Delete Replace Extracted 
ID All Data Matches Rows Source Object Extracted and Target Object to be Loaded 
---- -------- ------- ---------- ----------------------------------------------------------------------------------------------- 
D001 No - 43 Source: D-DSNLOCAT.TSOID01.EMP 
Target: D-DSNLOCAT.TSOID01.EMP 

D002 No - 3 Source: M-TSOID01.FASAMP.EMPMAST 
Target: M-TSOID01.FASAMP.EMPMAST.AC 

D003 No - 3 Source: M-TSOID01.FASAMP.EMPLOYEE 
Target: M-TSOID01.FASAMP.EMPLOYEE.AC 

D004 No - 0 Source: D-DSNLOCAT.TSOID01.PROJ 
Target: D-DSNLOCAT.TSOID01.PROJ

D005 No - 9 Source: D-DSNLOCAT.TSOID01.DEPT 
Target: D-DSNLOCAT.TSOID01.DEPT

D006 No - 0 Source: D-DSNLOCAT.TSOID01.ACT 
Target: D-DSNLOCAT.TSOID01.ACT 

D007 No - 0 Source: D-DSNLOCAT.TSOID01.PROJACT
Target: D-DSNLOCAT.TSOID01.PROJACT 

D008 No - 0 Source: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6 ____+__
__7____+____8____+____9_____+___10____+___11____+___12____+___.TABLE____1____+____2__
__+____3____+___4____+____5____+____6____+____7____+____8____+____9____+___10____+___
11____+___12____+___ 
Target: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6 ____+__
__7____+____8____+____9_____+___10____+___11____+___12____+___.TABLE____1____+____2__
__+____3____+___4____+____5____+____6____+____7____+____8____+____9____+___10____+___
11____+___12____+___ 

***** 58 TOTAL rows will be loaded to 4 objects ***** 

***** 8 Objects included in the Extract File, 4 objects had no rows extracted *****

* * * END OF REPORT * * *


The header part of the report shows the following:

• The name of the extract file. If the extract file is a PDS, the member name is also displayed.

The Pre-Load Summary Report consists of the following columns:

ID
The File-AID/RDX extract object identifier for the object to be loaded.

Delete ALL data

(Db2 only) Indicates whether or not File-AID/RDX deletes ALL of the data residing in the target
objects before it loads data from the extract file. For Db2 tables, Db2 delete rules are in effect.

Yes Delete all rows from the specified object before loading data.
Load 555

New Indicates that objects are to be created; they do not exist and, therefore, do not contain
data to be deleted.
No Indicates that the data is to be loaded into objects without deleting all existing rows.

Delete/Define
(MVS files only) Indicates whether or not File-AID/RDX deletes the target file and then redefines
it before it loads data from the extract file.

Yes File-AID/RDX deletes the object and then creates it again before loading data.
No File-AID/RDX appends data to the existing target object.

Replace Matches
When adding data to an object that is not empty and the INSERT operation fails because the row
or record already exists, this setting indicates whether or not the data should be replaced.

Yes For MVS:

If the target object is indexed (KSDS), data from the extract file replaces existing data in
the target object.

For Db2:
If the target Db2 table has a unique index, data from the extract file replaces existing
data in the target table.
No For MVS:
If the target object is indexed and an existing target record has a unique key that
matches the data from the extract file, the data from the extract file is discarded.

For Db2:
If the target table has a unique index and an existing target row has a unique key that
matches the data from the extract file, the data from the extract file is discarded. If the
target table does not contain a unique index and rows to be loaded already exist, no
data is discarded.

Extracted Rows
Indicates the number of extracted records (rows) to be loaded into each target object.

Source Object Extracted and Target Object to be Loaded

A list of the source and target objects to be loaded.

Source
Name of the source object from which records were extracted.

Target
Name of the target object to be loaded.

At the end of the Pre-Load Summary Report, messages summarize how many total records will be
loaded into the number of total objects, as well as, how many objects are in the extract file, including
the number of objects with no records extracted.
556 File-AID/RDX Reference

SQL Insert: DB2 Totals Report

The SQL Insert: DB2 Totals Report shown in Figure 303 is a summary of the tables and rows that were
loaded.

Figure 303. SQL Insert: DB2 Totals Report

File-AID/RDX 17.2 SQL Insert: DB2 Totals Report PAGE 1

DATE 2005-08-15
TIME 15.04.48



Inserted Replaced Discarded Load Object
---------- ---------- ---------- --------------------------------------------------------------------------------------------------- 
0 43 0 D-DSNLOCAT.TSOID01.EMP
9 0 0 D-DSNLOCAT.TSOID01.DEPT 
1 0 0 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8
____+____9_____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+___4____+___
_5____+____6____+____7____+____8____+____9____+___10____+___11____+___12____+___

***** 53 TOTAL rows were Loaded to 3 objects ***** 

***** 0 TOTAL rows were Discarded *****

* * * END OF REPORT * * *

The SQL Insert: DB2 Totals Report report consists of the following columns:

Inserted
The number of rows inserted into each object.

Replaced
The number of rows updated in each object.

Discarded
The number of extracted rows not loaded, but discarded, for each object.

Load Object
A list of the objects to which rows will be inserted.

MVS Load - MVS Totals Report

The MVS Load - MVS Totals Report shown in Figure 304 is a summary of the objects that were loaded,
showing how many records have been inserted, replaced, or discarded.
Load 557

Figure 304. MVS Load - MVS Totals Report

File-AID/RDX 17.2 MVS Load - MVS Totals Report PAGE 1

DATE 2005-08-15
TIME 15.04.48



Inserted Replaced Discarded Load Object
---------- ---------- ---------- ---------------------------------------------------------------------------------------------- 
3 - - M-TSOID01.FASAMP.EMPMAST.EMPM 
0 0 3 M-TSOID01.FASAMP.EMPLOYEE.EMPM 

***** 3 TOTAL rows were Loaded to 1 object ***** 

***** 3 TOTAL rows were Discarded for 1 object *****

* * * END OF REPORT * * *

The MVS Load - MVS Totals Report consists of the following columns:

Inserted
The number of records inserted into each file.

Replaced
The number of records updated in each file.

Discarded
The number of extracted records not loaded, but discarded, for each file.

Load Object
A list of the files to which records are loaded.

SQL Insert: DB2 Committed Rows Report

The SQL Insert: DB2 Committed Rows Report shown in Figure 305 on page 558 is a summary of
information about the rows inserted and committed.
558 File-AID/RDX Reference

Figure 305. SQL Insert: DB2 Committed Rows Report

File-AID/RDX 17.2 SQL Insert: DB2 Committed Rows Report PAGE 1

DATE 2005-08-15
TIME 15.04.49


Note: Use the last entry in the "Restart Point" column when you restart the job. Commit Interval: 2

Target Table: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____+___
10____+___11____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+____8____+_
___9____+___10____+___11____+___12____+___ 

Restart Point Committed 
-------------------------- ---------- 
RESTART=00000002/00000000 2
RESTART=00000004/00000000 2
RESTART=00000006/00000000 2
RESTART=00000008/00000000 2
RESTART=00000010/00000000 2
RESTART=00000012/00000000 2
RESTART=00000014/00000000 2
RESTART=00000016/00000000 2
RESTART=00000018/00000000 2
RESTART=00000020/00000000 2
RESTART=00000022/00000000 2
RESTART=00000024/00000000 2
RESTART=00000026/00000000 2
RESTART=00000028/00000000 2
RESTART=00000032/00000000 2
RESTART=00000034/00000000 2
RESTART=00000036/00000000 2
RESTART=00000038/00000000 2
RESTART=00000040/00000000 2
RESTART=00000042/00000000 2
Next Restart Point 1


Target Table: D-TSOID01.DEPT 

Restart Point Committed 
-------------------------- ---------- 
RESTART=00000044/00000000 1
RESTART=00000046/00000000 2
RESTART=00000048/00000000 2
RESTART=00000050/00000000 2
RESTART=00000052/00000000 2


The SQL Insert: DB2 Committed Rows Report displays the location of the tables into which rows were
inserted and the commit interval you specified in the Commit Every Nth Row field on the
Processing Options screen. In addition, the SQL Insert: DB2 Committed Rows Report contains the
following columns:

Target Table
A list of the tables to which rows have been committed. Entries in this column are arranged such
that each grouping represents the tables to which rows were committed within any given commit
interval.

Restart Point
For each group of rows committed in a given commit interval, this column displays the values for
the RESTART parameter in the DD EXTPARMS dataset necessary to restart the load job without
causing errors.

Committed
Displays the number of rows committed at each commit interval. If you specified a value other
than an asterisk (*) in the Maximum Rows to Discard field on the SQL Insert Processing Options
screen and you reach that value, the last entry in this column may contain a number less than
the commit interval.
Load 559

SQL Insert - DB2 Delete Report

The SQL Insert - DB2 Delete Report shown in Figure 306 on page 559 is a summary of the data deleted
during the load process.

Figure 306. SQL Insert - DB2 Delete Report

File-AID/RDX 17.2 SQL Insert - DB2 Delete Report PAGE 1

DATE 2005-08-15
TIME 15.04.48
SSID D810

Rows Deleted ALL EXISTING Data From Object 
---------- ------------------------------------------------------------------------------------------------------------------------

4 D-DSNLOCAT.TSOID01.DEPT 

1 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____+___10
____+___11____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+____8____+____9
____+___10____+___11____+___12____+___ 

***** 5 TOTAL rows were Deleted from 2 objects *****

* * * END OF REPORT * * *


The header part of the report shows the following:

• The Db2 subsystem ID.

The SQL Insert - DB2 Delete Report displays the location of the tables from which rows were deleted.
In addition, it contains the following columns:

Rows
The number of rows deleted from each table.

If the number of rows shows -1, it indicates that Db2 executed a mass delete
from a table in a segmented tablespace.

Deleted ALL EXISTING Data From Object

A list of tables from which rows were deleted.

DB2 Load - DB2 Delete Report

The DB2 Load - DB2 Delete Report shown in Figure 307 is a summary of the data deleted during the
load process.
560 File-AID/RDX Reference

Figure 307. DB2 Load - DB2 Delete Report

File-AID/RDX 17.2 DB2 Load - DB2 Delete Report PAGE 1

DATE 2005-08-15
TIME 15.04.48
SSID D810

Deleted ALL EXISTING Data From Object:
D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+ ____7____+____8____+____9_____+___10____+___11
____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+____8____+____9____+___10____+___11_
___+___12____+___
-------------------------------------------------------------------------------------------------------------------------------------

Referential constraint successfully dropped from table:
D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+ ____7____+____8____+____9_____+___10____+___11
____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+____8____+____9____+___10____+___11_
___+___12____+___


There were no rows to delete from table: 
D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+ ____7____+____8____+____9_____+___10____+___11
____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+____8____+____9____+___10____+___11_
___+___12____+___

Referential constraint successfully restored on table: 
D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+ ____7____+____8____+____9_____+___10____+___11
____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+____8____+____9____+___10____+___11_
___+___12____+___

* * * END OF REPORT * * *

The header part of the report shows the following:

• The Db2 subsystem ID.

The DB2 Load - DB2 Delete Report displays an execution message for each table from which rows
were deleted. The following are possible messages:

• Deleted ALL EXISTING Data From Object

• Referential constraint successfully dropped from table

• Referential constraint successfully restored on table

• There were no rows to delete from table

SQL Insert: DB2 Discard Report

The SQL Insert: DB2 Discard Report shown in Figure 308 is a summary of rows discarded during load
processing.
Load 561

Figure 308. SQL Insert: DB2 Discard Report

File-AID/RDX 17.2 SQL Insert: DB2 Discard Report PAGE 1
DATE 2005-08-15
TIME 15.04.48
SSID D810
Discard File . .: TSOID01.R43.DISCARD 

Note: 1) The "Record Number" indicates the relative data record within the Discard File; the line number when Viewing the file.
2) Detailed information on the SQL code or RDX error code causing the discard can be found in the RDERRORS DDNAME 

Target Object: LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____+__
_10____+___11____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+____8____
+____9____+___10____+___11____+___12____+___ 

Error Record(1) ID First 45 characters of the discarded record. Source Column Target Column
----- ----------- ----- --------------------------------------------- ------------------------------ ------------------------------ 
-803 325 D001 000010 CHRISTINE I RUSK A00 39
-803 326 D001 000020 MICHAEL L BENNETT B01 34
-803 327 D001 000030 SALLY A ALLE C01 47
-803 328 D001 000050 JOHN B KENNE E01 67
-803 329 D001 000060 IRVING F HEMIN D11 64
-803 330 D001 000070 EVA D DARROW D21 78
-803 331 D001 000090 EILEEN W MORAGA E11 54
-803 332 D001 000100 THEODORE Q ANDREWS E21 09
-803 333 D001 000110 VINCENZO G ZIEGFELD A00 34
-803 334 D001 000120 SEAN HEMINGWAY A00 21
-803 335 D001 000130 DOLORES M FRANKLIN C01 45
-803 336 D001 000140 HEATHER A MARTIN C01 17
-803 337 D001 000150 BRUCE RUSK D11 45
-803 338 D001 000160 ELIZABETH R MULSTR D11 37
-803 339 D001 000170 MASATOSHI J JONES D11 28
-803 340 D001 000180 MARILYN S STRANDEL D11 16
-803 341 D001 000190 JAMES H SAVAGE D11 29
-803 342 D001 000200 DAVID STRAN D11 45
-803 343 D001 000210 WILLIAM T SIMPS D11 09
-803 344 D001 000220 JENNIFER K ELLI D11 06
-803 345 D001 000230 JAMES J BENNETT D21 20
-803 346 D001 000240 SALVATORE M JACKSO D21 37
-803 347 D001 000250 DANIEL S MORAG D21 09
-803 348 D001 000260 SYBIL V JONES D21 89
-803 349 D001 000270 MARIA L FRANK D21 90
-803 350 D001 000280 ETHEL R RUSK E11 89
-803 351 D001 000290 JOHN R RICHAR E11 45
-803 352 D001 000300 PHILIP X BENNY E11 20
-803 353 D001 000310 MAUDE F BARNETT E11 33
-803 354 D001 000320 RAMLAL V JONES E21 99
-803 355 D001 000330 WING JAC E21 21

***** 31 of 43 rows from the Extract File were Discarded *****

* * * END OF REPORT * * *


The header part of the report shows the following:

• The Db2 subsystem ID.

• The name of the discard file.

The SQL Insert: DB2 Discard Report lists all target objects for which rows were discarded.

Target Object
The name of the target object the discarded record came from.

For each target object, The SQL Insert: DB2 Discard Report displays the following columns:

Error
The SQLCODE or File-AID/RDX error code indicating the error that caused the row to be
discarded.

Record
The "Record Number" indicates the relative data record within the Discard File, the line number
when viewing the file.
562 File-AID/RDX Reference

ID
The File-AID/RDX extract object identifier for the object to be loaded.

First 45 characters of the discarded record

Displays the first 45 characters of the discarded record.

Source Column
If the error that caused the row to be discarded was a column mapping error, this column
contains the name of the source column in error.

Target Column
If the error that caused the row to be discarded was a column mapping error, this column
contains the name of the target column in error.

MVS Load: VSAM Discard Report

The MVS Load: VSAM Discard Report shown in Figure 309 is a summary of records discarded during
load processing.

Figure 309. MVS Load: VSAM Discard Report

File-AID/RDX 17.2 MVS Load: VSAM Discard Report PAGE 1
DATE 2005-08-15
TIME 15.04.48

Discard File . .: TSOID01.R43.DISCARD.SQL.EMPM 

Note: 1) The "Record Number" indicates the relative data record within the Discard File; the line number when Viewing the file.

Target Object: M-TSOID01.FASAMP.EMPLOYEE.EMPM 

Error Record(1) ID First 45 characters of the discarded record. 
----- ----------- ----- --------------------------------------------- 
DUP 322 D003 00090MARTIAN EDWARD M AIRPLANE
DUP 323 D003 00100MULSTROM ROBERTA A HOLLYWOO
DUP 324 D003 00200JACKSON JOSEPH C ORATOR

***** 3 of 3 rows from the Extract File were Discarded *****

"* * END OF REPORT * * *

The header part of the report shows the following:

• The name of the discard file.

The MVS Load: VSAM Discard Report lists all target objects for which records were discarded.

Target Object
The name of the target object the discarded record(s) came from.

The MVS Load: VSAM Discard Report for each object consists of the following columns:

Error
The File-AID/RDX error code indicating the error that caused the record to be discarded.
Load 563

Record
The "Record Number" indicates the relative data record within the Discard File, the line number
when viewing the file.

ID
The File-AID/RDX extract object identifier for the object to be loaded.

First 45 characters of the discarded record

Displays the first 45 characters of the discarded record.
564 File-AID/RDX Reference
 565

Delete
Overview
Option 4, Delete, enables you to delete the data you have previously extracted from the source
objects. The related objects can be KSDS type VSAM files and/or Db2 tables or views. File-AID/RDX
determines which rows should be deleted based on the contents of a File-AID/RDX extract DASD or
tape file that you specify.

1. Before you can delete using an extract file on tape you must specify an
extract summary file (see Extract File Specification on page 573).
2. When your extract file contains Db2 records extracted from Db2 Image
Copy datasets, the Delete operation will be executed against the active
Db2 tables and not the Image Copy datasets.
3. Disguised extract files cannot be used for the Delete functions as the
disguised records will not match the source records as extracted.

The Delete function consists of an interactive phase and an execution phase.

The interactive phase takes place online and consists of a series of File-AID/RDX screens that prompt
you for information about the extract file and delete processing options. You can also save the
specified delete information as a Delete Request file. Using this information, File-AID/RDX builds JCL
that you can edit and save before you submit it for execution.

During the execution phase, File-AID/RDX performs the delete processing in batch mode. At the end
of the execution phase, File-AID/RDX produces reports that summarize the results of the delete
processing.

Support for Db2 XML and LOB Data Type

The Delete option processes an extract which includes XML and/or LOB columns.
566 File-AID/RDX Reference

Delete Reference List

The Delete Reference List screen shown in Figure 310 on page 566 is displayed when you

• Select Option 4, Delete, from the File-AID/RDX Primary Option Menu

or
• Enter the REFERENCE command from the Request File Member List.

The reference list for Delete includes all entries of the Load reference list plus all existing Delete
requests. When selecting a load request for the delete process, File-AID/RDX uses only the extract file
name from the selected list entry to start the on-line delete process (the selected request entry must
be a valid load or delete request).

File-AID/RDX adds a delete request to the list when a delete request is saved from the Delete
Processing Options Screen.

In addition, whenever you have successfully executed an extract, File-AID/RDX places an entry with
the extract file name into the delete reference list. However, extracts that originate from the “Single
Panel Extract” function are not included in the Delete Reference List.

You can also create a new delete request with the NEW command, or open a request file with the
REQUEST command to select the extract file for the delete process (the selected request entry must
be a valid load request).

Refer to Option G—Global User Defaults on page 82 for how to set the maximum number of list
entries for the reference list.

The reference list is stored in your personal USER profile. If your USER profile
file (‘userid.midlevlqualifier.PROFILE’) does not exist, File-AID/RDX will create
your USER profile when you are saving an extract or load request.

You may specify multiple line commands at a time. All line commands are processed before any
primary commands. When processing multiple commands File-AID/RDX displays a message like
“Processing line command 2 of 4” whenever it starts processing the next line command after the first.

Figure 310. Delete Reference List

File-AID/RDX ------------- Delete Reference List --------- Row 1 to 6 of 6

Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go S = Select
I = Info D = Delete from list L = Lock U = Unlock 

Request Extract File Name RT L YY/MM/DD
-------- ------------------------------------------------------ -- - --------
_ TSOID01.FRSAMP.CUSTDB.EXTRACT 10/02/02
_ TSOID01.FRSAMP.EXTRACT L L 10/02/01
_ TEST3 TSOID01.FRSAMP.TEST3.EXTRACT D 10/02/04
_ TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST) 09/01/24
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2 EL L 09/01/14
_ TEST2 TSOID01.FRSAMP.TEST2.EXTRACT L L 09/01/04
******************************* Bottom of data ********************************


The lower part of the screen displays a listing of your recently referenced load requests. Use the S line
commands to start a delete request based on the extract file specified for the selected entry.
Delete 567

Request
Name of the delete or load request (member name in the saved delete or load request file). A
blank entry means the request was saved to a sequential file or that it is an automatic entry after
executing an extract.

Extract File Name

Name of the file containing the extracted data. If saved to a PDS the member name is displayed in
parentheses.

RT
Request Type. Identifies the delete or load request type:

Delete only request.

EL

Extract and Continue with Load request.

Load only request.

L
Locked Entry. Identifies whether the request is locked in the reference list or whether it is
allowed to roll off.

blank

not protected from roll over.

Locked in reference list; entry will not roll off the list.

YY/MM/DD
Date when the load request was last saved or the extract was completed. The list entries are
ordered with the most recent date placed on top of the list.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

D (Delete from list)

Removes this request from the delete/load reference list.
568 File-AID/RDX Reference

G (Go)
Submits this delete request without any changes. The request must be a saved delete or load
request (RT must be D or L). File-AID/RDX validates the request before submitting the JCL for the
delete request.

The G line command is not available if the delete request includes objects
with XML and/or LOB columns. Use the S line command to process the
delete request.

I (Info)
Displays the Request Details screen, which provides more comprehensive information about the
load request. See Figure 311 for an example.

Figure 311. Request Details

File-AID/RDX ---------------- Request Details -------------------------------

Command ===>

Request Information: 
Request File Name . : TSOID01.FRSAMP.REQUEST 
Member Name . . . . : TEST3 
Request Type . . . . : DELETE 
Description . . . . : FRSAMP Delete request test 3 
Reference Date . . . : 2010/02/04 Reference Time: 00:00:07 

Driving Object Information: 
SSID . . . . . . . . : 
Name . . . . . . . . : 

Extract Information: 
Extract File Name . : TSOID01.FRSAMP.TEST3.EXTRACT 
Summary File Name . : 
Disguise Control File: 
Repository Name: 
Project Name: 
Extract Date . . . . : 2010/01/03 Extract Time : 00:00:07 

Relationship Information: 
File Name . . . . . : TSOID01.FRSAMP.RELATION 

L (Lock)
Protects this entry from rolling off the reference list.

S (Select)
Selects this request and displays the Delete Confirmation screen prefilled with the information
from the request.

U (Unlock)
Does not protect this entry from rolling off the reference list.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
Delete 569

DETAIL (D)
Expands the one-line display for each request into a two-line display. The additional line shows
the request description. See Figure 312 for an example. DETAIL is a toggle switch so enter DETAIL
again to return to the original format.

Figure 312. Delete Reference List - DETAIL Screen

File-AID/RDX ------------- Delete Reference List --------- Row 1 to 6 of 6

Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go S = Select
I = Info D = Delete from list L = Lock U = Unlock 

Request Extract File Name RT L YY/MM/DD
-------- ----------------------------------------------------- -- - --------
_ TSOID01.FRSAMP.CUSTDB.EXTRACT 04/09/02
Description: DB2-TSOID01.CUSTOMER 
_ TSOID01.FRSAMP.EXTRACT L L 04/09/01
Description: DB2-FRSAMP.CUSTOMER 
_ TEST3 TSOID01.FRSAMP.TEST3.EXTRACT D 10/02/04
Description: Delete from Test3
_ TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST) 04/08/24
Description: MVS-TSOID01.CUSTOMER 
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2 EL L 09/01/14
Description: MVS-TSOID01.ORDERTAB
_ TEST2 TSOID01.FRSAMP.TEST2.EXTRACT L L 09/01/04
Description: MVS-TSOID01.PARTTABL 
******************************* Bottom of data ********************************

Find
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.

Find looks for matches in the request detail information for each list entry. When a match is
found and is not visible in the displayed row, use the I (info) line command to display the detail
information.

NEW (N)
Starts a new delete request from an existing extract file. Use the NEW command to open extract
files created with File-AID/RDX prior to Release 3.0 that don’t have any saved load requests
associated with them, yet.

REQUEST (REQ)
Opens a saved request file. Refer to Request File Member List on page 570 for more information.

File-AID/RDX uses the default value as specified in your current profile. If your profile doesn’t
include a request file, File-AID/RDX prompts for one.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 313 on page 570 for an example. SIZE is a toggle switch so enter SIZE again to
return to the original format.
570 File-AID/RDX Reference

Figure 313. Delete Reference List - SIZE Screen

File-AID/RDX ------------- Delete Reference List --------- Row 1 to 6 of 6

Command ===> Scroll ===> CSR 
Request--Extract File Name-------------------------------------RT-L-YY/MM/DD
_ TSOID01.FRSAMP.CUSTDB.EXTRACT 04/09/02
_ TSOID01.FRSAMP.EXTRACT L L 04/09/01
_ TEST3 TSOID01.FRSAMP.TEST3.EXTRACT D 10/02/04
_ TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST) 04/08/24
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2 EL L 04/08/14
_ TEST2 TSOID01.FRSAMP.TEST2.EXTRACT L L 04/08/04
****************************** Bottom of data ********************************

Request File Member List

The Request File Member List shown in Figure 314 on page 570 is displayed when you

• Enter the REQUEST primary command on the Delete Reference List screen.

This screen displays the member list of a saved request file. Use one of the line commands to select a
member for your delete request.

If you select a member that does not contain valid delete request information, File-AID/RDX will
issue a message. Select a different member or issue the NEW or REFERENCE command to start
another delete request.

If you want to delete from an extract file created prior to Release 3.0, use the
NEW command to initiate a new delete request. Then you can enter the
name of the extract file to be used.

Figure 314. Request File Member List

File-AID/RDX ------------ Request File Member List ------- Row 1 to 8 of 8 

Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, REFerence
Line commands: G = Go S = Select

Request File ===> FRSAMP.EXTCRIT 

Member Description Changed 
-------- -------------------------------------------------- ---------- 
_ DB2VSAM db2 to vsam extract 2004/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 2004/08/13 
_ MIKE1 Member List 2004/05/10 
_ NODB2 mcust with db2 deleted 2004/01/25 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 2004/08/30
_ PART1 Member List 2003/02/11
_ SELCUST test select customer 2002/01/28 
_ TESTA test saving the criteria 2001/04/12
******************************* Bottom of data ********************************






Request File
If you didn’t specify a name with the REQUEST command, the request file name comes from your
current profile. Enter a new file name to change to a different saved request file and File-
AID/RDX will display its member list.

The lower part of the screen displays a listing of the file’s members.
Delete 571

Member
Member name in the saved delete, extract, or load request file. The member names are displayed
in alphabetical order.

Description
Text that was entered in the Description field when the delete, extract, or load request or extract
criteria was created. If you left the field blank during the request creation, File-AID/RDX sets the
description to the driving object type and name.

Changed
Date when the member was last saved.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

D (Delete)
Delete this member from the request file. Displays the Delete Confirmation window (Figure 315).

Figure 315. Delete Confirmation window

Delete Confirmation 
COMMAND ===> 

Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 

Member to be Deleted: TESTA 


ENTER to confirm delete 
END to return to Request File Member List 



G (Go)
Submits this delete request without any changes. The request must be a saved delete or load
request (RT must be D or L). File-AID/RDX validates the request before submitting the JCL for the
delete request.

The G line command is not available if the delete request includes objects
with XML and/or LOB columns. Use the S line command to process the
delete request.

R (Rename)
Rename the request member. The Rename Confirmation window (Figure 316) allows you to enter
a new name for the request file member.
572 File-AID/RDX Reference

Figure 316. Rename Confirmation window

Rename Confirmation 
COMMAND ===> 

Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 

Member to be Renamed: TESTA 
New Member name ===> 


ENTER to confirm rename 
END to return to Request File Member List 



S (Select)
Selects this request and displays the Delete Confirmation screen prefilled with all the
information from the selected request.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 317 for an example. SIZE is a toggle switch so enter SIZE again to return to the
original format.

Figure 317. Saved Request File Member List - SIZE Screen

File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8 

Command ===> Scroll ===> CSR
Member Description 
_ DB2VSAM db2 to vsam extract 
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 
_ MIKE1 Member List 
_ NODB2 mcust with db2 deleted 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 
_ PART1 Member List 
_ SELCUST test select customer 
_ TESTA test saving the criteria 
******************************* Bottom of data ********************************

REFERENCE
opens your delete reference list. Refer to Delete Reference List on page 566 for more information.
Delete 573

Extract File Specification

The Extract File Specification screen shown in Figure 318 is displayed when you

• Enter the NEW command in either the Delete Reference List or the Request File Member List.

Figure 318. Extract File Specification

File-AID/RDX ----------- Extract File Specification

-------------------------
Command ===> 


Please specify an Extract File or a pattern name (in order to select an 
Extract File from a list). 

Extract File ===> FRSAMP.EXTRACT 





* * * * When the Extract File is on TAPE, a Summary File is REQUIRED. * * * * 
* * * * When the Extract File is on DISK, a Summary File is OPTIONAL. * * * * 

Summary File usage ===> N (N = None; E = Existing; C = Create; U = Update) 
Summary File ===> 

Note: Creating or updating a Summary File requires the submission of 
a BATCH job. Upon completion of this batch job, the Summary File 
will be available for your use.

Use this screen to specify the name of the extract file on which you want to base the delete and
optionally, the extract summary file. Press ENTER to continue to the Delete Confirmation (Summary
File usage = N or E), Create New File (Summary File usage = C), or the ISPF/PDF EDIT Screen
(Summary File usage = U).

Extract File
Specify the name of the File-AID/RDX extract file on which you want to base the delete. An
asterisk (*) or pattern displays a selection list. The extract file must be in the format that File-
AID/RDX creates during extract. See Extract File on page 44 and File-AID/RDX Extract File on
page 377 for information about the format of the extract file.

When the extract contains an XML column, more rows may be deleted
than expected, since the XML column is not part of the WHERE clause
on the delete.

Summary File usage

Specify whether your delete request should utilize the summary file. The summary file is required
for extract files on tape or cartridge, it’s optional for extract files on disk. Starting with Release
4.8 of File-AID/RDX, a summary file is created automatically during the extract to tape process
(see Specify Extract “TO” File Information on page 338). For a multi-volume extract file, a
summary file can speed up processing as it contains the header and trailer information for the
extract.

N None - Specify N when the extract file is on disk and a summary file is not needed.
574 File-AID/RDX Reference

E Existing - Specify E when the summary file for this particular extract file already exists.
File-AID/RDX continues with the Delete Confirmation.
C Create - Specify C when you want File-AID/RDX to create the summary file for the above
extract file. File-AID/RDX then starts a batch job that extracts header and trailer
information from the extract file. After the batch job to create the summary file has
finished, you can continue the delete request for this extract file.

File-AID/RDX will display the Create New File screen (see Create New File) to allocate the
new file.
U Update - Specify U when you want File-AID/RDX to update an existing summary file for
the above extract file. File-AID/RDX then starts a batch job that extracts header and trailer
information from the extract file. After the batch job to update the summary file has
finished, you can continue the delete request for this extract file.

Summary File
Specify the name for the summary file (previously known as tape control file) that contains the
information for the above extract file that’s stored on tape, cartridge, or disk. The summary file is
required for extract files on tape or cartridge, it’s optional for extract files on disk. If your extract
file is a multi-volume file, a summary file can speed up processing as it contains the header and
trailer information for the extract. An asterisk (*) or pattern displays a selection list.

The summary file is the same for both Load and Delete processes. Therefore,
you may use a summary file created with the LOAD Option for deleting rows
based on the same extract tape file.

Edit JCL
The ISPF/PDF EDIT screen shown in Figure 319 is displayed when you select to have File-AID/RDX
create or update the summary file on the Extract File Specification screen.

Figure 319. ISPF/PDF EDIT Screen

VIEW - File-AID/RDX Generated JCL --------------------------- COLUMNS 001 072

COMMAND ===> SCROLL ===> CSR
You are now editing the JCL that File-AID/RDX has generated to perform
the required function. Change this JCL as desired before submitting. 



000004 //* XFRJSUMM
000005 //*--------------------------------------------------------------------
000006 //* THIS STEP WILL BUILD A SUMMARY FILE BY READING THE HEADER RECORDS 
000007 //* AND TRAILER RECORDS OF YOUR EXTRACT FILE. 
000008 //* 
000009 //SUMMARY EXEC PGM=XFREXEC,REGION=4096K,
000010 // PARM=(FR,A,B)
000011 //STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ170.CXVJLOAD, 
000012 // DD DISP=SHR,DSN=CPWR.MXVJ170.SXVJLOAD 
000013 //RDXMLIB DD DSN=CPWR.MXVJ170.CXVJMENU,DISP=SHR
000014 //EXTPARMS DD DSN=TSOID01.RDX.PARMS.1300827.T094308,DISP=SHR
000015 //EXTRACT DD DSN=TSOID01.FRSAMP.EXTRACT,
000016 // DISP=SHR
000017 //*
000018 //CONTROL DD DSN=TSOID01.RDX.SUMMARY,
000019 // DCB=(RECFM=VB,LRECL=32756,BLKSIZE=32760),
000020 // DISP=(NEW,CATLG,DELETE),
000021 // SPACE=(TRK,(5,5),RLSE),

Use this screen to edit and submit the extract summary JCL generated by File-AID/RDX.
Delete 575

If you want to save this JCL, use the ISPF/PDF CREATE or REPLACE command before you exit this
screen. Otherwise, File-AID/RDX deletes this file.

Submit this JCL to create the summary file with the extract header and trailer information. File-
AID/RDX will return to the Delete Reference List or Request File Member List where you entered the
NEW command.

Delete Confirmation
The Delete Confirmation screen shown in Figure 320 is displayed after you specified the extract file
to be used for the delete request.

Figure 320. Delete Confirmation

File-AID/RDX ------------- Delete Data Summary ------------------------------

Command ===> Scroll ===> PAGE

Extract File: TSOID01.FRSAMP.EXTRACT
SSID: DSN Location:

Obj Num rows/rec 
Object Name Type to delete Status 
-------------------------------------------- ---- ------------ ----------------
LOCATION.FRSAMP.PART_TABLE DB2 28 
LOCATION.FRSAMP.SUPPLIER_TABLE DB2 32 
LOCATION.FRSAMP.CUSTOMER_TABLE DB2 15 
LOCATION.FRSAMP.ORDER_TABLE DB2 33 
LOCATION.FRSAMP.ORDER_LINE_TABLE DB2 49 
LOCATION.FRSAMP.CONTACT_TABLE DB2 18 
'TSOID01.FRSAMP.CONTACTT' File 18 
'TSOID01.FRSAMP.ORDERLIN' File 49 
'TSOID01.FRSAMP.PARTTABL' File 28 
'TSOID01.FRSAMP.ORDERTAB' File 33 
'TSOID01.FRSAMP.SUPPLIER' File 32 
** End of List **

Use this screen to view information about the data to be deleted. The fields on this screen are display-
only—you cannot modify any values on this screen. Use the NEXT command to proceed.

In addition to the screen title and COMMAND field, the heading lines on this screen contain the
following field:

SSID
Displays the ID of the Db2 subsystem in which the tables and views that contain rows to be
deleted exist.

The body of this screen consists of the following fields:

Object Name
Displays the fully qualified name of the object from which to delete. If it is a Db2 object it
includes the location and creator ID of the table. MVS object names are fully qualified and
enclosed in single quotes (’).

OBj Type
The object type is indicated in the next column

• DB2
576 File-AID/RDX Reference

• File (MVS KSDS)

Num rows/rec to delete

Displays the number of rows or records that were extracted from each object when the extract file
was generated. A value of 0 in this column indicates that no rows or records were extracted from
the object and none will be deleted.

If your extract file was generated by a release of File-AID/RDX earlier than

release 1.2, File-AID/RDX will display N/A for each object in this column.

Status
If File-AID/RDX cannot find an object from which rows are to be deleted, it displays the message
Object not found.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:

NEXT
The NEXT command invokes the Delete Processing Options screen.

Delete Processing Options

The Delete Processing Options screen shown in Figure 321 is displayed when you enter the NEXT
command on the Delete Confirmation screen.

Figure 321. Delete Processing Options Screen

File-AID/RDX ------------ Delete Processing Options -------------- SSID: DSN

Command ===> 

Extract Dataset Name: TSOID01.FRSAMP.EXTRACT 

Discard Processing Options: 
Maximum Rows to Discard ===> * (* for no maximum) 
Save Discarded Rows ===> YES (Yes or No) 
Dataset for Discarded Rows ===> 'TSOID01.DISCARD.DELETE' 

Specify Processing Options for DB2 Objects: 
Commit Every Nth Row ===> 5000 (1-99999)

Save a Request ===> (Y or N)

Use the NEXT command to continue 

Use this screen to specify how often a Db2 COMMIT should be issued, whether or not tables should
be locked during delete processing, and options related to discarding rows that could not be deleted.
Use the NEXT command to proceed.

Extract File Name

Displays the name of the extract file that the delete process is using.
Delete 577

Discard Processing Options for DB2 Objects Area

Specify the discard options to be used with delete.

Maximum Rows to Discard

Specify the maximum number of errors encountered before processing stops. Specify an asterisk
(*) for no maximum or a value greater than 0. Specify 1 if you want processing to stop after any
errors are encountered. The discard file need not exist to specify a value in this field.

Save Discarded Rows

Specify whether or not to save rows that could not be deleted.

Yes Save rows that cannot be deleted in the discard file. If you specify Yes, you
must also specify a file in the File for Discarded Rows field.
No Do not save rows that cannot be deleted.

File for Discarded Rows

Specify the name of the file to which discarded rows will be saved. The discard file must be
sequential. If you specify Yes in the Save Discarded Rows field and specify a file that does not
exist, File-AID/RDX will display the Discard File Allocation pop-up window. The discard file can
be used as input to the Db2 delete process if a previous delete job was completed normally, but
rows were discarded.

Specify Processing Options Area

Specify the Db2 processing options to be used when deleting Db2 data. This section only displays
when there are Db2 objects in the extract file.

Commit Every Nth Row

Specify the number of rows File-AID/RDX should delete before it performs a Db2 COMMIT. This
value must be less than or equal to the value specified for the Max Commit Interval installation
parameter.

Save a Request
Specify whether or not to save the delete request to a request file.

Yes Save the current delete request information to a request file. File-AID/RDX
presents the Save Delete Request panel (Figure 323 on page 579) where
you identify the delete request file to save your request to.
No Do not save the current delete request.

After you save the request in the Save Delete Request panel (Figure 323 on
page 579), the Delete Processing Options Screen is redisplayed with this
field set to 'No'. Each time you set the field to 'Yes' you have the option of
creating another saved delete request or replacing the existing request.

Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:
578 File-AID/RDX Reference

NEXT
The NEXT command invokes the next screen in the delete process. If you specified a discard file
that does not exist, the Discard File Allocation pop-up window is displayed next. If you specified
a discard file that already exists, the Edit Delete JCL screen is displayed. There are no operands
associated with this command.

Discard File Allocation

The Discard File Allocation pop-up window shown in Figure 322 is displayed when you specify a non-
existent discard file on the Delete Processing Options screen.

Figure 322. DISCARD File Allocation Pop-Up Window

File-AID/RDX ------------ Delete Processing Options -------------- SSID: DSN 

Command ===> n 

Ex Discard File Allocation 

Di Command ===> 
M 
S Discard File: TSOID01.DISCARD.DATA 
F 
Specify the Discard File attributes 
Sp VOLSER ===> 
C Generic Unit ===> SYSDA 
Block Size ===> 23680 (DSORG=PS,RECFM=VB,LRECL= 127 ) 
Space Units ===> TRK (BLK, TRK, or CYL) 
Primary QTY ===> 2 (in above units) 
Secondary QTY ===> 2 (in above units) 


Use this window to specify the characteristics of the discard file to be allocated. Press ENTER to
proceed.

Discard File
Displays the name of the file to which discarded rows will be written. See Discard File on page 45
for more information about the discard file.

VOLSER
Specify the volume serial number of the file. A volume serial number is optional.

Generic Unit
Specify the device type on which the new file will reside. The names of these devices are
installation dependent.

Block Size
Specify the block size for the new file. You can specify BLKSIZE=0 for systems that support it. This
causes the system to determine an optimum block size.
Delete 579

Space Units
Specify whether space for the new file will be allocated in blocks (BLK), tracks (TRK), or cylinders
(CYL).

Primary QTY
Specify the initial number of space units that will be allocated for the new file.

Secondary QTY
Specify the number of space units that will be allocated for each secondary extent.

Primary Commands
The following File-AID/RDX-specific primary command is valid in the Discard File Allocation
window.

NEXT
Opens an edit session on the Delete JCL generated by File-AID/RDX. There are no operands
associated with this command.

Save Delete Request

The Save Delete Request panel shown in Figure 323 is displayed when you specify Y in the Save a
Request field of the Delete Processing Options Screen.

Figure 323. Save Delete Request

File-AID/RDX --------------- Save Delete Request ---------------------------

COMMAND ===> 

Specify Delete Request File Information: 
File name ===> FRSAMP.EXTCRIT 
Member ===> 

Description ===> 


Use this screen to save the current delete request information.

Press Enter to process the file information. The saved request will also appear in your Delete
Reference List (see Delete Reference List on page 566).

The body of the Save Delete Request screen consists of the following fields:
580 File-AID/RDX Reference

File Name
Specify the name of the file where you want to save the delete request. You can save the request
to existing files. Existing files must conform to the format outlined for the request file in File-
AID/RDX Extract/Load/Delete Request File on page 368.

Pre-Release 4.3 extract/load request files have fixed or fixed-blocked

(RECFM=F or RECFM=FB) record format. When saving a Pre-Release 4.3
request file, File-AID/RDX will issue an invalid format message. Specify a new
name to save the request file in variable-blocked (RECFM=VB) format.

If you specify a new file, you must specify the following allocation parameters in the Create New
File screen (Figure 175 on page 334).

Member
If the file is partitioned, specify the name of the member to contain the delete request.

Description
Enter a short description of the delete request. This description is displayed in the Delete
Reference List. Using this description is a helpful way to document your delete request.

After you save the request, the Delete Processing Options Screen is
redisplayed with this field set to 'NO'.

SAVE Confirmation
When saving an Extract, Delete or Load request File-AID/RDX checks to see if the member already
exists. If the member already exists, the Save Confirmation window (Figure 324) displays:

Figure 324. Save Confirmation window

Save Confirmation
COMMAND ===> 

The following member exists and will be replaced: 
Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 
Member to be Deleted: TESTA 


ENTER to confirm Save and replace existing member 
END return to Save Request enter a different member name 



Viewing Delete JCL

The ISPF/PDF VIEW screen shown in Figure 325 is displayed when you enter the NEXT command on
the Delete Processing Options screen or the Discard File Allocation pop-up window.
Delete 581

Figure 325. ISPF/PDF VIEW Screen

VIEW - File-AID/RDX Generated JCL --------------------------- COLUMNS 001 072

COMMAND ===> SCROLL ===> HALF
You are now editing the JCL that File-AID/RDX has generated to perform
the required function. Change this JCL as desired before submitting. 

SYSIN data is contained in: TSOID01.RDX.FBCNTL.D080202.T115332
TSOID01.RDX.VBCNTL.D080202.T115332
****** ***************************** TOP OF DATA ******************************
000004 /* XFRJDLT1
000005 //*SQLID TSOID01 IS UNAUTHORIZED TO:
000006 //* DELETE ROWS FROM TABLE FRSAMP.ORDER_TABLE
000007 //* DELETE ROWS FROM TABLE FRSAMP.ORDER_LINE_TABLE
000008 //* DELETE ROWS FROM TABLE FRSAMP.PART_TABLE
000009 //* XFRJSTRD
000010 //*-------------------------------------------------------------------
000011 //* CLEAN1ST: - THIS STEP WILL ENSURE THAT ALL TEMPORARY DATASETS
000012 //* USED IN THIS JOB ARE DELETED.
000013 //* - THIS ALLOWS FOR KEEPING AND RERUNNING THE JOB EVEN IF
000014 //* SUBSEQUENT STEPS FAIL.
000015 //* - THIS JCL IS ALSO RESTARTABLE AT
000016 //* RESTART=XXXXXXXX ON THE JOBCARD.
000017 //*-------------------------------------------------------------------
000018 //CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
000019 //SYSPRINT DD SYSOUT=*
000020 //SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW

Use this screen to edit and submit the delete JCL generated by File-AID/RDX.

If you want to save this JCL, use the ISPF/PDF CREATE or REPLACE command before you exit this
screen. Otherwise, File-AID/RDX deletes this file and other temporary files, including the control card
PDSEs (prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix and prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix) (see Control
Card Cleanup on page 581).

Submit this JCL with the SUBMIT command to perform the delete.

Control Card Cleanup

The last 2 steps, CLEANCTL and CLEANEXT, in the load and delete jobs delete the File-AID/RDX
control card PDSEs and EXTPARMS parameter files. Whether steps CLEANCTL and CLEANEXT are
commented out or executed is determined by the global job option Delete in-stream data datasets at
EOJ (page 83). If the job option is set to NO, File-AID/RDX control card PDSEs and EXTPARMS
parameter files created in the load and delete jobs will NOT be deleted. Keeping the datasets until all
steps run successfully allows for the restarting of the JCL at any step.

Periodically, you may want to manually delete the control card PDSEs and EXTPARMS parameter files
that are no longer needed for saved jobs to be resubmitted.
582 File-AID/RDX Reference

The Delete Process

This section describes the delete process including:

• Db2 Delete Job Steps

• Db2 Delete JCL
• MVS Delete Job Steps
• MVS Delete JCL

Db2 Delete Job Steps

This section describes the steps in the Db2 delete job.

1. CLEAN1ST—File Cleanup (IDCAMS)

This step ensures that all temporary files used in this job are deleted. This enables you to keep
and rerun a JCL stream.

2. DLDRV—Delete Driver (XFREXEC)

This step ensures that the tables from which data is to be deleted exist. In addition, this step
checks user authorization for subsequent steps and separates the extract file into multiple files,
one file per table to be deleted.

3. DELETE—Delete Rows (XFREXEC)

This step deletes data from the tables listed on the Delete Confirmation screen.

The DELETE step uses Db2 SQL with all the data that was extracted included in the WHERE
clause. File-AID/RDX deletes rows based on exact matches instead of index values.

File-AID/RDX determines the order in which to delete rows such that rows from dependent tables
are deleted first. Then, rows from parent tables are deleted. This continues until all rows are
either deleted or discarded.

4. CLEANLST—File Cleanup (IDCAMS)

This step deletes all File-AID/RDX temporary files used in this job. Deleting these files in the last
job step enables the job to be restarted in any prior step.

5. CLEANCTL—File Cleanup (IEFBR14) - Optional

This step deletes the File-AID/RDX control card PDSEs. Whether step CLEANCTL is commented
out or executed is determined by the global job option Delete in-stream data datasets at EOJ (page
83). If the job option is set to NO, File-AID/RDX control card PDSEs created in the load and delete
jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows for the
restarting of the JCL at any step.

6. CLEANEXT—File Cleanup (IDCAMS) - Optional

This step deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is
commented out or executed is determined by the global job option Delete in-stream data datasets
at EOJ (page 83). If the job option is set to NO, File-AID/RDX EXTPARMS files created in the load
and delete jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows
for the restarting of the JCL at any step.

Db2 Delete JCL

The delete JCL shown in Figure 326 performs the execution phase of the delete process for Db2
objects. You can code and execute the JCL separately in a batch job. In addition, File-AID/RDX can
automatically generate the JCL through the interactive portion of the Delete option.
Delete 583

Figure 326. Delete JCL (continues on next page)

//* XFRJDLT1
//*SQLID TSOID01 IS AUTHORIZED FOR ALL THE DELETE STEPS
//* XFRJSTRD
//*-------------------------------------------------------------------
//* CLEAN1ST: - THIS STEP WILL ENSURE THAT ALL TEMPORARY FILES
//* USED IN THIS JOB ARE DELETED.
//* - THIS ALLOWS FOR KEEPING AND RERUNNING THE JOB EVEN IF
//* SUBSEQUENT STEPS FAIL.
//* - THIS JCL IS ALSO RESTARTABLE AT ANY STEP BY CODING
//* RESTART=XXXXXXXX ON THE JOBCARD. (XXXXXXXX = STEPNAME)
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-split-file
DELETE File-AID-deletbl-file
DELETE File-AID-discard-file
SET MAXCC=0
SET LASTCC=0
/*
//* 
//* --------------------------------------------------------------------
//* DLDRV:- DELETE DRIVER
//* THE FOLLOWING IS PERFORMED IN THIS STEP.
//* - ENSURE TABLES EXIST.
//* - SPLIT EXTRACT FILE INTO SEPARATE DELETE FILES.
//* --------------------------------------------------------------------
//DLDRV EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT),
// PARM=(FR,9,B)
//*
//STEPLIB DD DSN=File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//EXTRACT DD DSN=TSOID01.FRSAMP.EXTRACT,
// DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//*
//DISCARDS DD DSN=File-AID-discard-file,
// DCB=(RECFM=VB,LRECL=302,BLKSIZE=306,DSORG=PS),
// SPACE=(TRK,(1,1),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//*
//DELETBL DD DSN=File-AID-loadtbl-file,
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920,DSORG=PS),
// SPACE=(TRK,(1,1),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//*
//SPLITnnn DD DSN=File-AID-split-file,
// DCB=(RECFM=VB,LRECL=119,BLKSIZE=123,DSORG=PS),
// SPACE=(123,(2300,460),RLSE),
// UNIT=SYSDA,
// DISP=(NEW,CATLG,DELETE)
//SYSOUT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//SYSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DB2DCT), 
// DISP=SHR 
584 File-AID/RDX Reference

Figure 327. Db2 Delete JCL (continued)

//*-XFRDLT2----------------------------------------------------------
//* DELETE: - DELETE FROM TABLES
//*
//* NOTE: WHEN FILE-AID/RDX PERFORMS A DELETE, ALL DB2 DELETE RULES
//* ARE OBSERVED. THE CASCADE AND SET NULL DELETE RULES MAY
//* HAVE AN IMPACT ON WHICH ROWS ARE DELETED AND FROM WHICH
//* TABLES. SEE THE REFERENCE MANUAL FOR MORE DETAILS.
//*
//*-------------------------------------------------------------------
//DELETE EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT),
// PARM=(FR,8,B)
//*
//STEPLIB DD DSN=File-AID/RDX-load-libraries,DISP=SHR
// DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//SYSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(DB2DCT),
// DISP=(SHR)
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//DELETEIN DD DSN=TSOID01.prefix.SPLITnnn.Dnnnnnn.Tnnnnnn.suffix,
// DISP=(OLD,KEEP,KEEP)
//XCPTNRPT DD SYSOUT=(*)
//TOTLSRPT DD SYSOUT=(*)
//COMMTRPT DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSOUT DD SYSOUT=(*)
//DISCARDS DD DSN=TSOID01.DISCARD,
// DISP=MOD
//SYSPRINT DD SYSOUT=(*)
//TPTPRINT DD SYSOUT=(*)
//*
//*-------------------------------------------------------------------
//* CLEANLST: - THIS STEP WILL PERFORM A DELETE OF ALL TEMPORARY
//* FILES USED IN THIS JOB.
//* - KEEPING THE FILES UNTIL ALL STEPS RUN SUCCESSFULLY
//* ALLOWS FOR THE RESTARTING OF THE JCL AT ANY STEP.
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-split-file
DELETE File-AID-deletbl-file
DELETE File-AID-discard-file

SET MAXCC=0
SET LASTCC=0
/*
/*-------------------------------------------------------------------
//CLEANCTL EXEC PGM=IEFBR14,COND=(4,LT) 
//DFBPDSE DD DSN=DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//DVBPDSE DD DSN=DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//CLEANEXT EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 XFRJCLXT
//SYSPRINT DD SYSOUT=*
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE extract-parms-file,
SET MAXCC=0
SET LASTCC=0
//* 
//* /*XFRJCLXT*/
Delete 585

DLDRV Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.

The parameter information in the PARM field on the EXEC statement for the DLDRV step must have
the following format:

Table 66. EXEC Statement PARM Field—DLDRV Step

Default
Parameter Length Description
Value
Product FR 2 File-AID/RDX
Option 9 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the DLDRV step:

Table 67. DD Statements—DLDRV Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTRACT File-AID/RDX extract file name.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
DISCARDS File-AID/RDX discard file.
DELETBL File into which File-AID/RDX reads the Delete Control Table. The Delete Control Table is used by
the DELETE step.
SPLITnnn Output file to which File-AID/RDX writes data from a single table from the extract file.

• One file for each table, where 001 ≤ nnn ≤ 099.

• The LRECL and BLKSIZE parameters must be large enough to hold the extracted records.

• The SPACE parameters must be large enough to hold all extracted records.
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSPRINT Standard output stream.
SYSTERM Output class for runtime errors.
TPTPRINT Standard output stream for optional diagnostics.
SYSIN File-AID/RDX’s Delete Control Table. Used to verify authorities and identify tables from which
data is to be deleted.

Delete Control Table

The Delete Control Table (member DB2DCT in the control card PDSE) contains information about
the tables from which data is to be deleted. It is the input (SYSIN) for the DELETE step.
586 File-AID/RDX Reference

Figure 328. Db2 Delete Control Table

*FR.17.02.00 F=1------- D B 2 D E L E T E C O N T R O L T A B L E ---------

*
*
* TARGET OBJECT 
* ----------------------------------
TI: ID=003 ROW COUNT= 888 NNN 
TC: TSOID01
TT: PART_TABLE
*
* TARGET OBJECT 
* ----------------------------------
TI: ID=002 ROW COUNT= 357 NNN 
TC: TSOID01
TT: ORDER_TABLE
*
* TARGET OBJECT 
* ----------------------------------
TI: ID=001 ROW COUNT= 1462 NNN 
TC: TSOID01
TT: ORDER_LINE_TABLE
*

The Delete Control Table contains the following columns:

Table 68. Delete Control Table

Field Name Description
TI Target Information:
ID Internal table control number; corresponds to the Hnnn record in the extract file.
ROW COUNT Identifies the number of rows to be deleted; the number of records extracted from the table
when the extract file was generated.
N or Y Represents the D record supplement indicator (see also Product Record — 0 on page 378).
N or Y Represents the extract IMPLICITLY HIDDEN columns indicator (see also Extract IMPLICITLY
HIDDEN columns on page 251).
N, C or V Represents the compression indicator (see also Compress on page 339).
TC The target creator ID. Creator ID of the table from which data is to be deleted.
TT The target table; the table from which data is to be deleted.

DELETE Step Parameters and DD Statements

XFREXEC is the File-AID/RDX program name.

The parameter information in the PARM field in the EXEC statement must have the following format:
Table 69. EXEC Statement PARM Field—Delete Step
Default
Parameter Length Description
Value
Product FR 2 File-AID/RDX
Option 8 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch
Delete 587

The following DD statements are required for delete:

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
SYSIN File-AID/RDX’s Delete Control Table. Used to verify authorities and identify tables from which
rows will be deleted.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
DELETEIN Input file(s) generated during split processing.
XCPTNRPT Output class for Delete Exception Report.
TOTLSRPT Output class for Delete Summary Report.
COMMTRPT Output class for Commit Report.
RDXSQLCD Output class for detailed SQL error information from Db2.
SYSOUT Output class for error messages and reports.
DISCARDS File-AID/RDX discard file.
SYSPRINT Standard output stream.
TPTPRINT Standard output stream for optional diagnostics.
SYSTERM Output class for runtime errors.

Return Codes
An execution return code (RC) appears in the output listing. For return codes other than 0, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return
Description
Code
0 Job ran to completion.
4 Job ran to completion, warnings issued.
8 Job completed with error.
16 Severe error, job aborted.

MVS Delete Job Steps

This section describes the steps in the delete job when you include MVS objects in the delete process.

1. CLEAN1ST—File Cleanup (IDCAMS)

This step deletes any existing files that are to be created in this job. This enables you to keep and
rerun a JCL stream.

2. DLDRV—Delete Driver (XFREXEC)

This step checks user authorization for subsequent steps and separates the extract file into
multiple files, one file per object where records are to be deleted.

3. DLMVS—MVS Delete (XFREXEC)

This step generates and executes the DELETE statements to delete data from the objects.

4. CLEANLST—File Cleanup (IDCAMS)

This step deletes all File-AID/RDX temporary files used in this job.

5. CLEANCTL—File Cleanup (IEFBR14) - Optional

588 File-AID/RDX Reference

This step deletes the File-AID/RDX control card PDSEs. Whether step CLEANCTL is commented
out or executed is determined by the global job option Delete in-stream data datasets at EOJ (page
83). If the job option is set to NO, File-AID/RDX control card PDSEs created in the load and delete
jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows for the
restarting of the JCL at any step.

6. CLEANEXT—File Cleanup (IDCAMS) - Optional

This step deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is
commented out or executed is determined by the global job option Delete in-stream data datasets
at EOJ (page 83). If the job option is set to NO, File-AID/RDX EXTPARMS files created in the load
and delete jobs will NOT be deleted. Keeping the datasets until all steps run successfully allows
for the restarting of the JCL at any step.

MVS Delete JCL

The following pages contain the delete JCL that is generated when the delete process contains only
MVS files. When Db2 and MVS objects are included, the JCL will also include the JCL for the Db2
delete option as described earlier. You can code and submit the JCL on the following pages to execute
the delete process without invoking the interactive phase of the Delete function. The required
parameter information and DD statements for File-AID/RDX-specific steps are described following the
JCL.
Delete 589

Figure 329. MVS Delete JCL (continues on next page)

//* XFRJDLT1
//*SQLID TSOID01 IS AUTHORIZED FOR ALL THE DELETE STEPS
//* XFRJSTRD
//*------------------------------------------------------------------- 
//* CLEAN1ST: - THIS STEP WILL ENSURE THAT ALL TEMPORARY FILES 
//* USED IN THIS JOB ARE DELETED. 
//* - THIS ALLOWS FOR KEEPING AND RERUNNING THE JOB EVEN IF 
//* SUBSEQUENT STEPS FAIL. 
//* - THIS JCL IS ALSO RESTARTABLE AT ANY STEP BY CODING 
//* RESTART=XXXXXXXX ON THE JOBCARD. (XXXXXXXX = STEPNAME) 
//*------------------------------------------------------------------- 
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-split-file
DELETE File-AID-MVS-info-file
DELETE File-AID-discard-file
SET MAXCC=0
SET LASTCC=0
/*
//* 
//* 
//*--------------------------------------------------------------------- 
//* DLDRV:- DELETE DRIVER 
//* THE FOLLOWING IS PERFORMED IN THIS STEP. 
//* - ENSURE TABLES EXIST. 
//* - SPLIT EXTRACT FILE INTO SEPARATE DELETE FILES. 
//*---------------------------------------------------------------------
//DLDRV EXEC PGM=XFREXEC,REGION=8192K,COND=(4,LT), 
// PARM=(FR,9,B) 
//* 
//STEPLIB DD DSN=File-AID/RDX-load-libraries,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR 
//EXTRACT DD DSN=File-AID-extract-file, 
// DISP=SHR 
//* 
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//DISCARDS DD DSN=File-AID-discard-file, 
// DCB=(RECFM=VB,LRECL=309,BLKSIZE=27998,DSORG=PS), 
// SPACE=(27998,(2,2),RLSE), 
// UNIT=SYSDA, 
// DISP=(NEW,CATLG,DELETE) 
//MVSINFO DD DSN=File-AID-MVS-info-file, 
// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920,DSORG=PS), 
// SPACE=(TRK,(1,1),RLSE), 
// UNIT=SYSDA, 
// DISP=(NEW,CATLG,DELETE) 
//DDnnn DD DSN=MVS-file, 
// DISP=SHR
//* 
//SPLITnnn DD DSN=File-AID-split-file, 
// DCB=(RECFM=VB,LRECL=309,BLKSIZE=27998,DSORG=PS), 
// SPACE=(27998,(2,2),RLSE), 
// UNIT=SYSDA, 
// DISP=(NEW,CATLG,DELETE) 
//SYSOUT DD SYSOUT=(*) 
//RDXSQLCD DD SYSOUT=(*) 
//SYSPRINT DD SYSOUT=(*)
//TPTPRINT DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*) 
590 File-AID/RDX Reference

Figure 330. MVS Delete JCL (continued from previous page)

//*-XFRJDLT3---------------------------------------------------------- 
//* DELETE FROM MVS/KSDS 
//*------------------------------------------------------------------- 
//DLMVS EXEC PGM=XFREXEC,COND=(4,LT), 
// PARM=(FR,E,B) 
//* 
//STEPLIB DD DSN=File-AID/RDX-load-libraries,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR 
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//MVSIN DD DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix(MVSDCT), 
// DISP=SHR 
//DELETEIN DD DSN=File-AID-splitnnn-file,
// DISP=(OLD,KEEP,KEEP) 
//DDnnn DD DSN=MVS-file, 
// DISP=(MOD,KEEP,KEEP) 
//XCPTNRPT DD SYSOUT=(*) 
//TOTLSRPT DD SYSOUT=(*) 
//COMMTRPT DD SYSOUT=(*) 
//RDERRORS DD SYSOUT=(*) 
//SYSOUT DD SYSOUT=(*) 
//DISCARDS DD DSN=File-AID-discard-file, 
// DISP=MOD 
//SYSPRINT DD SYSOUT=(*) 
//SYSTERM DD SYSOUT=(*) 
//* 
//*------------------------------------------------------------------- 
//* CLEANLST: - THIS STEP WILL PERFORM A DELETE OF ALL TEMPORARY 
//* FILES USED IN THIS JOB. 
//* - KEEPING THE FILES UNTIL ALL STEPS RUN SUCCESSFULLY 
//* ALLOWS FOR THE RESTARTING OF THE JCL AT ANY STEP. 
//*-------------------------------------------------------------------
//CLEAN1ST EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 
//SYSPRINT DD SYSOUT=* 
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE File-AID-sort-file
DELETE File-AID-split-file
DELETE File-AID-MVS-info-file
DELETE File-AID-discard-file
SET MAXCC=0
SET LASTCC=0
/*
//* 
//*-------------------------------------------------------------------
//* CLEANCTL: - THIS STEP WILL PERFORM A DELETE OF THE TEMPORARY 
//* SYSIN CNTL PDSE DATASETS USED IN THIS JOB. 
//* - KEEPING THE DATASETS UNTIL ALL STEPS RUN SUCCESSFULLY 
//* ALLOWS FOR THE RESTARTING OF THE JCL AT ANY STEP. 
//* NOTE! - IF THIS JOB IS TO BE RESUBMITTED ON A REGULAR BASIS 
//* THIS STEP MUST BE DELETED IN ORDER TO KEEP THE 
//* ORIGINAL SYSIN DATA INTACT. 
/*-------------------------------------------------------------------
//CLEANCTL EXEC PGM=IEFBR14,COND=(4,LT) 
//* 
//DFBPDSE DD DSN=DSN=TSOID01.prefix.FBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//DVBPDSE DD DSN=DSN=TSOID01.prefix.VBCNTL.Dnnnnnn.Tnnnnnn.suffix, 
// DISP=(OLD,DELETE,DELETE) 
//CLEANEXT EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048 XFRJCLXT 
//SYSPRINT DD SYSOUT=*
//SYSIN DD * IDCAMS DELETE STATEMENTS FOLLOW
DELETE extract-parms-file,
SET MAXCC=0
SET LASTCC=0
//* 
//* /* XFRJCLXT*/
Delete 591

DLDRV Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.

The parameter information in the PARM field on the EXEC statement for the DLDRV step must have
the following format:

Table 70. EXEC Statement PARM Field—DLDRV Step

Parameter Default Description
Length
Value
Product FR 2 File-AID/RDX
Option 9 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the DLDRV step:

Table 71. DD Statements—LDDRV Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD).
RDXMLIB Library containing File-AID/RDX messages.
EXTRACT File-AID/RDX extract file name.
DISCARDS File-AID/RDX discard file.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
MVSINFO File-AID/RDX information for MVS files from which to delete.
DDnnn MVS files from which to delete.
SPLITnnn Output file to which File-AID/RDX writes data for a single file from the extract file.

• One file for each object, where 001≤ nnn≤ 099.

• The LRECL and BLKSIZE parameters must be large enough to hold the extracted records.

• The SPACE parameters must be large enough to hold all extracted records.
SYSOUT Output class for error messages and reports.
RDXSQLCD Output class for detailed error information.
SYSPRINT Standard output stream.
TPTPRINT Standard output stream for optional diagnostics.
SYSTERM Output class for runtime errors.
MVSIN File-AID/RDX’s Delete Control Table. Used to verify authorities.

MVS Delete Control Table

The MVS Delete Control Table (member MVSDCT in the control card PDSE) contains information
about the objects from which to delete data. It is the input (MVSIN) for the DLMVS step.
592 File-AID/RDX Reference

Figure 331. MVS Delete Control Table (MVSDCT)


*FR.17.02.00 F=2-------- M V S D E L E T E C O N T R O L T A B L E --------
* 
*CONTROL NUMBER OF ROWS 
*NUMBER FILE NAME TO BE DELETED S
*------- ---------------------------------------------- -------------- -
006 TSOID01.FRSAMP.CONTACTT 18 N
005 TSOID01.FRSAMP.CUSTOMER 15 N
004 TSOID01.FRSAMP.ORDERTAB 33 N
003 TSOID01.FRSAMP.ORDERLIN 49 N
002 TSOID01.FRSAMP.SUPPLIER 32 N
001 TSOID01.FRSAMP.PARTTABL 28 N
/* 

The table contains the following information:

Table 72. MVS Delete Control Table

Field Name Description
CONTROL NUMBER Internal table control number.
FILE NAME Contains a list of the MVS files from which data is to be deleted.
NUMBER OF ROWS TO Contains the number of rows that were extracted from each file when the extract file was
BE DELETED generated.
S N or Y. Represents the D record supplement indicator (see also Product Record — 0 on page
378).

DLMVS Step Parameter List and DD Statements

XFREXEC is the File-AID/RDX program name.

The parameter information in the PARM field on the EXEC statement for the DLMVS step must have
the following format:
Table 73. EXEC Statement PARM Field—DLMVS
Parameter Default Description
Length
Value
Product FR 2 File-AID/RDX
Option E 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for the DLMVS step:

Table 74. DD Statements—DLMVS Step

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD); Db2 load library.
RDXMLIB Library containing File-AID/RDX messages.
EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
MVSIN File-AID/RDX’s MVS Delete Control Table (MVSDCT). Used to verify authorities.
DELETEIN Input file(s) generated during split processing.
DDnnn MVS files from which to delete.
XCPTNRPT Output class for Insert Exception Report.
TOTLSRPT Output class for Load Summary Report.
COMMTRPT Output class for Commit Report.
Delete 593

Table 74. DD Statements—DLMVS Step (Continued)

DD Statement Description
RDERRORS Output class for detailed error information and field mapping error information from File-
AID/RDX.
SYSOUT Output class for error messages and reports.
DISCARDS File-AID/RDX discard file.
SYSPRINT Standard output stream.
TPTPRINT Standard output stream for optional diagnostics.
SYSTERM Output class for runtime errors.

MVS Delete Return Codes

An execution return code (RC) appears in the output listing. For return codes other than 0, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return
Description
Code
0 Job ran to completion without error.
4 Job ran to completion without error, warnings issued.
8 Job ran with error. Subsequent job steps stopped.
16 Severe error, job aborted.
594 File-AID/RDX Reference

Miscellaneous Delete Topics

This section provides information about the following topics:

• Db2 Privileges
• Db2 Delete Rules
• Restartability (Db2 only)
• Reusing the Discard File
• Delete Reports.

Db2 Privileges
The SQLID used to submit the Delete JCL is the default SQLID as specified in the load profile (see also
Default SQLID on page 65) and must have one of the privileges listed below.

• SYSADM.
• DBADM for the database where tables or views from which rows are to be deleted reside.
• DELETE privilege for all tables or views from which rows are to be deleted.
• Ownership of the tables and views (and their dependents) from which rows are to be deleted.

Db2 Delete Rules

File-AID/RDX determines which rows to delete by comparing the extract file to the tables from which
rows were extracted in Option 2, Extract. When a record from the extract file matches a row from a
table, File-AID/RDX deletes the row from the table.

File-AID/RDX begins deleting rows from a dependent table, then proceeds with a parent table, and then
its parent table, etc. When File-AID/RDX performs a delete, all Db2 delete rules are observed. CASCADE
and SET NULL delete rules, however, may have an unexpected impact on which rows are deleted and
from which tables.

CASCADE
When File-AID/RDX deletes a row from a parent table, Db2 also deletes all related rows from dependent
tables that have the CASCADE delete rule in effect. If the parent table has dependents that were not
part of the original extract and the CASCADE delete rule is in effect for these relationships, Db2 will
delete rows that were not part of the original extract file. Furthermore, File-AID/RDX will not report on
such rows because they were not in the original extract file.

SET NULL
When File-AID/RDX deletes a row from a parent table, Db2 sets to null the foreign key value of all
related rows in a dependent table for which the SET NULL delete rule is in effect. If these tables are
involved in a cyclical relationship (where Table A is a parent of Table B, Table B is a parent of Table C,
and Table C is a parent of Table A) and the SET NULL delete rule is in effect for one of the
relationships (for example, Table A—Table B relationship,) the following occurs:

1. File-AID/RDX deletes rows from Table A using values from the extract file.
2. Db2 enforces the SET NULL delete rule, setting foreign key values for the corresponding
dependent rows in Table B to null.
3. Based on the extract file, File-AID/RDX successfully deletes rows from Table C.
4. Based on the extract file, File-AID/RDX attempts to delete rows from Table B. The delete is only
partially successful, however. Those rows in Table B whose foreign key values were set to null were
not deleted because their column values no longer match the values in the File-AID/RDX extract
file.
5. File-AID/RDX discards the rows from the extract file for which the delete failed.
Delete 595

Restartability (Db2 only)

File-AID/RDX enables you to restart a failed Db2 delete job from any particular step.

The JCL generated for the Delete job is step-restartable. To restart a Delete job:

1. Code the RESTART keyword parameter on the job card as follows:

RESTART=xxxxxxxx

where xxxxxxxx is the name of the step at which you want to restart the job.

If the job failed before the DELETE step skip to step 5.

If the job failed during the DELETE step, you must restart the job at the DELETE step and then
continue with step 2.

2. Examine the Commit Report. Find the last report entry value in the Restart Point column of the
Commit Report. This value has the following format:

'RESTART=yyyyyyyy/zzzzzzzz'

where yyyyyyyy is the number of rows committed and zzzzzzzz is the number of rows discarded.
File-AID/RDX uses these values to determine where processing should restart.

3. Edit the DD EXTPARMS dataset and modify the line containing RESTART
RESTART=00000000/00000000 with the values from step 2.
4. Determine whether or not the delete job stopped because the maximum rows to discard limit was
reached. To do this, examine the delete job output for File-AID/RDX error E336 or E187. These
errors indicate that the limit set by Max Rows to Discard parameter was reached. In this case,
increase the Max Rows to Discard parameter for the DELETE step. Max Rows to Discard is the
fourteenth parameter in the DELETE EXEC statement PARM field (directly preceding the Restart
Point Indicator).
5. Submit the JCL.

Reusing the Discard File

File-AID/RDX enables you to reuse the discard file as input to the Db2 delete process when the Db2
delete job was completed normally, but rows were discarded.

Discarded records are written to the discard file when you specify YES in the Save Discarded Rows
field on the Delete Processing Options screen. The discard file is modeled after the extract file with
similar attributes and contents, such as product, header, base table create, map, data and trailer
records. The discard data records are those that have been discarded because of RI constraints,
duplicate rows, etc.

To reuse the discard file as input for the interactive phase of the Db2 Delete function, you must step
through the interactive phase specifying the name of the discard file in the File Name field on the
Delete Extracted Rows screen. If you use the discard file as input for the interactive phase, be sure to
specify a new discard file during the interactive phase.

Delete Reports
File-AID/RDX generates the reports described below during the delete process. There are seven delete
reports:

Delete - DB2 Authority Report

Contains information about the authority of the SQLID to be used for the delete.
596 File-AID/RDX Reference

Pre-Delete Summary Report

Contains a summary of the delete process.

Delete: DB2 Discard Report

Contains information about rows discarded during delete processing.

MVS Delete: VSAM Discard Report

Contains information about VSAM records discarded during delete processing.

Delete: DB2 Totals Report

Contains information about rows deleted and discarded.

MVS Delete: MVS Totals Report

Contains information about records deleted and discarded from MVS KSDS type files.

Delete: DB2 Committed Rows Report

Contains information about how many times Db2 COMMITS were issued and how many rows
were affected.

Delete - DB2 Authority Report

The Delete - DB2 Authority Report shown in Figure 332 contains information about the authority of
a given SQLID.

Figure 332. Delete - DB2 Authority Report

File-AID/RDX 17.2 DB2 Delete - DB2 Authority Report PAGE 1

DATE 2005-08-15
Extract File. . : TSOID01.R42.EXTRACT(Member) TIME 15.04.49
SSID D810
SQLID. . . . . .: TSOID01

Objects With Errors 
------------------------------------------------------------------------------------------------------------------------------------
Error: E273 The SQLID does not have authority to execute Delete 
Target: D-FADB2.ORDER_1

Error: E273 The SQLID does not have authority to Delete
Target: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____+___10___
_+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9____+
___10____+____11____+___12____+___



* * END OF REPORT * * *

The header part of the report shows the following:

• The name of the extract file. If the extract file is a PDS, the member name is also displayed.
• The Db2 subsystem ID.
• The SQLID used for the delete request.

The Delete - DB2 Authority Report provides the following information:

Delete 597

Objects With Errors

Lists the errors and the name of the target object the error applies to.

Error
Lists the File-AID/RDX error message associated with the object in error.

Target
Lists the name of the target object the error applies to.

If there are no authority issues, the following message appears instead:

“The SQLID has authority to perform all the job steps”

Pre-Delete Summary Report

The Pre-Delete Summary Report shown in Figure 333 is a summary of the tables and rows to be
deleted.

Figure 333. Pre-Delete Summary Report

File-AID/RDX 17.2 Pre-Delete Summary Report PAGE 1

DATE 2005-08-15
Extract File. . : TSOID01.R42.EXTRACT(Member) TIME 15.04.49
SSID D810

Extracted
ID Rows Delete From Object 
---- ---------- ------------------------------------------------------------------------------------------------------------------

D001 43 D-DSNLOCAT.TSOID01.EMP 

D002 (3) M-TSOID01.FASAMP.EMPMAST *** Sequential File data will not be deleted ***

D003 3 M-TSOID01.FASAMP.EMPLOYEE 

D004 0 D-DSNLOCAT.TSOID01.PROJ 

D005 9 D-DSNLOCAT.TSOID01.DEPT 

D006 0 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+___
_8____+____9____+___10____+___11____+___12____+___ 

D007 0 D-DSNLOCAT.TSOID01.PROJACT 

D008 0 D-DSNLOCAT.TSOID01.EMPPROJACT 

* * * END OF REPORT * * *

The header part of the report shows the following:

• The name of the extract file. If the extract file is a PDS, the member name is also displayed.
• The name of the delete (load) request file. If the request file is a PDS, the member name is also
displayed.
• The Db2 subsystem ID.

The Pre-Delete Summary Report consists of the following columns:

ID
The File-AID/RDX extract object identifier for the object from which rows or records will be
deleted.
598 File-AID/RDX Reference

Extracted Rows
The number of rows or records to be deleted from each listed object.

Delete From Object

A list of the objects from which rows or records will be deleted.

Delete: DB2 Discard Report

The Delete: DB2 Discard Report shown in Figure 334 on page 598 is a summary of rows discarded
during delete processing.

Figure 334. Delete: DB2 Discard Report

File-AID/RDX 17.2 Delete: DB2 Discard Report PAGE 1

DATE 2005-08-15
TIME 15.04.49
SSID D810
Discard File . .: TSOID01.R43.DELETE.DISCARD.EMPM 

Note: 1) The "Record Number" indicates the relative data record within the Discard File; the line number when Viewing the file.
2) DSNITAR information on the SQL code(s) causing the discard can be found in the RDXSQLCD DDNAME.

Target Object: D-DSNLOCAT.TSOID01.DEPT

Error Record(1) ID First 45 characters of the discarded record. Source Column Target Column
----- ----------- ----- --------------------------------------------- ------------------------------ ------------------------------
-100 323 D005 A00 SPIFFY COMPUTER SERVICE DIV.
-100 324 D005 B01 PLANNING
-100 325 D005 E01 SUPPORT SERVICES
-100 326 D005 E11 OPERATIONS
-100 327 D005 E21 SOFTWARE SUPPORT

***** 4 of 9 rows from the Extract File were Discarded *****


Target Object: D-DSNLOCAT.TSOID01.EMP

Error Record(1) ID First 45 characters of the discarded record. Source Column Target Column
----- ----------- ----- --------------------------------------------- ------------------------------ ------------------------------
-100 328 D001 000010 CHRISTINE I RUSK A00 39
-100 329 D001 000020 MICHAEL L BENNETT B01 34

***** 2 of 43 rows from the Extract File were Discarded *****


The header part of the report shows the following:

• The Db2 subsystem ID.

• The name of the discard file.

The Delete: DB2 Discard Report lists all target objects for which rows were discarded.

Target Object
The name of the target object the discarded record came from.

The Delete: DB2 Discard Report for each object consists of the following columns:

Error
The SQLCODE or File-AID/RDX error code indicating the error that caused the row to be
discarded.
Delete 599

Record
The "Record Number" indicates the relative data record within the Discard File, the line number
when viewing the file.

ID
The File-AID/RDX extract object identifier for the object to be deleted.

First 45 characters of the discarded record

Displays the first 45 characters of the discarded record.

MVS Delete: VSAM Discard Report

The MVS Delete: VSAM Discard Report shown in Figure 335 is a summary of records discarded during
delete processing of MVS data.

Figure 335. MVS Delete: VSAM Discard Report

File-AID/RDX 17.2 MVS Delete: VSAM Discard Report PAGE 1

DATE 2005-08-15
TIME 15.04.49

Discard File . .: TSOID01.R43.DELETE.DISCARD.EMPM 

Note: 1) The "Record Number" indicates the relative data record within the Discard File; the line number when Viewing the file.

Target Object: M-TSOID01.FASAMP.EMPLOYEE 

Error Record(1) ID First 45 characters of the discarded record. 
------- --------- ----- --------------------------------------------- 
NFD 322 D003 00090MARTIN EDWARD M AIRPLANE MAN

***** 1 of 3 rows from the Extract File was Discarded *****

* * * END OF REPORT * * *

The header part of the report shows the following:

• The name of the discard file.

The body of the MVS Delete: VSAM Discard Report lists all target objects for which records were
discarded.

Target Object
The name of the target object the discarded record(s) came from.

The MVS Delete: VSAM Discard Report for each object consists of the following columns:

Error
The File-AID/RDX error code indicating the error that caused the record to be discarded.

Record
The "Record Number" indicates the relative data record within the Discard File, the line number
when viewing the file.
600 File-AID/RDX Reference

ID
The File-AID/RDX extract object identifier for the object to be deleted.

First 45 characters of the discarded record

Displays the first 45 characters of the discarded record.

Delete: DB2 Totals Report

The Delete: DB2 Totals Report shown in Figure 336 is a summary of the deleted rows for each object.

Figure 336. Delete: DB2 Totals Report

File-AID/RDX 17.2 Delete: DB2 Totals Report PAGE 1

DATE 2005-08-15
TIME 15.04.49
SSID D810

Deleted Discarded Deleted From Object
---------- ---------- ---------------------------------------------------------------------------------------------------------

41 2 D-DSNLOCAT.TSOID01.EMP
4 5 D-DSNLOCAT.TSOID01.ACT
1 0 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+_
___9_____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6
____+____7____+____8____+____9____+___10____+___11____+___12____+___ 

***** 46 TOTAL rows were Deleted from 3 objects ***** 

***** 7 TOTAL rows were Discarded for 2 objects *****

* * * END OF REPORT * * *

The header part of the report shows the following:

• The Db2 subsystem ID.

The Delete: DB2 Totals Report consists of the following columns:

Deleted
The number of rows deleted from each table.

Discarded
The number of rows discarded from each table.

Deleted From Object

A list of the tables from which rows were deleted.

MVS Delete: MVS Totals Report

The MVS Delete: MVS Totals Report shown in Figure 337 on page 601 is a summary of the files from
which the specified number of records were deleted.
Delete 601

Figure 337. MVS Delete: MVS Totals Report

File-AID/RDX 17.2 MVS Delete: MVS Totals Report PAGE 1

DATE 09/07/2005
TIME 15.04.49



Deleted Discarded Deleted From Object
---------- ---------- -------------------------------------------------------------------------------------------------- 
2 1 M-TSOID01.FASAMP.EMPLOYEE 

***** 2 TOTAL rows were Deleted from 1 object ***** 

***** 1 TOTAL row was Discarded for 1 object *****

* * * END OF REPORT * * *


The MVS Delete: MVS Totals Report consists of the following columns:

Deleted
The number of records deleted from each file.

Discarded
The number of records discarded from each file

Deleted From Object

A list of the fully qualified MVS file names (without quotes) from which records were deleted.

Delete: DB2 Committed Rows Report

The Delete: DB2 Committed Rows Report shown in Figure 338 is a summary of information about the
rows inserted and committed.
602 File-AID/RDX Reference

Figure 338. Delete: DB2 Committed Rows Report

File-AID/RDX 17.2 Delete: DB2 Committed Rows Report PAGE 1

DATE 2005-08-15
TIME 15.04.49


Note: Use the last entry in the "Restart Point" column when you restart the job. Commit Interval: 2

Target Table: D-TSOID01.DEPT 

Restart Point Committed 
-------------------------- ---------- 
RESTART=00000002/00000000 2
RESTART=00000004/00000000 2

***** TOTAL Rows 4 ***** 

Target Table: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____+___
10____+___11____+___12____+___.TABLE____1____+____2____+____3____+___4____+____5____+____6____+____7____+____8____+_
___9____+___10____+___11____+___12____+___ 

Restart Point Committed 
-------------------------- ---------- 
RESTART=00000006/00000000 2
RESTART=00000008/00000000 2
RESTART=00000010/00000000 2
RESTART=00000012/00000000 2
RESTART=00000014/00000000 2
RESTART=00000016/00000000 2
RESTART=00000018/00000000 2
RESTART=00000020/00000000 2
RESTART=00000022/00000000 2
RESTART=00000024/00000000 2
RESTART=00000026/00000000 2
RESTART=00000028/00000000 2
RESTART=00000032/00000000 2
RESTART=00000034/00000000 2
RESTART=00000036/00000000 2
RESTART=00000038/00000000 2
RESTART=00000040/00000000 2
RESTART=00000042/00000000 2
RESTART=00000044/00000000 2
RESTART=00000045/00000000 1

***** TOTAL Rows 41 *****

The Delete: DB2 Committed Rows Report displays either the subsystem or the location of the tables
from which rows were deleted and the commit interval you specified in the Commit Every Nth Row
field on the SQL Insert Processing Options screen. In addition, the Commit Report contains the
following columns:

Target Table
A list of the tables to which rows have been committed. Entries in this column are arranged such
that each grouping represents the tables to which rows were committed within any given commit
interval.

Restart Point
For each group of rows committed in a given commit interval, this column displays the values for
the DELETE RESTART parameter necessary to restart the delete job without causing errors.

Committed
Displays the number of rows committed at each commit interval. If you specified a value other
than an asterisk (*) in the Maximum Rows to Discard field on the SQL Insert Processing Options
screen and you reach that value, the last entry in this column may contain a number less than
the commit interval.
 603

Data Privacy
Overview
Option 5, Data Privacy, enables you to disguise extracted data from one or more related objects and
works in conjunction with File-AID/Data Solutions and File-AID Data Privacy. Compuware
recommends installation and/or configuration of the current GA versions of the three products to
take advantage of recent enhancements. File-AID/Data Solutions must be installed at your site to
access Option 5, Data Privacy.

Using File-AID/RDX with File-AID Data Privacy (Using DPR)

File-AID Data Privacy is a component of the Topaz Workbench 1 and provides the ability to easily
create Data Privacy rules for your Enterprise files or databases.

File-AID Data Privacy protects your data by concealing sensitive information while maintaining data
integrity, table relationships, and data format during processing. For example, a female employee
name field can be replaced by a recognizable fictitious female name or a nonsensical set of characters.
File-AID Data Privacy:

• Builds rules used to disguise data for a defined collection of fields.

• Provides a graphical means for applying data encryption to fields for supported data connections.
• Allows you to replace field values with consistent valid data via key encryption (using an
encoding key value) or via substitution with meaningful readable data.
• Allows you to age dates by adding or subtracting from the date or replacing the date with a
specific date.

File-AID Data Privacy is Compuware's solution for addressing all of your data privacy needs whether
you have files or databases on distributed machines or on a mainframe computer. File-AID Data
Privacy allows you to protect your data by concealing sensitive information while maintaining data
integrity, table relationships, and data format during processing. You can:

• Build rules to disguise data for a defined collection of fields.

• Replace field values with consistent valid data via key encryption or via substitution with
meaningful readable data.

Refer to the File-AID Data Privacy documentation on how to define Dynamic Privacy Rules (DPR) that
can be applied to File-AID/RDX extracts. Once the Dynamic Privacy Rules have been defined, you can
disguise data during an extract using File-AID/RDX Option 2 Extract (see also Option 2, Use DPR, of
Disguise Extract File on page 341) or disguise an existing extract file with Option P of the Data
Privacy Menu (see also DPR: Disguise Existing Extract on page 611).

In order to execute batch jobs using File-AID Data Privacy, the job submitter must
have a RACF record with an OMVS segment for z/OS UNIX (or equivalent if using
a different security package). This can be done with BPX.DEFAULT.USER, but note
that z/OS v1.13 is the last release to support BPX.DEFAULT.USER. The
CPUTIMEMAX value in the OMVS segment must be large enough to
accommodate the File-AID Data Privacy jobs being run.

1. The Compuware Workbench has been replaced by the Topaz Workbench. The Topaz Workbench provides all of the
functionality of the previous Compuware Workbench as well as any additional chargeable functionality.
604 File-AID/RDX Reference

Using File-AID/RDX with File-AID/Data Solutions (Using DCF)

File-AID/RDX provides the relationship information for the objects to be extracted and propagates
the disguised data to the related objects.

File-AID/Data Solutions provide the functionality to disguise data fields through aging, encryption,
translation, data generation, and field exits. For each data field being disguised, disguise criteria must
be defined with the specific details of the disguise action. Disguise criteria can be defined for Db2 and
MVS objects.

The process of defining what data is sensitive and how each field is to be disguised requires careful
planning and should be handled by someone in a privacy administration role.

Once the disguise criteria have been defined they can be stored in the Disguise Criteria File. What
disguise criteria and where it is stored is also included in the Disguise Control File (DCF). The
Disguise Control File can be made available to all users of the product who choose to use that
Disguise Control File. As part of creating an extract request, you have an option to disguise the
extract. When the disguise option is selected and a Disguise Control File specified, all disguise criteria
defined for objects included in the extract will be applied.

What Is Disguise?
There are many different ways to disguise data. The File-AID/Data Solutions product provides disguise
functionality and groups three functions together as disguise functions: encryption, aging and
translation. Encryption is really character substitution where a numeric position is replaced with a
numeric position and an alphabetic position is replaced by an alphabetic position. Aging is used to
disguise date fields by incrementing or decrementing the original date. Translation is replacing the
original data with other data stored in a translate table. There are several different ways to determine
which data from the translate table is used as the replacement value. Translate always uses some data
as input to determine which entry is selected from the translate table and then replaces the data in
the requested fields with data stored in the translate table.

In addition to the three functions identified within File-AID/Data Solutions as disguise techniques,
data generation and field exits are also valid ways to disguise data. Data Generation can generate
sequential or random values appropriate for the data type; it can also generate new values based on a
table of valid values. Field Exits are user written exit routines that can take whatever action is
required to disguise the data.

Which disguise function to use is determined by the three R's of disguise: repeatable, reversible, and
readable. Repeatable means that the same input value must always return the same value or set of
values; the same data from multiple objects or files must be disguised the same. Reversible means that
there must be a way to get back to the original data value. Readable means that the data must look
valid to the human eye; name fields should contain name information not just a random string of
characters.

Planning Disguise Strategy

Disguise is much more than a new product feature. Being successful will require careful planning and
understanding your related data and disguise requirements.

The first part of this process is deciding what data is considered sensitive data and determining how it
should be disguised. Once the sensitive data fields have been identified it is not always a small task to
locate all the tables and files in which the sensitive data exists. The File-AID/RDX relationship file
can assist you to identify the related objects and fields.

Most likely, you will define disguise criteria for a specific purpose. For example, you establish disguise
rules that are to apply whenever data is moved from the production to any test region. Once a
strategy has been defined and disguise criteria created, many users would likely share the criteria;
every user extracting data from the production environment would be directed to use the defined
disguise rules. Any File-AID/RDX user can create disguise criteria as long as they have authority to
write to the Disguise Control File.
Data Privacy 605

File-AID/RDX and File-AID/Data Solutions are tools for implementing a data protection strategy;
before any disguise criteria can be defined, the customer has to design a data protection strategy. File-
AID/RDX assumes that work has been done and supports the implementation of the strategy.

When related fields are considered sensitive data there are additional planning considerations. It is
your responsibility to choose a disguise method that will produce appropriate results for the related
field. If the related field is a key field, it is likely that the replacement value will need to be unique.
You must choose a technique that produces unique values; encryption and some translate methods
will fulfill this requirement.

Enforcing Disguise
File-AID/RDX does not place restrictions on who is authorized to extract and disguise data. However,
the user running the extract must be able to read the data in order to run the extract. If they can read
the data to extract, they can likely read the data in other ways as well.

It will be a user's responsibility to request the extract file be disguised and to provide the appropriate
Disguise Control File. If the Disguise Control File does not include criteria for an object being
extracted, no disguise will be applied to that object.

Creating DCF Disguise Criteria

All criteria used by the File-AID/RDX disguise function must be created through the bridge to File-
AID/Data Solutions from File-AID/RDX. Criteria created directly within File-AID/Data Solutions is not
usable from File-AID/RDX disguise.

File-AID/RDX provides a central point of control for defining disguise criteria and will provide the
necessary layout information to File-AID/Data Solutions. The actual panel on which the criteria are
entered will be a File-AID/Data Solutions panel but the criteria will be stored in a file provided by
File-AID/RDX.

Criteria creation is always done by object. Each object must be uniquely identified, which for Db2
objects includes the location, creator and object name. There can be three different types of criteria:
related, associated and unrelated. File-AID/RDX determines what type of disguise criteria will be
created based on the fields selected for disguising.

Unrelated Criteria
Unrelated criteria is straightforward, it applies to a single object and must be defined for any field in
the object that is to be disguised. Unrelated criteria always applies to a single object and cannot be
shared.

Related Criteria
Related criteria can be more complex because it is defined once and propagated to related fields in
other objects.

Associated Criteria
Associated criteria are always defined on a single unrelated field and can be applied to fields in
different objects; identification of the additional data locations is a manual process.

Simple and Complex Disguise Criteria

Simple disguise criteria are entirely determined by the contents of a single field, and are repeatable. If
the value of "ABC" is replaced with "123" once, and the same disguise rule is applied again, it will
yield the same value, "123", every time.

Any disguise criteria that are not repeatable, or that are not entirely determined by the contents of a
single field, are called complex criteria. This includes any disguise rule for a field based on the
606 File-AID/RDX Reference

contents of another field. It also includes the use of a partial column in a relationship when the
disguise of one part is based on the contents of another part. It also includes the use of the File-
AID/Data Solutions Data Generator because the value generated for the current column is affected by
the value generated for the previous column. Also any rule that involves randomization is complex,
because it is not repeatable across multiple objects.

Disguise Control File and Disguise Criteria Storage

The Disguise Control File (DCF) determines which disguise criteria is applied to which object. The
actual criteria created by File-AID/Data Solutions will be stored in the Disguise Criteria File. The
Disguise Criteria File must be a PDS. File-AID/RDX generates the member name for related and
unrelated criteria; the user can provide a name for associated criteria.

The Disguise Control File will control all disguise actions and will allow the same set of disguise
specifications to be used with different Relationship Files.

A Disguise Control File contains a set of disguise rules for specific objects. Maintaining multiple
Disguise Control Files provides flexibility in how you choose to manage the disguise process. You
may choose to define different sets of disguise criteria for the same objects by storing them in
different Disguise Control Files. For example, one set of disguise criteria could be defined for
production data being moved to the training subsystem and a different set of disguise criteria could
be defined for production data being moved to the offshore test subsystem. The disguise rules for data
being loaded for training purposes may be much less extensive than the disguise rules required if the
data is to be sent offshore for testing. Multiple Disguise Control Files allow customers to define
protection that is appropriate for the environment where the data will be loaded.

The related, associated and unrelated disguise criteria is stored in the Disguise Criteria File. This
allows the correct disguise criteria to be applied for each object and also allows the same disguise
criteria to be applied to multiple objects for related and associated criteria. At extract time, you
specify the Disguise Control File and all disguise criteria defined for the objects being extracted will
be applied as defined in the DCF.

Sharing Disguised Data with Other File-AID Products

You can disguise your Db2 extracted data for greater data security. The Data Privacy function in File-
AID/RDX is the same as in File-AID for DB2 and in File-AID for IMS. File-AID/RDX can share the
Disguise Control File and Disguise Criteria File with File-AID for DB2 and File-AID for IMS. File-
AID/RDX can also share disguise rules with File-AID for DB2.

Db2 XML and LOB Data Type Considerations

DCF Disguise Criteria cannot be created on XML and/or LOB columns.

XML and CLOB column data in extracts can only be disguised with Dynamic Privacy Rules (Disguise
Option 2, DPR). Dynamic Privacy Rules must be defined with the File-AID Data Privacy component of
the Topaz Workbench (see also Using File-AID/RDX with File-AID Data Privacy (Using DPR) on page
603). Disguising DBCLOB columns is not supported.

Disguise Considerations for Conditional (Data-Driven) Application

Relationships (AR-C)
Disguise Criteria may not be defined for columns/fields that are the dependent of a data driven
Application Relationship (Conditional AR).

When a data driven AR exists in a relationship thread, data that may have been extracted outside of
this data driven relationship, due to other potential relationships, may not be disguised.
Data Privacy 607

Disguise Considerations for “Cloned” Extract Requests

When disguising a “cloned” extract request (see also Modify Extract Request on page 227), any
Disguise rules created for the modified object names will be applied. If there is no Disguise Criteria
defined for the modified object name, File-AID/RDX applies the Disguise Criteria defined for the
original object name.

Unicode Considerations
DCF Disguise Criteria cannot be created on Unicode columns or fields.

Unicode data in extracts can only be disguised with Dynamic Privacy Rules (Disguise Option 2, DPR).
Dynamic Privacy Rules must be defined with the File-AID Data Privacy component of the Topaz
Workbench (see also Using File-AID/RDX with File-AID Data Privacy (Using DPR) on page 603).

GDG Considerations
You can define disguise criteria for the GDG base and specific relative and absolute generations.

When specifying the GDG base without a relative generation as the MVS Filter Object, the Object
Preview will list the GDG base and all the existing GDS with their absolute generations. When
entering the GDG with a relative generation, the name will be treated as a fully qualified name and
the Object Preview will include only the GDS with the relative generation.

This processing allows you to define disguise criteria for the GDG base for absolute generations and
for relative generations.

Define the Disguise Criteria for a GDG object in the same way as the object is extracted (based on the
relationship definition) for the Disguise Criteria to be applied. If the object is extracted as the GDG
base, the Disguise Criteria must be defined for the GDG base. If the object is extracted with the
relative GDS, the Disguise Criteria must be defined for the relative GDS. If the object is extracted with
the absolute GDS, the Disguise Criteria must be defined for the absolute GDS.

The Disguise Control File (DCF) specifies the disguise criteria to be used for the GDG base or specific
generation.

Audit Trail reports include the full GDS name with the absolute generation.

Suggested Disguise Approach

To ensure consistent disguise result, it is recommended to have a Privacy or Security Administrator
identify:

• The objects that contain sensitive data that needs to be disguised

• The data fields in those objects that need to be disguised

• The relationship file that is the most comprehensive for the objects to be disguised

• One Disguise Control File that will contain the disguise information for all objects to be
disguised (Only use multiple Disguise Control Files when the same objects needs to have
different disguise criteria.)

• Disguise Criteria and Business Rules files

Then the Privacy or Security Administrator can:

• Build the object list of all objects to be disguised

– Use an existing extract request that includes all or most of the objects to be disguised
608 File-AID/RDX Reference

– Use ObjectIn and Related commands to add other object to be disguised

• Use the most suitable disguise method and criteria for each field to be disguised

• Create secondary data (translate tables, encryption exits etc.)

• Create Related, Associated, or Unrelated Disguise rules for each object and field to be disguised

• Test the disguise criteria with test extracts

• Refine the disguise criteria where necessary

• Verify disguised extract results using the File-AID Data Privacy Summary Report and Audit Trail
Report files

• Make the Disguise Control File available for regular File-AID/RDX users by adding it to their SITE
and/or USER profiles. Set RACF security 1 for the Disguise Control File so only authorized users
can make changes, and regular File-AID/RDX users can then use it to execute extract requests
with disguise or disguise already existing extract files.

Regular File-AID/RDX users should request either the File-AID/RDX profile name or the Disguise
Control File name from the Privacy or Security Administrator depending on their Profile Type (i.e.,
SITE, USER, or prefix).

Data Privacy Menu

Selecting Option 5, Data Privacy, from the File-AID/RDX Primary Option Menu displays the Data
Privacy Menu as shown in Figure 339.

If Dynamic Privacy Rules have been defined with the File-AID Data Privacy component of the Topaz
Workbench, you can disguise extracted data by specifying the Dynamic Privacy Rules Project.

Alternatively, you can define disguise criteria from within File-AID/RDX for the objects containing
sensitive data that you intend to extract and store the disguise information in the Disguise Control
File (DCF).

You can also disguise existing extracts which were created with this or earlier releases of File-
AID/RDX using the disguise information stored in the Disguise Control File (DCF).

For your initial disguise access, you must specify the File-AID/Data Solutions
parameters with Option 3, Parms, before selecting options 1 or 2.

The Data Privacy Menu also includes Data Privacy utilities that allow you to:

• Create Disguise Control File (DCF)

• Create Disguise Criteria File
• Print Disguise Control File
• Print Disguise Audit Trail File

1. The Privacy or Security Administrator, or anyone using option 5.1 (Create and Modify Disguise Criteria), requires UPDATE
or greater RACF authority to the Disguise Control File. A “Regular” File-AID/RDX user requires READ or greater RACF
authority to execute the disguise function in batch.
Data Privacy 609

Figure 339. Data Privacy Menu

File-AID/RDX ----------------- Data Privacy Menu -----------------------------

Option ===> Profile: RDXMENU 

Primary commands: menu-option

Dynamic Privacy Rules Options: 
P Privacy - DPR: Disguise Existing Extract File 

Data Disguise with DCF Options: 
Disguise Control File ===> 'TSOID01.FRSAMP.DISGUISE' 
1 Criteria - Create and Modify DCF Disguise Criteria 
2 Disguise - DCF: Disguise Existing Extract File 
3 Parms - File-AID/Data Solutions Parameters 
4 Control - Allocate Disguise Control File 
5 Criteria - Allocate Disguise Criteria File 
6 Validate - Validate/Update Disguise Control File 
7 Print Control - Print Disguise Control File 

Audit Trail Options: 
A Print Audit - Print Disguise Audit Trail 





The top of this screen consists of the following field:

USER Profile or SITE Profile

Displays the name of the current profile that provides the profile settings for this disguise extract
request. To change the profile, return to the File-AID/RDX Primary Option Menu.

Data Privacy Menu Options

Enter the option number (1 through 7) or letter (P or A) to select the desired option.

Dynamic Privacy Rules Options

P - Privacy
Select this option to disguise an existing extract file and apply the disguise criteria rules as
defined in the File-AID Data Privacy DPR: Dynamic Privacy Rules Project. File-AID/RDX displays
the DPR: Disguise Existing Extract panel (Figure 340 on page 612).

This option requires installation of Compuware’s File-AID/Data Solutions and File-AID Data
Privacy.

Data Disguise with DCF Options

The following options allow you to create data disguise criteria, apply the defined disguise criteria to
extracted data, and execute data disguise utilities.

Disguise Control File

Specify the name of the file that contains a list of objects that have related, associated, or
unrelated disguise criteria defined. File-AID/RDX then uses the information from the control file
to apply the disguise criteria when disguising an extract. If you specify a pattern, select a file from
the “Catalog Utility File List” (see Figure 121 on page 236).

If the file does not exist, use Option 4, Allocate Disguise Control File of the Data Privacy Menu to
allocate a new file (see Allocate Disguise Control File on page 670).
610 File-AID/RDX Reference

1 - Criteria
Select this option when you want to define or modify disguise criteria for objects to be extracted
and disguised. Creating a list of objects is always the first step in creating or modifying disguise
criteria. Use of the object list as the starting point for criteria creation is based on thinking that
criteria will be created for a specific set of objects and having the ability to view these objects
together would be helpful. An object list may contain both Db2 and MVS objects. Your current
profile variable determines which panel displays next, either the Extract Reference List for
Disguise on page 622, Request File Member List Screen on page 626, NEW - DB2 Object Filter on
page 628, or NEW - MVS Object Filter on page 630.

Before selecting this option make sure that you have set the correct File-
AID/Data Solutions parameters with Option 3, Parms, and that the Disguise
Control and Disguise Criteria files already exist. To allocate new Disguise
Control and Disguise Criteria files, use options 4- Control and 5- Criteria.

2 - Disguise
Select this option to disguise an existing extract file and apply the disguise criteria rules as
defined in the DCF: Disguise Control File. File-AID/RDX displays the Disguise Extract File panel
DCF: Disguise Existing Extract on page 665.

This option also allows you to disguise extract files that were created with an earlier version of
File-AID/RDX if you are using disguise criteria rules defined in the Disguise Control File (DCF).
The extract file must can be compressed (see also Compress on page 339), and can be a retained
extract file (see also Retain pre-disguise file on page 342).

It is possible to use a Disguise Control File with different Relationship Files as long as the set of
related objects being disguised has not changed. If there have been changes to the set of related
objects, the disguise rules will not be applied to any added relationships. No error checking will
be done at disguise execution time.

3 - Parms
Select this option to specify File-AID/Data Solutions parameters that File-AID/RDX uses to
properly connect to File-AID/Data Solutions, including:

– The Disguise Criteria File where File-AID/Data Solutions will store the actual disguise criteria
(necessary).
– The Dynamic Privacy Rules Project Name and Repository where File-AID Data Privacy will
store the actual privacy rules.
– The Business Rules dataset File-AID/Data Solutions uses when operating on date fields; it can
also be used by field exits (optional, only needed when applying business rules).

Options 4 through 7 are data disguise file utilities. Enter the option number to select the desired
utility:

4- Control
Displays the Allocate Disguise Control File panel where you can allocate a new Disguise Control
File (DCF). The File-AID/RDX disguise control file is required for the data disguise function and is
the repository that keeps track of all defined disguise criteria for each object.
Data Privacy 611

5- Criteria
Displays the Allocate Disguise Criteria File panel where you can allocate a new Disguise Criteria
File. This file is maintained by File-AID/Data Solutions and is the repository for all detailed
disguise criteria for File-AID/RDX extracts.

6- Validate
The Validate/Update Disguise Control File utility is no longer supported.

7 - Print Control
Displays the Print Disguise Control File panel where you specify to print the contents of the
disguise control file.

Audit Trail Options

When a disguise job using either disguise method (DPR or DCF) also created an audit trail for
each disguised object, you can print the audit trail reports.

A - Print Audit
Displays the Print Disguise Audit Trail panel where you specify to print the disguise audit trail
information for a disguised object.

DPR: Disguise Existing Extract

The DPR: Disguise Existing Extract screen shown in Figure 340 is displayed when you

• Select Option P, Privacy, from the Data Privacy Menu on page 608.

Use this screen to specify information required for the disguise operation using File-AID Data Privacy
Dynamic Privacy Rules, then enter GO to submit the batch job for disguise.

Hint
• Before you submit the disguise job, make sure that the Disguise Control File or the Dynamic
Privacy Rules Project includes the desired disguise criteria for the objects included in the extract
file.
612 File-AID/RDX Reference

Figure 340. DPR: Disguise Existing Extract

File-AID/RDX ------------ DPR: Disguise Existing Extract --------------------

COMMAND ===> 

Primary Commands: JCL view, GO to submit job 

Specify File Names: 
Extract File ===> EXTRACT.ORDVW25 
Member ===> (Blank or pattern for member list)

Disguised Extract File ===> DISGEXT.ORDVW25 
Member ===> (Blank or pattern for member list)
VOLSER ===> 
Disposition ===> NEW (NEW, OLD, SHR)

DPR: Repository Name ===> 
Project Name ===> 

Create Audit Trail ===> N ( Y = Yes; N = No) 
Audit Trail prefix ===> 

Enter the requested file information before viewing the JCL or submitting the disguise job with the
GO command directly:

Extract File
Specify the name of the Extract File that is to be disguised. The extract file can also be a
compressed extract file (see Compress on page 339).

If the Extract File is on tape, specify the name of the Extract Summary File instead of the name of
the Extract File on tape. The Extract Summary File was created when the generated extract was
saved to tape (see Specify Extract “TO” File Information on page 338). If your extract file on tape
was created with an earlier release of File-AID/RDX than 4.8, create a summary file as described in
Extract File Specification on page 419.

Only extract files created with File-AID/RDX Release 4.8 or higher can be disguised using
Dynamic Privacy Rules.

An Extract File cannot be disguised more than once.

When you had requested an extract with disguise and the disguise step of that extract failed, or
you had also set the option to save the pre-disguise records to a file in a masked format, you can
enter the name of the pre-disguise Extract File here as the extract file to be disguised. You find the
name of the pre-disguise file in the output of the extract job.

The name assigned to the pre-disguise extract file will use the standard File-AID/RDX routine to
generate a "temporary" name. The name will be the user prefix, the mid-level qualifier from the
Profile, the word "EXTRACT" and finally the current date and time fields (i.e. D120128.T055709).

Member
If the file you specified in Extract File is partitioned, you can enter a member name. If you leave
this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up containing a list
of members that match the specified pattern. The only valid pattern character is an asterisk (*).
Data Privacy 613

Disguised Extract File

Specify the name where the disguised extracted data is to be written. Make sure the size
allocation is at least the same as the size of the extract file to be disguised. See also Size Allocation
of Disguise Extract File on page 685.

When the specified disguised extract output is to tape or cartridge, File-AID/RDX automatically
creates a summary file on DASD. The name of the summary file is the one specified in your
profile or, if none is specified there, it is the name of the extract file with SUMMARY replacing
the last node of the extract file name or a truncated form of SUMMARY as to not exceed 44
characters. If the summary file exists, File-AID/RDX will update (overwrite) its content. Refer to
Extract Summary File on page 45 for more information.

Member
If the file you specified in Disguised Extract File is partitioned, you can enter a member name. If
you leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*). You can create new members by entering the name of the new member.

VOLSER
If the file specified in Disguised Extract File is non-cataloged or new, specify the volume serial
number of the file. For non-cataloged files, a volume serial number is required. For new files, a
volume serial number is optional.

Disposition
Specify the disposition of the disguise "to" file. You can extract to existing files with a disposition
of OLD. Existing files must conform to the format outlined for the extract file in File-AID/RDX
Extract File on page 377. Specify a disposition of NEW to create a new file.

If you specify NEW in the Disposition field, you must specify the following allocation
parameters in the Create New File screen (Figure 175 on page 334).

DPR: Repository Name

Specify the name of the Privacy Rules Repository to be used for this extract.

Specify the full repository name (up to 128 characters). Or enter an asterisk (*) by itself for a list
of all repositories. Then select the desired repository from the list (see Privacy Repository List on
page 74).

This field is prefilled with your current profile’s value (see DPR: Repository Name on page 73) or
global default value (see Option G—Global User Defaults).

Project Name
Specify the name of the Dynamic Privacy Rules Project to be used for this extract. Dynamic
Privacy Rules are created with the File-AID Data Privacy component of the Topaz Workbench. The
Dynamic Privacy Rules Project keeps track of how to apply the privacy rules to which extracted
data element.
614 File-AID/RDX Reference

Specify the full project name (up to 128 characters) or a pattern ending with an asterisk (*) for a
list of matching projects. Asterisk (*) by itself lists all projects. Then select the desired project
from the list (see Privacy Project List on page 74).

This field is prefilled with your current profile’s value (see DPR: Project Name on page 73).

The specified project must exist in the repository you specified in the DPR:
Repository Name field or the message 'Project not found' is
displayed.

Create Audit Trail

Specify whether an Audit Trail is to be created for each object being disguised. The Audit Trail will
contain the before and after images of each record that was disguised.

No. Audit Trail datasets will not be created.

Yes. File-AID/RDX creates a separate Audit Trail dataset for each disguised object. The naming
convention for each Audit Trail dataset (Audit Trail File on page 47) is

prefix.RDXA.DnnnBnnn.Dyymmdd.Thhmmss.Msss

Audit Trail file prefix

Specify the prefix to be assigned to the Audit Trail dataset names. Prefix plus USERID can be up to
14 positions, the remainder of the dataset name will follow the above mentioned naming
convention. If prefix is blank, only the USERID will be used. Any value specified will be appended
to the USERID. Precede the prefix value with a single quote (‘) to use the value without the
USERID.

Primary Commands
The following primary commands are valid:

GO
Submit the batch job for disguise.

JCL
View the JCL generated for the disguise job prior to submitting the job with the SUBMIT
command (see also View JCL on page 615).

1. When disguising an extract with File-AID Data Privacy defined Dynamic Privacy
Rules (DPR), specify a region size large enough to run Java (REGION=0M is
suggested, 200M is the minimum) in your jobcard. See also Disguise Extract File on
page 341, option 2, Use DPR.
2. The FARULES DD identifies the Privacy Rules Repository name and Dynamic Privacy
Rules Project ID. 
The FARULES DD may be allocated to a sequential file or a member of a PDS. The
record length must be fixed 80 bytes.
Data Privacy 615

View JCL
The ISPF/PDF Edit screen shown in Figure 341 on page 615 is displayed when you enter the JCL
command in the DPR: Disguise Existing Extract panel.

Figure 341. View File-AID/RDX generated JCL

EDIT - File-AID/RDX Generated SQL --------------------------- COLUMNS 000 000 

Command ===> SCROLL ===> CSR 
You are now editing the JCL that File-AID/RDX has generated to perform 
the required function. Change this JCL as desired before submitting. 
****** ***************************** Top of Data ******************************
==MSG> -Warning- The UNDO command is not available until you change 
==MSG> your edit profile using the command RECOVERY ON. 
000001 //TSOID01A JOB ('OFRBAS4.3',W06P02),'JOHN_SMITH', 
000002 // CLASS=L,MSGCLASS=R,NOTIFY=TSOID01 
000003 //* 
000004 //* XFRJDISG
000005 //* --------------------------------------------------------------------
000006 //* DATA DISGUISE STEP 
000007 //* --------------------------------------------------------------------
000008 //* 
000009 //EXDISG EXEC PGM=XFREXEC,REGION=0M,MEMLIMIT=4G, 
000010 // PARM=(FR,F,B) 
000011 //STEPLIB DD DSN=CPWR.MXVJ170.CXVJLOAD,DISP=SHR
000012 // DD DSN=CPWR.MXVJ170.SXVJLOAD,DISP=SHR 
000013 //* 
000014 //SYSPRINT DD SYSOUT=(*) 
000015 //SYSUDUMP DD SYSOUT=(*) 
000016 //SYSOUT DD SYSOUT=(*) 
000017 //XVJPRINT DD SYSOUT=(*) 

Use this screen to view or edit the JCL generated by File-AID/RDX to disguise an existing extract file
with predefined disguise criteria as specified in the Dynamic Privacy Rules Project. Use the SUBMIT
command to submit the extract request for execution. If you want to save this JCL, use the ISPF/PDF
CREATE or REPLACE command before you exit the panel.

XVJPRINT Execution Log Output

File-AID Data Privacy jobs now write execution information to XVJPRINT DD (instead of SYSPRINT
DD). If XVJPRINT DD does not exist in your JCL, File-AID will dynamically allocate XVJPRINT.

If you want the execution log output sent to a file, point XVJPRINT DD at a file (instead of
SYSOUT=*). This file must be allocated with RECFM=FBA, LRECL=133.

Optional Data Privacy Report Output Written to a File

If you want the Data Privacy Report information written to a fixed layout sequential file and/or to a
CSV (Comma Separated Values) file, manually add the appropriate DD statement to the File-AID Data
Privacy job.

1. When disguising multiple objects, the disposition of the file pointed at by

DPRSTAT1 or DPRSTAT2 must be "MOD". If it is "OLD", only the columns of the
last object will be found in the file.
2. This functionality requires File-AID Data Privacy Release 17.2.3 or newer.

DPRSTAT1 DD (Fixed Layout Sequential File)

When you add a DPRSTAT1 DD to a File-AID Data Privacy job and it points at a file defined as
RECFM=FB,LRECL=2737, at end of job, the file will have the report information for each column
written out as a single record containing all the same report information but in a formatted fixed
layout sequential file.

Example:
616 File-AID/RDX Reference

//DPRSTAT1 DD DSN=fixed_layout_sequential_file, 
// DISP=MOD

or for a new file:

//DPRSTAT1 DD DSN=fixed_layout_sequential_file, 
// DCB=(RECFM=FB,LRECL=2737,DSORG=PS), 
// SPACE=(TRK,(1,2),RLSE), 
// UNIT=SYSDA, 
// DISP=(NEW,CATLG,CATLG)

Record Layout for Output File

To view the output file in formatted mode you can use File-AID/MVS Browse or Edit with the
following COBOL record layout describing a record in the output file:

01 DPR-STATISTICS. 
15 DPR-COLUMN-NUMBER PIC 9(9) COMP.
15 DPR-NUMBER-CHANGED PIC 9(9) COMP.
15 DPR-NUMBER-INVALID PIC 9(9) COMP.
15 DPR-COLUMN-NAME PIC X(128). 
15 DPR-RULE-NAME PIC X(512). 
15 DPR-RULE-DESCRIPTION PIC X(512). 
15 DPR-LAYOUT PIC X(1573).

DPRSTAT2 DD (CSV)
When you add a DPRSTAT2 DD to a File-AID Data Privacy job and it points at a CSV (Comma
Separated Values) file defined as RECFM=VB,LRECL=2751, at end of job, the file will have the report
information for each column written out as a single record containing all the same report
information but they will be Comma Separated Value (CSV) records.

Example:

//DPRSTAT2 DD DSN=CSV_file, 
// DISP=MOD

or for a new file:

//DPRSTAT2 DD DSN=CSV_file, 
// DCB=(RECFM=VB,LRECL=2751,DSORG=PS), 
// SPACE=(TRK,(1,2),RLSE), 
// UNIT=SYSDA, 
// DISP=(NEW,CATLG,CATLG)

Optional Source Data Identifiers (SDIs) Override During Execution

File-AID/RDX now allows you to replace, during execution of a DPR project, Source Data Identifiers
(SDIs) defined in the File-AID Data Privacy project.

To override SDIs, manually add the following DD statement to the JCL:

//DPRSDI DD DISP=SHR,DSN=u.data.mysdis

where the existing dataset u.data.mysdis contains the definitions of SDIs that will be used for this
execution.

If the DPRSDI DD is defined in JCL, all SDIs defined in the project will be ignored and replaced with
definitions provided in the override dataset.

If the specified override file does not exist, Message UNABLE TO OPEN
DPRSDI FILE is issued and processing stops with a RC=8.
Data Privacy 617

Override File Format

Replacement SDIs can be defined either in XML or in JSON format. The tags in XML and names in
name/value pairs in JSON correspond to SDI properties that can be defined through the Compuware
Workbench User Interface. Refer to the Source Data Identifier Overrides topic in the Compuware Workbench
File-AID Data Privacy User Guide for more information.

Override Data Privacy Environment Parameters

If you need to, you can override the Data Privacy Environment parameters listed in Table 75
(established with your site’s File-AID Data Privacy Environment parameters (refer to File-AID Data
Privacy Environment in the File-AID Advanced Configuration Guide).

Table 75. Data Privacy Environment Parameter Overrides

Parameter DD statement
JAVA_VIRTUAL_MACHINE_PATH 
FAJPATH
(z/OS UNIX Path Name for Java Virtual Machine (JVM))
JAVAOPNn
FAJOPTS
(Java (JVM) Options)
FILEAID_SERVICES_USER_EXECUTION_PORT
FAIPADDR
(File-AID Data Privacy IP address and execution port)
FILEAID_RULES_ENGINE_PATH
(z/OS UNIX Path Name for File-AID Rules Engine (FARE), FAEXPATH
formerly Common Disguise Engine (CDE))

To do so, insert any of these FAJPATH, FAJOPTS, FAIPADDR, and FAEXPATH DD statements as needed.
For example:

//FAIPADDR DD * 
127.372.322.101:4180
/* 
//FAJPATH DD * 
/usr/lpp/java/J7.1_64.bld111513/
/*

It is also possible to specify more than one debug parameter inline. For example:

//FADEBUG DD *
Level=FINER 
Filename=/u/userid/
/*

Override Execution Parameter in a Data Privacy Project

In order to override an execution parameter (public variable or translate table) in a Data Privacy
Project, add a DPRPARMS DD statement to your JCL. This DD can point to a file or a PDS member
containing the override values (maximum record length is 512 bytes). The override values can also be
specified inline. Specify override values in the following way:

executionParm=overrideValue

The execution parameter must have been defined in the Topaz Workbench user interface for the
project.

Example:
Your DPR project ‘project1’ includes:

• 2 translate tables, ‘Title table’ and ‘Titles for HR dept’ (Figure 342)

– The source table for ‘Title table’ is file ‘ABC.TRANS’.

618 File-AID/RDX Reference

• 2 public variables, ‘scramvar’ and ‘altscram‘ (Figure 343 on page 618)

– The initial value for ‘scramvar’ is string ‘123abc’.

• 2 execution parameters, ‘Parameter1’ identifies the translate table ‘Title table’ and
‘Param2Variable’ identifies variable ‘scramvar’ (Figure 344 on page 619).

At execution time, however, you want to override the defined execution parameters for translate
table ‘Title table’ with the new translate table ‘ABC.NEWTRANS’ and the initial value of variable
‘altscram‘ with the new string ‘789xyz’. The new translate table must have the same characteristics as
the original one.

To do so, insert the following DPRPARMS DD statement in the JCL (inline example):

//DPRPARMS DD * 
Parameter1=ABC. NEWTRANS
Param2Variable=789xyz
/*

Figure 342. Manage Translate Tables

Figure 343. Process Variables

Data Privacy 619

Figure 344. Manage Execution Parameters

Execution Parameter List of Values

If the execution parameter variable type is either a String List or Numeric List, you can also override
the list of values.

Specify a list of values in the following way:

executionParm=LIST(X)=overrideValueXoverrideValueXoverrideValue

The X variable inside the =LIST( )= parentheses defines the delimiter for the list of values. The
delimiter can be any character. Connect each overridevalue with the defined delimiter.

For example, insert the following DPRPARMS DD statement in the JCL (inline example) to override
the values of the String List named STATE (* is the defined delimiter):

//DPRPARMS DD * 
STATE=LIST(*)=MI*OH*RI*CA*MO*IN
/*

Multiple Origins for a Data Privacy Rule

Normally, when a Data Privacy Rule is applied to a related field, one object 1 in the relationship
thread is chosen as the “origin”. For every record in the origin, the Data Privacy Rule is applied to the
related field and the BEFORE and AFTER values are saved. For every record in a “non-origin”, the Data
Privacy Rule is not applied. Rather, the appropriate AFTER value is retrieved from where it was saved.
This guarantees relationship integrity.

This methodology is efficient and sufficient in most scenarios, but there are some scenarios where no
single origin contains all of the values required by the non-origins. When this occurs, it is possible to
direct File-AID to use all objects that contain the necessary fields referenced by the Data Privacy Rule
as origins. This directive is specified by adding to your JCL:

1. An object is a Db2 table, an MVS file, or an IMS segment.

620 File-AID/RDX Reference

//MULTISRC DD DUMMY

The use of multiple origins degrades job execution performance, so it is not

recommended as a default behavior.

Special Instructions for Oracle Translate Table

If your Data Privacy job uses Data Translation with an Oracle Translate Table and your File-AID Data
Privacy Environment parameters do not include the following JAVA options (refer to File-AID Data
Privacy Environment in the File-AID Advanced Configuration Guide), insert the following FAJOPTS DD
statement after the FARULES DD statement:

//FAJOPTS DD * 
-verbose:sizes
-Dfile.encoding=UTF-8
-Dlog.encoding=IBM1047

If the JAVA options in the File-AID Data Privacy Environment parameters include other site specific
JAVA options, also add them to the FAJOPTS DD statement before submitting the job.

Adding the above FAJOPTS DD statement will override the JAVA options in the File-AID Data Privacy
Environment parameters and make it possible to run an Oracle translation while the log will be
generated in EBCDIC.

An indicator that you need to make this JCL change is when the Data Privacy job ended with the
following error:

Method execPrivacyRules failed (RC=8) at line nnn in file EXECDPR.C.

However, this general message is not conclusive. Your error log file should have something like the
following:

Throwable occurred: java.sql.SQLException: Internal - Unexpected value 

at oracle.jdbc.driver.T4CTTIoauthenticate.processRPA(T4CTTIoauthenticate.java:516) 
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:295) 
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) 
at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate.java:390) 
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:356) 
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:531) 
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:221) 
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32) 
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:503) 
at java.sql.DriverManager.getConnection(DriverManager.java:322) 
at java.sql.DriverManager.getConnection(DriverManager.java:358) 

If you see the above, then you need to insert the FAJOPTS DD statement.

Set Incomplete Disguise Continuation Indicator

When during the disguise process of an object, File-AID/RDX cannot disguise some records
completely, File-AID/RDX, by default, issues a warning and removes these records from the disguised
extract file. The resulting extract file might not be loadable or usable. Possible reasons for the
incomplete disguise could be:

• Two related columns have unlike data types; error may be due to non-normalized data

• Error may be due to childless parents and/or orphans in your database

The disguise audit file for the object contains the before image for the offending records. Print it (see
Print Disguise Audit Trail on page 679) so you can determine whether the discarded records are
needed in your extract file.

The TEST parameter for the disguise (EXDISG) EXEC statement in the EXTPARMS dataset (see
EXTPARMS File on page 367) can be used to change the default behavior. When you set the parameter
Data Privacy 621

to Y, File-AID/RDX will issue a fatal error (RC=8) for this object instead of just discarding the
incomplete disguise records. When set to N, File-AID/RDX will issue warning messages for incomplete
disguise (RC=6) for an object, but continue disguise of object.

Control Card Cleanup

The last step, CLEANEXT, in the disguise jobs deletes the File-AID/RDX EXTPARMS parameter file.
Whether step CLEANEXT is commented out or executed is determined by the global job option
Delete in-stream data datasets at EOJ (page 83). If the job option is set to NO, File-AID/RDX
EXTPARMS parameter files created in the extract jobs will NOT be deleted. Keeping the datasets until
all steps run successfully allows for the restarting of the JCL at any step.

Periodically, you may want to manually delete the EXTPARMS parameter files that are no longer
needed for saved jobs to be resubmitted.

Extract Reference List for Disguise

The Extract Reference List for Disguise screen shown in Figure 345 is displayed when you

• Select Option 1, Criteria, from the Data Privacy Menu on page 608 and your profile set it as the
first Data Privacy panel (see also First Disguise panel on page 74);
or
• Enter the REFerence command on the Request File Member List Screen.

The Extract Reference List for Disguise lists the same extract requests as the Extract Reference List
described on page 213.

If your reference list is empty, File-AID/RDX will display the Request File
Member List screen, listing the members of the request file specified in your
profile, or if none is in your profile, display either the NEW - DB2 Object Filter
or NEW - MVS Object Filter screen so you can create a new object list.

Refer to Option G—Global User Defaults on page 82 for how to set the maximum number of list
entries for the reference list.

Creating a list of objects is the first step in creating or modifying disguise criteria. Use of the object
list as the starting point for criteria creation is based on thinking that criteria will be created for a
specific set of objects and having the ability to view these objects together would be helpful. An
object list may contain both Db2 and MVS objects.

You create an initial disguise object list either by creating a NEW list with the NEW command, or
extracting the objects from an extract request you select from the Extract Reference List for Disguise,
or open a saved extract request file with the REQUEST command. Use the REQUEST command to
open extract criteria files created with File-AID/RDX prior to Release 3.0.

You may specify multiple line commands at a time. All line commands are processed before any
primary commands. When processing multiple commands File-AID/RDX displays a message like
“Processing line command 2 of 4” whenever it starts processing the next line command after the first.
622 File-AID/RDX Reference

Figure 345. Extract Reference List for Disguise

File-AID/RDX ----- Extract Reference List for Disguise -- Row 1 to 6 of 6 

Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: S = Select
I = Info D = Delete from list L = Lock U = Unlock

Request Extract File Name RT L YY/MM/DD
-------- ----------------------------------------------------- -- - -------- 
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT E 04/02/18
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM E 04/02/04
_ TSOID01.FRSAMP.EXTRACT EL L 04/02/01
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT E 04/01/31
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2(EXTCUST) EL L 03/12/24
_ MVORDR TSOID01.FRSAMP.EXTRACT.ORDEER E 03/08/24
******************************* Bottom of data ********************************

The lower part of the screen displays a listing of your recently referenced extract requests. Use the
line commands to manage the list.

Request
Name of the extract request (member name in the saved extract request file or extract criteria
file). A blank entry means the request was saved to a sequential file.

Extract File Name

Name of the file containing the extracted data. If saved to a PDS the member name is displayed in
parentheses.

RT
Request Type. Identifies the extract request type:

Extract only request.

EL

Extract and Continue with Load request.

L
Locked Entry. Identifies whether the request is locked in the reference list or whether it is
allowed to roll off.

blank

not protected from roll over.

Locked in reference list; entry will not roll off the list.
Data Privacy 623

YY/MM/DD
Date when the extract request was last saved or executed. The list entries are ordered with the
most recent date placed on top of the list.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

D (Delete from list)

Removes this extract request from the extract reference list, but does not delete the member from
the extract request file itself.

I (Info)
Displays the Request Details screen, which provides more comprehensive information about the
extract request. See Figure 346 for an example.

Figure 346. Request Details

File-AID/RDX ---------------- Request Details -------------------------------

Command ===>

Request Information: 
Request File Name . : TSOID01.FRSAMP.REQUEST 
Member Name . . . . : MVSSAMP 
Request Type . . . . : EXTRACT 
Description . . . . : MVS 
Reference Date . . . : 2011/01/03 Reference Time: 00:00:07 

Driving Object Information: 
SSID . . . . . . . . : 
Name . . . . . . . . : MVS - TSOID01.FRSAMP.ORDERTAB 

Extract Information: 
Extract File Name . : TSOID01.FRSAMP.OUT 
Summary File Name . : TSOID01.FRSAMP.TAPECNTL 
Disguise Control File: 
Repository Name: 
Project Name: 
Extract Date . . . . : 2011/01/03 Extract Time : 12:00:01 

Relationship Information: 
File Name . . . . . : TSOID01.FRSAMP.RELATION 

L (Lock)
Protects this entry from rolling off the extract reference list.

S (Select)
Selects this extract request and adds all non-excluded objects of the request to the initial disguise
object list. Objects excluded from the extract request will not be added to the object list.

U (Unlock)
Does not protect this entry from rolling off the extract reference list.
624 File-AID/RDX Reference

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

DETAIL (D)
Expands the one-line display for each request into a two-line display. The additional line shows
the request description. See Figure 347 for an example. Detail is a toggle switch so enter Detail
again to return to the original format.

Figure 347. Extract Reference List - DETAIL Screen

File-AID/RDX ----- Extract Reference List for Disguise -- Row 1 to 6 of 6 


Command ===> Scroll ===> CSR 

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: S = Select
I = Info D = Delete from list L = Lock U = Unlock

Request Extract File Name RT L YY/MM/DD
-------- ----------------------------------------------------- -- - --------
_ MVSSAMP TSOID01.FRSAMP.EXTRACT E 11/01/03
Description: MVS 
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT E 04/02/18
Description: This extract uses Acct number 
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM E 04/02/04
Description: DB2-FR.PRODUCT_CONTRACT 
_ TSOID01.FRSAMP.EXTRACT EL L 04/02/01
Description: This extract selects region 10 
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT E 04/01/31
Description: MVS-FRSAMP.CUSTOMER 
_ MVORDR TSOID01.FRSAMP.EXTRACT.ORDER E 99/08/24
Description: MVS-FRSAMP.ORDER 
******************************* Bottom of data ********************************

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.

Find looks for matches in the request detail information for each list entry. When a match is
found and is not visible in the displayed row, use the I (info) line command to display the detail
information.

NEW (N)
Starts a new object list based on your current profile. File-AID/RDX displays either the Db2 or
MVS Object Filter screen as set in your profile (see Figure 353 or Figure 354).

You can also include one of the optional parameters, DB2 or MVS, to display the respective New
Object Filter screen.

REQUEST (REQ)
Opens a saved extract request file. You also use the REQuest command to open extract criteria
files created with File-AID/RDX prior to Release 3.0. Refer to Figure 349 for more information.

File-AID/RDX opens the request file specified in your current profile or prompts for the file name
when none is in your profile.
Data Privacy 625

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 348 for an example. Size is a toggle switch, so enter Size again to return to the
original format.

Figure 348. Extract Reference List - Size Screen

File-AID/RDX ------------- Extract Reference List --------- Row 1 to 6 of 6

Command ===> SCROLL ===> CSR 
Request Extract File Name RT L YY/MM/DD
_ MVSSAMP TSOID01.FRSAMP.REQUEST E 11/01/03
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT E 04/02/18
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM E 04/02/04
_ TSOID01.FRSAMP.EXTRACT EL L 04/02/01
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT E 04/01/31
_ DIEBLD TSOID01.FRSAMP.CUST.EXTRACT.NODB2(EXTCUST) EL L 03/12/24
_ MVORDR TSOID01.FRSAMP.EXTRACT.ORDEER E 03/08/24
****************************** Bottom of data ********************************

Request File Member List

The Request File Member List Screen shown in Figure 349 is displayed when you

• Select Option 1, Criteria, from the Data Privacy Menu and your profile set the Request File
Member List as the first disguise panel (see also First Disguise panel on page 74);
or
• Enter the REQuest command on the Extract Reference List for Disguise panel

The Request File Member List Screen lists the same extract requests as the Request File Member List -
Size Screen described on page 221.

File-AID/RDX also displays the Request File Member List screen, when your
profile lists the Extract Reference List for Disguise as the first disguise panel,
but the list is empty and your profile includes an extract request file.

Creating a list of objects is the first step in creating or modifying disguise criteria. Use of the object
list as the starting point for criteria creation is based on thinking that criteria will be created for a
specific set of objects and having the ability to view these objects together would be helpful. An
object list may contain both Db2 and MVS objects.

You create an initial disguise object list either by creating a NEW list with the NEW command, or
extracting the objects from an extract request you select from the Request File Member List or from
an extract request off the Extract Reference List for Disguise (REFERENCE command).

This screen displays the member list of a saved extract request file or an extract criteria file created
with File-AID/RDX prior to Release 3.0. Use the S line commands to select an extract request and add
all of its objects to the initial object list.
626 File-AID/RDX Reference

Figure 349. Request File Member List Screen

File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8

Command ===> Scroll ===> CSR

Primary commands: New, Find, Size, REFerence
Line commands: S = Select, D = Delete R = Rename
Request File ===> FRSAMP.EXTCRIT 

Member Description Changed
-------- -------------------------------------------------- ---------- 
_ DB2VSAM db2 to vsam extract 2004/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 2004/08/13 
_ MIKE1 Member List 2004/05/10 
_ NODB2 mcust with db2 deleted 2004/01/25 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 2004/08/30
_ PART1 Member List 2003/02/11
_ SELCUST test select customer 2002/01/28 
_ TESTA test saving the criteria 2001/04/12
******************************* Bottom of data ********************************

Request File
The request file name comes from your current profile. If your profile does not include a request
file, File-AID/RDX will prompt for one. Enter a new file name to change to a different saved
request file or extract criteria file and File-AID/RDX will display its member list.

Clear the field and File-AID/RDX displays the Extract Reference List for Disguise (page 622).

The lower part of the screen displays a listing of the file’s members.

Member
Member name in the saved extract request file or extract criteria file. The member names are
displayed in alphabetical order.

Description
Text that was entered in the Description field when the extract request was created. If you left the
field blank, File-AID/RDX sets the description to the driving object type and name.

Changed
Date when the member was last saved.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

D (Delete)
Delete this member from the request file. Displays the Delete Confirmation window (Figure 350).
Data Privacy 627

Figure 350. Delete Confirmation window

Delete Confirmation 
COMMAND ===> 

Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 

Member to be Deleted: TESTA 


ENTER to confirm delete 
END to return to Request File Member List 



R (Rename)
Rename the request member. The Rename Confirmation window (Figure 351) allows you to enter
a new name for the request file member.

Figure 351. Rename Confirmation window

Rename Confirmation 
COMMAND ===> 

Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’ 

Member to be Renamed: TESTA 
New Member name ===> 


ENTER to confirm rename 
END to return to Request File Member List 



S (Select)
Selects this extract request and adds all objects included in the request to the initial disguise
object list.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

FIND (F)
Searches the member list for the specified string and scrolls the list to display the first matching
entry at the top of the displayed entries. Use RFind to repeat the search.

NEW (N))
Starts a new object list based on your current profile. File-AID/RDX displays either the DB2 or
MVS Object screen as set in your profile (see Figure 353 or Figure 354).

You can also include one of the optional parameters, DB2 or MVS, to display the respective New
Object Filter screen.

REFERENCE (REF)
Displays your Extract Reference List panel. Refer to Figure 345 on page 622 for more information.
628 File-AID/RDX Reference

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 352 for an example. Size is a toggle switch so enter Size again to return to the
original format.

Figure 352. Request File Member List - Size Screen

File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8 

Command ===> Scroll ===> CSR
Member Description Changed
_ DB2VSAM db2 to vsam extract 2001/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 2001/08/13 
_ MIKE1 Member List 2002/05/10 
_ NODB2 mcust with db2 deleted 2001/01/25 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 2001/08/30
_ PART1 Member List 2002/02/11
_ SELCUST test select customer 1999/01/28 
_ TESTA test saving the criteria 2001/04/12
******************************* Bottom of data ********************************

NEW - DB2 Object Filter

The NEW - DB2 Object Filter screen shown in Figure 353 is displayed when you

• Select Option 1, Criteria, from the Data Privacy Menu and your profile set the New - DB2 Object
Filter as the first disguise panel (see also Default NEW object type and First Disguise panel on
page 74);
or
• Enter the NEW command in the Extract Reference List for Disguise or the Request File Member
List screens and your profile specifies that the NEW object type is a Db2 object, or you enter the
DB2 command in the NEW - MVS Object Filter screen.

Use this screen to specify a Db2 object filter to add Db2 objects to your initial object list.

Figure 353. NEW - DB2 Object Filter

File-AID/RDX ------------- NEW - DB2 Object Filter --------------------------

-----
Command ===> 

Primary commands: MVS object filter

DB2 Objects Filter: 
SSID ===> DSN 
Location ===> (* or pattern for selection list)
Creator ===> FRSAMP (* or pattern for selection list)
Table Name ===> * (* or pattern for selection list)

Object List Content:
Object source ===> R (C = MVS Catalog; R = Relationship File)
Relationship File . .: FRSAMP.RELATION 




After entering the information for the new DB2 object filter, press ENTER to proceed to the ObjectIn
Preview.
Data Privacy 629

DB2 Objects Filter Area

Use the fields in this area to specify the Db2 objects to be included in your initial object list for
specifying disguise criteria. When specifying patterns in the fields, File-AID/RDX searches the Db2
catalog and/or the relationship file to find matches.

SSID
Displays the current Db2 subsystem ID. Type over this field to connect to a new Db2 subsystem.
If you leave the Location field blank, the objects you specify must exist in the Db2 subsystem
displayed here.

Location
Specify the location of the objects you want to include in the object list if it resides in a remote
Db2 subsystem. The location you enter must be defined in the Db2 system catalog table,
SYSIBM.LOCATIONS.

Leave this field blank if the objects you want included are in the Db2 subsystem in the SSID field.

Creator
Specify the authorization ID of the owner of the objects that you want to include in the object
list. Enter a pattern in this field if you want to include objects from more than one creator. Valid
pattern characters are %, _, and * (see Pattern Characters on page 27).

Table Name
Specify a pattern for the object names you want to include in the object list. Valid pattern
characters are %, _, and * (see Pattern Characters on page 27).

Object List Content:

Object Source
Specify whether to search for matching objects to be added to the initial object list in the
relationship file or in the Db2 catalog.

Catalog. File-AID/RDX searches the Db2 catalog to find matching objects.

Relationship. File-AID/RDX searches only the relationship file to find matching objects.

Relationship File
Specify the name of the file that contains the referential integrity and application relationship
information you want to use for the object list. In the object list, File-AID/RDX identifies related
objects based only on the relationship definition found in the relationship file.

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:
630 File-AID/RDX Reference

MVS (M)
Switches to the NEW - MVS Object Filter panel prefilled with the applicable information from
your profile. Refer to NEW - MVS Object Filter on page 630.

NEW - MVS Object Filter

The NEW - MVS Object Filter screen shown in Figure 354 is displayed when you

• Select Option 1, Criteria, from the Data Privacy Menu and your profile set the New - MVS Object
Filter as the first disguise panel (see also Default NEW object type and First Disguise panel on
page 74);
or
• Enter the NEW command in the Extract Reference List for Disguise or the Request File Member
List screens and your profile specifies that the NEW object type an MVS file, or you enter the
MVS command in the NEW - DB2 Object Filter screen.

Use this screen to specify a MVS object filter to add MVS objects to your initial object list.

Figure 354. NEW - MVS Object Filter

File-AID/RDX ---------- NEW - MVS Object Filter -----------------------------

--
Command ===> 

Primary commands: DB2 

MVS Objects Filter: (* or pattern for selection list)
File name ===> FRSAMP.*

OPTIONAL Additional filters for MVS Objects in the Relationship File: 
Record layout usage ===> (S = Single; X = XREF;)
Record layout file ===> 
Member name ===> 
XREF file ===> 
Member name ===> 

Object List Content:
Object source ===> R (C = MVS Catalog; R = Relationship File)
Relationship File ===> FRSAMP.RELATION 


After entering MVS object filter information, press ENTER to proceed to the ObjectIn Preview.

MVS Objects Filter Area

Specify a pattern for the MVS objects to be included in your initial object list for specifying disguise
criteria. When specifying patterns in the fields, File-AID/RDX searches the MVS catalog and/or the
relationship file to find matches.

File name
Specify the MVS file name pattern for the objects you want to add to the object list. Valid pattern
character is * (see Pattern Characters on page 27).
Data Privacy 631

OPTIONAL Additional filters for MVS Objects in the Relationship File Area
The following fields are only needed when you want to use the single or XREF record layout
information as additional filters for MVS files to be searched in the relationship file (Object
Source=R). When searching the MVS catalog the record layout fields are ignored.

Record layout usage

Indicate whether a single record layout (usage "S"), or an XREF (usage "X") had been used to
define the selection criteria. Only needed when specifying record layout information as
additional filters.

Record layout file

Specify the record layout file for the MVS object(s) you want to add to the object list. To view a
list of layout files, specify a pattern. Valid pattern character is * (see Pattern Characters on page
27). If you specify a pattern, select a file from the “Catalog Utility File List” as shown in Figure
364 on page 640.

Member name
Specify the member of the record layout file that contains the layout information for the MVS
object. Leave blank or use a pattern to narrow the search.

XREF file
Only used as filter when layout usage is X. Specify the XREF file name for the MVS object(s) you
want to add to the object list. Valid pattern character is * (see Pattern Characters on page 27). If
you specify a pattern, select a file from the “Catalog Utility File List” as shown in Figure 364 on
page 640.

Member name
Specify the member of the XREF file that contains the layout information for the MVS object(s).
Leave blank or use a pattern to narrow the search, see also Figure 366 on page 642.

Object List Content:

Object Source
Specify whether to search for matching objects to be added to the initial object list in the
relationship file or in the MVS catalog.

Catalog. File-AID/RDX searches the MVS catalog to find matching objects.

Relationship. File-AID/RDX searches only the relationship file to find matching objects.
632 File-AID/RDX Reference

Relationship File
Specify the name of the file that contains the referential integrity and application relationship
information you want to use for the object list. In the object list, File-AID/RDX identifies related
objects based only on the relationship definition found in the relationship file.

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:

DB2 (D)
Switches to the NEW - DB2 Object Filter panel prefilled with the applicable information from
your profile. Refer to NEW - DB2 Object Filter on page 628.

ObjectIn Preview
The ObjectIn Preview window shown in Figure 355 is displayed any time after you press Enter on
either NEW - DB2 Object Filter or the NEW - MVS Object Filter screens. It displays the results of your
object filter search and allows you to select all, none, or individual objects to be included in your
initial object list.

Use this preview to select only those objects you want to include.

Figure 355. ObjectIn Preview

Fi ObjectIn Preview -------- 

Co Command ===> Row 1 to 2 of 2 
SCROLL ===> PAGE 
Pr Primary Commands: ALL, Find 
Line Commands: S = Select 
D 
Object Name n list) 
----------------------------------------------- 
_ FRSAMP.ORDER_LINE_TABLE 
_ FRSAMP.ORDER_TABLE 
******************* Bottom of data ******************** 
O 













After selecting all desired objects to be included in the object list, press END to proceed to the Data
Disguise - Object List. If you press END without selecting any objects, you proceed to an empty Data
Disguise - Object List.

Object Name
Identifies the name of the objects that match the specified object filter.
Data Privacy 633

Line Commands
The following File-AID/RDX-specific line command is valid:

S (Select)
Selects and marks this object to be included in the object list. Blank out the S marker for
individual objects you don’t want included in the object list. Use in conjunction with the ALL
primary command to mark your selections.

Primary Commands
The following File-AID/RDX-specific primary commands are valid:

ALL
Selects and marks all objects listed in the preview to be included in the object list. Blank out the
S marker for individual objects you don’t want included in the object list. Use in conjunction
with the S line command to mark your selections.

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.

Data Disguise - Object List

The Data Disguise - Object List screen shown in Figure 356 is displayed when you select an existing
request from the Extract Reference List for Disguise or the Request File Member List Screen to build
the object list or press END on the ObjectIn Preview window when you create a new object list after
selecting Option 1, Create and Modify criteria from the Data Privacy Menu.

This screen displays the list of the objects, in alphabetical order, that have been filtered into the
Object List. From this list you select an object in order to create or modify disguise criteria for the
object. Disguise criteria are defined for an object and will be applied whenever that object is extracted
and disguise is requested for the extract file.

Figure 356. Data Disguise - Object List

File-AID/RDX ----------- Data Disguise - Object List ------- Row 1 to 7 of 7 

Command ===> Scroll ===> CSR 

Primary Commands: ObjectIn, ObjectOut, Find, Size 
Line Commands: S = Select I = Info 
O = ObjectOut R = Related objects L = List DB 

SSID: D701 Location: D701CW01 
Object Name Disguised Columns/Fields +
-------------------------------------------- --------------------------------
_ DSN8710.ACT 
_ DSN8710.DEPT 
_ DSN8710.EMP 
_ DSN8710.EMPPROJACT 
_ DSN8710.PROJ 
_ DSN8710.PROJACT 
_ ‘TSOID01.FASAMP.EMPMAST’ 
******************************* Bottom of data ********************************

634 File-AID/RDX Reference

After selecting all desired objects to be included in the object list, press END to proceed to the Data
Disguise - Column/Field List.

Object Name
Identifies the name of the objects that match the specified object filter.

Disguised Columns/Fields
Displays the names of the columns and fields with disguise criteria defined. This field is a
scrollable field so the entire contents of the field may not be displayed in the area allowed.
Position the cursor on the field and enter the EXPAND command to view the entire field
contents.

Line Commands
The following File-AID/RDX-specific line command is valid:

S (Select)
Selects this object for data disguise and displays the Data Disguise - Column/Field List. If the
selected object is an MVS file for which File-AID/RDX does not have any record layout
information, File-AID/RDX displays the “MVS XREF/Record Layout” window where you must
specify the applicable record layout information.

I (Info)
Displays the Disguised Columns/Fields for each object. Figure 357 displays the disguised
columns/fields with the disguise rule and disguise description for the selected object. The
Disguise Rule field is scrollable, use LEFT and RIGHT commands to view the remainder of the
description field.

Figure 357. Disguised Columns Information

File-AID/RDX ------------- Disguised Columns --------------- Row 1 to 2 of 2 

Command ===> Scroll ===> CSR 

Disguise Object: FRSAMP.ORDER_LINE_TABLE 

Column/Field Disguise Rule + 
------------------------------- ---------------------------------------------- 
START_DATE U0000002 UNRELATED FRSAMP.ORDER_LINE_TABLE 
ORDER_NUM R0000005 RELATED ORDER_NUM:FRSAMP.ORDER_LINE_TA
******************************* Bottom of data ********************************

O (ObjectOut)
Removes this object from the object list.

R (Related objects)
Searches the relationship file and displays any related objects that are not yet included in the
object list (see Figure 358). Then you can select any of the related objects to be added to the
object list.
Data Privacy 635

Figure 358. Related ObjectIn Preview

Fi Related ObjectIn Preview w 1 to 10 of 10 

Co Row 1 to 3 of 3 croll ===> CSR 
Command ===> SCROLL ===> PAGE 
Pr Primary Commands: ALL, Find 
Line Commands: S = Select 
DB 
Object Name 
----------------------------------------------- 
_ FRSAMP.CUSTOMER_TABLE s/Fields +
_ FRSAMP.ORDER_TABLE ----------------
_ _ FRSAMP.PART_TABLE 
_ ******************* Bottom of data ******************** 
R NUM

L (List DB)
Lists all objects that are in the same database as this object and are not already in the Object List
(see Figure 359). Then you can select any of the objects to be added to the object list.

Figure 359. Database ObjectIn Preview

Fi Database ObjectIn Preview w 1 to 10 of 10 

Co Row 1 to 3 of 3 croll ===> CSR 
Command ===> SCROLL ===> PAGE 
Pr Primary Commands: ALL, Find 
Line Commands: S = Select 
DB 
Object Name 
----------------------------------------------- 
_ IFHALC0.JASON s/Fields +
_ IFHALC0.MY_TABLE ----------------
_ _ FRSAMP9.PART_TABLE 
_ ******************* Bottom of data ******************** 

Primary Commands
The following File-AID/RDX-specific primary commands are valid:

OBJECTIN (OI)
Allows you to add objects to your current object list. This command displays either the “ObjectIn
- DB2 Object Filter” or “ObjectIn - MVS Object Filter” screen. The ObjectIn Filter panels work the
same as the NEW - DB2 Object Filter (Figure 353 on page 628) and NEW - MVS Object Filter
(Figure 354 on page 630) with the exception that the relationship file, Db2 SSID and Db2
Location fields are protected.

OBJECTOUT (OO)
Allows you to remove objects from your current object list. This command displays either the
ObjectOut - DB2 Object Filter (Figure 360 on page 636) or “Object-Out - MVS Object Filter”
screen (Figure 354 on page 630).

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.
636 File-AID/RDX Reference

SIZE (SI)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. SIze is a toggle switch so enter SIze again to return to the original format.

ObjectOut - DB2 Object Filter

The ObjectOut - DB2 Object Filter screen shown in Figure 360 is displayed when you enter the OO
command in the Data Disguise - Object List, or you enter the DB2 command in the ObjectOut - MVS
Object Filter screen.

Use this screen to specify a Db2 object filter to remove Db2 objects from your current object list.

Figure 360. ObjectOut - DB2 Object Filter

File-AID/RDX ----------- ObjectOut - DB2 Object Filter ----------------------

---------
Command ===> 

Primary commands: MVS 

DB2 Objects Filter: 
SSID . . . . . . . . : DSN (* or pattern for selection list)
Location . . . . . . : DSNLOC 
Creator ===> DSN8710 
Table Name ===> * 

After entering the information for the new Db2 object filter, press ENTER to proceed to the
“ObjectOut Preview”.

DB2 Objects Filter Area

Use the fields in this area to specify the Db2 objects to be removed from your current object list.
specifying patterns in the fields, File-AID/RDX searches the object list to find matches.

SSID
Displays the current Db2 subsystem ID.

Location
Displays the current Db2 location.

Creator
Specify the authorization ID of the owner of the objects that you want to remove from the object
list. Enter a pattern in this field if you want to remove objects from more than one creator. Valid
pattern characters are %, _, and * (see Pattern Characters on page 27).

Table Name
Specify a pattern for the object names you want to remove from the object list. Valid pattern
characters are %, _, and * (see Pattern Characters on page 27).

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:
Data Privacy 637

MVS (M)
Switches to the NEW - MVS Object Filter panel prefilled with the applicable information from
your profile. Refer to NEW - MVS Object Filter on page 630.

ObjectOut - MVS Object Filter

The ObjectOut - MVS Object Filter screen shown in Figure 361 is displayed when you enter the OO
primary command in the Data Disguise - Object List, or you enter the MVS primary command in the
ObjectOut - DB2 Object Filter screen.

Use this screen to specify an MVS object filter to remove MVS objects from your current object list.

Figure 361. ObjectOut - MVS Object Filter

File-AID/RDX ----------- ObjectOut - MVS Object Filter ----------------------

---------
Command ===> 

Primary commands: DB2 

MVS Objects Filter: (* or pattern for selection list)
File name ===> 

After entering the information for the MVS object filter, press ENTER to proceed to the “ObjectOut
Preview”.

MVS Objects Filter Area

Use the fields in this area to specify the MVS objects to be removed from your current object list.
specifying patterns in the fields, File-AID/RDX searches the object list to find matches.

File name
Specify the MVS file name pattern for the objects you want to remove from the object list. Valid
pattern character is * (see Pattern Characters on page 27).

Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:

DB2 (D)
Switches to the ObjectOut - DB2 Object Filter panel prefilled with the applicable information
from your profile. Refer to ObjectOut - DB2 Object Filter on page 636.

ObjectOut Preview
The ObjectOut Preview window shown in Figure 362 is displayed any time after you press enter on
either ObjectOut - DB2 Object Filter or the ObjectOut - MVS Object Filter screens. It displays the
results of your object filter search and allows you to select all, none, or individual objects to be
removed from your current object list.

Use this preview to select only those objects you want to remove.
638 File-AID/RDX Reference

Figure 362. ObjectOut Preview

Fi ObjectOut Preview -------- 

Co Command ===> Row 1 to 2 of 2 
SCROLL ===> PAGE 
Pr Primary Commands: ALL, Find 
Line Commands: S = Select 
D 
Select objects and press END to process n list) 

Object Name 
----------------------------------------------- 
_ FRSAMP.ORDER_LINE_TABLE 
_ FRSAMP.ORDER_TABLE 
******************* Bottom of data ******************** 
O 











After selecting all desired objects to be removed from the object list, press END to return to the Data
Disguise - Object List.

Object Name
Identifies the name of the objects that match your specified object filter.

Line Commands
The following File-AID/RDX-specific line command is valid:

S (Select)
Selects and marks this object to be removed from the object list. Blank out the S marker for
individual objects you don’t want removed from the object list. Use in conjunction with the ALL
primary command to mark your selections.

Primary Commands
The following File-AID/RDX-specific primary commands are valid:

ALL
Selects and marks all objects listed in the preview to be removed from the object list. Blank out
the S marker for individual objects you don’t want removed from the object list. Use in
conjunction with the S line command to mark your selections.

FIND (F)
Searches the preview list for the specified string and scrolls the list to display the first matching
entry at the top of the displayed entries. Use RFind to repeat the search.
Data Privacy 639

MVS XREF/Record Layout Window

When you select an MVS file with the S line command in the Data Disguise - Object List for which
File-AID/RDX does not have any record layout information, File-AID/RDX displays the “MVS
XREF/Record Layout” window where you must specify the applicable record layout information.

Figure 363. MVS XREF/Record Layout Window

MVS XREF/Record Layout 


Command ===> Scroll ===> CSR 

MVS file name: 'TSOID01.FASAMP.EMPLOYE1' 

Specify Record Layout and XREF Information: 
Record layout usage ===> (S = Single; X = XREF;) 
Record layout file ===> 
Member name ===> (Blank or pattern for member list) 
XREF File name ===> 
Member name ===> (Blank or pattern for member list) 


Field Descriptions

MVS File Name

Displays the file name of the selected MVS object.

Specify Record Layout and XREF Information

In the following fields you specify the record layout information to be used for the selected object.

Record layout usage

Indicate whether a single record layout (usage "S"), or an XREF (usage "X") had been used to
define the record layout information.

Record layout file

Specify the record layout file for the MVS object. To view a list of layout files, specify a pattern.
Valid pattern character is * (see Pattern Characters on page 27). If you specify a pattern, select a
file from the “Catalog Utility File List” as shown in Figure 364 on page 640.

Member name
Specify the member of the record layout file that contains the layout information for the MVS
object. Leave blank or use a pattern to narrow the search.

XREF file
Only needed if layout usage is X. Specify the XREF file name for the MVS object from which you
want to extract related data. Valid pattern character is * (see Pattern Characters on page 27). If
you specify a pattern, select a file from the “Catalog Utility File List” as shown in Figure 364 on
page 640.
640 File-AID/RDX Reference

Member name
Specify the member of the XREF file that contains the layout information for the MVS object.
Leave blank or use a pattern to narrow the search, see also Figure 366 on page 642.

MVS Catalog Utility File List

When specifying a pattern in the Record layout file or XREF File name fields in the MVS XREF/Record
Layout Window, File-AID/RDX searches the MVS catalog and displays any matches. Select the file
name you want to place in the applicable field with the S line command. The message in the top line
indicates for which field the list is displayed:

• Select Record Layout

• Select XREF file

Figure 364. MVS Catalog Utility File List (for Pattern FAS*.LAY*)

File-Aid/RDX ------------- Catalog Utility File List ---- Select Record Layout 
Command ===> SCROLL ===> CSR 
----- D A T A S E T N A M E -------------- 
S TSOID01.FASAMP.LAYOUTS NON-VSAM PRD938 
TSOID01.FASAMP2.LAYOUTS NON-VSAM MIGRAT 
******************************* Bottom of data ********************************

Field Descriptions

Dataset Name
File names that match the entered file name pattern.

Type
Catalog entry type. Types that may be displayed include: CLUSTER, DATA, INDEX, ALT INDEX,
PATH, NON-VSAM, GDG BASE, USER CTLG, ALIAS, and PAGESPACE.

Volume
Volume on which the file is stored. Multi-volume files are identified by the + (plus sign)
following the Volume field.

PDS Processing Options

A PDS Processing Options screen, as shown in Figure 365, is displayed when the file name on the
NEW - MVS Object Filter screen refers to a partitioned dataset (PDS). It is used to specify member
selection values to choose members based on a name mask, name range, the userid for last
modification, and creation and modification date ranges.

To display a nonselective member list, leave all member selection options blank on the PDS
Processing Options screen and press Enter.
Data Privacy 641

Figure 365. PDS Processing Options Screen

File-Aid/RDX ----------------- PDS Processing Options ------------------------

Command ===> 


Layout File: TSOID01.FASAMP.LAYOUTS 







Specify Member Selection Options (Blank for All Members) 
Member name mask ===> 
Member name range ===> to ===> 
Last modified userid ===> to ===> 
Creation date ===> to ===> (YY/MM/DD) 
Modification date ===> to ===> (YY/MM/DD) 



Use ENTER to continue, END to return to file specification screen 


Field Descriptions
The following list describes all PDS processing options that File-AID/RDX can present.

Member name mask

Specify a member name mask to select a subset of members based on the mask criteria. A pattern
member name or mask consists of explicit characters or a combination of explicit and pattern
characters.

Member name range

Specify a member name range to select a subset of members based on the characters in the
member name. The endpoint member names (FROM and TO) can be complete or partial and are
included in the member list when found. Pattern characters are not allowed.

If the FROM member field is blank and a TO member is specified, File-AID/RDX selects the
members less than or equal to the TO member padded with high values.

If a FROM member field is specified and the TO member is blank, File-AID/RDX selects members
greater than or equal to the FROM member padded with low values.

Entering the same characters in the FROM and TO fields selects all members beginning with
those characters.

Last modified userid

Specify a user identification range to select a subset of members based on the user ID that last
updated and saved a member. This information is a PDS statistic that is stored in the directory.

The endpoint userids (FROM and TO) can be complete or partial and are included in the member
list when found. Pattern characters are not allowed. As with member name range, the FROM field
is padded with low values and the TO field is padded with high values.

Members without PDS statistics, because they were not created (STATS OFF) or the statistics were
deleted, are not selected.
642 File-AID/RDX Reference

Creation date
Specify a creation date range to select a subset of members based on their creation date(s). This is
a PDS statistic that is stored in its directory.

The endpoint (FROM and TO) dates can be complete or partial and are included in the member
list when found. Leading zeros are required when specifying the year, month, and day.

If the FROM date field is blank and a TO date is specified, File-AID selects all members created on
or before the specified TO date.

If a FROM member date is specified and the TO date is blank, File-AID selects all members created
on or after the specified FROM date.

Entering the same dates in the FROM and TO fields selects members created only on that date.
The two-character year is assumed between 1960 and 2059. Partial creation dates are treated
positionally (YY/MM/DD) and are padded with default values.

For example, if you enter blanks the default FROM value becomes 60/01/01 and the TO value
becomes 59/12/31. If you enter 85, the defaults are 85/01/01 and 85/12/31. If you enter 85/09,
the defaults are 85/09/01 and 85/09/30.

Members without PDS statistics, because they were not created (STATS OFF) or the statistics were
deleted, are not selected.

Modification date
Specify a modification date range to select a subset of members based on the last modified
date(s). This is a PDS statistic that is stored in its directory. The last modified date is updated with
the current date each time a member is updated and saved.

See the description of the Creation date field for more information on specifying a modification
range. The specifications are identical.

Members without PDS statistics, because they were not created (STATS OFF) or the statistics were
deleted, are not selected.

XREF Select Member List

The XREF Select Member List screen, shown in Figure 366, is displayed when a blank or a pattern is
specified in the Member field for the XREF file name. The list may be scrolled using LOCATE
commands (LOC mem) or scrolling commands (such as UP and DOWN).

Select the desired XREF member with the S line command.

Figure 366. XREF Select Member List Screen

File-Aid/RDX - XREF Select - TSOID01.FRSAMP.XREF ------------ Row 1 to 5 of 5 

Command ===> SCROLL ===> PAGE 
S NAME DESCRIPTION TYPE CHANGED ID 
ADVMST4 FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
A020815 FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
RETEST1 FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
TEDS646 FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
S USERNEW FILE-AID/RDX GENERATED XREF __ XREF 00:00 AX 
******************************* Bottom of data ********************************
Data Privacy 643

Data Disguise - Column List

The Data Disguise - Column/Field List screen shown in Figure 367 is displayed when you select an
object from the Data Disguise - Object List.

It lists all columns/fields of the selected object along with the assigned disguise rule and rule
description.

Use the available line commands to manage the disguise information for the column.

Figure 367. Data Disguise - Column/Field List

File-AID/RDX --------- Data Disguise - Column/Field List --- Row 1 to 9 of 9 

Command ===> Scroll ===> CSR 

Primary Commands: Find, Size, SOrt 
Line Commands: S = Select A = Add/Assign rule U = Unassign rule I = Info


Disguise Object . .: FRSAMP.ORDER_LINE_TABLE 

Column/Field Name Type(Length) Disguise Rule +
--------------------------------- ------------ ------------------------------
_ ORDER_NUM * CHAR(6) 
_ ORDER_LINE_NUMBER DEC(5,0) 
_ PART_NUM * CHAR(6) 
_ PLAN_QTY DEC(7,2) 
_ UNITS_COMPLETE INTEGER 
_ UNITS_STARTED DEC(9,3) 
_ SCRAP_QTY DEC(9,3) 
_ START_DATE DATE U0000002 UNRELATED FRSAMP.ORDE
_ LINE_STATUS CHAR(6) 
******************************* Bottom of data ********************************




After you completed all desired disguise criteria for this object, press END to return to Data Disguise -
Object List.

Disguise Object
Identifies the name of the object you selected in the Data Disguise - Object List.

Column/Field Name
Identifies the name of the columns/fields of the object. An asterisk (*) to the right of the column
name indicates a related column.

NULL values will remain NULL even when disguise criteria are applied to the
field. The NULL indicator is not changed so the column will be considered
NULL at load time: the disguised value will not be loaded.

Type(Length)
Displays the column’s or field’s data type. The length of the data is displayed in parentheses
immediately following the data type for CHAR, CH, VCHAR, VC, GRPH, VGRPH, DEC, FIXPIC,
National data types only.
644 File-AID/RDX Reference

Unicode Db2 character data types are identified as CH(x), VC(x) or LV(x) with a suffix of U16 or
U-8. Unicode character data from an MVS file is identified as N(x) U-16.

See Table 8 on page 147 for more information about data types displayed in this column.

Column types CLOB, BLOB, DBCLOB, ROWID, DECFLOAT, BIGINT, BINARY,

VARBINARY, XML, or Unicode data types cannot be selected for disguise.

Disguise Rule
Identifies the disguise rule and description assigned to the column/field. When the criteria is
stored in a disguise criteria file, File-AID/RDX generates a unique name for each rule and
identifies its mode with a prefix, either A, R or U.

Annnnnnn identifies an associated rule

Rnnnnnnn identifies a related rule

Unnnnnnn identifies an unrelated rule

Rules not following this identification pattern are Associated rules for which
the identifier has been changed manually.

Position the cursor on the field and enter the EXPAND command to view the entire field
contents.

Line Commands
The following File-AID/RDX-specific line command is valid:

A (Add/Assign Rule)
Displays the Associated Rules List where you can select an already defined associated disguise rule
or create a new associated rule to assign to this column (see also Associated Rules List on page
646). You can only enter the A line command for a column that does not have a rule assigned to
it, yet.

I (Info)
Displays the disguise information for the selected column. The presented information differs
depending on the type of disguise rule, related, associated, or unrelated. Figure 368 displays the
information for unrelated columns/fields.
Data Privacy 645

Figure 368. Unrelated Rules Information - Criteria in Disguise Criteria File

File-AID/RDX -------- Data Disguise - Column/Field List ----- Row 1 to 9 of 9 

Command ===> Scroll ===> CSR 
Unrelated Columns/Fields 
Row 1 to 1 of 1 
Command ===> Scroll ===> CSR 

Rule: U0000002 - UNRELATED FRSAMP.ORDER_LINE_TABLE 
Criteria File: TSOID01.FRSAMP.DISCRIT 

Object Name + Unrelated Column/Field Name 
---------------------------------------- --------------------------------- 
FRSAMP.ORDER_LINE_TABLE START_DATE 
***************************** Bottom of data ****************************** 

S (Select)
Selects this column as a column to be disguised or to modify its existing disguise information.
When you press Enter, File-AID/RDX transfers control over to File-AID/Data Solutions’ Disguise
function where you actually define or modify the disguise criteria for the selected object.
Depending on the column type File-AID/RDX transfers to File-AID/Data Solutions in either
Related, Associated, or Unrelated mode (see also File-AID/Data Solutions Criteria Menu on page
648, File-AID/Data Solutions Criteria Menu on page 648, and File-AID/Data Solutions Criteria
Menu on page 648).

When selecting a column that already has a disguise rule defined for it, you can modify the
disguise criteria as long as the criteria was defined for the selected object and column.

However, when selecting a column with an Associated or Related disguise rule that was defined
using a different object and column, a warning message informs that you can either modify the
criteria using the original object and column or cancel your selection.

U (Unassign Rule)
Removes any disguise rule from this column. Notice the behavior depending on the type of rule:

– Unassigning a rule from a related field will unassign it from all related columns.

– Unassigning a rule from an associated field will only affect that object. However, if
unassigned from the object of origin, (the object used to define the rule), a warning popup
will display all of the places where the rule was applied and the rule will be unassigned from
all the associated objects, unless you cancel the command.

– Unassigning an unrelated rule will remove criteria from all unrelated fields. To remove
criteria from a single unrelated field, cancel the Unassign, then use the S line command to
select the rule and remove the criteria with File-AID/Data Solutions.

Unassigning a rule does not delete it from the criteria file as it might be used by another Disguise
Control File.

Primary Commands
The following File-AID/RDX-specific primary commands are valid:
646 File-AID/RDX Reference

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. SIze is a toggle switch so enter SIze again to return to the original format.

SORT (SO)
Sorts the displayed list by the specified display column name.

Associated Rules List

The Associated Rules List shown in Figure 369 is displayed when you enter an A line command for a
column in the Data Disguise - Column/Field List.

Associated rules are a special kind of criteria for unrelated fields. The criteria are always defined for a
single field and will be stored separately by associated field. Other objects can share this type of
criteria. The same field can exist in multiple objects even though the fields are not related. Associated
rules allow the criteria to be defined once and applied to the other objects where the same data exists.
You must manually identify the objects and fields that are to share the associated criteria with the A
line command; File-AID/RDX does not provide automated identification assistance.

Associated rules are like related criteria but instead of the Relationship File identifying where the
criteria are to be applied, you identify the data locations. Any changes made to associated disguise
criteria will apply to all objects that share the criteria.

File-AID/Data Solutions provides disguise options that are repeatable, but it is up to you to choose a
disguise method that will return the same replacement value in all objects if the values are to be
consistent across objects.

The Associated Rules List lists all currently defined associated rules. You can select an existing rule or
create a new one. The associated rule must match the column type and length of the selected column.

Use the available line commands to manage the associated rules for the column.
Data Privacy 647

Figure 369. Associated Rules List

File-AID/RDX -------- Data Disguise - Column/Field List --- Row 1 to 14 of 18 

Command ===> Scroll ===> CSR 
Associated Rules 
Pri 
Command ===> Scroll ===> CSR o 

Dis Primary Commands: NEW, Find, SOrt, Size 
Line Commands: S = Select I = Info 
C +
- Column/Field. .: CONTACT-NAME ---
_ C Disguise Object: TSOID01.FRSAMP.CUSTOMER 
_ C 
_ A Disguise Rule + Type Length 
_ C -------------------------------------------------- ------- ------ 
_ S ************************* Bottom of data ************************** 
_ Z 
_ C 
_ A 
_ T 
A C 
_ C 
_ C 
_ C 
_ C

After you selected an existing or defined and selected a new rule, press END to return to Data
Disguise - Column/Field List.

Column/Field
Identifies the name of the column/field for which you entered the A line command in the Data
Disguise - Column/Field List.

Disguise Object
Identifies the name of the object you selected in the Data Disguise - Object List.

Disguise Rule
Identifies the defined disguise rule by its member name in the Disguise Criteria File and displays
the disguise rule description as entered during the disguise creation.

Use the SCROLL LEFT and SCROLL RIGHT commands to view descriptions that are longer than
the display field.

Type
Displays the column’s or field’s data type. See Table 8 on page 147 for more information about
data types displayed in this column.

Length
Displays the column’s or field’s data length.

Line Commands
The following File-AID/RDX-specific line command is valid:
648 File-AID/RDX Reference

I (Info)
Displays the disguise information for the selected associated rule.

S (Select)
Assigns this associated rule to the column/field and returns to the Data Disguise - Column List
with the selected rule assigned to the column/field.

Primary Commands
The following File-AID/RDX-specific primary commands are valid:

NEW
Allows you to define a new associated criteria rule for this column. When you press Enter, File-
AID/RDX transfers control over to File-AID/Data Solutions’ Disguise function in associated mode.
There you actually define the new associated disguise criteria (see Criteria Menu - Associated
Mode on page 654). After defining the new associated rule, you return to the Data Disguise -
Column List with the new rule assigned to the column.

FIND (F)
Searches the list for the specified string and scrolls the list to display the first matching entry at
the top of the displayed entries. Use RFind to repeat the search.

SIZE (SI)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. SIze is a toggle switch so enter SIze again to return to the original format.

SORT (SO)
Sorts the displayed list by the specified column name.

File-AID/Data Solutions Criteria Menu

The File-AID/Data Solutions Criteria Menu is the entry and exit panel into File-AID/Data Solutions
after File-AID/RDX transfers the control so you can specify the disguise criteria for the selected object
column/field. The File-AID/Data Solutions Criteria Menu looks slightly different depending on
whether related, associated, or unrelated mode is in effect. The menu is specifically designed to
accommodate disguise criteria creation or modification for File-AID/RDX extract objects. This menu
cannot be accessed from the stand-alone File-AID/Data Solutions product, only via the bridge from
File-AID/RDX.

Regardless of the mode, the presented disguise criteria options are a subset of all available File-
AID/Data Solutions functions that are most likely to be used to disguise data for related extracts. You
can use the MENU primary command to view to all available options of the File-AID/Data Solutions
Criteria Menu.

As File-AID/RDX provides all the layout information and disguise criteria file and member names, all
you need to do is specify the disguise criteria for the selected object.
Data Privacy 649

The disguise criteria is stored in the disguise criteria file. The Disguise Control File (DCF) keeps track
of where the disguise criteria is stored.

Consult your File-AID/Data Solutions User Reference Manual on how to specify the disguise information.

Figure 370 shows File-AID/Data Solutions Criteria Menu.

Figure 370. File-AID/Data Solutions Criteria Menu

File-AID/Data Solutions -17.02.00- Criteria Menu --- ---- CREATE NEW CRITERIA 
OPTION ===> 

G GLOBAL - GLOBAL Fields 0 fields 
1 DATE AGING - Aging criteria 0 sets 
4 TRANSLATOR - Data Translator criteria 0 sets 
5.1 GENERATOR - Data Generator criteria 0 sets 
5.2 PATTERN - Pattern Data Generation 0 sets 
6 FIELD EXITS - Utilities criteria 0 sets 
7 DATA ENCRYPTION - Data Encryption Criteria 0 sets 
8 REPLACE - Data Replace Criteria 0 sets 




Disguise Object. . . : DSN8710.EMP 
Column. . . . . . .: LASTNAME 
Associated Rule ===> A0000001
Description . . ===> DSN8710.EMP:LASTNAME 

Commands: VIEW, SAVE, END, CANCEL, MENU

After you complete defining all the disguise criteria for the selected object column/field, press END to
return to the File-AID/RDX Data Disguise - Column List.

Criteria Menu Options

Enter the option number (G, 1, 4, 5.1, 5.2, 6, 7, or 8) to select the desired option. The status column
to the right of each option identifies the number of criteria sets the have been defined for the current
criteria rule with each criteria option.

G - GLOBAL
Displays the Define Global Fields Screen, shown in Figure 375 on page 658, and enables you to
view, define and change user global fields (user variables). It lists all existing user variables in the
entered order and displays blank lines for definition of additional user variables. Global fields
must start with & (ampersand) and they are retained in the order entered.

1 - DATA AGING
Displays the File-AID/Data Solutions Aging Criteria screen (see Figure 376 on page 658). Aging
criteria enables you to age dates in data records displayed with a record layout. To specify an
aging criterion, choose a date field and enter a relational operator of +, -, R, or FM a numeric
value in the century, year, month, and/or days field, and the appropriate date pattern. Leave the
relational operator blank for fields not involved in the aging criteria. Use = in the RO field to
replicate the last entered criteria.
650 File-AID/RDX Reference

4 - TRANSLATOR
Displays the File-AID/Data Solutions Data Translator Criteria screen (see Figure 382 on page 661).
The Data Translator feature translates data values in one or more fields based on a translate table
containing lookup and/or result values. The Translator function accesses the translate table based
on values from the fields specified on the formatted panel in five different ways:

– Binary search (S): Sorts the values internally and performs a binary search thereby speeding
up processing.

– Key search (K): Your search field matches the key field when your table file is a KSDS (Keyed
Sequential Dataset). If the entire table fits into memory, the key search functions identical to
the Binary Search. If there is insufficient memory the table is directly accessed by key.

– Direct row pointer search (D): The search field is hashed to a random number between 1
and the number of rows in the table. The resulting number determines the row to be used. No
value in the table matches the original search field.

– Hash to a key search (H): Similar in function to the Direct Row Pointer Key search except
that the random number is used to perform the Key search. The search field is hashed to a
random number between 1 and the number of rows in the table. For the Hash function to
work, the key of the VSAM file must be numeric with leading zeros, start with 1, and
increment by 1 for each row.

– Unique key search (U): Each different input value will return a different entry number
which will then be used to access the replacement values from the translate table. This will
produce unique replacement values as long as the translate table contains unique
replacement values.

When the corresponding row is determined, the Translator function returns the result values and
uses them to replace the specified output field value.

5.1 - GENERATOR
Displays the File-AID/Data Solutions Data Generator Criteria screen (see Figure 383 on page 661).
The Data Generator feature is used to fill fields with new data values. You may use the Data
Generator to fill new fields with test data, or to replace live data that may be sensitive production
information that should not be used in test. Data can be generated for numeric and character
fields by using one of four methods: sequential, random, pattern masking, or by picking valid
values from another file. An object of an ODO/REFER is non-selectable.

The Data Generation function can also be used to generate new records into a new file without
specifying an input file from which to model the records. A Layout containing an ODO/REFER
CANNOT be used.

5.2 - PATTERN
Displays the File-AID/Data Solutions Pattern Data Generator Criteria screen (see Figure on page
661). The Data Pattern Generator feature is used to fill fields with new data values. You may use
the Data Pattern generator to fill new fields with test data, or to replace live data that may be
sensitive production information that should not be used in test. Data can be generated for
unsigned numeric and character fields by using one of two methods: sequential & random.

The Data Generation function can also be used to generate new records into a new file without
specifying an input file from which to model the records. A Layout containing an ODO/REFER
CANNOT be used.
Data Privacy 651

6 - FIELD EXITS
Displays the File-AID/Data Solutions Field Exit Criteria screen (see Figure 385 on page 662).
Formatted field exit criteria enables you to define and process both Data Solutions-defined and
user-defined business function data conversions. Field exits distributed with Data Solutions
perform the following business functions: Addition, Data Analysis, Date Analysis, Division,
European currency conversion, Encryption/decryption, Field Replacement, Multiplication, Test
date generator, Resequencing, Subtraction, and Use global area.

HASH VALUE and MOVE FIELD exits not allowed by File-AID/RDX.

To specify a formatted field exit criterion, choose a data field and enter the EX relational
operator, valid parameters for the exit in the PARAMETERS field, and the name of the exit in the
EXIT NAME field. If you enter EP in the RO field, Data Solutions displays the Field Exit
Parameters screen. If you leave the EXIT NAME field blank, Data Solutions displays the List of
Available Field Exits screen. Leave the relational operator blank for fields not involved in the
aging criteria.

Use the INPUT, INSERT, or REPEAT primary command to specify multiple sets of change criteria.
When multiple sets are specified, Data Solutions applies them separately in the order specified.

In addition, you can make the change process contingent on the field values in the record
through the use of selection criteria. Simply enter the SELECT primary command on the
Formatted Field Exit Criteria screen to display the Formatted Selection Criteria screen.

7 - DATA ENCRYPTION
Displays the File-AID/Data Solutions Data Encryption Criteria screen (see Figure 386 on page
663). The Data Encryption function simplifies the process of encrypting and decrypting a data
file. It transforms a field value to mask the original value and is useful when creating test files
from production files.

File-AID/Data Solutions uses encryption/decryption exits to define and process both Data
Solutions-defined and user-defined encryption routines. Simply choose a routine for a particular
field from Data Solution's list of Available Encryption/Decryption Exits. With the use of selection
criteria, you can assign an encryption routine to a field based on the data in that field or on the
data in another field in the record.

The original data characteristics are maintained (i.e. valid packed fields or punctuation in
character fields). In addition, unique values are maintained so that the key field remains unique.
This permits you to decrypt the encrypted data to its original value.

The Key Encrypt/Decrypt Exit is a Data Solutions-defined exit. Two sample

encryption/decryption routines are also available. You can use one of the sample
encryption/decryption routines or create your own routine.

8 - REPLACE
Displays the File-AID/Data Solutions Data Replace Criteria screen. It allows you to specify a
replace value (R) or source (FF for field-to-field) for the specified field.

The status column to the right of each option identifies the number of criteria sets the have been
defined for the current criteria rule with each criteria option.
652 File-AID/RDX Reference

Status
Displays the status of the various types of criteria associated with the criteria dataset listed on the
top line of this screen and the disguise rule for the current disguise object:

n fields

Specifies the number of global variable fields that have been defined. These user defined
variables are available for use by any of the sets within the criteria.

n sets

Specifies the number of sets that are specified for change criteria. A set of change criteria is
defined as a single expression that can lead to the selection of a record. A set may test for one
condition or several conditions. The conditions can be ANDed together and several
conditions separated by commas create nested OR conditions within a set.

Primary Commands
The following primary commands are valid:

CANCEL (CAN)
Returns to the File-AID/RDX Data Disguise - Column List without saving any criteria
information.

END
Saves the current change criteria in the criteria dataset you specified in the File-AID/Data
Solutions Parameters and returns to the File-AID/RDX Data Disguise - Column List.

MENU
Displays all options of the File-AID/Data Solutions Criteria Menu so you can access the remaining
File-AID/Data Solutions Criteria Menu options. The MENU command is a toggle switch so enter
MENU again to return to the previous display format.

Figure 371. File-AID/Data Solutions Full Criteria Menu

File-AID/Data Solutions -17.02.00- Criteria Menu --- -------------------------

OPTION ===> 

G GLOBAL - GLOBAL Fields 0 fields 
1 DATE AGING - Aging criteria 0 sets 
2.1 EURO CONVERSION - Euro Conversion criteria 0 sets 
2.2 TRIANGULATION - Currency Triangulation 0 sets 
3.1 DATE PATTERN ANALYSIS - Date Pattern criteria 0 sets 
3.2 VALIDATION - Validate criteria 0 sets 
3.3 DATA ANALYSIS - Data Analysis criteria 0 sets 
4 TRANSLATOR - Data Translator criteria 0 sets
5.1 GENERATOR - Data Generator criteria 0 sets 
5.2 PATTERN - Pattern Data Generation 0 sets 
6 FIELD EXITS - Utilities criteria 0 sets 
7 DATA ENCRYPTION - Data Encryption Criteria 0 sets 
8 REPLACE - Data Replace Criteria 0 sets 


Disguise Object. .: DSN8710.EMP 
Column. . . . . . .: LASTNAME 
Associated Rule ===> A0000001
Description . . ===> DSN8710.EMP:LASTNAME 

Commands: VIEW, SAVE, END, CANCEL, MENU
Data Privacy 653

These additional options are available from the expanded criteria menu:

2.1 - EURO CONVERSION

Displays the File-AID/Data Solutions Euro Conversion Criteria screen (see Figure 377 on page
659). The European Currency Conversion Criteria screen enables you to enter currency
conversion criteria to convert the specified field to or from the EURO (or ECU (European
Currency Unit)). You must specify the dataset name of an existing European currency rate file
(i.e. DASAMP.FACTORS).

2.2 - TRIANGULATION
Displays the File-AID/Data Solutions Triangulation Criteria screen (see Figure 378 on page
659). Euro Triangulation enables you to convert from one local currency into another using
Euro values to triangulate and control the conversion in accordance with ECU guidelines. An
audit report can be generated to document the changes, including the intermediate Euro
values.

3.1 - DATE PATTERN ANALYSIS

Displays the File-AID/Data Solutions Date Analysis Criteria screen (see Figure 379 on page
659). The Date Analysis feature simplifies the identification of date fields. It is functionally
the same as the Date Analysis field exit.

By automatically comparing date values to a list of date patterns, File-AID/Data Solutions

produces a report that lists the percentage of times a valid date is present and the number of
times each date format is valid. You can compare your files to the date patterns provided or
to those you've specifically created. The report can be viewed online or in batch mode.

3.2 - VALIDATION
Displays the File-AID/Data Solutions Validation Criteria screen (see Figure 380 on page 660).
Validation Analysis enables you to validate data based on data type or the actual values
within the record. You may specify the "valid" values for a field online or in an external file.
Validation processes include alpha, alphanumeric, and numeric data checking.

When invalid data is found in any of the fields of a record, a user-specified return code is set
indicating the validation process failed.

3.3 - DATA ANALYSIS

Displays the File-AID/Data Solutions Data Analysis Criteria screen (see Figure 381 on page
660). The Data Analysis function analyzes the data in a particular field by comparing the data
to its record layout field definition and reports whether the data is valid or invalid. The
report includes whether invalid data was found in the specified field, the range of data found
in that field, and the number of times each unique value occurs within the field.

You can determine how the values are analyzed. You may supply a list of values for Data
Solutions to search for and report only those values found within the field.

RETURN
Saves the current change criteria in the criteria dataset you specified in the File-AID/Data
Solutions Parameters and returns to the File-AID/RDX Primary Option Menu.
654 File-AID/RDX Reference

SAVE
Saves the current criteria in the criteria dataset you specified in the File-AID/Data Solutions
Parameters.

See Disguise Criteria Dataset Specification on page 663 for more information.

It is highly recommended you use separate criteria files for disguise criteria created
through the File-AID/RDX interface and name them in such a way as to easily recognize
them as such. As the layout information for the File-AID/RDX extract object may be
different from the information you would provide with the stand-alone File-AID/Data
Solutions, the disguise process may not produce valid and repeatable results.

VIEW
Displays the View Criteria screen, which summarizes the options and criteria sets into a scrollable
display.

Criteria Menu - Associated Mode

The File-AID/Data Solutions Criteria Menu - Associated Mode screen shown in Figure 372 is displayed
when you create or modify an associated disguise rule. The menu is specifically designed to
accommodate disguise criteria creation for File-AID/RDX extracts. This menu cannot be accessed from
the stand-alone File-AID/Data Solutions product, only via the bridge from File-AID/RDX.

Here you select the desired disguise option(s) and identify the associated rule with a meaningful
description as you can change the generated name to a more descriptive associated rule name.

When specifying criteria in associated mode, only the associated field is

displayed in the respective criteria screen (see Figure 383 on page 661 for
an example).

Figure 372. File-AID/Data Solutions Criteria Menu - Associated Mode

File-AID/Data Solutions -17.02.00- Criteria Menu --- ---- CREATE NEW CRITERIA 
OPTION ===> 

G GLOBAL - GLOBAL Fields 0 fields 
1 DATE AGING - Aging criteria 0 sets 
4 TRANSLATOR - Data Translator criteria 0 sets 
5.1 GENERATOR - Data Generator criteria 0 sets 
5.2 PATTERN - Pattern Data Generation 0 sets 
6 FIELD EXITS - Utilities criteria 0 sets 
7 DATA ENCRYPTION - Data Encryption Criteria 0 sets 
8 REPLACE - Data Replace Criteria 0 sets 




Disguise Object. . . : DSN8710.EMP 
Column. . . . . . .: LASTNAME 
Associated Rule ===> A0000001
Description . . ===> DSN8710.EMP:LASTNAME 

Commands: VIEW, SAVE, END, CANCEL, MENU
Data Privacy 655

After you completed all desired disguise criteria for this object, press END to exit File-AID/Data
Solutions and return to the Data Disguise - Column/Field List.

Disguise Object
Identifies the name of the object you selected in the Data Disguise - Object List.

Column Name
Identifies the name of the columns/fields of the object you selected in the Data Disguise -
Column/Field List.

Associated Rule
Identifies the disguise rule member name in the Disguise Criteria file. When creating a new rule
File-AID/RDX assigns a unique name (Annnnnnn) in the current disguise criteria file. You can
change the generated name to a more descriptive associated rule name. This field only displays
when criteria is stored in the Disguise Criteria file.

Description
Displays the disguise rule description as entered during the disguise creation. By default, it
includes the word ASSOCIATED for associated mode, followed by the column/field and object
name. You can change the generated description to better reflect your disguise criteria.

Criteria Menu - Related Mode

The File-AID/Data Solutions Criteria Menu - Related Mode screen shown in Figure 373 is displayed
when you create or modify a related disguise rule. The menu is specifically designed to accommodate
disguise criteria creation for File-AID/RDX extracts. This menu cannot be accessed from the stand-
alone File-AID/Data Solutions product, only via the bridge from File-AID/RDX.

Here you select the desired disguise option(s) and identify the related rule with a meaningful
description.

When you select a disguise option, File-AID/Data Solutions enters the respective criteria screen.

In the criteria screens, all columns are displayed and can be used as search
or select values. However, only the selected, related column/field can be
replaced.
656 File-AID/RDX Reference

Figure 373. File-AID/Data Solutions Criteria Menu - Related Mode

File-AID/Data Solutions -17.02.00- Criteria Menu --- --- CREATE NEW CRITERIA 
OPTION ===> 4 

G GLOBAL - GLOBAL Fields 0 fields 
1 DATE AGING - Aging criteria 0 sets
4 TRANSLATOR - Data Translator criteria 0 sets
5.1 GENERATOR - Data Generator criteria 0 sets 
5.2 PATTERN - Pattern Data Generation 0 sets 
6 FIELD EXITS - Utilities criteria 0 sets 
7 DATA ENCRYPTION - Data Encryption Criteria 0 sets 
8 REPLACE - Data Replace Criteria 0 sets 




Disguise Object. .: DSN8710.EMP 
Column. . . . . : EMPNO 
Related Rule : R0000001
Description ===> RELATED EMPNO:DSN8710.EMP 

Commands: VIEW, SAVE, END, CANCEL, MENU

After you completed all desired disguise criteria for this object, press END to exit File-AID/Data
Solutions and return to Data Disguise - Object List.

Disguise Object
Identifies the name of the object you selected in the Data Disguise - Object List.

Column
Identifies the name of the column/field of the object you selected in the Data Disguise -
Column/Field List. For a related rule, you can only replace the value of the related column/field,
but you may search/select on other fields.

Related Rule
Identifies the disguise rule member name that applies to the related column/field. File-AID/RDX
generates the name and you cannot change it. This field only displays when criteria is stored in
the Disguise Criteria file.

Description
Displays the disguise rule description as entered during the disguise creation. By default, it
includes the word RELATED for related mode, followed by the related column/field and object
name. You can change the generated description to better reflect your disguise criteria.

Criteria Menu - Unrelated Mode

The File-AID/Data Solutions Criteria Menu - Unrelated Mode screen shown in Figure 374 is displayed
when you create or modify an unrelated disguise rule. The menu is specifically designed to
accommodate disguise criteria creation for File-AID/RDX extracts. This menu cannot be accessed from
the stand-alone File-AID/Data Solutions product, only via the bridge from File-AID/RDX.
Data Privacy 657

Here you select the desired disguise option(s) and identify the unrelated rule with a meaningful
description. The column name is not displayed as you can specify disguise criteria for more than one
column/field.

Figure 374. File-AID/Data Solutions Criteria Menu - Unrelated Mode

File-AID/Data Solutions -17.02.00- Criteria Menu --- --- CREATE NEW CRITERIA 
OPTION ===> 4 

G GLOBAL - GLOBAL Fields 0 fields 
1 DATE AGING - Aging criteria 0 sets 
4 TRANSLATOR - Data Translator criteria 0 sets 
5.1 GENERATOR - Data Generator criteria 0 sets 
5.2 PATTERN - Pattern Data Generation 0 sets 
6 FIELD EXITS - Utilities criteria 0 sets 
7 DATA ENCRYPTION - Data Encryption Criteria 0 sets 
8 REPLACE - Data Replace Criteria 0 sets 




Disguise Object. .: DSN8710.EMP 

Unrelated Rule : U0000001
Description ===> Unrelated DSN8710.EMP 

Commands: VIEW, SAVE, END, CANCEL, MENU

After you completed all desired disguise criteria for this object, press END to exit File-AID/Data
Solutions and return to Data Disguise - Object List.

Disguise Object
Identifies the name of the object you selected in the Data Disguise - Object List.

Unrelated Rule
Identifies the disguise rule member name that applies to the selected object. File-AID/RDX
generates the name and you cannot change it. This field only displays when criteria is stored in
the Disguise Criteria file.

Description
Displays the disguise rule description as entered during the disguise creation. By default, it
includes the word UNRELATED for unrelated mode, followed by the object name.

Define Global Fields

The Define Global Fields Screen, shown in Figure 375, enables you to view, define and change user
global fields. It lists all existing user variables in the entered order and displays blank lines for
definition of additional user variables. Global fields must start with & (ampersand) and they are
retained in the order entered.

Refer to Chapter 14, “Criteria (S)” in the File-AID/Data Solutions User Reference Manual for detail information
on how to create user global fields.
658 File-AID/RDX Reference

Figure 375. Define Global Fields Screen

File-AID Define Global Fields Row 1 to 17 of 51

Command ===> Scroll ===> PAGE

Define User global fields: 

Field name Char/Num Length
--------------------------- -------- ------
&GSSEL C 1
___________________________ _ ____
___________________________ _ ____
___________________________ _ ____
___________________________ _ ____
___________________________ _ ____

File-AID/Data Solutions Aging Criteria

The File-AID/Data Solutions Aging Criteria displays when you enter Option 1, DATE AGING from the
File-AID/Data Solutions Criteria Menu. The messages “RELATED DISGUISE”, “UNRELATED
DISGUISE”, or “ASSOCIATED DISGUISE” remind you of the current File-AID/RDX disguise mode for
which you are creating date aging criteria.

Refer to Chapter 4, “Date Aging (1)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create date aging criteria.

Figure 376. File-AID/Data Solutions Aging Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Aging Criteria ------------ UNRELATED DISGUISE 
COMMAND ===> SCROLL ===> CSR 
RULES ===> ("*" or pattern for member list) 
SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO -C- -Y- -M- --D-- --DATE PATTERN-- R 
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN 
5 FIRSTNME LENGTH 
14/VCHR 
5 MIDINIT 1/AN 
5 LASTNAME LENGTH 
17/VCHR 
5 WORKDEPT 6/AN 
5 PHONENO 4/AN 
5 HIREDATE 10/AN 
5 JOB 8/AN 
5 EDLEVEL 2/BI 
5 SEX 1/AN 
5 BIRTHDATE 10/AN 
Valid RO: +, -, R, FM - For list of patterns,leave PATTERN blank.
Commands: SELect, View

File-AID/Data Solutions Euro Conversion Criteria

The File-AID/Data Solutions Euro Conversion Criteria displays when you enter Option 2.1, EURO
CONVERSION from the File-AID/Data Solutions Criteria Menu. The first time you create criteria for
an object, the messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED
DISGUISE” remind you of the current File-AID/RDX disguise mode.

Refer to Chapter 5, “Euro Tools (2)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create Euro conversion criteria.
Data Privacy 659

Figure 377. File-AID/Data Solutions Euro Conversion Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Euro Conversion Crite UNRELATED DISGUISE
COMMAND ===> SCROLL ===> CSR 
EURO RATE DATASET ===> 
SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO FROM/TO CURRENCY DECIMAL ADJUST 
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN

After you defined the Euro conversion criteria, press END to return to the File-AID/Data Solutions
Criteria Menu.

File-AID/Data Solutions Triangulation Criteria

The File-AID/Data Solutions Triangulation Criteria displays when you enter Option 2.2, EURO
TRIANGULATION from the File-AID/Data Solutions Criteria Menu. The first time you create criteria
for an object, the messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED
DISGUISE” remind you of the current File-AID/RDX disguise mode.

Refer to Chapter 5, “Euro Tools (2)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create Euro triangulation criteria.

Figure 378. File-AID/Data Solutions Triangulation Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Triangulation Criteria ------------------------
COMMAND ===> SCROLL ===> CSR 
EURO RATE DATASET ===> 
SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO FROM TO EURO-DEC TO-DEC AUDIT 
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 

After you defined the Euro triangulation criteria, press END to return to the File-AID/Data Solutions
Criteria Menu.

File-AID/Data Solutions Date Analysis Criteria

The File-AID/Data Solutions Date Analysis Criteria displays when you enter Option 3.1, DATE
PATTERN ANALYSIS from the File-AID/Data Solutions Criteria Menu. The first time you create criteria
for an object, the messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED
DISGUISE” remind you of the current File-AID/RDX disguise mode.

Refer to Chapter 6, “Data Analyzer (3)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create date analysis criteria.

Figure 379. File-AID/Data Solutions Date Analysis Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Date Analysis Criteria ------------------------
COMMAND ===> SCROLL ===> CSR 

SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO -OPTIONAL LENGTH---------------------
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN
660 File-AID/RDX Reference

After you defined the date analysis criteria, press END to return to the File-AID/Data Solutions
Criteria Menu.

File-AID/Data Solutions Validation Criteria

The File-AID/Data Solutions Validation Criteria displays when you enter Option 3.2, VALIDATION
from the File-AID/Data Solutions Criteria Menu. The first time you create criteria for an object, the
messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED DISGUISE” remind you
of the current File-AID/RDX disguise mode.

Refer to Chapter 6, “Data Analyzer (3)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create validation criteria.

Figure 380. File-AID/Data Solutions Validation Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Validation Criteria ---------------------------
COMMAND ===> SCROLL ===> CSR 

SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO --------- PARAMETERS -------------- +
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN

After you defined the validation criteria, press END to return to the File-AID/Data Solutions Criteria
Menu.

File-AID/Data Solutions Data Analysis Criteria

The File-AID/Data Solutions Data Analysis Criteria displays when you enter Option 3.3, DATA
ANALYSIS from the File-AID/Data Solutions Criteria Menu. The first time you create criteria for an
object, the messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED DISGUISE”
remind you of the current File-AID/RDX disguise mode.

Refer to Chapter 6, “Data Analyzer (3)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create data analysis criteria.

Figure 381. File-AID/Data Solutions Data Analysis Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Data Analysis Criteria ------------------------
COMMAND ===> SCROLL ===> CSR 

SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO --------- PARAMETERS -------------- +
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN

After you defined the data analysis criteria, press END to return to the File-AID/Data Solutions
Criteria Menu.

File-AID/Data Solutions Data Translator Criteria

The File-AID/Data Solutions Data Translator Criteria displays when you enter Option 4, TRANSLATOR
from the File-AID/Data Solutions Criteria Menu. The first time you create criteria for an object, the
messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED DISGUISE” remind you
of the current File-AID/RDX disguise mode.
Data Privacy 661

Refer to Chapter 7, “Translator (4)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create data translator criteria.

Figure 382. File-AID/Data Solutions Data Translator Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Data Translator Criteria ---- RELATED DISGUISE 
COMMAND ===> SCROLL ===> CSR 
TABLE DATASET ===> 
SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO --------- PARAMETERS ---------------+
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN

After you defined the data translator criteria, press END to return to the File-AID/Data Solutions
Criteria Menu.

File-AID/Data Solutions Data Generator Criteria

The File-AID/Data Solutions Data Generator Criteria displays when you enter Option 5.1,
GENERATOR from the File-AID/Data Solutions Criteria Menu. The first time you create criteria for an
object, the messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED DISGUISE”
remind you of the current File-AID/RDX disguise mode.

Refer to Chapter 8, “Generator (5)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create data generator criteria.

Figure 383. File-AID/Data Solutions Data Generator Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Data Generator Criter ASSOCIATED DISGUISE 
COMMAND ===> SCROLL ===> CSR 
TABLE DATASET ===> 
SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO --------- PARAMETERS ---------------+
******************************* TOP OF DATA ***********************************
5 LASTNAME 17/VCHR 
***************************** BOTTOM OF DATA **********************************

After you defined the data generator criteria, press END to return to the File-AID/Data Solutions
Criteria Menu.

File-AID/Data Solutions Pattern Data Generator Criteria

The File-AID/Data Solutions Pattern Data Generator Criteria displays when you enter Option 5.2,
PATTERN from the File-AID/Data Solutions Criteria Menu. The first time you create criteria for an
object, the messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED DISGUISE”
remind you of the current File-AID/RDX disguise mode.

Refer to Chapter 8, “Generator (5)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create data generator criteria.
662 File-AID/RDX Reference

Figure 384. File-AID/Data Solutions Pattern Data Generator Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Pattern Data Criteria ASSOCIATED DISGUISE 
COMMAND ===> SCROLL ===> CSR 
SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO --------- PARAMETERS ---------------+
******************************* TOP OF DATA ***********************************
5 LASTNAME 17/VCHR 
***************************** BOTTOM OF DATA **********************************

After you defined the pattern data generator criteria, press END to return to the File-AID/Data Solutions
Criteria Menu.

File-AID/Data Solutions Field Exit Criteria

The File-AID/Data Solutions Field Exit Criteria displays when you enter Option 6, FIELD EXITS from
the File-AID/Data Solutions Criteria Menu. The first time you create criteria for an object, the
messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED DISGUISE” remind you
of the current File-AID/RDX disguise mode.

Refer to Chapter 9, “Field Exits (6)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create field exit criteria.

HASH VALUE and MOVE FIELD exits not allowed by File-AID/RDX.

Figure 385. File-AID/Data Solutions Field Exit Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Field Exit Criteria --------- RELATED DISGUISE 
COMMAND ===> SCROLL ===> CSR 

SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----PARAMETERS---- + ---EXIT NAME--- 
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN

After you defined the field exit criteria, press END to return to the File-AID/Data Solutions Criteria
Menu.

File-AID/Data Solutions Data Encryption Criteria

The File-AID/Data Solutions Data Encryption Criteria displays when you enter Option 7, DATA
ENCRYPTION from the File-AID/Data Solutions Criteria Menu. The first time you create criteria for an
object, the messages “RELATED DISGUISE”, “UNRELATED DISGUISE”, or “ASSOCIATED DISGUISE”
remind you of the current File-AID/RDX disguise mode.

Refer to Chapter 10, “Data Encryption (7)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create data encryption criteria.
Data Privacy 663

Figure 386. File-AID/Data Solutions Data Encryption Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Data Encryption Criteria ----------------------
COMMAND ===> SCROLL ===> CSR 

SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----PARAMETERS---- + ENCRYPTION NAME 
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN

After you defined the data encryption criteria, press END to return to the File-AID/Data Solutions
Criteria Menu.

File-AID/Data Solutions Data Replace Criteria

The File-AID/Data Solutions Data Replace Criteria displays when you enter Option 8, REPLACE from
the File-AID/Data Solutions Criteria Menu. It allows you to specify a replace value or source for the
specified field.

Refer to Chapter 11, “Data Replace (8)” in the File-AID/Data Solutions User Reference Manual for detail
information on how to create data replace criteria.

Figure 387. File-AID/Data Solutions Data Replace Criteria

Action Sets Display Show Options Menu Help 

-------------------------------------------------------------------------------
File-AID/Data Solutions ------- Data Replace Criteria -------------------------
COMMAND ===> SCROLL ===> CSR 

SET 1 OF 1 EMP-TBL GBL = N SEL = N
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----PARAMETERS---- + ENCRYPTION NAME 
******************************* TOP OF DATA ***********************************
5 NULL-INDICATORS 20/AN 
5 EMPNO 6/AN

After you defined the data replace criteria, press END to return to the File-AID/Data Solutions Criteria
Menu.

Disguise Criteria Dataset Specification

When you enter the SAVE primary command, File-AID/Data Solutions displays the Change Criteria
Dataset Specification screen as shown in Figure 388.
664 File-AID/RDX Reference

Figure 388. File-AID/Data Solutions Change Criteria Dataset Specification - New Criteria

File-AID/Data Solutions -- Change Criteria Dataset Specification -------------

COMMAND ===> SCROLL ===> CSR 

Specify Change Criteria Information: 
Criteria dataset name ===> 'PFHKFL0.FRSAMP.DISGCRIT' 
Unrelated rule.: ===> U0000010 (Blank or pattern for member list)












Use ENTER to save into the specified location 
Use END to stop SAVE processing and continue 

Specify Change Criteria Information:

Criteria dataset name

Identifies the disguise criteria file name, if the existing criteria is stored in the Criteria file (PDS).
Only displays if Existing criteria location is PDS.

Unrelated Rule
Identifies the rule number (member name) of the Criteria file that stores the current disguise
criteria. File-AID/RDX generates the name and you cannot change it, unless it’s an associated
rule.

or

Related Rule
Identifies the rule number (member name) of the Criteria file that stores the current disguise
criteria. File-AID/RDX generates the name and you cannot change it, unless it’s an associated
rule.

or

Associated Rule
Identifies the rule number (member name) of the Criteria file that stores the current disguise
criteria. File-AID/RDX generates the name and you can change it, as it’s an associated rule.

DCF: Disguise Existing Extract

The DCF: Disguise Existing Extract screen shown in Figure 389 is displayed when you

• Select Option 2, Disguise, from the Data Privacy Menu on page 608.
Data Privacy 665

Use this screen to specify information required for the disguise operation, then enter GO to submit
the batch job for disguise.

Hints
• Before you submit the disguise job, make sure that the Disguise Control File or the Dynamic
Privacy Rules Project includes the desired disguise criteria for the objects included in the extract
file.

• It is also recommended that the relationship information in both the extract and disguise control
file matches.

• Also, when using disguise rules with complex criteria, the object that you used to define the
criteria originally must be included (not excluded) in the extract file or the disguise may not be
successful.

• For related disguise rules, always define the criteria on the object that contains all of the different
unique values (including orphans) to be extracted.

Figure 389. DCF: Disguise Existing Extract

File-AID/RDX ------------ DCF: Disguise Existing Extract --------------------

COMMAND ===> 

Primary Commands: JCL view, GO to submit job 

Specify File Names: 
Extract File ===> EXTRACT.ORDVW25 
Member ===> (Blank or pattern for member list)

Disguised Extract File ===> DISGEXT.ORDVW25 
Member ===> (Blank or pattern for member list)
VOLSER ===> 
Disposition ===> NEW (NEW, OLD, SHR)

DCF: Control File ===> FRSAMP.DISGUISE 

Create Audit Trail ===> N ( Y = Yes; N = No) 
Audit Trail prefix ===> 

Enter the requested file information before viewing the JCL or submitting the disguise job with the
GO command directly:

Extract File
Specify the name of the Extract File that is to be disguised. The extract file can also be a
compressed extract file (see Compress on page 339).

If the Extract File is on tape, specify the name of the Extract Summary File instead of the name of
the Extract File on tape. The Extract Summary File was created when the generated extract was
saved to tape (see Specify Extract “TO” File Information on page 338). If your extract file on tape
was created with an earlier release of File-AID/RDX than 4.8, create a summary file as described in
Extract File Specification on page 419.

Any existing Extract File can be disguised; however, a file cannot be disguised more than once.

When you had requested an extract with disguise and the disguise step of that extract failed, or
you had also set the option to save the pre-disguise records to a file in a masked format, you can
666 File-AID/RDX Reference

enter the name of the pre-disguise Extract File here as the extract file to be disguised. You find the
name of the pre-disguise file in the output of the extract job.

The name assigned to the pre-disguise extract file will use the standard File-AID/RDX routine to
generate a "temporary" name. The name will be the user prefix, the mid-level qualifier from the
Profile, the word "EXTRACT" and finally the current date and time fields (i.e. D050128.T055709).

Member
If the file you specified in Extract File is partitioned, you can enter a member name. If you leave
this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up containing a list
of members that match the specified pattern. The only valid pattern character is an asterisk (*).

Disguised Extract File

Specify the name where the disguised extracted data is to be written. Make sure the size
allocation is at least the same as the size of the extract file to be disguised. See also Size Allocation
of Disguise Extract File on page 685.

When the specified disguised extract output is to tape or cartridge, File-AID/RDX automatically
creates a summary file on DASD. The name of the summary file is the one specified in your
profile or, if none is specified there, it is the name of the extract file with SUMMARY replacing
the last node of the extract file name or a truncated form of SUMMARY as to not exceed 44
characters. If the summary file exists, File-AID/RDX will update (overwrite) its content. Refer to
Extract Summary File on page 45 for more information.

Member
If the file you specified in Disguised Extract File is partitioned, you can enter a member name. If
you leave this field blank or specify a pattern, File-AID/RDX displays a Member List pop-up
containing a list of members that match the specified pattern. The only valid pattern character is
an asterisk (*). You can create new members by entering the name of the new member.

VOLSER
If the file specified in Disguised Extract File is non-cataloged or new, specify the volume serial
number of the file. For non-cataloged files, a volume serial number is required. For new files, a
volume serial number is optional.

Disposition
Specify the disposition of the disguise "to" file. You can extract to existing files with a disposition
of OLD. Existing files must conform to the format outlined for the extract file in File-AID/RDX
Extract File on page 377. Specify a disposition of NEW to create a new file.

If you specify NEW in the Disposition field, you must specify the following allocation
parameters in the Create New File screen (Figure 175 on page 334).

DCF: Control File

Specify the Disguise Control File Name. The Disguise Control File determines what disguise
criteria are applied to objects included in this extract. Required for Disguise Selection option 1.
Data Privacy 667

Create Audit Trail

Specify whether an Audit Trail is to be created for each object being disguised. The Audit Trail will
contain the before and after images of each record that was disguised.

No. Audit Trail datasets will not be created.

Yes. File-AID/RDX creates a separate Audit Trail dataset for each disguised object. The naming
convention for each Audit Trail dataset (Audit Trail File on page 47) is

prefix.RDXA.DnnnBnnn.Dyymmdd.Thhmmss.Msss

Audit Trail file prefix

Specify the prefix to be assigned to the Audit Trail dataset names. Prefix plus USERID can be up to
14 positions, the remainder of the dataset name will follow the above mentioned naming
convention. If prefix is blank, only the USERID will be used. Any value specified will be appended
to the USERID. Precede the prefix value with a single quote (‘) to use the value without the
USERID.

Primary Commands
The following primary commands are valid:

GO
Submit the batch job for disguise.

JCL
View the JCL generated for the disguise job prior to submitting the job with the SUBMIT
command (see also View JCL on page 667).

View JCL
The ISPF/PDF Edit screen shown in Figure 390 is displayed when you enter the JCL command in the
DCF: Disguise Existing Extract panel.
668 File-AID/RDX Reference

Figure 390. View File-AID/RDX generated JCL

EDIT - File-AID/RDX Generated SQL --------------------------- COLUMNS 000 000 

Command ===> SCROLL ===> CSR 
You are now editing the JCL that File-AID/RDX has generated to perform 
the required function. Change this JCL as desired before submitting. 
****** ***************************** Top of Data ******************************
==MSG> -Warning- The UNDO command is not available until you change 
==MSG> your edit profile using the command RECOVERY ON. 
000001 //TSOID01A JOB ('OFRBAS4.3',W06P02),'JOHN_SMITH', 
000002 // CLASS=L,MSGCLASS=R,NOTIFY=TSOID01 
000003 //* 
000004 //* XFRJDISG
000005 //* --------------------------------------------------------------------
000006 //* DATA DISGUISE STEP 
000007 //* --------------------------------------------------------------------
000008 //* 
000009 //EXDISG EXEC PGM=XFREXEC,REGION=0M,MEMLIMIT=4G, 
000010 // PARM=(FR,F,B) 
000011 //STEPLIB DD DSN=CPWR.MXVJ170.CXVJLOAD,DISP=SHR
000012 // DD DSN=CPWR.MXVJ170.SXVJLOAD,DISP=SHR 
000013 //* 
000014 //SYSPRINT DD SYSOUT=(*) 
000015 //SYSUDUMP DD SYSOUT=(*) 
000016 //SYSOUT DD SYSOUT=(*) 
000017 //XVJPRINT DD SYSOUT=(*) 

Use this screen to view or edit the JCL generated by File-AID/RDX to disguise an existing extract file
with predefined disguise criteria as specified in the Disguise Control file. Use the SUBMIT command
to submit the extract request for execution. If you want to save this JCL, use the ISPF/PDF CREATE or
REPLACE command before you exit the panel.

XVJPRINT Execution Log Output

File-AID Data Privacy jobs now write execution information to XVJPRINT DD (instead of SYSPRINT
DD). If XVJPRINT DD does not exist in your JCL, File-AID will dynamically allocate XVJPRINT.

If you want the execution log output sent to a file, point XVJPRINT DD at a file (instead of
SYSOUT=(*). This file must be allocated with RECFM=FBA, LRECL=133.

Redirect File-AID/Data Solutions Report

You can choose to redirect the disguise report output produced by File-AID/Data Solutions to
FADSPRNT DD by simply adding it to the JCL. The FADSPRNT DD can point at a file or at SYSOUT.
When it points at a file and multiple objects are being disguised, use DISP=MOD.

Since the use of FADSPRNT splits the File-AID/Data Solutions report output away from the File-
AID/RDX report output, FADSPRNT and SYSPRINT must be looked at together to get a complete
picture of the job.

Set Incomplete Disguise Continuation Indicator

When during the disguise process of an object, File-AID/RDX cannot disguise some records
completely, File-AID/RDX, by default, issues a warning and removes these records from the disguised
extract file. The resulting extract file might not be loadable or usable. Possible reasons for the
incomplete disguise could be:

• Two related columns have unlike data types; error may be due to non-normalized data

• Error may be due to childless parents and/or orphans in your database

The disguise audit file for the object contains the before image for the offending records. Print it (see
Print Disguise Audit Trail on page 679) so you can determine whether the discarded records are
needed in your extract file.

The TEST parameter for the disguise (EXDISG) EXEC statement in the EXTPARMS dataset (see
EXTPARMS File on page 367) can be used to change the default behavior. When you set the parameter
Data Privacy 669

to Y, File-AID/RDX will issue a fatal error (RC=8) for this object instead of just discarding the
incomplete disguise records. When set to N, File-AID/RDX will issue warning messages for incomplete
disguise (RC=6) for an object, but continue disguise of object.

Control Card Cleanup

The last step, CLEANEXT, in the disguise jobs deletes the File-AID/RDX EXTPARMS parameter file.
Whether step CLEANEXT is commented out or executed is determined by the global job option
Delete in-stream data datasets at EOJ (page 83). If the job option is set to NO, File-AID/RDX
EXTPARMS parameter files created in the extract jobs will NOT be deleted. Keeping the datasets until
all steps run successfully allows for the restarting of the JCL at any step.

Periodically, you may want to manually delete the EXTPARMS parameter files that are no longer
needed for saved jobs to be resubmitted.

File-AID/Data Solutions Parameters

The File-AID/Data Solutions Parameters screen shown in Figure 391 is displayed when you

• Select Option 3, Parms, from the Data Privacy Menu on page 608.

Disguise criteria are created by File-AID/Data Solutions and used by File-AID/RDX.

Use this screen to specify information required by File-AID/Data Solutions to create and apply
disguise criteria.

Figure 391. File-AID/Data Solutions Parameters

File-AID/RDX ---------- File-AID/Data Solutions Parameters------------------

Command ===> 

Specify Disguise Information: 
Record layout language ===> 1 ( 1 = COBOL; 2 = PLI) 
Disguise Criteria File ===> 'TSOID01.FRSAMP.DISCRIT' 

Specify Business Rules or Field Exits Dataset Information: 
Dataset name ===> ‘TSOID01.DASAMP.BUSINESS.RULES’

Specify Disguise Audit Trail Allocation Parameters:
UNIT ===> 
Storage Class ===> 
Management Class ===> 


Enter the requested parameter information before exiting with the END command.

Record layout Language

Specify the language to be used for layouts displayed within File-AID/Data Solutions for the
objects to be disguised.

1 Use COBOL record layouts.

2 Use PL/I record layouts.

Disguise Criteria File

Specify the Disguise Criteria File (DCF) name. Disguise criteria created by File-AID/Data Solutions
will be stored in this file. The file must be a PDS or PDSE. Use Allocate Disguise Criteria File on
page 673 to create a new file. The name of Disguise Criteria File is required.
670 File-AID/RDX Reference

Business Rules or Field Exits Dataset

Specify the name of the Business Rules dataset required by any of the criteria created. The
Business Rules dataset is used by aging criteria to identify which days are holidays. See the File-
AID/Data Solutions documentation for more details on the Business dataset. This dataset is used
when the disguise criteria are applied.

Specify Disguise Audit Trail Allocation Parameters

Unit
Specify the default unit for the disguise audit trail files.

Storage Class
Specify the default storage class for the disguise audit trail files.

Management Class
Specify the default management class for the disguise audit trail files.

Allocate Disguise Control File

The Allocate Disguise Control File screen shown in Figure 392 is displayed when you

• Select Option 4, Control, from the Data Privacy Menu on page 608.

Use this screen to allocate a new disguise control file in addition to the one created during the
installation of File-AID/RDX.

Figure 392. Allocate Disguise Control File

File-AID/RDX ------------- Allocate Disguise Control File -------------------

Command ===> 

New VSAM Component names:
Cluster ===> 'TSOID01.FRSAMP.DISGUISE'
Data Component LLQ ===> DATA 
Index Component LLQ ===> INDEX 
Data component . . . . : 'TSOID01.FRSAMP.DISGUISE.DATA' 
Index component . .. . : 'TSOID01.FRSAMP.DISGUISE.INDEX' 

Specify SMS Class Information:
Storage ===> S Data ===> Management ===> T 

Space Allocation: DATA Component KSDS INDEX Component (Blank for default)
Volume serial ===> ===> 
Units ===> TRK ===> (TRKs; CYLs; RECs; K; M)
Primary ===> 1 ===> (Amount in above units)
Secondary ===> 1 ===> (Amount in above units)


When parameters are complete, use END to continue.

Use this screen to allocate the new Disguise Control file that File-AID/RDX uses as a repository to
keep track of the defined disguise criteria for objects included in an extract file.
Data Privacy 671

Press END (PF3) to allocate the SMS file, or use the CANCEL command to cancel the allocation. When
allocation is complete, File-AID/RDX displays a message: FILE ALLOCATED in the upper-right corner
of the screen.

New VSAM Component Names

Cluster
Specify the name of the VSAM cluster for the Disguise Control file to be allocated. If you don’t
use quotes around the name, File-AID/RDX will add your TSO ID as the prefix.

Data component LLQ

Low level qualifier for the data component. You may overtype this field, if your installation uses
a different data component LLQ.

Index component LLQ

Low level qualifier for the index component. You may overtype this field, if your installation uses
a different index component LLQ.

Data component
Displays the name of the data component as it will be allocated. It reflects the new cluster name
and low level qualifier after you press Enter.

Index component
Displays the name of the index component as it will be allocated. It reflects the new cluster name
and low level qualifier after you press Enter.

If a long cluster name results in data and index component names longer
than 44 characters, the cluster name portion in front of the component LLQ
is truncated.

Specify SMS Class Information

Storage
Specify the SMS storage class to use for the allocation of the file. The storage class describes the
hardware requirements of the file.

Data
Specify the SMS data class to use for the allocation of the file. The data class describes the
attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.

Management
Specify the SMS management class to use for the allocation of the file. The management class
describes the migration, backup, and retention for the file.
672 File-AID/RDX Reference

Space Allocation
Specify the space allocation values for the data and index components. Leave fields blank for
defaults.

Volume serial
Specify the volume serial of the direct access device that contains the file.

Space units
Specify one of the following storage unit types depending on how the file size is expressed:

TRK - Tracks
CYL - Cylinders
K - Kilobytes
M - Megabytes
REC - Records

Primary quantity
Specify the primary allocation quantity as specified in the space units field.

Secondary quantity
Specify the secondary allocation quantity as specified in the space units field.
Data Privacy 673

Allocate Disguise Criteria File

The Allocate Disguise Criteria File screen shown in Figure 393 is displayed when you

• Select Option 5, Criteria, from the Data Privacy Menu on page 608.

Use this screen to allocate a new disguise criteria file to be used by File-AID/Data Solutions to store
disguise criteria for individual objects.

Figure 393. Allocate Disguise Criteria File

File-AID/RDX ---------- Allocate Disguise Criteria File ---------------------

Command ===> 

File name ===> FRSAMP.DISCRIT

Management Class ===> (Blank for default)
Storage Class ===> (Blank for default)
Generic unit ===> SYSDA 
Volume serial ===> (Blank for default)
Data Class ===> (Blank for default)
Space units ===> TRK (BLK; TRK; CYL)
Primary quantity ===> 1 (In above units)
Secondary quantity ===> 1 (In above units)
Directory blk ===> 10 (Use 0 for sequential file)
Record Format ===> VB 
Record length ===> 300 
Block size ===> 27998 

When parameters are complete, use END to continue. 






Use this screen to allocate the new Disguise Criteria file that File-AID/Data Solutions uses as a
repository of disguise criteria for objects included in an extract file.

Press END (PF3) to allocate the SMS file, or use the CANCEL command to cancel the allocation. When
allocation is complete, File-AID/RDX displays a message: FILE ALLOCATED in the upper-right corner
of the screen.

File Name
Specify the name of the Disguise Criteria file to be allocated. If you don’t use quotes around the
name, File-AID/RDX will add your TSO ID as the prefix.

Management Class
Specify the SMS management class to use for the allocation of the file. The management class
describes the migration, backup, and retention for the file.

Storage Class
Specify the SMS storage class to use for the allocation of the file. The storage class describes the
hardware requirements of the file.
674 File-AID/RDX Reference

Generic Unit
Specify the device type on which the new file will reside. The names of these devices are
installation dependent.

Volume serial
Specify the volume serial of the direct access device that contains the file.

Data Class
Specify the SMS data class to use for the allocation of the file. The data class describes the
attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.

Space units
Specify one of the following storage unit types depending on how the file size is expressed:

TRK - Tracks
CYL - Cylinders
BLK - Blocks
KB - Kilobytes
MB - Megabytes

Primary quantity
Specify the primary allocation quantity as specified in the space units field.

Secondary quantity
Specify the secondary allocation quantity as specified in the space units field.

Directory quantity
For a PDS, specify the number of directory blocks. For a Sequential file, specify zero (0).

Record format
Record format must be VB (Variable length blocked)

Record length
Record length must be 300.

Block size
Block size must be 27998.
Data Privacy 675

Print Disguise Control File

The Print Disguise Control File screen shown in Figure 394 is displayed when you

• Select Option 7, Print, from the Data Privacy Menu on page 608.

Figure 394. Print Disguise Control File

File-AID/RDX ---------------- Print Disguise Control File ---------------------

Command ===> 

Primary commands: JCL view, Go to submit job

Specify Print Information:
Print format ===> O (O = Object; R = Rule)
Modify print options ===> Y (Y = Yes; N = No)
Disguise Control File ===> FRSAMP.DISGUISE)

Use this screen to request File-AID/RDX to print the contents of the disguise control file. This is a
simple report of what columns will be disguised for each object and the disguise criteria used for each
column.

It is possible for one disguise control file to point to criteria in more than one disguise criteria file.
The report is formatted in such a way that each page of the report can only contain criteria from a
single disguise criteria file. If multiple disguise criteria files are used, they will be reported on
different pages of the report.

This report does not include the detail for the disguise criteria. Use the Print Change Criteria
Function available within File-AID/Data Solutions to print the detailed disguise criteria, if required.

Print format
Specify the order you want the report to be printed:

Object. The report lists the contents of the disguise control file by object. The report will include
a list of all the disguised columns and the criteria defined for each column. Use this format to see
which columns of an object are being disguised.

Rule. The report lists the contents of the disguise control file by defined disguise rules. The report
will include a list of all rules and the columns/objects where each rule has been applied. Use this
format to see where a rule has been applied.

Modify print options

Specify whether you want to change the print parameters for this print job or not. If you specify
Yes, File-AID/RDX displays the Print Options Screen. See Print Options Screen on page 186 for a
detailed description.

Disguise Control File

Specify the name of the file that contains the related, associated, and unrelated disguise
information for extracted objects. If you specify a pattern, select a file from the “Catalog Utility
File List” (see Figure 121 on page 236).
676 File-AID/RDX Reference

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

JCL
View the JCL for the Print Disguise Control File utility. File-AID/RDX shows the Generated JCL
panel where you review and modify the print JCL. Enter the SUBMIT command to submit the
print job.

GO (G)
Submits this print request without displaying the JCL. Before issuing the GO command, make
sure you have specified the desired print option as well as the disguise control file. File-AID/RDX
will also issue a message upon completion of the job.

Print DCF Reports

When printing the contents of the Disguise Control File you have a choice of listing the disguise
information by object (Figure 395) or by rule (Figure 396).

For a PDS the member and description will be printed.

Data Privacy 677

Figure 395. Sample Print DCF Report by Object

File-AID/RDX 17.2 Disguise Control File Report by Object PAGE 1

DATE 2007-03-28
Disguise Control File . . .: TSOID01.FR45.DCF TIME 09:34:33

Disguised Object List
===================================================================================================================================
Object Name / Column Disguise Rule
------------------------------------------------------------------------------------------------------------------------------------
D-DSNLOCAT.TSOID01.DEPT
Column: LOCATION A0000001 ASSOCIATED PHONENO:TSOID01.EMP
FILE: TSOID01.FR45.DISGCRIT
Column: MGRNO R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT

D-DSNLOCAT.TSOID01.EMP
Column: EMPNO R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT
Column: PHONENO A0000001 ASSOCIATED PHONENO:TSOID01.EMP
FILE: TSOID01.FR45.DISGCRIT

D-DSNLOCAT.TSOID01.EMPPROJACT
Column: EMPNO R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT

D-DSNLOCAT.TSOID01.PROJ
Column: PROJNAME PROJECT ASSOCIATED PROJNAME:TSOID01.PROJ
FILE: TSOID01.FR45.DISGCRIT
Column: RESPEMP R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT

M-TSOID01.FASAMP.EMPLOYEE/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT

M-TSOID01.FASAMP.EMPMAST/EMPLOYEE-MASTER-FILE
Column: EMP-DATE-OF-BIRTH U0000002 UNRELATED 'TSOID01.FASAMP.EMPMAST'
FILE: TSOID01.FR45.DISGCRIT
Column: EMP-NUMBER R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT
Column: EMP-CON-HOME-PHONE A0000001 ASSOCIATED PHONENO:TSOID01.EMP
FILE: TSOID01.FR45.DISGCRIT
Column: EMP-CON-WORK-PHONE ASSOCIATED PHONENO:TSOID01.EMP
FILE: TSOID01.FR45.DISGCRIT
Column: EMP-NATL-ID-NUMBER A0000006 ASSOCIATED EMP-NATL-ID-NUMBER:'TSOID01.FASAMP.EMPM
FILE: TSOID01.R42.DISGCRIT

M-TSOID01.FR45.GDG.G0001V00/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT

M-TSOID01.FR45.GDG.G0002V00/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT
M-TSOID01.FR45.GDG.G0002V00/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT
M-TSOID01.FR45.GDG2.G0009V00/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT

Figure 396. Sample Print DCF Report by Rule

678 File-AID/RDX Reference

File-AID/RDX 17.2 Disguise Control File Report by Rule PAGE 1

DATE 2007-03-31
Disguise Control File . . .: TSOID01.FR45.DCF TIME 12:09:31

Disguised Object List
===================================================================================================================================
Disguise Rule / Column Name Object Name
------------------------------------------------------------------------------------------------------------------------------------
A0000001 ASSOCIATED PHONENO:TSOID01.EMP 
FILE: TSOID01.FR45.DISGCRIT
Column: EMP-CON-HOME-PHONE M-TSOID01.FASAMP.EMPMAST/EMPLOYEE-MASTER-FILE
Column: EMP-CON-WORK-PHONE M-TSOID01.FASAMP.EMPMAST/EMPLOYEE-MASTER-FILE
Column: LOCATION D-DSNLOCAT.TSOID01.DEPT
Column: PHONENO D-DSNLOCAT.TSOID01.EMP

A0000006 ASSOCIATED EMP-NATL-ID-NUMBER:'TSOID01.FASAMP.EMPM
FILE: TSOID01.R42.DISGCRIT
Column: EMP-NATL-ID-NUMBER M-TSOID01.FASAMP.EMPMAST/EMPLOYEE-MASTER-FILE

PROJECT ASSOCIATED PROJNAME:TSOID01.PROJ
FILE: TSOID01.FR45.DISGCRIT
Column: PROJNAME D-DSNLOCAT.TSOID01.PROJ

R0000002 RELATED EMP-NUMBER:'TSOID01.FR45.GDG.G0001V00'
FILE: TSOID01.FR45.DISGCRIT
Column: EMP-NUMBER M-TSOID01.FASAMP.EMPLOYEE/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER M-TSOID01.FASAMP.EMPMAST/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER M-TSOID01.FR45.GDG.G0001V00/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER M-TSOID01.FR45.GDG.G0002V00/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER M-TSOID01.FR45.GDG.G0003V00/EMPLOYEE-MASTER-FILE
Column: EMP-NUMBER M-TSOID01.FR45.GDG2.G0009V00/EMPLOYEE-MASTER-FILE
Column: EMPNO D-DSNLOCAT.TSOID01.EMP
Column: EMPNO D-DSNLOCAT.TSOID01.EMPPROJACT
Column: MGRNO D-DSNLOCAT.TSOID01.DEPT
Column: RESPEMP D-DSNLOCAT.TSOID01.PROJ

U0000002 UNRELATED 'TSOID01.FASAMP.EMPMAST'
FILE: TSOID01.FR45.DISGCRIT
Column: EMP-DATE-OF-BIRTH M-TSOID01.FASAMP.EMPMAST/EMPLOYEE-MASTER-FILE

U0000006 UNRELATED TSOID01.EMP
FILE: TSOID01.FR45.DISGCRIT
Column: EMPNO D-DSNLOCAT.TSOID01.EMP
Data Privacy 679

Print Disguise Audit Trail

The Print Disguise Audit Trail screen shown in Figure 397 is displayed when you

• Select Option A, Print Audit, from the Data Privacy Menu on page 608.

Figure 397. Print Disguise Audit Trail

File-AID/RDX ---------------- Print Disguise Audit Trail ---------------------

Command ===> 

Primary commands: JCL view, Go to submit job

Specify Audit Trail Information:
Audit trail dataset ===> 'TSOID01.RDXA.D010.D150722.T164243.M345'
Print format ===> H (H = Hex; C = Character)
Records to print ===> 10 (nnn = number; ALL)
Audit trail disposition ===> PK (PK = Print dataset and keep;
PD = Print dataset and delete)

Specify Batch JCL Information:
Sysout class ===> *


Use this screen to request File-AID/RDX to print the contents of the audit trail that File-AID/Data
Solutions created for each object being disguised. The audit trail print provides the before and after
images of the disguised record. An audit trail for disguised objects will only be created when your
File-AID/Data Solutions installation enforces auditing or you disguise extract request called for an
audit trail.

Audit trail dataset

Specify the file name of the disguise audit trail dataset you want printed. A separate audit trail
dataset is created for each disguised object of the extract (identified by its extract data record
number (Dnnn). The Data Privacy Summary Report created for the disguise extract lists the audit
trail dataset for each disguised object (see also Audit File on page 689). The naming convention
for each Audit Trail dataset is:

prefix.RDXA.DnnnBnnn.Dyymmdd.Thhmmss.Msss

The prefix is specified when the Extract File is disguised. Dnnn is the identifing number assigned
to the object in the Extract File. Bnnn is only used when an Audit Trail is produced for an MVS
object that uses an XREF; Bnnn is the layout number within the XREF.

Print format
Specify whether the disguise audit trail is to be printed in character or hex mode. Formatted
printing is not supported.

Hex. The disguise audit trail prints in hex mode. The Hex format will print three lines for
each data line; a character line, a zone line and a digit line.

Character. The disguise audit trail prints in character mode. The character format will print a
single line for each data line.
680 File-AID/RDX Reference

Both reports format 100 positions of the record per print line. The after images for each 100
positions only prints when the data in those positions has changed. A change flag line identifies
the changed data positions.

Records to print
You can limit the number of audit records printed. This limit count is a record count; the before
and after images are considered two records.

nnn

Maximum number of records to print.

ALL

All records.

Audit trail disposition

Enter one of the following:

PK

Print and Keep the audit trail dataset.

PD

Print and Delete the audit trail dataset.

Sysout class
Enter the sysout class for the Audit Trail Report.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

JCL
View the JCL for the Audit Trail Print utility. File-AID/RDX shows the Generated JCL panel where
you review and modify the print JCL. Enter the SUBMIT command to submit the print job.

GO (G)
Submits this Audit Trail Print request without displaying the JCL. Before issuing the GO
command, make sure you have specified the desired print options as well as the audit trail file.
File-AID/RDX will also issue a message upon completion of the job.

Printing Multiple Audit Trail Datasets

When you want to concatenate multiple audit trail datasets together and produce a separate Audit
Trail Report for each dataset with one batch job execution, edit the generated JCL before submitting
the batch job.
Data Privacy 681

Audit Trail Report

The Audit Trail Report is printed by the batch job submitted from the Print Audit Trail screen. The
report displays the audit trail contents and is printed in a character or hexadecimal format. The
report also contains summary information.

Samples of the character and hexadecimal formats of the Audit Trail Report are shown in Figure 398
on page 682 and Figure 399 on page 683.

Each page of the Audit Trail Report begins with page headings that consist of the edited dataset name,
the date and time the report was produced, the File-AID/Data Solutions release number, and the page
number.

Following the page headings is the date and time when the data file was opened for disguise, and the
TSO user ID that was used to perform the disguise. If the data file organization was VSAM-KSDS, File-
AID/RDX includes the starting position and length of the defined key.

Preceding the image of each data file disguise on the report are audit trail record headings. The first
line contains a sequential number assigned to each data file disguise, the disguise action (explained
more fully below), and the date and time the disguise occurred.

For VSAM-RRDS data files, File-AID/RDX includes the relative record number of the disguised record.

HEX Print Report Contents

When printing the audit trail contents in HEX, File-AID/RDX displays each record in a three-line
format similar to the hexadecimal mode of File-AID/MVS Edit unformatted mode. The top line
contains the character representation of the record, the middle line contains the upper half-byte of
each character in HEX, and the third line contains the lower half-byte of each character in
hexadecimal.

Up to l00 positions of the record are printed in each set of three lines. The POSITION column
immediately to the left of the record contents indicates the starting position in the record
represented by each set of three lines. For the updated records, the before image is printed, followed
immediately by the after image, if a change has occurred on that line.

When the before and after images of a changed record are displayed, the Audit Trail Report also
indicates the record positions that were changed with an asterisk (*) under each changed position.
For each three-line set of print lines that contains changed record positions, CHANGE ===> is printed
to the left and between the print lines, on the same line as the asterisks.
682 File-AID/RDX Reference

Figure 398. Audit Trail Report — Hexadecimal

02 SEP 2004 15:47:00 File-AID/RDX 4.2 DISGUISE AUDIT TRAIL REPORT PAGE: 1
EXTRACT FILE : TSOID01.R42.EXTRACT OPENED ON: 30 AUG 2004 AT 14:47:34 USER ID: TSOID01
SOURCE OBJECT: TSOID01.R42.TESTDA.EMPMAST
RECORD LAYOUT: EMPLOYEE-MASTER-FILE

====================================================================================================================================
UPDATE NUMBER: 1 ACTION: CHANGE RECORDED: 30 AUG 2004 AT 14:47:34
DATA DISPLAYED ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0

BEFORE POSITION 1 00090MARTIN EDWARD M AIRPLANE MANUFACTURER 427890125 101954920101M30000} 
ZONE FFFFFDCDECD444444444CCECDC4444D44CCDDDCDC4DCDECCCEEDCD444444444FFFFFFFFF4FFFFFFFFFFFFDFFFFFD04005005
DIGIT 0009041939500000000054619400004001997315504154613349590000000004278901250101954920101430000070D20C00
CHANGE---> * *** *** ****
AFTER POSITION 1 00090MURPHY JONATHON M AIRPLANE MANUFACTURER 427890125 101954920101M30000} 
ZONE FFFFFDEDDCE444444444DDDCECDD44D44CCDDDCDC4DCDECCCEEDCD444444444FFFFFFFFF4FFFFFFFFFFFFDFFFFFD04005005
DIGIT 0009044978800000000016513865004001997315504154613349590000000004278901250101954920101430000070D20C00
BEFORE POSITION 101 859 O'FARREL ST. SAN FRANCISCO CA 12121BILL JONES 40855558974155556981
ZONE 0FFF4D7CCDDCD4EE44444444444ECD4CDCDCCECD44CC44FFFFFCCDD4DDDCE44444444444444444FFFFFFFFFFFFFFFFFFFF
DIGIT C85906D619953023B000000000021506915392360031001212129330165520000000000000000040855558974155556981
====================================================================================================================================
UPDATE NUMBER: 2 ACTION: CHANGE RECORDED: 30 AUG 2004 AT 14:47:34
DATA DISPLAYED ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0
BEFORE POSITION 1 00100MULSTROM ROBERTA A HOLLYWOOD SEAMSTRESS 346573656 090859920111S80000{&
ZONE FFFFFDEDEEDDD4444444DDCCDEC444C44CDDDEEDDC4ECCDEEDCEE4444444444FFFFFFFFF4FFFFFFFFFFFFEFFFFFC05005007
DIGIT 0010044323964000000096259310001008633866640251423952200000000003465736560090859920111280000050C00C10
CHANGE---> ** *****
AFTER POSITION 1 00100ELLIOT ROBERTA A HOLLYWOOD SEAMSTRESS 346573656 090859920111S80000{&
ZONE FFFFFCDDCDE444444444DDCCDEC444C44CDDDEEDDC4ECCDEEDCEE4444444444FFFFFFFFF4FFFFFFFFFFFFEFFFFFC05005007
DIGIT 0010053396300000000096259310001008633866640251423952200000000003465736560090859920111280000050C00C10
BEFORE POSITION 101 4701 N. BASCOM AVE. #430 ANAHEIM CA 95126GEORGE 21555520102155559021
ZONE 0FFFF4D44CCECDD4CEC447FFF44CDCCCCD44444444CC44FFFFFCCDDCC444444444444444444444FFFFFFFFFFFFFFFFFFFF
DIGIT C470105B02123640155B0B4300015185940000000031009512675697500000000000000000000021555520102155559021
====================================================================================================================================
UPDATE NUMBER: 3 ACTION: CHANGE RECORDED: 30 AUG 2004 AT 14:47:34
DATA DISPLAYED ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0
BEFORE POSITION 1 00200JACKSON JOSEPH C ORATOR 275587177 020462920121S00000{&
ZONE FFFFFDCCDEDD44444444DDECDC4444C44DDCEDD444444444444444444444444FFFFFFFFF4FFFFFFFFFFFFEFFFFFC05000000
DIGIT 0020011322650000000016257800003006913690000000000000000000000002755871770020462920121200000050C20C00
CHANGE---> ****
AFTER POSITION 1 00200NIELSON JOSEPH C ORATOR 275587177 020462920121S00000{&
ZONE FFFFFDCCDEDD44444444DDECDC4444C44DDCEDD444444444444444444444444FFFFFFFFF4FFFFFFFFFFFFEFFFFFC05000000
DIGIT 0020059532650000000016257800003006913690000000000000000000000002755871770020462920121200000050C20C00
BEFORE POSITION 101 1401 S. BASCOM AVE. CANOGA PARK CA 94106ANGELA 21255520102125559021
ZONE 0FFFF4E44CCECDD4CEC44444444CCDDCC4DCDD4444CC44FFFFFCDCCDC444444444444444444444FFFFFFFFFFFFFFFFFFFF
DIGIT C140102B02123640155B000000031567107192000031009410615753100000000000000000000021255520102125559021
====================================================================================================================================

Character Report Contents

The character audit trail report is similar to the HEX report except that the two hexadecimal lines are
not printed. Unprintable characters are printed as blanks.
Data Privacy 683

Figure 399. Audit Trail Report — Character

02 SEP 2004 15:47:00 File-AID/RDX 4.2 DISGUISE AUDIT TRAIL REPORT PAGE: 1
EXTRACT FILE : TSOID01.R42.EXTRACT OPENED ON: 30 AUG 2004 AT 14:47:34 USER ID: TSOID01
SOURCE OBJECT: TSOID01.R42.TESTDA.EMPMAST
RECORD LAYOUT: EMPLOYEE-MASTER-FILE
====================================================================================================================================
UPDATE NUMBER: 1 ACTION: CHANGE RECORDED: 30 AUG 2004 AT 14:47:34
DATA DISPLAYED ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0
BEFORE POSITION 1 00090MARTIN EDWARD M AIRPLANE MANUFACTURER 427890125 101954920101M30000} 
CHANGE---> * *** *** ****
AFTER POSITION 1 00090MURPHY JONATHON M AIRPLANE MANUFACTURER 427890125 101954920101M30000} 
BEFORE POSITION 101 859 O'FARREL ST. SAN FRANCISCO CA 12121BILL JONES 40855558974155556981
====================================================================================================================================
UPDATE NUMBER: 2 ACTION: CHANGE RECORDED: 30 AUG 2004 AT 14:47:34
DATA DISPLAYED ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0
BEFORE POSITION 1 00100MULSTROM ROBERTA A HOLLYWOOD SEAMSTRESS 346573656 090859920111S80000{
CHANGE---> ** *****
AFTER POSITION 1 00100ELLIOT ROBERTA A HOLLYWOOD SEAMSTRESS 346573656 090859920111S80000{&
BEFORE POSITION 101 4701 N. BASCOM AVE. #430 ANAHEIM CA 95126GEORGE 21555520102155559021
====================================================================================================================================
UPDATE NUMBER: 3 ACTION: CHANGE RECORDED: 30 AUG 2004 AT 14:47:34
DATA DISPLAYED ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0
BEFORE POSITION 1 00200JACKSON JOSEPH C ORATOR 275587177 020462920121S00000{& 
CHANGE---> ****
AFTER POSITION 1 00200NIELSON JOSEPH C ORATOR 275587177 020462920121S00000{& 
BEFORE POSITION 101 1401 S. BASCOM AVE. CANOGA PARK CA 94106ANGELA 21255520102125559021
====================================================================================================================================
UPDATE NUMBER: 4 ACTION: CHANGE RECORDED: 30 AUG 2004 AT 14:47:34
DATA DISPLAYED ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0
BEFORE POSITION 1 10000ANDREWS GEORGE ACTOR 576312032 042248920131S00000{ &
CHANGE---> *******
AFTER POSITION 1 10000PEI GEORGE ACTOR 576312032 042248920131S00000{ & &
BEFORE POSITION 101 375 MERRIVALE W. SQ. SUNNYVALE CA 94134DICK 40455520104045559021
====================================================================================================================================
UPDATE NUMBER: 5 ACTION: CHANGE RECORDED: 30 AUG 2004 AT 14:47:34
DATA DISPLAYED ----+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8----+----9----+----0
BEFORE POSITION 1 15000MURPHY RONALD L PAINTER 987654321 120255920201S50000{ ø 
CHANGE---> *** ***
AFTER POSITION 1 15000SIMPSON RONALD L PAINTER 987654321 120255920201S50000{ ø 
BEFORE POSITION 101 7716 HAWTHORNE AVE. SANTA CLARA CA 95025JEFF 31255520103125559021
====================================================================================================================================
02 SEP 2004 15:47:00 File-AID/RDX 4.2 DISGUISE AUDIT TRAIL REPORT PAGE: 18
EXTRACT FILE : TSOID01.R42.EXTRACT OPENED ON: 30 AUG 2004 AT 14:47:34 USER ID: TSOID01
SOURCE OBJECT: TSOID01.R42.TESTDA.EMPMAST

Summary Information
Summary information is printed on the last page of the Audit Trail Report. See Figure 400 on page
684. It contains the following information:

• Name of the audit trail dataset that was printed.

• Number of data file records that were changed.

• The number of members updated if the edit dataset was a PDS.

• Name of the updated data file that created the audit trail.

• Names of the record layout dataset and member specified for the update and the record layout
dataset type (SEQ for sequential, PDS for partitioned, PAN for CA Panvalet, LIB for CA Librarian).

• Names of the record layout XREF dataset and member specified for the update (if an X was
specified in the Record layout usage field).

• Names of the selection criteria dataset and member, if existing selection criteria was used for the
update. If temporary selection criteria was used during for the update, the literal ** TEMPORARY
** is printed.

• Date and time the data file was closed.

• The system ID on which the data file was updated.

684 File-AID/RDX Reference

Figure 400. Audit Trail Report — Summary

22 JUL 2015 15:47:00 File-AID/RDX 17.2 DISGUISE AUDIT TRAIL REPORT PAGE: 18
EXTRACT FILE : TSOID01.R42.EXTRACT OPENED ON: 30 AUG 2004 AT 14:47:34 USER ID: TSOID01
SOURCE OBJECT: TSOID01.R42.TESTDA.EMPMAST

SUMMARY INFORMATION

AUDIT TRAIL FILE PRINTED: TSOID01.RDXA.D010.D150722.T164243.M345

TOTAL RECORDS CHANGED: 50
TOTAL RECORDS UNCHANGED: 0
TOTAL RECORDS DISCARDED: 0

RECORD LAYOUT: EMPLOYEE-MASTER-FILE
SOURCE OBJECT: TSOID01.R42.TESTDA.EMPMAST 
EXTRACT FILE : TSOID01.R42.EXTRACT CLOSED ON: 22 JUL 2015AT 14:47:41 SYSTEM ID: CW01

************************************************* -> E N D O F R E P O R T <- **************************************************

Executing Print Audit Trail Independently in Batch

You can execute the Print Audit Trail function as a separate step in a batch job by coding the JCL
shown in Figure 401. This process can be useful when you want to print multiple audit trail datasets
in one batch print job.

Figure 401. Print Audit Trail JCL

//DISGAUDT EXEC PGM=UDASOLUT,REGION=8M

//STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ170.CXVJLOAD
// DD DISP=SHR,DSN=CPWR.MXVJ170.SXVJLOAD
//SYSPRINT DD SYSOUT=*
//SYSLIST DD SYSOUT=*
//DD01 DD DISP=(OLD,KEEP,KEEP),
// DSN=’TSOID01.prefix.RDXA.D010.D150722.T164243.M345’
//SYSIN DD *
$$DD01 APRINT
/*

Audit Trail Print Execution Return Codes

The audit trail print execution return codes are summarized in Table 76.

Table 76. Print Execution Return Codes

RC Explanation Error Description
0 Job ran to completion. None.
8 Job may have ended prematurely. Dataset related error.
12 Job may have ended prematurely. I/O related error.
16 Severe error occurred. System error.
Data Privacy 685

Miscellaneous Data Privacy Topics (Using DCF)

This section provides information about the following topics:

• Db2 Alias, Synonym, and View Support

• VSAM PATH Support for Disguise
• Size Allocation of Disguise Extract File
• Unlike Column/Field Data Types and Disguise Criteria
• Data Privacy JCL

Refer to the File-AID Data Privacy documentation for information on the corresponding topics for
using File-AID Data Privacy.

Db2 Alias, Synonym, and View Support

Disguise criteria can be defined for tables and views but not for alias and synonyms. Relationships
cannot be created to an alias or a synonym but they can be used as the driving object in the extract
and will be resolved to the base table. If disguise criteria are defined on a table and the table is
extracted via an alias or a synonym, the disguise criteria defined on the table will be applied.

Views are treated as independent objects, just like tables. If disguise criteria are defined on a view, it
will be applied only when the extract uses that view. If disguise criteria are defined on a table, they
are applied when the extract uses that table name. If an extract uses a view on the table that has
disguise criteria defined, it will not be applied; the criteria must be defined on the view for it to be
applied. If a single table is extracted using different views, the disguise criteria will have to be defined
on each view. There will not be any validation that the same column is disguised the same way in
each view; it will be your responsibility to define criteria that will disguise the same data in the same
way for each view and the base table.

VSAM PATH Support for Disguise

A relationship cannot be established to a VSAM AIX or PATH. An extract that specifies an AIX as the
driving object will process the AIX as a single, standalone object; it will not extract the base object or
the objects related to the base object. Extracting via a PATH is not supported. Defining disguise
criteria on an AIX or PATH is not supported. If disguise criteria is defined on the base object, that
criteria is not applied.

Size Allocation of Disguise Extract File

Early in the disguise processing File-AID/RDX compares the amount of space used in the undisguised
extract file with the amount of space allocated to the output disguised extract file. If the disguised
extract file is smaller than the amount of space used in the undisguised extract file, then the
disguised extract file is reallocated before the disguise processing starts. Be aware that your site may
limit this allocation request and issue a warning in that case.

This reallocation is only available for sequential files (DSORG=PS) and does
not occur for a PDS disguise extract file.

Unlike Column/Field Data Types and Disguise Criteria

File-AID/RDX supports relationships between unlike columns/fields in application relationships (see
also Table 9 Column/Field Types Mapping on page 148). When a disguise rule is applied to a data
column/field that is related to another column/field in a different format, then data conversion is
required for the disguised value.
686 File-AID/RDX Reference

When complex disguise criteria are applied (and unlike column conversions are by definition
complex disguise criteria), then the column of origin is disguised and both values are stored in a
lookup table. When the data value from an unlike column is required to have the same value
replaced, then that value is converted to the format of the origin, it is looked up in the disguise value
table, the replacement value is retrieved, and the replacement value is then converted to the format
of the current (non-origin) column.

Special Consideration for Numeric to Character Conversion

If the data at the origin is in numeric format (SMALLINT, INTEGER, DEC, or FIXPIC) and the
character field is in a non-normalized format, the resulting disguised value in the character field will
be normalized (see Normalized Format). If it is desired that the character field remain non-
normalized, use the character field when creating your disguise criteria.

If the number of digits in the character field is greater than the number of digits that can fit into the
non-origin, related numeric field (SMALLINT, INTEGER, DEC, or FIXPIC), then you need to use a
partial column relationship to identify the digits in the character field that do fit. See Extended
Column Relationship Definition on page 169 for more information on how to create a partial column
relationship.

Normalized Format
Numeric data will be right justified and zero filled on the left when converted to character. If the
origin has a non-zero scale, i.e. digits to the right of the decimal point, the decimal point will be
explicitly filled in with the appropriate number of positions to its right. A minus sign, if needed, will
be in the left-most character position.

Data Privacy JCL

The data privacy JCL shown in Figure 402 performs the batch portion of the disguise process and
generates the appropriate reports. File-AID/RDX automatically generates the JCL through the online
screens for disguise existing extract file and extracts with disguise.

Figure 402. Data Privacy JCL

//EXDISG EXEC PGM=XFREXEC,REGION=0M,MEMLIMIT=4G,

// PARM=(FR,F,B)
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
//SYSPRINT DD SYSOUT=(*) 
//SYSUDUMP DD SYSOUT=(*) 
//SYSTERM DD SYSOUT=(*) 
//SYSOUT DD SYSOUT=(*) 
//XVJPRINT DD SYSOUT=(*) 
//RDXMLIB DD DSN=File-AID/RDX-message-library,DISP=SHR
//MSGLIB DD DSN=File-AID/Data Solutions-message-library,DISP=SHR
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,DISP=SHR 
//EXTRACT DD DSN=pre-disguise-extract-file-name,DISP=(OLD,KEEP,KEEP)
//DISGCTL DD DSN=disguise-control-file-name,DISP=(SHR)
//FARULES DD *
privacy rules repository name
nnnnnnnnnn (dynamic privacy rules project ID)
//DD01BR DD DSN=File-AID/Data Solutions-business-rules-file-name,DISP=(SHR)
//AUDIT DD *
audit-file-name-prefix
/* 
//DISGEXT DD DSN=disguise-extract-file-name, 
// DISP=OLD 
//CHKPT DD DSN=checkpoint data file, 
// DISP=SHR 
//* 

XFREXEC is the File-AID/RDX program name.

Data Privacy 687

EXDISG is the name of Data Disguise EXEC statement. The parameter information in the PARM field
in the EXEC statement must have the following format:

Table 77. EXEC Statement PARM Field—Disguise Extract Step (EXDISG)

Default
Parameter Length Description
Value
Product FR 2 File-AID/RDX
Option F 1 File-AID/RDX option number.
Operating Mode B 1 B : Batch

The following DD statements are required for data disguise:

Table 78. DD Statements—Data Disguise
DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD)
XVJPRINT Output for data disguise report.
RDXMLIB Library containing File-AID/RDX messages.
MSGLIB Library containing File-AID/Data Solutions messages.
EXTPARMS File containing the disguise parameters (see EXTPARMS File on page 367).
EXTRACT Pre-disguised extract file to be disguised.
DISGCTL File name of the Disguise Control File (DCF).
DD01BR File name of File-AID/Data Solutions business rules dataset.
FARULES Privacy Rules Repository name and Dynamic Privacy Rules Project ID.
XREFxxx File name of XREF file for the MVS object xxx; when extracting MVS objects.
AUDIT Prefix for the File-AID/Data Solutions data disguise audit trail dataset name(s).
DISGEXT File name of the disguised extract file.
CHKPT Optional Checkpoint Data File.
FAJPATH (obsolete) File name of the Java-Info-file(FAJPATH) for File-AID Data Privacy
FAJOPTS (obsolete) File name of the Java-Info-file(FAJOPTS) for File-AID Data Privacy
FAIPADDR (obsolete) File name of the Java-Info-file(FAIPADDR) for File-AID Data Privacy
FAEXPATH (obsolete) File name of the Java-Info-file(FAEXPATH) for File-AID Data Privacy

If your site requires special SMS information for the disguise split files, you can insert an SMSMODEL
DD statement with a file name you want File-AID/RDX to use as a model for the disguise split files
(see Figure 403). If no SMSMODEL DD is present, File-AID/RDX models SMS information on the file
pointed to by the EXTRACT DD in the JCL.

If you want the SMSMODEL DD statement in all of your disguise jobs, you can edit skeleton member
XFRJDISG in the File-AID SXVJSENU library.

Figure 403. SMSMODEL DD statement

//SMSMODEL DD DSN=sms.model.datasetname,
// DISP=SHR

File-AID/RDX will verify that the disguise extract dataset referred to by the DISGEXT DD is at least
the same size as the extract dataset referred to by the EXTRACT DD. If the DISGEXT dataset is smaller,
messages DISG0030, DISG0070, and DISG0080 will print and the DISGEXT dataset will be re-
allocated automatically. If your site does not want the re-allocation to be attempted, add a
X37DEACT DD statement to the EXDISG step as shown in Figure 404 on page 688 to deactivate this
feature.

If you want the X37DEACT DD statement in all of your disguise jobs, you can edit skeleton member
XFRJDISG in the File-AID SXVJSENU library.
688 File-AID/RDX Reference

Figure 404. X37DEACT DD statement

//X37DEACT DD DUMMY

Return Codes
An execution return code (RC) appears in the output listing. For return codes other than 0, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return Code Description

0 Job ran to completion.
4 Job ran to completion, warnings issued.
Job ran to completion, records with disguise
6
failures not written to extract file.
8 Job completed with error.
16 Severe error, job aborted.

Data Privacy Reports

After the data privacy job is submitted and executed, the File-AID/RDX Disguise reports are
generated.

Split File Allocation Report

The Split File Allocation Report shown in Figure 405 shows the file allocation parameters for the split
files File-AID/RDX created for disguise process.

Figure 405. Split File Allocation Report

DISG1065 INFO -
SUCCESSFUL ALLOCATION OF SPLIT FILE DSN:TSOID01.RDX.S002.D050425.T163623
ORG=PS,RECFM=V,RECLEN=286,BLKSIZE=27998,UNIT=SYSDA,ALCUNIT=CY
L,SPACE=1,EXTEND=1
DISG1065 INFO -
SUCCESSFUL ALLOCATION OF SPLIT FILE DSN:TSOID01.RDX.S005.D050425.T163624
ORG=PS,RECFM=V,RECLEN=176,BLKSIZE=27998,UNIT=SYSDA,ALCUNIT=CY
L,SPACE=1,EXTEND=1

File-AID Data Privacy Summary Report

The Data Privacy Summary Report shown in Figure 406 shows the file names for the input and output
extract files and the Disguise Control File, followed by the data privacy information for each
disguised object.
Data Privacy 689

Figure 406. Data Privacy Summary Report

File-AID DATA PRIVACY SUMMARY REPORT

====================================
INPUT EXTRACT FILE: TSOID01.RDX.EXTRACT.D150722.T115732
DISGUISED EXTRACT FILE: TSOID01.EXTRACT
DISGUISE CONTROL FILE: TSOID01.R42.DCF
---------------------------------------------------------------------------------------- START: 2015/07/22 11:57:40

Object: D-DSNLOCAT.TSOID01.EMP
ROWS: 42
COLUMN: EMPNO RULE: R0000004 DESC: RELATED EMPNO:TSOID01.EMP
AUDIT FILE: TSOID01.RDXA.D010.D150722.T115741.M345 
SET 1 ENCR-====================================================================================
SET 1 ENCR-Records Read 42, Selected 42, Fields Changed 42, Invalid 0

Object: M-TSOID01.FASAMP.EMPMAST/EMPLOYEE-MASTER-FILE
ROWS: 3
COLUMN: EMP-NUMBER RULE: R0000004 DESC: RELATED EMPNO:TSOID01.EMP
FILE: TSOID01.R42.DISGCRIT
Object: D-DSNLOCAT.TSOID01.V_EMP
ROWS: 42
COLUMN: EMPNO RULE: R0000004 DESC: RELATED EMPNO:TSOID01.EMP
FILE: TSOID01.R42.DISGCRIT

------------------------------------------------------------------------------------------ END: 2015/07/22 11:57:42

The Data Privacy Summary Report first lists the pre-disguised (input) and disguised (output) extract
file names. Then, if the disguise used the File-AID/RDX Disguise Control File (DCF), it lists the
disguise control, and business rules file names that were used during the disguise process. Or, if the
disguise used File-AID Data Privacy, the report identifies the Disguise Privacy Project Name and the
Privacy Rules Repository Name.

The disguise report then lists the following information for each disguised object:

Object
The name of the object preceded by object type identifier (D for Db2, M for MVS).

Rows
Identifies the number of extracted Db2 rows or MVS records for the object.

Column
Name of the column/field that the following disguise rule is assigned to.

Rule
Displays the rule assigned to the column with the rule description.

File
Displays the name of the disguise criteria file, if the disguise criteria is stored in a PDS.

Audit File
Displays the name of the disguise audit trail file for the disguised object, if an audit trail was
requested for the disguise (see Create Audit Trail on page 667). This is the file name you specify
when you request printing an audit trail (see Print Disguise Audit Trail on page 679).
690 File-AID/RDX Reference

Set n Disguise Method

Identifies the set number of the disguise method that was applied to the above listed object
columns/fields. It also lists the number of records read, selected for disguise, fields changed, and
invalids.

If an error occurs during the disguise for an object, the error information will also be displayed in
this place.

This information may not be displayed when the disguise values have been
propagated from columns/fields that have already been disguised in a
previous step. The columns/fields are disguised, unless an error message
indicates otherwise.

At the end of the report a note identifies how many of the extracted objects were not scheduled to be
disguised.
 691

File-AID/RDX Utilities
Overview
Option 6, Utilities, allows you to manage some of your File-AID/RDX Disguise Control, Disguise
Criteria, and Audit files and to allocate relationship files.

RDX Utilities Menu

When you select Option 6, Utilities, File-AID/RDX displays the Utilities Menu as shown in Figure 407.

Figure 407. Utilities Menu

File-AID/RDX ------------------ Utilities Menu ------------------------------

Option ===> Profile: RDXMENU

Primary commands: menu-option

Saved Request Utilities: 
1 Update - Update Saved Extract Requests 
2 JCL/Overrides - Execute Saved Request (ESR) options

Extract File Utilities: 
3 Compress - Compress or Decompress Extract File 
4 Generate DDL - Generate DDL from Extract File 


Options 1 and 2 are utilities for Saved Requests. Enter the option number to select the desired utility:

1 - Update
Displays the Update Saved Extract Requests panel where you can specify to update a previously
saved extract request with the current relationship information from a relationship file.

2- JCL/Overrides
Displays the Execute Saved Request (ESR) Options panel where you can specify to generate the
JCL and optional override file to execute previously saved extract, load, extract and load, and
delete requests.

Options 3 and 4 are utilities for Extract files. Option 3 is a utility for Extract file compression and
Option 4 is a utility to convert masked DDL information from a File-AID/RDX Extract file into
readable form. Enter the option number to select the desired utility:

3 - Compress
Displays the Extract File - Compress Utility panel where you can run utilities to compress or
decompress the extracted data in an extract file.
692 File-AID/RDX Reference

4- Generate DDL
Displays the Generate DDL Utility panel where you can specify the File-AID/RDX extract file from
which to convert the masked DDL information into readable form.

Update Saved Extract Requests

The Update Saved Extract Requests screen shown in Figure 408 is displayed when you

• Select Option 1, Update, from the Utilities Menu.

Use this screen to initiate a batch job that updates your saved extract requests with the current
information from the specified Relationship file.

This utility function operates against a library of saved requests. Any changes made to a saved request
will be made to a copy of the saved request; the original saved request will not be changed.

The Update Saved Extract Requests utility allows processing of “cloned” requests (see also
Modify Extract Request on page 227). The utility detects them during batch processing
and prints the informational message ‘Cloned request updated. Internal
disguise information links removed. This request is no longer
classified as a clone. ’. The consequences of updating a cloned request are that
File-AID/RDX will not maintain any internal links to the load or disguise information from
the original request.

Figure 408. Update Saved Extract Requests

File-AID/RDX --------------- Update Saved Extract Requests

-------------------
COMMAND ===> 

Primary Commands: JCL view, GO to submit job 

Specify Request Information: 
Validate Action ===> R (R = Report only; U = Update requests)
Request to Copy ===> A (A = All; U = Updated only) 
Request File ===> FRSAMP.EXTCRIT 
Member ===> 
New Request File ===> 

Update requests that use the following SSID and relationship file: 
SSID ===> DSN (SSID; ALL) 
Relationship File ===> FRSAMP.RELATION 

On this screen you specify the Extract Request library to be updated and whether to copy only the
changed requests or all requests into the new Extract Request library. You also identify the Db2
subsystem from which to gather catalog information and the Relationship file from which to update
the relationship information in the extract requests. Only the requests that were created using the
specified Relationship File will be updated, all others will be bypassed.

Enter GO to submit the job or enter JCL to review the JCL before submitting.

After you enter GO, File-AID/RDX displays the message: JOB SUBMITTED and returns to the Utilities
Menu.

Specify Request Information:

Validate Action
Specify whether to generate a report only (R) or update the requests (U) as well.
File-AID/RDX Utilities 693

Request to Copy
Specify whether to copy only the updated requests (U) or all requests (A) into the new request
library, if the request file is a PDS.

Request File
Specify the name of the existing extract request to be updated. If you don’t use quotes around the
name, File-AID/RDX will add your TSO ID as the prefix. The existing request file will not be
updated. Changed request data will be copied into the new request file.

Member
Specify the member name of the existing extract request to be updated, if the request file is a
PDS. Specifying a pattern selects all matching member names for processing at execution time.

Leaving the member field blank tells File-AID/RDX that the new request file
should be a sequential file and File-AID/RDX will prefill the Create New File
panel accordingly (see also Create New File on page 334).

New Request File

Specify the name of the new extract request file into which the updated request data is to be
copied. If you don’t use quotes around the name, File-AID/RDX will add your TSO ID as the
prefix. Leaving this field blank will use the original file as the output file.

If the new file does not exist, File-AID/RDX displays the Create New File panel where you specify
the file allocation values for the new request file (see Create New File on page 334).

If the old request file is a PDS, make sure that the new one is a PDS also.

Update requests that use the following SSID and relationship file:

SSID
Specify the subsystem ID of the Db2 subsystem from where you want to gather catalog
information to update the request. Specify ALL if catalog information is to be gathered from all
Db2 subsystems listed in the request.

Relationship File
Specify the name of the Relationship file from which to update the relationship information in
the extract requests.

Only the requests that were created using the specified Relationship File will
be updated, all others will be bypassed.
694 File-AID/RDX Reference

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

JCL
View the JCL for the Update Saved Extract Requests utility (see Figure 409). File-AID/RDX shows
the Generated JCL panel where you review and modify the JCL. Enter the SUBMIT command to
submit the job.

GO (G)
Submits this Update Saved Extract Requests job request without displaying the JCL. Before issuing
the GO command, make sure you have specified the existing and new request files, the
relationship file and Db2 subsystem. File-AID/RDX will also issue a message upon completion of
the job.

Update process
In effect, a new extract request will be created using the Driving Object specified in the original
request. Any user modifications made in the original request will be applied to the new request; this
will include the following:

• Extract Options
• Extract Scope - object view line commands
• (Exclude, All, Passthru)
• Extract Scope object sampling criteria
• Extract Scope - relationship view line commands
• (Exclude)
• Extract Scope relationship sampling criteria
• Extract Scope relationship navigation criteria
• Selection Criteria

The updated request is identical to the old request except for the changes made to the set of related
objects; the following will not change:

• Unrelated objects
• Input (External) Key File
• IMS and Output Key File
• Extract File

Errors
There may be situations in which the updated saved request is no longer valid, for example, if the
driving object no longer exists. Whenever error checking can detect that the new request is invalid, it
is marked “not executable” and cannot be executed. An example for marking a request “not
executable” can occur when a relationship has been added to an IMS object or Output Key, which
requires defining the IMS key file in order for the request to actually be executable.

Any request marked “not executable” can be corrected with the online interface (Option 2 Extract);
correcting the request removes the not executable indicator.

File-AID/RDX currently does integrity checking whenever changes are made to the navigation
settings. The integrity checking is done to verify that the extract will be loadable. In the online
interface, the user has the option to accept or reject the objects identified in the integrity warning.
Since this update will be done in batch, this option will not be available; accept any changes
identified by the integrity warning.
File-AID/RDX Utilities 695

“Modeled” Relationships
File-AID/RDX allows extract requests to be created for Db2 objects that are not in the Relationship
file by choosing to model the relationships defined for a different set of Db2 objects (see Using
Relationship Definitions Across Db2 Subsystems on page 199). Any request that was created prior to
File-AID/RDX Release 4.5 using modeling will be converted into a single table extract, unless
relationships have been added to the relationship file for the driving object.

Modeled requests created with File-AID/RDX Release 4.5 and higher include the record type 57
Model: (see record type 57 on page 371). When a request with record type 57 is encountered File-
AID/RDX

• First checks if relationships have been added to the driving object to make it directly related to
other objects. 
If this is the case, these relationships are now the controlling factor and used to update the
request.

• If no direct relationship exists to the driving object then File-AID/RDXretrieves relationship

information in the same way that it was originally done using the type 57 Model object and then
compares it with the contents of the request. If this relationship information has changed then
the changes are reflected in the saved request. If there are no relationship changes, the request
remains unchanged.

Batch Job
Figure 409 on page 695 shows a sample job. The JCL parameters are based on the values in the
Prepare, Product Option, and Subsystem tables as specified during the execution of Install Manager.

Figure 409. Update Saved Extract Requests JCL

//RDXUPDRQ EXEC PGM=XFREXEC, REGION=8192K,

// PARM=(FR,L,B) 
//* 
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
//PARMS DD * 
REQDS 'input request dataset name' 
OREQDS 'output request dataset name' 
MEMBER 'input member name' 
SSID 'subsystem ID' 
UPDATE 'All Valiated or Updated only indicator' 
RELDS 'relationship-file' 
//* 
//EXTPARMS DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,
// DISP=SHR 
//RDXMLIB DD DSN=’File-AID-message-library’,DISP=SHR 
//SYSOUT DD SYSOUT=* 
//REPORT DD SYSOUT=* 
//ERRORRPT DD SYSOUT=* 
//SYSUDUMP DD SYSOUT=* 
//SYSPRINT DD SYSOUT=* 
//SYSTERM DD SYSOUT=* 

The parameter information in the PARM field in the EXEC statement must have the following format:

Default
Parameter Length Description
Value
Product FR 2 File-AID/RDX
Option L 1 File-AID/RDX option number.
Operating Mode B
B 1
Batch
696 File-AID/RDX Reference

The following DD statements are required:

DD Statement Description
STEPLIB File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD).
PARMS The following parameters are expected:

• REQDS: input extract request file

• OREQDS: output extract request file

• MEMBER: member name or pattern if request file is a PDS

• SSID: Db2 subsystem ID

• UPDATE: Copy All or Updated only indicator

• RELDS: relationship file

EXTPARMS File containing the load parameters (see EXTPARMS File on page 367).
RDXMLIB The library containing File-AID/RDX messages.
SYSOUT Output class for error messages and reports.
REPORT Output class for reports.
ERRORREPT Output class for error reports.
SYSPRINT Standard output stream.
SYSTERM Output class for runtime errors.

Return Codes
An execution return code (RC) appears in the output listing. For return codes 4, 8, and 16, an error
code and message indicating the specific problem also appear in the listing. In general, the return
codes can be summarized as follows:

Return Description
Code
0 Job ran to completion.
4 Job ran to completion with warning messages issued.
8 Job may have ended prematurely. Dataset or security related error.
16 Severe error, job aborted.

Report
A report (Figure 410 on page 697) will be produced during the Update Saved Request processing
which will include a line for each member processed and details of the actions taken for each request.
Members which are not processed because they did not meet the specified criteria or were not extract
requests are identified with a message stating the reason.
File-AID/RDX Utilities 697

Figure 410. Sample Update Saved Extract Requests Report

File-AID/RDX 17.2 Update Saved Request Utility (No Update) PAGE 1

DATE 03
-28-2007
Request File . . . . . . .: TSOID01.FR45.REQUEST Member: * TIME 01
:14 PM
New Request File . . . . . : TSOID01.FR45.REQUEST.NEW Requests to Copy : Updated only
Relationship File . . . . .: TSOID01.FR45.RELATION SSID: All 

Update Activity Report 
===========================================================================================================================
=========
Member Message Action / Description
-------- -------- -------------------------------------------------------------------------------------------------------
----------
T1850002 RDXEEnnn Request validated - no changes. 
T1850003 RDXEE180 Relationship deleted - A relationship in the request is no longer in the relationship file. 
Parent. . .: D-DSNLOCAT.FR.OBJC
Dependent: D-DSNLOCAT.FR.OBJA
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.FR.OBJC
Dependent: D-DSNLOCAT.FR.OBJA
RDXEE182 The extract request DPSI options have been adjusted due to relationship changes.
T1870003 RDXEE184 No relationships found for driving object - request converted to single table extract.
T1880003 RDXEE184 No relationships found for driving object - request converted to single table extract.
T1890003 RDXEE184 No relationships found for driving object - request converted to single table extract. 
T1900003 RDXEE184 No relationships found for driving object - request converted to single table extract.
T1910003 RDXEE184 No relationships found for driving object - request converted to single table extract. 
T2030003 RDXEE180 Relationship deleted - A relationship in the request is no longer in the relationship file. 
Parent. . .: D-DSNLOCAT.FR.BV_P147791_DRV
Dependent: D-DSNLOCAT.FR.BV_P147791_SLF_REF
RDXEE180 Relationship deleted - A relationship in the request is no longer in the relationship file. 
Parent. . .: D-DSNLOCAT.FR.BV_P147791_SLF_REF
Dependent: D-DSNLOCAT.FR.BV_P147791_DEP
RDXEE180 Relationship deleted - A relationship in the request is no longer in the relationship file. 
Parent. . .: D-DSNLOCAT.FR.BV_P147791_SLF_REF
Dependent: D-DSNLOCAT.FR.BV_P147791_SLF_REF
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.FR.BV_P147791_DRV
Dependent: D-DSNLOCAT.FR.BV_P147791_SLF_REF
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.FR.BV_P147791_SLF_REF
Dependent: D-DSNLOCAT.FR.BV_P147791_DEP
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.FR.BV_P147791_SLF_REF
Dependent: D-DSNLOCAT.FR.BV_P147791_SLF_REF
RDXEE182 The DPSI options have been adjusted due to relationship changes.
T2080003 RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.SYSIBM.SYSCHECKS
Dependent: D-DSNLOCAT.SYSIBM.SYSCHECKDEP
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.SYSIBM.SYSCHECKS
Dependent: D-DSNLOCAT.SYSIBM.SYSCHECKS2
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.SYSIBM.SYSTABCONST
Dependent: D-DSNLOCAT.SYSIBM.SYSKEYCOLUSE
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.SYSIBM.SYSTABLES
Dependent: D-DSNLOCAT.SYSIBM.SYSCHECKS
File-AID/RDX 17.2 Update Saved Request Utility (No Update) PAGE 1
DATE 03
-28-2007
Request File . . . . . . .: TSOID01.FR45.REQUEST Member: All TIME 01
:14 PM
New Request File . . . . . : TSOID01.FR45.REQUEST.NEW Requests to Copy : Updated only
Relationship File . . . . .: TSOID01.FR45.RELATION SSID: All 

Update Activity Report 
============================================================================================================================
========
Member Message Action / Description
-------- -------- -------------------------------------------------------------------------------------------------------
---------
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.SYSIBM.SYSTABLES
Dependent: D-DSNLOCAT.SYSIBM.SYSCONSTDEP
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.SYSIBM.SYSTABLES
Dependent: D-DSNLOCAT.SYSIBM.SYSRELS
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.SYSIBM.SYSTABLES
Dependent: D-DSNLOCAT.SYSIBM.SYSTABCONST
RDXEE181 Relationship added - A relationship in the relationship file has been added to the extract request.
Parent. . .: D-DSNLOCAT.SYSIBM.SYSTABLES
Dependent: D-DSNLOCAT.SYSIBM.SYSTABLES_HIST
698 File-AID/RDX Reference

JCL/Overrides Utility
The Execute Saved Request (ESR) Options screen shown in Figure 411 is displayed when you

• Select Option 2, JCL/Overrides, from the Utilities Menu.

Use this screen to initiate a process that generates the JCL and optional override files to execute
previously saved requests. Eligible saved requests can either be extract, load, extract and load, and
delete requests.

The creation of the File-AID/RDX Execute Saved Request JCL will typically be done by the Application
Programmer as part of preparing or staging for turnover to Production Control.

Execute Saved Request is supported for requests created by File-AID/RDX

Release 4.5 and above. Extract and load requests which were created prior
to File-AID/RDX Release 4.5 will execute, but they are not supported for this
functionality.

Figure 411. Execute Saved Request (ESR) Options

File-AID/RDX -------------- Execute Saved Request (ESR) Options

-------------
COMMAND ===> 

Primary Commands: ENTER to select Requests, GEN to generate 

Specify Requests to be Processed: Members selected. . . .: 1
Request File ===> FRSAMP.EXTCRIT 
Member name ===> ORDER (* or pattern for selection list) 

Specify Execute Saved Request Files: 
ESR JCL File ===> FRSAMP.ESRJCL 
Object Override File ===> FRSAMP.OBJOVERR 
SC Override File ===> FRSAMP.SCOVERR 
JCLOUT for extract JCL ===>
JCLOUT for load JCL ===>

Select files and DD statements to generate for each request:
N Gen ESR JCL N Include JCLOUT DD for Job scheduler input
N Gen Object override file N Include OVERRIDE DD for Object override
N Gen SC override file N Include SCOVERRD DD for SC override 
Object Override File Options: 
Override DB2 table names ===> N (Y = Yes; N = No) 
Override File Usage ===> 2 (1 = Global; 2 = Per Request) 


On this screen you specify the input saved request and output ESR (Execute Saved Request) JCL files
as well as any override information.

Enter GEN to process the selected options.

When the message “Generate process complete” displays, verify that the desired JCL and/or
override files have been generated.

Specify Requests to be Processed:

Request file
Specify the name of a previously saved request file for which you want to generate the JCL for
execution at a later time. Eligible saved requests include load, extract and load, and delete
requests.
File-AID/RDX Utilities 699

Member name
Specify the member name of the saved request(s). Leave blank or use a pattern to select from the
Request File Member List (see Request File Member List on page 706). You can select multiple or
all members from the list for processing.

1. If you specify a sequential request file as input, File-AID/RDX fills the Member name field
with TEMPNAME and uses TEMPNAME as the member name in the output PDS(s). After
processing is completed, rename the fixed TEMPNAME member name in the output
PDS(s) and the PARM entry in the ESR JCL to avoid overwriting when processing another
sequential request file.
2. For cloned or modeled requests object override files will not be generated and when
executing ESR JCL for cloned or modeled requests, any included object override files will
be ignored.

Members selected
Identifies how many saved request members have been selected from the request file.

Specify Execute Saved Request Files:

ESR JCL File

Specify the name of the output file to store the generated JCL for execution at a later time. The
ESR JCL file must be PDS - member names will be the same names as the request file member
names. When the input request file is sequential, File-AID/RDX defaults to TEMPNAME as the
member name.

Object Override File

Specify the name of the Object Override file that stores the original and new object and
environment names for execution of saved requests at a later time. The Object Override file must
be sequential for Override File Usage 1=GLOBAL and PDS for Override File Usage 2=Per Request.

SC Override File
Specify the name of the SC (Selection Criteria) Override file that stores the original and new
selection criteria of the driving object for execution of saved requests at a later time. The SC
Override file can be sequential or PDS.

JCLOUT for extract JCL

Specify the name of the JCLOUT file for the extract JCL. The JCL generated when the ESR job is
run will be generated to the file named on the JCLOUT DD statement. If the dataset is a PDS, the
member name of the generated JCL will be the same as the request name. The JCLOUT file can be
sequential or PDS.

JCLOUT for load JCL

Specify the name of the JCLOUT file for the load JCL. The JCL generated when the ESR job is run
will be generated to the file named on the JCLOUT DD statement. If the dataset is a PDS, the
member name of the generated JCL will be the same as the request name. The JCLOUT file can be
sequential or PDS.
700 File-AID/RDX Reference

The JCLOUT files can specify any MVS output file that is capable of accepting JCL. Specifically, the
dataset characteristics should include RECFM=FB, LRECL=80.

It is your responsibility to manage the assignment of dataset names such that there will not be
conflict and that there will be proper control and flow of the JCL into and through any scheduling
systems.

If any of the ESR JCL or override files don’t exist, you must specify the allocation parameters in the
Create New File screen (Figure 175 on page 334).

Select files and DD statements to generate for each request:

Gen ESR JCL

Select with Y to create JCL members for execution at a later time. Specify N (default) and JCL
members will not be created.

Gen Object Override File

Select with Y to include the object override file in the ESR JCL. Specify N (default) and the Object
override file will not be generated.

Gen SC Override File

Select with Y to include the SC (Selection Criteria) override file in the ESR JCL. Specify N (default)
and the SC (Selection Criteria) override file will not be generated.

Include JCLOUT DD for Job scheduler input

Select with Y to generate DD for Job scheduler input in the ESR JCL. Specify N (default) and the
DD for Job scheduler input will not be included.

Include OVERRIDE DD for Object override

Select with Y to generate DD for use of Object Override in the ESR JCL. Specify N (default) and
the DD for use of Object Override will not be included.

Include SCOVERRD DD for SC override

Select with Y to generate DD for use of Selection Criteria Override in the ESR JCL. Specify N
(default) and the DD for use of Selection Criteria Override will not be included.

If you only want to generate or update the SC override file, you must also
specify Y for Gen Object Overrides File.

Object Override File Options:

Override DB2 Table Names

Specify Y to update the object override file to include Db2 Table names. Specify N and File-
AID/RDX will not include Db2 table names in the object override file update.
File-AID/RDX Utilities 701

Override File Usage

Specify 1 for a global override file. The global override file contains all override entries from all
selected requests. Remember that the Object Override File must be sequential for global.

Specify 2 (default) for an override file per request. Remember that the Object Override File must
be a PDS for this option.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

GEN
Processes the selected ESR options without displaying any JCL. Before issuing the GEN command,
make sure you have specified the desired request members from the request file, the ESR JCL file,
any override files, and the desired processing options. File-AID/RDX will issue the message
“Generate process complete” upon completion of the process.

Override File Entries

The top (header) line in an override file identifies with which File-AID/RDX release the request
was created and the date and time of the last override file generation.

An entry can be generated for the Override file for each item that can be overridden at execution
time. Except for SCROBJO, SCROBJN, TRGOBJO, and TRGOBJN, each entry will include both the
old-value and the new-value for the item to be overridden; initially, both values will be the same.

The entries for the combined Creator ID/Table name tags (SCROBJO, SCROBJN, TRGOBJO, and
TRGOBJN) are not generated when File-AID/RDX generates an override file; they must be entered
manually. They only list one value, either the old or the new value, but they must be in pairs,
with the OLD value followed by the NEW value, for example, SCROBJO (Source object OLD)
followed by SCROBJN (Source object NEW). Likewise, TRGOBJO and TRGOBJN must also be in
pairs.

The existing entries within the Override File will be retained and new entries will be added as
needed. An entry will be added for any item specified in the selected requests that is not already
named as the old-value in an existing entry for that item type. All added entries will be at the end
of the file.

Table 79. Object Override Identifiers

Override Identifier Description
SCRCRE Source Db2 Creator ID
SCRLOC Source Db2 Location ID
SCROBJO Source object (Creator ID/Table name) OLD
SCROBJN Source object (Creator ID/Table name) NEW
SCRSSID Source Db2 Subsystem ID
SCRTAB Source Db2 Table name
TRGCRE Load Target Db2 Creator ID
TRGLOC Load Target Db2 Location ID
TRGOBJO Load Target object (Creator ID/Table name) OLD
TRGOBJN Load Target object (Creator ID/Table name) NEW
TRGSSID Load Target Db2 Subsystem ID
TRGTAB Load target Db2 Table name
702 File-AID/RDX Reference

Table 79. Object Override Identifiers (Continued)

Override Identifier Description
DSN MVS Dataset names (various file names, see list
under Values to Override)

As an example, suppose that you are creating a Global Override file for the following three
requests:

Request 1 - Extract, SSID=DB01, Tables = FR.TAB1, FR.TAB2, FR.TAB3

Request 2 - Extract, SSID=DB01, Tables = FR.TAB1, FR.TAB2, FRTST.TAB3
Request 3 - Extract, SSID=DB01, Tables = FRQA.TAB1,MVS=FR.TEST.FILE

The generated Override file would contain the following entries with the old entries starting at
position 10 and the new entries at position 140 (not valid format):

Pos 10 Pos 140

----+----1----+----2 4----+----5----+----6-
* Old New
SRCSSID DB01 DB01 
SRCLOC CW01DB01 CW01DB01 
SRCCRE FR FR
SRCTAB TAB1 TAB1
SRCTAB TAB2 TAB2
SRCTAB TAB3 TAB3
SRCCRE FRTST FRTST
SRCCRE FRQA FRQAT
DSN FR.TEST.FILE FR.TEST.FILE

If you want to provide an override value for a specific Creator ID/table name combination,
manually insert the SCROBJO/SCROBJN or TRGOBJO/TRGOBJN tags as paired tags with the OLD
followed by the NEW value, for example:

Pos 10 Pos 140

----+----1----+----2 4----+----5----+----6-
* Creator ID Table Name
SCROBJO FRTST TAB3
SCROBJN LASTTEST NEWTAB4

Values to Override
The values which can be overridden will include the following items but more may be added as
design progresses.

• USERID
• SSID
• Location
• Creators
• MVS file names
• MVS record layout file names
• MVS XREF file names
• Input (External) Key file
• Related MVS object names
• Extract File
• IMS and Output Key File
• IMS Extract Request File
• Selection Criteria
• Temporal Table parameters
• Tables - The separate option Override Table Names allows you to specify whether to
include Db2 Table names in the generated overrides
• Combined Source and Target objects (CreatorID/Table name).
File-AID/RDX Utilities 703

Override Layout

Editing the object override file can require quite a bit of scrolling since the fields are all in fixed
positions and Db2 object names are 128 positions. Editing with File-AID/MVS formatted view allows
the old and new object names to be displayed together and easily edited.

Override Processing
After the Override file has been created and populated, you can edit the file to provide the new-values
to be used instead of the original values for each item to be overridden.

Use standard ISPF EDIT or File-AID/MVS EDIT to make the necessary modifications to the Override
file. You might choose to have this modification done programmatically rather than by manually
editing the file.

Entries within the Override File can be marked as a comment by coding * in the 1st position of the
entry.

Apply Overrides
As each selected request is processed, the values within the request will be modified based on the
replacement values specified within the Override file. When the old-value within the request matches
the old-value specified in the Override file, the old-value within the request will be replaced with the
new-value specified in the Override file.

The processing of the Override file does not depend on the file entries being in any specific order.
New entries can be appended to the existing data and the file may be manually updated so there is no
way to predict the order of the entries.

The first entry for each item old-value will be used and any duplicate entries will be bypassed. If
duplicate old-values are found with different new-values, a warning message will be issued but it will
not affect the return code for the job. Any entries in the Override file which do not match the item
values used in the request will not be processed. Any item in the request which does not have a
matching entry in the Override file will not be overridden.

When the new values from the Override file for target objects in a Load
Request are non-existing objects, File-AID/RDX will NOT create the new
target objects.

Save updated request

If the request is being updated as part of Update Saved Request processing, the updated request is not
saved to a permanent location. The updated request is used to generate the JCL required to execute
the updated request; the original request is not altered.

Update request report

A report identifies what changes were made to each request. When an override is applied to the value,
the report includes the item name with the original and replacement values. When there is no
override for the value, the report will include the original value and an indication that the value was
not overridden. The message for each value will include information identifying the item type; for
example, Db2 Creator, Extract File.

Original object names in Extract File

Override processing is very similar to the online Modify request processing when object names are
changed (see also Modify Extract Request on page 227). During Modify processing the original object
names are retained and written to the Extract File so that Data Disguise can be based on the original
object names.
704 File-AID/RDX Reference

Override processing also records the original object names into the Extract File so that they will be
available for processing at Load time and for use by Disguise.

Managing the Override datasets

You choose how you want to manage the Override files. You may choose to have a separate Override
file for each File-AID/RDX request (Override File Usage = 2) or to have multiple File-AID/RDX requests
share the same Override file (Override File Usage = 1).

It is expected that you will choose to define Override files by application or environment, that is,
each application or environment will have its own set of Override files.

When you request that an Override file be populated, any existing override entries within the file will
be retained. File-AID/RDX will write an override entry for each old-value-name that is not already in
the Override file. All existing override entries will be retained and any new entries will be added to
the end of the existing entries. An entry is defined as the pair of old-value plus new-value.

Separate Override Files

For separate Override files (Override File Usage = 2), you must specify a PDS/PDSE for the Override
files. This will cause the File-AID/RDX Utility to generate a separate override file for each request; the
Override file member name will be the same as the request member name.

Shared Override Files

For shared Override files (Override File Usage = 1), you must specify a sequential file for the Override
file. File-AID/RDX will write an override entry for each old-value in the selected requests that is not
already in the Override file; the entries required for all the selected requests will be written to the
same Override file.

Editing the Override Files

It is your responsibility to maintain control over the Override file and its contents. The correctness of
the Override file being produced is critical to the success of the override process. For example, the
Override files can be created and populated by an Application Programmer and used as the base for
the Override files which will actually be used to execute a saved request.

To be sure that there is a correct entry for each item specified within the requests, the populating of
the Override file and updating of new-value information can be done at production cut-over time.
The Override file must be fully up-to-date when the requests are executed.

Prior to being used, the Override files must be updated with any new-values which are to be used in
the new environment. All old-values to be overridden must be in the Override file. The person
responsible for providing the new-values will edit the Override file. No update functionality will be
provided within File-AID/RDX. Edit the Override file outside of the product with the edit tool of your
choice or edit the file programmatically.

When a new value in the object override file is blank, the old value will not be overridden,
except for the Override Identifier TRGLOC (Load Target Db2 Location ID), which has its own
rules for handling blank values for old and new values. TRGLOC allows old and new values to
be blank. If the new value for TRGLOC is blank, it will override any old value of TRGLOC with
a blank. Likewise, a non-blank new value will override a blank old value.

It is expected that updating will be limited to a few people who are authorized to make these changes.

Editing the SC (Selection Criteria) Override Files

When editing a SC (Selection Criteria) Override file (Figure 412 and Figure 413 on page 705), do not
change any object information, that means, do not change the Db2 SELECT * FROM statement, or the
MVS file information (file, record layout and XREF names) in the DEFINE BLOCKS and SELECT
File-AID/RDX Utilities 705

statements. The Object Override file takes care of all the object override information. The intent of
the SC (Selection Criteria) Override is to allow you to change the selection values only, not to rewrite
the complete selection criteria. When changing the selection criteria for Db2, DO NOT code the
ending ; (semi-colon).

Figure 412. Sample Db2 SC (Selection Criteria) Override File

********************************* Top of Data **********************************

SELECT * FROM FRSAMP.ORDER_TABLE 
WHERE ORDER_NUMBER = 'BT33-C' 
OR CUST_NUM = 'CW3375' 
******************************** Bottom of Data ********************************

Figure 413. Sample MVS SC (Selection Criteria) Override File

********************************* Top of Data **********************************

DEFINE BLOCKS=SELECTION, 

LAYOUT_DSNAME=TSOID01.FRSAMP.LAYOUTS,
LAYOUT_MBRNAME=CUSTOMER, 

INITIAL_SKIP=0, 
THEN_SELECT=1, 
THEN_SKIP=0, 

MAXIMUM_TO_SEARCH=ALL, 
MAXIMUM_TO_SELECT=ALL 

SELECT SET=1,LAYOUT=PROD001-CUSTOMER-TABLE 
IF 
FIELD_NAME=CUSTOMER-NUMBER, 
POSITION=1,LENGTH=6,OPERATOR=EQ, 
TYPE=T,VALUE=CW3375 

******************************** Bottom of Data ********************************

Job Scheduler Usage

The customer will define jobs to their job scheduler package in whatever way is appropriate for their
scheduling package. Basically, the behavior will be as follows with each job verifying that the
previous step ran successfully.

Extract request

Step1: Use FR utility to create ESR JCL and override files. Include DD statements for OVERRIDE and
JCLOUT in the ESR JCL.

Job 1: Modify override files with any changes needed to run the extract

Job 2: Submit the ESR JCL to populate JCLOUT for extract

Job 3: Submit the JCLOUT for extract

Load request

Step1: Use FR utility to create ESR JCL and override files. Include DD statements for OVERRIDE and
JCLOUT in the ESR JCL.

Job 1: Modify override files with any changes needed to run the load

Job 2: Submit the ESR JCL to populate JCLOUT for load

Job 3: Submit the JCLOUT for load

706 File-AID/RDX Reference

Extract continue with load request

Step1: Use FR utility to create ESR JCL and override files. Include DD statements for OVERRIDE and
JCLOUT in the ESR JCL. Specify a different file for JCLOUT for extract and JCLOUT for load.

Job 1: Modify override files with any changes needed to run the extract

Job 2: Modify override files with any changes needed to run the load

Job 3: Submit the ESR JCL to populate JCLOUT for extract. The second step generated will be ESR for
load; it must include the OVERRIDE and JCLOUT for load.

Job 4: Submit the JCLOUT for extract file. This will run the extract and populate JCLOUT for load.

Job 5: Submit the JCLOUT for load.

Request File Member List

The Request File Member List Screen shown in Figure 414 is displayed when you specify a pattern in
the Request File Member name field of the Execute Saved Request (ESR) Options screen.

This screen displays the member list of a saved extract request file. Use the ALL primary command or
the S line command to select all, one or multiple members.

Figure 414. Request File Member List Screen

File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8

Command ===> Scroll ===> CSR

Press END after selecting request(s) to return to ESR Options

Primary commands: ALL, Find, Size, END
Line commands: S = Select
Request File ===> FRSAMP.EXTCRIT 

Member Description Status
-------- -------------------------------------------------- ---------- 
_ DB2VSAM db2 to vsam extract 
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE 
_ MIKE1 Member List 
_ NODB2 mcust with db2 deleted 
_ ORDER DB2 - LOCATION.TSOID01.CUSTOMER 
_ PART1 Member List 
_ SELCUST test select customer 
_ TESTA test saving the criteria 
******************************* Bottom of data ********************************

Request File
Displays the request file name you specified on the Execute Saved Request (ESR) Options screen.

The lower part of the screen displays a listing of the file’s members.

Member
Member name in the saved extract request file or extract criteria file. The member names are
displayed in alphabetical order.

Description
Text that was entered in the Description field when the extract request was created. If you left the
field blank, File-AID/RDX sets the description to the driving object type and name.
File-AID/RDX Utilities 707

Status
Displays SELECTED after a member has been selected with the S line or the ALL primary
command.

Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:

S (Select)
Selects this extract request member.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

ALL
Selects all members in the Request File Member List.

END
Returns to the Execute Saved Request (ESR) Options screen. The Members selected field is updated
with the number of members you selected in the Request File Member List (see also Members
selected on page 699).

FIND (F)
Searches the member list for the specified string and scrolls the list to display the first matching
entry at the top of the displayed entries. Use RFind to repeat the search.

SIZE (S)
Increases the scrollable area to display more entries at a time by hiding some of the screen header
lines. See Figure 108 on page 221 for an example. Size is a toggle switch so enter Size again to
return to the original format.

Generated ESR JCL

Figure 415 on page 708 shows a sample of the generated Execute Saved Request (ESR) JCL. Review and
then submit this JCL to execute a saved request including any specified override files.
708 File-AID/RDX Reference

Figure 415. Generated ESR JCL

//Job card information', 

//*-------------------------------------------------------------------
//COPYTLIB EXEC PGM=IEBCOPY 
//SYSPRINT DD SYSOUT=* 
//SYSOUT DD SYSOUT=* 
//INDD0 DD DISP=SHR,DSN=TSOID01.ISPF.ISPPROF 
//INDD1 DD DISP=SHR,DSN=File-AID/RDX.SXVJTENU 
//INDD2 DD DISP=SHR,DSN=ISP.SISPTENU 
//OUTDD DD DSN=&&TBLIBS, 
// DISP=(NEW,PASS,DELETE), 
// SPACE=(TRK,(30,15,15),RLSE), 
// DSNTYPE=LIBRARY,LRECL=80 
//SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(4,4)) 
//SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(4,4)) 
//SYSIN DD * 
COPY INDD=INDD0,OUTDD=OUTDD 
S M=(ISPSPROF,ISPCMDS) 
COPY INDD=INDD1,OUTDD=OUTDD 
S M=((ISPSPROF,,R),RDXPROF) 
COPY INDD=INDD2,OUTDD=OUTDD 
COPY INDD=INDD3,OUTDD=OUTDD
/* 
//*-------------------------------------------------------------------
//EXSAVREQ EXEC PGM=IKJEFT01,DYNAMNBR=80, 
// REGION=8192K,COND=(7,LT) 
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
//RDXMLIB DD DISP=SHR,DSN=File-AID/RDX-message-library 
//SYSPROC DD DSN=Combined-File-AID/RDX-CLIST-libraries,DISP=SHR
//ISPPLIB DD DISP=SHR,DSN=File-AID/RDX-panel-library 
// DD DISP=SHR,DSN=ISP.SISPPENU 
// DD DISP=SHR,DSN=ISR.V?R?M?.ISRPENU 
//ISPMLIB DD DISP=SHR,DSN=File-AID/RDX-message-library 
// DD DISP=SHR,DSN=ISP.SISPMENU 
// DD DISP=SHR,DSN=ISR.ISRMENU 
//ISPSLIB DD DISP=SHR,DSN=File-AID/RDX-skeleton-libraries 
// DD DISP=SHR,DSN=ISP.SISPSENU 
// DD DISP=SHR,DSN=ISR.ISRSENU 
//RDXUISPF DD DISP=SHR,DSN=TSOID01.ISPF.ISPPROF
//ISPTLIB DD DISP=(OLD,DELETE),DSN=&&TBLIBS 
//EXTPARMS DD 
PROD FR 
FUNC M 
VVRRMM 170200 
TEST N 
SQLID USER 
TERM Y 
CAPS ON 
RPTTITLE File-AID/RDX 17.02.00................... 
MSGPREF RDX 
JC1 PJCL1 
JC2 PJCL2 
JC3 PJCL3 
JC4 PJCL4 
JC5 PJCL5 
TERMTYPE 3278 
UHQL TSOID01.prefix 
CWLPRCST E 
//OVERRIDE DD DISP=SHR,DSN=object_override_file(member) 
//SCOVERRD DD DISP=SHR,DSN=selection_criteria_override_file(member) 
//SYSOUT DD SYSOUT=* 
//REPORT DD SYSOUT=* 
//ERRORRPT DD SYSOUT=* 
//RDXSQLCD DD SYSOUT=* 
//SYSUDUMP DD SYSOUT=* 
//SYSPRINT DD SYSOUT=* 
//SYSTERM DD SYSOUT=* 
//ISPPROF DD DISP=(NEW,DELETE,DELETE), 
// DSN=&&BATPROF, 
// DCB=(BLKSIZE=3120,LRECL=80,DSORG=PO,RECFM=FB), 
// SPACE=(TRK,(1,,1)),UNIT=SYSDA 
//ISPCTL1 DD DISP=NEW,UNIT=SYSALLDA,SPACE=(TRK,(1,1)), 
// DCB=(LRECL=80,BLKSIZE=6160,RECFM=FB) 
//ISPLOG DD SYSOUT=*,DCB=(RECFM=VA,LRECL=125,BLKSIZE=129) 
//SYSTSPRT DD SYSOUT=* 
//SYSTERM DD SYSOUT=* 
//SYSPRINT DD SYSOUT=* 
//SYSUDUMP DD SYSOUT=* 
//SYSTSIN DD * 
ISPSTART CMD(XFREXED FR,M,B) NEWAPPL(RDX) PASSLIB
//* 
//PARMS DD * 
REQDS request_file 
MEMBER member 
//*
File-AID/RDX Utilities 709

Report
A report (Figure 416) will be produced during the Execute Saved Request processing.

Figure 416. Sample Execute Saved Requests Utility Report

File-AID/RDX 17.02.00 Execute Saved Requests Utility PAGE 1

DATE 08-26-2009
Request File. . . . . . . .: TSOID01.FRSAMP.EXTCRIT TIME 09:36 AM



Update Activity Report 
===================================================================================================================================
Member Message Action / Description 
-------- -------- ----------------------------------------------------------------------------------------------------------------
ORDER RDXEE196 Member selected for processing. 
* * * END OF REPORT * * *
RDXI128 1 Extract requests tested for updates. 
******************************** BOTTOM OF DATA *************************************************************************************

ESR Basic Methodology

This section documents a basic methodology that allows extract and load requests to be put into
production using the File-AID/RDX “Execute Saved Request” (ESR) capability. There are many
possible variations that can be used to handle special needs. This sample procedure presents simple
and more complex examples. Some additional explanations assist users who have more complex
needs.

Requirements
This ESR capability requires that saved requests be available and that they are in a form that is
suitable for production work:

• All input and output files must have proper security and are owned by an appropriate group.

• Security must allow processing of:

– extract requests

– load requests

– delete requests

The basic approach is that the “Online ISPF Dialog” is executed and all validation and JCL generation
is done as if a user were at a terminal, but if anything at all requires a user to take action, then the
request execution is abandoned. The utility executes TSO and ISPF in batch and the RDX dialogs are
being executed with a “GO” command as if done by a user. Because of this it must be considered what
user-id is to be used for authority during the running of these jobs. Authority should be considered
for two basic areas:

1. access to data objects for extract and/or load

2. ability to write to output files such as extract files and output key files.

We will describe two simple requests, an extract and a load. Then we will describe a level of further
sophistication by making use of overrides.

After describing the four jobs just mentioned then we will discuss, but not in specific detail the
various options and RDX capabilities that can be supported.

Extract Example
1. Inspect an extract request for production readiness:
710 File-AID/RDX Reference

a. In Option 2, EXTRACT, select the extract request file and the member name, for example
‘FR.SAMPLE.REQUEST(EXT0101)’, to display it in the Extract Menu.
b. Look at the extract file definition. Does it have an appropriate name? If it does not, then
change it by selecting Extract Menu Option 7, Extract File.
c. Save the changed extract request (Extract Menu Option 12).
d. Look to see if there is an external key file specified for Extract Menu Option 4, Input Key File.
Input Key File is used for supplying keys for the driving object. Is that named appropriately?
If not, change it by selecting Extract Menu Option 4.
e. Save the changed extract request (Extract Menu Option 12).
f. Look to see if there are any output key files specified for Extract Menu Option 6, Output Key
Files. If so, are they named appropriately? If not, change it by selecting Extract Menu Option
6.
g. Save the changed extract request (Extract Menu Option 12).
2. Once the extract request is ready for production go to Option 6, UTILITIES, where you can
generate the JCL to be used for the production job. 
This example uses extract request in ‘FR.SAMPLE.REQUEST(EXT0101)’. This extract uses the File-
AID/RDX sample tables. The driving object is ORDER_TABLE.
a. Select Option 6, UTILITIES from the File-AID/RDX Primary Option Menu.
b. Select Option 2, JCL/Overrides. This option displays the Execute Saved Request (ESR) Options
panel.
c. Fill in your values for the Request File, Member name, ESR JCL File, and JCLOUT for extract
JCL fields.
d. Set Gen ESR JCL to Y
e. Set Include JCLOUT DD for Job Scheduler Input to Y. 
The JCLOUT option and DSN says that you do not want JCL generated to be submitted to the
internal reader, but rather to be written to the JCLOUT file and it will be your own
responsibility to get it executed.
f. Enter GEN on the command line. 
Watch for message ”I332 Generate process complete”.
g. Review the contents of the generated ESR job that was just created, in this example
FR.SAMPLE.ESR.JCL. This utility dialog is set up so that if 20 extract requests are selected then
20 JCL members will be put into the ESR output file. In this case, ESR JCL File was specified as
FR.SAMPLE.ESR.JCL and since only one extract request, EXT0101, was selected, then only one
member is put into FR.SAMPLE.ESR.JCL. The same member name as the extract request, in
this case EXT0101.
h. The first thing to call your attention to is at the bottom of this file. The last 4 lines of this
member are:

//PARMS DD * 
REQDS FR.SAMPLE.REQUEST
MEMBER EXT0101 
//*

REQDS is the keyword that identifies the dataset name of the file containing the requests to
be processed. MEMBER is the member name of the request to be processed. There can be
multiple member name parameters. Each one will be processed. What does it mean to “be
processed”? It means that the request is going to have a “G” (go) line command issued. Since
each request has a type record, the ESR job determines if the request is an Extract, Load, or
Delete request and the ISPF dialog is executed “almost” like it would be if there was a human
at a terminal. “Almost” is important though, because even warning messages become fatal
errors, since there is no-one at a terminal to make changes.

Now, here is the full JCL that was generated by the above procedure:
File-AID/RDX Utilities 711

000001 //DFHEJK0T JOB ('OFRBAS16.3.1DEV',4W1805),'RDX TEST',CLASS=A, 

000002 // MSGCLASS=X,NOTIFY=&SYSUID,REGION=81M 
000003 /*JOBPARM SYSAFF=CW01 
000004 //* TEST 
000005 //* PROFILE JOBCARD 
000006 //* XFRJESR
000007 //COPYTLIB EXEC PGM=IEBCOPY 
000008 //SYSPRINT DD SYSOUT=* 
000009 //SYSOUT DD SYSOUT=* 
000010 //INDD0 DD DISP=SHR,DSN=ISP.SISPTENU 
000011 //INDD1 DD DISP=SHR,DSN=DFHEJK0.ISPF.ISPPROF 
000012 //INDD2 DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..SXVJTENU 
000013 //OUTDD DD DSN=&&TBLIBS, 
000014 // DISP=(NEW,PASS,DELETE), 
000015 // SPACE=(CYL,(2,1,15),RLSE), 
000016 // DSNTYPE=LIBRARY,LRECL=80 
000017 //SYSUT3 DD SPACE=(CYL,(4,4)),UNIT=SYSDA 
000018 //SYSUT4 DD SPACE=(CYL,(4,4)),UNIT=SYSDA 
000019 //SYSIN DD * 
000020 COPY INDD=INDD0,OUTDD=OUTDD 
000021 S M=(ISPSPROF,ISPCMDS) 
000022 COPY INDD=INDD1,OUTDD=OUTDD 
000023 S M=((ISPSPROF,,R),RDXPROF) 
000024 COPY INDD=INDD2,OUTDD=OUTDD 
000025 /* 
000026 //*------------------------------------------------------------------- 
000027 //EXSAVREQ EXEC PGM=IKJEFT01,DYNAMNBR=80, 
000028 // REGION=8192K,COND=(7,LT) 
000029 //STEPLIB DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..CXVJLOAD 
000030 // DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..SXVJLOAD 
000031 //RDXMLIB DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..SXVJMENU 
000032 //SYSPROC DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..CXVJCLIB 
000033 // DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..SXVJCLIB 
000034 //ISPPLIB DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..SXVJPENU 
000035 // DD DISP=SHR,DSN=ISP.SISPPENU 
000036 //ISPMLIB DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..SXVJMENU 
000037 // DD DISP=SHR,DSN=ISP.SISPMENU 
000038 //ISPSLIB DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..CXVJSENU 
000039 // DD DISP=SHR,DSN=SYS2.CW.&CWGAVJ..SXVJSENU 
000040 // DD DISP=SHR,DSN=ISP.SISPSLIB 
000041 //RDXUISPF DD DISP=SHR,DSN=DFHEJK0.ISPF.ISPPROF 
000042 //ISPTLIB DD DISP=(OLD,DELETE),DSN=&&TBLIBS 
000043 //EXTPARMS DD * 
000044 PROD FR 
000045 FUNC M 
000046 VVRRMM 170200 
000047 TEST Y 
000048 SQLID FRDBA 
000049 TERM Y 
000050 CAPS ON 
000051 RPTTITLE File-AID/RDX 17.02.00 
000052 MSGPREF RDX 
000053 JC1 PJCL1 
000054 JC2 PJCL2 
000055 JC3 PJCL3 
000056 JC4 PJCL4 
000057 JC5 PJCL5 
000058 TERMTYPE 3278 
000059 UHQL DFHEJK0.RDX 
000060 CWLPRCST E 
000061 LINESPP 55 
000062 //JCLOUT DD DISP=SHR,DSN=FR.SAMPLE.ESR.JCLOUT(EXT0101) 
000063 //SYSOUT DD SYSOUT=* 
000064 //REPORT DD SYSOUT=* 
000065 //ERRORRPT DD SYSOUT=* 
000066 //RDXSQLCD DD SYSOUT=* 
000067 //SYSUDUMP DD SYSOUT=* 
000068 //SYSPRINT DD SYSOUT=* 
000069 //ISPPROF DD DISP=(NEW,DELETE,DELETE), 
000070 // DSN=&&BATPROF, 
000071 // DCB=(BLKSIZE=3120,LRECL=80,DSORG=PO,RECFM=FB), 
000072 // SPACE=(CYL,(1,1,15)),UNIT=SYSDA 
000073 //ISPCTL1 DD DISP=NEW,SPACE=(CYL,(1,1)),UNIT=SYSDA, 
000074 // DCB=(LRECL=80,BLKSIZE=6160,RECFM=FB) 
000075 //ISPLOG DD SYSOUT=*,DCB=(RECFM=VA,LRECL=125,BLKSIZE=129) 
000076 //SYSTSPRT DD SYSOUT=* 
000077 //SYSTSIN DD * 
000078 ISPSTART CMD(XFREXED FR,M,B) NEWAPPL(RDX) PASSLIB 
000079 //* 
000080 //PARMS DD * 
000081 REQDS FR.SAMPLE.REQUEST 
000082 MEMBER EXT0101 
000083 //*
712 File-AID/RDX Reference

Some Notes Concerning the Generated JCL

• The first 5 lines are the Jobcard from the current user’s File-AID/RDX profile (Option 0). These
five lines are not literally the same lines that will be used to execute the request, but they will
indeed be regenerated into the job that will execute the request. Therefore, the userid that you
want used for the production job should be used when generating the ESR JCL.

• Notice that there is a COPYTLIB job step that is the first part of the ESR JCL. This step creates a
temporary ISPTLIB dataset. It copies a number of members into this dataset from three separate
libraries. One of these members is RDXPROF from the TSO userid’s ISPF profile dataset (see
INDD1). Again, if it is significant, then use the userid of someone who has clearance to run
production jobs.

• The step that does the actual request validation and JCL generation is step EXSAVREQ. Look at
DD named RDXUISPF. It has the DSN of the current TSO userid.

• Look at line 48 and 59. Line 48 has the SQLID set by the current user. Make sure this is acceptable
for a production job. Line 59 is the User’s High Level Qualifier. Again, make sure that this is
suitable for use in a production job.

• Note line 62. This JCLOUT is optional. When used, the ESR job will write the customized JCL to
this file. When not used, the ESR job writes the customized JCL to the internal reader with the
assumption that it will be executed right away. Some options that might be taken would be to set
the JOBCARD to nulls or comments and then stack multiple requests after line 82, making sure
that a valid job card is programmatically placed before the contents of the JCLOUT file.

Load Example
After the above extract has been run, the extracted data is put into the specified extract file, in this
case, FR.SAMPLE.ORDER.EXTRACT. For the sake of this example, let’s take this same data and load it
to a new set of tables with the creator-id of FRUSER and save the load request as member LOD0201 in
the same request file, FR.SAMPLE.REQUEST.

You can use the same method to produce the ESR JCL as for the extract request. Or you can take the
ESR JCL generated for the extract, FR.SAMPLE.ESR.JCL(EXT0101), and modify it by only changing the
MEMBER from EXT0101 to LOD0201 in lines 62 and 82 and save as member LOD0201. Either will
work.

Putting this “Into Production”

Now you are ready to put the ESR job FR.SAMPLE.ESR.JCL into production. The most common way to
do this is to put the ESR JCL into the production JCL repository and scheduler and let the generated
JCL go directly to the internal reader. By ESR JCL let us be very clear - it is the above JCL
FR.SAMPLE.ESR.JCL, not what gets written to JCLOUT.

Why Not Take the Contents of JCLOUT?

Because this has been custom generated based on conditions at the time that the ESR JCL gets
submitted, which should be immediately before the actual request gets submitted. DD names and
DISP settings can be affected. Especially in the case of load jobs, work file sizes will be calculated
based on the actual work to be performed on a table by table basis. Also for a load, there is at least
one file, the LCT (load control table) that needs to be customized based on the row counts that are in
the extract dataset.

Customizing and Tailoring

Frequently, an extract will have selection criteria that needs to be adjusted on a run by run basis. How
is this handled? There are a number of different ways to deal with this. The method you choose will
depend on the nature of your needs. If the extract request is not sensitive and does not need to be
“locked down” then opening the request and changing the selection criteria is an easy way. But if this
File-AID/RDX Utilities 713

is a production job then usually the request will be locked. The following is a list of potential ways to
customize a saved request without actually altering the request. The list is meant to be in an order of
simple to more complex, but what is simple or complex can be dependent upon your needs.

• Use an external key file.

This is defined as a standard part of an extract request. It simply means that a file is presented
with a list of key values. The key values always apply to columns of the driving object. They do
not have to be against columns/fields that are in an index. There can be only one external key
file and it can only be against the one and only driving object. How does this permit
customization? Well, each and every time that the extract is run the contents of this key file
might be different. The number of records in it for one run might be 1 and for the next run it
might be 100 million records. The external key file can be locked down and controlled by
security and even the contents might be controlled by an installation controlled program that
populates the file under controlled conditions.

• Use overrides to alter the selection criteria.

The ESR mechanism allows an extract request to be treated as a “template” that can have
substitutions applied to it. For extract requests, there can be two override files, Object Override
File and SC Override File. SC Override File is dedicated to altering the selection criteria. The
overrides are provided in a file. As a consequence, it is possible to have one extract request with
multiple override files, each of which is a locked down MVS dataset that is selected just before the
ESR job is run. Also, it is possible that the contents of the override file is more tightly controlled
by a program that selects the contents of the file.

• Use overrides to alter what tables are extracted from.

Depending on circumstances this can be either very simple or very complex. This was designed
for a situation similar to the following:

A company has a set of tables that describe sales reporting. The company’s data is separated
by regions, NORTH, SOUTH, EAST, and WEST. Each region has an identically configured set
of 50 tables that describes the sales activities. The 50 tables each have a Creator-ID of the
region (i.e. NORTH, SOUTH, EAST, or WEST).

There may be some tables that are common to all regions. This is of no special consequence.
There is a need to extract data from one region at a time and load it into a set of tables that
will be used for analysis. An extract request is created to operate on one region, say the WEST
region.

Once satisfied that it operates as desired, create the ESR job, then construct three override
files as described in Override File Entries on page 701 and Override Processing on page 703 to
create:

• One to override all creators from WEST to EAST

• Another to override all creators from WEST to NORTH

• A third one to override all creators from WEST to SOUTH.

What does the override file look like?

In this case it will simply have one record. It will have SRCCRE in positions 1-8 and WEST in
positions 10-138 and EAST in positions 140-268. This has the effect of changing all creator-id
that matches WEST in the extract to a creator-id of EAST as a temporary override. Then four
different ESR jobs can all use the same extract request: one with no overrides, one that
overrides WEST to EAST, one that overrides WEST to NORTH, and one that overrides WEST to
SOUTH.

Building upon the two extract and the load examples above (see Step 2 on page 710 of the Extract
Example), create two more ESR jobs, this time with additional override options:
714 File-AID/RDX Reference

a. Fill in your values for the Request File, Member name, ESR JCL File, Object Override File,
and JCLOUT for extract JCL fields.
b. Set Gen ESR JCL to Y
c. Set Include JCLOUT DD for Job Scheduler Input to Y. 
The JCLOUT option and DSN says that you do not want JCL generated to be submitted to the
internal reader, but rather to be written to the JCLOUT file and it will be your own
responsibility to get it executed.
d. Set Gen Object override file to Y.
e. Set Include OVERRIDE DD for Object override to Y.
f. Set Override DB2 table names to Y.
g. Set Override File Usage to 2.
h. Enter GEN on the command line. 
Watch for message ”I332 Generate process complete”.

Supported File-AID/RDX Features in ESR

With these basic capabilities in mind what about the need for various features and abilities of File-
AID/RDX and how it is affected by ESR? Here is a table of basic features and whether they are
supported and if there are any special concerns.

Table 80. Supported File-AID/RDX Features in ESR

Supported in
Feature Special Attention
ESR
External Key File Yes No
Output Key File Yes No
Temporal Table Yes No
Online Extract No No
Selection Criteria Yes If overrides are provided, then use care in providing the overrides.
Extract from Image Copy No, other than the basic requirements of processing from an image
Yes
copy.
Extract and Continue w. Load Yes This uses ESR for the load portion on a routine basis.
Extract and Disguise Yes No
Extract from MVS files Yes No
Extract includes LOB columns Yes No
Load using SQL insert Yes No
Load using DB2 load utility Yes No
Load using Autocreate Some extra caution is warranted. Test runs where autocreate is
Yes
exercised is a good thing.
Delete processing Yes No
Combination of Extract, Use care to ensure the proper sequence of operations that have
Possible
Delete, Extract, and Load dependencies.
File-AID/RDX Utilities 715

Extract File Compress Utility

The Extract File - Compress Utility screen shown in Figure 417 is displayed when you

• Select Option 3, Compress, from the Utilities Menu.

Use this screen to initiate a batch job that compresses or decompresses extract files.

There are two different types of compression available for the extract file: Compress and VARCHAR
compress. The Compress Utility can produce either of these types of compressed files and can
decompress either of these types of compressed files.

If you intend to use a compressed extract file outside of File-AID/RDX, for example to load the extract
file via File-AID/EX or manipulate it with File-AID/Data Solutions outside of the File-AID/RDX
Disguise option, decompress it beforehand using this Decompress utility.

Figure 417. Extract File - Compress Utility

File-AID/RDX -------------- Extract File - Compress Utility

------------------
COMMAND ===> 

Primary Commands: JCL view, GO to submit job 

Utility to execute ===> 1 (1 = Compress; 2 = Decompress) 
Compress utility option ===> V (V = VARCHAR; C = Compress) 

Specify Input Extract File: 
Extract File name IN ===> FRSAMP.EXTRACT 
Member ===> (Blank or pattern for member list) 
VOLSER ===> 

Specify Output Extract File: 
Extract File name OUT ===> FRSAMP.EXTRACT 
Member ===> (Blank or pattern for member list) 
VOLSER ===> 
Disposition ===> OLD (NEW or OLD) 

On this screen you specify the input and output extract files to be compressed or decompressed.
Input and output files can have the same file name.

Enter GO to submit the job or enter JCL to review the JCL before submitting.

After you enter GO, File-AID/RDX displays the message: JOB SUBMITTED and returns to the Utilities
Menu.

Compress Information:

Utility to execute
Specify 1 to compress (default) or 2 to decompress an extract file.

Compress utility option

If you want to compress an extract file, specify one of the compress options for the extracted data
in the extract file:

C Compress; The extracted data will be compressed to reduce the file size and
preserve disk space. The entire data record is compressed. This technique
provides the greatest amount of data compression. File-AID/RDX recognizes these
compressed extract files as valid input files for all functions: Load, Delete, and
Disguise.
716 File-AID/RDX Reference

V VARCHAR compression only affects VARCHAR, LONGVAR, VARGRAPHIC, and

LONGVARGRAPHIC columns of Db2 objects; it will not apply to MVS objects. The
VARCHAR compression option only writes the actual data within each VARCHAR
column without padding the records with trailing blanks; the length of a
VARCHAR column will vary for each row based on the data within the row.
VARCHAR data written to the Extract file using VARCHAR compression will be
readable since only the trailing blanks will be dropped.

File-AID/RDX recognizes these compressed extract files as valid input files for all
functions: Load, Delete, and Disguise.

Specify Input Extract File:

The original extract file specified as input into the Compress Utility must not be compressed. The
Compress utility will also return an error at execution time and end the job if the original extract file
is already compressed.

The original Extract file specified as input into the Decompress Utility must be compressed. The
Decompress utility will also return an error at execution time and end the job if the original extract
file is not compressed.

A pre-disguise extract file is not a valid input file for either compression
utility. This file is always masked and is only intended to be used as input to
Disguise. You can, however, compress or decompress an already disguised
extract file.

Extract File name IN

Specify the name of the input extract file to be compressed or decompressed. The extract file can
be on tape.

Member
Specify the member name of the input extract file, if the request file is a PDS. Specifying a pattern
allows you to select a member.

VOLSER
Specify the volume serial of the direct access device that contains the file.

Specify Output Extract File:

The output extract file can have the same name as the input file.

Extract File name OUT

Specify the name of the output extract file to be compressed or decompressed. The output extract
file can be saved to tape.

Member
Specify the member name of the output extract file, if the request file is a PDS. Specifying a
pattern allows you to select a member.
File-AID/RDX Utilities 717

VOLSER
Specify the volume serial of the direct access device that contains the file.

Disposition
Specify the disposition of the output extract file. You can save to existing files with a disposition
of OLD. Specify a disposition of NEW to create a new PDS or sequential file.

If you specify NEW in the Disposition field, you must specify the allocation parameters in the
Create New File screen (Figure 175 on page 334).

Remember to allocate an adequate amount of space for the output extract file to avoid out of
space conditions (SB37).

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

JCL
View the JCL for the Compress or Decompress utility. File-AID/RDX shows the Generated JCL
panel (Figure 418) where you review and modify the JCL. Enter the SUBMIT command to submit
the job.

GO (G)
Submits this Compress or Decompress job request without displaying the JCL. Before issuing the
GO command, make sure you have specified the input and output files and the compression
options. File-AID/RDX will issue a message upon completion of the job.

View JCL
The ISPF/PDF Edit screen shown in Figure 418 is displayed when you enter the JCL command in the
Extract File - Compress Utility panel.
718 File-AID/RDX Reference

Figure 418. ISPF/PDF EDIT Screen—File-AID/RDX-generated JCL

EDIT - Generated JCL ---------------------------------------- COLUMNS 000 000 

Command ===> SCROLL ===> CSR 
****** ***************************** Top of Data ******************************
==MSG> -Warning- The UNDO command is not available until you change 
==MSG> your edit profile using the command RECOVERY ON. 
000001 //TSOID01A JOB ('OFRBAS4.2DOC',SFA4562),'TSOID01', 
000002 // CLASS=U,MSGCLASS=R,NOTIFY=TSOID01 
000003 /*JOBPARM SYSAFF=CWCW 
000004 //* XFRJCMPRS
000005 //*------------------------------------------------------------------- 
000006 //* THIS JOB IS USED TO COMPRESS/DECOMPRESS EXTRACT FILES 
000007 //* 
000008 //*------------------------------------------------------------------- 
000009 //RDXCMPRS EXEC PGM=XFREXEC,REGION=8192K, 
000010 // PARM=(FR,O,B) 
000011 //* 
000012 //STEPLIB DD DSN=CPWR.MXVJ170.CXVJLOAD,DISP=SHR
000013 //* XFRSSTPL
000014 //RDXMLIB DD DSN=CPWR.MXVJ170.SXVJMENU,DISP=SHR 
000015 //SYSOUT DD SYSOUT=(*) 
000016 //SYSPRINT DD SYSOUT=(*) 
000017 //SYSUDUMP DD SYSOUT=(*)
000018 //* 
000019 //EXTIN DD DSN=TSOID01.FRSAMP.EXTPDS(FRSMPD1), 
000020 // DISP=OLD 
000021 //* 
000022 //EXTPARMS DD DSN=TSOID01.RDX.PARMS.D130314.T155100
000023 // DISP=OLD 
000024 //EXTOUT DD DSN=TSOID01.FRSAMP.EXTPDS(CCSMPD1), 
000025 // DISP=OLD 
000026 //*------------------------------------------------------------------- 
000026 //* THIS IS THE END OF JOB TO COMPRESS/DECOMPRESS EXTRACT FILES 
000027 //*------------------------------------------------------------------- 
****** **************************** Bottom of Data ****************************

Use this screen to view or edit the JCL generated by File-AID/RDX to compress or decompress an
existing extract file. Use the SUBMIT command to submit the extract request for execution. If you
want to save this JCL, use the ISPF/PDF CREATE or REPLACE command before you exit the panel.

Report
A report (Figure 419) will be produced during the Extract File Compress Utility processing.

Figure 419. Extract File Compress Utility Report

FILE-AID/RDX COMPRESS EXTRACT FILE UTILITY REPORT 

================================================= 

INPUT EXTRACT FILE: TSOID01.FRSAMP.EXTRACT 
OUTPUT EXTRACT FILE: TSOID01.FRSAMP.EXTRACT 
COMPRESS METHOD: VARIABLE FIELD 

*** UTILITY SUCCESSFUL *** 

*** EXTRACT COMPRESSED ***
File-AID/RDX Utilities 719

Generate DDL Utility

The Generate DDL Utility screen shown in Figure 420 is displayed when you

• Select Option 4, Generate DDL, from the Utilities Menu.

Beginning with File-AID/RDX Release 4.6, the extract files no longer contained readable DDL that
described the source environment.

Use this screen to initiate the utility that converts the masked Db2 DDL statements from a File-
AID/RDX extract file and places them into an output file in a readable format.

The DDL statements in an extract file are intended for File-AID/RDX’s use
only and may not be usable outside of File-AID/RDX.

Figure 420. Generate DDL Utility

File-AID/RDX -------------- Generate DDL

------------------------------------
COMMAND ===> 

Primary Commands: GEN to generate DDL, JCL view, GO to submit job 

Specify Extract File or Summary File: 
INPUT File Name ===> FRSAMP.EXTRACT 
Member Name ===> (* or pattern for selection list) 
VOLSER ===> 


Specify Output File: 
OUTPUT File name ===> 
Member Name ===> (* or pattern for selection list) 
VOLSER ===> 
Disposition ===> OLD (NEW or OLD)

On this screen you specify the input extract file or extract summary file, the output DDL file and
whether to process the request in online or batch mode.

Enter GEN to execute the utility in online mode. After you enter GEN and successful conversion, File-
AID/RDX displays the message: Generate process complete.

Or, enter JCL to view the generated JCL or GO to submit the job in batch mode.

Specify Input Extract File or Summary File:

If the extract file is on tape, specify the summary file you created for it (see also Summary File on
page 421).

INPUT File name

Specify the name of the input extract file or extract summary file. An asterisk (*) or pattern
displays a selection list.

Member
Specify the member name of the input extract file, if the extract file is a PDS. Specifying a pattern
allows you to select a member.
720 File-AID/RDX Reference

VOLSER
Specify the volume serial of the direct access device that contains the file.

Specify Output File:

OUTPUT File name

Specify the name of the output file that will contain the DDL statements from the above specified
input extract file.

Member
Specify the member name of the output DDL file, if it is a PDS. Specifying a pattern allows you to
select a member.

VOLSER
Specify the volume serial of the direct access device that contains the file.

Disposition
Specify the disposition of the output DDL file. You can save to existing files with a disposition of
OLD. Specify a disposition of NEW to create a new PDS or sequential file.

If you specify NEW in the Disposition field, you must specify the allocation parameters in the
Create New File screen (Figure 175 on page 334).

Remember to allocate an adequate amount of space for the output DDL file to avoid out of space
conditions (SB37).

For an existing output file, the utility deletes the content and inserts the data
from the current conversion.

Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:

GEN
Processes the Generate DDL utility request in online mode. Before issuing the GEN command,
make sure you have specified the desired input and output files. File-AID/RDX will issue a
message upon completion.

GO (G)
Submits this Generate DDL job request without displaying the JCL. Before issuing the GO
command, make sure you have specified the input and output files.
File-AID/RDX Utilities 721

JCL
View the JCL for the Generate DDL utility in batch mode. File-AID/RDX shows the Generated JCL
panel (Figure 418 on page 718) where you review and modify the JCL. Enter the SUBMIT
command to submit the job.

View JCL
The ISPF/PDF Edit screen shown in Figure 421 is displayed when you enter the JCL command in the
Generate DDL Utility panel.

Figure 421. ISPF/PDF EDIT Screen—File-AID/RDX-generated JCL - Generate DDL

EDIT - Generated JCL ---------------------------------------- COLUMNS 000 000 

Command ===> SCROLL ===> CSR 
****** ***************************** Top of Data ******************************
==MSG> -Warning- The UNDO command is not available until you change 
==MSG> your edit profile using the command RECOVERY ON. 
000001 //TSOID01A JOB ('OFRBAS4.2DOC',SFA4562),'TSOID01', 
000002 // CLASS=U,MSGCLASS=R,NOTIFY=TSOID01 
000003 /*JOBPARM SYSAFF=CWCW 
000004 //* XFRJGDDL
000005 //*------------------------------------------------------------------- 
000006 //* THIS JOB IS USED TO GENERATE DDL FROM EXTRACT FILES 
000007 //* 
000008 //*------------------------------------------------------------------- 
000009 //RDXGNDDL EXEC PGM=XFREXEC,REGION=8192K, 
000010 // PARM=(FR,P,B) 
000011 //STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ170.CXVJLOAD
000013 // DD DISP=SHR,DSN=CPWR.MXVJ170.SXVJLOAD
000014 //* 
000015 //RDXMLIB DD DSN=CPWR.MXVJ170.SXVJMENU,DISP=SHR 
000016 //SYSOUT DD SYSOUT=(*) 
000017 //SYSPRINT DD SYSOUT=(*) 
000018 //SYSUDUMP DD SYSOUT=(*)
000019 //* 
000020 //EXTIN DD DSN=TSOID01.FRSAMP.EXTRACT, 
000021 // DISP=OLD 
000022 //* 
000023 //EXTPARMS DD DSN=TSOID01.RDX.PARMS.D130314.T155100
000024 // DISP=OLD
000025 //DDLOUT DD DSN=TSOID01.FRSAMP.EXTRACT.DDL, 
000026 // DISP=OLD 
000027 //*------------------------------------------------------------------- 
000028 //* THIS IS THE END OF JOB TO GENERATE DDL FROM AN EXTRACT FILE 
000029 //*------------------------------------------------------------------- 
****** **************************** Bottom of Data ****************************

Use this screen to view or edit the JCL generated by File-AID/RDX to convert the masked Db2 DDL
statements from a File-AID/RDX extract file and place them into an output file in a readable format.
Use the SUBMIT command to submit the job for execution. If you want to save this JCL, use the
ISPF/PDF CREATE or REPLACE command before you exit the panel.

Report
A report (Figure 422) will be produced at the end of the batch Generate DDL Utility processing.

Figure 422. Generate DDL Utility Report

FILE-AID/RDX GENERATE DDL UTILITY REPORT 

================================================= 

INPUT EXTRACT FILE: TSOID01.FRSAMP.EXTRACT 
OUTPUT DDL FILE: TSOID01.FRSAMP.EXTRACT.DDL 


*** UTILITY SUCCESSFUL *** 

*** DDL GENERATED ***
722 File-AID/RDX Reference
 723

Tutorial and Online Help

Overview
The tutorial (Option T) provides online documentation that describes how to use File-AID/RDX. You
can invoke the tutorial in one of the following ways:

• Enter Option T on the File-AID/RDX Primary Option Menu or enter the "=T" ISPF/PDF JUMP
function from most screens.
• Enter the HELP command on any screen when a message is not displayed.
• Enter the HELP command twice after a message is displayed (the first HELP command displays
the extended message and the second invokes the tutorial).

The File-AID/RDX tutorial operates similarly to the ISPF/PDF tutorial. That is, to move about in the
File-AID/RDX tutorial, you use the same commands that you use in the ISPF/PDF tutorial.

Primary Menu Option T

If you invoke the tutorial with Option T or =T from the File-AID/RDX Primary Option Menu, the
screen shown in Figure 423 is displayed.

Figure 423. Tutorial Introduction–First Screen

File-AID/RDX -------------------- Introduction ------------------- TUTORIAL

COMMAND ===> 

File-AID/RDX Tutorial 

This tutorial provides on-line information about the use of
File-AID/RDX. It is organized hierarchically and you may view it
sequentially or select topics from lists that are displayed on
many of the tutorial pages. 

The table of contents contains a list of the major topics. Each
topic contains additional lists that lead you to lower levels of
detail. You may also select topics from the tutorial index which
is in alphabetical sequence. 

The next two pages contain a description of how to use the tutorial. 

Press the ENTER key to proceed to the next page, or
Enter the UP command to go directly to the table of contents, or
Enter the END command to return to the primary option menu.

You can view the next two screens of the tutorial introduction by pressing Enter. These screens
explain how to move about in the tutorial.
724 File-AID/RDX Reference

Figure 424. Tutorial Introduction–Second Screen

File-AID/RDX ------------- Introduction (continued) -------------- TUTORIAL

COMMAND ===>


To view the tutorial sequentially, leave the COMMAND field blank
and repeatedly press <ENTER>. To select topics from the lists
that are displayed on many of the tutorial pages, enter the topic
number in the COMMAND/OPTION field on line 2 of the screen. For
example:

OPTION ===> 2 (to select topic 2)

You may also enter one of the following commands on any tutorial page:

BACK or B - to back up to the previously viewed page.
SKIP or S - to skip the current topic and go on to the next topic.
UP or U - to display a higher level list of topics.
TOC or T - to display the table of contents.

(continued on next page)

Figure 425. Tutorial Introduction–Third Screen

File-AID/RDX ------------- Introduction (continued) --------------- TUTORIAL

COMMAND ===>

DEFAULT ASSIGNMENT
FOR PF KEY PAD
You may use the following commands to move about +--------+--------+--------+
in the tutorial (the default PF key assignment | HELP | | END |
for each command is shown to the right): | PF1 or | | PF3 or |
| PF13 | | PF15 |
HELP - to get help on how to use the tutorial. |--------|--------|--------|
END - to end the tutorial. | | | |
UP - to display a higher level page. | | | |
DOWN - to go on to the next topic (skip). | | | |
LEFT - to display the previous page (back). |--------|--------|--------|
RIGHT - to display the next page (next), which | UP | DOWN | |
is the same as pressing ENTER. | PF7 or | PF8 or | |
| PF19 | PF20 | |
Note: Default PF key assignments are not |--------|--------|--------|
provided for the LEFT and RIGHT | | | |
commands. | | | |
| | | |
+--------+--------+--------+

HELP Primary Command

If you enter the HELP primary command to invoke the tutorial, the appropriate section of the tutorial
is displayed based on what you were doing when you requested HELP. You can use the TOC command
on any screen in the tutorials to display the Tutorial Table of Contents screen shown in Figure 426.

While in the tutorial, you can enter the HELP command at any time to display a one-screen summary
of how to use the tutorial.

To terminate the tutorial, enter the END command and you return to the screen from where you
requested help. You cannot use the RETURN command or ISPF/PDF JUMP function to terminate the
tutorial.
Tutorial and Online Help 725

Figure 426. Tutorial Table of Contents

Help
-------------------------------------------------------------------------------
File-AID/RDX ---------------- Table of Contents --------------------- TUTORIAL
OPTION ===> 
-------------------------------------------
| File-AID/RDX TUTORIAL TABLE OF CONTENTS |
-------------------------------------------
The following topics are presented in sequence or may be selected
by entering a one-character code in the OPTION field: 

O - File-AID/RDX Product Overview
0 - Select, Create or Change Profiles
1 - Browse, modify, create relationship definitions
2 - Extract sets of related data
3 - Load sets of related data
4 - Delete sets of related data
5 - Specify Global User Defaults
6 - Transfer to File-AID for DB2

The following will be presented only if explicitly selected: 
B - RI Update batch job
C - Command summary
D - Download File-AID/RDX extract data 
L - Legal and Copyright Notices

Tutorial Help Pull-down Menu

The Tutorial Table of Contents screen also includes the HELP action bar item. It provides access to the
tutorial index function, PF Keys Help, and the File-AID/RDX About... panel. You invoke the Help pull-
down in the following way:

• Tab to the HELP action bar item and press ENTER. In the HELP pull-down select the desired
tutorial entry option.

Figure 427. Help Pull-down Menu

Help 
---------------------------------------------------------- 
File-AID/RDX ---------------- Table of Contents ---------- 1. Help Index 
OPTION ===> 2. Keys Help 
------------------------------------------ 3. About... 
| File-AID/RDX TUTORIAL TABLE OF CONTENTS 
------------------------------------------- 

Help Index
You access the index function for the File-AID/RDX tutorial panel from the Help action bar item. The
Help Index screen as shown in Figure 428 on page 726 lists index key word entries in alphabetical
order.
726 File-AID/RDX Reference

Figure 428. Help Index Screen

Menu Actions Options Help

-------------------------------------------------------------------------------
File-AID/RDX Help Index Row 1 to 15 of 1,710
Option ===> 

Enter S to select help topic from list 

CMD Key Word Description
- -------------- ------------------------------
_ (ALL) A (All) line-command 
_ (COMPLEX) Create DB2 View (Complex) 
_ (CRITERIA_SETS FORWARD Command (Criteria_Sets 
_ (CRITERIA_SETS INSERT Command (Criteria_Sets) 
_ (CRITERIA_SETS DELETE Command (Criteria_Sets) 
_ (CRITERIA_SETS BACK Command (Criteria_Sets) 
_ (CRITERIA_SETS REPEAT Command (Criteria_Sets) 
_ (LOCK-TABLE) L (Lock-table) line-command 
_ (PASSTHRU) P (Passthru) line-command 
_ (SIMPLE) Create DB2 View (Simple) 
_ A A Line_Command All 
_ A A Line_Command Accept Path 
_ A A Line_Command Add 
_ A A Line_Command Add_Relation 
_ A A (All) line-command 

Use the UP and DOWN scroll commands to scroll through the index listing. Enter the S line
command on your desired index entry. This will take you to the tutorial panel associated with your
selected index entry.

Use the FIND key word command to locate your desired topic quickly (see Figure 429 and Figure 430).

Figure 429. Find Command in Actions Pull-Down

Menu Actions Options

Help 
----- ------------------------------------------------------- 
File- _ 1. Find... Help Index Row 1 to 15 of 1,710 
Optio 

Enter S to select help topic from list 

CMD Key Word Description 
- -------------- ------------------------------ 
_ (ALL) A (All) line-command 
_ (COMPLEX) Create DB2 View (Complex) 

Figure 430. Find Key Word Entry Screen

Menu Actions Options Help 

- Enter Find for Keyword ------------
F 15 of 1,710
O String ===> SELEC 

E 

CMD Key Word Description 
- -------------- ------------------------------ 
_ (ALL) A (All) line-command 
_ (COMPLEX) Create DB2 View (Complex) 

You see the result of the key word search in the Index Keyword Find/Search Results windows as
shown in Figure 431 on page 727.
Tutorial and Online Help 727

Figure 431. Help Index Find Result Window

Menu Actions Options Help 

- Index Keyword Find/Search Results ------------------- 
F 13 references found w 1 to 15 of 1,710 
O Command ===> SCROLL ===> PAGE 

E Enter S to select from search results list 

CMD Key Word Description 
- -------------- ------------------------------ 
_ SELECT Select Profile 
_ SELECT S Line_Command Select 
_ SELECT Extract, Select driving object 
S SELECT. Defining MVS Select. Criteria 
_ SELECTION Selection Criteria Report 
_ SELECTION Where- table selection 
_ SELECTION Table Selection Criteria 
_ SELECTION Selection Criteria Status 
_ SELECTION Object Selection Criteria 
_ SELECTION Formatted Selection Criteria 
_ SELECTION Selection Criteria Options 

_ A A Line_Command Add 
_ A A Line_Command Add_Relation 
_ A A (All) line-command 

Enter the S line command on the desired index entry. File-AID/RDX enters the tutorial program at the
selected tutorial panel.

When you exit the tutorial you return to the Help Index panel.
728 File-AID/RDX Reference
 729

Command Summary A

Overview
This chapter contains descriptions of File-AID/RDX primary and line commands. Each description
consists of notes on command usage and a syntax diagram. For a more detailed explanation, refer to
the chapter that covers the option where the command is used.

Primary Commands
The following section describes File-AID/RDX primary commands. The command syntax is presented
along with a brief explanation of the command function. For a more detailed explanation, refer to
the chapter that covers the primary option(s) or sub-option(s) where the command is used.
Commands processed identically in ISPF/PDF and File-AID/RDX are noted with an asterisk (*).

Several commands described below have repetition factors as valid operands. This is symbolized using
the character n. Except where noted, n must be a positive integer value between one and
2,147,483,647.

See Reading the Syntax Diagrams on page 20 for an explanation of how to

read the "railroad logic" diagrams used to notate primary command syntax.

ACCEPT (A)
Accept all suggested relationships to be included in the extract. When you press Enter, you return to
the previous Extract Scope screen where you entered the CHECK command. Check Extract Warning
screen only.

ADD (A)
Allows you to add an application relationship. Displays the Add Relationships — Specify Object Types
screen so you can specify the parent and dependent object types for the new relationship. See Add
Relationships — Specify Object Types on page 123.

ALL
Selects all available menu options for you to step through in sequence. Profile, Extract, and Load
menus only. Selects all objects in the Object List Preview windows.

Selects and loads all RI relationships into the relationship file. Valid in the RI Relationship Detail
Screen.

BACK (BA)
Displays the previous selection criteria set in a criteria file. Valid only on the Selection Criteria
Specification Screen when defining or modifying multiple selection criteria sets (see Object Selection
Criteria on page 301). There are no operands associated with this command.

CANCEL (CAN)
Exits the current panel without saving changes made to the data. There are no operands associated
with this command.
730 File-AID/RDX Reference

CAPS
Controls whether alphabetic data entered should be automatically translated to uppercase or left as
is.

The caps mode is not "remembered" from session to session. Instead, it is set to ON when you invoke
File-AID/RDX. You can change the setting at any time using the CAPS command within File-
AID/RDX.

CAPS ON
OFF
CHANGE (C)
Allows you to globally replace character strings in the listed items on a panel. Valid parameters vary
from panel to panel. When entered without any parameter, a Change Command window prompts for
these parameters.

CHECK (CHE)
Use the CHECK command to verify the extract paths after you made navigational changes. When the
path integrity validation processing is complete, the results are displayed in the Check Extract
Warning window where you can resolve or ignore the findings. Extract Scope Relationship View
screen only.

CHECK is not valid when when the extract nrequest is built with
relationships in the Direct Plus or All Children Only mode (see Direct on
page 248).

COND
Displays the Relationship Condition Definition panel where you can define a conditional test for the
current AR. You must have already established a relationship before you can issue the COND
command. Valid only on the Column/Field Relationships panels

There are no operands associated with this command.

CREATOR
Enter the CREATOR primary command in the graphical relationship display and all Db2 objects will
include their Creator ID. This command acts as a toggle command, thus, when entering the
command again, Db2 objects will include their Creator ID only when there is more than one object
with the same name.

There are no operands associated with this command.

CURSOR*
Moves the cursor to the first input field on line two of the screen. This field is usually the OPTION or
COMMAND field.

There are no operands associated with this command.

DB2
Switches to the corresponding Db2 Object panel, in order to specify Db2 objects. Valid only for the
MVS Driving Object, MVS Relationship Facilitator, NEW MVS Object Filter, ObjectIn MVS Object
Filter, or ObjectOut MVS Object Filter panels.
Command Summary 731

DELETE (DEL)
Deletes the current selection criteria set in a criteria file. Valid only on the Selection Criteria
Specification Screen when defining or modifying multiple selection criteria sets (see Output Key File
Definition on page 332). There are no operands associated with this command.

DELETE
DEL nnnn
DETAIL (D)
Toggles the list display between a one-line and a two-line display in the Reference List screens.

DOWN
Causes scrolling toward the end of the data by the specified scroll amount.

DOWN
n
CSR
CUR
PAGE
HALF
MAX
DATA
EDIT (E)
Displays the JCL for this extract request. File-AID/RDX shows the Generated JCL panel where you
review and modify the extract JCL. Extract - DB2 Driving Object and Extract - MVS Driving Object
screens only.

END*
Terminates the current operation and returns control to the previous, higher-level screen. If you enter
the END command on the File-AID/RDX Primary Option Menu, File-AID/RDX is terminated.

There are no operands associated with this command.

EXCLUDE (EX)
Exclude relationships from the extract or load process. Valid parameters vary from panel to panel.
When entered without any parameters, an Exclude Command window prompts for these parameters.

EXPAND*
The EXPAND command enables you to view the full content of a scrollable field in a separate
window. Db2 long object names are displayed in scrollable fields. In order to view a long name in a
separate window, type EXPAND in the command line of the panel, move the cursor into the field to
expand, and press ENTER.

There are no operands associated with this command.

FILTER (FIL)
The FILTER command restricts the relationships being displayed to the relationships for a specific
object. Any relationship where the specified object is either a parent or a child will be displayed. The
FILTER command can be issued to build a display that contains the relationships for multiple objects
by choosing the option to retain the currently filtered list. For example, you could issue the FILTER
command to display the relationships for PROJ resulting in a display of only the PROJ relationships.
Then issue FILTER again, this time requesting the relationships for EMP and specifying to retain the
732 File-AID/RDX Reference

currently filtered list. The resulting display will contain all relationships for PROJ and EMP. This is
the same functionality available from the object view when the R line command is issued for multiple
objects prior to the VIEW command.

FILTER Command Window

When you enter the FILTER command, File-AID/RDX will pop up the Filter Command Window as
shown in Figure 432. Enter the object for which you want to display all relationships, and specify the
other filtered list options.

Figure 432. Filter Command Window


Filter Command 
Command ===> 
Display relationships for this object: 

Object Name Field ===> 
Include Creator Name ===> 

Retain Current Filtered List ===> N (Y = Yes, N = No) 

Enter to process, END to return 



Specify the object name and filtered list options.

Object Name Field

Enter the name of the object for which to display all relationships.

Include Creator Name

Specify whether the displayed relationships for Db2 objects should also include the objects’
creator name.

Retain Current Filtered List

Enter Y to add the specified object to the current list of displayed relationships. Enter N to clear
the current filtered list and display only the relationships for the specified object.
Command Summary 733

FIND (F)
The FIND command searches through data in the display and positions the line with the next
occurrence of the specified find-string to the first line of the displayed data. 
Table 81 lists the panels where the FIND command can be issued.

Entering FIND without parameters displays the window shown in Figure

433.

NEXT
FIND 'find-string'
ALL
PREV
FIRST
LAST

Find String
Value to be found. The first parameter for the FIND command is always the find-string. The find-
string value is not case sensitive. Enclose the string in either single or double quotes when

• the find-string contains blanks

• the find-string contains a single quote (’), you must enclose it in double quotes.
• the find-string contains double quotes ("), you must enclose it in single quotes.

Modifiers
Specify one of the following parameters to modify the search order.

NEXT
Default. Starts a search for the next occurrence of the find-string at the beginning of the first line
being displayed (if the cursor is still on the COMMAND line), or at the cursor location (if the
cursor is in the data part of the display).

ALL
Finds all occurrences of the find-string starting at the beginning of the first line of the data and
continues to the bottom of data. If you specify both a column name and the ALL parameter, all
occurrences in the specified column of the find-string are found.

PREV
Starts a search for the previous occurrence of the find-string starting at the end of the line
preceding the first line being displayed (if the cursor is still on the COMMAND line), or at the
cursor location (if the cursor is in the data display).

FIRST
Starts a search for the first occurrence of the find-string starting at the beginning of the first line of
the data and continues until the string is found or the bottom of data is reached.
734 File-AID/RDX Reference

LAST
Starts a search for the last occurrence of the find-string starting at the end of the last line of the
data and continues backward until the string is found, or the top of data is reached.

Table 81. List of Panels supporting FIND command

FIND with find-string, Modifiers and FIND
FIND with only find-string
Parameter Window
• Relationship Detail • Extract Reference List
• RI Relationship Detail • Load Reference List
• Application Relationship Detail • Disguise Reference List
• Table List - SYSIBM.SYSTABLES • Delete Reference List
• Request File Member List
• Catalog Utility File List
• New List (Disguise)
• Data Disguise - Object List
• Data Disguise - Column/Field List

FIND Parameter Window

When you enter the FIND command without any find-string, File-AID/RDX will pop up the Enter
Find Parameter Window as shown in Figure 433. Enter the find-string and modifier as described in
Find String on page 733 and Modifiers on page 733.

Figure 433. Enter Find Parameter Window


Menu Actions Options Help 
------------------------------------------------------------------------------- 
Fi Enter Find Parameters SSID: DSN 
CO LL ===> CSR 
String ===> 
Sp Modifier ===> NEXT (FIRST,LAST,NEXT,PREV,ALL) 


Line Commands: 

FORWARD (FOR)
Displays the next selection criteria set in a criteria file. Valid only on the Selection Criteria
Specification Screen when defining or modifying multiple selection criteria sets. There are no
operands associated with this command.

FUNCTION LOCK
Enables the “Lock Table during Extract” function for all Db2 objects. The Extract Scope - Object
View panel will display and enable the L line command and display the L status column. See also
L (Lock Table) on page 258. FUNCTION LOCK is a toggle switch so enter FUNCTION LOCK again
to return to the original format. Extract Scope - Object View panel only. There are no operands
associated with this command.

The FUNCTION LOCK primary command is only valid if File-AID/RDX was

configured at installation to allow locking tables during extract.

GEN
1. Processes the selected execute saved request (ESR) options without displaying any JCL. Before
issuing the GEN command, make sure you have specified the desired requests from the request
Command Summary 735

file, the ESR JCL file, and any override files. File-AID/RDX will not issue a message upon
completion of the job. Valid on the Execute Saved Request (ESR) Options panel.
2. Processes the Generate DDL utility request. Before issuing the GEN command, make sure you have
specified the desired input and output files. File-AID/RDX will issue a message upon completion.
Valid on the Generate DDL Utility panel.

GO (G)
Submits an extract request from the Extract - DB2 Driving Object or Extract - MVS Driving Object
panel.

Submits a File-AID/RDX utilities job from the Print Disguise Control File, Print Disguise Audit Trail,
Batch RI Load, Update Saved Extract Requests, or Extract File Compress Utility panel.

GRAPHIC (G,GR)
Displays the Graphical Relationship Display screen. This command is valid from the Browse -
Relationship Detail screen, the AR Relationship Detail screen, the RI Relationship Detail screen, and
the Relationship Criteria screen. There are no operands associated with this command.

HELP*
Shows the extended description of a message that has been displayed, or invokes the online tutorial
facility. If File-AID/RDX displays a message in the upper right corner, entering the HELP command
will display the extended description on line three of the screen. The tutorial is invoked by
immediately entering another HELP command, or by entering HELP when no message has been
displayed.

There are no operands associated with this command.

HIDE (H)
The HIDE command allows less data to be displayed. Included, excluded and special status objects
can be removed or hidden from the display so that the remaining content is more meaningful.
Special status is any status other than blank or excluded; this will include any error messages and any
objects where criteria has been provided at the relationship level as well as the object level. Use the
RESET command to return all hidden objects to the display. Valid Parameters differ between Extract
Scope and Target Environment implementation.

IGNORE (I)
Ignore all flagged relationships, they will not be included in the extract and their status changes to
“Relational error ignored”. You can still use the Accept Path line command to change the status
individually or enter the ACCEPT primary command. Check Extract Warning screen only.

INSERT (INS)
Inserts a new selection criteria set after the currently displayed set in a criteria file. The new set’s id
number equals the current set’s number incremented by 1. Example: current id = 3 of 5, id of inserted
set= 4 of 6. Any following set id numbers in the criteria file are of course incremented accordingly, for
example 4 of 5 becomes 5 of 6, 5 of 5 becomes 6 of 6. Valid only on the Selection Criteria
Specification Screen when defining or modifying multiple selection criteria sets (see Output Key File
Definition on page 332). There are no operands associated with this command.

INSERT
INS nnnn
736 File-AID/RDX Reference

KEYLIST*
Calls the key list utility so you can browse and modify the File-AID/RDX keylists as defined for all
File-AID/RDX CUA panels.

OFF
KEYLIST
ON

ON and OFF are only valid for ISPF version 4.1 or newer.

KEYS*
Causes an immediate display of a screen on which current PF key definitions are shown and can be
modified.

There are no operands associated with this command.

LEFT
Causes scrolling toward the left margin of the data by the specified scroll amount. Valid on the
Selection Criteria screen only.

LEFT
n
CSR
CUR
PAGE
HALF
MAX
DATA
LIMITKEY (LK)
Displays the Limit Key Definition screen which lets you define the limit key value for each logical
partition, if the tablespace is partitioned. Valid in the Create Tablespace, Create DB2 Table, and
Create Index panels.

LOCATE (L)
Searches the sorted column of the displayed list and positions the line with the first occurrence of the
LOCATE value to the first line of the displayed data. Valid whenever a list is displayed. If the list has
not been sorted, enter a line number.

LOCATE value
L

value
Value to locate. Either the beginning string of the sorted column’s entry, or a line (row)
number for an unsorted list (see also SORT on page 740).
Command Summary 737

MENU
Switches to the full Extract or Load Menu from an extract or load submenu when in flow mode.
Toggles between displaying all or a subset of options in the File-AID/Data Solutions Criteria Menu.

MODE
Use the MODE command to switch the current extract or load mode to either INTERACTIVE (online)
or BATCH, if your installation allows extract or load requests to be executed online. Extract Menu and
Load Menu only.

There are no operands associated with this command.

MVS
Switches to the corresponding MVS Object panel, in order to specify MVS objects. Valid only for the
DB2 Driving Object, DB2 Relationship Facilitator, NEW DB2 Object Filter, ObjectIn DB2 Object Filter,
or ObjectOut DB2 Object Filter panels.

NAVIGATION (NAV)
The NAVIGATION command takes you directly to the NAVIGATION format of the relationship view.
Extract Scope Object View and Extract Scope Relationship View screens only.

NEW (N)
Creates a new extract, load, or delete request or a new disguise object list. (Reference List and Request
File Member List screens only).

Also defines a new associated criteria rule in the Associated Rules List.

For an extract request or disguise object list, include one of the optional parameters, DB2 or MVS, to
display the respective Driving Object screen.

NEW
N DB2
MVS
NEXT (N)
Displays the next screen in the process being performed.

There are no operands associated with this command.

OBJECTIN (OI)
Allows you to add objects to your current object list. This command displays either the “ObjectIn -
DB2 Object Filter” or “ObjectIn - MVS Object Filter” screen. The ObjectIn Filter panels work the same
as the NEW - DB2 Object Filter (Figure 353 on page 628) and NEW - MVS Object Filter (Figure 354 on
page 630).

OBJECTOUT (OO)
Allows you to remove objects from your current object list. This command displays either the
ObjectOut - DB2 Object Filter (Figure 360 on page 636) or ObjectOut - MVS Object Filter screen
(Figure 361 on page 637).

PARTITION (PART)
Displays the “Partition Definition” screen which lets you define the attributes for each
index/tablespace partition (Edit Tablespace and Edit Index screens only).
738 File-AID/RDX Reference

PREV
Goes to previous selected menu option in flow mode (Profile screens only).

PRINT*
Causes a snapshot of the current screen to be recorded in the ISPF/PDF list file for subsequent
printing.

There are no operands associated with this command.

PRINT-HI*
Same as PRINT except that high-intensity characters on the screen are printed with overstrikes to
simulate the high-intensity display.

There are no operands associated with this command.

PRINTL*
Causes a snapshot of the current logical screen to be recorded in the ISPF/PDF list file.

There are no operands associated with this command.

PRINTLHI*
Same as PRINTL except that high-intensity characters on the screen are printed with overstrikes to
simulate high-intensity display.

There are no operands associated with this command.

REFERENCE (REF)
Switches to the applicable Reference List from a Request File Member List or from the Extract or Load
Menu.

REFRESH (R)
Refreshes the list of objects of the Target Environment screen (Figure 249 on page 451). Use the
REFRESH command after changes to the listed objects have an influence on the hierarchal and
alphabetical order of the display.

REPEAT (REP)
Repeats (duplicates) the current selection criteria set after the currently displayed set in a criteria file.
The new set’s id number equals the current set’s number incremented by 1. Example: current id = 1 of
5, id of inserted set= 2 of 6. Any following set id numbers in the criteria file are of course incremented
accordingly, for example 2 of 5 becomes 3 of 6, 3 of 5 becomes 4 of 6, etc.. Valid only on the Selection
Criteria Specification Screen when defining or modifying multiple selection criteria sets (see Output
Key File Definition on page 332). There are no operands associated with this command.

REPeat
nnnn
REPORT (REP)
Prints the currently displayed object or relationship list. Valid on the Extract Scope Object View and
Relationship View panels only.

REQUEST (REQ)
Switches to the applicable Request File Member List from a Reference List or from the Extract or Load
Menu.
Command Summary 739

RESET (RES)
Use the RESET command to return all hidden objects to the display. Extract Scope Object View and
Extract Scope Relationship View screens only.

RETRIEVE*
Causes a previously entered command to be recalled to the command line.

There are no operands associated with this command.

RETURN
Causes an immediate return to the File-AID/RDX Primary Option Menu.

There are no operands associated with this command.

RFIND
The RFIND command repeats the previous FIND command.

RIGHT
Causes scrolling toward the right margin of the data by the specified scroll amount. Valid on the
Selection Criteria screen only.

RIGHT
n
CSR
CUR
PAGE
HALF
MAX
DATA
SAMPLE
The SAMPLE command takes you directly to the SAMPLE format of the relationship view. Extract
Scope Object View and Extract Scope Relationship View screens only.

SHOW (SH)
The SHOW command alters the contents of the SHOW column in the Target Environment screen
(Figure 249 on page 451). Depending on the specified parameter, the SHOW column can display the
associated database, tablespace or stogroup information for the appropriate Db2 objects in the list.
SHOW without a parameter displays the SHOW COMMAND window. Target Environment screen
only.

SHOW
SH NONE
DB
TS
STOGROUP
SIZE (SI)
Toggles the size of list display area by hiding or displaying the panel header lines in various list
display screens.
740 File-AID/RDX Reference

SORT
Sorts the displayed list by the specified column name. After sorting a column you can use the
LOCATE primary command in that column. Valid whenever a list is displayed.

SORT column-name
SPLIT*
Causes split screen mode to be entered or the location of the split line to be changed. The position of
the split line depends on the cursor location at the time the command is entered.

There are no operands associated with this command.

SQL
Invokes an edit session on selection criteria in SQL format. Valid on the Selection Criteria screen.

There are no operands associated with this command.

SQLID
Enter the SQLID primary command to change or view the Db2 SQLID for the current load session.
Each load session starts with the default SQLID as specified in the load profile (see also Default SQLID
on page 65). In the Set SQLID window, enter the desired SQLID. USER is a valid entry and changes the
SQLID to match the current userid. If you blank out the SQLID, it defaults to the SQLID as specified
in the load profile.

STATUS (STAT)
The STATUS command takes you directly to the STATUS format of the relationship view. Extract
Scope Object View and Extract Scope Relationship View screens only.

SUBMIT*
Submits the JCL for execution. Valid only on the ISPF/PDF EDIT screen shown in the Extract, Load
and Delete functions.

SUGGEST (SUG)
The SUGGEST command suggests a relationship when the parent and dependent column or field
name, type and length are identical. Column/Field Relationships screens only.

SWAP*
Positions the cursor to wherever it was previously located on the other logical screen of a split screen
pair.

There are no operands associated with this command.

TABLE (TAB)
Displays the “Tables Within View” screen which lists the tables that are part of the complex view. Edit
View screen only.

TSO*
Allows a TSO command or CLIST to be entered from the COMMAND or OPTION field of any screen.

There are no operands associated with this command.

Command Summary 741

UDTSWAP
Swaps the display for distinct type columns from UDT name to the built-in data type and length and
vice versa. This command is valid only on the Driving Table Selection Criteria, Table Selection
Criteria (Extract), and Column Mapping (Load) screens.

There are no operands associated with this command.

UDTTYPE
Lists all distinct data types (UDTs) that are part of the extract. The list displays the schema, UDT
name, and the built-in data type and length. This command is valid only on the Driving Table
Selection Criteria and Table Selection Criteria screens.

There are no operands associated with this command.

UNEXCLUDE
Causes all the relationships on the list displayed to be included again in the extract or the load
process. This command is valid only on the Extract Scope - Object View, Relationship Criteria and
Source to Target Mapping screens. The optional parameters DB2, KEY, and MVS limit the
UNEXCLUDE command to one of the three object types. ALL is the default.

UNEXCLUDE
U DB2
KEY
MVS
UP
Causes scrolling toward the top of the data by the specified scroll amount.

UP
n
CSR
CUR
PAGE
HALF
MAX
DATA
VALIDATE
Validate all relationships before you continue with the extract process. The message “No changes”
informs you that all relationships have been successfully validated. If there are inconsistencies, the
Update Saved Request window reports the validation results and gives you the opportunity to update
the extract request. Extract Scope - Relationship View panel only.

VALIDATE is not valid when when the extract nrequest is built with
relationships in the Direct Plus or All Children Only mode (see Direct on
page 248).

VIEW (VI)
The VIEW command allows you to easily switch between the object and relationship views. SAMPLE,
STATUS and NAVIGATION can be used to go directly to the corresponding format of the relationship
742 File-AID/RDX Reference

view. These commands are not included on the primary command line for the object view but will be
processed if entered. Extract Scope Object View and Extract Scope Relationship View screens only.

VIEW
VI NAVIGATION
NAV
SAMPLE
SAM
STATUS
STA

Line Commands
A (Accept Path)
Accept an individual relationship to be included in the extract. When you press Enter, you return to
the previous Extract Scope screen where you entered the CHECK command. Check Extract Warning
screen.

A (Add)
On the Application Relationship Detail and DB2 or MVS Object List screen, A enables you to create a
new application relationship by displaying the Add Relationships screen. On the Unrelated Object
Specification screen, A allows you to add unrelated objects to your extract specification. On the
Default Value Definition screen, A allows you to add literal definitions during load column mapping.

A line command summary:

• Add a new AR relationship

• Add an unrelated object
• Add a literal definition

A (Add/Assign Rule)
Displays the Associated Rules List where you can select an already defined associated disguise rule or
create a new associated rule to assign to a selected column (see also Associated Rules List on page
646). You can only enter the A line command for a column that does not have a rule assigned to it,
yet.

A (All)
Extract all data from this object regardless of the relationships from and to this object. Extract Scope
- Object View screen.

B (Browse)
From the Relationship Facilitator Option, B enables you to browse the relationship file for the
selected object by displaying the Column Relationships screen.

B line command summary:

• Browse for a relationship

C (Change and Go)

Select an extract request and change the selection criteria for the driving object before submitting the
request (Extract Reference List and Extract Request File Member List screens).

C (Copy)
Copies a profile member (Profile Selection screen).
Command Summary 743

D (Delete)
Valid on the Application Relationship Detail screen, RI Relationship Detail screen, SQL Edit screen,
and the Column Relationships screen. Deletes the relationship on the line containing the D line
command. On the Default Value Definition screen, D deletes a literal definition during load column
mapping.

D line command summary:

• Deletes relationship on the current line

• Deletes selection criteria for the object on the current line
• Deletes literal definition during Load Column/Field Mapping
• Deletes entries from a Reference List or Request File
• Entries from the list of partition definitions

E (Edit AR)
From the Relationship Facilitator Option, E enables you to maintain (add, edit, delete) application
relationships for the selected object by displaying the Column Relationships screen.

E line command summary:

• Edit an AR relationship

E (Edit Object)
In the Target Environment screen, E enables you to edit the create information for the selected
object. Only valid for objects marked to be created.

E line command summary:

• Edit object create information

G (Go)
Submits an extract, or load request immediately without any changes (Reference List and Request File
Member List screens).

I (Ignore Path)
Ignore an individual relationship, it will not be included in the extract and its status changes to
“Relational error ignored”. You can still use the Accept Path line command to change the status
individually or enter the ACCEPT primary command. Check Extract Warning screen.

I (Information)
Valid on Relationship Detail screens in the Browse Relationships, RI Relationship, and Application
Relationship suboptions. Also valid on the Relationship Criteria screen and the Graphical
Relationship Display screen. Displays the Relationship Information pop-up window. This window
contains slightly different information for each suboption. When entered in the Extract, Load, or
Delete Reference List, it displays the Request Details screen with detailed information about the
selected request. In the Target Environment screen, I displays the DDL for the selected Db2 object. In
the Data Disguise - Object List, I displays data disguise information for an object and in the Data
Disguise - Column/Field List, I displays data disguise information for a column/field.

I line command summary:

• Display information about a relationship

• Display detailed information about an extract, delete, or load request
• Display DDL for selected Db2 object
• Display data disguise information for an object
• Display data disguise information for a column/field
744 File-AID/RDX Reference

I (Insert)
The I (Insert) line command inserts a different partition after the current partition. The inserted
partition(s) are based on the model partition. To insert more than 1 partition at a time, enter the
number of partitions with the I line command (nnn = 1 - 999). Valid on the Tablespace Partition
Definition and Index Partition Definition panels.

L (List DB)
In the Data Disguise - Object List, lists all objects that are in the same database as the selected object
and are not already in the object list. Then you can select any of the objects to be added to the object
list.

L (Load RI)
From the Relationship Facilitator Option, L enables you to maintain (load, delete) Db2 RI
relationships for the selected object by displaying the Column Relationships screen.

L line command summary:

• Load an RI relationship

L (Lock)
Prevents the request entry from rolling off the Reference List.

L (Lock Table)
Indicate whether or not a table will be locked during extract. The L line command acts as a toggle
switch, enter it once and it will set the status to Locked. Enter L a second time, and the Locked status
is removed. FUNCTION LOCK must be enabled for the L line command to be valid. Extract Scope -
Object View screen.

M (Modify Request)
Valid in the Extract Reference List and Extract Request File Member List screens. Selects this extract
request, displays the Modify Extract Request panel where you can change the Db2 subsystem and any
object name in the request. This allows you to create an extract request on one Db2 subsystem or
MVS environment and then easily modify or "clone" it to run on a different Db2 subsystem or MVS
environment which has the same objects but with different names.

M line command summary:

• Selects an extract request, allows changing SSID and/or object names.

M (Modify MVS Object)

When issued in the Unrelated Object Specification screen for an unrelated MVS file, it displays the
Modify Unrelated MVS Object Definition screen where you can change the record layout and/or XREF
information for the file.

M line command summary:

• Selects an unrelated MVS file to modify its record layout information (valid on Unrelated
Object Specification screen only).

n (Column or Field Number)

Valid only on the Column/Field Relationships screens. Establishes an application relationship
between a parent column or field (the column/field next to which you enter the command) and a
dependent column or field (the column/field designated by the entered number).

n line command summary:

• Establish a new column relationship

Command Summary 745

O (ObjectOut)
In the Data Disguise - Object List, removes the selected object from the object list.

P (Passthru)
Don’t extract any data from this object, but process all relationships as if records based on the
relationship would have been extracted. Extract Scope - Object View screen.

R (Related objects)
In the Data Disguise - Object List, searches the relationship file and displays any related objects that
are not yet included in the object list. Then you can select any of the related objects to be added to
the object list.

R (Relationship View)
Mark this object to be included in the Relationship View when the VIEW primary command is
entered. Extract Scope - Object View screen.

R (Remove)
Removes an unrelated object from the Unrelated Object List.

R (Rename)
Renames a profile member (Profile Selection screen) or a request file member (Request File Member
List screen).

R (Repeat)
The R (Repeat) line command repeats a partition definition in the list of different partitions from the
model. To repeat a partition definition more than once, enter the number of repetitions with the R
line command (nnn = 1 - 999). Valid on the Tablespace Partition Definition and Index Partition
Definition panels.

R (Restore original name)

Restores the original object name for the selected object. Valid on the Modify Object Names - DETAIL
Screen.

S (Select)
Valid on the Browse - Relationship Summary window, RI Relationship Detail screen (load/refresh),
Application Relationship Detail screen, and Relationship Criteria screen. Valid also on the
Relationship Listing pop-up window and the Table List pop-up window. Selects a relationship or table
to be operated on.

Selects a column to load a literal in the Column Mapping screen. Selects a literal definition to be
assigned to a column in the Default Value Definition screen.

Selects an extract, load, or delete request and displays the appropriate Extract, Load, or Delete Menu
or screen (Reference List and Request File Member List screens).

Selects an object in the ObjectIn Preview, ObjectOut Preview, or Data Disguise - Object List screen or
a column/field in the Data Disguise - Column/Field List screen for data disguise.

S line command summary:

• Select a relationship or table

• Select a column/field to load literals
• Select a literal definition for a column/field
• Select an object or member from a list
• Select a profile from the profile list
746 File-AID/RDX Reference

• Select an extract, load, or delete request

• Select an object for data disguise
• Select a column/field for data disguise

U (Unassign Rule)
Removes a disguise rule from a column in the Data Disguise - Column/Field List.

U (Unexclude)
Valid on the Extract Scope - Object and Relationship Views, Graphical Relationship Display, Source to
Target Mapping, and Target Environment screens. Selects a previously excluded object/relationship to
be included in the extract or load.

U line command summary:

• Undo exclude on a relationship

U (Undo Remove)
Reverses removing an unrelated object from the Unrelated Object List.

U (Unlock)
Removes the lock status from a request entry in a Reference List.

U (Update)
On the Default Value Definition screen, U allows you to update literal definitions during load column
mapping.

U line command summary:

• Update a literal definition

V (View JCL)
Displays the JCL for this load or extract request. File-AID/RDX shows the Generated JCL panel where
you review and modify the load or extract JCL (Reference List and Request File Member List screens
for extract and load).

V line command summary:

• View extract or load JCL

X (Exclude)
Valid on the Relationship Criteria screen and the Graphical Relationship Display screen. Excludes a
relationship from the extract or load.

X line command summary:

• Exclude a relationship
 747

Extract Navigation Criteria Examples A

A Closer Look
This appendix presents some examples that illustrate the navigational and sampling controls
available since File-AID/RDX Release 4.0. While the examples in this appendix are Db2 objects only,
the extract options apply to MVS object types as well.

Navigation Controls
The four Navigation Controls are:

• Direct (D) - Extract all of the dependents of the driving object and their dependents.

• Parent (P) - Extract parents of all extracted data to maintain the integrity of the extracted data.

• Sibling (S) - Extract other dependents of the extracted parents from the same relationships.

• Indirect (I) - Extract other dependents of the extracted parents from other relationships.

Sometimes the Navigation Controls are referred to by their initials: DPSI.

Order of Accessing Objects During Execution

When File-AID/RDX executes an extract, it accesses the objects in the following order:

1. Driving object
2. Unrelated objects
3. Objects marked as ALL
4. Direct dependents of the driving objects
5. Parent objects
6. Siblings
7. Indirects
748 File-AID/RDX Reference

Examples Overview
The examples in this appendix use the sample training tables as referred to in the File-AID/RDX User
Guide.

Figure 434. Test Data Sample Structure

The examples use the same selection criteria and differ only in the chosen Navigation Options.
Comparing the different extract steps and extracted rows in the extract files and their reports will
help you understand the differences in the extract navigation options. Follow the instructions in the
File-AID/RDX User Guide, page 1-5 on how to create the sample file. Use the File-AID/RDX Load Option
to load the Sample Extract File.

All other extract sampling criteria are set to their default values (*) with the Quiesce extract option
unless otherwise noted for each example.

The extracted D records presented in the sample extract results have been produced without
compression or disguise options to demonstrate the extract process.

Example 1
In example 1, File-AID/RDX will extract data based on ORDER_TABLE as the driving table for all rows
WHERE ORDER_NUMBER = ’BT33-C’ OR CUST_NUM = ’CW3375’.

Example 2
In example 2, File-AID/RDX will extract data based on PART_TABLE as the driving table for all rows
WHERE PART_NUMBER = ’AA4555’.
Extract Navigation Criteria Examples 749

Summary Comparison of Extract Results

Performance improvements for Release 4.0 have resulted in reducing the number of table open
operations while extracting the same set of data.

Table 82. Example 1 Summary

D=Y D=Y
D=Y D=Y D=Y P=Y P=Y D=P D=C
P=Y P=Y P=Y S=Y S=N P=Y P=N
Tables
S=N S=N S=Y I=Y (Modified) S=N S=N
I=Y I=N I=Y CYCLE=1 I=N I=N I=N
Quiesce=Q (Modified)
PART_TABLE 8 8 20 8 8 8 0
CUSTOMER_TABLE 2 2 11 8 8 2 0
CONTACT_TABLE 2 0 14 2 10 0 0
ORDER_TABLE 4 4 17 10 10 4 4
ORDER_LINE_TABLE 8 8 39 17 17 8 8
SUPPLIER_TABLE 11 0 24 11 0 0 0
Total Rows Extracted 35 22 125 56 53 22 12
Total Table Open Operations 6 4 28 10 8 4 2

Table 83. Example 2 Summary

D=N
D=Y
D=Y D=Y D=Y P=Y D=P D=C
P=Y
P=Y P=Y P=Y S=N P=Y P=Y
Tables S=Y
S=N S=N S=Y (Modified) S=N S=N
I=Y
I=Y I=N I=Y I=N I=N I=N
CYCLE=1
(Modified)
PART_TABLE 1 1 27 4 1 1 1
CUSTOMER_TABLE 3 3 12 3 3 3 0
CONTACT_TABLE 3 0 15 3 3 0 0
ORDER_TABLE 3 3 28 6 6 3 0
ORDER_LINE_TABLE 3 3 48 6 3 3 3
SUPPLIER_TABLE 2 2 31 2 2 2 2
Total Rows Extracted 15 12 161 24 18 12 6
Total Table Open Operations 6 5 40 9 7 5 3
750 File-AID/RDX Reference

DPSI=YYNY
Similar to Previous Extract Method STANDARD

This global navigation setting, without any overrides for any individual relationships, will extract all
direct and indirect dependents as well as their parent records, in other words, "When satisfying
relationships, always chase the structure completely down to extract all children. If you have gone up in
the structure to obtain a parent row, do not chase back down to that same relationship to select any
additional children of that parent row."

The extract of the driving table will be based on the specified selection criteria and all limits will be
respected. All of the qualified rows of the driving table are extracted, followed by the direct
dependents of the extracted rows from the driving table. Then, all of the parents of the extracted
direct dependent and driving table rows are extracted to satisfy the relationship that may exist.
Going up in the structure to extract a parent row will not cause any more children (siblings) from the
prior dependent table to be extracted. All other children (indirect) of the currently extracted rows are
then extracted.

Example 1
With the global navigation control switches set to DPSI=YYNY, File-AID/RDX will extract data in the
following way, based on ORDER_TABLE as the driving table for all rows WHERE ORDER_NUMBER =
’BT33-C’ OR CUST_NUM = ’CW3375’.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - - - Y 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y N - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE - Y N - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE - - - Y 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- -----------------------------------------------------------------------------------------------
D004 4 D-DSNLOCAT.FRSAMP.ORDER_TABLE 

D001 8 D-DSNLOCAT.FRSAMP.PART_TABLE
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D002 11 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
11 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 2 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D005 8 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
11 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 2 D-DSNLOCAT.FRSAMP.CONTACT_TABLE
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 35 TOTAL rows extracted from 6 objects *****


Step 1. Extract rows from the driving table ORDER_TABLE that match ORDER_NUMBER = ’BT33-C’
or CUST_NUM = ’CW3375’.
Extract Navigation Criteria Examples 751

Number of rows extracted: 4

D004....AZ0099CW3375246-80-13572211445566778899PURCHASE1994-12-19OPEN ...á%.........SD1995-01-28..TERMINAL ACCESORIES

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FF6666CW3375112-23-92737665123872173567PURCHASE1994-12-16INITIAL ..àB..........GD1994-12-28..CONTROL UNIT
D004....GA1122CW3375238-18-2222362562872754534 PURCHASE1993-03-30OPEN ..é.....&.....PR1994-01-16..43 LINE 132 COLOR MO

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows of ORDER_TABLE rows extracted
in step 1.
Number of rows extracted: 8

D005....AZ0099r..12-ER3..................1994-11-09ONTIME
D005....AZ0099r..WE234T..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....BT33-C...HT5550../...............1994-06-09WAIT
D005....BT33-C...HT4320..................1993-06-25ONTIME
D005....FF6666~..UT1245..~...............1993-05-12ONTIME
D005....GA1122...PTLKIU..................1993-06-09BEHIND
D005....GA1122...TU/345..................1994-07-03ONTIME

Step 3. Extract rows from PART_TABLE which are parent rows of ORDER_LINE_TABLE rows extracted
in step 3.
Number of rows extracted: 8

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

D001..............HT4320600’ 1/2 IN MAGNETIC TAPE1993-09-10R55-22...Ø...........EA....%.....NAA-985
D001..............HT5550HIGH DENSITY CARTRIDGE 1994-10-30TU/345... ...........EA... ......NBB-398
D001..............PTLKIU8 BYTE PENTIUM PIN MEMORY1994-02-10UT1245...~...........EA..........YDF-782
D001..............TU/345400 FT HIGH DENSITY CART 1994-10-26HT5550..à.....&......EA........é.NRX-931
D001..............UT124516 BYTE 70NS PIN MEMORY 1994-05-20LP6677..à.....&......EA........é.NRX-931
D001..............WE234TMC SCSI BUS AND ADAPTER 1994-01-11PST098...~...........FT... ......YII-232
D001..............12-ER3X-Z MONITOR HOUSING FIX. 1994-02-27JJ4537...~...........FT... ......YII-232

Step 4. Extract rows from CUSTOMER_TABLE which are the parent rows of ORDER_TABLE rows
extracted in Step 1.
Number of rows extracted: 2

D003.. .............CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA UNITED

D003................CW3375SONORA COMPUTING 33345 W SKYLINE BLVD PHOENIX AZ87408 UNITED

Step 5. Extract rows from SUPPLIER_TABLE which are dependent rows of PART_TABLE rows extracted
in step 5.
Number of rows extracted: 11

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM
D002..............HT4320S001BILL JONES PARTS ...&. N.@MM
D002..............HT5550S001WMK INC. ..... N..MM
D002..............PTLKIUS001AA SUPPLY COMPANY ..........Y..MM
D002..............PTLKIUS002SMITH SUPPLY COMPANY ..... Y..MM
D002..............TU/345S001AVR PARTS AND REPAIR ..è.. N.âMM
D002..............UT1245S001BILL JONES PARTS ..... N..DD
D002..............UT1245S002STEVENSON PARTS ..... N..DD
D002..............WE234TS001WMK INC. ...-. Y.*MM
D002..............12-ER3S001SMITH SUPPLY COMPANY ... . Y.%MM

Step 6. Extract rows from CONTACT_TABLE which are dependent rows of CUSTOMER_TABLE rows
extracted in step 2.
Number of rows extracted: 2

D006....CS228002JIMMY SMITHS ASSOCIATE BUYER CC212555 PEACHTREE ST

D006....CW337502TINA LLOYD MARKETING SUPERVISOR CC014556 E SHEA SCOTTSDALE

Total Number of rows extracted: 35

752 File-AID/RDX Reference

Figure 435. Example 1 - DPSI=YYNY

Extract Navigation Criteria Examples 753

DPSI=YYNN
Similar to Previous Extract Method OPTIMUM

This global navigation setting, without any overrides for any individual relationships, will extract all
direct dependents as well as their parent records, in other words, "While satisfying relationships select
only children of parents obtained while going down in the structure. Do not select children of a row
obtained by going up in the structure."

The extract of the driving table will be based on the specified selection criteria and all limits will be
respected. All of the qualified rows of the driving table are extracted, followed by the direct
dependents of the extracted rows from the driving table. Then, all of the parents of the extracted
direct dependent and driving table rows are extracted to satisfy the relationship that may exist.

DPSI=YYNN Example 1
With the global navigation control switches set to DPSI=YYNN, File-AID/RDX will extract data in the
following way, based on ORDER_TABLE as the driving table for all rows WHERE ORDER_NUMBER =
’BT33-C’ OR CUST_NUM = 'CW3375'.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - - - N Inactive 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y N - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE - Y N - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE - - - N Inactive 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- -------------------------------------------------------------------------------------------------
D004 4 D-DSNLOCAT.FRSAMP.ORDER_TABLE 

D001 8 D-DSNLOCAT.FRSAMP.PART_TABLE
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D002 0 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE


D003 2 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D005 8 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
11 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 0 D-DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 22 TOTAL rows extracted from 6 objects *****


Step 1. Extract rows from the driving table ORDER_TABLE that match ORDER_NUMBER =BT33-C or
CUST_NUM = ’CW3375’.

Number of rows extracted: 4

D004....AZ0099CW3375246-80-13572211445566778899PURCHASE1994-12-19OPEN ...á%.........SD1995-01-28..TERMINAL ACCESORIES

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FF6666CW3375112-23-92737665123872173567PURCHASE1994-12-16INITIAL ..àB..........GD1994-12-28..CONTROL UNIT
D004....GA1122CW3375238-18-2222362562872754534 PURCHASE1993-03-30OPEN ..é.....&.....PR1994-01-16..43 LINE 132 COLOR MO
754 File-AID/RDX Reference

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows extracted
in step 1.
Number of rows extracted: 8

D005....AZ0099r..12-ER3..................1994-11-09ONTIME
D005....AZ0099r..WE234T..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....BT33-C...HT5550../...............1994-06-09WAIT
D005....BT33-C...HT4320..................1993-06-25ONTIME
D005....FF6666~..UT1245..~...............1993-05-12ONTIME
D005....GA1122...PTLKIU..................1993-06-09BEHIND
D005....GA1122...TU/345..................1994-07-03ONTIME

Step 3. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows extracted
in step 3.
Number of rows extracted: 8

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

D001..............HT4320600’ 1/2 IN MAGNETIC TAPE1993-09-10R55-22...Ø...........EA....%.....NAA-985
D001..............HT5550HIGH DENSITY CARTRIDGE 1994-10-30TU/345... ...........EA... ......NBB-398
D001..............PTLKIU8 BYTE PENTIUM PIN MEMORY1994-02-10UT1245...~...........EA..........YDF-782
D001..............TU/345400 FT HIGH DENSITY CART 1994-10-26HT5550..à.....&......EA........é.NRX-931
D001..............UT124516 BYTE 70NS PIN MEMORY 1994-05-20LP6677..à.....&......EA........é.NRX-931
D001..............WE234TMC SCSI BUS AND ADAPTER 1994-01-11PST098...~...........FT... ......YII-232
D001..............12-ER3X-Z MONITOR HOUSING FIX. 1994-02-27JJ4537...~...........FT... ......YII-232

Step 4. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 1.
Number of rows extracted: 2

D003.......CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA UNITED

D003.......CW3375SONORA COMPUTING 33345 W SKYLINE BLVD PHOENIX AZ87408 UNITED

Total Number of rows extracted: 22

Figure 436. Example 1 - DPSI=YYNN

Extract Navigation Criteria Examples 755

DPSI=YYYY
Similar to Previous Extract Method MOST

This global navigation setting, without any overrides for any individual relationships, will extract all
direct, sibling, and indirect dependents as well as their parent records, in other words, "When
satisfying relationships, always chase the structure down to extract all children. If you go up in the
structure to extract a parent row, you must also go back down in the structure to extract any other
children of that parent row that may exist."

The extract of the driving table will be based on the specified selection criteria and all limits will be
respected. All of the qualified rows of the driving table are extracted, followed by the direct
dependents of the extracted rows from the driving table. Then, all of the parents of the extracted
direct dependent and driving table rows are extracted to satisfy the relationship that may exist.
Going up in the structure to extract a parent row will cause more children (siblings) from the prior
dependent table to be extracted. All other children (indirect) of the currently extracted rows are then
also extracted. The extract is in effect being constantly re-driven as new rows are selected, in both the
downward and upward direction until all possible relationships are satisfied. This cycle continues until
steps no longer result in additional rows extracted or the cycle number exceeds the specified
maximum cycle number.

DPSI=YYYY Example 1
With the global navigation control switches set to DPSI=YYYY, File-AID/RDX will extract data in the
following way, based on ORDER_TABLE as the driving table for all rows WHERE ORDER_NUMBER =
’BT33-C’ OR CUST_NUM = ’CW3375’.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - - - Y 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y Y - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE Y Y Y Y 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE - Y Y - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE - - - Y 
FRSAMP.SUPPLIER_TABLE SUPPPART 
756 File-AID/RDX Reference

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- ------------------------------------------------------------------------------------------------
D004 17 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
13 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D001 20 D-DSNLOCAT.FRSAMP.PART_TABLE
20 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D002 24 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
24 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 11 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
11 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D005 39 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
21 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
18 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
D006 14 D-DSNLOCAT.FRSAMP.CONTACT_TABLE
14 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 125 TOTAL rows extracted from 6 objects *****

Step 1. Extract rows from the driving table ORDER_TABLE that match ORDER_NUMBER = ’BT33-C’
or CUST_NUM = ’CW3375’.

Number of rows extracted: 4

D004....AZ0099CW3375246-80-13572211445566778899PURCHASE1994-12-19OPEN ...á%.........SD1995-01-28..TERMINAL ACCESORIES

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FF6666CW3375112-23-92737665123872173567PURCHASE1994-12-16INITIAL ..àB..........GD1994-12-28..CONTROL UNIT
D004....GA1122CW3375238-18-2222362562872754534 PURCHASE1993-03-30OPEN ..é.....&.....PR1994-01-16..43 LINE 132 COLOR MO

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows extracted
in step 1.
Number of rows extracted: 8

D005....AZ0099r..12-ER3..................1994-11-09ONTIME
D005....AZ0099r..WE234T..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....BT33-C...HT5550../...............1994-06-09WAIT
D005....BT33-C...HT4320..................1993-06-25ONTIME
D005....FF6666~..UT1245..~...............1993-05-12ONTIME
D005....GA1122...PTLKIU..................1993-06-09BEHIND
D005....GA1122...TU/345..................1994-07-03ONTIME

Step 3. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows extracted
in Step 2.
Number of rows extracted: 8

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

D001..............HT4320600’ 1/2 IN MAGNETIC TAPE1993-09-10R55-22...Ø...........EA....%.....NAA-985
D001..............HT5550HIGH DENSITY CARTRIDGE 1994-10-30TU/345... ...........EA... ......NBB-398
D001..............PTLKIU8 BYTE PENTIUM PIN MEMORY1994-02-10UT1245...~...........EA..........YDF-782
D001..............TU/345400 FT HIGH DENSITY CART 1994-10-26HT5550..à.....&......EA........é.NRX-931
D001..............UT124516 BYTE 70NS PIN MEMORY 1994-05-20LP6677..à.....&......EA........é.NRX-931
D001..............WE234TMC SCSI BUS AND ADAPTER 1994-01-11PST098...~...........FT... ......YII-232
D001..............12-ER3X-Z MONITOR HOUSING FIX. 1994-02-27JJ4537...~...........FT... ......YII-232

Step 4. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 1.
Number of rows extracted: 2

D003.........CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA UNITED

D003.........CW3375SONORA COMPUTING 33345 W SKYLINE BLVD PHOENIX AZ87408 UNITED
Extract Navigation Criteria Examples 757

Step 5. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
Step 3.
Number of rows extracted: 11

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM
D002..............HT4320S001BILL JONES PARTS ...&. N.@MM
D002..............HT5550S001WMK INC. ..... N..MM
D002..............PTLKIUS001AA SUPPLY COMPANY ..........Y..MM
D002..............PTLKIUS002SMITH SUPPLY COMPANY ..... Y..MM
D002..............TU/345S001AVR PARTS AND REPAIR ..è.. N.âMM
D002..............UT1245S001BILL JONES PARTS ..... N..DD
D002..............UT1245S002STEVENSON PARTS ..... N..DD
D002..............WE234TS001WMK INC. ...-. Y.*MM
D002..............12-ER3S001SMITH SUPPLY COMPANY ... . Y.%MM

Step 6. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in Step 3.
Number of rows extracted: 9

D005....BB1111...PTLKIU.. ....... .......1993-06-09ONTIME 

D005....BB1111...TU/345..&...............1994-10-09ONTIME 
D005....BS1188h..AA4555..................1993-06-09ONTIME 
D005....BS1188h..12-ER3.Å................1993-10-30ONTIME 
D005....DQ0066Ã..PTLKIU.. .......é.......1994-06-09WAIT 
D005....FA0011...AA4555.......ð..î.......1994-06-09BEHIND 
D005....GG22-S...HT5550..................1994-10-15ONTIME 
D005....GG22-S...HT4320..&...............1994-09-09ONTIME 
D005....IA2121...PTLKIU.g.....ä..î.......1994-11-09BEHIND 

Step 7. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in Step 6.
Number of rows extracted: 6

D004....BB1111CU4477125-23-45355402038500234524PURCHASE1994-01-31OPEN ..fÏ..........ON1994-02-28..LASER PRINTER 

D004....BS1188CS1144612-20-44253430982643534442PURCHASE1994-11-05PRIORITY....æ....æ....PR1994-12-09..VDT COVERS - BLACK
D004....DQ0066CC3300754-22-89273768890823866665PURCHASE1994-02-04OPEN ..À&..........GD1994-12-13..MOLDED KEYBOARD FRAM
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...Ø....Ø.....SD1994-12-12..DIODES
D004....GG22-SCS0060229-84-98886011340956008564SUBCONTR1994-09-28REVIEW ..ì°<..ì°<.... 1994-10-01..9600 BAUD DIAL-

Step 8. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in Step 7.
Number of rows extracted: 6

D003................CC3300JORDAN COMPUTING 1224 W WACKER DR CHICAGO IL60610 UNI

D003................CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648 UNI
D003................CS0060WILD TURNKEY SYSTEMS 4562 E BOURBON ST NEW ORLEANS LA70128 UNI
D003................CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243 UNI
D003................CU4477KNIGHT & QUEEN CONSULTING 123 FROST AVE LONDON LU5 5TA UNI
D003................CW4533WHITE PEAK MANUFACTURING 1208 TECHNOLOGY DR COLORADO SPRINGS CO80919 UNI

Step 9. Extract rows from ORDER_TABLE which are child rows to CUSTOMER_TABLE rows extracted
in Steps 4 and 8 and that also match ORDER_NUMBER = ’BT33-C’ or CUST_NUM =
’CW3375’.
Number of rows extracted: 0
(Qualifying rows did not match selection criteria)
Step 10. Extract rows from CONTACT_TABLE which are child rows to CUSTOMER_TABLE rows
extracted in Steps 4 and 8.
758 File-AID/RDX Reference

Number of rows extracted: 10

D006..CC330002TONY SMITH PRESIDENT OF OPERATIONS CC013451 E BELL ST CHICAGO

D006..CC330003STEVE SMITH VICE PRESIDENT CC611231 W SHAWMUT AVE CHICAGO
D006..CC330004ARTHUR STEVENSON DIRECTOR OF MANUFACTURING CC013451 E BELL ST CHICAGO
D006..CE002102JIM SMITH MANAGER OF OPERATIONS CC024562 W 91 ST NEW YORK CITY
D006..CS006002GEORGE GRIMES VICE-PRESIDENT, MANUFACTURING CC11
D006..CS114402JOSE GARCIA MANAGER OF PURCHASING CC015660 W WILLOW SUITE 3 COLUMBUS
D006..CS228002JIMMY SMITHS ASSOCIATE BUYER CC212555 PEACHTREE ST
D006..CU447702HILDA PALMER MANAGER OF PURCHASING CC32
D006..CW337502TINA LLOYD MARKETING SUPERVISOR CC014556 E SHEA SCOTTSDALE
D006..CW453302ALICE JACKSON CHIEF MANUFACTURING MANAGER CC653450 W 7TH ST

Step 11. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows
extracted in Step 7.
Number of rows extracted: 6

D005....BB1111...YY5-UI.á.....à..î.......1994-12-09BEHIND 
D005....DQ0066Ã..YY5-UI.......H..........1993-11-12AHEAD 
D005....GG22-S...A55-44..ø...............1993-06-15ONTIME 
D005....GG22-S...R55-22..°...............1994-10-02AHEAD 
D005....IA2121...RW-098.`&...............1993-06-08WAIT 
D005....IA2121...I0YU12.á.....Q..........1994-02-08BEHIND 

Step 12. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in Step 11.
Number of rows extracted: 5

D001..............A55-44TONER CARTRIDGE 1994-10-14WA2209...n...........EA....<.....YDF-564 

D001..............I0YU1216TP, 16/16 ETHERNET CARD1994-11-10TZC098...&...........EA...ø......YKK-053 
D001..............RW-098FINISHED INSPECTION 1994-05-10 ..........EA..à.......NMX-639 
D001..............R55-22900 FT 1/2 INCH MAG TAPE 1994-12-20HT4320..À.....&......EA........Ê.NRX-931 
D001..............YY5-UICD ROM HOUSING 1993-06-24H229ZZ...°...........FT... ......YII-232 

Step 13. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
Step 12.
Number of rows extracted: 6

D002..........A55-44S001CAL PARTS ...Í. Y.@DD 

D002..........I0YU12S001TOM DEE COMPANY ..... Y..MM 
D002..........RW-098S001AVR PARTS AND REPAIR N.%MM 
D002..........RW-098S002SOUTH STORES N.%MM 
D002..........R55-22S001WESTERN PARTS ..à.....&.N.<MM 
D002..........YY5-UIS001BRM PARTS CO. ...&. Y..DD 

Step 14. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in Step 12.
Number of rows extracted: 7

D005AA2222...I0YU12.. ...............1993-01-02ONTIME 
D005AA2222...YY5-UI.......æ..`.......1994-10-23AHEAD 
D005AA2222...A55-44.. ...............1994-06-22AHEAD 
D005CC6666Ã..A55-44..................1994-11-09ONTIME 
D005ET2555í..I0YU12..Ø...............1994-11-12ONTIME 
D005GT4444à..I0YU12.. ....h..á.......1994-02-09AHEAD 
D005LP4664/..R55-22.Ç.....ü..&.......1994-12-09ONTIME 

Step 15. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in Step 14.
Number of rows extracted: 5

D004....AA2222CC3300749-81-12125129384759872345PURCHASE1993-11-22OPEN ..ÃÉ..........ON1993-12-28..CASINGS AND CIRCUIT

D004....CC6666CG3499249-02-55233620987453453454PURCHASE1994-06-18REVIEW .ã.a...Áø.....SD1994-05-06..486 66MGZ 12K RAM D
D004....ET2555CC3300155-43-16735312294875734004PURCHASE1993-01-15OPEN ...&....&.....ON1993-12-28..9600 BAUD DIAL-UP M
D004....GT4444CN0022388-12-11113054549358609843PURCHASE1993-08-28OPEN ..Ìo....&.....RM1993-12-28..9600 BAUD DIAL-UP M
D004....LP4664CW4533268-73-78323898712001293402PURCHASE1994-05-08OPEN ..ßÏ@.........GD1995-12-13..100 OHM TWIN PRINT 
Extract Navigation Criteria Examples 759

Step 16. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in Step 15.
Number of rows extracted: 2

D003................CG3499AUTOBAHN ASSOCIATES EIFFESTRASSE 901 1678 DUESSELDORF 13

D003................CN0022RUSTIC DISTRIBUTION 2233 W BLUERIDGE PARKWAY MILWAUKEE WI53202

Step 17. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in Step 15.
Number of rows extracted: 6

D005AA2222...H229ZZ..........ì.......1994-02-12AHEAD 
D005AA2222...UT1234..ø...............1994-01-09AHEAD 
D005ET2555í..RTY0TP..-...............1994-06-09ONTIME 
D005ET2555í..JJ4537.. ...............1993-06-09WAIT 
D005GT4444à..KL4445..ø.......á.......1993-01-15ONTIME 
D005GT4444à..PST098.. .......ï.......1994-06-09ONTIME

Step 18. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in Step 17.
Number of rows extracted: 6

D001..............H229ZZCD ROM DRIVE CHASIS 1994-10-15YY5-UI....*........ [email protected] 

D001..............JJ4537MONITOR FIXTURES 1994-06-2012-ER3............. .EA...&*.....NAS-716 
D001..............KL4445KEYBOARD CABLE ADAPTER 1993-06-1634-TDZ...-...........EA....<.....YJI-630 
D001..............PST098VESA-BUS FAST SCSI 1994-11-20WE234T...&...........EA...ø<.....YKK-053 
D001..............RTY0TPTJS-MONITOR CASE 1994-12-2012-ER3..q............EA..à.......NMX-639 
D001..............UT1234ALLOY WIRE ENCASEMENT 1993-06-12QM9944...&...........EA...ø......YKK-053 

Step 19. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
Step 18.
Number of rows extracted: 6

D002..........H229ZZS001SAN JOSE SUPPLIES ....* Y..MM 

D002..........JJ4537S001JOHNSON PARTS ..... N..MM 
D002..........KL4445S001CAL PARTS ..... Y..DD 
D002..........PST098S001SAN JOSE SUPPLIES ..... Y..DD 
D002..........RTY0TPS001BRM PARTS CO. ..h.. N..DD 
D002..........UT1234S001ABG AND SONS ..... Y..MM 

Step 20. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in Step 18.
Number of rows extracted: 2

D005HY3333...RTY0TP..........&.......1994-06-04ONTIME 
D005JC7070ø..PST098..&...............1993-03-09ONTIME 

Step 21. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in Step 20.
Number of rows extracted: 2

D004....HY3333CS1144334-97-55553011293487520374PURCHASE1993-03-04OPEN ..îÊ....-.....ON1993-08-09..CD-ROM DRIVE 

D004....JC7070CJ1125337-99-033361010123&4172301PURCHASE1994-02-13HOLD ..Îïð.........GD1993-02-28..PRINTER RIBBON CART

Step 22. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in Step 21.
Number of rows extracted: 1

D003................CJ1125TRANSPACIFIC 222 34 FUJI ST TOKOYO 

760 File-AID/RDX Reference

Step 23. Extract rows from ORDER_TABLE which are child rows to CUSTOMER_TABLE rows extracted
in Steps 16 and 20 and that also match ORDER_NUMBER = ’BT33-C’ or CUST_NUM =
’CW3375’.
Number of rows extracted: 0
(Qualifying rows did not match selection criteria)
Step 24. Extract rows from CONTACT_TABLE which are child rows to CUSTOMER_TABLE rows
extracted in Steps 16 and 22.
Number of rows extracted: 4

D006..CG349902MICK JAIGER PURCHASING DIRECTOR CC73HANSAALLEE 402 2000 HAMBURG 26

D006..CJ112502BILL WYETH MANAGER,,MANUFACTURING CC01
D006..CJ112503WALTER DURHAM DIRECTOR OF FINANCE CC21
D006..CN002202MARY ANN JOHNSON SUPERVISOR CC042114 E HAMLET AVE 

Step 25. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows
extracted in Step 21.
Number of rows extracted: 1

D005HY3333...QWZ-34.ß........ñ.......1993-10-08BEHIND 

Step 26. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in Step 25.
Number of rows extracted: 1

D001..............QWZ-34WIRING HARNESS 1993-11-18UT1234...°...........EA... ......YJH-344 

Step 27. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
Step 26.
Number of rows extracted: 1

D002..........QWZ-34S001SUPPLIERS INC. ... . Y..DD 

Step 28. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in Step 26.
Number of rows extracted: 0
Total Number of rows extracted: 125
Extract Navigation Criteria Examples 761

Figure 437. Example 1 - DPSI=YYYY

762 File-AID/RDX Reference

DPSI=YYYY, CYCLE=1, QUIESCE=Q

Similar to Previous Extract Method MOST with CYCLE=1

This global navigation setting, without any overrides for any individual relationships, will extract all
direct, sibling, and indirect dependents as well as their parent records, in other words, "When
satisfying relationships, always chase the structure down to extract all children. If you go up in the
structure to extract a parent row, you must also go back down in the structure to extract any other
children of that parent row that may exist."

The extract of the driving table will be based on the specified selection criteria and all limits will be
respected. All of the qualified rows of the driving table are extracted, followed by the direct
dependents of the extracted rows from the driving table. Then, all of the parents of the extracted
direct dependent and driving table rows are extracted to satisfy the relationship that may exist.
Going up in the structure to extract a parent row will cause more children (siblings) from the prior
dependent table to be extracted. All other children (indirect) of the currently extracted rows are then
also extracted. The extract is when the cycle limit for all relationships has been reached.

DPSI=YYYY CYCLE=1 Example 1

With the global navigation control switches set to DPSI=YYYY and all relationships CYCLE=1, File-
AID/RDX will extract data in the following way, based on ORDER_TABLE as the driving table for all
rows WHERE ORDER_NUMBER = ’BT33-C’ OR CUST_NUM = ’CW3375’.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria Sampling Criteria
Seq Object Name Dir Par Sib Ind Status Cycle MaxRow Dep Status
---- ----------------------------------- --- --- --- --- ------- ----- ------ --- ------
0001 FRSAMP.CUSTOMER_TABLE - - - Y 1 * *
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y Y - 1 * *
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE Y Y Y Y 1 * *
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE - Y Y - 1 * *
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE - - - Y 1 * *
FRSAMP.SUPPLIER_TABLE SUPPPART 
Extract Navigation Criteria Examples 763

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- ------------------------------------------------------------------------------------------------
D004 10 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
6 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D001 8 D-DSNLOCAT.FRSAMP.PART_TABLE
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D002 11 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
11 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.SUPPLIER_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 8 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_TABLE


D005 17 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
9 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 2 D-DSNLOCAT.FRSAMP.CONTACT_TABLE
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.CONTACT_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 56 TOTAL rows extracted from 6 objects *****


Step 1. Extract rows from the driving table ORDER_TABLE that match ORDER_NUMBER = ’BT33-C’
or CUST_NUM = ’CW3375’.

Number of rows extracted: 4

D004....AZ0099CW3375246-80-13572211445566778899PURCHASE1994-12-19OPEN ...á%.........SD1995-01-28..TERMINAL ACCESORIES

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FF6666CW3375112-23-92737665123872173567PURCHASE1994-12-16INITIAL ..àB..........GD1994-12-28..CONTROL UNIT
D004....GA1122CW3375238-18-2222362562872754534 PURCHASE1993-03-30OPEN ..é.....&.....PR1994-01-16..43 LINE 132 COLOR M

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows extracted
in step 1.
Number of rows extracted: 8

D005....AZ0099r..12-ER3..................1994-11-09ONTIME
D005....AZ0099r..WE234T..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....BT33-C...HT5550../...............1994-06-09WAIT
D005....BT33-C...HT4320..................1993-06-25ONTIME
D005....FF6666~..UT1245..~...............1993-05-12ONTIME
D005....GA1122...PTLKIU..................1993-06-09BEHIND
D005....GA1122...TU/345..................1994-07-03ONTIME

Step 3. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows extracted
in Step 2.
764 File-AID/RDX Reference

Number of rows extracted: 8

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

D001..............HT4320600’ 1/2 IN MAGNETIC TAPE1993-09-10R55-22...Ø...........EA....%.....NAA-985
D001..............HT5550HIGH DENSITY CARTRIDGE 1994-10-30TU/345... ...........EA... ......NBB-398
D001..............PTLKIU8 BYTE PENTIUM PIN MEMORY1994-02-10UT1245...~...........EA..........YDF-782
D001..............TU/345400 FT HIGH DENSITY CART 1994-10-26HT5550..à.....&......EA........é.NRX-931
D001..............UT124516 BYTE 70NS PIN MEMORY 1994-05-20LP6677..à.....&......EA........é.NRX-931
D001..............WE234TMC SCSI BUS AND ADAPTER 1994-01-11PST098...~...........FT... ......YII-232
D001..............12-ER3X-Z MONITOR HOUSING FIX. 1994-02-27JJ4537...~...........FT... ......YII-232

Step 4. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 1.
Number of rows extracted: 2

D003.........CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA UNITED

D003.........CW3375SONORA COMPUTING 33345 W SKYLINE BLVD PHOENIX AZ87408 UNITED

Step 5. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
Step 3.
Number of rows extracted: 11

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM
D002..............HT4320S001BILL JONES PARTS ...&. N.@MM
D002..............HT5550S001WMK INC. ..... N..MM
D002..............PTLKIUS001AA SUPPLY COMPANY ..........Y..MM
D002..............PTLKIUS002SMITH SUPPLY COMPANY ..... Y..MM
D002..............TU/345S001AVR PARTS AND REPAIR ..è.. N.âMM
D002..............UT1245S001BILL JONES PARTS ..... N..DD
D002..............UT1245S002STEVENSON PARTS ..... N..DD
D002..............WE234TS001WMK INC. ...-. Y.*MM
D002..............12-ER3S001SMITH SUPPLY COMPANY ... . Y.%MM

Step 6. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in Step 3.
Number of rows extracted: 9

D005....BB1111...PTLKIU.. ....... .......1993-06-09ONTIME 

D005....BB1111...TU/345..&...............1994-10-09ONTIME 
D005....BS1188h..AA4555..................1993-06-09ONTIME 
D005....BS1188h..12-ER3.Å................1993-10-30ONTIME 
D005....DQ0066Ã..PTLKIU.. .......é.......1994-06-09WAIT 
D005....FA0011...AA4555.......ð..î.......1994-06-09BEHIND 
D005....GG22-S...HT5550..................1994-10-15ONTIME 
D005....GG22-S...HT4320..&...............1994-09-09ONTIME 
D005....IA2121...PTLKIU.g.....ä..î.......1994-11-09BEHIND 

Step 7. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in Step 6.
Number of rows extracted: 6

D004....BB1111CU4477125-23-45355402038500234524PURCHASE1994-01-31OPEN ..fÏ..........ON1994-02-28..LASER PRINTER

D004....BS1188CS1144612-20-44253430982643534442PURCHASE1994-11-05PRIORITY....æ....æ....PR1994-12-09..VDT COVERS - BLACK
D004....DQ0066CC3300754-22-89273768890823866665PURCHASE1994-02-04OPEN ..À&..........GD1994-12-13..MOLDED KEYBOARD FRAM
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...Ø....Ø.....SD1994-12-12..DIODES
D004....GG22-SCS0060229-84-98886011340956008564SUBCONTR1994-09-28REVIEW ..ì°<..ì°<.... 1994-10-01..9600 BAUD DIAL-UP MO
D004....IA2121CW4533111-22-33339743765675123989REWORK 1994-02-28OPEN ...Á%.........RM1994-03-02..REASSEMBLE PRINTER 

Step 8. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in Step 7.
Extract Navigation Criteria Examples 765

Number of rows extracted: 6

D003................CC3300JORDAN COMPUTING 1224 W WACKER DR CHICAGO IL60610

D003................CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648
D003................CS0060WILD TURNKEY SYSTEMS 4562 E BOURBON ST NEW ORLEANS LA70128
D003................CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243
D003................CU4477KNIGHT & QUEEN CONSULTING 123 FROST AVE LONDON LU5 5TA 
D003................CW4533WHITE PEAK MANUFACTURING 1208 TECHNOLOGY DR COLORADO SPRINGS CO80919

Step 9. Extract rows from ORDER_TABLE which are child rows to CUSTOMER_TABLE rows extracted
in Steps 4 and 8 and that also match ORDER_NUMBER = ’BT33-C’ or CUST_NUM =
’CW3375’.
Number of rows extracted: 0
(Qualifying rows did not match selection criteria)
Step 10. Extract rows from CONTACT_TABLE which are child rows to CUSTOMER_TABLE rows
extracted in Step 4.
Number of rows extracted: 2

D006..CS228002JIMMY SMITHS ASSOCIATE BUYER CC212555 PEACHTREE ST

D006..CW337502TINA LLOYD MARKETING SUPERVISOR CC014556 E SHEA SCOTTSDALE

Total Number of rows extracted: 56

Figure 438. Example 1 - DPSI=YYYY, CYCLE=1, QUIESCE=Q

766 File-AID/RDX Reference

DPSI=YYNN Modified
Similar to Previous Extract Method DETAILED

This extract navigation rule is: "Satisfy relationships by chasing all of the relationships exactly as
specified by the user in the "Relationship Navigation Criteria" panel." In this method, as in all methods,
the extract of the driving table will be based on the specified selection criteria and all limits will be
respected. The users specify how they want the product to chase relationships by setting the
navigation settings individually, overriding the global navigation setting.

Modified Example 1
With the global navigation control switches set to DPSI=YYNN, but the Sibling and Indirect
navigation settings "Modified" on individual relationships, this extract example will extract data
based on ORDER_TABLE as the driving table for all rows WHERE ORDER_NUMBER = ’BT33-C’ OR
CUST_NUM = ’CW3375’ and this modified navigation selection:

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - - - Y 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y N - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE Y Y N - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE - Y Y - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE - - - N Inactive 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- -------------------------------------------------------------------------------------------------
D004 10 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
6 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D001 8 D-DSNLOCAT.FRSAMP.PART_TABLE
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D002 0 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 8 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D005 17 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
9 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 10 D-DSNLOCAT.FRSAMP.CONTACT_TABLE
10 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 53 TOTAL rows extracted from 6 objects *****


Note that File-AID/RDX automatically excludes 1 relationship, PART_TABLE to SUPPLIER_TABLE,

which was marked INDirect=N. As ORDER_TABLE is the driving table, SUPPLIER_TABLE is a child
that requires going UP in the structure.

Step 1. Extract rows from the driving table ORDER_TABLE.

Extract Navigation Criteria Examples 767

Number of rows extracted: 4

D004....AZ0099CW3375246-80-13572211445566778899PURCHASE1994-12-19OPEN ...á%.........SD1995-01-28..TERMINAL ACCESORIES

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FF6666CW3375112-23-92737665123872173567PURCHASE1994-12-16INITIAL ..àB..........GD1994-12-28..CONTROL UNIT
D004....GA1122CW3375238-18-2222362562872754534 PURCHASE1993-03-30OPEN ..é.....&.....PR1994-01-16..43 LINE 132 COLOR M

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows extracted
in step 1.
Number of rows extracted: 8

D005....AZ0099r..12-ER3..................1994-11-09ONTIME
D005....AZ0099r..WE234T..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....BT33-C...HT5550../...............1994-06-09WAIT
D005....BT33-C...HT4320..................1993-06-25ONTIME
D005....FF6666~..UT1245..~...............1993-05-12ONTIME
D005....GA1122...PTLKIU..................1993-06-09BEHIND

Step 3. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows extracted
in step 2.
Number of rows extracted: 8

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

D001..............HT4320600’ 1/2 IN MAGNETIC TAPE1993-09-10R55-22...Ø...........EA....%.....NAA-985
D001..............HT5550HIGH DENSITY CARTRIDGE 1994-10-30TU/345... ...........EA... ......NBB-398
D001..............PTLKIU8 BYTE PENTIUM PIN MEMORY1994-02-10UT1245...~...........EA..........YDF-782
D001..............TU/345400 FT HIGH DENSITY CART 1994-10-26HT5550..à.....&......EA........é.NRX-931
D001..............UT124516 BYTE 70NS PIN MEMORY 1994-05-20LP6677..à.....&......EA........é.NRX-931
D001..............WE234TMC SCSI BUS AND ADAPTER 1994-01-11PST098...~...........FT... ......YII-232
D001..............12-ER3X-Z MONITOR HOUSING FIX. 1994-02-27JJ4537...~...........FT... ......YII-232

Step 4. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 1.
Number of rows extracted: 2

D003.........CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA UNITED

D003.........CW3375SONORA COMPUTING 33345 W SKYLINE BLVD PHOENIX AZ87408 UNITED

Step 5. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 3.
Number of rows extracted: 9

D005....BB1111...PTLKIU.. ....... .......1993-06-09ONTIME 

D005....BB1111...TU/345..&...............1994-10-09ONTIME 
D005....BS1188h..AA4555..................1993-06-09ONTIME 
D005....BS1188h..12-ER3.Å................1993-10-30ONTIME 
D005....DQ0066Ã..PTLKIU.. .......é.......1994-06-09WAIT 
D005....FA0011...AA4555.......ð..î.......1994-06-09BEHIND 
D005....GG22-S...HT5550..................1994-10-15ONTIME 

Step 6. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 5.
Number of rows extracted: 6

D004....BB1111CU4477125-23-45355402038500234524PURCHASE1994-01-31OPEN ..f™..........ON1994-02-28..LASER PRINTER

D004....BS1188CS1144612-20-44253430982643534442PURCHASE1994-11-05PRIORITY....â....â....PR1994-12-09..VDT COVERS - BLACK
D004....DQ0066CC3300754-22-89273768890823866665PURCHASE1994-02-04OPEN ..Ä&..........GD1994-12-13..MOLDED KEYBOARD FRA
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...\....\.....SD1994-12-12..DIODES
D004....GG22-SCS0060229-84-98886011340956008564SUBCONTR1994-09-28REVIEW ..ì~<..ì~<.... 1994-10-01..9600 BAUD DIAL-UP MO
D004....IA2121CW4533111-22-33339743765675123989REWORK 1994-02-28OPEN ...Á%.........RM1994-03-02..REASSEMBLE PRINTER 

Step 7. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 6.
768 File-AID/RDX Reference

Number of rows extracted: 6

D003.......CC3300JORDAN COMPUTING 1224 W WACKER DR CHICAGO IL60610

D003.......CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648 U
D003.......CS0060WILD TURNKEY SYSTEMS 4562 E BOURBON ST NEW ORLEANS LA70128 U
D003.......CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243 U
D003.......CU4477KNIGHT & QUEEN CONSULTING 123 FROST AVE LONDON LU5 5TA U
D003.......CW4533WHITE PEAK MANUFACTURING 1208 TECHNOLOGY DR COLORADO SPRINGS CO80919 U

Step 8. Extract rows from CONTACT_TABLE which are child rows to CUSTOMER_TABLE rows
extracted in steps 4 and 7.
Number of rows extracted: 10

D006..CS228002JIMMY SMITHS ASSOCIATE BUYER CC212555 PEACHTREE ST

D006..CW337502TINA LLOYD MARKETING SUPERVISOR CC014556 E SHEA SCOTTSDALE
D006..CC330002TONY SMITH PRESIDENT OF OPERATIONS CC013451 E BELL ST CHICAGO
D006..CC330003STEVE SMITH VICE PRESIDENT CC611231 W SHAWMUT AVE CHICAGO
D006..CC330004ARTHUR STEVENSON DIRECTOR OF MANUFACTURING CC013451 E BELL ST CHICAGO
D006..CE002102JIM SMITH MANAGER OF OPERATIONS CC024562 W 91 ST NEW YORK CITY
D006..CS006002GEORGE GRIMES VICE-PRESIDENT, MANUFACTURING CC11
D006..CS114402JOSE GARCIA MANAGER OF PURCHASING CC015660 W WILLOW SUITE 3 COLUMBUS
D006..CU447702HILDA PALMER MANAGER OF PURCHASING CC32
D006..CW453302ALICE JACKSON CHIEF MANUFACTURING MANAGER CC653450 W 7TH ST

Total Number of rows extracted: 53

Figure 439. Example 1 - DPSI=YYNN (Modified)

Extract Navigation Criteria Examples 769

DPSI=PYNN Direct Plus

This extract navigation rule is: "Extract all of the direct relationships of the driving object, i.e. all of its
parents and first level dependents only. Direct "Plus" means resolve all objects’ parents until there are no
more parents to return." Direct Plus must be set in your profile (see Direct on page 58). In this method,
as in all methods, the extract of the driving table will be based on the specified selection criteria and
all limits will be respected.

Direct Plus Example 1

With the global navigation control switches set to DPSI=PYNN Direct Plus, this extract example will
extract data based on ORDER_TABLE as the driving table for all rows WHERE ORDER_NUMBER =
’BT33-C’ OR CUST_NUM = ’CW3375’. The users cannot set any other navigation settings during the
extract specification.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - Y N - 
FRSAMP.ORDER_TABLE 
0002 FRSAMP.ORDER_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0003 FRSAMP.PART_TABLE - Y N - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- ------------------------------------------------------------------------------------------------
D001 8 D-DSNLOCAT.FRSAMP.PART_TABLE 
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D002 4 D-DSNLOCAT.FRSAMP.ORDER_TABLE 

*** Selection Criteria Applied *** 

D003 8 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE 
8 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D004 2 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 


***** 22 TOTAL rows extracted from 4 objects ***** 

Note that File-AID/RDX automatically excludes 2 relationships, PART_TABLE to SUPPLIER_TABLE,

and CUSTOMER_TABLE to CONTACT_TABLE as a result of Direct Plus.

Step 1. Extract rows from the driving table ORDER_TABLE.

Number of rows extracted: 4

D002....AZ0099CW3375246-80-13572211445566778899PURCHASE1994-12-19OPEN ...á%.........SD1995-01-28..TERMINAL ACCESORIES

D002....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D002....FF6666CW3375112-23-92737665123872173567PURCHASE1994-12-16INITIAL ..àB..........GD1994-12-28..CONTROL UNIT
D002....GA1122CW3375238-18-2222362562872754534 PURCHASE1993-03-30OPEN ..é.....&.....PR1994-01-16..43 LINE 132 COLOR M

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows extracted
in step 1.
770 File-AID/RDX Reference

Number of rows extracted: 8

D003....AZ0099r..12-ER3..................1994-11-09ONTIME
D003....AZ0099r..WE234T..................1993-06-09ONTIME
D003....BT33-C...AA4555.......á..........1993-03-09AHEAD
D003....BT33-C...HT5550../...............1994-06-09WAIT
D003....BT33-C...HT4320..................1993-06-25ONTIME
D003....FF6666~..UT1245..~...............1993-05-12ONTIME
D003....GA1122...PTLKIU..................1993-06-09BEHIND
D003....GA1122...TU/345..................1994-07-03ONTIME

Step 3. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows extracted
in step 2.
Number of rows extracted: 8

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

D001..............HT4320600’ 1/2 IN MAGNETIC TAPE1993-09-10R55-22...Ø...........EA....%.....NAA-985
D001..............HT5550HIGH DENSITY CARTRIDGE 1994-10-30TU/345... ...........EA... ......NBB-398
D001..............PTLKIU8 BYTE PENTIUM PIN MEMORY1994-02-10UT1245...~...........EA..........YDF-782
D001..............TU/345400 FT HIGH DENSITY CART 1994-10-26HT5550..à.....&......EA........é.NRX-931
D001..............UT124516 BYTE 70NS PIN MEMORY 1994-05-20LP6677..à.....&......EA........é.NRX-931
D001..............WE234TMC SCSI BUS AND ADAPTER 1994-01-11PST098...~...........FT... ......YII-232
D001..............12-ER3X-Z MONITOR HOUSING FIX. 1994-02-27JJ4537...~...........FT... ......YII-232

Step 4. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 1.
Number of rows extracted: 2

D004.........CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA UNITED

D004.........CW3375SONORA COMPUTING 33345 W SKYLINE BLVD PHOENIX AZ87408 UNITED

Total Number of rows extracted: 22

Figure 440. Example 1 - DPSI=PYNN (Direct Plus)

Extract Navigation Criteria Examples 771

DPSI=CNNN All Children Only

This extract navigation rule is: "Extract the dependents of the driving object and all of their dependents
only. This option ignores all other Navigational Criteria Options." All Children Only must be set in your
profile (see Direct on page 58). Using the C method to extract data and only its dependent data can
lead to extracted data that is not loadable because of referential integrity issues due to the omitted
related parent data. This can be useful for extracting specific data that is then used for a purge
procedure.

In this method, as in all methods, the extract of the driving table will be based on the specified
selection criteria and all limits will be respected. The users cannot set any other navigation settings
during the extract specification.

All Children Only Example 1

With the global navigation control switches locked to All Children Only, this extract example will
extract data based on ORDER_TABLE as the driving table for all rows WHERE ORDER_NUMBER =
’BT33-C’ OR CUST_NUM = ’CW3375’ and this navigation selection:

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.ORDER_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- ------------------------------------------------------------------------------------------------
D001 4 D-FRSAMP.FRSAMP.ORDER_TABLE 

*** Selection Criteria Applied *** 

D002 8 D-FRSAMP.FRSAMP.ORDER_LINE_TABLE 
8 Rows from relationship Parent: D-FRSAMP.FRSAMP.ORDER_TABLE 
Dependent: D-FRSAMP.FRSAMP.ORDER_LINE_TABLE


***** 12 TOTAL rows extracted from 2 objects ***** 

As File-AID/RDX only extracts children, the extract stops after the first relationship as ORDER_TABLE
has only one direct dependent relationship to ORDER_LINE_TABLE.

Step 1. Extract rows from the driving table ORDER_TABLE.

Number of rows extracted: 4

D001....AZ0099CW3375246-80-13572211445566778899PURCHASE1994-12-19OPEN ...á%.........SD1995-01-28..TERMINAL ACCESORIES

D001....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D001....FF6666CW3375112-23-92737665123872173567PURCHASE1994-12-16INITIAL ..àB..........GD1994-12-28..CONTROL UNIT
D001....GA1122CW3375238-18-2222362562872754534 PURCHASE1993-03-30OPEN ..é.....&.....PR1994-01-16..43 LINE 132 COLOR M

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows extracted
in step 1.
Number of rows extracted: 8

D002....AZ0099r..12-ER3..................1994-11-09ONTIME
D002....AZ0099r..WE234T..................1993-06-09ONTIME
D002....BT33-C...AA4555.......á..........1993-03-09AHEAD
D002....BT33-C...HT5550../...............1994-06-09WAIT
D002....BT33-C...HT4320..................1993-06-25ONTIME
D002....FF6666~..UT1245..~...............1993-05-12ONTIME
D002....GA1122...PTLKIU..................1993-06-09BEHIND
D002....GA1122...TU/345..................1994-07-03ONTIME
772 File-AID/RDX Reference

Total Number of rows extracted: 12

Figure 441. Example 1 - DPSI=CNNN (All Children Only)

Extract Navigation Criteria Examples 773

DPSI=YYNY Example 2
Similar to Previous Extract Method STANDARD

With the global navigation control switches set to DPSI=YYNY, Example 2 will extract data based on
PART_TABLE as the driving table for all rows WHERE PART_NUMBER = ’AA4555’.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - - - Y 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y N - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE - Y N - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE Y - - - 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- ------------------------------------------------------------------------------------------------
D001 1 D-DSNLOCAT.FRSAMP.PART_TABLE

D002 2 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 3 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D004 3 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE


D005 3 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 3 D-DSNLOCAT.FRSAMP.CONTACT_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 15 TOTAL rows extracted from 6 objects *****


Step 1. Extract rows from the driving table PART_TABLE that match PART_NUMBER = ’AA4555’.

Number of rows extracted: 1

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

Step 2. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 1.
Number of rows extracted: 2

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM

Step 3. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 1.
Number of rows extracted: 3

D005....BS1188h..AA4555..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....FA0011...AA4555.......C..í.......1994-06-09BEHIND
774 File-AID/RDX Reference

Step 4. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 3.
Number of rows extracted: 3

D004....BS1188CS1144612-20-44253430982643534442PURCHASE1994-11-05PRIORITY....â....â....PR1994-12-09..VDT COVERS - BLACK

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...\....\.....SD1994-12-12..DIODES

Step 5. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 4.
Number of rows extracted: 3

D003................CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648

D003................CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243
D003................CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA

Step 6. Extract rows from CONTACT_TABLE which are child rows to CUSTOMER_TABLE rows
extracted in step 5.
Number of rows extracted: 3

D006....CE002102JIM SMITH MANAGER OF OPERATIONS CC024562 W 91 ST NEW YORK CITY

D006....CS114402JOSE GARCIA MANAGER OF PURCHASING CC015660 W WILLOW SUITE 3 COLUMBUS
D006....CS228002JIMMY SMITHS ASSOCIATE BUYER CC212555 PEACHTREE ST

Total Number of rows extracted: 15

Figure 442. Example 2 - DPSI=YYNY

Extract Navigation Criteria Examples 775

DPSI=YYNN Example 2
Similar to Previous Extract Method OPTIMUM

With the global navigation control switches set to DPSI=YYNN, this example will extract data with
PART_TABLE as the driving table for all rows WHERE PART_NUMBER = ’AA4555’.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - - - N Inactive 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y N - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE - Y N - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE Y - - - 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- ------------------------------------------------------------------------------------------------
D001 1 D-DSNLOCAT.FRSAMP.PART_TABLE

D002 2 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 3 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D004 3 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE


D005 3 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 0 D-DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 12 TOTAL rows extracted from 6 objects *****

Step 1. Extract rows from the driving table PART_TABLE that match PART_NUMBER = ’AA4555’.

Number of rows extracted: 1

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

Step 2. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 1.
Number of rows extracted: 2

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM

Step 3. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 1.
Number of rows extracted: 3

D005....BS1188h..AA4555..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....FA0011...AA4555.......C..í.......1994-06-09BEHIND
776 File-AID/RDX Reference

Step 4. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 3.
Number of rows extracted: 3

D004....BS1188CS1144612-20-44253430982643534442PURCHASE1994-11-05PRIORITY....â....â....PR1994-12-09..VDT COVERS - BLACK

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...\....\.....SD1994-12-12..DIODES

Step 5. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 4.
Number of additional rows extracted: 3

D003................CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648

D003................CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243
D003................CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA

Total Number of rows extracted: 12

Figure 443. Example 2 - DPSI=YYNN

Extract Navigation Criteria Examples 777

DPSI=YYYY Example 2
Similar to Previous Extract Method MOST

With the global navigation control switches set to DPSI=YYYY this extract example will extract data
based on PART_TABLE as the driving table for all rows WHERE PART_NUMBER = ’AA4555’.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE - - - Y 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y Y - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE - Y Y Y 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE Y Y Y - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE Y - - Y 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- ------------------------------------------------------------------------------------------------
D001 27 D-DSNLOCAT.FRSAMP.PART_TABLE
26 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D002 31 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
31 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 12 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
12 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D004 28 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
15 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE
13 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D005 48 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
31 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
17 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 15 D-DSNLOCAT.FRSAMP.CONTACT_TABLE
15 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE


Step 1. Extract rows from the driving table PART_TABLE that match PART_NUMBER = ’AA4555’.

Number of rows extracted: 1

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

Step 2. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 1.
Number of rows extracted: 2

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM

Step 3. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 1.
778 File-AID/RDX Reference

Number of rows extracted: 3

D005....BS1188h..AA4555..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....FA0011...AA4555.......C..í.......1994-06-09BEHIND

Step 4. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 3.
Number of rows extracted: 3

D004....BS1188CS1144612-20-44253430982643534442PURCHASE1994-11-05PRIORITY....â....â....PR1994-12-09..VDT COVERS - BLACK

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...\....\.....SD1994-12-12..DIODES

Step 5. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 4.
Number of rows extracted: 3

D003................CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648

D003................CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243
D003................CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA

Step 6. Extract rows from ORDER_TABLE which are child rows to CUSTOMER_TABLE rows extracted
in step 5.
Number of rows extracted: 3

D004....AD9797CE0021133-19-16225287322360092345WORK 1994-06-21PRIORITY...Ø..........GD1994-10-14..INSTALLATION AND ASS

D004....HY3333CS1144334-97-55553011293487520374PURCHASE1993-03-04OPEN ..íÉ....-.....ON1993-08-09..CD-ROM DRIVE
D004....IH66-CCS2280333-44-55559038729873676786CONTRACT1992-10-06OPEN ....â......... 1994-11-24..HIGH-PERFORMANCE MAG

Step 7. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows extracted
in steps 4 and 6.
Number of rows extracted: 7

D005AD9797p..AS-355..&...............1993-11-23BEHIND 
D005AD9797p..AS-777..................1993-06-09WAIT 
D005BS1188h..12-ER3.Å................1993-10-30ONTIME 
D005BT33-C...HT5550..Ø...............1994-06-09WAIT 
D005BT33-C...HT4320..°...............1993-06-25ONTIME 
D005HY3333...QWZ-34.ß........ñ.......1993-10-08BEHIND 
D005HY3333...RTY0TP..........&.......1994-06-04ONTIME 

Step 8. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows extracted
in step 7.
Number of rows extracted: 7

D001..............AS-355CIRCUIT RESTORATION 1994-06-30 ........&*FT... ......YNC-219

D001..............AS-777ADAPTOR INSTALLATION 1994-05-14 ........Ø.EA....*.....YDH-836
D001..............HT4320600' 1/2 IN MAGNETIC TAPE1993-09-10R55-22...ø...........EA....%.....NAA-985
D001..............HT5550HIGH DENSITY CARTRIDGE 1994-10-30TU/345... ...........EA... ......NBB-398
D001..............QWZ-34WIRING HARNESS 1993-11-18UT1234...°...........EA... ......YJH-344
D001..............RTY0TPTJS-MONITOR CASE 1994-12-2012-ER3..q............EA..à.......NMX-639
D001..............12-ER3X-Z MONITOR HOUSING FIX. 1994-02-27JJ4537...°...........FT... ......YII-232

Step 9. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 8.
Extract Navigation Criteria Examples 779

Number of rows extracted: 7

D002..........AS-355S001TOM DEE COMPANY ...ø. Y..DD 

D002..........AS-777S001JOHNSON PARTS ..... Y..DD 
D002..........HT4320S001BILL JONES PARTS ...&. N.@MM 
D002..........HT5550S001WMK INC. ..... N..MM 
D002..........QWZ-34S001SUPPLIERS INC. ... . Y..DD 
D002..........RTY0TPS001BRM PARTS CO. ..h.. N..DD 
D002..........12-ER3S001SMITH SUPPLY COMPANY ... . Y.%MM 

Step 10. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 8.
Number of rows extracted: 4

D005AZ0099r..12-ER3..................1994-11-09ONTIME
D005ET2555í..RTY0TP..-...............1994-06-09ONTIME
D005GG22-S...HT5550..................1994-10-15ONTIME
D005GG22-S...HT4320..&...............1994-09-09ONTIME

Step 11. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 10.
Number of rows extracted: 3

D004............ AZ0099CW3375PURCHASE1994-12-19OPEN ...á%.........SD1995-01-28..TERMINAL ACCESORIES 

D004............ ET2555CC3300PURCHASE1993-01-15OPEN ...&....&.....ON1993-12-28..9600 BAUD DIAL-UP MODEM
D004............ GG22-SCS0060SUBCONTR1994-09-28REVIEW ..ì°<..ì°<.... 1994-10-01..9600 BAUD DIAL-UP MODEM

Step 12. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 11.
Number of rows extracted: 3

D003................ CC3300 JORDAN COMPUTING 1224 W WACKER DR CHICAGO IL60610 

D003................ CS0060 WILD TURNKEY SYSTEMS 4562 E BOURBON ST NEW ORLEANS LA70128 
D003................ CW3375 SONORA COMPUTING 33345 W SKYLINE BLVD PHOENIX AZ87408 

Step 13. Extract rows from CONTACT_TABLE which are child rows to CUSTOMER_TABLE rows
extracted in steps 5 and 12.
Number of rows extracted: 8

D006.. CC3300 02TONY SMITH PRESIDENT OF OPERATIONS CC013451 E BELL ST CHICAGO

D006.. CC3300 03STEVE SMITH VICE PRESIDENT CC611231 W SHAWMUT AVE CHICAGO
D006.. CC3300 04ARTHUR STEVENSON DIRECTOR OF MANUFACTURING CC013451 E BELL ST CHICAGO
D006.. CE0021 02JIM SMITH MANAGER OF OPERATIONS CC024562 W 91 ST NEW YORK CITY
D006.. CS0060 02GEORGE GRIMES VICE-PRESIDENT, MANUFACTURING CC11
D006.. CS1144 02JOSE GARCIA MANAGER OF PURCHASING CC015660 W WILLOW SUITE 3 COLUMBUS
D006.. CS2280 02JIMMY SMITHS ASSOCIATE BUYER CC212555 PEACHTREE ST
D006.. CW3375 02TINA LLOYD MARKETING SUPERVISOR CC014556 E SHEA SCOTTSDALE

Step 14. Extract rows from ORDER_TABLE which are child rows to CUSTOMER_TABLE rows extracted
in step 12.
Number of rows extracted: 7

D004....AA2222 CC3300 749-81-12125129384759872345PURCHASE1993-11-22OPEN ..ÃÉ..........ON1993-12-28..CASINGS AND CIRCUITS

D004....BB5757 CS0060 135-79-24680327462050237456WORK 1994-10-11OPEN ..Áç..........--1994-12-03..SOLDERING OF SUB-CHAS
D004....CF7900 CC3300 431-00-22545529782098724503PURCHASE1993-04-30OPEN ..àìæ..àìæ....--1993-12-16..COAXIAL CABLE SPLICIN
D004....CV66-S CC3300 452-09-74123892477234534453SUBCONTR1991-06-27OPEN ..îË<..°Ø..... 1994-05-18..MULTISYNC 3FGE 70HZ M
D004....DQ0066 CC3300 754-22-89273768890823866665PURCHASE1994-02-04OPEN ..À&..........GD1994-12-13..MOLDED KEYBOARD FRAME
D004....FF6666 CW3375 112-23-92737665123872173567PURCHASE1994-12-16INITIAL ..àß..........GD1994-12-28..CONTROL UNIT

Step 15. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows
extracted in steps 11 and 14.
780 File-AID/RDX Reference

Number of rows extracted: 16

D005 AA2222...I0YU12.. ...............1993-01-02ONTIME

D005 AA2222...H229ZZ..........ì.......1994-02-12AHEAD
D005 AA2222...YY5-UI.......æ..`.......1994-10-23AHEAD
D005 AA2222...UT1234..ø...............1994-01-09AHEAD 
D005 AA2222...A55-44.. ...............1994-06-22AHEAD 
D005 AZ0099r..WE234T..................1993-06-09ONTIME
D005 BB5757ï..AS-334.. ....>..........1994-06-09AHEAD 
D005 DQ0066Ã..PTLKIU.. .......é.......1994-06-09WAIT 
D005 DQ0066Ã..YY5-UI.......H..........1993-11-12AHEAD 
D005 ET2555í..JJ4537.. ...............1993-06-09WAIT 
D005 ET2555í..I0YU12..Ø...............1994-11-12ONTIME 
D005 FF6666Ã..UT1245..°...............1993-05-12ONTIME 
D005 GA1122...TU/345..................1994-07-03ONTIME 
D005 GA1122...PTLKIU..................1993-06-09BEHIND 
D005 GG22-S...A55-44..ø...............1993-06-15ONTIME 
D005 GG22-S...R55-22..°...............1994-10-02AHEAD 

Step 16. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 15.
Number of rows extracted: 12

D001.............. AS-334 SOLDER AND INSPECTION 1993-11-12RW-532 ..........EA...ø......YKK-053 

D001.............. A55-44 TONER CARTRIDGE 1994-10-14WA2209...n...........EA....<.....YDF-564 
D001.............. H229ZZ CD ROM DRIVE CHASIS 1994-10-15YY5-UI....*........ [email protected] 
D001.............. I0YU12 16TP, 16/16 ETHERNET CARD1994-11-10TZC098...&...........EA...ø......YKK-053 
D001.............. JJ4537 MONITOR FIXTURES 1994-06-2012-ER3............. .EA...&*.....NAS-716 
D001.............. PTLKIU 8 BYTE PENTIUM PIN MEMORY1994-02-10UT1245...°...........EA..........YDF-782 
D001.............. R55-22 900 FT 1/2 INCH MAG TAPE 1994-12-20HT4320..À.....&......EA........Ê.NRX-931 
D001.............. TU/345 400 FT HIGH DENSITY CART 1994-10-26HT5550..À.....&......EA........Ê.NRX-931 
D001.............. UT1234 ALLOY WIRE ENCASEMENT 1993-06-12QM9944...&...........EA...ø......YKK-053 
D001.............. UT1245 16 BYTE 70NS PIN MEMORY 1994-05-20LP6677..À.....&......EA........Ê.NRX-931 
D001.............. WE234T MC SCSI BUS AND ADAPTER 1994-01-11PST098...°...........FT... ......YII-232 
D001.............. YY5-UI CD ROM HOUSING 1993-06-24H229ZZ...°...........FT... ......YII-232 

Step 17. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 16.
Number of rows extracted: 14

D002..........AS-334S001WESTERN PARTS ...-. Y..DD 

D002..........A55-44S001CAL PARTS ...Í. Y.@DD 
D002..........H229ZZS001SAN JOSE SUPPLIES ....* Y..MM 
D002..........I0YU12S001TOM DEE COMPANY ..... Y..MM 
D002..........JJ4537S001JOHNSON PARTS ..... N..MM 
D002..........PTLKIUS001AA SUPPLY COMPANY ..........Y..MM 
D002..........PTLKIUS002SMITH SUPPLY COMPANY ..... Y..MM 
D002..........R55-22S001WESTERN PARTS ..à.....&.N.<MM 
D002..........TU/345S001AVR PARTS AND REPAIR ..è.. N.æMM 
D002..........UT1234S001ABG AND SONS ..... Y..MM 
D002..........UT1245S001BILL JONES PARTS ..... N..DD 
D002..........UT1245S002STEVENSON PARTS ..... N..DD 
D002..........WE234TS001WMK INC. ...-. Y.*MM 
D002..........YY5-UIS001BRM PARTS CO. ...&. Y..DD 

Step 18. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 16.
Number of rows extracted: 8

D005BB1111...YY5-UI.á.....à..î.......1994-12-09BEHIND 
D005BB1111...PTLKIU.. ....... .......1993-06-09ONTIME 
D005BB1111...TU/345..&...............1994-10-09ONTIME 
D005CC6666Ã..A55-44..................1994-11-09ONTIME 
D005GT4444à..I0YU12.. ....h..á.......1994-02-09AHEAD 
D005IA2121...PTLKIU.g.....ä..î.......1994-11-09BEHIND 
D005IA2121...I0YU12.á.....Q..........1994-02-08BEHIND 
D005LP4664/..R55-22.Ç.....ü..&.......1994-12-09ONTIME 

Step 19. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 18.
Extract Navigation Criteria Examples 781

Number of rows extracted: 5

D004....BB1111125-23-45355402038500234524CU4477PURCHASE1994-01-31OPEN ..fÏ..........ON1994-02-28..LASER PRINTER 

D004....CC6666CG3499249-02-55233620987453453454PURCHASE1994-06-18REVIEW .ã.a...Áø.....SD1994-05-06..486 66MGZ 12K RAM DE
D004....GT4444CN0022388-12-11113054549358609843PURCHASE1993-08-28OPEN ..Ìo....&.....RM1993-12-28..9600 BAUD DIAL-UP MO
D004....IA2121CW4533111-22-33339743765675123989REWORK 1994-02-28OPEN ...Á%.........RM1994-03-02..REASSEMBLE PRINTER C
D004....LP4664CW4533268-73-78323898712001293402PURCHASE1994-05-08OPEN ..ßÏ@.........GD1995-12-13..100 OHM TWIN PRINT H

Step 20. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 19.
Number of rows extracted: 4

D003................CG3499AUTOBAHN ASSOCIATES EIFFESTRASSE 901 1678 DUESSELDORF 13

D003................CN0022RUSTIC DISTRIBUTION 2233 W BLUERIDGE PARKWAY MILWAUKEE WI53202
D003................CU4477KNIGHT & QUEEN CONSULTING 123 FROST AVE LONDON LU5 5TA
D003................CW4533WHITE PEAK MANUFACTURING 1208 TECHNOLOGY DR COLORADO SPRINGS CO80919 

Step 21. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows
extracted in step 19.
Number of rows extracted: 3

D005GT4444à..KL4445..ø.......á.......1993-01-15ONTIME
D005GT4444à..PST098.. .......ï.......1994-06-09ONTIME
D005IA2121...RW-098.`&...............1993-06-08WAIT 

Step 22. through ...

Step 23. steps continue until the cycle number for all relationships exceeds the specified maximum
or the preceding steps don’t extract any more additional rows for the current steps to chase
all their relationships.
Step 24. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in Step 37.
Refer to the resulting extract file and extract reports for the complete output.
Total Number of rows extracted: 161
782 File-AID/RDX Reference

Figure 444. Example 2 - DPSI=YYYY

Extract Navigation Criteria Examples 783

DPSI=YYYY, CYCLE=1, QUIESCE=Q Example 2

Similar to Previous Extract Method MOST with CYCLE=1

With the global navigation control switches set to DPSI=YYYY and all relationships CYCLE=1, this
extract example method will extract data based on PART_TABLE as the driving table for all rows
WHERE PART_NUMBER = ’AA4555’.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria Sampling Criteria
Seq Object Name Dir Par Sib Ind Status Cycle MaxRow Dep Status
---- ----------------------------------- --- --- --- --- ------- ----- ------ --- ------
0001 FRSAMP.CUSTOMER_TABLE - - - Y 1 * *
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y Y - 1 * *
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE - Y Y Y 1 * *
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE Y Y Y - 1 * *
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE Y - - Y 1 * *
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- ------------------------------------------------------------------------------------------------
D001 4 D-DSNLOCAT.FRSAMP.PART_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D002 2 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.SUPPLIER_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 3 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_TABLE

D004 6 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D005 6 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 3 D-DSNLOCAT.FRSAMP.CONTACT_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE
***** Maximum cycle count has DSNLOCAT.FRSAMP.CONTACT_TABLE
been met for this relationship ***** DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 24 TOTAL rows extracted from 6 objects *****


Step 1. Extract rows from the driving table PART_TABLE that match PART_NUMBER = ’AA4555’.

Number of rows extracted: 1

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...........EA... ......YII-232

784 File-AID/RDX Reference

Step 2. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 1.
Number of rows extracted: 2

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM

Step 3. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 1.
Number of rows extracted: 3

D005....BS1188h..AA4555..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....FA0011...AA4555.......C..í.......1994-06-09BEHIND

Step 4. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 3.
Number of rows extracted: 3

D004....BS1188CS1144612-20-4425343098264353444PURCHASE1994-11-05PRIORITY....â....â....PR1994-12-09..VDT COVERS - BLACK

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...\....\.....SD1994-12-12..DIODES

Step 5. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 4.
Number of rows extracted: 3

D003................CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648

D003................CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243
D003................CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA

Step 6. Extract rows from ORDER_TABLE which are child rows to CUSTOMER_TABLE rows extracted
in step 5.
Number of rows extracted: 3

D004....AD9797CE0021133-19-16225287322360092345WORK 1994-06-21PRIORITY...Ø..........GD1994-10-14..INSTALLATION AND ASS

D004....HY3333CS1144334-97-55553011293487520374PURCHASE1993-03-04OPEN ..íÉ....-.....ON1993-08-09..CD-ROM DRIVE
D004....IH66-CCS2280333-44-55559038729873676786CONTRACT1992-10-06OPEN ....â......... 1994-11-24..HIGH-PERFORMANCE MAG

Step 7. Extract rows from ORDER_LINE_TABLE which are child rows to ORDER_TABLE rows extracted
in steps 4 and 6.
Number of rows extracted: 3

D005....BS1188h..12-ER3.Å................1993-10-30ONTIME
D005....BT33-C...HT5550..\...............1994-06-09WAIT
D005....BT33-C...HT4320..~...............1993-06-25ONTIME

Step 8. Extract rows from PART_TABLE which are parent rows to ORDER_LINE_TABLE rows extracted
in step 7.
Number of rows extracted: 3

D001..............HT4320600’ 1/2 IN MAGNETIC TAPE1993-09-10R55-22...Ø...........EA....%.....NAA-985

D001..............HT5550HIGH DENSITY CARTRIDGE 1994-10-30TU/345... ...........EA... ......NBB-398
D001..............12-ER3X-Z MONITOR HOUSING FIX. 1994-02-27JJ4537...~...........FT... ......YII-232

Step 9. Extract rows from CONTACT_TABLE which are child rows to CUSTOMER_TABLE rows
extracted in step 5.
Extract Navigation Criteria Examples 785

Number of rows extracted: 3

D006....CE002102JIM SMITH MANAGER OF OPERATIONS CC024562 W 91 ST NEW YORK CI

D006....CS114402JOSE GARCIA MANAGER OF PURCHASING CC015660 W WILLOW SUITE 3 COLUMBUS
D006....CS228002JIMMY SMITHS ASSOCIATE BUYER CC212555 PEACHTREE ST

Total Number of rows extracted: 24

Figure 445. Example 2 - DPSI=YYYY, CYCLE=1, QUIESCE=Q

786 File-AID/RDX Reference

DPSI=YYNN Modified Example 2

Similar to Previous Extract Method DETAILED

The "Modified" extract example will extract data based on PART_TABLE as the driving table for all
rows WHERE PART_NUMBER = ’AA4555’ and this modified navigation selection:

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ----------
0001 FRSAMP.CUSTOMER_TABLE - - - Y 
FRSAMP.CONTACT_TABLE CONTCUST 
0002 FRSAMP.CUSTOMER_TABLE - Y Y - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0003 FRSAMP.ORDER_TABLE - Y N N 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0004 FRSAMP.PART_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0005 FRSAMP.PART_TABLE Y - - - 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- -------------------------------------------------------------------------------------------------
D001 1 D-DSNLOCAT.FRSAMP.PART_TABLE

D002 2 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE

D003 3 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

D004 6 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D005 3 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D006 3 D-DSNLOCAT.FRSAMP.CONTACT_TABLE
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE

***** 18 TOTAL rows extracted from 6 objects *****


For this particular example, File-AID/RDX builds 6 steps to finish the extract.

Step 1. Extract rows from the driving table PART_TABLE that match PART_NUMBER = ’AA4555’.
Number of rows extracted: 1

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...

Step 2. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 1.
Number of rows extracted: 2

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM

Step 3. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 1.
Extract Navigation Criteria Examples 787

Number of rows extracted: 3

D005....BS1188h..AA4555..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....FA0011...AA4555.......C..í.......1994-06-09BEHIND

Step 4. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 2.
Number of rows extracted: 3

D004....BS1188CS1144612-20-44253430982643534442PURCHASE1994-11-05PRIORITY....â....â....PR1994-12-09..VDT COVERS - BLACK

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...\....\.....SD1994-12-12..DIODES

Step 5. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 4.
Number of rows extracted: 3

D003................CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648

D003................CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243
D003................CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA

Step 6. Extract rows from ORDER_TABLE which are child rows to CUSTOMER_TABLE rows extracted
in step 5.
Number of rows extracted: 3

D004....AD9797CE0021133-19-16225287322360092345WORK 1994-06-21PRIORITY...ø..........GD1994-10-14..INSTALLATION AND AS

D004....HY3333CS1144334-97-55553011293487520374PURCHASE1993-03-04OPEN ..îÊ....-.....ON1993-08-09..CD-ROM DRIVE 
D004....IH66-CCS2280333-44-55559038729873676786CONTRACT1992-10-06OPEN ....æ......... 1994-11-24..HIGH-PERFORMANCE MAG

Step 7. Extract rows from CONTACT_TABLE which are child rows to CUSTOMER_TABLE rows
extracted in step 5.
Number of rows extracted: 3

D006....CE002102JIM SMITH MANAGER OF OPERATIONS CC024562 W 91 ST NEW YORK CI

D006....CS114402JOSE GARCIA MANAGER OF PURCHASING CC015660 W WILLOW SUITE 3 COLUMBUS
D006....CS228002JIMMY SMITHS ASSOCIATE BUYER CC212555 PEACHTREE ST

Total Number of rows extracted: 18

788 File-AID/RDX Reference

Figure 446. Example 2 - DPSI=YYNN Modified

Extract Navigation Criteria Examples 789

DPSI=PYNN Direct Plus Example 2

This extract navigation rule is: "Extract all of the direct relationships of the driving object, i.e. all of its
parents and first level dependents only. Direct "Plus" means resolve all objects’ parents until there are no
more parents to return." Direct Plus must be set in your profile (see Direct on page 58). In this method,
as in all methods, the extract of the driving table will be based on the specified selection criteria and
all limits will be respected.

The Direct "Plus" extract example will extract data based on PART_TABLE as the driving table for all
rows WHERE PART_NUMBER = ’AA4555’. The users cannot set any other navigation settings during
the extract specification.

Navigation Setting
SSID: DSN Location: DSNLOCAT Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ----------
0001 FRSAMP.CUSTOMER_TABLE - Y N - 
FRSAMP.ORDER_TABLE CUSTOMER TO ORDERTABLE 
0002 FRSAMP.ORDER_TABLE - Y N - 
FRSAMP.ORDER_LINE_TABLE ORDLORD 
0003 FRSAMP.PART_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0004 FRSAMP.PART_TABLE Y - - - 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- -------------------------------------------------------------------------------------------------
D001 1 D-DSNLOCAT.FRSAMP.PART_TABLE 

*** Selection Criteria Applied *** 

D002 3 D-DSNLOCAT.FRSAMP.ORDER_TABLE 
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D003 3 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE 
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D004 2 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE 
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE 

D005 3 D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE 


***** 12 TOTAL rows extracted from 5 objects ***** 

For this particular example, File-AID/RDX builds 5 steps to finish the extract.

Step 1. Extract rows from the driving table PART_TABLE that match PART_NUMBER = ’AA4555’.
Number of rows extracted: 1

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 1.
Number of rows extracted: 3

D005....BS1188h..AA4555..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....FA0011...AA4555.......C..í.......1994-06-09BEHIND

Step 3. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 1.
790 File-AID/RDX Reference

Number of rows extracted: 2

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM

Step 4. Extract rows from ORDER_TABLE which are parent rows to ORDER_LINE_TABLE rows
extracted in step 2.
Number of rows extracted: 3

D004....BS1188CS1144612-20-44253430982643534442PURCHASE1994-11-05PRIORITY....â....â....PR1994-12-09..VDT COVERS - BLACK

D004....BT33-CCS2280262-49-12445529778934287434CONTRACT1993-05-15OPEN ...&....&..... 1993-08-28..RCA-BNC ADAPTERS
D004....FA0011CE0021298-64-91894749999999999999PURCHASE1994-11-15OPEN ...\....\.....SD1994-12-12..DIODES

Step 5. Extract rows from CUSTOMER_TABLE which are parent rows to ORDER_TABLE rows
extracted in step 4.
Number of rows extracted: 3

D003................CE0021BOSS-DOS COMPUTING 34467 N HAMPTON TRENTON NJ08648

D003................CS1144UNITED TEXAS COMPUTING 1345 E BELTLINE DALLAS TX75243
D003................CS2280SOUTHERN SYSTEMS 2334 S PEACHTREE ST ATLANTA GA

Total Number of rows extracted: 12

Figure 447. Example 2 - DPSI=PYNN Direct Plus

Extract Navigation Criteria Examples 791

DPSI=CNNN All Children Only Example 2

This extract navigation rule is: "Extract the dependents of the driving object and all of their dependents
only. This option ignores all other Navigational Criteria Options." All Children Only must be set in your
profile (see Direct on page 58). Using the C method to extract data and only its dependent data can
lead to extracted data that is not loadable because of referential integrity issues due to the omitted
related parent data. This can be useful for extracting specific data that is then used for a purge
procedure.

In this method, as in all methods, the extract of the driving table will be based on the specified
selection criteria and all limits will be respected. The users cannot set any other navigation settings.

With the global navigation control switches locked to "All Children Only", this extract example will
extract data based on PART_TABLE as the driving table for all rows WHERE PART_NUMBER =
’AA4555’.

Navigation Setting

SSID: DSN Location: DSNLOCAT Navigation Criteria 

Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.PART_TABLE Y - - - 
FRSAMP.ORDER_LINE_TABLE ORDLPRT 
0002 FRSAMP.PART_TABLE Y - - - 
FRSAMP.SUPPLIER_TABLE SUPPPART 

Extract Summary

ID Rows Extracted Objects and Relationships 

---- ---------- -------------------------------------------------------------------------------------------------
D001 1 D-DSNLOCAT.FRSAMP.PART_TABLE

*** Selection Criteria Applied *** 

D002 3 D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE 
3 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

D003 2 D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE 
2 Rows from relationship Parent: D-DSNLOCAT.FRSAMP.PART_TABLE 
Dependent: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE 


***** 6 TOTAL rows extracted from 3 objects *****

As File-AID/RDX only extracts children, the extract stops after two relationships as
ORDER_LINE_TABLE and SUPPLIER_TABLE have no dependent relationships of there own.

For this particular example, File-AID/RDX builds 3 steps to finish the extract.

Step 1. Extract rows from the driving table PART_TABLE that match PART_NUMBER = ’AA4555’.

Number of rows extracted: 1

D001..............AA4555PRINTER DISPLAY PANEL 1993-12-31UT1245...~...

Step 2. Extract rows from ORDER_LINE_TABLE which are child rows to PART_TABLE rows extracted
in step 1.
Number of rows extracted: 3

D005....BS1188h..AA4555..................1993-06-09ONTIME
D005....BT33-C...AA4555.......á..........1993-03-09AHEAD
D005....FA0011...AA4555.......C..í.......1994-06-09BEHIND
792 File-AID/RDX Reference

Step 3. Extract rows from SUPPLIER_TABLE which are child rows to PART_TABLE rows extracted in
step 1.
Number of rows extracted: 2

D002..............AA4555S001AA SUPPLY COMPANY ...\....-.Y.*MM

D002..............AA4555S002SMITH SUPPLY COMPANY ...\. Y.*MM

Total Number of rows extracted: 6

Figure 448. Example 1 - DPSI=CNNN (All Children Only)

 793

Glossary
Overview
This glossary contains definitions of terms
particular to File-AID/RDX, this document, or
B
subject matter related to File-AID/RDX.
batch. Processing in which jobs are grouped
together (batched). The jobs are executed sequen-
A tially, and each job must be processed to comple-
tion before the following job can begin execution.

alias. An alternate name for a Db2 table or view BLOB (binary large object). A sequence of
requiring SYSADM or SYSCRTL authority or the binary data, up to 2 GB - 1, without an associated
CREATE ALIAS privilege to define it. An alias can CCSID.
be defined on the name of a table or view that is
not on the current server. The table or view need
not be defined when the alias is defined. Dropping C
a table or view has no effect on its aliases. An alias
can be used by any authorization ID. An alias
defined at one Db2 subsystem cannot be used at catalog. Db2-maintained tables that contain
another Db2 subsystem. descriptions of all Db2 objects.

application relationship (AR). A relationship chase key. Field (or combination of fields) that
created by the user or an application. Application File-AID/RDX uses to 'chase' or retrieve records
relationships are not recognized by Db2. Applica- from the dependent or parent object. The key is
tion relationships can be defined between Db2, composed from the related field(s) between the
MVS, and IMS objects. parent and child.

associated relationships. In Option 1, Relation- CLOB (character large object). A sequence of

ships, the set of relationships that is related to the single-byte characters or a mixture of single and
specified object as either parent or dependent; or double-byte characters up to 2 GB - 1.
related to an object that is related to the specified
object as either parent or dependent. clustering index. An index that determines how
rows are physically ordered in a tablespace.
In Option 2, Extract, the set of relationships that
includes objects that are either RI parents or RI column. The vertical component of a Db2 table.
parents of RI parents of the driving object or A column has a name and a particular data type,
dependents of the driving object or RI parents or for example, decimal or integer.
dependents of those dependents.
conditional application relationship (AR-C).
associated criteria (rule). Associated disguise cri-
teria are always defined on a single unrelated field An application relationship with one or more
and can be applied to fields in different objects; conditional tests on the parent object; at extract
identification of the additional data locations is a execution time, the condition on the parent object
manual process. will be evaluated and the defined relationship will
be navigated only when the condition is true.
authorization ID. An identifier that has an asso-
ciated set of privileges. This identifier can also be creator. The authorization ID of the owner of a
verified for connection to Db2. table.

auxiliary table. A Db2 table that stores columns

outside the table in which they are defined, for D
example LOBs.

database. A set of tablespaces and index spaces.

794 File-AID/RDX Reference

database administrator. An individual who

designs, implements, and maintains an opera-
E
tional database.
extract criteria. Former name of extract request.
data disguise. A process that replaces the value of See extract request.
data fields with data of the same type to protect
sensitive data. For example, a female employee extract file. The file created by the Extract func-
name field in production can be replaced by a tion. This file contains object data, object infor-
recognizable fictitious female name or a nonsensi- mation, and relationship information about the
cal set of characters for testing. extracted objects. This file is used as the input for
the Load function.
DBCLOB (double-byte character large object).
A sequence of double-byte characters up to 2 GB - extract from image copy. Extract related data
1. from the most recent, full Db2 Image Copy data-
sets for the applicable tablespace(s) as opposed to
Db2 catalog. A set of tables maintained by Db2 extracting directly from Db2 tables or views.
that contain descriptions of objects such as tables,
views, and indexes. extract request. A set of rules used to limit the
scope of the Extract function. Extract request con-
dependent table. In a referential integrity rela- sists of relationship and selection criteria.
tionship, the dependent table contains the foreign
key. In an application relationship, the dependent
table contains a column (or columns), which are F
analogous to a foreign key. Application relation-
ships are created and maintained by user applica-
tions, not by Db2. field. The vertical component of an MVS file. A
field is defined in its associated record layout file
direct descendant. In an extract, any object that and has a name and a particular data type, for
is reached by navigating downward from the driv- example, decimal or integer.
ing object is a direct descendant so any relation-
ship on this downward navigation has a valid file. Collection of data treated as a unit that is the
direct descendant path. Only the rows initially primary unit of access and storage.
selected from the driving object will be sent down
this path so the direct descendant path will be file name. Term or phrase used to identify a file
navigated only once. (same as dataset).

disguise control file (DCF). The Disguise Control foreign key. A key that is specified in the defini-
File contains sets of disguise rules for specific tion of a referential constraint.
objects and determines which File-AID/Data Solu-
tions disguise criteria is applied to which object
when disguising the data of an extract file.
I
disguise criteria file. The disguise criteria file IAM. Innovation access method.
contains the sets of File-AID/Data Solutions
change criteria for the objects to be disguised. indirect descendant. The indirect descendant
path includes two different situations. First, it is
distinct type. A user-defined data type that is the downward navigation from any object reached
defined from an existing built-in type (base type). in an upward direction. Second, it is downward
navigation from the driving object and it's direct
DPSI. Short for the four navigation flags Direct descendents for all rows other than the original
descendant, Parent, Indirect descendant and Sib- selection from the driving object.
ling. See also navigation path.
Innovation Access Method (IAM). Key-indexed
driving object. The MVS file or Db2 table file access method, by Innovation Data Processing,
selected to be the starting point of the extract pro- Inc., intended primarily for use as a transparent
cess. alternative to VSAM.
 795

K between the parent object and dependent object

in an application relationship.

KEY relationship (AR). An application relation- parent path. In an extract, any object that is on
ship (AR) between a Db2 table or MVS file (parent) the upward navigation from a selected object has a
and an Output Key File (dependent) created by the valid parent path. This does not mean that every
user or an application. Also used to create a rela- relationship has a valid parent path; navigation
tionship to an IMS database. These AR relation- has to be possible in an upward direction for the
ships are not recognized by Db2. parent path to be valid.

primary index. A unique index that is part of the

L definition of a Db2 table. The values defined in a
parent table’s primary index match the foreign
keys defined in the corresponding dependent
LOB (large object). A sequence of bytes repre- table.
senting bit data, single-byte characters, double-
byte characters, or a mixture of single and double- primary key. A unique key that is part of the
byte characters. A LOB can be up to 2GB -1 byte in definition of a Db2 table.
length. See also BLOB, CLOB, and DBCLOB.

location. A name for a particular Db2 subsystem R

in a network of subsystems.

locking. The process by which integrity of data is record layout file. The record layout file is a file
ensured. Locking prevents concurrent users from containing source code record layouts. A record
accessing inconsistent data. layout file can be a sequential, partitioned, CA
Panvalet, or CA Librarian file. A record layout can
be a separate file or member.
M
referential constraint. The requirement that
nonnull values of a designated foreign key are
member. One partition of a partitioned file. valid only if they equal values of the primary key
of a designated Db2 table.
MVS. Multiple Virtual Storage. An IBM operating
system that manages multiple virtual address referential integrity (RI) relationship. A rela-
spaces in IBM processors. tionship required by Db2 rules. Information about
referential integrity relationships is gathered by
File-AID/RDX at installation time to create a rela-
N tionship file.

navigation path. In an extract, each relation- related criteria (rule). Related disguise criteria is
ship will have four navigation flags associated defined once for a field and then propagated to
with it; direct descendant, parent, indirect descen- related fields in other objects.
dant and sibling. How the object is related to the
driving object will determine which navigation relationship. A defined connection between the
paths are valid for each relationship. records of one or two objects. The objects can be
Db2 tables and/or MVS files. A Db2 relationship is
the internal representation of a Db2 referential
P constraint.

relationship file. A file that contains informa-

parent object. In a Db2 referential integrity rela- tion about RI and application relationships. File-
tionship, the parent object’s primary index con- AID/RDX builds the first relationship file at instal-
tains values that match the foreign keys defined in lation time. Information about the relationships
the corresponding dependent table. In an applica- in a Db2 subsystem is gathered from the Db2 cata-
tion relationship, the parent object references the log table, SYSRELS. The user can use Option 1,
Db2 column(s) or MVS field(s), which is analogous Relationships, to browse and modify the relation-
to a Db2 foreign key, that match the Db2 col- ship file. In addition, File-AID/RDX enables the
umn(s) or MVS field(s) located in the correspond- user to add application relationships (AR) to the
ing dependent object (Db2 table or MVS file). The relationship file.
user must create the column relationship(s)
796 File-AID/RDX Reference

relationship criteria. A set of rules you specify to

control which relationships contained in the rela-
T
tionship file are extracted. Relationship criteria
and selection criteria comprise extract criteria. table. A named Db2 data object consisting of a
specific number of columns and some number of
unordered rows.
S
target subsystem. The Db2 subsystem to which
you want to load extracted Db2 data.
sampling. Object sampling is intended to extract
a sample of rows from an object. The selection
target object. An MVS file or Db2 table to which
processing for sampling is based strictly on count-
data is loaded.
ing and not on the contents of the row, as is the
case with selection criteria. Sampling criteria may
timestamp. A value consisting of a date and time
not extract the same rows each time it is executed.
expressed in years, months, days, hours, minutes,
There are three different kinds of sampling: cycle,
seconds, and microseconds.
maxrow and n th.
trigger. A set of SQL instructions to be performed
selection criteria. A set of rules used to control
on table(s) when the trigger is activated. A trigger
which rows from the driving object are extracted.
package is created with a CREATE TRIGGER state-
Selection criteria also enables the user to control
ment.
how many rows from dependent objects are
extracted. Selection Criteria and relationship crite-
ria comprise extract criteria. U
sequential file (SEQ). A file with sequential orga-
nization. UDT (User-defined Data Type). See distinct
type.
sequential organization. The permanent logical
file structure in which a record is identified by a unrelated criteria (rule). Unrelated disguise cri-
predecessor-successor relationship established teria applies to a single object and must be defined
when the record is placed into the file. for any field in the object that is to be disguised.
Unrelated criteria always applies to a single object
sibling path. In an extract, parent paths are and cannot be shared.
always paired with sibling paths. Whenever a row
is sent up the parent path it is possible to come
back down the same relationship to get the sibling V
rows.

source object. An MVS file or Db2 table from view. An alternative representation of data from
which data is extracted. one or more Db2 tables. A view can include all or
some of the columns contained in the table or
synonym. An alternate name for a Db2 table or tables on which it is defined.
view requiring no authorization to define it. A
synonym can only be defined on the name of an VSAM (Virtual Storage Access Method). A high-
existing view or table at the current server. Drop- performance mass storage access method. File-
ping a table or view drops its synonyms. A syn- AID/RDX supports two types of data organization:
onym can only be used by the authorization ID entry sequenced datasets (ESDS) and key
that created it. sequenced datasets (KSDS).

subscript. An occurrence number represented by

either an integer, a data-name optionally followed
W
by an integer with the operator + or -, or an index-
name optionally followed by an integer with the WHERE clause. A clause within an SQL state-
operator + or -, which identifies a particular ele- ment that restricts rows that participate in the
ment in a table. answer set.
 797

X
XREF. Record layout cross reference. XREFs
describe how record layouts are to be associated
with individual file records or record segments. If
a file has more than one record type and requires
more than a single record layout to describe it,
you can use an XREF to establish application rela-
tionships.
798 File-AID/RDX Reference