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

[Link]

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 - [Link] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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, [Link] 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
[Link] 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 [Link]
• 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, [Link] 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
[Link]

Visit Compuware on the web at [Link] 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: [Link] 
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: [Link] 
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: [Link].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
--- ---------------------------------------------- ---- ----- -----------------
_ [Link].CUSTOMER_TABLE DB2 AR
[Link].ORDER_TABLE DB2
_ [Link].ORDER_TABLE DB2 RI
[Link].ORDER_LINE_TABLE DB2 ORDLORD
_ [Link].CUSTOMER_TABLE DB2 RI ASSOCIATED REL.
[Link].CONTACT_TABLE DB2 CONTCUST
_ [Link].PART_TABLE DB2 RI ASSOCIATED REL.
[Link].ORDER_LINE_TABLE DB2 ORDLPRT
_ [Link].PART_TABLE DB2 RI ASSOCIATED REL.
[Link].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 - [Link] 
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: [Link].ORDER_TABLE Type: DB2 



Dependent Name: [Link].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 [Link] 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 [Link].
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
[Link].
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-
[Link]
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-
[Link]
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, [Link]
to [Link]. 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:

[Link]

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: [Link] 
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 : [Link]

_ 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 [Link], 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 [Link].

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 . .: [Link] 

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 [Link]

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 . .: [Link] 


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 . .: [Link] 


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,
[Link].

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,
[Link].

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. [Link] becomes [Link].

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
[Link] 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:

[Link]

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:

[Link]

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
[Link]. 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, [Link], 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. [Link](0) to [Link](0)
2. [Link](0) to [Link](-1)
3. [Link](0) to [Link](-2)

When specifying the GDG base in a relationship, for example [Link], 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 ===> [Link] 

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 - [Link]

4
DB2 Object List

5
Table List - [Link]

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 [Link] 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 
--- -------------------------------------- ------ ---- 
[Link].CONTACT_TABLE RI DSN es 
[Link].CUSTOMER_TABLE AR/RI DSN 
[Link].ORDER_LINE_TABLE RI DSN 
[Link].ORDER_TABLE AR/RI DSN 
S [Link].PART_TABLE AR/RI DSN 
[Link].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 - [Link]

The Table List - [Link] 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 - [Link]

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

O Table List - [Link] ===> 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 
--- -------------------------------------- ------ ---- 
[Link].CONTACT_TABLE RI DSN es 
[Link].CONTACT_VIEW CATLG DSN 
[Link].CUSTOMER_TABLE AR/RI DSN 
[Link].CUSTOMER_VIEW CATLG DSN 
S [Link].ORDER_LINE_TABLE RI DSN 
[Link].ORDER_LINE_VIEW Catlg DSN ction list) 
[Link].ORDER_TABLE AR/RI DSN ction list) 
[Link].ORDER_VIEW CATLG DSN ction list) 
[Link].PART_TABLE AR/RI DSN ction list) 
[Link].PART_VIEW CATLG DSN 
S [Link].SUPPLIER_TABLE AR/RI DSN 
[Link].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 - [Link] 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 [Link] 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 ===> '[Link].*' 
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 ===> [Link] 
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 
--- ------------------------------------------------------ 
[Link] 
[Link] 
[Link] 
[Link] 
[Link] 
[Link] 
******************************* 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 
--- ------------------------------------------------------ 
_ [Link] 
_ [Link] 
_ [Link] 
S _ [Link] 
_ [Link] 
_ [Link] 
********************** 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: '[Link]' 

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
'[Link]' MVS Order to Sales H
_ '[Link]' MVS AR
'[Link]' MVS Sales History to
_ '[Link]' MVS AR
'[Link]' 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-'[Link]' 
| 
|__ DB2-CUSTOMER_TABLE 
| 
|__ MVS-'[Link]' 
| 
|__ DB2-CONTACT_TABLE 
| 
|__ MVS-'[Link]' 
| 
|__ MVS-'[Link]' 
| 
|__ 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-'[Link]. 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.
[Link]' 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-
'[Link]' 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-
'[Link]' is a parent of DB2-CUSTOMER_TABLE. DB2-
CUSTOMER_TABLE itself is a parent of MVS-'[Link]' 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-'[Link]' 
| 
|__ DB2-CUSTOMER_TABLE 
Option List for: MVS-'[Link]' 
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-'[Link]' 
***************************** 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: '[Link]' Type: MVS 
Layout Dataset: ‘[Link]’ 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: '[Link]' Type: MVS 
Layout Dataset: [Link] Mbr: EMPLOYEE 
XREF Dataset: Mbr: 
01 Level Name: EMPLOYEE-MASTER-FILE 
Dependent Name: '[Link]' Type: MVS 
Layout Dataset: [Link] 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, [Link] (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 ===> [Link] 

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: [Link].ORDER_TABLE

Obj Rel 
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ [Link].ORDER_TABLE DB2 RI Not in Dataset
[Link].ORDER_LINE_TABLE DB2 
_ [Link].PART_TABLE DB2 RI Not in Dataset
[Link].ORDER_LINE_TABLE DB2 
_ [Link].PART_TABLE DB2 RI Not in Dataset
[Link].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: [Link].ORDER_TABLE

Obj Rel 
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ [Link].ORDER_TABLE DB2 RI Not in Dataset
[Link].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: [Link].ORDER_TABLE

Obj Rel 
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ [Link].ORDER_TABLE DB2 RI Not in Dataset
[Link].ORDER_LINE_TABLE DB2 
_ [Link].CUSTOMER_TABLE DB2 RI Not in Dataset
[Link].CONTACT_TABLE DB2 
_ [Link].PART_TABLE DB2 RI Not in Dataset
[Link].ORDER_LINE_TABLE DB2 
_ [Link].PART_TABLE DB2 RI Not in Dataset
[Link].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: [Link].ORDER_TABLE

Obj Rel 
CMD Parent/Dependent Type Type Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.$[Link] DB2 RI Not in Dataset 
LOCATION.$[Link] DB2 
_ LOCATION.$[Link] DB2 RI Not in Dataset 
LOCATION.$[Link] DB2 
_ LOCATION.$[Link] DB2 RI Not in Dataset 
LOCATION.$[Link] DB2 
_ LOCATION.$[Link] DB2 RI Not in Dataset 
LOCATION.$[Link] DB2 
_ LOCATION.$[Link] DB2 RI Not in Dataset 
LOCATION.$[Link] DB2 
_ LOCATION.$[Link] DB2 RI Not in Dataset 
LOCATION.$[Link] DB2 
_ LOCATION.$[Link] DB2 RI Not in Dataset 
LOCATION.$[Link] 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 [Link].

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
[Link].
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: [Link] Type: DB2 



Dependent Name: [Link] 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 [Link].

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 [Link].

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, [Link] (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: [Link] 

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
--- ---------------------------------------------- ---- ----- -----------------
_ [Link] DB2 AR 
[Link] 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 ===> [Link]



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: [Link]
Dependent: [Link]
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: [Link] 
Dependent: [Link]
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: [Link].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 
[Link].

Dependent
Displays the full name of the dependent object preceded by the object type. For example,

– Db2 tables are identified in the form

[Link].

– MVS files are identified in the form

[Link](member).

– IMS root segments are identified in the form

[Link] library dataset(member).

– IMS segment layouts are identified in the form

[Link] layout dataset(member).

– Output Key File layouts are identified in the form

[Link] 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, [Link].

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 [Link]. 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 [Link]±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 ±[Link], 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: [Link]
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: [Link]
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: [Link].CUSTOMER_TABLE
Dependent: [Link].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: [Link].CUSTOMER_TABLE
Dependent: [Link](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: [Link].CUSTOMER_TABLE
Dependent: [Link](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: [Link].ORDER_TABLE
Dependent: [Link]
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 : [Link] 
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 : [Link] 
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: [Link]
Dependent: [Link]
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 ===> '[Link]'
Data Component LLQ ===> DATA 
Index Component LLQ ===> INDEX 
Data component . . : '[Link]' 
Index component . .: '[Link]' 

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 ===> '[Link]' 

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=[Link],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 ===> [Link]

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=[Link]
000010 // DD DISP=SHR,DSN=[Link]
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. . : '[Link]' TIME [Link]

Type Parent to Dependent Relationships 
---- ------------------------------------------------------------------------------------------------------------------------------
Parent. . .: [Link] 
RI Dependent: [Link] 
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: [Link](PORDR) 
RELNAME: CUSTOMER-ORDER RELATION KEY 
Columns: Parent = DEPTNO___A_________B________30 CHAR(1,3) Dependent = ORDR01 CHAR(1,3) 

Parent. . .: [Link].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: [Link].CUSTOMER_TABLE 
RELNAME: CONDITIONAL AR 
Columns: Parent = CUSTOMER_NUMBER CHAR(6) Dependent = CUSTOMER_NUMBER CHAR(6)

Parent. . .: [Link].CUSTOMER_TABLE 
RI Dependent: [Link].CONTACT_TABLE 
RELNAME: CONTCUST 
Columns: Parent = CUSTOMER_NUMBER CHAR(6) Dependent = CUSTOMER_NUMBER CHAR(6) 

AR Dependent: [Link].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. . : '[Link]' TIME [Link]

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 .: [Link].CONTACT_TABLE 
RI Parent: [Link].CUSTOMER_TABLE 

Dependent .: [Link].ORDER_LINE_TABLE 
RI Parent: [Link].ORDER_TABLE 

Dependent .: [Link].ORDER_LINE_TABLE 
RI Parent: [Link].PART_TABLE 

Dependent .: [Link].ORDER_TABLE 
AR Parent: [Link].CUSTOMER_TABLE 

Dependent .: [Link].ORDER_TABLE 
AR Parent: [Link].ORDER_TABLE 

Dependent .: [Link].SUPPLIER_TABLE 
RI Parent: [Link].PART_TABLE 

Dependent .: [Link](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 .: [Link] 
AR Parent: [Link] 

Dependent .: [Link] 
AR Parent: [Link] 

Dependent .: [Link] 
AR Parent: [Link].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 [Link]
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
[Link] [Link] [Link]
[Link] [Link] [Link]

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 [Link] 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 [Link] 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 _ [Link] DVLP 
S [Link] PROD 
_ [Link] TEST 
********************** Bottom of data *********************** 


3. specify the [Link] to [Link] 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: [Link] 
SSID: ACPT Location: LOCATION Navigation Criteria 
Seq Object Name Dir Par Sib Ind Status 
---- ---------------------------------------------- --- --- --- --- ---------- 
X001 [Link] Y - - - 
[Link] CONTCUST 
0002 [Link] Y - - - 
[Link] Customer to Order AR 
X003 [Link] Y - - - 
A.ORDER_LINE ORDLORD 
X004 [Link] - Y N - 
A.ORDER_LINE ORDLPRT 
X005 [Link] - - - N 
[Link] 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
‘[Link](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 ===> [Link] 
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 ===> '[Link]' 

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,
[Link].

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 ===> [Link] 

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 ===> [Link] 
Edit Data Privacy Spec ===> (Y = Yes; N = No) *DCF*

Relationship information stored in: 
File Name ===> [Link] 

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
(‘[Link]’) 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 [Link] E 11/01/03
_ SAMPMIN [Link] E 01/02/18
_ DIEBLDX [Link].DB2VSAM E 01/02/04
_ [Link] EL L 01/02/01
_ DIEBLD1 [Link] E 01/01/31
_ DIEBLD [Link].NODB2(EXTCUST) EL L 00/12/24
_ MVORDR [Link] 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 . : [Link] 
Member Name . . . . : MVSSAMP 
Request Type . . . . : EXTRACT 
Description . . . . : MVS 
Reference Date . . . : 2011/01/03 Reference Time: [Link] 

Driving Object Information: 
SSID . . . . . . . . : 
Name . . . . . . . . : MVS - [Link] 

Extract Information: 
Extract File Name . : [Link] 
Summary File Name . : [Link] 
Disguise Control File: 
Repository Name: 
Project Name: 
Extract Date . . . . : 2011/01/03 Extract Time : [Link] 

Relationship Information: 
File Name . . . . . : [Link] 

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 [Link] E 11/01/03
Description: MVS 
_ SAMPMIN [Link] E 04/02/18
Description: This extract uses Acct number 
_ DIEBLDX [Link].DB2VSAM E 04/02/04
Description: DB2-FR.PRODUCT_CONTRACT 
_ [Link] EL L 04/02/01
Description: This extract selects region 10 
_ DIEBLD1 [Link] E 04/01/31
Description: [Link] 
_ MVORDR [Link] E 99/08/24
Description: [Link] 
******************************* 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 [Link] E 11/01/03
_ SAMPMIN [Link] E 04/02/18
_ DIEBLDX [Link].DB2VSAM E 04/02/04
_ [Link] EL L 04/02/01
_ DIEBLD1 [Link] E 04/01/31
_ DIEBLD [Link].NODB2(EXTCUST) EL L 03/12/24
_ MVORDR [Link] 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 ===> [Link] 

Member Description Changed
-------- -------------------------------------------------- ---------- 
_ DB2VSAM db2 to vsam extract 2004/06/01
_ MCUST0DB MVS - [Link] 2004/08/13 
_ MIKE1 Member List 2004/05/10 
_ NODB2 mcust with db2 deleted 2004/01/25 
_ ORDER DB2 - [Link] 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 ....: ‘[Link]’ 

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 ....: ‘[Link]’ 

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 - [Link] 2001/08/13 
_ MIKE1 Member List 2002/05/10 
_ NODB2 mcust with db2 deleted 2001/01/25 
_ ORDER DB2 - [Link] 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 ===> '[Link]' 

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,
[Link].

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 _ [Link] DSNG 
_ [Link] DSN 
_ [Link] DSN 
_ [Link] DSN 
_ [Link] DSN 
_ [Link] 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 
--------------------------------------------- ------------------------------ 
_ [Link] EXTRACT FILE NAME 
_ [Link].EXTCRIT2 REQUEST FILE NAME 
_ [Link] RELATIONSHIP FILE NAME 
_ [Link] PROFILE FILE NAME 
_ [Link] DISGUISE CONTROL FILE NAME 
_ FRSAMP.ORDER_TABLE DB2 TABLE NAME 
_ FRSAMP.CUSTOMER_TABLE DB2 TABLE NAME 
_ FRSAMP.CONTACT_TABLE DB2 TABLE NAME 
_ [Link] FILE OBJECT NAME 
_ [Link](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 
---------------------------------------------------------------------------- 
_ [Link] 
[Link] 
_ [Link].EXTCRIT2 
[Link].EXTCRIT2 
_ [Link] 
[Link] 
_ [Link] 
[Link] 
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 
--------------------------------------------- ------------------------------ 
_ [Link] EXTRACT FILE NAME 
_ [Link].EXTCRIT2 REQUEST FILE NAME 
_ [Link] RELATIONSHIP FILE NAME 
_ [Link] PROFILE FILE NAME 
_ [Link] DISGUISE CONTROL FILE NAME 
_ FRSAMP.ORDER_TABLE DB2 TABLE NAME 
_ FRSAMP.CUSTOMER_TABLE DB2 TABLE NAME 
_ FRSAMP.CONTACT_TABLE DB2 TABLE NAME 
_ [Link] FILE OBJECT NAME 
_ [Link](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 . . . .: '[Link]' 
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 ===> '[Link]' 

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: 
'[Link]' 
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 ===> '[Link]' 

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 -------------- 
[Link] NON-VSAM MIGRAT 
[Link] NON-VSAM MIGRAT 
[Link] NON-VSAM MIGRAT 
S [Link] CLUSTER PRD981 
[Link] CLUSTER PRD908 
[Link] 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: [Link] 







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 - [Link] ------------ 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 [Link] 
_ 8 Data Privacy DISGUISED DCF: [Link]
_ 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: [Link]

_ 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 ===> '[Link]' 

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 ===> [Link]

Optional File Information: 
Record layout usage ===> S 
Record layout file ===> [Link] 
Member name ===> ORDERTAB 
XREF file name ===> 
Member name ===> 

Specify Relationship Information:
File name ===> '[Link]'

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: [Link] 

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 spec