File-AID/RDX Reference

File-AID/RDX Reference
File-AID/Related Data XPERT
Reference
Release 16.03
ii
File-AID/RDX Reference
Please direct questions about File-AID/RDX
or comments on this document to:
Compuware Customer Support
http://go.compuware.com/
This document and the product referenced in it are subject to the following legends:
Copyright 1994-2015 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, FrontLine, Compuware,
Compuware Workbench, and Topaz Workbench are trademarks or registered trademarks of Compuware
Corporation.
IBM, DB2 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. JAN2016
December 18, 2015.
iii
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
How This Manual is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Notation Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv
Reading the Syntax Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii
Compuware Go Customer Support Website . . . . . . . . . . . . . . . . . . . . . . . . . xxviii
Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii
Phone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxviii
Web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxviii
Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxviii
Corporate Website . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxviii
Chapter 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Product Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Invoking File-AID/RDX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
File-AID/RDX Primary Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Option 0—Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Option 1—Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Option 2—Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Option 3—Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Option 4—Delete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Option 5—Data Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Option 6—Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Option G—Global Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Option FD—FADB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Option C—Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Option T—Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Option X—Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Screen Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Pattern Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Escape Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Double-Byte Character Set (DBCS) Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Table Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Column Name Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Types of Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Option Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Option Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Scrollable Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Pop-Up Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Scrollable Fields for DB2 Long Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Long Name Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
Using the LEFT and RIGHT Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
Using the EXPAND Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
Command Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Assign PF Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Concatenate Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Stacking Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
ISPF/PDF JUMP Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
iv
File-AID/RDX Reference
Terminal Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Program Access (PA) Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Program Function (PF) Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Terminal Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
DB2 Subsystem ID Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
DB2 Call Attach Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
File-AID/RDX Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Relationship File Compatibility Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16
Relationship File characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-16
Relationship File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17
Creating and Loading the Relationship File. . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Using the Relationship File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Reviewing Relationships in the File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-21
Using Relationship Definitions from Another DB2 Subsystem . . . . . . . . . . . . . .1-21
Conditional AR Criteria File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Extract/Load/Delete Request File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Dynamic Reallocation of Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-23
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-24
1-24
1-24
1-25
1-25
1-25
1-26
1-26
1-26
Option FD—Transfer to File-AID for DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Chapter 2. Profiles and Global Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Option 0—Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Select Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Editing the Profile Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-1
2-1
2-2
2-5
Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Locking a Profile Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Session and Batch Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Extract Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Load Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Disguise Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Privacy Repository List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-19
Privacy Project List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20
Permanent File Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Temporary File Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Option G—Global User Defaults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26
Chapter 3. Relationship Facilitator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Relationship File Compatibility Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Relationship File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
DB2 Referential Integrity (RI) Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Application Relationships (AR). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Conditional (“Data Driven”) Application Relationships (AR-C) . . . . . . . . . . . 3-2
Considerations for MVS Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Use of DB2 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
DB2 Relationship Facilitator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
DB2 Object List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Table List in Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Table List - SYSIBM.SYSTABLES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
MVS Relationship Facilitator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
v
MVS Object List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Object List in Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Relationship Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Graphical Relationship Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Understanding the Graphical Relationship Display . . . . . . . . . . . . . . . . . . . . . . .3-17
Option List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19
Relationship Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
DB2 RI Update Online Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
RI Relationship Detail Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
RI Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Application Relationship Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Relationship Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Add Relationships — Specify Object Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34
Add Application Relationships — DB2 to DB2 . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Add Relationships — DB2 to MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Add Relationships — DB2 to IMS and Output Key Files. . . . . . . . . . . . . . . . . 3-39
Add Relationships — MVS to DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
Add Relationships — MVS to MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44
Add Relationships — MVS to IMS and Output Key Files . . . . . . . . . . . . . . . . 3-47
Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50
Relationship Condition Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Selection Criteria Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-57
Formatted Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-61
Field Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
Primary Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-69
Building Column/Field Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Extended Column Relationship Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
Rules for DECIMAL/FIXPIC and CHARACTER Columns/Fields . . . . . . . . . . . 3-73
Extended Column Relationships Examples . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-74
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-75
Specify MVS Field Subscripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Allocate Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Batch RI Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Print Relationship File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Formatted Relationship Report Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Print Options Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Edit Print JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89
Relationship File - Related Objects Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89
Chapter 4. Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Determining Which Rows Will Be Extracted . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Selecting a Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2
Determining the Scope of the Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3
Using Relationship Definitions Across DB2 Subsystems. . . . . . . . . . . . . . . . . . 4-7
Cloning Extract Requests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Support for DB2 XML and LOB Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Support for DB2 Temporal Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
GDG Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Download File-AID/RDX Extract Data to the Workstation Environment . . . 4-12
Extract Driving Object - Single Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Extract - DB2 Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Use of DB2 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17
Use of Aliases and Synonyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17
Extract - MVS Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Extract Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Request File Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Extract Requests from Releases prior to Release 4.0 . . . . . . . . . . . . . . . . . . . . 4-26
DB2 Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
vi
File-AID/RDX Reference
Use of DB2 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-29
Use of Aliases and Synonyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-29
Relationship Listing Window for DB2 Objects . . . . . . . . . . . . . . . . . . . . . . . . . . .4-29
Modify Extract Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Modify Extract Request - Object Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Save Cloned Extract Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
SAVE Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36
MVS Driving Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Relationship Listing Window—No Relationships. . . . . . . . . . . . . . . . . . . . . . . . .4-39
MVS Catalog Utility File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40
PDS Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40
XREF Select Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42
Extract Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extract Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driving Object - DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Driving Object - MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Extract Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-43
4-44
4-47
4-48
4-49
SELECT FROM Temporal Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-54
Extract Scope - Object View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-56
Extract Scope - Relationship Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-63
Extract Scope - Relationship Sampling Criteria . . . . . . . . . . . . . . . . . . . . . . . . . .4-70
Extract Scope - Relationship Navigation Criteria . . . . . . . . . . . . . . . . . . . . . . . . .4-73
Graphical Relationship Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-76
Relationship Information Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-79
Check Extract Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-80
Update Saved Request Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-82
Unrelated Object Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83
Add Unrelated DB2 Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-84
Unrelated Object Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86
Modify Unrelated MVS Object Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-87
Input Key File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
Input Key File - Positional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-90
Input Key File - Delimited . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-92
Object Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
Object Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-97
SQL Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-101
MVS File Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-102
Selection Criteria Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-103
Formatted Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-107
Field Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-114
Primary Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-115
Selection Criteria Record Layout Specification . . . . . . . . . . . . . . . . . . . . . . . . .4-115
Selection Criteria for XREFs and Multiple Record Type Files . . . . . . . . . . . . . .4-115
Output Key Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-118
Output Key File Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-118
Output Key Files List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-118
Output Key File Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-119
Extract File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Privacy Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supporting File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Continue With Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save Extract Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-124
4-127
4-129
4-131
4-132
SAVE Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-133
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-134
Override Data Privacy Environment Parameters . . . . . . . . . . . . . . . . . . . . . . . .4-134
Override Execution Parameter in a Data Privacy Project . . . . . . . . . . . . . . . . . .4-135
Multiple Origins for a Data Privacy Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-137
Special Instructions for Oracle Translate Table . . . . . . . . . . . . . . . . . . . . . . . . .4-138
Redirect File-AID/Data Solutions Report (Data Disguise with DCF only) . . . . .4-138
Control Card Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-138
View REXX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-139
vii
Submit JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-139
Execute Rexx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-139
Interactive Extract Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-140
Interactive Extract Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-140
Miscellaneous Extract Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-142
Extract JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-142
DD statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-143
EXTPARMS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-144
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-144
DB2 Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144
File-AID/RDX Extract/Load/Delete Request File . . . . . . . . . . . . . . . . . . . . . . 4-144
Obsolete Record Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-152
File-AID/RDX Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154
Product Record — 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-154
Header Record — H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-155
Base Table Record — B. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-156
Database Create Record — F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-157
Tablespace Create Record — G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-157
DB2 Source Environment Record — C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-158
MVS File Create Record — E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-158
View Create Record — V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-159
Alias Create Record — A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-159
Synonym Create Record — S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-160
Map Record — M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-160
Relationship Record — R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-161
Data Record — D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-161
XML/LOB Data Record — x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-162
Order Record — O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-162
Trailer Record — T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-163
Work files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-164
File-AID/RDX Encryption Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164
Encryption Exit Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-165
Record Layout and File-AID/MVS XREF JCL . . . . . . . . . . . . . . . . . . . . . . . . . 4-165
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-166
File-AID/RDX Record Layout File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-166
Sample COBOL Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-167
Sample PL/I Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-168
File-AID/MVS XREF File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-168
Sample XREF for Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-168
Extract Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-170
Extract Progress Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-170
Relationship Navigation and Sampling Report. . . . . . . . . . . . . . . . . . . . . . . 4-171
Relationship Navigation and Sampling Excluded Object Report . . . . . . . . . 4-172
Object Sampling and Selection Criteria Report. . . . . . . . . . . . . . . . . . . . . . . 4-173
Object Sampling and Selection Criteria Excluded Object Report . . . . . . . . . 4-175
Extract Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-176
Summary of Objects with Zero Rows Extracted . . . . . . . . . . . . . . . . . . . . . . 4-177
Create Record Layout Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-177
DB2 Index Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-178
RDX Hybrid Scan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-179
Chapter 5. Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Support for DB2 XML and LOB Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Support for DB2 Temporal Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
GDG Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Load Reference List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Request File Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Extract File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Edit JCL for Summary File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Load Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
viii
File-AID/RDX Reference
Load Object Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
SQL Insert and DB2 Load Utility Load Options . . . . . . . . . . . . . . . . . . . . . . . . . .5-15
Source to Target Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
File Mapping Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-21
Field Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23
Column Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26
Default Value Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28
Default Value Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-29
Delete Literal Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-30
Column/Field Mapping Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32
Data Type Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-32
Miscellaneous Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-33
Column Mapping Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-34
Target Environment Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
Generating CREATE DDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-44
Create/Edit DB2 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-45
Create/Edit DB2 Tablespace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-46
Tablespace Partition Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-50
Create/Edit DB2 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-52
Create/Edit DB2 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-55
Create/Edit DB2 Alias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-59
Create/Edit DB2 Synonym . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-60
Create/Edit DB2 View (Simple) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-61
Create/Edit DB2 View (Complex) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-62
Create/Edit MVS File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-64
Create/Edit VSAM CLUSTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-65
Support of IAM File Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-67
Create/Edit VSAM AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-68
Create VSAM PATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-69
Existing Data Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
Save Load Request. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
SAVE Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-76
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77
Control Card Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-77
View REXX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-77
Submit JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
Execute REXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-78
Interactive Load Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
Control Card Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-79
The Load Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80
DB2 Batch Load Utility Load Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80
DB2 LOAD Utility Load JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
CREATE Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . .5-87
LDDRV Step Parameter List and DD Statements. . . . . . . . . . . . . . . . . . . . . . . . . .5-89
Load Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-89
DELTEnnn Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . .5-91
FIXDLnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-92
SORTnnn Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-92
LOADnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-92
RPAIRnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-93
CHCKDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-94
IMAGECPY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-94
COPYnnn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-94
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-94
SQL Insert Load Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-95
SQL INSERT Load JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-96
CREATE Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . .5-99
LDDRV Step Parameter List and DD Statements. . . . . . . . . . . . . . . . . . . . . . . . .5-101
DB2 Load Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-101
DELETE Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . .5-103
ix
SORTnnn Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-104
LDSQLIN Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . .5-104
SQL Insert Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-105
MVS Load Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-106
MVS Load JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-107
VSAMALOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-110
VSAMCRTE Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-110
FILEDLTE Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-110
FILEALLC Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-110
LDDRV Step Parameter List and DD Statements. . . . . . . . . . . . . . . . . . . . . . . . .5-111
MVS Load Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-111
LDMVSIN Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . .5-114
SORTnnn Step DD Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-114
MVS Insert Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-115
Miscellaneous Load Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-116
Tablespaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-116
“Target Environment” Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116
Single-Table and Multi-Table Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116
CHECK PENDING Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-116
COPY PENDING Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-117
Restartability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-117
DB2 Load Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-117
SQL Insert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-117
Reusing the Discard File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
Use of Views in Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
DB2 Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
Privileges Required for Load Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-119
Load Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-121
SQL Insert - DB2 Authority Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-122
DB2 Load - DB2 Authority Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-122
Create DB2 Target Environment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-123
Pre-Load Summary Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-124
SQL Insert: DB2 Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-125
MVS Load - MVS Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-126
SQL Insert: DB2 Committed Rows Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-126
SQL Insert - DB2 Delete Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-127
DB2 Load - DB2 Delete Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-128
SQL Insert: DB2 Discard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-129
MVS Load: VSAM Discard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-130
Chapter 6. Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Support for DB2 XML and LOB Data Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Delete Reference List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Request File Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Extract File Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Edit JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Delete Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Delete Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Discard File Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Save Delete Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
SAVE Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13
Viewing Delete JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Control Card Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14
The Delete Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
DB2 Delete Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15
DB2 Delete JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
DLDRV Step Parameter List and DD Statements. . . . . . . . . . . . . . . . . . . . . . . . . .6-18
Delete Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18
DELETE Step Parameters and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-20
x
File-AID/RDX Reference
MVS Delete Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
MVS Delete JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
DLDRV Step Parameter List and DD Statements. . . . . . . . . . . . . . . . . . . . . . . . . .6-24
MVS Delete Control Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-24
DLMVS Step Parameter List and DD Statements . . . . . . . . . . . . . . . . . . . . . . . . .6-25
MVS Delete Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-26
Miscellaneous Delete Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
DB2 Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
DB2 Delete Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27
CASCADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27
SET NULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27
Restartability (DB2 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Reusing the Discard File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Delete Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28
Delete - DB2 Authority Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-29
Pre-Delete Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-29
Delete: DB2 Discard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30
MVS Delete: VSAM Discard Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31
Delete: DB2 Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-32
MVS Delete: MVS Totals Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-32
Delete: DB2 Committed Rows Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-33
Chapter 7. Data Privacy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using File-AID/RDX with File-AID Data Privacy (Using DPR) . . . . . . . . . . . . .
Using File-AID/RDX with File-AID/Data Solutions (Using DCF) . . . . . . . . . . .
7-1
7-1
7-1
7-2
What Is Disguise? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
Planning Disguise Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-2
Creating DCF Disguise Criteria. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Simple and Complex Disguise Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4
Disguise Control File and Disguise Criteria Storage . . . . . . . . . . . . . . . . . . . . . . . .7-4
Sharing Disguised Data with Other File-AID Products . . . . . . . . . . . . . . . . . . . . . .7-5
DB2 XML and LOB Data Type Considerations . . . . . . . . . . . . . . . . . . . . . . . .
Disguise Considerations for Conditional (Data-Driven) Application
Relationships (AR-C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disguise Considerations for “Cloned” Extract Requests . . . . . . . . . . . . . . . . .
Unicode Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GDG Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Suggested Disguise Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-5
7-5
7-5
7-5
7-5
7-6
Data Privacy Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
DPR: Disguise Existing Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Override Data Privacy Environment Parameters . . . . . . . . . . . . . . . . . . . . . . . . .7-13
Override Execution Parameter in a Data Privacy Project . . . . . . . . . . . . . . . . . . .7-14
Multiple Origins for a Data Privacy Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
Special Instructions for Oracle Translate Table . . . . . . . . . . . . . . . . . . . . . . . . . .7-16
Set Incomplete Disguise Continuation Indicator . . . . . . . . . . . . . . . . . . . . . . . . .7-17
Control Card Cleanup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-17
Extract Reference List for Disguise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Request File Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NEW - DB2 Object Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NEW - MVS Object Filter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ObjectIn Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Disguise - Object List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ObjectOut - DB2 Object Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ObjectOut - MVS Object Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-18
7-21
7-24
7-26
7-28
7-29
7-31
7-32
ObjectOut Preview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-32
MVS XREF/Record Layout Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-33
MVS Catalog Utility File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-34
PDS Processing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-35
XREF Select Member List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-36
xi
Data Disguise - Column List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Associated Rules List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
File-AID/Data Solutions Criteria Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Criteria Menu - Associated Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Criteria Menu - Related Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Criteria Menu - Unrelated Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
Define Global Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
File-AID/Data Solutions Aging Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49
File-AID/Data Solutions Euro Conversion Criteria . . . . . . . . . . . . . . . . . . . . 7-49
File-AID/Data Solutions Triangulation Criteria . . . . . . . . . . . . . . . . . . . . . . . 7-50
File-AID/Data Solutions Date Analysis Criteria . . . . . . . . . . . . . . . . . . . . . . . 7-50
File-AID/Data Solutions Validation Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . 7-50
File-AID/Data Solutions Data Analysis Criteria . . . . . . . . . . . . . . . . . . . . . . . 7-51
File-AID/Data Solutions Data Translator Criteria . . . . . . . . . . . . . . . . . . . . . . 7-51
File-AID/Data Solutions Data Generator Criteria . . . . . . . . . . . . . . . . . . . . . . 7-52
File-AID/Data Solutions Pattern Data Generator Criteria . . . . . . . . . . . . . . . 7-52
File-AID/Data Solutions Field Exit Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52
File-AID/Data Solutions Data Encryption Criteria . . . . . . . . . . . . . . . . . . . . . 7-53
File-AID/Data Solutions Data Replace Criteria . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Disguise Criteria Dataset Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-54
DCF: Disguise Existing Extract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57
Redirect File-AID/Data Solutions Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-57
Set Incomplete Disguise Continuation Indicator . . . . . . . . . . . . . . . . . . . . . . . . .7-57
Control Card Cleanup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-58
File-AID/Data Solutions Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59
Allocate Disguise Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
Allocate Disguise Criteria File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62
Print Disguise Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
Print DCF Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Print Disguise Audit Trail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Printing Multiple Audit Trail Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
Audit Trail Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
HEX Print Report Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-68
Character Report Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-69
Summary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-70
Executing Print Audit Trail Independently in Batch . . . . . . . . . . . . . . . . . . . 7-71
Audit Trail Print Execution Return Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-71
Miscellaneous Data Privacy Topics (Using DCF) . . . . . . . . . . . . . . . . . . . . . . . 7-72
DB2 Alias, Synonym, and View Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
VSAM PATH Support for Disguise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
Size Allocation of Disguise Extract File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
Unlike Column/Field Data Types and Disguise Criteria . . . . . . . . . . . . . . . . . 7-72
Special Consideration for Numeric to Character Conversion . . . . . . . . . . . . . . .7-73
Normalized Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-73
Data Privacy JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74
Return Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-75
Data Privacy Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
Split File Allocation Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
File-AID Data Privacy Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
Chapter 8. File-AID/RDX Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
RDX Utilities Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Update Saved Extract Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
JCL/Overrides Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Override File Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-11
Override Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-13
Request File Member List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-16
Generated ESR JCL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-17
xii
File-AID/RDX Reference
Extract File Compress Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-22
Generate DDL Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
View JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-25
Chapter 9. Tutorial and Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Primary Menu Option T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HELP Primary Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-1
9-1
9-1
9-2
Tutorial Help Pull-down Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
Help Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3
Appendix A. Command Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Primary Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
ACCEPT (A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
ADD (A). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
BACK (BA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
CANCEL (CAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
CAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
CHANGE (C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
CHECK (CHE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
COND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
CREATOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
CURSOR* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
DB2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
DELETE (DEL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
DETAIL (D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
DOWN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
EDIT (E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
END* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
EXCLUDE (EX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
EXPAND* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
FILTER (FIL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
FIND (F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
FORWARD (FOR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
FUNCTION LOCK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
GEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
GO (G). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
GRAPHIC (G,GR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
HELP* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
HIDE (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
IGNORE (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
INSERT (INS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
KEYLIST* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
KEYS* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
LEFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
LIMITKEY (LK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
LOCATE (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
MENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
MODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
NAVIGATION (NAV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
NEW (N) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
NEXT (N). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
OBJECTIN (OI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
OBJECTOUT (OO). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
PARTITION (PART) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
PREV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
PRINT* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
PRINT-HI* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
PRINTL* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
PRINTLHI* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
REFERENCE (REF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
REFRESH (R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
xiii
REPEAT (REP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REPORT (REP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REQUEST (REQ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RESET (RES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RETRIEVE* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RETURN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RFIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RIGHT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAMPLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHOW (SH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SIZE (SI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SPLIT* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SQLID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STATUS (STAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SUBMIT* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SUGGEST (SUG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SWAP* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TABLE (TAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TSO* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UDTSWAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UDTTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNEXCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VALIDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VIEW (VI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-10
A-10
A-10
A-10
A-10
A-10
A-11
A-11
A-11
A-11
A-11
A-11
A-11
A-12
A-12
A-12
A-12
A-12
A-12
A-12
A-12
A-12
A-13
A-13
A-13
A-13
A-13
Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-14
A (Accept Path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A (Add) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A (Add/Assign Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A (All) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B (Browse) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C (Change and Go) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C (Copy) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D (Delete) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E (Edit AR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
E (Edit Object) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
G (Go) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I (Ignore Path) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I (Information) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I (Insert). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L (List DB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L (Load RI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L (Lock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L (Lock Table) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M (Modify Request) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M (Modify MVS Object) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
n (Column or Field Number) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
O (ObjectOut) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
P (Passthru) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
R (Related objects). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
R (Relationship View) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
R (Remove) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
R (Rename) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
R (Repeat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
R (Restore original name) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
S (Select) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
U (Unassign Rule) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
U (Unexclude) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
U (Undo Remove) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
U (Unlock). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
U (Update) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
V (View JCL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X (Exclude) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A-14
A-14
A-14
A-14
A-14
A-14
A-15
A-15
A-15
A-15
A-15
A-15
A-15
A-16
A-16
A-16
A-16
A-16
A-16
A-16
A-17
A-17
A-17
A-17
A-17
A-17
A-17
A-17
A-17
A-17
A-18
A-18
A-18
A-18
A-18
A-18
A-18
xiv
File-AID/RDX Reference
Appendix B. Extract Navigation Criteria Examples . . . . . . . . . . . . . . . . . . . . . . . . B-1
A Closer Look . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Navigation Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Order of Accessing Objects During Execution . . . . . . . . . . . . . . . . . . . . . . . . B-1
Examples Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Summary Comparison of Extract Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
DPSI=YYNY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
DPSI=YYNN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
DPSI=YYNN Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
DPSI=YYYY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
DPSI=YYYY Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
DPSI=YYYY, CYCLE=1, QUIESCE=Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
DPSI=YYYY CYCLE=1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
DPSI=YYNN Modified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
Modified Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
DPSI=PYNN Direct Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21
Direct Plus Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21
DPSI=CNNN All Children Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23
All Children Only Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23
DPSI=YYNY Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25
DPSI=YYNN Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27
DPSI=YYYY Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
DPSI=YYYY, CYCLE=1, QUIESCE=Q Example 2 . . . . . . . . . . . . . . . . . . . . . B-34
DPSI=YYNN Modified Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37
DPSI=PYNN Direct Plus Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-39
DPSI=CNNN All Children Only Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . B-41
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . I-1
Figures
xv
Figures
1-1.
1-2.
1-3.
1-4.
1-5.
1-6.
1-7.
1-8.
1-9.
1-10.
1-11.
1-12.
2-1.
2-2.
2-3.
2-4.
2-5.
2-6.
2-7.
2-8.
2-9.
2-10.
2-11.
2-12.
2-13.
3-1.
3-2.
3-3.
3-4.
3-5.
3-6.
3-7.
3-8.
3-9.
3-10.
3-11.
3-12.
3-13.
3-14.
3-15.
3-16.
3-17.
3-18.
3-19.
3-20.
3-21.
3-22.
3-23.
3-24.
3-25.
3-26.
3-27.
3-28.
3-29.
3-30.
3-31.
3-32.
3-33.
File-AID/RDX Primary Option Menu .......................................................................1-2
Option Selection Screen Example ............................................................................1-6
Option Information Screen Example .......................................................................1-7
Scrollable Data Screen Example................................................................................1-7
Selection Pop-Up Window Example ........................................................................1-8
Information Display Screen Example.......................................................................1-8
Long Name Indicator Example...............................................................................1-10
EXPAND Command in Scrollable Field .................................................................1-11
EXPANDed Field .....................................................................................................1-11
Subsystem ID Selection Window............................................................................1-14
DB2 Call Attach Alert .............................................................................................1-15
File-AID for DB2 Primary Option Menu .................................................................1-27
RDX Profile Screen....................................................................................................2-1
Select Profile Screen ..................................................................................................2-3
Copy Profile window ................................................................................................2-4
Rename Profile window............................................................................................2-4
Session and Batch Defaults.......................................................................................2-6
Extract Defaults - Scrollable Screen ..........................................................................2-8
Load Defaults - Scrollable Screen............................................................................2-13
Disguise Defaults - Scrollable Screen ......................................................................2-17
Privacy Repository List Screen ................................................................................2-19
Privacy Project List Screen ......................................................................................2-20
Permanent File Defaults - Scrollable Screen ...........................................................2-21
Temporary File Defaults Screen ..............................................................................2-24
Global User Defaults Screen ...................................................................................2-26
Sample Scenario of Conditional AR .........................................................................3-3
DB2 Relationship Facilitator.....................................................................................3-5
DB2 Object List .........................................................................................................3-7
Table List in Relationship File ..................................................................................3-9
Table List - SYSIBM.SYSTABLES ..............................................................................3-10
MVS Relationship Facilitator ..................................................................................3-11
MVS Object List ......................................................................................................3-13
Object List in Relationship File ..............................................................................3-14
Relationship Detail .................................................................................................3-15
Graphical Relationship Display Screen ..................................................................3-17
Graphical Relationship Display with Option List ..................................................3-19
Relationship Information Screen—RI relationship information ...........................3-20
Relationship Information Screen—MVS to DB2 Application 
Relationship Information .................................................................................3-21
Relationship Information Screen—MVS to MVS AR Relationship Information ...3-21
DB2 RI Update Online Options Screen ..................................................................3-24
RI Relationship Detail Screen RI Load Option 1 ....................................................3-26
RI Relationship Detail Screen RI Load Option 2 ....................................................3-27
RI Relationship Detail Screen RI Load Option 3 ....................................................3-27
RI Relationship Detail Screen RI Load Option 4 ....................................................3-28
RI Information Screen ............................................................................................3-30
Application Relationship Detail Screen..................................................................3-32
Object Type Selection Screen for Adding Application Relationship......................3-34
Add Relationships Screen — DB2 to DB2...............................................................3-35
Add Relationships Screen — DB2 to MVS ..............................................................3-37
Add Relationships Screen — DB2 to KEY ...............................................................3-39
Add Relationships Screen — MVS to DB2 ..............................................................3-42
Add Relationships Screen — MVS to MVS .............................................................3-44
Add Relationship Screen — MVS to KEY................................................................3-47
Relationships Screen - Column Relationships not yet defined..............................3-50
Relationships Screen — Field Relationships already defined.................................3-51
Relationships Screen — with Unicode data ...........................................................3-51
Selection Criteria Menu ..........................................................................................3-57
View Criteria Screen ...............................................................................................3-58
xvi
File-AID/RDX Reference
3-34.
3-35.
3-36.
3-37.
3-38.
3-39.
3-40.
3-41.
3-42.
3-43.
3-44.
3-45.
3-46.
3-47.
3-48.
3-49.
3-50.
3-51.
3-52.
3-53.
3-54.
3-55.
3-56.
3-57.
3-58.
3-59.
3-60.
3-61.
3-62.
3-63.
4-1.
4-2.
4-3.
4-4.
4-5.
4-6.
4-7.
4-8.
4-9.
4-10.
4-11.
4-12.
4-13.
4-14.
4-15.
4-16.
4-17.
4-18.
4-19.
4-20.
4-21.
4-22.
4-23.
4-24.
4-25.
4-26.
4-27.
4-28.
4-29.
4-30.
Selection Criteria Options ......................................................................................3-59
Selection Criteria Options Example .......................................................................3-60
Selection Criteria Options Example. Default - Examines All Records ...................3-61
Formatted Selection Criteria Screen .......................................................................3-61
Formatted Selection Criteria Examples ..................................................................3-63
Field Mask Criteria..................................................................................................3-68
Relationships Screen — Creating a DB2 to MVS Relationship ..............................3-70
Extended Column Relationship Definition Window ............................................3-71
Relationships Screen — New DB2 Column to MVS Field Relationship 
Established. .......................................................................................................3-71
Extended Column Relationship Definition Window ............................................3-72
Relationship Screen with column-number command...........................................3-75
Extended Column Relationship Definition Window ............................................3-75
Column/Segment Relationships Screen with Segment-Number command..........3-76
Extended Column Relationship Definition Window ............................................3-76
Changed Dependent Start Position and Length ....................................................3-77
Partial Column/Segment Relation Established ......................................................3-77
Column/Field Relationships Screen Mapping DECIMAL to CHAR .......................3-78
Extended Column Relationship Definition Window with DECIMAL to CHAR ...3-78
Extended Column Relationship Definition Window after Modification ..............3-79
Specify MVS Field Subscripts for Parent Field ........................................................3-79
Specify MVS FIeld Subscripts for Dependent Field ................................................3-80
Extended Field Relationship Definition with Field Subscripts Defined.................3-81
Extended Field Relationship with Defined Subscripted Relationship ...................3-81
Allocate Relationship File .......................................................................................3-82
Batch RI Load..........................................................................................................3-84
RI load Batch Job JCL .............................................................................................3-85
Formatted Relationship Report Screen ...................................................................3-87
Print Options Screen...............................................................................................3-88
ISPF/PDF EDIT Screen — File-AID/RDX-generated JCL .........................................3-89
Relationship File - Related Objects Report .............................................................3-90
Sample Tables and Relationships .............................................................................4-2
Global Navigation Controls - Direct = Y ..................................................................4-4
Global Navigation Controls - Direct = Y, Parent = Y ...............................................4-4
Global Navigation Controls - Direct = Y, Parent = Y, Sibling = Y ............................4-5
Global Navigation Controls - Direct = Y, Parent = Y, Sibling = Y, Indirect = Y .......4-6
Driving Object - DB2 ................................................................................................4-8
Relationship Listing..................................................................................................4-9
Relationship Navigation Criteria..............................................................................4-9
Load Object Specification.......................................................................................4-10
Extracting Data From Subsystem ACCEPT Based on Relationships in 
Subsystem PROD...............................................................................................4-11
Extract - DB2 Driving Object..................................................................................4-14
Extract - MVS Driving Object .................................................................................4-18
Extract Reference List .............................................................................................4-20
Request Details .......................................................................................................4-21
Extract Reference List - DETAIL Screen ..................................................................4-22
Extract Reference List - Size Screen.........................................................................4-23
Request File Member List Screen ............................................................................4-24
Delete Confirmation window ................................................................................4-25
Rename Confirmation window..............................................................................4-25
Request File Member List - Size Screen...................................................................4-26
DB2 Driving Object ................................................................................................4-28
Relationship Listing Window—Multiple Relationship Definitions.......................4-30
Partially Matching Relationship.............................................................................4-31
Modify Extract Request ..........................................................................................4-32
Modify Extract Request - Object Names.................................................................4-33
CHANGE Command Window - Modify Extract Request.......................................4-34
Modify Object Names - DETAIL Screen..................................................................4-35
Extract Reference List - Size Screen.........................................................................4-35
Save Cloned Extract Request ..................................................................................4-36
Save Confirmation window....................................................................................4-37
Figures
4-31.
4-32.
4-33.
4-34.
4-35.
4-36.
4-37.
4-38.
4-39.
4-40.
4-41.
4-42.
4-43.
4-44.
4-45.
4-46.
4-47.
4-48.
4-49.
4-50.
4-51.
4-52.
4-53.
4-54.
4-55.
4-56.
4-57.
4-58.
4-59.
4-60.
4-61.
4-62.
4-63.
4-64.
4-65.
4-66.
4-67.
4-68.
4-69.
4-70.
4-71.
4-72.
4-73.
4-74.
4-75.
4-76.
4-77.
4-78.
4-79.
4-80.
4-81.
4-82.
4-83.
4-84.
4-85.
4-86.
4-87.
4-88.
4-89.
4-90.
4-91.
xvii
MVS Driving Object................................................................................................4-38
Relationship Listing Window - No Relationships ..................................................4-40
MVS Catalog Utility File List (for Pattern FR*.ORDERTAB) ...................................4-40
PDS Processing Options Screen ..............................................................................4-41
XREF Select Member List Screen.............................................................................4-42
Extract Menu ..........................................................................................................4-44
Extract Menu - Interactive Extract Mode ...............................................................4-47
Driving Object - DB2 ..............................................................................................4-48
Driving Object - MVS .............................................................................................4-48
Extract Scope Screen ...............................................................................................4-50
SELECT FROM Temporal Table ..............................................................................4-54
Extract Scope - Object View....................................................................................4-56
CHANGE Command Window - Object View Sampling Criteria ...........................4-59
Exclude Command Window ..................................................................................4-60
Hide Command Window .......................................................................................4-61
Unexclude Command Window .............................................................................4-62
Relationship Criteria...............................................................................................4-63
Exclude Command Window - Relationship View .................................................4-65
Filter Command Window.......................................................................................4-66
Hide Command Window .......................................................................................4-67
Unexclude Command Window - Relationship View.............................................4-68
Relationship Sampling Criteria ..............................................................................4-70
CHANGE Command Window - Relationship Sampling Criteria...........................4-72
Relationship Navigation Criteria............................................................................4-73
CHANGE Command Window - Relationship Navigation Criteria........................4-75
Graphical Relationship Display Screen ..................................................................4-76
Graphical Relationship Display with Option List ..................................................4-77
Relationship Information Window — RI Relationship Information.....................4-79
Relationship Information Screen—MVS to DB2 Application Relationship 
Information.......................................................................................................4-79
Check Extract Warning ..........................................................................................4-80
Relationship Listing — Update Saved Request Window........................................4-82
Unrelated Object Definition...................................................................................4-83
Add Unrelated DB2 Object .....................................................................................4-85
Unrelated Object Specification...............................................................................4-86
Modify Unrelated MVS Object Definition .............................................................4-87
Input Key File Specification....................................................................................4-89
Input Key File - Positional ......................................................................................4-91
Input Key File - Delimited ......................................................................................4-92
Object Selection Criteria.........................................................................................4-94
DB2 Object Selection Criteria.................................................................................4-97
Distinct Data Types for This Extract Window......................................................4-101
Object Selection Criteria Screen — Undisplayable Criteria Specified..................4-101
SQL Edit Screen.....................................................................................................4-102
Selection Criteria Menu ........................................................................................4-103
View Criteria Screen .............................................................................................4-104
Selection Criteria Options ....................................................................................4-105
Selection Criteria Options Example .....................................................................4-106
Selection Criteria Options Example. Default - Examines All Records .................4-107
Formatted Selection Criteria Screen .....................................................................4-107
Formatted Selection Criteria Examples ................................................................4-109
Field Mask Criteria................................................................................................4-114
Record Layout Specification Screen......................................................................4-115
Display XREF Screen .............................................................................................4-116
Formatted Selection Criteria Screen. For Multiple Record Type Files. .................4-117
Output Key Files ...................................................................................................4-118
Output Key File Definition ...................................................................................4-120
Create New File.....................................................................................................4-121
Extract File Specification Screen...........................................................................4-124
Data Privacy Specification ....................................................................................4-127
Supporting File Specification................................................................................4-129
Continue With Load.............................................................................................4-131
xviii
File-AID/RDX Reference
4-92.
4-93.
4-94.
4-95.
4-96.
4-97.
4-98.
4-99.
4-100.
4-101.
4-102.
4-103.
4-104.
4-105.
4-106.
4-107.
4-108.
4-109.
4-110.
4-111.
4-112.
4-113.
4-114.
4-115.
4-116.
4-117.
4-118.
4-119.
4-120.
4-121.
4-122.
4-123.
4-124.
4-125.
4-126.
4-127.
4-128.
4-129.
4-130.
4-131.
4-132.
4-133.
5-1.
5-2.
5-3.
5-4.
5-5.
5-6.
5-7.
5-8.
5-9.
5-10.
5-11.
5-12.
5-13.
5-14.
5-15.
5-16.
5-17.
5-18.
5-19.
Save Extract Request .............................................................................................4-132
Save Confirmation window..................................................................................4-133
ISPF/PDF EDIT Screen—File-AID/RDX-generated JCL .........................................4-134
Manage Translate Tables ......................................................................................4-136
Process Variables...................................................................................................4-136
Manage Execution Parameters .............................................................................4-137
ISPF/PDF EDIT Screen—File-AID/RDX Generated REXX .....................................4-139
Interactive Extract Execution ...............................................................................4-140
Interactive Extract Reports ...................................................................................4-141
Extract JCL ............................................................................................................4-142
Extract JCL XFRIMAGE Parm statement ..............................................................4-143
Sample Extract/Load Request File ........................................................................4-146
Product Record Layout .........................................................................................4-155
Header Record Layout ..........................................................................................4-155
Base Table Record Layout .....................................................................................4-156
Database Create Record Layout ............................................................................4-157
Tablespace Create Record Layout .........................................................................4-158
DB2 Source Environment Record Layout.............................................................4-158
MVS File Create Record Layout ............................................................................4-159
View Create Record Layout ..................................................................................4-159
Alias Create Record Layout...................................................................................4-160
Synonym Create Record Layout ...........................................................................4-160
Map Record Layout...............................................................................................4-161
Relationship Record Layout .................................................................................4-161
Data Record Layout ..............................................................................................4-161
XML/LOB Data Record Layout .............................................................................4-162
Order Record Layout.............................................................................................4-162
Trailer Record Layout ...........................................................................................4-163
Record Layout JCL ................................................................................................4-165
Sample COBOL Record Layout (Create XREF=NO)..............................................4-167
Sample PL/I Record Layout (created with XREF=YES) .........................................4-168
Sample XREF for DB2 and MVS objects ...............................................................4-169
Extract Progress Report .........................................................................................4-170
Relationship Navigation and Sampling Report....................................................4-171
Relationship Navigation and Sampling Excluded Object Report ........................4-172
Object Sampling and Selection Criteria Report ...................................................4-173
Object Sampling and Selection Criteria Excluded Object Report ........................4-175
Extract Summary Report.......................................................................................4-176
Summary of Objects with Zero Rows Extracted ...................................................4-177
Create Record Layout Report................................................................................4-178
DB2 Index Report .................................................................................................4-179
DB2 Index Report with Hybrid Scan ....................................................................4-179
Load Reference List...................................................................................................5-3
Request Details .........................................................................................................5-4
Load Reference List - DETAIL Screen........................................................................5-4
Load Reference List - SIZE Screen .............................................................................5-5
Request File Member List Screen ..............................................................................5-6
Delete Confirmation window ..................................................................................5-6
Rename Confirmation window................................................................................5-7
Request File Member List - SIZE Screen ....................................................................5-7
Extract File Specification ..........................................................................................5-8
ISPF/PDF EDIT Screen ...............................................................................................5-9
Load Menu..............................................................................................................5-10
Load Menu - ONLINE Mode...................................................................................5-12
Load Object Specifications .....................................................................................5-13
Source to Target Mapping ......................................................................................5-16
Change Command Window ..................................................................................5-19
Exclude Command Window ..................................................................................5-20
File Mapping Specifications....................................................................................5-21
Field Mapping.........................................................................................................5-23
Column Mapping ...................................................................................................5-26
Figures
5-20.
5-21.
5-22.
5-23.
5-24.
5-25.
5-26.
5-27.
5-28.
5-29.
5-30.
5-31.
5-32.
5-33.
5-34.
5-35.
5-36.
5-37.
5-38.
5-39.
5-40.
5-41.
5-42.
5-43.
5-44.
5-45.
5-46.
5-47.
5-48.
5-49.
5-50.
5-51.
5-52.
5-53.
5-54.
5-55.
5-56.
5-57.
5-58.
5-59.
5-60.
5-61.
5-62.
5-63.
5-64.
5-65.
5-66.
5-67.
5-68.
5-69.
5-70.
5-71.
5-72.
5-73.
5-74.
5-75.
5-76.
5-77.
5-78.
5-79.
5-80.
5-81.
xix
Default Value Definition ........................................................................................5-28
Default Value Specification ....................................................................................5-30
Delete Value Confirmation ....................................................................................5-31
DB2 Column Mapping Screen After Some Column Assignments .........................5-34
Target Environment................................................................................................5-35
CHANGE Command Window................................................................................5-38
CHANGE Command Window with Stogroup Option...........................................5-39
Exclude Command Window ..................................................................................5-40
Hide Command Window .......................................................................................5-41
Show Command Window ......................................................................................5-43
Target Environment - SIZE Screen with SHOW DATABASE ..................................5-43
Create Database ......................................................................................................5-45
Create Tablespace ...................................................................................................5-46
Tablespace Partition Definition..............................................................................5-50
CHANGE Command Window - Partition Definition ............................................5-52
Create DB2 Table ....................................................................................................5-53
Limit Key Definition...............................................................................................5-55
Create Index ...........................................................................................................5-56
Index Partition Definition ......................................................................................5-58
Create Alias .............................................................................................................5-60
Create Synonym .....................................................................................................5-61
Create View.............................................................................................................5-62
Create View (Complex) ..........................................................................................5-63
Tables Within View ................................................................................................5-64
Create MVS File.......................................................................................................5-64
Create VSAM CLUSTER ..........................................................................................5-66
Create VSAM AIX....................................................................................................5-68
Create VSAM PATH.................................................................................................5-69
Existing Data Options.............................................................................................5-71
CHANGE Command Window - Existing Data Options.........................................5-73
Processing Options .................................................................................................5-74
Save Load Request...................................................................................................5-76
Save Confirmation window....................................................................................5-76
ISPF/PDF VIEW - File-AID/RDX Generated JCL .....................................................5-77
ISPF/PDF EDIT Screen—File-AID/RDX Generated REXX .......................................5-78
Interactive Load Reports.........................................................................................5-79
DB2 Load Utility Load JCL (continues on next page)............................................5-83
DB2 Load Utility Load JCL (continues on next page)............................................5-84
DB2 Load Utility Load JCL (continues on next page)............................................5-85
DB2 Load Utility Load JCL .....................................................................................5-86
DB2 Create DDL (member DB2CREAT) .................................................................5-88
DB2 Load Control Table (DB2LCT) ........................................................................5-90
SYSIN Load Data (member LOADnnn) ...................................................................5-93
SQL Insert Load JCL (continues on next page) ......................................................5-96
SQL Insert Load JCL (continues on the next page)................................................5-97
SQL Insert Load JCL................................................................................................5-98
Create DDL (member DB2CREAT) .......................................................................5-100
Load Control table (member DB2LCT) ................................................................5-102
MVS Load JCL (continues on next page) .............................................................5-107
MVS Load JCL (continues on the next page) .......................................................5-108
MVS Load JCL .......................................................................................................5-109
Sample VSAMCRTE control card (Member VSAMCRTE) .....................................5-110
MVS Load Control Table (MVSLCT) ....................................................................5-112
Example of SQLID Authorization Error Comments in Load JCL.........................5-119
SQL Insert - DB2 Authority Report.......................................................................5-122
DB2 Load - DB2 Authority Report........................................................................5-122
Create DB2 Target Environment Report ..............................................................5-123
Pre-Load Summary Report....................................................................................5-124
SQL Insert: DB2 Totals Report ..............................................................................5-126
MVS Load - MVS Totals Report ............................................................................5-126
SQL Insert: DB2 Committed Rows Report............................................................5-127
SQL Insert - DB2 Delete Report ............................................................................5-128
xx
File-AID/RDX Reference
5-82.
5-83.
5-84.
6-1.
6-2.
6-3.
6-4.
6-5.
6-6.
6-7.
6-8.
6-9.
6-10.
6-11.
6-12.
6-13.
6-14.
6-15.
6-16.
6-17.
6-18.
6-19.
6-20.
6-21.
6-22.
6-23.
6-24.
6-25.
6-26.
6-27.
6-28.
6-29.
7-1.
7-2.
7-3.
7-4.
7-5.
7-6.
7-7.
7-8.
7-9.
7-10.
7-11.
7-12.
7-13.
7-14.
7-15.
7-16.
7-17.
7-18.
7-19.
7-20.
7-21.
7-22.
7-23.
7-24.
7-25.
7-26.
7-27.
7-28.
7-29.
DB2 Load - DB2 Delete Report .............................................................................5-128
SQL Insert: DB2 Discard Report............................................................................5-129
MVS Load: VSAM Discard Report.........................................................................5-130
Delete Reference List.................................................................................................6-2
Request Details .........................................................................................................6-3
Delete Reference List - DETAIL Screen .....................................................................6-4
Delete Reference List - SIZE Screen...........................................................................6-5
Request File Member List..........................................................................................6-5
Delete Confirmation window ..................................................................................6-6
Rename Confirmation window................................................................................6-6
Saved Request File Member List - SIZE Screen..........................................................6-7
Extract File Specification ..........................................................................................6-7
ISPF/PDF EDIT Screen ...............................................................................................6-8
Delete Confirmation.................................................................................................6-9
Delete Processing Options Screen ..........................................................................6-10
DISCARD File Allocation Pop-Up Window ............................................................6-11
Save Delete Request ................................................................................................6-12
Save Confirmation window....................................................................................6-13
ISPF/PDF VIEW Screen............................................................................................6-13
Delete JCL (continues on next page)......................................................................6-16
DB2 Delete JCL (continued) ...................................................................................6-17
DB2 Delete Control Table.......................................................................................6-19
MVS Delete JCL (continues on next page) .............................................................6-22
MVS Delete JCL (continued from previous page) ..................................................6-23
MVS Delete Control Table (MVSDCT) ...................................................................6-25
Delete - DB2 Authority Report ...............................................................................6-29
Pre-Delete Summary Report ...................................................................................6-30
Delete: DB2 Discard Report ....................................................................................6-31
MVS Delete: VSAM Discard Report ........................................................................6-31
Delete: DB2 Totals Report.......................................................................................6-32
MVS Delete: MVS Totals Report .............................................................................6-33
Delete: DB2 Committed Rows Report ....................................................................6-33
Data Privacy Menu ...................................................................................................7-7
DPR: Disguise Existing Extract ...............................................................................7-10
View File-AID/RDX generated JCL .........................................................................7-13
Manage Translate Tables ........................................................................................7-14
Process Variables.....................................................................................................7-15
Manage Execution Parameters ...............................................................................7-15
Extract Reference List for Disguise .........................................................................7-18
Request Details .......................................................................................................7-19
Extract Reference List - DETAIL Screen ..................................................................7-20
Extract Reference List - Size Screen.........................................................................7-20
Request File Member List Screen ............................................................................7-21
Delete Confirmation window ................................................................................7-22
Rename Confirmation window..............................................................................7-22
Request File Member List - Size Screen...................................................................7-23
NEW - DB2 Object Filter.........................................................................................7-24
NEW - MVS Object Filter ........................................................................................7-26
ObjectIn Preview ....................................................................................................7-28
Data Disguise - Object List......................................................................................7-29
Disguised Columns Information ............................................................................7-30
Related ObjectIn Preview........................................................................................7-30
Database ObjectIn Preview .....................................................................................7-30
ObjectOut - DB2 Object Filter ................................................................................7-31
ObjectOut - MVS Object Filter ...............................................................................7-32
ObjectOut Preview..................................................................................................7-33
MVS XREF/Record Layout Window .......................................................................7-34
MVS Catalog Utility File List (for Pattern FAS*.LAY*) ............................................7-34
PDS Processing Options Screen ..............................................................................7-35
XREF Select Member List Screen.............................................................................7-36
Data Disguise - Column/Field List..........................................................................7-37
Figures
7-30.
7-31.
7-32.
7-33.
7-34.
7-35.
7-36.
7-37.
7-38.
7-39.
7-40.
7-41.
7-42.
7-43.
7-44.
7-45.
7-46.
7-47.
7-48.
7-49.
7-50.
7-51.
7-52.
7-53.
7-54.
7-55.
7-56.
7-57.
7-58.
7-59.
7-60.
7-61.
7-62.
7-63.
7-64.
7-65.
7-66.
7-67.
8-1.
8-2.
8-3.
8-4.
8-5.
8-6.
8-7.
8-8.
8-9.
8-10.
8-11.
8-12.
8-13.
8-14.
8-15.
8-16.
9-1.
9-2.
9-3.
9-4.
9-5.
9-6.
9-7.
xxi
Unrelated Rules Information - Criteria in Disguise Criteria File............................7-38
Associated Rules List ...............................................................................................7-40
File-AID/Data Solutions Criteria Menu ..................................................................7-41
File-AID/Data Solutions Full Criteria Menu ...........................................................7-44
File-AID/Data Solutions Criteria Menu - Associated Mode ....................................7-46
File-AID/Data Solutions Criteria Menu - Related Mode .........................................7-47
File-AID/Data Solutions Criteria Menu - Unrelated Mode.....................................7-48
Define Global Fields Screen ....................................................................................7-48
File-AID/Data Solutions Aging Criteria ..................................................................7-49
File-AID/Data Solutions Euro Conversion Criteria ................................................7-49
File-AID/Data Solutions Triangulation Criteria......................................................7-50
File-AID/Data Solutions Date Analysis Criteria......................................................7-50
File-AID/Data Solutions Validation Criteria...........................................................7-51
File-AID/Data Solutions Data Analysis Criteria......................................................7-51
File-AID/Data Solutions Data Translator Criteria...................................................7-51
File-AID/Data Solutions Data Generator Criteria...................................................7-52
File-AID/Data Solutions Pattern Data Generator Criteria ......................................7-52
File-AID/Data Solutions Field Exit Criteria.............................................................7-53
File-AID/Data Solutions Data Encryption Criteria .................................................7-53
File-AID/Data Solutions Data Replace Criteria .......................................................7-54
File-AID/Data Solutions Change Criteria Dataset Specification - New Criteria.....7-54
DCF: Disguise Existing Extract ...............................................................................7-55
View File-AID/RDX generated JCL .........................................................................7-57
File-AID/Data Solutions Parameters .......................................................................7-59
Allocate Disguise Control File ................................................................................7-60
Allocate Disguise Criteria File.................................................................................7-62
Print Disguise Control File .....................................................................................7-64
Sample Print DCF Report by Object .......................................................................7-65
Sample Print DCF Report by Rule...........................................................................7-66
Print Disguise Audit Trail .......................................................................................7-67
Audit Trail Report — Hexadecimal.........................................................................7-69
Audit Trail Report — Character..............................................................................7-70
Audit Trail Report — Summary ..............................................................................7-71
Print Audit Trail JCL ...............................................................................................7-71
Data Privacy JCL .....................................................................................................7-74
SMSMODEL DD statement .....................................................................................7-75
Split File Allocation Report.....................................................................................7-76
Data Privacy Summary Report................................................................................7-77
Utilities Menu ...........................................................................................................8-1
Update Saved Extract Requests.................................................................................8-3
Update Saved Extract Requests JCL ..........................................................................8-6
Sample Update Saved Extract Requests Report ........................................................8-8
Execute Saved Request (ESR) Options ......................................................................8-9
Sample DB2 SC (Selection Criteria) Override File ..................................................8-15
Sample MVS SC (Selection Criteria) Override File .................................................8-15
Request File Member List Screen ............................................................................8-17
Generated ESR JCL..................................................................................................8-18
Sample Execute Saved Requests Utility Report ......................................................8-19
Extract File - Compress Utility................................................................................8-20
ISPF/PDF EDIT Screen—File-AID/RDX-generated JCL............................................8-22
Extract File Compress Utility Report ......................................................................8-22
Generate DDL Utility..............................................................................................8-23
ISPF/PDF EDIT Screen—File-AID/RDX-generated JCL - Generate DDL .................8-25
Generate DDL Utility Report ..................................................................................8-25
Tutorial Introduction–First Screen ...........................................................................9-1
Tutorial Introduction–Second Screen.......................................................................9-2
Tutorial Introduction–Third Screen .........................................................................9-2
Tutorial Table of Contents .......................................................................................9-3
Help Pull-down Menu ..............................................................................................9-3
Help Index Screen.....................................................................................................9-4
Find Command in Actions Pull-Down.....................................................................9-4
xxii
File-AID/RDX Reference
9-8.
9-9.
A-1.
A-2.
B-1.
B-2.
B-3.
B-4.
B-5.
B-6.
B-7.
B-8.
B-9.
B-10.
B-11.
B-12.
B-13.
B-14.
B-15.
Find Key Word Entry Screen ....................................................................................9-4
Help Index Find Result Window ..............................................................................9-5
Filter Command Window ....................................................................................... A-4
Enter Find Parameter Window ................................................................................ A-6
Test Data Sample Structure.......................................................................................B-2
Example 1 - DPSI=YYNY...........................................................................................B-6
Example 1 - DPSI=YYNN ..........................................................................................B-8
Example 1 - DPSI=YYYY .........................................................................................B-13
Example 1 - DPSI=YYYY, CYCLE=1, QUIESCE=Q ..................................................B-17
Example 1 - DPSI=YYNN (Modified) ......................................................................B-20
Example 1 - DPSI=PYNN (Direct Plus)....................................................................B-22
Example 1 - DPSI=CNNN (All Children Only).......................................................B-24
Example 2 - DPSI=YYNY.........................................................................................B-26
Example 2 - DPSI=YYNN ........................................................................................B-28
Example 2 - DPSI=YYYY .........................................................................................B-33
Example 2 - DPSI=YYYY, CYCLE=1, QUIESCE=Q ..................................................B-36
Example 2 - DPSI=YYNN Modified.........................................................................B-38
Example 2 - DPSI=PYNN Direct Plus ......................................................................B-40
Example 1 - DPSI=CNNN (All Children Only).......................................................B-42
Tables
xxiii
Tables
1-1.
1-2.
1-3.
1-4.
1-5.
1-6.
3-1.
3-2.
3-3.
4-1.
4-2.
4-3.
4-4.
4-5.
4-6.
4-7.
4-8.
4-9.
4-10.
4-11.
4-12.
4-13.
5-1.
5-2.
5-3.
5-4.
5-5.
5-6.
5-7.
5-8.
5-9.
5-10.
5-11.
5-12.
5-13.
5-14.
5-15.
5-16.
5-17.
5-18.
5-19.
5-20.
5-21.
5-22.
5-23.
5-24.
5-25.
5-26.
5-27.
5-28.
5-29.
5-30.
5-31.
5-32.
5-33.
5-34.
5-35.
5-36.
Valid Scroll Amount Values......................................................................................1-9
Default Key Lists for File-AID/RDX ........................................................................1-12
Key Fields ................................................................................................................1-17
Related Object Information....................................................................................1-18
Relationship Details (parent objects only) .............................................................1-18
MVS Record Layout Information ...........................................................................1-20
Relationship Titles ..................................................................................................3-50
Data Type Values ....................................................................................................3-53
Column/Field Types Mapping................................................................................3-54
DB2 Subsystems ........................................................................................................4-8
Conversion of Old Extract Methods.......................................................................4-26
Maximum Key File Lengths....................................................................................4-92
Data Type Values ....................................................................................................4-97
Output Key File Layout.........................................................................................4-118
Data Privacy Environment Parameter Overrides..................................................4-135
EXEC Statement PARM Field—Extract Step .........................................................4-143
EXEC Statement PARM Field—Extract Step for Image Copy ...............................4-143
DD Statements—Extract .......................................................................................4-143
File-AID/RDX Encryption Exit Output Parameters ..............................................4-165
File-AID/RDX Encryption Exit Input Parameters .................................................4-165
EXEC Statement PARM Field—Extract Step .........................................................4-166
DD Statements—Record Layout ...........................................................................4-166
Target Objects Status Messages...............................................................................5-17
Data Type Values ....................................................................................................5-24
Column/Field Mapping Data Type Compatibility.................................................5-32
Numeric Data Type Value Ranges ..........................................................................5-33
Object Status Messages ...........................................................................................5-37
Valid Tablespace Types ...........................................................................................5-49
Valid Tablespace Type Changes .............................................................................5-49
EXEC Statement PARM Field—CREATE Step .........................................................5-87
DD Statements—CREATE Step ...............................................................................5-87
EXEC Statement PARM Field——LDDRV Step.......................................................5-89
DD Statements—LDDRV Step ................................................................................5-89
Load Control Table—Source and Target Table Information..................................5-90
Load Control Table—Column Mapping Information ...........................................5-91
EXEC Statement PARM Field—DELTEnnn Step.....................................................5-92
DD Statements—DELTEnnn Step...........................................................................5-92
DD Statements—SORT Step....................................................................................5-92
EXEC Statement PARM Field—CREATE Step .........................................................5-99
DD Statements—CREATE Step ...............................................................................5-99
EXEC Statement PARM Field——LDDRV Step.....................................................5-101
DD Statements—LDDRV Step ..............................................................................5-101
DB2 Load Control Table—Source and Target Table Information........................5-102
Load Control Table—Column Mapping Information .........................................5-103
EXEC Statement PARM Field—DELTEnnn Step...................................................5-103
DD Statements—DELETE Step..............................................................................5-104
DD Statements—SORT Step..................................................................................5-104
EXEC Statement PARM Field—DELTEnnn Step...................................................5-104
DD Statements—LDSQLIN Step ...........................................................................5-105
DD Statements—VSAMCRTE Step........................................................................5-110
DD Statements—FILEDLTE Step...........................................................................5-110
DD Statements—FILEALLC Step...........................................................................5-110
EXEC Statement PARM Field——LDDRV Step.....................................................5-111
DD Statements—LDDRV Step ..............................................................................5-111
Load Control Table—Source and Target Object Information..............................5-112
Load Control Table—Field Mapping Information ...............................................5-113
EXEC Statement PARM Field——LDDRV Step.....................................................5-114
DD Statements—LDMVSIN Step ..........................................................................5-114
xxiv
File-AID/RDX Reference
5-37.
6-1.
6-2.
6-3.
6-4.
6-5.
6-6.
6-7.
6-8.
6-9.
7-1.
7-2.
7-3.
7-4.
8-1.
9-1.
B-1.
B-2.
DD Statements—SORT Step..................................................................................5-114
EXEC Statement PARM Field—DLDRV Step ..........................................................6-18
DD Statements—DLDRV Step ................................................................................6-18
Delete Control Table ..............................................................................................6-19
EXEC Statement PARM Field—Delete Step ............................................................6-19
EXEC Statement PARM Field—DLDRV Step ..........................................................6-24
DD Statements—LDDRV Step ................................................................................6-24
MVS Delete Control Table......................................................................................6-25
EXEC Statement PARM Field—DLMVS ..................................................................6-25
DD Statements—DLMVS Step ................................................................................6-25
Data Privacy Environment Parameter Overrides ...................................................7-13
Print Execution Return Codes ................................................................................7-71
EXEC Statement PARM Field—Disguise Extract Step (EXDISG) ............................7-74
DD Statements—Data Disguise ..............................................................................7-74
Object Override Identifiers .....................................................................................8-11
List of Panels supporting FIND command .............................................................. A-5
Example 1 Summary.................................................................................................B-3
Example 2 Summary.................................................................................................B-3
Introduction
xxv
Introduction
Intro
This is a detailed reference manual for users of File-AID/Related Data XPERT (FileAID/RDX). It provides the information necessary to take advantage of the features of FileAID/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:
• Chapter 1, “Overview” provides an overview of File-AID/RDX, including a brief
description of the product’s features and functionality.
• Chapter 2, “Profiles and Global Defaults” describes Option 0, Profile, and.Option G,
Global Defaults.
• Chapter 3, “Relationship Facilitator” describes Option 1, Relationship Facilitator, the
object-centric entry to relationship maintenance.
• Chapter 4, “Extract” describes Option 2, Extract.
• Chapter 5, “Load” describes Option 3, Load.
• Chapter 6, “Delete” describes Option 4, Delete.
• Chapter 7, “Data Privacy” describes Option 5, Data Privacy.
• Chapter 8, “File-AID/RDX Utilities” describes Option 6, File-AID/RDX Utilities.
• Chapter 9, “Tutorial and Online Help” describes Option T, Tutorial and Online Help,
and Option C, Changes.
In addition, the manual includes the following appendixes:
• Appendix A, “Command Summary” provides a summary of File-AID/RDX commands.
• Appendix B, “Extract Navigation Criteria Examples” provides different examples of
global navigation settings for File-AID/RDX’s extract.
• “Glossary” provides a summary of product-specific terms.
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.
xxvi
File-AID/RDX Reference
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
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
OPTIONAL-KEYWORD2
OPTIONAL-KEYWORD3
optional-var2
optional-var3
COMMAND
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
Introduction
xxvii
Related Publications
• File-AID/Related Data XPERT User Guide provides a self-study style, scenario-based
description of many of File-AID/RDX’s features and functions. It is intended for users
of File-AID/RDX.
• File-AID Single Install Image Installation and Configuration Guide provides a step-by-step
description of the process necessary to configure File-AID products, including FileAID/RDX. It is intended for database administrators and the systems group
responsible for File-AID/RDX at your installation.
• File-AID Quick Configuration Guide: Provides an abbreviated set of steps to quickly
configure File-AID products, including File-AID/RDX.
• 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/Related Data XPERT Release Notes provides a summary of the latest
enhancements to File-AID/RDX. It is intended for IS management and users of FileAID/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 Go
customer support website at http://go.compuware.com in the following electronic
formats:
•
•
•
•
Release Notes in HTML format
Product manuals in PDF format
Adobe PDF index file (PDX file)
Product manuals in HTML format.
The product documentation is available for viewing or downloading:
• View PDF files with the free Adobe Reader, available at http://www.adobe.com.
• View HTML files with any standard web browser.
Getting Help
At Compuware, we strive to make our products and documentation the best in the
industry. Feedback from our customers helps us to maintain our quality standards.
If problems arise, consult your manual or the File-AID/RDX customer support
representative at your site. If problems persist, please obtain the following information
before calling 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.
xxviii
File-AID/RDX Reference
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 provides a variety of support resources to make it easy for you to find the
information you need.
Compuware Go Customer Support Website
You can access online information for Compuware products via our Compuware Go
customer support website at http://go.compuware.com.
Compuware Go provides access to critical information about your Compuware products.
You can review frequently asked questions, read or download documentation, access
product fixes, or e-mail your questions or comments. The first time you access
Compuware Go, you are required to register and obtain a password. Registration is free.
Contacting Customer Support
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 http://go.compuware.com.
Web
You can report issues via the Quick Link Create & View Support Cases on the
Compuware Go home page.
Note:
Please report all high-priority issues by telephone.
Mail
Compuware Customer Support
Compuware Corporation
One Campus Martius
Detroit, MI 48226-5099
Corporate Website
To access Compuware’s site on the Web, go to http://www.compuware.com.
The Compuware site provides a variety of product and support information.
1-1
Chapter 1.
Overview
Chap 1
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.
Note:
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 FileAID/RDX by itself.
The File-AID/RDX Primary Option Menu shown in Figure 1-1 is the first screen displayed
when you invoke File-AID/RDX.
Note:
When DB2 is being used by another application in your current TSO session, FileAID/RDX issues a warning when connecting to DB2 (see “DB2 Call Attach Alert”
on page 1-15).
1-2
File-AID/RDX Reference
Figure 1-1. File-AID/RDX Primary Option Menu
File-AID/RDX 16.3 ------OPTION ===> 
0
1
2
3
4
5
6
G
FD
C
T
X
PROFILE
RELATIONSHIPS
EXTRACT
LOAD
DELETE
DATA PRIVACY
UTILITIES
GLOBAL DEFAULTS
FADB2
CHANGES
TUTORIAL
EXIT
-
Primary Option Menu
-------------------------------
USERID
TSOID01
Select, Create or Change Profile
TIME
14:15
Relationship Facilitator
TERMINAL 3278
Extract from Related Objects
PF KEYS 24
Load Data Records
Delete Extracted Rows from DB2 Tables and/or MVS Files
Data Privacy Menu
Utility Functions
Define User Parms
Transfer to File-AID for DB2
Summary of File-AID/Related Data XPERT changes
Information about File-AID/Related Data XPERT
Exit File-AID/Related Data XPERT

Profile ===> RDXMENU RDXMENU - DISPLAY ALL OF THE MENU OPTIONS
Type
===> SITE
(SITE, USER or prefix)

Copyright (c) 1994 - 2015 Compuware Corporation. All Rights Reserved.
Unpublished - rights reserved under the Copyright Laws of the United States.
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
1-2 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 2-2 on page 2-3).
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.
Note:
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.
• Create, view, delete, and edit conditional (data-driven) application relationships.
Overview
1-3
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 4-89) 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 FileAID/EX, formerly known as File-AID/CS, 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.
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.
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 FileAID/Data Solutions and, optionally, File-AID Data Privacy products.
These Disguise Utilities allow you to:
• Allocate Disguise Control File
• Allocate Disguise Criteria File
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.
1-4
File-AID/RDX Reference
• 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
Command or Option prompt
Short Message or DB2 Subsystem ID
Scroll amount or DB2 Subsystem prompt
Long Message
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
Overview
1-5
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 4-99 for a list of valid
operators)
’(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 <'
1-6
File-AID/RDX Reference
where,
=
any valid operator (see “Where” on page 4-99 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 1-2 is an example of an Option Selection screen.
Figure 1-2. Option Selection Screen Example
File-AID/RDX 16.3 ------OPTION ===> 
0
1
2
3
4
5
6
G
FD
C
T
X

PROFILE
RELATIONSHIPS
EXTRACT
LOAD
DELETE
DATA PRIVACY
UTILITIES
GLOBAL DEFAULTS
FADB2
CHANGES
TUTORIAL
EXIT
-
Primary Option Menu
-------------------------------
USERID
TSOID01
Select, Create or Change Profile
TIME
14:15
Relationship Facilitator
TERMINAL 3278
Extract from Related Objects
PF KEYS 24
Load Data Records
Delete Extracted Rows from DB2 Tables and/or MVS Files
Data Privacy Menu
Utility Functions
Define User Parms
Transfer to File-AID for DB2
Summary of File-AID/Related Data XPERT changes
Information about File-AID/Related Data XPERT
Exit File-AID/Related Data XPERT

Profile ===> RDXMENU RDXMENU - DISPLAY ALL OF THE MENU OPTIONS
Type
===> SITE
(SITE, USER or prefix)

Copyright (c) 1994 - 2015 Compuware Corporation. All Rights Reserved.
Unpublished - rights reserved under the Copyright Laws of the United States.
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 1-3 is an
example of an Option Information screen.
Overview
1-7
Figure 1-3. Option Information Screen Example
File-AID/RDX --------Option ===>
DB2 Relationship Facilitator
------------------------
Scroll ===> CSR 
SITE Profile: RDXMENU
Primary commands: menu-option, MVS Relationship Facilitator
1
2
3
4
5
6
A
L
P
BROWSE ALL
EDIT AR
ADD AR
LIST RDX
LOAD RI
LIST DB2
ALLOCATE
BATCH RI LOAD
PRINT
-
Browse all existing Relationships
Edit existing Apllication Relationships
Add new Application Relationships
List DB2 objects from RDX Relationship File
Load RI Relationships from DB2 Catalog tables
List DB2 objects from DB2 Catalog
Allocate Relationship File
Batch Job to Load RI Relationships
Print the Relationship File
Specify a Table Name or pattern:
SSID
===> DSN
Location
===>
Creator
===> TSOID01
Table Name
===> ORD*
(*
(*
(*
(*
or
or
or
or
pattern
pattern
pattern
pattern
for
for
for
for
selection
selection
selection
selection













list)
list)
list)
list)

See “DB2 Relationship Facilitator” on page 3-5 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 1-4 is an example of a
scrollable data display.
Figure 1-4. Scrollable Data Screen Example



File-AID/RDX
COMMAND ===>
Relationship Detail
Relationships for:
LOCATION.FRSAMP.ORDER_TABLE
Line Commands: S - Select Relationship to Modify
A - Add Application Relationship
Row 1 to 6 of 6
SCROLL ===> CSR
D - Delete Relationship
I - Relationship Information
Obj Rel
CMD
Parent/Dependent
Type Type
Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.FRSAMP.CUSTOMER_TABLE
DB2 AR
LOCATION.FRSAMP.ORDER_TABLE
DB2
_ LOCATION.FRSAMP.ORDER_TABLE
DB2 RI
LOCATION.FRSAMP.ORDER_LINE_TABLE
DB2
ORDLORD
_ LOCATION.FRSAMP.CUSTOMER_TABLE
DB2 RI
ASSOCIATED REL.
LOCATION.FRSAMP.CONTACT_TABLE
DB2
CONTCUST
_ LOCATION.FRSAMP.PART_TABLE
DB2 RI
ASSOCIATED REL.
LOCATION.FRSAMP.ORDER_LINE_TABLE
DB2
ORDLPRT
_ LOCATION.FRSAMP.PART_TABLE
DB2 RI
ASSOCIATED REL.
LOCATION.FRSAMP.SUPPLIER_TABLE
DB2
SUPPPART
******************************* Bottom of data *************************
See “Relationship Detail” on page 3-15 for a description of this screen example.
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.
1-8
File-AID/RDX Reference
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 1-5 is an example of a selection pop-up
window.
Figure 1-5. Selection Pop-Up Window Example
File-AID/RDX ------------OPTION ===>
Primary Comma
Specify table
SSID
Location
Creator
Table Name
Relationship
File name o

DB2 Driving Object
-------------------------------

Table List - SYSIBM.SYSTABLES 
Row 1 to 8 of 238 
COMMAND ===>
SCROLL ===> CSR


Enter 'S' to select table name


CMD Location
Creator
Table Name
Type

--- ---------------- -------- ------------------- ----
_
LOCATION
FADBTST
ACT
TABLE

_
LOCATION
FADBTST
ADEPT
ALIAS

_
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 1-6 is an example of an
information display screen.
Figure 1-6. Information Display Screen Example
File-AID/RDX
COMMAND ===>
Parent Name:
Relationship Information
LOCATION.FRSAMP.ORDER_TABLE
Dependent Name: LOCATION.FRSAMP.ORDER_LINE_TABLE
DB2 Row 1 to 2 of 2
SCROLL
===> CSR
Type: DB2
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 ***
See “Relationship Information Screen” on page 3-20 for a description of this screen
example.





















Overview
1-9
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
LEFT
RIGHT
n
CSR
CUR
C
DATA
D
HALF
H
PAGE
P
Valid scroll amounts are:
Table 1-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
CSR
Scroll such that the line on which the cursor is positioned moves to the top or
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.
1-10
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 1-7, the long name indicator
“+++>” for Table Name alerts that EMP_GENERATED_TIMESTAMP_HIDD is longer than
displayed EMP_GENERATED_TIMEST.
Figure 1-7. Long Name Indicator Example
File-AID/RDX
Command ===>
Specify Parent DB2
Location
===>
Creator
===>
Table Name
+++>
---
Add Application Relationships
-------------------------


Table for Relationship Definition:

DSNLOCAT

FRSAMP
(* or pattern for selection list)

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
1-8 and Figure 1-9 for an example).
Use the KEYS command to set the EXPAND command to a PF key (see also “Assign PF
Keys”).
Overview
1-11
Figure 1-8. EXPAND Command in Scrollable Field


File-AID/RDX --------------Command ===> EXPAND
DB2 Object List
Line Commands: A = Add Application Relationship
E = Edit Application Relationship
-------------- Row 1 to 2 of 2
SCROLL ===> CSR
B = Browse 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 1-9. EXPANDed Field
File-AID/RDX
---------------
DB2 Object List
FRQSNAME+0 
-------------- Row 1 to 2 of 2
4 


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 ===>
Line
1 of
Scroll ===> CSR
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 1-12 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 A, “Command Summary”. Commands are described in detail in the
appropriate chapters.
1-12
File-AID/RDX Reference
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 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 1-12).
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 1-2 shows the default key lists for File-AID/RDX:
Table 1-2.
Default Key Lists for File-AID/RDX
PF Key
F2CMDS3
F2CMDS3B F2CMDS8A RDXDFLT1
PF1/13
HELP
HELP
HELP
RDXHELP
HELP/EXPAND HELP
RDXPARMS
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
Overview
Table 1-2.
1-13
Default Key Lists for File-AID/RDX (Continued)
PF Key
F2CMDS3
F2CMDS3B F2CMDS8A RDXDFLT1
RDXHELP
RDXPARMS
PF10/22
LEFT
PREV
LEFT
BACK/PREV
PREV/LEFT
LEFT
PF11/23
RIGHT
NEXT
RIGHT
RIGHT
NEXT
NEXT/RIGHT
PF12/24
RETRIEVE
RETRIEVE
RETRIEVE
CANCEL
RETRIEVE
RETRIEVE/ZCLRSFLD
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 FileAID/RDX. That is, if you edit your PC settings file and change the dimensions to some
nonstandard setting, File-AID/RDX screen displays may fail.
If you use a nonstandard setting and you are not concerned about it causing occasional
screen display failures, Compuware recommends to select choice "3. Max" under ISPF
Option 0 - Settings, Terminal Characteristics - Screen format. That is an IBM ISPF setting,
not a File-AID/RDX setting. It controls IBM ISPF screen handling. Choosing Screen
format 3.Max tends to give best results for working with the broadest range of screen
dimensions. Note again that File-AID/RDX only supports the standard dimensions of
standard IBM terminal types.
1-14
File-AID/RDX Reference
DB2 Subsystem ID Selection
The Subsystem ID Selection window shown in Figure 1-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 1-10. Subsystem ID Selection Window
File-AID/RDX ------------Option ===>
Primary Commands: MVS
Specify table to driv
SSID
==
Location
==
Creator
==
Table Name
==
Relationship Informat
File name or patter
DB2 Driving Object
------------------------------
Subsystem ID Selection
Row 1 from 4
Command ===>
Enter 'S' to select SSID
Cmd SSID
--- ---_
DSNF
_
DSNH
_
DSNI
_
DSNJ
****** Bottom
DB2 Version
----------1010
1010
1110
1110
of data *******
rn for selection list)
rn for selection list)
rn for selection list)



















This window includes a selection list of all subsystems that have been defined for your
site during File-AID/RDX’s installation.
Note:
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.
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.
Overview
1-15
DB2 Call Attach Alert
The DB2 Call Attach Alert window shown in Figure 1-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 1-11. DB2 Call Attach Alert
File-AID/RDX ------------Option ===>
DB2 Driving Object
-------------------------------
DB2 Call Attach Alert



Primary Commands
Command ===>
Specify table to
SSID
Location
Creator
Table Name
Relationship Inf
File name or p
Another DB2 application is currently active
within this TSO session.
ection list)
ection list)
ection list)
You may experience DB2 Call Attach problems
if these applications attempt to allocate
different levels of the DB2 load libraries.
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.
1-16
File-AID/RDX Reference
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”.
Relationship File
The relationship file contains information about relationship definitions that FileAID/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 3-82).
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
Overview
1-17
and can be updated with the File-AID/RDX “Batch RI Load” utility. See “Batch RI
Load” on page 3-83 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 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 1-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
CHAR
52
Object name. Fully qualified name of the object; for DB2
objects, for example, it consists of location.creator.object.
Obj-nm-DB2 Sync
GRP
52
Redefines the object name to fit DB2 naming
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
GRP
52
Redefines the object name to fit MVS naming
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
1-18
File-AID/RDX Reference
Table 1-3.
Key Fields (Continued)
Field Name
Type
Length
Description
DBD-Member
CHAR
8
Member name
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 1-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
CHAR
52
Related Object name. Fully qualified name of the object; for
DB2 objects, for example, it consists of
location.creator.object.
Rel-Obj-SEQ-NO
Binary
4
Unique number to identify specific relationship for the
related object
Version-stamp
Sync
GRP
18
Information about the product that created this entry.
product_id
CHAR
2
ID of the product that created this entry.
product_rel
CHAR
8
Version, release, and modification level of the product that
created this entry.
Func-release
CHAR
8
Relationship release used to update this entry.
Rel-type
CHAR
2
Relationship type
RI : Referential Integrity
AR : Application Relationship
Depend-fullname-offset
PIC
S9999
Offset for dependent full name (long object names only)
Parent-full-name- PIC
offset
S9999
Offset for parent full name (long object names only)
Long-name-text
X(550)
Full object name (long object names only) for parent and
dependent DB2 long name objects. Includes: total length,
object type, location name length, location name, creator
name length, creator name, table name length, table
name.
PIC
Relationship Details (parent objects only)
The following fields provide information about the Relationship Details and is only
included for parent objects.
Table 1-5.
Relationship Details (parent objects only)
Field Name
Type
Length
rel-description
CHAR
30
Description
Description of the relationship. For RI relationships, this is the
RELNAME from the DB2 catalog. For AR relationships, this is
the description entered on the Column Relationships screen.
Overview
Table 1-5.
1-19
Relationship Details (parent objects only) (Continued)
Field Name
Type
Length
Description
Parent-delim-ind
CHAR
1
Parent delimiter indicator.
0 : No delimiter required
1 : Delimiter required for Table
2 : Delimiter required for Creator
3 : 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-ind
CHAR
1
Dependent delimiter indicator. See Parent delimiter
indicator for explanation of possible values.
Audit-info Sync
GRP
68
Timestamp and User ID for creation and modification of the
relationship
Load-tmstmp
CHAR
26
Timestamp indicating when the relationship was created or
loaded into the relationship file. The timestamp is written in
the following format: YYYY-MM-DD-HH.MM.SS.NNNNNN
Load-userid
CHAR
8
Userid that created or loaded the relationship.
Mod_tmstmp
CHAR
26
Timestamp indicating when the relationship was last
modified. The timestamp is written in the following format:
YYYY-MM-DD-HH.MM.SS.NNNNNN
Mod_userid
CHAR
8
Userid that last modified the relationship.
Rel-data-DB2 Sync
GRP
14
Database information for the relationship
DBMS-info-parent
Sync
GRP
7
Database information for the parent
DBMS-VRM
CHAR
3
DBMS version
DBMS-SubsysID
CHAR
4
DBMS subsystem ID
DBMS-info-child
Sync
GRP
7
Database information for the dependent
DBMS-VRM
CHAR
3
DBMS version
DBMS-SubsysID
CHAR
4
DBMS subsystem ID
Filler
CHAR
4
Filler
Parent-full-nameoffset
PIC
S9999
Offset for parent full name (long names only)
Depend-full-name- PIC
offset
S9999
Offset for dependent full name (long names only)
Column-source
Sync
GRP
112
Number-cols
Binary
Column-detail (1)
Sync
GRP
110
Parent and child column/field detail information; occurs 1 to
38 times 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
2
Parent and child column/field information
Number of related columns.
1-20
File-AID/RDX Reference
Table 1-5.
Relationship Details (parent objects only) (Continued)
Field Name
Type
Length
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
PIC
X(550)
Description
Full object name (long object names only) for parent and
dependent DB2 long name objects. Includes: total length,
object type, location name 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 1-6.
MVS Record Layout Information
Field Name
Type
Rel-data-file Sync GRP
Length Description
294
2
MVS Record Layout Information; (only applicable if one or both
objects of the relationship are MVS object types)
Num-layouts
Binary
Layout-info (1)
Sync
GRP
Layout-type
CHAR
1
Layout type
S : 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
146
Number of MVS layouts defined in the relationship
Layout information for MVS object in the relationship; occurs 0
to 2 times depending on the number of MVS objects defined in
the relationship.
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).
Overview
1-21
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 3-83 for more information. In addition, you can load select RI
relationships using the online Load RI option (see “5 - Load RI” on page 3-6) or the L
(Load RI) line command (see “L” on page 3-8) in the Relationship Facilitator.
Appendix G, “Refreshing Relationship File from an Outside Source” in the File-AID Single
Install Image Installation and 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” periodically to refresh the file with referential integrity information from the DB2
catalog (see also “L- Batch RI Load” on page 3-6).
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, FileAID/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 3-9 on page 3-15).
Visualizer
The Visualizer plugin for 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 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
1-22
File-AID/RDX Reference
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 4-11 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 3-56.
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 3-56).
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
Note:
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, FileAID/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 4-132).
See “File-AID/RDX Extract/Load/Delete Request File” on page 4-144 for more information
about how File-AID/RDX uses this file and how it is structured.
Overview
1-23
Visualizer
The Visualizer plugin for 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 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)
Notes:
a. 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).
b. 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 Chapter 4, “Extract” for more information about how File-AID/RDX uses this file. See
“File-AID/RDX Extract File” on page 4-154 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 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.
Note:
When creating the intermediary file, the routine changes the last character of the
file name to a letter between J and R, for example, FRSAMP.EXTRACT to
FRSAMP.EXTRACK. If these files already exist, File-AID/RDX will not create the
intermediary file and the dynamic reallocation will fail.
1-24
File-AID/RDX Reference
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 4-124, Chapter 5, “Load” or “DCF:
Disguise Existing Extract” on page 7-55 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 Chapter 5, “Load” and Chapter 6,
“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 4-154.
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).
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”
Overview
1-25
(see Figure 2-1 on page 2-1) 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
7-9).
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 Chapter 7, “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
7-9).
CAUTION:
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)
Logical record length
300 (LRECL=300)
Minimum block size
304 (BLKSIZE=304)
See Chapter 7, “Data Privacy” for more information about how File-AID/RDX uses this
file.
Audit Trail File
Audit Trail files are created when Auditing is requested during the disguise operation. A
separate Audit Trail file will be produced for each object being disguised.
The naming convention used for the Audit Trail files is:
prefix.RDXA.DnnnBnnn.Dyymmdd.Thhmmss.Msss
1-26
File-AID/RDX Reference
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 7-9) 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 8-1).
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 8-9 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 8-1).
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)
See “JCL/Overrides Utility” on page 8-9 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 8-1).
Overview
1-27
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 8-9 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 1-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 1-12. File-AID for DB2 Primary Option Menu

File-AID for DB2 - 16.3 ------ 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 - DBA-XPERT 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 - 2015 Compuware Corporation. All Rights Reserved.

Online Technical Support available at: http://go.compuware.com.

Type LEGAL on the command line for Copyright/Trade Secret Notice.

Unpublished - rights reserved under the Copyright Laws of the United States.
1-28
File-AID/RDX Reference
2-1
Chapter 2.
Profiles and Global Defaults
Chap 2
The File-AID/RDX main menu displays the current user or site profile for your FileAID/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 2-26.
Option 0—Profile
The “RDX Profile Screen” shown in Figure 2-1 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 2-1. RDX Profile Screen
File-AID/RDX --------------Option ===>
RDX Profile
------------------- Profile
Primary commands: menu-number, ALL, CANCEL

Line commands: S or / to create flow through selected options.
Active Profile
Profile Type ===>
Name
===>
Description
===>
Profile Dataset :
_
_
_
_
_
_
1
2
3
4
5
6
loaded 


SITE
(SITE, USER or prefix)
RDXFLOW
(* or blank for list)
RDXFLOW - FLOW THROUGH THE MENU OPTIONS
FARDX.SITE.PROFILE
Batch defaults
Extract Defaults
Load Defaults
Disguise Defaults
Permanent File
Temporary File
-
Modify session and batch defaults
Modify extract parameter defaults
Modify load and delete parameter defaults
Modify Data Disguise parameter defaults
Specify permanent file defaults
Specify temporary file defaults


















Active profile
Profile Type : Specify which profile file to open. If the specified profile doesn’t exit, FileAID/RDX attempts to create the profile file.
SITE identifies the installation wide profile file.
USER Enter USER to select your own profile file (your userid.mlq.PROFILE, see also
“Profile Dataset”). The TYPE field then displays your userid.
prefix identifies a profile file with the specified high level qualifier (up to 26
positions) (see also “Profile Dataset”). Entering a prefix that includes the string
&USERID will substitute the current userid when the profile file is allocated. The prefix
2-2
File-AID/RDX Reference
must not include the midlevel qualifier.
Example: prefix FDM.&USERID allocates FDM.userid.RDX.PROFILE.
The TYPE field, however, continues to display &USERID.
Name : Specify the profile name (member name in the profile file). Enter an asterisk (*)
or leave blank to display a list.
Description : Enter text that provides a concise description of the profile’s content or
purpose.
Profile Dataset : Displays the full name of the physical profile dataset (PDSE) including
the prefix and midlevel qualifier (mlq) for the profile. The midlevel qualifier (product
parameter variable RDXPMDQL) is specified during configuration of File-AID/RDX.
Enter the option number (1 - 6) to select the desired option or enter ALL to step through
all options in sequence. Alternatively, you may also select one or more options with the S
or / line command.
1 - Batch Defaults : Displays the “Session and Batch Defaults” screen where you can set
batch job parameters and job statements for the current profile.
2 - Extract Defaults : Displays the “Extract Defaults” screen where you can set all the
extract related defaults for the current profile.
3 - Load Defaults : Displays the “Load Defaults” screen where you can set all the load
related defaults for the current profile.
4 - Disguise Defaults : Displays the “Disguise Defaults” screen where you can set all the
data disguise related defaults for the current profile.
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.
Note:
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 2-2 is displayed when you entered an asterisk
(*) or blanked out the profile field of the “File-AID/RDX Primary Option Menu” (Figure 11) or the “RDX Profile Screen” (Figure 2-1). Use this screen to select the current profile as
well as copy, rename or delete site or user profiles.
Profiles and Global Defaults
2-3
Figure 2-2. Select Profile Screen

File-AID/RDX --------------- Select Profile ------------------ Row 1 to 3 of 3 
Command ===>
Scroll ===> CSR 

Type
===> SITE
(SITE, USER or prefix)
Dataset . .: FARDX.SITE.PROFILE 

Line commands - Enter S = Select, R = Rename, C to Copy, D to Delete

- Profile - New Name - Description --------------------------------------------
_ RDXFLOW
RDXFLOW - FLOW THROUGH THE MENU OPTIONS

S RDXMENU
RDXMENU - DISPLAY ALL OF THE MENU OPTIONS

_ RDXQUICK
RDXQUICK - THE QUICKER SETTER UPPER

******************************* Bottom of data ********************************

Specify profile information to display
Type : Specify in which profile file to look for the profile member(s) to display. If the
specified profile doesn’t exit, File-AID/RDX attempts to create the profile file.
SITE identifies the installation wide profile file.
USER identifies your own profile file (your userid). When you enter USER your userid
displays to indicate your USER profile type.
prefix identifies a profile file with the specified high level qualifier (up to 26
positions). Entering a prefix that includes the string &USERID will substitute the
current userid when the profile file is allocated. The prefix must not include the
midlevel qualifier.
Example: prefix FDM.&USERID allocates FDM.userid.RDX.PROFILE
Dataset : Displays the full name of the physical profile dataset including the prefix and
midlevel qualifier for the profile. The midlevel qualifier (product parameter variable
RDXPMDQL) is specified during configuration of File-AID/RDX.
Profile List Area
line command : Enter line command in the first column of the list area. See “Line
Commands” for valid line commands.
Profile : Lists the profile name (member name in the SITE or USER profile file).
New Name : Space to specify the new profile name when renaming (R line command) or
copying (C line command) the profile.
Description : Text can be used to provide a more detailed description of the profile’s
content or purpose. Description can be entered when copying or renaming a profile.
Line Commands
C : Copy the profile. If you leave NEW NAME column blank, the “Copy Profile window”
(Figure 2-3) displays where you can specify the new profile name (member name) and
profile type, USER, SITE, or prefix.
Note:
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”.
2-4
File-AID/RDX Reference
Figure 2-3. Copy Profile window

File-AID/RDX --------------- Select Profile ------------------ Row 1 to 3 of 3 
Command ===>
Scroll ===> CSR 

Type
===> SITE
(SITE, USER or prefix)
Dataset . .: FARDX.SITE.PROFILE 

Copy Profile 
COMMAND ===>
Copy profile RDXMENU
Specify new profile information:
Profile type ===> SITE
(SITE, USER or prefix)
Name
===>
Description ===> RDXMENU - DISPLAY ALL OF THE MENU OPTIONS
Press ENTER to process, CANCEL or END to return













R : Rename the profile. Type the new profile name in the NEW NAME column. If you
don’t enter a name in the NEW NAME column, the “Rename Profile window” (Figure
2-4) allows you to enter a new name and also to modify the old profile description in
the Description field.
Figure 2-4. Rename Profile window

File-AID/RDX --------------- Select Profile ------------------ Row 1 to 3 of 3 
Command ===>
Scroll ===> CSR 

Type
===> SITE
(SITE, USER or prefix)
Dataset . .: FARDX.SITE.PROFILE 

Rename Profile 
COMMAND ===>
Rename profile RDXMENU
Profile type ===> SITE
(SITE, USER or prefix)
Name
===>
Description ===> RDXMENU - DISPLAY ALL OF THE MENU OPTIONS
Press ENTER to process, CANCEL or END to return










S : Select the profile (member name in the profile file) to be the current profile. FileAID/RDX automatically saves the current profile when selecting another profile.
D : Delete the profile (member name) from the profile file.
Profiles and Global Defaults
2-5
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.
Note:
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.
2-6
File-AID/RDX Reference
Session and Batch Defaults
The “Session and Batch Defaults” screen shown in Figure 2-5 is displayed when you select
Option 1 from the “RDX Profile Screen”. Use this screen to specify the batch defaults for
the current profile.
Figure 2-5. 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 AbendAID 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
4-170.
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.
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 2-26.
Note:
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 2-18, option 2, DPR.
Profiles and Global Defaults
2-7
Extract Defaults
The Extract Defaults screen shown in Figure 2-6 on page 2-8 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.
2-8
File-AID/RDX Reference
Figure 2-6. Extract Defaults - Scrollable Screen
File-AID/RDX ---------------Command ===>




Extract Defaults
-----------------------------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
Maximum rows/records
from all objects
Action at maximum count
Extract w/ Uncommitted Reads
===> 1
(* for no limit)
===> *
===> Q
===> N
(* for no limit)
(Q = Quiesce, S = Stop)
(Y = Yes; N = No) 
===> N
===> N
===> N
(Y = Yes; N = No)
(Y = Yes; N = No) 
(Y = Yes; N = No) 
Create File-AID/MVS XREF
Create record layouts 
for DB2 objects
Language
===> N
(Y = Yes; N = No) 
===> N
===> 1
(Y = Yes; N = No) 
(1 = COBOL, 2 = PL/I)
Use DB2 Image Copy
DB2 Format
===> N
===> 2
(Y = Yes; N = No) 
(1 = Unicode;

2 = Compatibility;

convert Unicode; 
File Options:
Capture View DDL
Capture Alias DDL
Capture Synonym DDL













---------------------------- 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 - Continue with Load
===> SHOW

11 - Save Extract Request
===> SHOW

12 - View JCL/View REXX
===> SHOW

13 - Submit JCL/Execute REXX
===> SHOW 
Profiles and Global Defaults
2-9
All Extract Request Defaults Area
Extract Scope Options Area
Specify the Navigational Criteria Options associated with the current profile. See
“Extract Scope” on page 4-49 for detailed information.
Direct : Specify to extract the dependents (children) of the driving object and their
dependents.
Y : Extract the dependents of the driving object and their dependents (default).
N : Do NOT extract the dependents of the driving object and their dependents.
C : (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.
P : (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.
Note:
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 4-49 for detailed
information.
Default Detail View : Specify which detail extract scope view is displayed when you
enter the Extract Scope display:
N : None does not display either of the detail extract scope panels.
O : Object displays the Extract Scope - Object View panel, listing all objects related
to the driving object from which to extract data.
R : 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 4-49 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.
2-10
File-AID/RDX Reference
Action at Maximum Count : Specify how the extract should terminate when the
maximum count has been reached:
Q : Quiesce resolves all orphan records after maximum count has been reached.
(May result in more records than the maximum count.)
S : 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.
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. FileAID/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 4-168 for detailed
information.
Create Record Layouts for DB2 objects : Specify whether or not to create a COBOL or
PL/I record layout file when File-AID/RDX performs the extract. See also “FileAID/RDX Record Layout File” on page 4-166 for detailed information.
Language : Specify whether the record layout will be in COBOL (1) or PL/I (2) format.
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 UIMGCPY to Yes. Refer to “UIMGCPY” in the File-AID Single
Install Image Installation and 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.
1 : Unicode option will write the data using Unicode encoding without utilizing IBM
z/OS Conversion Services.
2 : 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.
Note:
DB2 utilities do NOT support enclosing lowercase creator IDs with quotes.
Profiles and Global Defaults
2-11
DB2 Environment Area
DB2 Subsystem : Specify the DB2 subsystem ID for the DB2 objects to be extracted using
this profile.
Location : Specify the location of the object you want to drive the extract if it resides in
a remote DB2 subsystem. The location you enter must be defined in the DB2 system
catalog table, SYSIBM.LOCATIONS.
You may leave this field blank if the table you want to drive the extract is in the DB2
subsystem in the DB2 Subsystem field.
Creator : Specify the authorization ID of the owner of the table, view, synonym, or alias
that you want to drive the extract process using this profile.
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 FileAID/RDX supports view, aliases, and synonyms in Extract, see “Use of DB2 Views” on
page 4-29 and “Use of Aliases and Synonyms” on page 4-29.
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.
R : Reference List (default)
F : Request File
S : 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:
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.
2-12
File-AID/RDX Reference
Load Defaults
The Load Defaults screen shown in Figure 2-7 on page 2-13 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.
Profiles and Global Defaults
2-13
Figure 2-7. Load Defaults - Scrollable Screen
File-AID/RDX ----------------Command ===>

Load Defaults
--------------------------------
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

Auto Create Defaults for DB2 Objects: 
Database
===>

Tablespace
===>
Implicit Tablespace
===> N
STOGROUP
===> 
Primary Quantity(K)
===> 20 
Secondary Quantity(K)
===> 15 
Freepage
===> 10
Pctfree
===> 10 
Buffer Pool
===> BP0
Space recalculation
===> N

....................Defaults for Load Method
Existing Data Options:
Delete all rows
===> N
Replace matches
===> Y


(DB2 OR SQL)
(Y = Yes; N = No)
(Y = Yes; N = No)



= SQL Insert .....................

(Y = Yes; N = No)

(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)

--------------------------- 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

2-14
File-AID/RDX Reference
DB2 Data Defaults
Target DB2 Environment Area
Default SQLID : Specify the DB2 SQLID to be used during load and delete processing
using this profile. If blank, SQLID defaults to USER.
SSID : Specify the DB2 subsystem ID of the target DB2 objects to be loaded using this
profile.
Location : Specify the location of the target objects you want to load if they reside in a
remote DB2 subsystem. The location you enter must be defined in the DB2 system
catalog table, SYSIBM.LOCATIONS.
You may leave this field blank if the DB2 objects you want to load reside in the DB2
subsystem you specified in the SSID field.
Creator : Specify the authorization ID of the owner of the target DB2 objects that you
want to load using this profile.
Index name prefix value : Specify the default prefix to be added to the index names in
the target environment. Leave blank if you don’t want to specify a default prefix.
Index name suffix value : Specify the default suffix to be added to the index names in
the target environment. Leave blank if you don’t want to specify a default suffix.
If an index were named XDEPT1, adding a prefix of T would make the new index
name T_XDEPT1, adding a suffix of T would make it XDEPT1_T, adding both prefix
and suffix would make it T_XDEPT1_T.
DB2 Load Method : Specify whether you want to load DB2 data using SQL INSERT
statements or the IBM DB2 Batch Load Utility. See also “SQL Insert and DB2 Load
Utility Load Options” on page 5-15.
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.
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.
Note:
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 5-46.
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.
Profiles and Global Defaults
2-15
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.
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.
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.
1 : Log DB2 logging will occur during the load process.
2-16
File-AID/RDX Reference
2 : 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.
3 : 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.
4 : 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.
File name suffix value : Specify the default file name suffix to be added when creating
MVS objects in the target environment, e.g. FRSAMP.ORDERTAB becomes
FRSAMP.ORDERTAB.NEW.
Space recalculation : Specify YES if you want File-AID/RDX to calculate the space
allocation for the new target file based on the extracted data. The calculated space
will not exceed the space allocation of the source.
When set to NO the MVS file allocation parameters for the new object will be the
same as for the source file.
Storage Class : Specify the default storage class for the target files.
Management Class : Specify the default management class for the target files.
Existing Data Options for MVS Objects Area
Delete/Define : Specify whether or not File-AID/RDX should delete the target file and
then redefine it before it loads data from the extract file.
Yes : File-AID/RDX generates a step in the JCL to delete the object and then create it
again before loading data.
No : Appends data to the existing target object.
Replace Matches : When you are adding data to an object that is not empty and the
INSERT operation fails because the row or record already exists, specify whether or
not it should be replaced. Only applies if the target object is indexed.
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.
R : Recently Referenced List (default)
Profiles and Global Defaults
2-17
F : 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.
Disguise Defaults
The Disguise Defaults screen shown in Figure 2-8 on page 2-17 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 2-8. 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)

2-18
File-AID/RDX Reference
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.
1 : Use DCF. Disguise the extracted data using a disguise control file (DCF). This
option requires installation of Compuware’s File-AID/Data Solutions.
2 : Use DPR. Disguise the extracted data using a Dynamic Privacy Rules Project
(DPR). This option requires installation of Compuware’s File-AID/Data Solutions
and the File-AID Data Privacy component of the Topaz Workbench.
3 : No Disguise. The extracted data will not be disguised.
Note:
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 2-6.
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 7-59 for more information.
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 7-9) to allocate it. Refer to
“Disguise Control File” on page 1-25 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 1-25 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
Profiles and Global Defaults
2-19
File” on page 2-18). 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 2-19).
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 2-27). 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 7-11 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 2-20).
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.
First Disguise panel : Specify which panel displays first when selecting Option 5 Data
Disguise from the File-AID/RDX Primary Option Menu.
R : Recently Referenced List
F : Saved Request File
S : 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 2-8 on page 2-17) or the “Global User Defaults Screen” (Figure 2-13 on
page 2-26). Select the desired repository name and press <Enter> .
Figure 2-9 shows the “Privacy Repository List Screen”.
Figure 2-9. 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 **************************
2-20
File-AID/RDX Reference
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 2-10 shows the “Privacy Project List Screen”.
Figure 2-10. 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.
Profiles and Global Defaults
2-21
Permanent File Defaults
The Permanent File Defaults screen shown in Figure 2-11 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.
Figure 2-11. Permanent File Defaults - Scrollable Screen
File-AID/RDX
COMMAND ===>

Permanent Dataset Defaults

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 1-16 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 1-23 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 1-24 and “Specify Extract “TO” File Information” on page 4-124 for more
information.
2-22
File-AID/RDX Reference
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 4-89 for more information.
Output Key file : Specify the name of the default File-AID/RDX Output Key file to be
used for this profile. File-AID/RDX will copy the extracted key values for the selected
KEY relation into the Output key file. This Output Key file can be used as the Input
Key file for another extract or other process of your choosing.If the relationship is to
an IMS segment, the resulting key file can then be used by File-AID for IMS to extract
the related IMS data. Refer to “Output Key Files” on page 4-118 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 3-12
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 4-39 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 5-75
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 8-10
for more information.
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 8-10 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 8-10 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.
Profiles and Global Defaults
2-23
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.
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
Note:
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 FileAID/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.
2-24
File-AID/RDX Reference
Temporary File Defaults
The Temporary File Defaults screen shown in Figure 2-12 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:

userid.prefix.XXXXXXXX.Dnnnnnn.Tnnnnnn.suffix

where XXXXXXXX is a constant indicating the type of the temporary file, for example,
SPLIT001 or FBCNTL .
Figure 2-12. Temporary File Defaults Screen
File-AID/RDX -----------COMMAND ===>

Temporary File Defaults
---------------------------
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)

Temp Work File Allocation:
Space Units
Primary Quantity
Secondary Quantity
===> CYL
===> 1
===> 1
(BLK, TRK, or CYL)
Chase Key File Allocation:
Space Units
Primary Quantity
Secondary Quantity
===> CYL
===> 1
===> 1
(BLK, TRK, or CYL)










Temporary file allocations Area
UNIT : Specify the default unit for the temporary files. File-AID/RDX will verify that the
unit specified is a valid generic unit (for example, SYSDA) on the LPAR where you are
currently logged on.
Storage Class : Specify the default storage class for the temporary files.
Management Class : Specify the default management class for the temporary files.
File Prefix : Specify the default file prefix for all temporary files for this profile. This is
the prefix used for files that must be allocated for batch functions. File-AID/RDX will
prefix temporary files with userid.prefix. To prefix a file without a userid, place one
double quote as the first character of the pattern. For example, “RDX will prefix a
temporary file with RDX. only. If the resulting file name exceeds 44 characters, the
specified prefix will be truncated to fit the maximum name length.
Entering the string &USERID will substitute the current userid at the time a
temporary file is allocated. For example, “RDX.&USERID will generate temporary
files beginning with RDX, followed by the current userid, followed by the rest of the
generated dataset name.
The default of userid.RDX can be changed during product configuration with product
option variable “FTPREFIX” (refer to “FTPREFIX” in the File-AID Single Install Image
Installation and Configuration Guide)
Profiles and Global Defaults
2-25
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. FileAID/RDX will append this suffix to the names of generated file names for batch jobs.
The default value can be changed during product configuration with product option
variable “FTSUFFIX” (refer to “FTSUFFIX” in the File-AID Single Install Image Installation
and Configuration Guide)
Note:
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.
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.
Note:
If your extract exceeds the size of these temporary file allocations (B37 abend)
change the allocation parameters here and repeat the extract (see Chapter 4,
“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 variable “EXTADDR” in the File-AID Single
Install Image Installation and Configuration Guide.
2-26
File-AID/RDX Reference
Option G—Global User Defaults
The Global User Defaults screen shown in Figure 2-13 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 2-13. Global User Defaults Screen
File-AID/RDX -------------Command ===>





Global User Defaults
----------------------------
FA/RDX Version: 16.3.0 

Reference List controls:
Extract reference list entries
Load reference list entries
===> 50
===> 50
Maximum Number of entries
Maximum Number of entries
Increment job name
Delete in-stream data datasets at EOJ
===> N
===> N
(Y = Yes; N = No)
(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.
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 4-20.
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 5-2 and “Delete Reference List” on page 6-2.
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 4-138, page 5-77 and page 6-14, as well as
“CLEANCTL—File Cleanup (IEFBR14) - Optional”on page 5-82, page 5-95, page
5-106, page 6-15, and page 6-21.
Profiles and Global Defaults
2-27
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
2-18). The repository stores the Dynamic Privacy Rules Projects created with the FileAID 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 2-19) throughout the rest of the product.
File-AID/Data Solutions and File-AID Data Privacy are required.
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 2-19).
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 2-6).
Note:
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 2-18, 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 FileAID/RDX Primary Option Menu.
END : Saves the current updates and returns to the File-AID/RDX Primary Option Menu.
2-28
File-AID/RDX Reference
3-1
Chapter 3.
Relationship Facilitator
Chap 3
Overview
This chapter describes Option 1, Relationship Facilitator. The Relationship Facilitator
enables you to view and manipulate the relationship file to:
• view all relationships defined to File-AID/RDX.
• load DB2-defined referential integrity (RI) relationships, including non-enforced RI,
from the DB2 catalog table, SYSIBM.SYSRELS, into the relationship file.
• refresh the relationship file when its RI information does not match the DB2 catalog.
• delete RI and user-defined application relationship information from the
relationship file.
• add application relationship information to the relationship file.
• define data driven (“conditional”) application relationships.
• modify existing application relationship information.
• allocate a new relationship file.
• refresh RI information using batch
• print formatted contents of a relationship file.
Relationship File Compatibility Notes
1. Relationship files can be shared between File-AID for DB2 and File-AID/RDX.
2. DB2 long name support requires File-AID/RDX Release 4.3, or higher, or File-AID for
DB2 Release 4.8.1, or higher. Once a DB2 long name has been added to a Version 2
relationship file, File-AID/RDX updates it to a Version 3 relationship file. Version 3
relationship files are not downward compatible with earlier product releases.
Relationship File Contents
The relationship file (relationship repository) is a VSAM-KSDS file in which File-AID/RDX
stores the following types of information:
DB2 Referential Integrity (RI) Relationships
This relationship is one in which the dependent table rows contain foreign keys, the
values of which are the primary index of the parent table. The rules that define RI
relationships are enforced by DB2.
Use Option 5, LOAD RI from the DB2 Relationship Facilitator menu (Option 1,
RELATIONSHIPS) for an online load or update of the RI information in the Relationship
File. For more information, see “DB2 RI Update Online Options” on page 3-24.
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 3-83.
3-2
File-AID/RDX Reference
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.
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). FileAID/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 4-89) 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 3-56) 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 3-1 on page 3-3, you would create four conditional
application relationships with the respective conditional criteria defined on the parent
object ACCOUNT.
Relationship Facilitator
3-3
Figure 3-1. Sample Scenario of Conditional AR
Considerations for MVS Objects
File-AID/RDX supports defining application relationships for MVS objects as either
parent and/or dependent objects. Before defining a relationship keep in mind:
• file type must be SEQ, including GDG and GDS, KSDS, ESDS, or IAM 1
• MVS object must be defined with a COBOL or PL/I record layout; COBOL and
unaligned PL/I record layouts are compiled as interpreted by File-AID/RDX.
• only one record layout per object in a relationship file (layout usage S); if more than
one is required, use XREF (layout usage X)
• only one XREF file per object in a relationship file
• the LRCL must be less than or equal to 32,756 in order for the data records to be
extracted
• File-AID/RDX does not support undefined record format (RECFM=U).
GDG Considerations
File-AID/RDX supports relative GDG numbers in addition to the G0000V00 (i.e.
.G0001V00) hard coded number for physical sequential files. File-AID/RDX allows you to
define application relationships (AR) to or from a GDG or a GDS. Relationships are
allowed between generations of the same GDG. If, for example, your current quarterly
report is to extract from the current and the two previous months, you define these
relationships:
1. GDG.PAYMENTS.QUARTER(0) to GDG.PAYMENTS.MONTH(0)
2. GDG.PAYMENTS.QUARTER(0) to GDG.PAYMENTS.MONTH(-1)
3. GDG.PAYMENTS.QUARTER(0) to GDG.PAYMENTS.MONTH(-2)
When specifying the GDG base in a relationship, for example GDG.PAYMENTS.MONTH,
File-AID/RDX extracts from all existing generations.
1. For File-AID/RDX to continue support of IAM (Innovation Access Method) file types, you must apply the
appropriate IAM version fix. IAM Version 9.0 requires fix P900235 and IAM Version 9.1 requires fix P910005.
3-4
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, FileAID/RDX will not display any relationships. To see the relationships for the view’s base
table you must enter the base table name.
Relationship Facilitator
3-5
DB2 Relationship Facilitator
The “DB2 Relationship Facilitator” screen shown in Figure 3-2 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 2-11). The “DB2 Relationship Facilitator” screen also appears when you
enter the DB2 command in the “MVS Relationship Facilitator” screen.
Figure 3-2. DB2 Relationship Facilitator
File-AID/RDX
Option ===>
--------
DB2 Relationship Facilitator
-------------------------
Scroll ===> CSR 
SITE Profile: RDXMENU 
Primary commands: menu-option, MVS Relationship Facilitator


1 BROWSE ALL
- Browse all existing Relationships

2 EDIT AR
- Edit existing Application Relationships

3 ADD AR
- Add new Application Relationships

4 LIST RDX
- List DB2 objects from RDX Relationship File

5 LOAD RI
- Load RI Relationships defined to DB2

6 LIST DB2
- List DB2 objects from DB2 Catalog

A ALLOCATE
- Allocate Relationship File

L BATCH RI LOAD
- Batch Job to Load RI Relationships
P PRINT
- Print the Relationship File


Specify a Table Name or pattern:

SSID
===> *
(* or pattern for selection list)
Location
===> *
(* or pattern for selection list)
Creator
===> *
(* or pattern for selection list)
Table Name
===> *
(* or pattern for selection list)

Specify Relationship Information:

File name
===> FRSAMP.RELATION

Use this screen to specify the name of the table or view for which you want to maintain
relationships and the File-AID/RDX relationship file that contains the information about
those relationships. Then enter one of the menu options to specify the action you want
to perform. When pressing Enter without selecting an option, File-AID/RDX selects
option 4, List RDX, and lists all matching entries found in the relationship file. FileAID/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.
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 3-15 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 3-32 for
3-6
File-AID/RDX Reference
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 3-34.
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
3-7.
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 3-24.
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 3-7.
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 3-82.
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 3-83.
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 3-87.
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 : 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.
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 1-4).
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 1-4).
Relationship Facilitator
3-7
Notes for Creator and Table fields : Which list File-AID/RDX will display depends
on the option you select:
1 : Table List in Relationship File
2 : Table List in Relationship File
3 : Table List - SYSIBM.SYSTABLES
4 : DB2 Object List
5 : Table List - SYSIBM.SYSTABLES
6 : DB2 Object List
If you specify a pattern and press the Enter key without selecting an option, the DB2
Object List screen shown in Figure 3-3 on page 3-7 is displayed. See “DB2 Object List”
on page 3-7 for more information. In the other table lists, select the desired
Creator.Table combination with the S line command.
Specify Relationship File Area
File Name : Specify the name of the File-AID/RDX relationship file that contains the
relationship information you want to display or maintain. Refer to “Relationship
File” on page 1-16 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 3-3 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 3-2 on page 3-5.
Figure 3-3. DB2 Object List


File-AID/RDX
Command ===>
---------------
DB2 Object List
Line Commands: A = Add Application Relationship
E = Edit Application Relationship
-------------- Row 1 to 6 of 6
SCROLL ===> CSR
B = Browse 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
3-8
File-AID/RDX Reference
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:
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 3-34.
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 3-15 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.
Relationship Facilitator
3-9
Table List in Relationship File
The “Table List in Relationship File” screen shown in Figure 3-4 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 3-2 on page 3-5.
Figure 3-4. Table List in Relationship File
-------- DB2 Relationship Facilitator ------------------------- 
Table List in Relationship File
===> CSR 
Row 1 to 6 of 6
e: RDXMENU
Command ===>
SCROLL ===> CSR


Enter 'S' to select table name

Relation

CMD
Object Name
Type
SSID

--- -------------------------------------- --------
DSNLOCAT.FRSAMP.CONTACT_TABLE
RI
DSN
es

DSNLOCAT.FRSAMP.CUSTOMER_TABLE
AR/RI
DSN

DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
RI
DSN

DSNLOCAT.FRSAMP.ORDER_TABLE
AR/RI
DSN

DSNLOCAT.FRSAMP.PART_TABLE
AR/RI
DSN

DSNLOCAT.FRSAMP.SUPPLIER_TABLE
AR/RI
DSN
ction list)
********************** Bottom of data ***********************
ction list)
ction list)
ction list)




File-AID/RDX
O
P
S
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 FileAID/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:
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 3-9 on page 3-15.
3-10
File-AID/RDX Reference
Table List - SYSIBM.SYSTABLES
The “Table List - SYSIBM.SYSTABLES” screen shown in Figure 3-5 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 3-2 on page 3-5.
Figure 3-5. Table List - SYSIBM.SYSTABLES
-------- DB2 Relationship Facilitator ------------------------- 
Table List - SYSIBM.SYSTABLES
===> CSR

Row 1 to 12 of 12
e: RDXMENU 
Command ===>
SCROLL ===> CSR


Enter 'S' to select table name

Relation

CMD
Object Name
Type
SSID

--- -------------------------------------- --------
DSNLOCAT.FRSAMP.CONTACT_TABLE
RI
DSN
es

DSNLOCAT.FRSAMP.CONTACT_VIEW
CATLG
DSN

DSNLOCAT.FRSAMP.CUSTOMER_TABLE
AR/RI
DSN

DSNLOCAT.FRSAMP.CUSTOMER_VIEW
CATLG
DSN

DSNLOCAT.FRSAMP.ORDER_LINE_TABLE
RI
DSN

DSNLOCAT.FRSAMP.ORDER_LINE_VIEW
Catlg
DSN
ction list) 
DSNLOCAT.FRSAMP.ORDER_TABLE
AR/RI
DSN
ction list) 
DSNLOCAT.FRSAMP.ORDER_VIEW
CATLG
DSN
ction list) 
DSNLOCAT.FRSAMP.PART_TABLE
AR/RI
DSN
ction list) 
DSNLOCAT.FRSAMP.PART_VIEW
CATLG
DSN

DSNLOCAT.FRSAMP.SUPPLIER_TABLE
AR/RI
DSN

DSNLOCAT.FRSAMP.SUPPLIER_view
CATLG
DSN

********************** Bottom of data ***********************


File-AID/RDX
O
P
S
S

This screen displays a list of DB2 objects defined in the DB2 catalog that match the
pattern. If there are more objects that match the pattern you specified on the previous
screen than will fit on the “Table List - SYSIBM.SYSTABLES” window, you can scroll the
list using standard scrolling commands. Use this window to select the object for which
File-AID/RDX will add an application relationship or load the RI information to the
relationship file. The resulting list of relationships associated with the selected object is
displayed on the “Relationship Detail” screen.
CMD : Enter an S line command in this column next to the object for which you want
to see a list of relationships or add a relationship.The S line command is the only
valid line command for this screen.
Object Name : Displays the names of DB2 objects that match the value specified in the
“DB2 Relationship Facilitator” screen.
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
Relationship Facilitator
3-11
object the “DB2 RI Update Online Options Screen” as shown in Figure 3-15 on page
3-24 is displayed. When adding an AR for the selected object, the “Object Type
Selection Screen for Adding Application Relationship” screen as shown in Figure 3-22
on page 3-34 is displayed.
MVS Relationship Facilitator
The “MVS Relationship Facilitator” screen shown in Figure 3-6 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 2-11). The “MVS Relationship Facilitator” screen also appears when you
enter the MVS command in the “DB2 Relationship Facilitator” screen.
Figure 3-6. MVS Relationship Facilitator
File-AID/RDX
Option ===>
--------
MVS Relationship Facilitator
-------------------------
TSOID01 Profile: A1


Primary commands: menu-option, DB2 Relationship Facilitator


1 BROWSE ALL
- Browse all existing Relationships

2 EDIT AR
- Edit existing Application Relationships

3 ADD AR
- Add new Application Relationships

4 LIST RDX
- List MVS objects from RDX Relationship File

A ALLOCATE
- Allocate Relationship File

P PRINT
- Print the Relationship File



Specify a File Name or Pattern:

File name
===> 'TSOID01.FRSAMP.*'

Record layout usage
===> S
(S = Single; X = XREF;)

Record layout file
===>

Member name
===>
(Blank or pattern for member list)

XREF file name
===>

Member name
===>

I/O exit name
===>


Specify Relationship Information:

File name
===> FRSAMP.RELATION

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. FileAID/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 3-15 for more
detail.
When browsing existing relationships you can also modify, delete, and add new
application relationships.
3-12
File-AID/RDX Reference
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 3-32 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 3-34.
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
3-13.
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.
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 1-4).
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 1-4).
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 1-4).
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.
I/O Exit Name : Specify the I/O Exit Name for the MVS object for which you want to
view relationship information.
Relationship Facilitator
3-13
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 1-16 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 3-7 is displayed when you select Option 4
and specify a pattern in the File Name field on the “MVS Relationship Facilitator” screen,
Figure 3-6 on page 3-11.
Figure 3-7. MVS Object List
-------------- Row 1 to 6 of 6 
SCROLL===> CSR


Line Commands: A = Add Application Relationships
B = Browse Relationship 
E = Edit Application Relationship


CMD
Object Name

--- -----------------------------------------------------
TSOID01.FRSAMP.CONTACTT

TSOID01.FRSAMP.CUSTOMER

TSOID01.FRSAMP.ORDERLIN

TSOID01.FRSAMP.ORDERTAB

TSOID01.FRSAMP.PARTTABL

TSOID01.FRSAMP.SUPPLIER

******************************* Bottom of data ********************************
File-AID/RDX
Command ===>
---------------
MVS Object List
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.
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 3-34.
3-14
File-AID/RDX Reference
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 3-15 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 3-8 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 3-6 on page 3-11.
Figure 3-8. Object List in Relationship File
File-AID/RDX
O
P
S
S
-------- MVS Relationship Facilitator -------------------------
Object List in Relationship File
e: SAMPMENU
Row 1 to 6 of 6

Command ===>
SCROLL ===> CSR


Enter 'S' to select table name


CMD
Object Name

--- -----------------------------------------------------
_
TSOID01.FRSAMP.CONTACTT

_
TSOID01.FRSAMP.CUSTOMER

_
TSOID01.FRSAMP.ORDERLIN

_
TSOID01.FRSAMP.ORDERTAB

_
TSOID01.FRSAMP.PARTTABL

_
TSOID01.FRSAMP.SUPPLIER

********************** Bottom of data ***********************

list)







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.
Relationship Facilitator
3-15
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 3-9 on page 3-15.
Relationship Detail
The “Relationship Detail” screen shown in Figure 3-9 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.
When your profile has navigation criteria Direct set to C or P (see also “Direct” on page
2-9), 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 3-9. Relationship Detail



File-AID/RDX
Command ===>
Base object:
-----------
------------ Row 1 to 5 of 9 
SCROLL ===> CSR 
Relationship Detail
'TSOID01.FARDX2.SAMP.SALEHIST'

Line Commands: S - Select Relationship to Modify
A - Add Application Relationship
D - Delete Relationship
I - Relationship Information
Obj
CMD
Parent/Dependent
Type
--- ---------------------------------------------- ---_ LOCATION.TSOID01.ORDER_TABLE
DB2
'TSOID01.FARDX2.SAMP.SALEHIST'
MVS
_ 'TSOID01.FARDX2.SAMP.SALEHIST'
MVS
'TSOID01.FARDX2.SAMP.CREDIT'
MVS
_ 'TSOID01.FARDX2.SAMP.SALEHIST'
MVS
'TSOID01.FARDX2.SAMP.ZIPCODE'
MVS
_ LOCATION.TSOID01.ORDER_TABLE
DB2
LOCATION.TSOID01.ORDER_LINE_TABLE
DB2
_ LOCATION.TSOID01.PART_TABLE
DB2
LOCATION.TSOID01.ORDER_LINE_TABLE
DB2
Rel
Status/
Type
Description
----- -----------------
AR
Order to Sales H
AR
Sales History to
AR
Sales History ZI
RI
ASSOCIATED REL.
ORDLORD
RI
ASSOCIATED REL.
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.
3-16
File-AID/RDX Reference
CMD : Enter line commands in this column. See “Line Commands” on page 3-19 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.
Note:
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.
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 3-33 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 3-34.
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 3-20 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 3-70 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 — 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 3-34.
Relationship Facilitator
3-17
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 3-17 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 3-10 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 3-10. Graphical Relationship Display Screen
File-AID/RDX
COMMAND ===>
---- Graphical Relationship Display ---------- Row 1 to 18 of 23
SCROLL ===> CSR
TAB to Object and press ENTER for an Option List
* Denotes the object is involved in additional relationships
MVS-'TSOID01.FARDX2.SAMP.ZIPCODE'
|
|__ DB2-CUSTOMER_TABLE
|
|__ MVS-'TSOID01.FARDX2.SAMP.CREDIT'
|
|__ DB2-CONTACT_TABLE
|
|__ MVS-'TSOID01.FARDX2.SAMP.SALEHIST'
|
|__ MVS-'TSOID01.FARDX2.SAMP.INVOICE'
|
|__ DB2-ORDER_TABLE
|
*|__ DB2-ORDER_LINE_TABLE
DB2-PART_TABLE
|
*|__ DB2-ORDER_LINE_TABLE
|
|__ DB2-SUPPLIER_TABLE




























Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:
CREATOR : Enter the CREATOR primary command in the graphical relationship display
and all DB2 objects will include their Creator ID. This command acts as a toggle
command, thus, when entering the command again, DB2 objects will include their
Creator ID only when there is more than one object with the same name.
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
3-18
File-AID/RDX Reference
• 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 “CREATOR”primary 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 3-10, MVS-'TSOID01.FARDX2.SAMP.
ZIPCODE' and DB2-PART_TABLE have no parents. They are at the top of their
groups, respectively. There is one group displayed for MVS-'TSOID01.
FARDX2.SAMP.ZIPCODE' and one group displayed for DB2-PART_TABLE.
Note:
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 3-10, MVS-'TSOID01.FARDX2.SAMP.CREDIT' is the object specified and is
therefore highlighted.
• Relationships are displayed as lines that connect the boxes. Lines start at the bottom
of parent objects and end at the left side of dependent objects. In Figure 3-10, MVS'TSOID01.FARDX2.SAMP.ZIPCODE' is a parent of DB2-CUSTOMER_TABLE. DB2CUSTOMER_TABLE itself is a parent of MVS-'TSOID01.FARDX2.SAMP.CREDIT' and
four other objects.
• Objects that are displayed more than once are denoted by an asterisk (*). In Figure 310 on page 3-17, 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.
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 3-11. In addition, you can enter the I line command to display the
Relationship Information screen. See “Line Commands” on page 3-19 for more
information about the I line command.
Relationship Facilitator
3-19
Figure 3-11. Graphical Relationship Display with Option List
File-AID/RDX
COMMAND ===>








---- Graphical Relationship Display ---------- Row 1 to 18 of 23
SCROLL ===> CSR
TAB to Object and press ENTER for an Option List
* Denotes the object is involved in additional relationships
MVS-'TSOID01.FARDX2.SAMP.ZIPCODE'
|
|__ DB2-CUSTOMER_TABLE

Option List for: MVS-'TSOID01.FARDX2.SAMP.CREDIT'

Row 1 to 3 of 3
COMMAND ===>
Enter "S" to select an option
CMD Description
--- ----------------------------------------------------------------_
Display Relationship Information(I)
_
Go to expanded view of dependents
_
Go to dependent of MVS-'TSOID01.FARDX2.SAMP.SALEHIST'
***************************** Bottom of data *****************************














Option List
To select an option from the Option List, type an S in the CMD column next to an option
and press Enter.
The options in the Option List are as follows:
Display Relationship Information (I) : Displays the Relationship Information pop-up
window. See “Relationship Information Screen” on page 3-20 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 3-10 on page 3-17, 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.
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.
3-20
File-AID/RDX Reference
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 3-12.
Figure 3-12. Relationship Information Screen—RI relationship information
DB2 Row 1 to 2 of 2 
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 ***




File-AID/RDX
Command ===>
Relationship Information
When you select an application relationship between an MVS and DB2 object, the
Relationship Information window is displayed as shown in Figure 3-13 on page 3-21.
Relationship Facilitator
3-21
Figure 3-13. Relationship Information Screen—MVS to DB2 Application Relationship Information
Row 1 to 2 of 2 
Scroll
===> CSR


Parent Name:
'TSOID01.FRSAMP.PARTTABL'
Type: MVS

Layout Dataset: ‘TSOID01.FRSAMP.LAYOUTS’
Mbr: PARTTABL 
XREF Dataset:
Mbr:

01 Level Name: PROD001-PART-TABLE

Dependent Name: LOCATION.TSOID01.SUPPLIER_TABLE
Type: DB2




Relationship Details:

Description:
AR 
Status:
ADDED

Created:
2006-11-01 16.00.16
User: TSOID01 
Last Modified
User:

Parent Fields
/Type(Length)
Dependent Columns /Type(Length)

----------------------------------------- ------------------------------------
1/PART-NUMBER
1/PART_NUMBER

CHAR(6)
CHAR(6)

*** End Of Fields ***
*** End Of Columns ***





File-AID/RDX
Command ===>
Relationship Information
When you select an MVS to MVS AR relationship, the Relationship Information screen is
displayed as shown in Figure 3-14.
Figure 3-14. Relationship Information Screen—MVS to MVS AR Relationship Information
Row 1 to 2 of 2 
SCROLL
===> CSR


Parent Name:
'TSOID01.FASAMP.EMPLOYEE'
Type: MVS

Layout Dataset: TSOID01.FASAMP.LAYOUTS
Mbr: EMPLOYEE 
XREF Dataset:
Mbr:

01 Level Name: EMPLOYEE-MASTER-FILE

Dependent Name: 'TSOID01.FASAMP.ORDRFILE'
Type: MVS

Layout Dataset: TSOID01.FASAMP.LAYOUTS
Mbr: ORDERWO

XREF Dataset:
Mbr:

01 Level Name: INTERNAL-WORK-ORDER

Relationship Details:

Description:
AR 
Status:

Created:
2006-11-01 15.26.06
User: TSOID01

Last Modified
User:

Parent Fields
/Type(Length)
Dependent Fields
/Type(Length)

----------------------------------------- ------------------------------------
1/EMP-NUMBER
2/ORDER-NO

CHAR(1,5)
CHAR(1,5)

*** End Of Fields ***
*** End Of Fields ***




File-AID/RDX
Command ===>
Relationship Information
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.
Type : Indicates the object type of the parent and dependent object.
DB2 : DB2 table.
MVS : MVS file.
3-22
File-AID/RDX Reference
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 * heading indicates that it is a conditional application relationship
created with the COND command. The column displays a value only for already defined
relationships in the Parent portion.
Description : A description of the selected relationship. The contents of this field vary according to
the relationship type as follows:
RI : The RELNAME from the DB2 catalog table, SYSIBM.SYSRELS (see Figure 3-12 on page 3-20).
AR : The description entered by the user when adding an application relationship (see Figure 313 on page 3-21).
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 descendent of
the driving object, or the driving object is a descendent 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:
Relationship Facilitator
3-23
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.
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 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.
3-24
File-AID/RDX Reference
Note:
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.
Note:
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 3-25 on page
3-39).
DB2 RI Update Online Options
The “DB2 RI Update Online Options Screen” shown in Figure 3-15 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.
Figure 3-15. DB2 RI Update Online Options Screen
------- DB2 RI Update Online Options ----------------------- 
Scroll ===> CSR 

RI Load Filter:

SSID
===> DSN

Location
===> LOCATION

Creator
===> FRSAMP

Table Name
===> ORDER_TABLE


RI Load Scope
===> _
(Enter load option)

1 = Load entire related thread for the creator and table

2 = Load only relationship to or from this creator and table

3 = Load all relationships for this creator

4 = Load all relationships for this subsystem


Note: Option 1 will display the entire related thread.

Options 2-4 will only display relationship changes.


Specify Relationship Information:

File name
===> FRSAMP.RELATION 
File-AID/RDX
Option ===>
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.
Relationship Facilitator
3-25
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.
1 : Load the entire related thread for the above specified creator and table, including
associated relationships. The “RI Relationship Detail Screen” (Figure 3-16 on page
3-26) 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 3-17 on page 3-27) 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 318 on page 3-27) 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
3-19 on page 3-28) 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 1-18 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 3-16.
3-26
File-AID/RDX Reference
Figure 3-16. RI Relationship Detail Screen RI Load Option 1
File-AID/RDX
Command ===>
------
RI Relationship Detail
------------ Row 1 to 3 of 3
SCROLL ===> CSR 

Primary Commands: ALL

Line Commands: S = Select Relationship to Load
D = Delete Relationship 
I = Relationship Information


Base Object:
LOCATION.FRSAMP.ORDER_TABLE

Obj Rel

CMD
Parent/Dependent
Type Type
Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.FRSAMP.ORDER_TABLE
DB2 RI
Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE
DB2

_ LOCATION.FRSAMP.PART_TABLE
DB2 RI
Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE
DB2

_ LOCATION.FRSAMP.PART_TABLE
DB2 RI
Not in Dataset
LOCATION.FRSAMP.SUPPLIER_TABLE
DB2

******************************* Bottom of data ********************************
This screen lists all DB2 RI relationships associated with the driving table, the DB2 table
specified in the Base Object: field, the table for which you had specified the Load RI
option or L line command.
Use this screen to load and refresh relationships in the File-AID/RDX relationship file (S
line command or ALL primary command), delete relationships from the relationship file
(D line command), and select relationships about which you want to view more detailed
information (I line command).
This screen displays information from the DB2 catalog and File-AID/RDX’s relationship
file about all RI relationships involving the specified table.
Relationships in which the driving table is either the parent or the dependent are listed
first. Those relationships that involve the dependents of the driving table are listed below
and are marked ASSOCIATED REL.
RI Load Scope Options 2, 3, or 4
When selecting RI Load Scope Options 2, 3, or 4, the RI Relationship Detail screen
displays as shown in Figure 3-17, Figure 3-18, and Figure 3-19. 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.
Relationship Facilitator
Figure 3-17. RI Relationship Detail Screen RI Load Option 2
File-AID/RDX
Command ===>
------
RI Relationship Detail
------------ Row 1 to 1 of 1
SCROLL ===> CSR 

Primary Commands: ALL

Line Commands: S = Select Relationship to Load


Base Object:
LOCATION.FRSAMP.ORDER_TABLE

Obj Rel

CMD
Parent/Dependent
Type Type
Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.FRSAMP.ORDER_TABLE
DB2 RI
Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE
DB2

******************************* Bottom of data ********************************
Figure 3-18. RI Relationship Detail Screen RI Load Option 3
File-AID/RDX
Command ===>
------
RI Relationship Detail
------------ Row 1 to 4 of 4
SCROLL ===> CSR 

Primary Commands: ALL

Line Commands: S = Select Relationship to Load


Base Object:
LOCATION.FRSAMP.ORDER_TABLE

Obj Rel

CMD
Parent/Dependent
Type Type
Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.FRSAMP.ORDER_TABLE
DB2 RI
Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE
DB2

_ LOCATION.FRSAMP.CUSTOMER_TABLE
DB2 RI
Not in Dataset
LOCATION.FRSAMP.CONTACT_TABLE
DB2

_ LOCATION.FRSAMP.PART_TABLE
DB2 RI
Not in Dataset
LOCATION.FRSAMP.ORDER_LINE_TABLE
DB2

_ LOCATION.FRSAMP.PART_TABLE
DB2 RI
Not in Dataset
LOCATION.FRSAMP.SUPPLIER_TABLE
DB2 
******************************* Bottom of data ********************************
3-27
3-28
File-AID/RDX Reference
Figure 3-19. RI Relationship Detail Screen RI Load Option 4
File-AID/RDX
Command ===>
------
RI Relationship Detail
-------- Row 1 to 7 of 4,454
SCROLL ===> CSR 

Primary Commands: ALL

Line Commands: S = Select Relationship to Load


Base Object:
LOCATION.FRSAMP.ORDER_TABLE

Obj Rel

CMD
Parent/Dependent
Type Type
Status
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.$172.AGTANSIR
DB2 RI
Not in Dataset 
LOCATION.$172.AGTANSHS
DB2

_ LOCATION.$172.AGTZIP
DB2 RI
Not in Dataset 
LOCATION.$172.AGTANSIR
DB2

_ LOCATION.$172.AGTVER
DB2 RI
Not in Dataset 
LOCATION.$172.AGTASGN
DB2

_ LOCATION.$172.AGTZIP
DB2 RI
Not in Dataset 
LOCATION.$172.AGTASGN
DB2

_ LOCATION.$172.AGTZIP
DB2 RI
Not in Dataset 
LOCATION.$172.AGTCITY
DB2

_ LOCATION.$172.AGTZIP
DB2 RI
Not in Dataset 
LOCATION.$172.AGTZIPHS
DB2

_ LOCATION.$172.VKTVENRQRSLOG
DB2 RI
Not in Dataset 
LOCATION.$172.VKTRQRSXREF
DB2 
For each relationship, the following columns are displayed:
CMD : Enter line commands in this column. See “Line Commands” on page 3-19 for
information about commands that are valid for this screen.
Parent/Dependent : Displays the name of the DB2 table defined as the parent in an RI
relationship in the upper row (the row with the CMD input field). The foreign keys
in the dependent table refer to this table. Table names are displayed in the format
location.creator.table.
Displays the name of the DB2 table defined as the dependent in an RI relationship in
the lower row. This table contains the foreign keys. Table names are displayed in the
format location.creator.table.
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.
Relationship Facilitator
3-29
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 3-16) 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.
I (Relationship Information) : (Load Option 1 only, see Figure 3-16) 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 3-20 on page 3-30). 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 3-12 on page 3-20).
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 3-17 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.
3-30
File-AID/RDX Reference
Figure 3-20. RI Information Screen
File-AID/RDX
Command ===>
Parent Name:
Relationship Information
LOCATION.FRSAMP.EMP
DB2 Row 1 to 2 of 2
Scroll
===> CSR
Type: DB2
Dependent Name: LOCATION.FRSAMP.DEPT
Type: DB2
Relationship Details:
Description:
RI - REP
Status:
Not in Dataset
Created:
User:
Last Modified
User:
Parent Columns /Type(Length)
Dependent Columns /Type(Length)
----------------------------------------- -----------------------------------LNAME
REP
*** End Of Columns ***
*** End Of Columns ***






















Parent and Dependent Object Name Area
The fields in this area provide information about the parent and dependent objects.
Parent Name : Displays the name of the table defined as the parent table in an RI
relationship. This table’s primary index contains values that match the foreign keys
defined in the corresponding dependent table. Tables are displayed in the format
location.creator.table.
Type : Indicates the object type of the parent and dependent object.
DB2
indicates a DB2 table.
Dependent Name : Displays the name of the table defined as the dependent table in an
RI relationship. This table contains the foreign key, the values of which match the
parent table’s primary index. Tables are displayed in the format
location.creator.table.
Relationship Details Area
The fields in this area provide information about the relationship such as the
Relationship Description, the Status of the relationship, creation and modification dates.
Description : A description of the selected relationship.
RI
The RELNAME from the DB2 catalog table, SYSIBM.SYSRELS (see Figure 3-12 on
page 3-20).
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.
Relationship Facilitator
3-31
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.
Note:
If the DB2 column data type is distinct (UDT), File-AID/RDX displays
only the underlying built-in data type.
3-32
File-AID/RDX Reference
Application Relationship Detail
The Application Relationship Detail screen shown in Figure 3-21 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 3-21. Application Relationship Detail Screen



File-AID/RDX
Command ===>

Base object:
Application Relationship Detail
LOCATION.TSOID01.BILLING
Row 1 to 1 of 1 
SCROLL ===> CSR

Line Commands: S - Select Relationship to Modify
A - Add Application Relationship
Relationship Information 
D - Delete Relationship
I -
Obj Rel
Status/
CMD
Parent/Dependent
Type Type
Description
--- ---------------------------------------------- ---- ----- -----------------
_ LOCATION.TSOID01.BILLING
DB2 AR

LOCATION.TSOID01.PURCHASEORDER
DB2
Billing to Purch
******************************* BOTTOM OF DATA ********************************
This screen displays a list of application relationships (AR) for the object and relationship
file specified with the Edit AR option or E line command. It is similar to the
“Relationship Detail” on page 3-15, 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 3-19 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.
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.
Relationship Facilitator
3-33
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 3-30 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
found
Cannot find one of the objects (dependent or parent) 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 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 3-34.
D (Delete) : Deletes an application relationship from the relationship file.
I (Relationship Information) : Invokes the Relationship Information screen. See
“Relationship Information Screen” on page 3-20 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 3-70 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 3-34.
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 3-17 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
3-20 for more information about the contents of this window.
3-34
File-AID/RDX Reference
Add Relationships — Specify Object Types
The Add Relationships — Specify Object Types screen shown in Figure 3-22 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 3-9 on
page 3-15).
Figure 3-22. Object Type Selection Screen for Adding Application Relationship





File-AID/RDX -------------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




Add Relationships
Specify Relationship File:
File Name
===> FRSAMP.RELATION


Use this screen to specify the object type of the parent and the dependent object for the
new relationship.
Parent Object Type : Select one of the two choices to indicate the object type of the
parent:
DB2 Table
Place an S line command in front of this option if the parent object is a DB2 table.
MVS File
Place an S line command in front of this option if the parent object is an MVS file.
Dependent Object Type : Select one of the three choices to indicate the object type of
the dependent:
DB2 Table
Place an S line command in front of this option if the dependent object is a DB2
table.
MVS File
Place an S line command in front of this option if the dependent object is an
MVS file.
IMS and Output Place an S line command in front of this option if the dependent object is an IMS
Segment or an Output Key file. Use this option when you want your extract to
Key Files
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 3-35
2. DB2 ==> MVS, see “Add Relationships — DB2 to MVS” on page 3-37
3. DB2 ==> KEY, see “Add Relationships — DB2 to IMS and Output Key Files” on page
3-39
4. MVS ==> DB2, see “Add Relationships — MVS to DB2” on page 3-42
5. MVS ==> MVS, see “Add Relationships — MVS to MVS” on page 3-44
Relationship Facilitator
3-35
6. MVS ==> KEY, see “Add Relationships — MVS to IMS and Output Key Files” on page
3-47
Add Application Relationships — DB2 to DB2
This Add Application Relationships screen shown in Figure 3-23 is displayed after you
specified DB2 tables for both parent and dependent objects in the previous screen, “Add
Relationships — Specify Object Types” on page 3-34 or “Application Relationship Detail”
on page 3-32.
Figure 3-23. Add Relationships Screen — DB2 to DB2




File-AID/RDX ---------------Command ===> 
Specify Parent DB2
Location
===>
Creator
===>
Table Name
===>
Add Application Relationships
----------------
Table for Relationship Definition:
LOCATION
TSOID01
(* or pattern for selection list)
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
Description
===> DSN
===>
(* or pattern for selection list)
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 1-4).
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 1-4).
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.
3-36
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
1-4).
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 1-4).
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 3-29 on page 3-50). 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 3-29 on page 3-50).
Note:
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 3-50.
Relationship Facilitator
3-37
Add Relationships — DB2 to MVS
This Add Relationships screen shown in Figure 3-24 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 3-34 or “Application Relationship Detail”
on page 3-32.
Figure 3-24. Add Relationships Screen — DB2 to MVS




File-AID/RDX
Command ===>
----------------
Specify Parent DB2
SSID
===>
Location
===>
Creator
===>
Table Name
===>
Add Relationships
----------------------------
Scroll ===> CSR
Table for Relationship Definition:
DSN
(* or pattern for selection list)
LOCATION
TSOID01
(* or pattern for selection list)
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.
Note:
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 1-4).
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 1-4).
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.
3-38
File-AID/RDX Reference
Note:
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 1-4).
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 1-4).
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
1-4).
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.
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 3-29 on page 3-50). 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 3-29 on page 3-50).
Note:
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 3-50.
Relationship Facilitator
3-39
Add Relationships — DB2 to IMS and Output Key Files
This Add Relationships screen shown in Figure 3-25 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 3-34 or “Application
Relationship Detail” on page 3-32.
Note:
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 4-89), 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 3-25. Add Relationships Screen — DB2 to KEY
File-AID/RDX
Command ===>
--------------
Add Application Relationships
-------------------
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.
SSID : Specify the DB2 subsystem ID of the DB2 subsystem on which the table resides for
which you want to add relationship information.
3-40
File-AID/RDX Reference
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 1-4).
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 1-4).
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 (*), 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 with identical names, type and length for
this relationship definition and present them in the following Column/Field or
Column/Segment Relationships Screen (see Figure 3-29 on page 3-50). 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 or Column/Segment Relationships Screen (see Figure
3-29 on page 3-50).
Relationship Facilitator
Note:
3-41
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, FileAID/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 3-50.
3-42
File-AID/RDX Reference
Add Relationships — MVS to DB2
This Add Relationships screen shown in Figure 3-26 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 3-34 or “Application Relationship Detail”
on page 3-32.
Figure 3-26. Add Relationships Screen — MVS to DB2
File-AID/RDX ---------------Command ===> 
Specify Parent File for
Name
Record Layout usage
Record layout file
Member name
XREF file name
Member name
I/O Exit Name
Add Relationships
----------------------------
Relationship Definition:
===>
===>
(S = Single; X = XREF;)
===>
===>
(Blank or pattern for member list)
===>
===>
(Blank or pattern for member list)
===>
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.
Note:
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 1-4).
Note:
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).
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 1-4).
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.
Relationship Facilitator
3-43
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 1-4).
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.
Note:
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 1-4).
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 1-4).
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
Field/Column Relationships Screen (see Figure 3-29 on page 3-50). 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 Field/Column Relationships Screen (see Figure 3-29 on page 3-50).
Note:
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 3-50.
3-44
File-AID/RDX Reference
Add Relationships — MVS to MVS
This Add Relationships screen shown in Figure 3-27 is displayed after you specified MVS
file as both parent and dependent object in the previous screen, “Add Relationships —
Specify Object Types” on page 3-34 or “Application Relationship Detail” on page 3-32.
Figure 3-27. Add Relationships Screen — MVS to MVS



File-AID/RDX ---------------Command ===> 
Specify Parent File for
Name
Record Layout usage
Record layout file
Member name
XREF file name
Member name
I/O Exit Name
Add Relationships
----------------------------
Relationship Definition:
===>
===>
(S = Single; X = XREF;)
===>
===>
(Blank or pattern for member list)
===>
===>
(Blank or pattern for member 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 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.
Note:
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 1-4).
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 1-4).
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 1-4).
Relationship Facilitator
3-45
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.
Note:
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 1-4).
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 1-4).
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
1-4).
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 fields with identical names, type and length for this
relationship definition and present them in the following Field Relationships
Screen (see Figure 3-29 on page 3-50). 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 Field Relationships Screen (see Figure 3-29 on page 3-50).
Note:
When parent and dependent objects are the same object, File-AID/RDX will
bypass the automatic suggest functions as all columns/fields would be
3-46
File-AID/RDX Reference
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 Relationship screen to define the related MVS fields, see
“Relationships” on page 3-50.
Relationship Facilitator
3-47
Add Relationships — MVS to IMS and Output Key Files
This Add Relationships screen shown in Figure 3-28 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 3-34 or
“Application Relationship Detail” on page 3-32.
Note:
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 4-89), 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 3-28. Add Relationship Screen — MVS to KEY



File-AID/RDX ---------------Command ===> 
Specify Parent File for
Name
Record Layout usage
Record layout file
Member name
XREF file name
Member name
I/O Exit Name
Add Relationships
----------------------------
Relationship Definition:
===>
===>
(S = Single; X = XREF;)
===>
===>
(Blank or pattern for member list)
===>
===>
(Blank or pattern for member 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 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.
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.
Note:
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.
3-48
File-AID/RDX Reference
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 1-4).
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 1-4).
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 1-4).
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 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 COBOL or PL/I segment record layout
describing 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 (*),
Relationship Facilitator
3-49
File-AID/RDX displays a Member List window containing a list of members that
match the specified pattern.
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 fields and root segments with identical names, type
and length for this relationship definition and present them in the following
Field or Field/Segment Relationships Screen (see Figure 3-29 on page 3-50). 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 Field or Field/Segment Relationships Screen (see Figure 3-29 on
page 3-50).
Note:
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 3-50.
3-50
File-AID/RDX Reference
Relationships
The Relationships screen shown in Figure 3-29 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 3-1 shows the possible title combinations.
Table 3-1.
Relationship Titles
Object Type Parent
Object Type Dependent
DB2
DB2
Title
Column Relationships
DB2
MVS
Column/Field Relationships
DB2
KEY
Column/Segment Relationships 
or
Column/Field Relationships if record/segment
layout is used
MVS
MVS
Field Relationships
MVS
DB2
Field/Column Relationships
MVS
KEY
Field/Segment Relationships 
or
Field Relationships if record/segment layout is
used
Figure 3-29. Relationships Screen - Column Relationships not yet defined

File-AID/RDX ------------- Column Relationships ----------------------------
Command ===>
SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands:
Column Number to Define Relationship D = Delete Relationship 
Parent:
DB2-LOCATION.TSOID01.EMP
Dependent: DB2-LOCATION.TSOID01.ORDKFL
CMD Parent Columns
Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
____ EMPNO
CHAR(6)
____ FIRSTNME
VCHAR(12)
____ MIDINIT
CHAR(1)
____ LASTNAME
VCHAR(15)
____ WORKDEPT
CHAR(3)
____ PHONENO
CHAR(4)
____ HIREDATE
DATE
NMBR Dependent Columns
Type(Length)
---- ------------------------------- ------------
1 ORDER_NUMBER
CHAR(6)
2 CUST_NUM
CHAR(6)
3 ORD_TYPE
CHAR(8)
4 ORD_DATE
DATE
5 ORD_STAT
CHAR(8)
6 ORD_AMOUNT
DEC(9,2)
Figure 3-29 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 3-30 on page 3-51 is displayed when
maintaining an MVS to MVS application relationship, with field relationships already
defined.
Relationship Facilitator
3-51
Figure 3-30. Relationships Screen — Field Relationships already defined

File-AID/RDX ------------- Field Relationships ----------------------------
Command ===>
SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships, CANcel
Line Commands:
Field Number to Define Relationship D = Delete Relationship 
Parent:
MVS-TSOID01.FARDX2.SAMP.SALEHIST 
Dependent: MVS-TSOID01.FARDX2.SAMP.ZIPCODE
CMD Parent fields
Type(Length)
---- ------------------------------- -----------____ FILLER
CHAR(15)
____ SH-DATE-SHIP
CHAR(8)
- - - - - - - - - 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)
Mapped fields
-----------------------------
6(1,11,1)
3(1,4,1)
- - - - - - -
Figure 3-30 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 3-31 is displayed when maintaining an MVS to
DB2 application relationship, with Unicode data types and field/column relationships
already defined.
Figure 3-31. Relationships Screen — with Unicode data
File-AID/RDX -------- Field/Column Relationships ---------------------------
Command ===>
SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships, CANcel
Line Commands:
Column Number to Define Relationship D = Delete Relationship

Parent:
MVS-TSOID01.FASAMP.EMPLOYU2 
Dependent: DB2-LOCATION.TSOID01.UNI_CUSTOMER_TABLE
CMD Parent fields
Type(Length) Mapped fields
---- ------------------------------- ------------ -----------------------------
____ 24/OUT-POSTAL-CODE
N(5) U16
15(1,5,1)/CONTACT_ZIP
- - - - - - - - - End of Related Columns - - - - - - - - 
____ OUT-STREET-ADDRESS
N(25) U16

____ FILLER
N(1) U16

____ OUT-CITY
N(15) U16

____ OUT-STATE
N(2) U16

____ FILLER
N(2) U16

NMBR Dependent Columns
Type(Length)

---- ------------------------------- -----------
14 CONTACT_STATE
CH(2) U-8

15 CONTACT_ZIP
CH(9) U-8

16 CONTACT_COUNTRY
CH(10) U-8

17 CONTACT_AREA_CD
CH(3) U-8

18 CONTACT_TELEPHONE
CH(7) U-8 
Use the relationship screen to create or update the column or field level relationship
detail for the related objects in the relationship file. See “Building Column/Field
Relationships” on page 3-70 for more information about how to use the Relationships
screen.
3-52
File-AID/RDX Reference
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 displayed at one time, use the scroll commands to
scroll through the data. Each area can also be scrolled individually with scroll mode CSR:
move the cursor into the area you want to scroll and use the UP or DOWN scroll
commands.
Object Names
The top portion of this screen displays the object names for the relationship:
Parent : Displays the full name of the parent object preceded by the object type. For
example, DB2 tables are identified in the form 
location.creator.table.
Dependent : Displays the full name of the dependent object preceded by the object type.
For example,
– DB2 tables are identified in the form
DB2-location.creator.table.
– MVS files are identified in the form
MVS-hlq.dataset(member).
– IMS root segments are identified in the form
KEY-hlq.DBD library dataset(member).
– IMS segment layouts are identified in the form
KEY-hlq.segment layout dataset(member).
– Output Key File layouts are identified in the form
KEY-hlq.record layout dataset(member).
Parent Portion
The Parent portion of this screen represents the parent information for the relationship.
If relationships have already been defined, the Parent portion is divided into two
scrollable areas by a dashed line, for example
- - - - - - - - - End of Related Columns - - - - - - - - -
The part above the dashed line contains the names of the columns/fields participating in
the application relationship with the Mapped Fields values filled in. The part below the
dashed line contains the names of all of the columns/fields for the parent.
CMD : Enter line commands in this column. See “Line Commands” on page 3-19 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.
– When there is a conflict between column information stored in the relationship
file and column information stored in the DB2 catalog table, SYSIBM.SYSCOLS.
Parent Columns or Parent Fields : Displays the names of the columns in the DB2 parent
table, or, if the parent is an MVS file, displays the names of the fields. If the field
contains an occurrence of subscripts, the element notation follows in parentheses.
Relationship Facilitator
3-53
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) U16. See Figure 3-31 for a sample screen.
See Table 3-2 for more information about data types displayed in this column.
Notes:
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, DECFLOAT, BIGINT,
VARBINARY, or XML cannot be part of an application relationship.
Table 3-2.
Data Type
Data Type Values
Value
CHAR or CH Fixed-length character strings less than or equal to 254 characters.
VCHAR or
VC
Variable-length character strings less than or equal to the field length specified when the
column is created. Maximum allowable field length is 4056 characters for 4k pages and
32,714 characters for 32k pages.
LVCHAR or
LV
Variable-length character strings less than or equal to 4056 characters for 4k pages and
32,714 characters for 32k pages.
GRPH
Fixed-length graphic strings less than or equal to 127 characters.
VGRPH
Variable-length graphic strings less than or equal to the field length specified when the
column is created. Maximum allowable field length is 2028 characters for 4k pages and
16,357 characters for 32k pages.
LVGRPH
Variable-length graphic strings less than or equal to 2028 characters for 4k pages and
16,357 characters for 32k pages.
SMALLINT
Fixed-length, binary integers in the range of -32,768 to +32,767, requiring two bytes of
storage.
INTEGER
Fixed-length, binary integers in the range of -2,146,483,648 to +2,147,483,467, requiring
four bytes of storage.
BIGINT
Fixed-length, binary integers in the range of -9223372036854775808 to
9223372036854775807, requiring eight bytes of storage.
DEC
Fixed-length, decimal numbers in the range of -10E15 to +10E15.
DECFLOAT
Decimal Floating Point can be either DECFLOAT(16) or DECFLOAT(34) representing either
16 or 34 significant digits. The range of a DECFLOAT(16) number is 10-383 to 10+384 and
the range of a DECFLOAT(34) number is 10-6143 to 10+6144. A DECFLOAT(16) field
occupies 8 bytes and a DECFLOAT(34) occupies 16 bytes.
REAL
Fixed-length, single-precision, floating-point numbers in the approximate range of 5.4E79 to 7.2E+75.
DOUBLE
Fixed-length, double-precision, floating-point numbers in the approximate range of 5.4E79 to 7.2E+75.
DATE
A three-part value (year, month, day) whose format is determined by DB2.
TIME
A three-part value (hour, minute, second) whose format is determined by DB2.
TMSTMP(n) TIMESTAMP: A seven-part value (year, month, day, hour, minute, second, and precision)
whose format is YYYY-MM-DD-HH.MM.SS.TTTTTTTTTTTT. The precision value
(TTTTTTTTTTTT) is variable length and has 0 to 12 digits (up to picosecond) with a default
of 6 (microsecond). TMSTMP(n) specifies the scale (length) with n = 0 through 12. For DB2
Versions prior to Version 10, the length is always 6.
TMESTZ(n)
TIMESTAMP WITH TIME ZONE: An eight-part value (year, month, day, hour, minute,
second, precision, time zone) whose format is YYYY-MM-DDHH.MM.SS.TTTTTTTTTTTT±HH:MM. The precision value (TTTTTTTTTTTT) is variable
length and has 0 to 12 digits (up to picosecond) with a default of 6 (microsecond). The
time zone is the difference in hours and minutes between local time and UTC. The range
of the hour offset is -12 to +14, and the minute offset is 00 to 59. The time zone is specified
in the format ±th.tm, with values ranging from -12.59 to +14.00. TMESTZ(n) specifies the
scale (length) with n = 0 through 12. DB2 Version 10 and higher only.
File-AID/RDX Reference
Table 3-2.
Data Type Values (Continued)
Data Type
Value
CLOB
A character large object (CLOB) is a varying-length string with a maximum length of 2 147
483 647 bytes (2 gigabytes minus 1 byte).
DBCLOB
A double-byte character large object (DBCLOB) is a varying-length string with a maximum
length of 1 073 741 823 double-byte characters.
XML
A data type for storage of well formed XML documents.
BLOB
A binary large object (BLOB) is a varying-length string with a maximum length of 2 147
483 647 bytes (2 gigabytes minus 1 byte).
BINARY
BINARY is a fixed length binary string which extends the support for binary strings beyond
BLOBs. Length attribute must between 1 and 255 inclusive.
VARBINARY VARBINARY is a variable length binary string which extends the support for binary strings
beyond BLOBs. Length attribute must between 1 and 32704.
ROWID
Row identifier. A value that uniquely identifies a row. If a table contains a large object it
must also have a ROWID column.
HEXADEC
Fixed length string, supported as a string only.
FLTPIC
Fixed length character string representing a floating point value.
FIXPIC
Fixed length character string representing a decimal or integer value.
N
(National)
Unicode data from an MVS file in COBOL is identified as PIC N or USAGE NATIONAL. This
is UTF-16, CCSID=1200. Identified as N(x) U-16.
Table 3-3 identifies the allowable column/field type mapping when building a column
relationship.
GRPH
FIXPIC
National
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
FLTPIC
X
X
X
HEXADEC
X
X
X
BINARY
X
TIMESTZ
LVCHAR or
LV
TMSTMP
X
TIME
X
DATE
X
DECFLOAT
X
X
DOUBLE
X
REAL
X
DEC
INTEGER
X
BIGINT
SMALLINT
X
LVGRPH
X
VCHAR or
VC
VGRPH
CHAR or CH
TO 
GRPH
FROM

LVCHARor LV
Column/Field Types Mapping
VCHAR or VC
Table 3-3.
CHAR or CH
3-54
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
TIME
X
X
X
TMSTMP
X
X
X
X
X
TMESTZ
X
X
X
X
X
BINARY
X
X
X
Relationship Facilitator
FIXPIC
National
X
FLTPIC
X
HEXADEC
X
BINARY
X
TIMESTZ
X
TMSTMP
X
TIME
N (National) X
DATE
X
DECFLOAT
X
DOUBLE
X
REAL
X
DEC
X
BIGINT
X
INTEGER
X
SMALLINT
X
HEXADEC
LVGRPH
X
FROM

VGRPH
LVCHARor LV
X
TO 
GRPH
VCHAR or VC
Column/Field Types Mapping (Continued)
CHAR or CH
Table 3-3.
3-55
X
X
X
X
X
FLTPIC
X
FIXPIC
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
– 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) U16. See Figure 3-31 for a sample screen.
See Table 3-2 on page 3-53 for more information about data types displayed in this
column. Table 3-3 identifies the allowable column/field type mapping when building
a column relationship.
Notes:
1. If a DB2 column is a distinct type (UDT) File-AID/RDX displays the built-in
column type only.
2. Columns with Large Object Type (CLOB, BLOB, DBCLOB), XML and/or
ROWID column types cannot be part of an application relationship.
3-56
File-AID/RDX Reference
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.
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 3-40 on page 3-70 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 3-42 on page 3-71.
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 FileAID/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 3-32 on page
3-57).
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”).
Relationship Facilitator
3-57
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.
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 ARC identifies that the relationship includes selection criteria.
Selection Criteria Menu
The Selection Criteria Menu, shown in Figure 3-32, provides access to the selection
criteria options and formatted selection criteria specification.
Figure 3-32. 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 3-58.
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 3-61.
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 condition or several conditions. The conditions
can be ANDed together and several conditions separated by commas create
nested OR conditions within a set.
3-58
File-AID/RDX Reference
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 3-33, 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 3-33. View Criteria Screen


File-AID/RDX -------------------- View Criteria ----------Command ===>
Use END to exit View Display 
Row 1 to 20 of 35
SCROLL ===> CSR
******************************* TOP OF CRITERIA *****************************
DEFINE BLOCKS=SELECTION, 

DESCRIPTION1="Selection Criteria for Data Driven AR",



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
LAYOUT_DSNAME=,
LAYOUT_MBRNAME=,
Selection Criteria Options
The Selection Criteria Options screen, shown in Figure 3-34 on page 3-59, enables you to
control record selection based on starting record key, RBA, or RRN or record counts
which determine how selection processing is executed and when it stops. File-AID/RDX
determines whether an individual 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.
Relationship Facilitator
3-59
Figure 3-34. Selection Criteria Options

File-AID/RDX ---------Command ===> 
Selection Criteria Options
--------------------------
Specify Selection Criteria Options:
Start at the following record key
(both blank for start of dataset)


Starting record key
- OR Starting RBA or RRN
===>
Initial records to skip
===> 0
===> 
Subsequent Selection Interval:
Records to select
===> 1
Records to skip
===> 0

Number of records to search ===> ALL
OR at the following RBA or RRN
then skip this many records

then repeat the following
- select this many records
- then skip this many records
until
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.
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
3-60
File-AID/RDX Reference
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 3-35 shows an example of the effect of selection criteria options.
Figure 3-35. Selection Criteria Options Example

Initial records to skip
===> 4

Subsequent Selection Interval:
Records to select
===> 2
Records to skip
===> 3
Number of records to search ===> 10
then skip this many records

then repeat the following
- select this many records
- then skip this many records
until
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
Relationship Facilitator
3-61
When the values shown in Figure 3-36 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 3-36. Selection Criteria Options Example. Default - Examines All Records


Initial records to skip
===> 0
Subsequent Selection Interval
Records to select
===> 1
Records to skip
===> 0
Number of records to search ===> ALL
then skip this many records

then repeat the following
- select this many records
- then skip this many records
until
you have read this many records
Formatted Selection Criteria
The Formatted Selection Criteria screen, shown in Figure 3-37, 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, FileAID/RDX displays the Record Layout Specification screen, shown in Figure 3-37, for entry
of the required information.
Figure 3-37. 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
3-62
File-AID/RDX Reference
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.
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 3-67 for more information.
Notes:
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.
Relationship Facilitator
3-63
The syntax of the search data is important since File-AID/RDX interprets a comma as an
OR expression. In order to search for a comma as data, enclose the comma in double
quotes (",").
For relational operators BT and NB, enter two values separated by a colon (for example,
BT -100:+100). In most cases, you will have sufficient space to enter the two values.
You can select records with an invalid field value by entering the NV relational operator.
Records with a valid field value can be selected by entering the VA relational operator.
The VA and NV operators can be used for packed decimal, and zoned decimal fields.
Relational operators CO and NC can be used to scan a field within each record for the
presence or absence of a particular value. The value for which you want to search is
entered in the data value column. Trailing blanks in the data value are ignored and not
included in the search string. The CAPS primary command controls whether FileAID/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 3-38. 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 3-35 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
3-64
File-AID/RDX Reference
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.
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.
Note:
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.
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.
Relationship Facilitator
3-65
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.
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.
Note:
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.
RETURN : Returns to the Primary Option Menu.
RIGHT : Positions the display to the next criteria. Synonym for FORWARD.
UP : Scrolls up.
3-66
File-AID/RDX Reference
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 3-33 on
page 3-58.
Selection Criteria Considerations When Data Fields May Be Nonexistent
When defining selection criteria with reference to fields where data might not exist in
some records, File-AID/RDX does not exclude those records from the selection test.
A positive selection operator, such as EQ (equal to), indicates to select the record for
processing if the condition is true.
A negative selection operator, such as NE (not equal to), indicates to select the record for
processing if the condition is false.
Therefore, when using a negative selection operator, File-AID/RDX can select records that
don’t have data in those fields.
A typical case of this is seen with fields that are specified in a record layout with OCCURS
DEPENDING ON. Some records may have several occurrences of the field, while other
records may have only one or none.
For example, consider a record layout called CUSTOMER, having a field called BALANCE
defined with up to 12 occurrences, one per month, depending on another field, called
DURATION-OF-ACCOUNT. The 12th occurrence will not exist for customers who have
had accounts with the company for less than a year.
Example:
Assume you have the following 3 records in your file:
Alice Alvarez has been a customer for 5 months and had monthly balances of 1000, 2000,
3000, 500, and 0.
Bruce Bandler has been a customer for 3 months and had monthly balances of 1000,
2000, and 3000.
Carlos Cramer has been a customer for 5 months and had monthly balances of 1000,
2000, 3000, 0, and 0.
The records look like this:
Alice Alvarez,05,1000,2000,3000,500,0
Bruce Bandler,03,1000,2000,3000
Carlos Cramer,05,1000,2000,3000,0,0
You specify: Select all records with BALANCE(4) NOT EQUAL TO 500
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-OFACCOUNT variable in the selection criteria:
Specify: Select all records with DURATION-OF-ACCOUNT >= 5 AND BALANCE(4) NOT
EQUAL TO 500
Relationship Facilitator
3-67
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.
Field Mask
The “Field Mask Criteria” screen, shown in Figure 3-39, 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.
3-68
File-AID/RDX Reference
Figure 3-39. 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

*



Note:
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.
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.
Note:
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.
Note1: Signs (+,-) are excluded when masking numeric fields.
Note2: 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.
Relationship Facilitator
3-69
The original format will be replaced by MASK on the Formatted Criteria and
Selection criteria screens, when Field Mask is in effect.
Note:
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.
3-70
File-AID/RDX Reference
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.
Note:
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 3-23 on page 3-35.
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 3-40.
Refer to Table 3-3 on page 3-54 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 3-40. Relationships Screen — Creating a DB2 to MVS Relationship



File-AID/RDX ------- Column/Field Relationships --------------------------
Command ===>
SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands:
Field Number to Define Relationship D = Delete Relationship 
Parent:
DB2-LOCATION.TSOID01.CUSTOMER_TABLE
Dependent:
MVS-TSOID01.FARDX2.SAMP.SALEHIST
CMD Parent Columns
Type(Length) Mapped Fields
---- ------------------------------- ------------ ----------------------------1___ CUSTOMER_NUMBER
CHAR(6)
____ COMPANY_NAME
CHAR(30)
____ ADDRESS
CHAR(30)
____ CITY
CHAR(25)
____ STATE
CHAR(2)
____ ZIP_CODE
CHAR(9)
NMBR Dependent fields
Type(Length)
---- ------------------------------- ------------
1 SH-CUST-NO
CHAR(6)
2 SH-ORD-NO
CHAR(6)
RDXI753 I753 RDX was unable to find parent/child columns with the same name, 
type, and length.

6 SH-ORD-LINE-NO
DEC(5,0)
3. Press Enter.
If one or both parent and dependent fields in an MVS file contain subscripts, FileAID/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 3-79.
Relationship Facilitator
3-71
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 3-41 on page 3-71. See “Extended Column Relationship
Definition” on page 3-72 for more information about extended column
relationships.
Figure 3-41. 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







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

COMMAND ===>

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 3-42. 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 3-42. Relationships Screen — New DB2 Column to MVS Field Relationship Established.

File-AID/RDX ------- Column/Field Relationships -------------------------- 
Command ===>
SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands:
Field Number to Define Relationship D = Delete Relationship
Parent:
DB2-LOCATION.TSOID01.CUSTOMER_TABLE
Dependent: MVS-TSOID01.FARDX2.SAMP.SALEHIST
CMD Parent Columns
Type(Length)
---- ------------------------------- -----------____ CUSTOMER_NUMBER
CHAR(6)
- - - - - - - - - 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)
Mapped Fields
-----------------------------
1/SH-CUST-NO
- - - - - - -
3-72
File-AID/RDX Reference
4. Repeat steps 1-3 for all columns/fields that you want to include in the application
relationship for the pair of objects.
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 3-43 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 3-43. 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.
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
3-55 on page 3-81 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.
Relationship Facilitator
3-73
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
3-55 on page 3-81 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).
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:
3-74
File-AID/RDX Reference
–
–
–
–
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).
• 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 3-44)
to create a DB2 to DB2 column relationship between two columns with data types of
CHAR and lengths of 6.
Relationship Facilitator
3-75
Figure 3-44. Relationship Screen with column-number command


File-AID/RDX ------------- Column Relationships ---------------------------- 
Command ===>
SCROLL ===> PAGE
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands:
Column Number to Define Relationship D = Delete Relationship 
Parent:
DB2-LOCATION.FRSAMP.CUSTOMER_TABLE
Dependent: DB2-LOCATION.FRSAMP.ORDER_TABLE
CMD Parent Columns
Type(Length) Mapped Fields
---- ------------------------------- ------------ ----------------------------2___ CUSTOMER_NUMBER
CHAR(6)
____ COMPANY_NAME
CHAR(30)
____ ADDRESS
CHAR(30)
____ CITY
CHAR(25)
____ STATE
CHAR(2)
____ ZIP_CODE
CHAR(9)
____ COUNTRY
CHAR(20)
NMBR Dependent Columns
Type(Length)
---- ------------------------------- ------------
1 ORDER_NUMBER
CHAR(6)
2 CUST_NUM
CHAR(6)
3 SOC_SEC_NUM
CHAR(11)
4 CREDIT_CARD_NUM
CHAR(16)
5 ORD_TYPE
CHAR(8)
6 ORD_DATE
DATE
The Extended Column Relationship Definition pop-up window would be displayed as
shown in Figure 3-45 with default values for starting position and length prefilled.
Figure 3-45. 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

Note:
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 3-46)
to create a DB2 to KEY relationship (using root segment, not segment layout) between
columns with data types of CHAR and different lengths.
3-76
File-AID/RDX Reference
Figure 3-46. Column/Segment Relationships Screen with Segment-Number command

File-AID/RDX --------- Column/Segment Relationships ------------------------ 
Command ===>
SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands:
Root number to Define Relationship D = Delete Relationship 
Parent:
DB2-LOCATION.FRSAMP.CUSTOMER_TABLE
Dependent: KEY-TSOID01.FISAMP.DBDLIB(PCUST)
CMD Parent Columns
Type(Length) Mapped Fields
---- ------------------------------- ------------ ----------------------------1___ CUSTOMER_NUMBER
CHAR(6)
____ COMPANY_NAME
CHAR(30)
____ ADDRESS
CHAR(30)
____ CITY
CHAR(25)
____ STATE
CHAR(2)
____ ZIP_CODE
CHAR(9)
____ COUNTRY
CHAR(20)
____ AREA_CODE
CHAR(3)
____ TELEPHONE_NUM
CHAR(7)
____ CONTACT_NAME
CHAR(30)
____ CONTACT_TITLE
CHAR(30)
____ CONTACT_ADDR
CHAR(30)
NMBR Dependent Root segment
Type(Length)
---- ------------------------------- ------------
1 CUST010
CHAR(6)
The Extended Column Relationship Definition pop-up window would be displayed as
shown in Figure 3-47 with default values for starting position and length prefilled.
Figure 3-47. 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 3-48 on page 3-77 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.
Relationship Facilitator
3-77
Figure 3-48. 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 3-49).
Figure 3-49. Partial Column/Segment Relation Established

File-AID/RDX --------- Column/Segment Relationships ------------------------
Command ===>
SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands:
Root Number
to Define Relationship D = Delete Relationship
Parent:
DB2-LOCATION.FRSAMP.CUSTOMER_TABLE
Dependent: KEY-TSOID01.FISAMP.DBDLIB(PCUST)
CMD Parent Columns
Type(Length)
---- ------------------------------- -----------____ CUSTOMER_NUMBER
CHAR(6)
- - - - - - - - - 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)
Mapped Fields
-----------------------------
1(1,2,5)/CUST010
- - - - - - -
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 3-50) to
create a DB2 to MVS relationship between a column with data type of DECIMAL and a
field with data type CHAR.
3-78
File-AID/RDX Reference
Figure 3-50. Column/Field Relationships Screen Mapping DECIMAL to CHAR


File-AID/RDX ---------- Column/Field Relationships -------------------------
Command ===>
SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands:
Field Number to Define Relationship D = Delete Relationship 
Parent:
DB2-LOCATION.FRSAMP.ORDER_TABLE
Dependent: MVS-FR.BASE.V2R0M0.SAMP.INVOICE
CMD Parent Columns
Type(Length) Mapped Fields
---- ------------------------------- ------------ -----------------------------
____ SOC_SEC_NUM
CHAR(11)
____ CREDIT_CARD_NUM
CHAR(16)
____ ORD_TYPE
CHAR(8)
____ ORD_DATE
DATE
____ ORD_STAT
CHAR(8) 
10__ ORD_AMOUNT
DEC(9,2)
____ ORD_DEPOSIT
DEC(9,2)
NMBR Dependent fields
Type(Length)
---- ------------------------------- ------------
8 IM-INVOICE-TOT
DEC(9,2)
9 IM-SHIP-CHG
DEC(7,2)
10 IM-SHIP-VIA
CHAR(20)
11 IM-SHIP-CODE
CHAR(4)
12 IM-SHIP-TO-CUST
CHAR(6)
13 IM-ORDER-NO
CHAR(6)
The Extended Column Relationship Definition pop-up window would be displayed as
shown in Figure 3-51 with default values for starting position and length prefilled:
Figure 3-51. 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 3-52 on page 3-79 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.
Relationship Facilitator
3-79
Figure 3-52. 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.
Specify MVS Field Subscripts
The Specify MVS Field Subscripts pop-up window shown in Figure 3-53 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 3-53. Specify MVS Field Subscripts for Parent Field
Extended Field
File-AID/RDX
COMMAND ===>
Parent
:
Field Name:
Data Type:
Subscript 1
Relationship Definition

Specify MVS Field Subscripts
TSOID01.FASAMP.INVFILE
INV-WAREHOUSE
CHAR(3)
===>
(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.
3-80
File-AID/RDX Reference
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.
After you press Enter, you continue either with the Dependent Field Subscripts
window (Figure 3-54 on page 3-80), if the dependent field contains subscripts, or the
Extended Field Relationship Definition window (Figure 3-55 on page 3-81), if the
parent and dependent field types qualify for Extended Field Relationship Definition,
or return directly to the Field/Column Relationship screen (see Figure 3-56 on page
3-81) when the relationship definition is completed.
Figure 3-54. Specify MVS FIeld Subscripts for Dependent Field
Extended Field
File-AID/RDX
COMMAND ===>
Dependent :
Field Name:
Data Type:
Subscript 1
Relationship Definition 
Specify MVS Field Subscripts
TSOID01.FASAMP.INVFILE
INV-STATUS
CHAR(6)
===>
(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.
After you press Enter, you continue either with the Extended Field Relationship
Definition window (Figure 3-55 on page 3-81), if the parent and dependent field types
qualify for Extended Field Relationship Definition, or return directly to the Field/Column
Relationship screen (see Figure 3-56 on page 3-81) when the relationship definition is
Relationship Facilitator
3-81
completed.
Figure 3-55. 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 3-72 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 3-56.
Figure 3-56. Extended Field Relationship with Defined Subscripted Relationship

File-AID/RDX -------- Field Relationships ----------------------------------
COMMAND ===>
SCROLL ===> CSR
Primary Command: CONDitional relationships, SUGgest Relationships
Line Commands:
Field Number to Define Relationship D = Delete Relationship
Parent:
MVS-TSOID01.FASAMP.INVFILE
Dependent: MVS-TSOID01.FASAMP.INVFILE
CMD Parent fields
Type(Length)
---- ------------------------------- -----------____ 5/INV-WAREHOUSE(1)
CHAR(3)
- - - - - - - - - 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) 
Mapped fields
-----------------------------
6(1,3,1)/INV-STATUS(1)
- - - - - - 











See “Relationships” on page 3-50 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.
3-82
File-AID/RDX Reference
Allocate Relationship File
The “Allocate Relationship File” screen shown in Figure 3-57 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 3-57. Allocate Relationship File





File-AID/RDX ----------Command ===> 
Allocate Relationship File
---------------------
New VSAM Component names:
Cluster
===> 'FRSAMP.R44.RELATION'
Data Component LLQ
===> DATA

Index Component LLQ
===> INDEX 
Data component . . : 'FRSAMP.R44.RELATION.NEW.DATA'
Index component . .: 'FRSAMP.R44.RELATION.NEW.INDEX'
Specify SMS Class Information:
Storage ===> S
Data
Space Allocation:
Volume serial
Units
Primary
Secondary
DATA Component
===>
===> TRK
===> 1
===> 1
===>
Management


===> T 
KSDS INDEX Component (Blank for default)
===>

===>
(TRKs; CYLs; RECs; K; M)
===>
(Amount in above units)
===>
(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 3-83).
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.
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.
Relationship Facilitator
Note:
3-83
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
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 3-58 on page 3-84 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.
3-84
File-AID/RDX Reference
Figure 3-58. Batch RI Load
--------------- Row 1 to 1 of 1 
SCROLL ===> CSR

Primary Commands: JCL view, GO to submit job

Line Commands:
D Delete


Specify Batch Parameters:

Relationship File Name ===> 'TSOID01.FRSMP491.RELATION'


SSID ===> DSN
Sysout Class ===> *


Filter List (optional):
Cmd Complete CREATOR ID

--------------------------------------------------
'

******************************* Bottom of data ********************************





File-AID/RDX
COMMAND ===>
----------------
Batch RI Load
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.
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 3-59 on page 3-85). FileAID/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.
Relationship Facilitator
3-85
Line Command
The following File-AID/RDX-specific line command is valid on this screen:
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.
Note:
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 3-6.
Figure 3-59 on page 3-85 shows a sample JCL.
Figure 3-59. RI load Batch Job JCL
//RIUPssid
//STEPLIB
//
//
//SYSOUT
//SYSUDUMP
//SYSPRINT
//RDXSQLCD
//RDXMLIB
//EXTPARMS
//RDXPARMS
RELDSN
CREATOR
TBNAME
GO
CREATOR
TBNAME
GO
EXEC PGM=XFREXEC, REGION=4096K,PARM=(FR,1,B)
DD DSN=File-AID-Customized-load-library,DISP=SHR
DD DSN=File-AID-Target-load-library
DD DSN=DB2-load-library
DD SYSOUT=*
DD SYSOUT=*
DD SYSOUT=* 
DD SYSOUT=* 
DD DSN=File-AID-message-library,DISP=SHR
DD DSN=TSOID01.prefix.PARMS.Dnnnnnn.Tnnnnnn.suffix,DISP=SHR
DD *
‘relationship-file’
creator id
table name
creator id
table name
XFREXEC is the File-AID/RDX program name.
3-86
File-AID/RDX Reference
The parameter information in the PARM field in the EXEC statement must have the
following format:
Default
Value
Length
Product
FR
2
FR : File-AID/RDX
Option
1
1
File-AID/RDX option number.
Operating Mode
B
1
B : Batch
Parameter
Description
The following DD statements are required:
DD Statement
Description
STEPLIB
Customized and Target File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD);
DB2 load 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 4-131).
RDXPARMS
RELDSN -- The File-AID/RDX relationship file to be updated. 
CREATOR -- Creator ID to limit relationships to be updated. (Optional)
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
Code
0
Description
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.
Relationship Facilitator
3-87
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" 
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 3-60 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 3-60. Formatted Relationship Report Screen

File-AID/RDX --------- Formatted Relationship Report ------------------------- 
Command ===> 
Specify Relationship File:
File Name ===> FRSAMP.RELATION
Use this screen to specify the relationship file for which you want to generate a report.
The body of the Formatted Relationship Report screen consists of the following field:
File Name : Specify the name of the relationship file for which you want to generate a
formatted report.
Print Options Screen
The Print Options screen shown in Figure 3-61 on page 3-88 is displayed when you
complete the Formatted Relationship Report screen and press Enter.
3-88
File-AID/RDX Reference
Figure 3-61. Print Options Screen







File-AID/RDX ----------------- Print Options --------------------------------- 
Command ===> 

Maximum lines per page ===> 55
(20-99)
Specify Print Options:
Printer Destination
Sysout Class
- OR -
"TO" Print file
VOLSER
Disposition
(NEW, OLD, or MOD)
===> LOCAL
===> R
===>
===>
===>

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
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).
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.
Relationship Facilitator
3-89
Edit Print JCL
The ISPF/PDF Edit screen shown in Figure 3-62 is displayed when you pressed Enter on
the Print Options screen.
Figure 3-62. 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. 
******
000001
000002
000003
000004
000005
000006
000007
000008
000009
000010
000011
000012
000014
000013
000015
000016
***************************** Top of Data ******************************
//*Your Jobcard information
//*
//*
//*
XFRJRD00
//*********************************************************************
//* PRINT FORMATTED REPORT
//*********************************************************************
//RELPRINT
EXEC PGM=XFRPRINT
//STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ160.CXVJLOAD
//
DD DISP=SHR,DSN=CPWR.MXVJ160.SXVJLOAD
//SYSUDUMP DD SYSOUT=*
//SYSTERM DD SYSOUT=*
//SYSOUT
DD SYSOUT=*
//SYSPRINT DD SYSOUT=(A),DEST=LOCAL,HOLD=YES 
//RDXPARMS DD *
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 3-63 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.
3-90
File-AID/RDX Reference
Figure 3-63. Relationship File - Related Objects Report
File-AID/RDX
16.3
Relationship File - Related Objects Report
PAGE 1
DATE 2009-09-06 
Relationship File. . : 'TSOID01.FRSAMP.RELATION'
TIME 16:01:00

Type Parent to Dependent Relationships

---- ------------------------------------------------------------------------------------------------------------------------------
Parent. . .: D-LOCATION.TSOID01.ACT

RI
Dependent: D-LOCATION.TSOID01.PROJACT

RELNAME: RPAA 
Columns: Parent = ACTNO
SMALLINT
Dependent = ACTNO
SMALLINT
Parent. . .: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.DEPT_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128

RI
Dependent: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.DEPT_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128

RELNAME: RDD______A_________B_________C_________D_________E_________F_________G_________H_________I_________J_________K__
_____L_____128

Columns: Parent = DEPTNO___A_________B________30 CHAR(3)
Dependent = ADMRDEPT_A_________B________30 CHAR(3)


AR
Dependent: I-FR.IXPSAMP.DBDLIB(PORDR)

RELNAME: CUSTOMER-ORDER RELATION KEY

Columns: Parent = DEPTNO___A_________B________30 CHAR(1,3)
Dependent = ORDR01
CHAR(1,3)


Parent. . .: D-DSNLOCAT.FARDX.CONTACT_TABLE

AR-C Relationship Condition:

SELECT SET=1,LAYOUT=CONTACT_TABLE-TBL

IF

FIELD_NAME=STATE,

POSITION=130,LENGTH=2,OPERATOR=EQ,

TYPE=T,VALUE=CA


Dependent: D-DSNLOCAT.FARDX.CUSTOMER_TABLE

RELNAME: CONDITIONAL AR

Columns: Parent = CUSTOMER_NUMBER
CHAR(6)
Dependent = CUSTOMER_NUMBER
CHAR(6)

Parent. . .: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE

RI
Dependent: D-DSNLOCAT.FRSAMP.CONTACT_TABLE

RELNAME: CONTCUST

Columns: Parent = CUSTOMER_NUMBER
CHAR(6)
Dependent = CUSTOMER_NUMBER
CHAR(6)


AR
Dependent: D-DSNLOCAT.FRSAMP.ORDER_TABLE

RELNAME: CUSTOMER-ORDER RELATIONSHIP 
Columns: Parent = CUSTOMER_NUMBER
CHAR(6)
Dependent = CUST_NUM
CHAR(6)

File-AID/RDX 16.3
Relationship File - Related Objects Report
PAGE 3
DATE 2009-09-06 
Relationship File. . : 'TSOID01.FRSAMP.RELATION'
TIME 16:01:00

Type Dependent to Parent Relationships

---- ------------------------------------------------------------------------------------------------------------------------------

Dependent .: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.PROJ_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128

RI
Parent: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
________K_________L_____128.DEPT_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128


Dependent .: D-DSNLOCAT.FRSAMP.CONTACT_TABLE

RI
Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE


Dependent .: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

RI
Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE


Dependent .: D-DSNLOCAT.FRSAMP.ORDER_LINE_TABLE

RI
Parent: D-DSNLOCAT.FRSAMP.PART_TABLE


Dependent .: D-DSNLOCAT.FRSAMP.ORDER_TABLE

AR
Parent: D-DSNLOCAT.FRSAMP.CUSTOMER_TABLE


Dependent .: D-DSNLOCAT.FRSAMP.ORDER_TABLE

AR
Parent: D-DSNLOCAT.FRSAMP.ORDER_TABLE


Dependent .: D-DSNLOCAT.FRSAMP.SUPPLIER_TABLE

RI
Parent: D-DSNLOCAT.FRSAMP.PART_TABLE


Dependent .: I-FR.IXPSAMP.DBDLIB(PORDR)

Parent: D-DSNLOCAT.FADB2610_A_________B_________C_________D_________E_________F_________G_________H_________I_________J_
AR
________K_________L_____128.DEPT_____A_________B_________C_________D_________E_________F_________G_________H__
_______I_________J_________K_________L_____128


Dependent .: M-TSOID01.FRSAMP.CONTACTT

AR
Parent: M-TSOID01.FRSAMP.CUSTOMER


Dependent .: M-TSOID01.FRSAMP.ORDERLIN

AR
Parent: M-TSOID01.FRSAMP.ORDERTAB


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.
Relationship Facilitator
3-91
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:
DMI-
DB2 object
MVS object
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.
3-92
File-AID/RDX Reference
4-1
Chapter 4.
Extract
Chap 4
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
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 Chapter 2, “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 4-131 and Chapter 5, “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;
• a new or existing member in a new or existing PDS
Note:
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).
4-2
File-AID/RDX Reference
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.
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 userdefined application relationships (AR) as defined in the relationship file. In order for FileAID/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 4-1 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.
Figure 4-1. Sample Tables and Relationships
Extract
4-3
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 FileAID/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 descendent path = Y (see Figure 4-2):
Definition : Extract selected rows from the driving object and all of the dependents of
the driving object and their dependents.
1. The ORDER_TABLE - ORDER_LINE_TABLE relationship can only be navigated via the
direct descendent 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.
Note:
When your profile has navigation criteria Direct set to C or P (see also
“Direct” on page 2-9), 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.
4-4
File-AID/RDX Reference
Figure 4-2. Global Navigation Controls - Direct = Y
Parent path = Y (Direct: Y Parent: Y Sibling: N Indirect: N) (see Figure 4-3):
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.
Note:
When your profile has navigation criteria Direct set to P (see also “Direct”
on page 2-9), 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.
Figure 4-3. Global Navigation Controls - Direct = Y, Parent = Y=
Extract
4-5
Siblings path = Y (Direct: Y Parent: Y Sibling: Y Indirect: N) (see Figure 4-4):
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).
Figure 4-4. Global Navigation Controls - Direct = Y, Parent = Y, Sibling = Y=
Indirect path = Y (Direct: Y Parent: Y Sibling: Y Indirect: Y) (see Figure 4-5):
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).
4-6
File-AID/RDX Reference
Figure 4-5. 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 4-42 on page 4-56 through
Figure 4-53 on page 4-73). 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 value sets the cycle count for each relationship in the
extract.
2. Relationship Level
The cycle count can be set for each individual relationship in the extract.
Cycle count only applies to downward navigation via the sibling and
Extract
4-7
indirect path. 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 times an object is accessed during
the 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.
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
4-8
File-AID/RDX Reference
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.
Note:
Data Disguise does not support this function. If the extract request is to be
disguised, make sure that disguise criteria has been defined for the new DB2
objects as data disguise criteria is defined for DB2 objects using the three part
object name location.creator.object and their relationships must be defined in the
relationship file.
The following scenario illustrates the process of how to extract data from one subsystem
using relationship information from a second subsystem to populate tables in a third
subsystem. In Table 4-1, there are three different subsystems (PROD, TEST, and ACCEPT).
Each entry in the columns represents the name of a table.
Table 4-1.
DB2 Subsystems
PROD
ACCEPT
TEST
P.CUSTOMER
A.CUSTOMER
T.CUSTOMER
P.ORDER
A.ORDER
T.ORDER
There is a relationship definition for the pair of tables CUSTOMER and ORDER in the
production subsystem, called PROD in the example, but none in the acceptance
subsystem. You want to use this relationship information as the model to extract data
from the CUSTOMER and ORDER tables residing in the acceptance subsystem (ACCEPT)
to populate the CUSTOMER and ORDER tables in the test subsystem (TEST).
To perform this extract:
1. specify A.CUSTOMER to drive the extract process.
Figure 4-6. Driving Object - DB2

File-AID/RDX ------------- DB2 Driving Object -------------------------------
Command ===>


Primary commands: MVS object, REFerence, REQuest 

Specify table to drive extract process:

SSID
===> ACPT
Location
===> LOCATION
(* or pattern for selection list)
Creator
===> A
(* or pattern for selection list)
Table Name
===> CUSTOMER
(* or pattern for selection list)
Relationship Information:
2. select the P.CUSTOMER relationship definition, if more than one relationship
definition exists for the Table Name value (CUSTOMER).
Extract
4-9
Figure 4-7. Relationship Listing
File-AID/RDX ------------Command ===>
DB2 Driving Object
-------------------------------
Relationship Listing
Primary Comma
Command ===>
Specify table
SSID
Location
Creator
Table Name

Row 1 to 3 of 3
SCROLL ===> CSR
Multiple relationships exist for object: CUSTOMER
Enter 'S' to select relationship definition for extract
Relationship
File Name o

CMD Object
SSID
--- -------------------------------------------------- ---_ LOCATION.Z.CUSTOMER
DVLP
S LOCATION.P.CUSTOMER
PROD
_ LOCATION.T.CUSTOMER
TEST
********************** Bottom of data ***********************















3. specify the P.CUSTOMER to P.ORDER relationship definitions from the PROD
subsystem as the extract criteria for the tables in the ACCEPT subsystem and exclude
the other relationships.
Figure 4-8. Relationship Navigation Criteria
File-AID/RDX ------Command ===>
Relationship Navigation Criteria ---------- Row 1 from 5
Scroll ===> PAGE
Primary Commands: EXclude/Unex, Change, Find, Hide, FILter, CHEck, SIze, SOrt
VIew, STATus, SAMple, NAVigation, VALidate, GRaphic, REPort
Line Commands: X = Exclude
U = Unexclude
I = Info
Driving Object: A.CUSTOMER

SSID: ACPT Location: LOCATION
Navigation Criteria
Seq Object Name
Dir Par Sib Ind Status
---- ---------------------------------------------- --- --- --- --- ---------X001 A.CUSTOMER
Y
A.CONTACT
CONTCUST
0002 A.CUSTOMER
Y
A.ORDER
Customer to Order AR
X003 A.ORDER
Y
A.ORDER_LINE
ORDLORD
X004 A.PART
Y
N
A.ORDER_LINE
ORDLPRT
X005 A.PART
N
A.SUPPLIER
SUPPPART
******************************* Bottom of data ********************************



















4. specify T as Creator ID and TEST as subsystem ID for the tables into which to load
the extracted data (the target tables).
Note:
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.
4-10
File-AID/RDX Reference
Figure 4-9. 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:
/ DB2 Creator
===> T
_ DB2 Index name prefix
===>
_ DB2 Index name suffix
===>

_ MVS high level qualifier ===> TSOID01
_ MVS file name suffix
===> NEW

_ Revert to source names
===>

(/ entry to apply modification)
(Creator for ALL DB2 objects)

(HLQ for ALL MVS objects)

(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 4-10 on page 4-11 for a diagram
illustrating the use of relationships across subsystems.
Extract
4-11
Figure 4-10. Extracting Data From Subsystem ACCEPT Based on Relationships in Subsystem PROD
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 4-24 on page 4-32. 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.
Note:
If there are no Disguise rules created for the new object names, the Disguise rules
for the original objects will be applied.
4-12
File-AID/RDX Reference
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 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 7-2).
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 7-1). 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 4-53). Image copy extracts do not include Temporal Table support.
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.
Note:
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 FileAID/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:
• specify that File-AID/RDX create a COBOL Record Layout File during the extract (see
also “Create layouts” on page 4-129)
• do not select the compress option for the extract or decompress the file beforehand
(see also “Compress” on page 4-125)
Extract
• sort the extract file using sample JCL provided in the sample file
‘hlq.CPWR.MXVJ160.SXVJSAMP(FAEXSORT)’
Refer to File-AID/EX’s documentation for transfer procedures.
4-13
4-14
File-AID/RDX Reference
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 2-11) 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 2-11) 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.
Note:
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 4-20).
Extract - DB2 Driving Object
The “Extract - DB2 Driving Object” screen shown in Figure 4-11 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.
Figure 4-11. Extract - DB2 Driving Object
File-AID/RDX
OPTION ===>
-----------
Extract - DB2 Driving Object
----------------------
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)
SELECT FROM Temporal Table
===>
(Y = Yes; N = No)
*None*

Specify Extract "TO" File Information:

File name
===> FRSAMP.EXTRACT

Format Unicode Data
===>
(1 = Extract as Unicode; 2 = Convert Unicode)
Edit Data Privacy Spec ===>
(Y = Yes; N = No)
*DCF*

Relationship Information:
File name or pattern ===> 'TSOID01.FRSAMP.RELATION'

The *Current Values* indicators to the right of certain extract option fields are display
fields only and are updated upon return from each of the extract options to reflect the
current status and value for the option.
The body of this screen consists of the following fields:
Extract
4-15
Specify Table To Drive Extract Process From Area:
Use the fields in this area to specify the DB2 table for which you want to retrieve
relationship information from the relationship file so you can extract related data. When
specifying patterns in the fields, File-AID/RDX searches the relationship file and presents
selection lists.
SSID : Displays the current DB2 subsystem ID as specified in your profile. Type over this
field to connect to a new DB2 subsystem. If you leave the Location field blank, the
table you specify to drive the extract must exist in the DB2 subsystem displayed here.
Location : Specify the location ID of the table you want to drive the extract if it resides
in a remote DB2 subsystem. The location you enter must be defined in the DB2
system catalog table, SYSIBM.LOCATIONS.
Leave this field blank if the table you want to drive the extract is in the DB2
subsystem in the SSID field.
Note:
The “Extract from Image Copy” option is not available when extracting from
a remote location. (see also “Extract from Image Copy” on page 4-52).
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 1-4). 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 4-17 and
“Use of Aliases and Synonyms” on page 4-29. Also refer to “Relationship Listing
Window for DB2 Objects” on page 4-29 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 1-4). 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 4-70 on page 4-97) 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.
SELECT FROM Temporal Table : Enter Yes if you want to specify or modify a timeperiod and date/timestamps for Temporal Tables or Temporal Views. File-AID/RDX
will display the “SELECT FROM Temporal Table” screen (refer to Figure 4-41 on page
4-54) 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.
4-16
File-AID/RDX Reference
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 4-41 on page 4-54).
Notes:
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
1-23 and “File-AID/RDX Extract File” on page 4-154 for more information on the
extract file. If you specify a pattern, select a sequential file from the “Catalog Utility
File List” (see Figure 4-33 on page 4-40) 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 2-10).
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 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 4-89 on page 4-127) 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 4-33
on page 4-40).
Note:
If you leave this field blank, File-AID/RDX will perform a single table extract.
Extract
4-17
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 2-11 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 4-17.
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.
Notes:
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.
Extract - MVS Driving Object
The “Extract - MVS Driving Object” screen shown in Figure 4-12 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.
4-18
File-AID/RDX Reference
Figure 4-12. Extract - MVS Driving Object
File-AID/RDX ----------OPTION ===>
Extract - MVS Driving Object
----------------------
SITE Profile: RDXQUICK

Primary Commands: DB2 driving object, Edit JCL, Go to submit job


Specify file to drive the extract process from:

File
===> FRSAMP.ORDERTAB


Optional File Information:

Record layout usage ===>
(S = Single; X = XREF)

Record layout file
===>

Member name
===>
(Blank or pattern for member list)

XREF file
===>

Member name
===>
(Blank or pattern for member list)


Specify Extract Options:
Edit Object Selection Criteria ===> N
(Y = Yes; N = No)
*Defined*

Specify Extract "TO" File Information:

File Name
===> FRSAMP.EXTRACTM

Edit Data Privacy Spec ===>
(Y = Yes; N = No)
*DCF*

Relationship information stored in:

File Name
===> FRSAMP.RELATION 
The *Current Values* indicators to the right of certain extract option fields are display
fields only and are updated upon return from each of the extract options to reflect the
current status and value for the option.
The body of this screen consists of the following fields:
Specify File To Drive The Extract Process From Area
Use the fields in this area to specify the MVS file for which you want to retrieve
relationship information from the relationship file so you can extract related data. When
specifying patterns in the fields, File-AID/RDX searches the relationship file and presents
selection lists.
File : Specify the MVS file name of the object from which you want to extract related
data. To view a list of files, specify a pattern. Valid pattern character is * (see “Pattern
Characters” on page 1-4). If you specify a pattern, the “Catalog Utility File List”
shown in Figure 4-33 on page 4-40 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 4-40 where you can
decide whether to continue with a single object extract or start a new extract request.
Note:
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 1-4). If you specify a pattern,
select a file from the “Catalog Utility File List” as shown in Figure 4-33 on page 4-40.
Extract
4-19
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 1-4). If you specify a pattern, select a file from the
“Catalog Utility File List” as shown in Figure 4-33 on page 4-40.
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 4-35 on page 4-42.
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 4-74 on page 4-103) 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.
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 1-23 and “File-AID/RDX Extract File” on page 4-154 for more information. If
you specify a pattern, select a sequential file from the “Catalog Utility File List” (see
Figure 4-33 on page 4-40) 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 4-89 on page 4-127).
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 4-33 on
page 4-40).
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 4-14.
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 2-11 is set to Y.
4-20
File-AID/RDX Reference
Extract Reference List
The “Extract Reference List” screen shown in Figure 4-13 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”.
Note:
If your reference list is empty, File-AID/RDX will display the “Request File
Member List” screen, listing the members of the request file specified in your
profile, or if none is in your profile, display either the “DB2 Driving Object” or
“MVS Driving Object” screen so you can create a new extract request.

The reference list is stored in your personal USER profile. If your USER profile file
(‘userid.midlevlqualifier.PROFILE’) does not exist, File-AID/RDX will create your
USER profile when you are saving an extract or load request.
You can also create a new extract request with the NEW command, or open a saved
extract request file with the REQUEST command. Use the REQUEST command to open
extract criteria files created with File-AID/RDX prior to Release 3.0.
Refer to “Option G—Global User Defaults” on page 2-26 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 4-13. Extract Reference List
------- Row 1 to 6 of 6 
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
File-AID/RDX ------------Command ===>

Extract Reference List
Request Extract File Name
RT L YY/MM/DD
-------- ----------------------------------------------------- -- - -------- 
_ MVSSAMP TSOID01.FRSAMP.REQUEST
E
11/01/03
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT
E
01/02/18
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM
E
01/02/04
_
TSOID01.FRSAMP.EXTRACT
EL L 01/02/01
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT
E
01/01/31
_ DIEBLD
TSOID01.FRSAMP.CUST.EXTRACT.NODB2(EXTCUST)
EL L 00/12/24
_ MVORDR
TSOID01.FRSAMP.EXTRACT.ORDER
E
99/08/24
******************************* Bottom of data ********************************
The lower part of the screen displays a listing of your recently referenced extract requests.
Use one of the line commands to either resubmit one of the extract requests or model a
new request after it.
Extract
4-21
Request : Name of the extract request (member name in the saved extract request file or
extract criteria file). A blank entry means the request was saved to a sequential file.
Extract File Name : Name of the file containing the extracted data. If saved to a PDS the
member name is displayed in parentheses.
RT : Request Type. Identifies the extract request type:
E : 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.
L : 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:
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.
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 4-14 for an example.
Figure 4-14. Request Details
File-AID/RDX ---------------- Request Details -------------------------------
Command ===>

Request Information:

Request File Name . : TSOID01.FRSAMP.REQUEST

Member Name . . . . : MVSSAMP

Request Type . . . . : EXTRACT

Description . . . . : MVS

Reference Date . . . : 2011/01/03
Reference Time: 00:00:07 

Driving Object Information:

SSID . . . . . . . . :

Name . . . . . . . . : MVS - TSOID01.FRSAMP.ORDERTAB


Extract Information:

Extract File Name . : TSOID01.FRSAMP.OUT

Summary File Name . : TSOID01.FRSAMP.TAPECNTL

Disguise Control File:

Repository Name:

Project Name:

Extract Date . . . . : 2011/01/03
Extract Time : 12:00:01 

Relationship Information:

File Name . . . . . : TSOID01.FRSAMP.RELATION

L (Lock) : Protects this entry from rolling off the extract reference list.
M (Modify) : Selects this extract request, displays the “Modify Extract Request” panel for
you to change or “clone” an existing extract request. See also “Modify Extract
Request” on page 4-32.
4-22
File-AID/RDX Reference
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 4-44.
Note:
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 4-134) where you
review and modify the extract JCL.
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 4-15 for an example. Detail
is a toggle switch so enter Detail again to return to the original format.
Figure 4-15. Extract Reference List - DETAIL Screen
File-AID/RDX ------------Command ===>

Extract Reference List
--------- Row 1 to 6 of 6
Scroll ===> CSR 

Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go
C = Change Selection & Go S = Select M = Modify
I = Info D = Delete from list
L = Lock
U = Unlock
Request Extract File Name
RT L YY/MM/DD
-------- ----------------------------------------------------- -- - --------
_ MVSSAMP TSOID01.FRSAMP.EXTRACT
E
11/01/03
Description: MVS 
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT
E
04/02/18
Description: This extract uses Acct number 
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM
E
04/02/04
Description: DB2-FR.PRODUCT_CONTRACT 
_
TSOID01.FRSAMP.EXTRACT
EL L 04/02/01
Description: This extract selects region 10 
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT
E
04/01/31
Description: MVS-FRSAMP.CUSTOMER 
_ MVORDR
TSOID01.FRSAMP.EXTRACT.ORDER
E
99/08/24
Description: MVS-FRSAMP.ORDER 
******************************* Bottom of data ********************************
FIND (F) : Searches the list for the specified string and scrolls the list to display the first
matching entry at the top of the displayed entries. Use RFind to repeat the search.
Find looks for matches in the request detail information for each list entry. When a
match is found and is not visible in the displayed row, use the I (info) line command
to display the detail information.
NEW (N) : Starts a new extract request based on your current profile. File-AID/RDX
displays either the DB2 or MVS Driving Object screen as set in your profile (see Figure
4-11 or Figure 4-12).
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 4-11 for more information.
File-AID/RDX opens the request file specified in your current profile or prompts for
the file name when none is in your profile.
Extract
4-23
SIZE (S) : Increases the scrollable area to display more entries at a time by hiding some of
the screen header lines. See Figure 4-16 for an example. Size is a toggle switch, so
enter Size again to return to the original format.
Figure 4-16. Extract Reference List - Size Screen
File-AID/RDX ------------- Extract Reference List --------- Row 1 to 6 of 6
Command ===>
SCROLL ===> CSR 
Request Extract File Name
RT L YY/MM/DD
_ MVSSAMP TSOID01.FRSAMP.REQUEST
E
11/01/03
_ SAMPMIN TSOID01.FRSAMP.CUST.EXTRACT
E
04/02/18
_ DIEBLDX TSOID01.FRSAMP.CUST.EXTRACT.DB2VSAM
E
04/02/04
_
TSOID01.FRSAMP.EXTRACT
EL L 04/02/01
_ DIEBLD1 TSOID01.FRSAMP.EXTRACT
E
04/01/31
_ DIEBLD
TSOID01.FRSAMP.CUST.EXTRACT.NODB2(EXTCUST)
EL L 03/12/24
_ MVORDR
TSOID01.FRSAMP.EXTRACT.ORDEER
E
03/08/24
****************************** Bottom of data ********************************
4-24
File-AID/RDX Reference
Request File Member List
The “Request File Member List Screen” shown in Figure 4-17 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
Note:
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 4-17. Request File Member List Screen


File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8
Command ===>
Scroll ===> CSR

Primary commands: New, Find, Size, REFerence
Line commands: G = Go C = Change Selection & Go S = Select M = Modify SSID
D = Delete R = Rename
Request File ===> FRSAMP.EXTCRIT

Member
Description
Changed
-------- -------------------------------------------------- ---------- 
_ DB2VSAM
db2 to vsam extract
2004/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE
2004/08/13 
_ MIKE1
Member List
2004/05/10 
_ NODB2
mcust with db2 deleted
2004/01/25 
_ ORDER
DB2 - LOCATION.TSOID01.CUSTOMER
2004/08/30
_ PART1
Member List
2003/02/11
_ SELCUST
test select customer
2002/01/28 
_ TESTA
test saving the criteria
2001/04/12
******************************* Bottom of data ********************************
Request File : The request file name comes from your current profile. If your profile does
not include a request file, File-AID/RDX will prompt for one. Enter a new file name to
change to a different saved request file or extract criteria file and File-AID/RDX will
display its member list.
Clear the field and File-AID/RDX displays the “Extract Reference List” (page 4-20).
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.
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:
Extract
4-25
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 4-94). 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 4-18).
Figure 4-18. Delete Confirmation window
Delete Confirmation 
COMMAND ===>
Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’

Member to be Deleted: TESTA
ENTER to confirm delete
END to return to Request File Member List










G (Go) : Submits this extract request without any changes.
M (Modify) : Selects this extract request, displays the “Modify Extract Request” panel for
you to change or “clone” an existing extract request. See also “Modify Extract
Request” on page 4-32.
R (Rename) : Rename the request member. The “Rename Confirmation window” (Figure
4-19) allows you to enter a new name for the request file member.
Figure 4-19. Rename Confirmation window
Rename Confirmation 
COMMAND ===>
Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’
Member to be Renamed: TESTA
New Member name ===>
ENTER to confirm rename
END to return to Request File Member List













S (Select) : Selects this extract request and displays the “Extract Menu” prefilled with all
the information from this request. See also “Extract Menu” on page 4-44.
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 4-134) 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
4-11 or Figure 4-12).
You can also include one of the optional parameters, DB2 or MVS, to display the
respective Driving Object screen.
4-26
File-AID/RDX Reference
REFERENCE (REF) : Displays your Extract Reference List panel. Refer to Figure 4-13 on
page 4-20 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 4-20 for an example. Size is a toggle switch so
enter Size again to return to the original format.
Figure 4-20. Request File Member List - Size Screen
File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8 
Command ===>
Scroll ===> CSR
Member
Description
Changed
_ DB2VSAM
db2 to vsam extract
2001/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE
2001/08/13 
_ MIKE1
Member List
2002/05/10 
_ NODB2
mcust with db2 deleted
2001/01/25 
_ ORDER
DB2 - LOCATION.TSOID01.CUSTOMER
2001/08/30
_ PART1
Member List
2002/02/11
_ SELCUST
test select customer
1999/01/28 
_ TESTA
test saving the criteria
2001/04/12
******************************* Bottom of data ********************************
Extract Requests from Releases prior to Release 4.0
File-AID/RDX accepts extract requests created with an earlier release of File-AID/RDX
than Release 4.0.
When selecting such a request with the S or M line command, File-AID/RDX will convert
the request to the new Release 4.0 format. For example, File-AID/RDX will set the
navigation and sampling controls to approximate the old extract method (OPTIMUM,
STANDARD, MOST, or DETAILED). However, the extract results may differ as an exact
conversion may not be possible.
Table 4-2.Conversion of Old Extract Methods
Navigation
Controls
OPTIMUM
MOST
STANDARD
DETAILEDa
Y
Y
Y
*
Parents
Y
Y
Y
*
Siblings
N
Y
N
*
Indirect
N
Y
Y
*
Direct
a. For Detailed, the controls are converted as specified per individual 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
4-27
• Extract every nth 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.
Note:
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 4-21 or page
4-25), the request will be converted and executed using a temporary request file.
4-28
File-AID/RDX Reference
DB2 Driving Object
The “DB2 Driving Object” screen shown in Figure 4-21 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 4-21. DB2 Driving Object



File-AID/RDX ------------- DB2 Driving Object -------------------------------
Command ===>


Primary commands: MVS driving object 

Specify table to drive extract process from:

SSID
===> DSN 
Location
===>
(* or pattern for selection list)
Creator
===> FRSAMP
(* or pattern for selection list)
Table Name
===> *
(* or pattern for selection list)
Relationship Information:
File name or pattern ===> 'TSOID01.FRSAMP.RELATION'

NOTE: For single object extract leave relationship file blank
ENTER to continue
After entering the information for the new DB2 driving object, press ENTER to proceed
to the “Extract Menu”.
The body of this screen consists of the following fields:
Specify Table To Drive Extract Process Area
Use the fields in this area to specify the DB2 table for which you want to retrieve
relationship information from the relationship file so you can extract related data. When
specifying patterns in the fields, File-AID/RDX searches the relationship file and presents
selection lists.
SSID : Displays the current DB2 subsystem ID. Type over this field to connect to a new
DB2 subsystem. If you leave the Location field blank, the table you specify to drive
the extract must exist in the DB2 subsystem displayed here.
Location : Specify the location of the table you want to drive the extract if it resides in a
remote DB2 subsystem. The location you enter must be defined in the DB2 system
catalog table, SYSIBM.LOCATIONS.
Leave this field blank if the table you want to drive the extract is in the DB2
subsystem in the SSID field.
Note:
The “Extract from Image Copy” option is not available when extracting from
a remote location (see also “Extract from Image Copy” on page 4-52).
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 1-4). 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
Extract
4-29
views, aliases, and synonyms in Extract, see “Use of DB2 Views” on page 4-17 and
“Use of Aliases and Synonyms” on page 4-29.
You can enter a pattern in this field. Valid pattern characters are %, _, and * (see
“Pattern Characters” on page 1-4). 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 1-4). If you specify a pattern, select a file from the “Catalog
Utility File List” as shown in Figure 4-33 on page 4-40.
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 4-38.
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.
Notes:
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.
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 4-80).
4-30
File-AID/RDX Reference
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.
Note:
If File-AID/RDX finds a single table that matches both the table name and
creator, it bypasses the Relationship Listing window.
Figure 4-22. Relationship Listing Window—Multiple Relationship Definitions
File-AID/RDX
Command ===>
Driving Object - DB2
Relationship Listing
Primary Comma
Row 1 to 6 of 6 
SCROLL ===> CSR


Multiple relationships exist for object: EMP


Enter 'S' to select relationship definition for extract


CMD Object
SSID

--- -------------------------------------------------- ---
_ LOCATION.CWS029.EMP
DSNG

_ LOCATION.CWS037.EMP
DSN

_ LOCATION.CWX0023.EMP
DSN

_ LOCATION.CWX0039.EMP
DSN

_ LOCATION.CWX0230.EMP
DSN

_ LOCATION.CWX0330.EMP
DSN




Command ===>
Specify table
SSID
Location
Creator
Table Name
Relationship
File Name o
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
1-9 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:
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.
Extract
4-31
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 4-23. 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:
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.
4-32
File-AID/RDX Reference
Modify Extract Request
The “Modify Extract Request” screen shown in Figure 4-24 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.
Note:
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 4-24. Modify Extract Request
File-AID/RDX ------------Option ===>
Modify Extract Request
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.
Extract
4-33
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.
Note:
The “Extract from Image Copy” option is not available when extracting from
a remote location. (see also “Extract from Image Copy” on page 4-52).
Modify Object names : Specify whether you want to modify the object names in your
extract request or not.
Y: Enter Y (Yes) to modify object names in the request. File-AID/RDX displays the
“Modify Extract Request - Object Names” panel (Figure 4-25) listing all object
names you can modify for the “cloned” request.
N: 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 4-25 is displayed
when you enter a Y in the Modify Object names field of the “Modify Extract Request”
screen.
Figure 4-25. Modify Extract Request - Object Names
Row 1 to 13 of 13 


Primary Commands: Change, Detail, Find, Size

Line Commands: R = Restore


SSID: DSN Location:

Object Name
Object Type

--------------------------------------------- ------------------------------ 
_ TSOID01.FRSAMP.EXTPDS
EXTRACT FILE NAME

_ TSOID01.FRSAMP.EXTCRIT2
REQUEST FILE NAME

_ TSOID01.FRSAMP.RELATION
RELATIONSHIP FILE NAME

_ TSOID01.VAR1M0.PROFILE
PROFILE FILE NAME

_ TSOID01.FRSAMP.DISGUISE
DISGUISE CONTROL FILE NAME

_ FRSAMP.ORDER_TABLE
DB2 TABLE NAME

_ FRSAMP.CUSTOMER_TABLE
DB2 TABLE NAME

_ FRSAMP.CONTACT_TABLE
DB2 TABLE NAME

_ TSOID01.FRSAMP.CUSTOMER
FILE OBJECT NAME

_ TSOID01.FRSAMP.LAYOUTS(CUSTOMER)
MVS LAYOUT FILE

_ FRSAMP.ORDER_LINE_TABLE
DB2 TABLE NAME

_ FRSAMP.PART_TABLE
DB2 TABLE NAME

_ FRSAMP.SUPPLIER_TABLE
DB2 TABLE NAME

******************************* Bottom of data ********************************
File-AID/RDX -----Option ===>
Modify Extract Request - Object Names
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.
4-34
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.
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)
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 Request”as shown in Figure 4-26.
Figure 4-26. 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. FileAID/RDX will change all matching strings in the listed object names.
Extract
4-35
From string : Enter the current From (old) string you want to change to the To (new)
string in the object name list.
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 4-27 for an example. Detail is a toggle switch so
enter Detail again to return to the original format.
Figure 4-27. Modify Object Names - DETAIL Screen
------------ Row 1 to 7 of 13 
Scroll ===> PAGE

Primary Commands: Change, Detail, Find, Size

Line Commands: R = Restore


SSID: D801 Location:

New Object Name / Original Object Name

---------------------------------------------------------------------------- 
_ TSOID01.FRSAMP.EXTPDS

TSOID01.FRSAMP.EXTPDS

_ TSOID01.FRSAMP.EXTCRIT2

TSOID01.FRSAMP.EXTCRIT2

_ TSOID01.FRSAMP.RELATION

TSOID01.FRSAMP.RELATION

_ TSOID01.VAR1M0.PROFILE

TSOID01.VAR1M0.PROFILE

TSOID01 FRSAMP DISGUISE

File-AID/RDX ------------Option ===>
Modify Object Names
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 4-16 for an example. Size is a toggle switch, so
enter Size again to return to the original format.
Figure 4-28. Extract Reference List - Size Screen

File-AID/RDX -----Option ===>
_
_
_
_
_
_
_
_
_
_
_
_
Modify Extract Request - Object Names
Object Name
--------------------------------------------TSOID01.FRSAMP.EXTPDS
TSOID01.FRSAMP.EXTCRIT2
TSOID01.FRSAMP.RELATION
TSOID01.VAR1M0.PROFILE
TSOID01.FRSAMP.DISGUISE
FRSAMP.ORDER_TABLE
FRSAMP.CUSTOMER_TABLE
FRSAMP.CONTACT_TABLE
TSOID01.FRSAMP.CUSTOMER
TSOID01.FRSAMP.LAYOUTS(CUSTOMER)
FRSAMP.ORDER_LINE_TABLE
FRSAMP.PART_TABLE
Row 1 to 13 of 13 

Object Type
-----------------------------EXTRACT FILE NAME
REQUEST FILE NAME
RELATIONSHIP FILE NAME
PROFILE FILE NAME
DISGUISE CONTROL FILE NAME
DB2 TABLE NAME
DB2 TABLE NAME
DB2 TABLE NAME
FILE OBJECT NAME
MVS LAYOUT FILE
DB2 TABLE NAME
DB2 TABLE NAME














When you have modified all the object names you wanted modified, enter the END
command to save the “cloned” extract request.
4-36
File-AID/RDX Reference
Save Cloned Extract Request
The Save Extract Request screen shown in Figure 4-29 is displayed when you enter the
END command in either the “Modify Extract Request” or “Modify Extract Request Object Names” screen.
Figure 4-29. Save Cloned Extract Request


File-AID/RDX
COMMAND ===>
---------------
Specify Extract
File name
Member
Description
Save Extract Request
Request File Information:
===>
===> 
===>
---------------------------




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 4-20).
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 4-144.
If you specify a new file, you must specify the following allocation parameters in the
“Create New File” screen (Figure 4-87 on page 4-121).
Note:
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.
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 4-30) displays:
Extract
4-37
Figure 4-30. Save Confirmation window

File-AID/RDX -------------------- Save Confirmation --------------------
Command ===>
The Following member exists and will be replaced:
Request File . . . .: 'TSOID01.FRSAMP.EXTCRIT'
Member to be saved : MVSKEY








ENTER to confirm Save and replace existing member

END return to Save Request enter a different member name 

Press Enter to confirm overwriting the existing file or member name. Press End to cancel
the Save request and return to the “Save Extract Request” panel where you can enter
another file or member name.
4-38
File-AID/RDX Reference
MVS Driving Object
The “MVS Driving Object” screen shown in Figure 4-31 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 4-31. MVS Driving Object
File-AID/RDX ------------Option ===>
MVS Driving Object
-------------------------------


Primary Commands: DB2 driving object


File to drive the extract process from:

File name
===>


Optional File Information:

Record layout usage ===>
(S = Single; X = XREF)

Record layout file
===>

Member name
===>

XREF file
===> XREF

Member name
===>


Relationship Information:

File name or pattern ===> 'TSOID01.FRSAMP.RELATION'


NOTE: For single object extract leave relationship file blank


After entering or viewing the driving object information, press ENTER to proceed to the
“Extract Menu”.
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 1-4). If you specify a pattern, select a file from the
“Catalog Utility File List” as shown in Figure 4-33 on page 4-40.
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 4-32
on page 4-40).
Note:
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
4-39
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 1-4). If you specify a pattern,
select a file from the “Catalog Utility File List” as shown in Figure 4-33 on page 4-40.
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 1-4). If you specify a pattern, select a file from the
“Catalog Utility File List” as shown in Figure 4-33 on page 4-40.
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 4-35 on page 4-42.
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
1-4). If you specify a pattern, select a file from the “Catalog Utility File List” as shown
in Figure 4-33 on page 4-40.
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 4-28.
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 4-32 on page 4-40).
4-40
File-AID/RDX Reference
Figure 4-32. Relationship Listing Window - No Relationships
File-AID/RDX ------------Option ===>
Primary Commands: D
File to drive the e
File name
Optional File Infor
Record layout usa
Record layout fil
Member name
XREF file

Member name
-------------------------------

Relationship Listing 

Command ===>


No relationships exist for:

'TSOID01.FRSMP.ORDERTAB'


Press ENTER to process a single table extract

Enter END to terminate processing


===>
MVS Driving Object
(Blank or pattern for member list)
Relationship Information:
File name or pattern ===> 'TSOID01.FRSAMP.RELATION'





If you press ENTER for a single object extract, File-AID/RDX will use the optional file
information you specified on the “MVS Driving Object” panel.
MVS Catalog Utility File List
When specifying a pattern in any of the file name fields in the “MVS Driving Object”
panel, File-AID/RDX searches the MVS catalog and displays any matches. Select the file
name you want to place in the applicable field with the S line command. The message in
the top line indicates for which field the list is displayed:
• Select File (driving object or relationship file)
• Select Record Layout
• Select XREF file
Figure 4-33. MVS Catalog Utility File List (for Pattern FR*.ORDERTAB)
File-Aid/RDX ------------- Catalog Utility File
Command ===>
----- D A T A S E T
N A M E -------------TSOID01.FRKFL.ORDERTAB
TSOID01.FRKFL.ORDERTAB.DATA
TSOID01.FRKFL.ORDERTAB.INDEX
S TSOID01.FRSAMP.ORDERTAB
TSOID01.FRSMP.ORDERTAB
TSOID01.FRSMP1.ORDERTAB
TSOID01 FRSMP2 ORDERTAB
List ------------- Select File 
SCROLL ===> CSR 

NON-VSAM
MIGRAT

NON-VSAM
MIGRAT

NON-VSAM
MIGRAT

CLUSTER
PRD981

CLUSTER
PRD908

CLUSTER
PRD970

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 4-34, 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
4-41
Figure 4-34. PDS Processing Options Screen
File-Aid/RDX
Command ===>
----------------- PDS Processing Options ------------------------



Layout File: TSOID01.FRSAMP.LAYOUTS








Specify Member Selection Options (Blank for All Members)

Member name mask
===>

Member name range
===>
to ===>

Last modified userid
===>
to ===>

Creation date
===>
to ===>
(YY/MM/DD)

Modification date
===>
to ===>
(YY/MM/DD)




Use ENTER to continue, END to return to file specification screen


Field Descriptions
The following list describes all PDS processing options that File-AID/RDX can present.
Member name mask : Specify a member name mask to select a subset of members based
on the mask criteria. A pattern member name or mask consists of explicit characters
or a combination of explicit and pattern characters.
Member name range : Specify a member name range to select a subset of members based
on the characters in the member name. The endpoint member names (FROM and
TO) can be complete or partial and are included in the member list when found.
Pattern characters are not allowed.
If the FROM member field is blank and a TO member is specified, File-AID/RDX
selects the members less than or equal to the TO member padded with high values.
If a FROM member field is specified and the TO member is blank, File-AID/RDX
selects members greater than or equal to the FROM member padded with low values.
Entering the same characters in the FROM and TO fields selects all members
beginning with those characters.
Last modified userid : Specify a user identification range to select a subset of members
based on the user ID that last updated and saved a member. This information is a PDS
statistic that is stored in the directory.
The endpoint userids (FROM and TO) can be complete or partial and are included in
the member list when found. Pattern characters are not allowed. As with member
name range, the FROM field is padded with low values and the TO field is padded
with high values.
Members without PDS statistics, because they were not created (STATS OFF) or the
statistics were deleted, are not selected.
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.
4-42
File-AID/RDX Reference
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 4-35, 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 4-35. XREF Select Member List Screen
File-Aid/RDX - XREF Select - TSOID01.FRSAMP.XREF ------------ Row 1 to 5 of 5 
Command ===>
SCROLL ===> PAGE 
S NAME
DESCRIPTION
TYPE
CHANGED
ID

ADVMST4
FILE-AID/RDX GENERATED XREF __
XREF
00:00 AX

A020815
FILE-AID/RDX GENERATED XREF __
XREF
00:00 AX

RETEST1
FILE-AID/RDX GENERATED XREF __
XREF
00:00 AX

TEDS646
FILE-AID/RDX GENERATED XREF __
XREF
00:00 AX

S USERNEW
FILE-AID/RDX GENERATED XREF __
XREF
00:00 AX

******************************* Bottom of data ********************************
Extract
4-43
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 1-22 and “File-AID/RDX Extract/Load/Delete
Request File” on page 4-144 for more information about the Extract Request File.
Note:
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.
4-44
File-AID/RDX Reference
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 4-36.
Note:
You profile’s selected extract flow (see “Panel Customization” on page 2-11)
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 “13 - Submit JCL” and
File-AID/RDX submits this extract job.
Figure 4-36. Extract Menu
File-AID/RDX -----------------Option ===>

Extract Menu
--------------------------------
Scroll ===> CSR
SITE Profile: RDXMENU
SSID: DSN
Primary commands: menu-number, ALL, REFerence, REQuest, MODE
Line commands: S or / to create flow through selected options.

Description ===> DB2-FRSAMP.ORDER_TABLE 

_ 1 Driving Object
DB2-FRSAMP.ORDER_TABLE 
/ 2 Extract Scope and
Dep=Y, Par=Y, Sib=N, Ind=N, Cycles=1
Detailed Extract Views 3 of 5 Relationships Active
/ 3 Unrelated Objects
None
_ 4 Input Key File
None
/ 5 Selection Criteria
None
_ 6 Output Key Files
Attention
/ 7 Extract File
TSOID01.FRSAMP.EXTRACT 
_ 8 Data Privacy DISGUISED DCF: TSOID01.FRSAMP.DISGUISE
_ 9 Supporting Files
None
_ 10 Continue with Load
No
_ 11 Save Extract Request
Request has not been saved 
_ 12 View JCL

_ 13 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 “FileAID/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, FileAID/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 “11- Save Extract Request”.
Extract
4-45
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 4-28 or “MVS
Driving Object” on page 4-38 panel depending on the driving object’s object type.
The MVS panel also includes layout and XREF information.
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.
6 - Output Key Files : If the extract request includes relationships to an Output Key File
(see “IMS and Output Key Files” on page 3-34), 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”.
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.
4-46
File-AID/RDX Reference
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 and a File-AID/MVS XREF for the extract file.
Current Values displays None, Layouts or Layouts and Xref.
10- Continue with Load : Specify whether the extract request should be a combined
extract and load (YES) or just an extract. When YES, File-AID/RDX presents the
“Continue With Load” Menu where you identify all your load options and
parameters.
Current Values displays Yes or No.
Notes:
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. The “Continue With Load” option is not available for interactive (online)
extract execution (see also “MODE” on page 4-47.)
3. The ALL primary command does not select the “Continue With Load” option
(see also “ALL” on page 4-47.)
11- Save Extract Request : Specify whether to save this extract request in a file. FileAID/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.
Note:
Make sure to save the request just before selecting Option “13 - 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.
12 - 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.
Note:
Option “12 - View JCL” switches to Option “12 - View REXX” when the
MODE primary command has set the execute extract mode to (see Figure 437 on page 4-47). INTERACTIVE (online) extract is a configuration option
and is only available if specifically installed at your site (see “OLEXTR” in the
File-AID Single Install Image Installation and Configuration Guide).
13 - 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.
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.
Note:
Option “13 - Submit JCL” switches to Option “13 - Execute REXX” when the
MODE primary command has set the execute extract mode to INTERACTIVE
(see Figure 4-37 on page 4-47). INTERACTIVE (online) extract is a
configuration option and is only available if specifically installed at your site
(see “OLEXTR” in the File-AID Single Install Image Installation and Configuration
Extract
4-47
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 “10- Continue with Load” and “13 - Submit JCL”. To submit
the extract JCL, select option “13 - 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 “12 - View JCL” and “13
- Submit JCL” will change to “12 - View REXX” and “13 - Execute REXX” (see Figure
4-37) to show that the extract will be executed interactively when selecting Option
“13 - Execute Rexx”. MODE acts as a toggle switch.
Notes:
a. INTERACTIVE (online) extract is a configuration option and is only available if
specifically installed at your site (see “OLEXTR” in the File-AID Single Install Image
Installation and Configuration Guide).
b. The following options are not available for interactive execution:
1. “Continue With Load” (see also “Continue With Load” on page 4-131).
2. “Extract from Image Copy” (see also “Extract from Image Copy” on page
4-52).
3. “Disguise Extract File” (see also “Disguise Extract File” on page 4-127).
c. If the extract file is a GDS, it must already exist, therefore (0) or (-n) are valid
while (+n) is not allowed.
Figure 4-37. Extract Menu - Interactive Extract Mode
/
_
_
_
_
_
_
7
8
9
10
11
12
13
Extract File
Data Privacy
Supporting Files
Continue with Load
Save Extract Request
View REXX
Execute REXX
TSOID01.FRSAMP.EXTRACT 
DCF: TSOID01.FRSAMP.DISGUISE
None
No
Request has not been saved 

*** INTERACTIVE EXTRACT MODE ACTIVE ***

REFERENCE (REF) : Returns to your “Extract Reference List” (page 4-20) to start a new
extract request.
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 4-24 for more information.
Note:
Make sure to save the request just before selecting Option “11- 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 4-38 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.
4-48
File-AID/RDX Reference
Figure 4-38. Driving Object - DB2



File-AID/RDX ------------Command ===>

Table to drive
SSID
Location
Creator
Table Name
DB2 Driving Object
extract process
===> DSN 
===> Location
===> FRSAMP
===> ORDER_TABLE
-------------------------------

(* or pattern for selection list)
(* or pattern for selection list)
(* or pattern for selection list)
Relationship Information:
File name
===> 'TSOID01.FRSAMP.RELATION'

After viewing the driving object information, press END to return to the “Extract Menu”.
The body of this screen consists of the following fields:
Table To Drive Extract Process Area
SSID : Displays the DB2 subsystem ID for the extract.
Location : Displays the location of the table you want to drive the extract.
Creator : Displays the authorization ID of the owner of the table, view, synonym, or alias
that you want to drive the extract process.
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 4-39 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 4-39. Driving Object - MVS

File-AID/RDX ------------Command ===>
MVS Driving Object
-------------------------------

File to drive extract process from:
File Name
===> FRSAMP.ORDERTAB

Optional File Information: 
Record layout usage
===> S

Record layout file
===> FRSAMP.LAYOUTS 
Member name
===> ORDERTAB

XREF file
name
===> 
Member name
===>


Specify Relationship Information:
File name
===> 'TSOID01.FRSAMP.RELATION'
After viewing the driving object information, press END to return to the “Extract Menu”.
Extract
4-49
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.
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 4-40 on page 4-50 is displayed when you
select Option “2 - Extract Scope and Detailed Extract Views” from the “Extract Menu”.
Note:
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
2-9), 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.
4-50
File-AID/RDX Reference
Figure 4-40. Extract Scope Screen
File-AID/RDX ------------------ Extract Scope ---------------------------------
Command ===>


Driving Object: TSOID01.FRSAMP.ORDERTAB


Extract Navigation Criteria:

Direct
===> Y
( Y = Yes, N = No)
Parents
===> Y

Siblings ===> N

Indirect ===> N

Extract scope detail view ===> O
( O = Object, R = Relationship, N = None) 
Extract Options:

Cycle count
===> 1
( * for no maximum) 
Maximum total rows/records from all objects ===> *
( * for no maximum) 
Action when maximum count is reached
===> Q
( Q = Quiesce, S = Stop) 
Extract from DB2 using Uncommitted Reads
===> N
( Y = Yes, N = No) 
Extract 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 B, “Extract Navigation Criteria Examples” 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 FileAID/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.
Note:
When your profile has navigation criteria Direct set to C or P (see also
“Direct” on page 2-9), 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 descendent so any relationship on this downward navigation has a valid
direct descendent path. Only the rows initially selected from the driving object
will be sent down this path so the direct descendent path will be navigated only
once.
Y : Extract the dependents of the driving object and their dependents (default).
N : Do NOT extract the dependents of the driving object and their dependents.
C : (All Children only) This option can only be set or changed in the profile (see
“Direct” on page 2-9). Extract the dependents of the driving object and all of
Extract
4-51
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.
P : (Plus) This option can only be set or changed in the profile (see “Direct” on
page 2-9). 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.
Note:
The C and P settings for Direct can only be set in the profile. The
profile settings are used to build the relationship tree with its related
objects when starting an extract specification.
Parents : Extract the parents of all extracted data to maintain the integrity of the
extracted data.
Any object that is on the upward navigation from a selected object has a valid
parent path. This does not mean that every relationship has a valid parent path;
navigation has to be possible in an upward direction for the parent path to be
valid.
Siblings : Extract other dependents of the extracted parents from the same
relationships.
Parent paths are always paired with sibling paths. Whenever a row is sent up the
parent path it is possible to come back down the same relationship to get the
sibling rows.
Consider a relationship between ORDER and CUSTOMER where a row has been
selected from ORDER. The CUSTOMER for that order will be extracted by
navigating the parent path. The sibling path would allow all of the rest of the
orders for that same customer to be extracted.
Parent/sibling special case:
A many to many application relationship presents a special case where it is
possible to have a parent and sibling path defined for a relationship that does
not meet the parent criteria specified above. Every many to many relationship
has a parent and sibling path.
Indirect : Extract other dependents of the extracted parents from other
relationships.
The indirect descendent path includes two different situations. First, it is the
downward navigation from any object reached in an upward direction.
Second, it is downward navigation from the driving object and its direct
descendents for all rows other than the original selection from the driving
object. For an indirect descendent path to be valid on the same relationship as a
direct descendent path there has to be a parent path that leads back to the
driving object or one of its parents; in effect, another path to the object.
The indirect descendent paths represent downward navigation for objects
reached via the parent path. The downward navigation for the relationship that
was navigated via the parent path is a sibling path and is not an indirect
descendent path. All the other relationships that lead down from an object are
valid indirect descendent paths.
This is not to say that a relationship can't have both a sibling path and an
indirect descendent path; this is possible when there are multiple parent paths
4-52
File-AID/RDX Reference
leading to the same object. If the object is on the direct descendent path it is
possible to have all three downward navigation paths marked as valid.
Note:
The status (Modified) identifies global settings that have been modified
individually with the navigation controls of the “Relationship Navigation
Criteria” screen or by the Accept primary or line command of the “Check Extract
Warning” screen.
Extract Scope Detail View : Specify whether you want to view the list of relationships or
list of related objects. Set to R or O to view the related objects and their relationships
in more detail. In the detail panels, you may apply extract and navigation controls to
individual relationships or objects.
N : None does not display either of the detail view panels.
O : Object displays the “Extract Scope - Object View” panel, listing all objects related
to the driving object from which to extract data. See “Extract Scope - Object
View” on page 4-56 for more information.
R : Relationship displays the “Relationship Criteria” panel, listing all the
relationships associated with the driving object from which to extract data. See
“Relationship Criteria” on page 4-63 for more information.
Note:
The Relationship View options are not accessible for a single object
extract.
Extract Options
Use these fields to limit the number of records to be extracted in this request. These
options also apply to all unrelated objects included in the extract.
Cycle Count : Specify the maximum number of cycles for all relationships leading from
the object. Cycle count only applies to downward navigation via the Sibling and
Indirect paths. This global setting for the Cycle Count can be modified for each
individual relationship (see “Cycle” on page 4-71).
Maximum Total Rows/Records From All Objects : Specify the maximum number of
rows or records to be extracted from all related objects. Once the limit is reached the
extract will terminate regardless of how many relationships have been chased. Enter
an asterisk (*) to set no limit.
Action When Maximum Count Is Reached : Specify how the extract should terminate
when the maximum count has been reached:
Q : Quiesce resolves all orphan records after maximum count has been reached.
(May result in more records than the maximum count.)
S : Stop does not resolve possible orphan records. (May extract dependent records
without their parents).
Extract from DB2 using Uncommitted Reads : Specify whether File-AID/RDX should
extract data from DB2 objects that include Uncommitted Reads or not.
Extract from Image Copy : Specify whether File-AID/RDX should extract data from DB2
Image Copy datasets or not. This option is only available if your site installation set
the product parameter variable UIMGCPY to Yes. Refer to “UIMGCPY” in the File-AID
Single Install Image Installation and Configuration Guide.
Y : File-AID/RDX will extract related data from the most recent, full DB2 Image
Copy(s) for the applicable tablespace(s). For partitioned tablespaces, FileAID/RDX will only extract from an image copy dataset that includes all
partitions.
An image copy dataset must exist and be in the MVS catalog for each DB2 table
in the extract request or the extract will terminate.
Extract
4-53
You must have one of the following authorization privileges to extract data from
DB2 Image Copy:
• RECOVERDB privilege for the database
• DBADM, or DBCTRL authority for the database
• SYSCTRL or SYSADM authority
N : File-AID/RDX will extract from the regular DB2 tables.
Note:
The “Extract from Image Copy” option requires executing File-AID/RDX from an
authorized library. Furthermore, the “Extract from Image Copy” option is not
available:
• for DB2 views.
• for interactive execution (see also “MODE” on page 4-47).
• when extracting from a remote location (see also “Location” on page 4-28).
SELECT FROM Temporal Table : Enter Yes if you want to specify or modify a timeperiod and date/timestamps for Temporal Tables or Temporal Views. File-AID/RDX
will display the “SELECT FROM Temporal Table” screen (refer to Figure 4-41 on page
4-54) 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 4-41 on page 4-54).
Notes:
1. When the *Defined* status displays and the extract request includes one or
more temporal tables or views, File-AID/RDX will include the SELECT FROM
Temporal Table statement even if the SELECT FROM Temporal Table field is
set to No.
The SELECT FROM Temporal Table statement is only generated for each
Temporal Table or Temporal View in the extract request.
2. Whenever the selection is based on SYSTEM_TIME, it is possible that some
rows come from the base table and some from the history table.
3. The *Defined* status is saved with the extract request.
4. The SELECT FROM Temporal Table field will be reset to its default (No,
*None*) when you exit the extract menu. It will be set to *Defined* when
when you return the extract menu with an extract request that includes the
*Defined* status.
Scope Summary Counts
The following fields display how many objects and relationships will be included in the
extract based on the specified navigation and sampling criteria.
Relationships Active : Displays how many relationships will be used to extract data
from the related objects.
Related DB2 objects : Displays how many related DB2 objects will be accessed to extract
data from.
4-54
File-AID/RDX Reference
Related MVS objects : Displays how many related MVS objects will be accessed to extract
data from.
Output Key Files : Displays how many Output Key files File-AID/RDX will create for this
extract request.
SELECT FROM Temporal Table
The SELECT FROM Temporal Table window displays when you enter Y in the “SELECT
FROM Temporal Table” field. It allows you to construct the SELECT FROM statement to
be used for a temporal table (or view starting with DB2 Version 11) to be browsed (System
Period and Business Period) or edited (Business Period only).
Figure 4-41. SELECT FROM Temporal Table
File-AID/RDX ----------------COMMAND ===>
Extract Scope
--------------------------------


Driving Object: FRSAMP.ORDER_TABLE

SELECT FROM Temporal Table -----------------------+
Ext
COMMAND ===>

D

P
SELECT FOR SYSTEM TIME:

S
Use System Time
===> N
(Y = Yes, N = No)

I
Time Period
===>
(1 = AS OF, 2 = FROM, 3 = BETWEEN)

E
Timestamp 1
===>

Ext
Timestamp 2
===>

C
(Example format: YYYY-MM-DD-hh.mm.ss or

M
CURRENT TIMESTAMP)

A

E
SELECT FOR BUSINESS TIME:

E
Use Business Time ===> N
(Y = Yes, N = No)

S
Time Period
===>
(1 = AS OF, 2 = FROM, 3 = BETWEEN)

Sco
Date/Timestamp 1
===>

Date/Timestamp 2
===>

(Example format: YYYY-MM-DD or YYYY-MM-DD-hh.mm.ss or

CURRENT DATE/TIMESTAMP)



A temporal table records the period of time when a row is valid. DB2 supports two types
of periods, the application period (BUSINESS_TIME) and the system period
(SYSTEM_TIME).
System Period
The system period consists of a pair of columns with system-maintained values that
indicate the period of time when a row is valid. The system period is meaningful because
you can define system-period data versioning on a table that has this period. Systemperiod data versioning specifies that old rows are archived into another table. The table
that contains the current active rows of a table is called the system-period temporal table.
The table that contains the archived rows is called the history table (Table Type=H). You
can delete the rows from the history table when those rows are no longer needed, if you
have the proper authorization.
When you define a base table to use system-period data versioning, or when you define
system-period data versioning on an existing table, you must create a history table,
specify a name for the history table, and create a tablespace to hold that table. You define
system-period data versioning by issuing the ALTER TABLE ADD VERSIONING statement
with the USE HISTORY TABLE clause.
Extract
4-55
Business (Application) Period
A business (application) period consists of a pair of columns with application-maintained
values that indicate the period of time when a row is valid. A table with only a business
period is called an application-period temporal table.
Bitemporal Table
A bitemporal table is both a system-period temporal table and an application-period
temporal table. You can use a bitemporal table to keep application period information
and system-based historical information. Therefore, you have a lot of flexibility in how
you query data based on periods of time.
For each System Time and Business Time, specify the time period to be used to select rows
from a temporal table.
Use System Time : Specify Yes if the table includes System Time and you want to select
rows from the specified period.
Time period : Select the period method you want to specify for System Time:
1 : AS OF creates the AS OF ... period statement to select valid rows as of a certain
point in time. This option requires you to also specify a value for
Date/Timestamp 1. Example statement:
FROM table FOR SYSTEM_TIME AS OF TIMESTAMP('2012-03-16-00.00.01')
2 : FROM creates the FROM ... TO ... period statement to select valid rows from a
certain time to a certain time. FROM is inclusive, TO is exclusive. That means,
the specified start time is included in the period but the specified end time is
not. This option requires you to also specify a value for Timestamp 1 (start time)
and Timestamp 2 (end time). Example statement:
FROM table FOR SYSTEM_TIME FROM TIMESTAMP('2011-03-16-00.00.01')
TO TIMESTAMP('2012-03-16-00.00.01')
3 : BETWEEN creates the BETWEEN ... AND ... period statement to select valid rows
from a certain time to a certain time. BETWEEN and AND are inclusive. That
means, that both the specified start time and end time are included in the
period. This option requires you to also specify a value for Timestamp 1 (start
time) and Timestamp 2 (end time). Example statement:
FROM table FOR SYSTEM_TIME BETWEEN TIMESTAMP('2011-03-16-00.00.01')
AND TIMESTAMP('2012-03-16-00.00.01')
Timestamp 1 : specify the corresponding start timestamp for the selected system time
period.
Timestamp 2 : specify the corresponding end timestamp for the selected system time
period. Only required for FROM and BETWEEN periods.
Use Business Time : Specify Yes if the table includes Business Time and you want to
select rows from the specified period.
Time period : Select the period method you want to specify for Business Time:
1 : AS OF creates the AS OF ... period statement to select valid rows as of a certain
point in time. This option requires you to also specify a value for
Date/Timestamp 1. Example statement:
FROM table FOR BUSINESS_TIME AS OF DATE('2011-03-16')
2 : FROM creates the FROM ... TO ... period statement to select valid rows from a
certain time to a certain time. FROM is inclusive, TO is exclusive. That means,
the specified start time is included in the period but the specified end time is
not. This option requires you to also specify a value for Date/Timestamp 1 (start
time) and Date/Timestamp 2 (end time). Example statement:
4-56
File-AID/RDX Reference
FROM table FOR BUSINESS_TIME FROM DATE('2011-03-16') TO CURRENT DATE
3 : BETWEEN creates the BETWEEN ... AND ... period statement to select valid rows
from a certain time to a certain time. BETWEEN and AND are inclusive. That
means, that both the specified start time and end time are included in the
period. This option requires you to also specify a value for Date/Timestamp 1
(start time) and Date/Timestamp 2 (end time). Example statement:
FROM table FOR BUSINESS_TIME BETWEEN DATE('2011-03-16') AND 
CURRENT DATE
Date/Timestamp 1 : specify the corresponding start date/time for the selected business
time period.
Date/Timestamp 2 : specify the corresponding end date/time for the selected business
time period. Only required for FROM and BETWEEN periods.
Note:
If the arguments for business Date/Timestamp 1/2 include only date
information, the time information in the result value is all zeros. This
means that date value of '2000-10-31' will result in a TIMESTAMP of
'2000-10-31-00.00.00'. This could result in different rows being returned
than if a user entered '2000-10-31-23.59.59'.
Extract Scope - Object View
The “Extract Scope - Object View” screen shown in Figure 4-42 is displayed when you
specify O in the “Extract Scope Detail View” field of the “Extract Scope Screen” (Figure 440 on page 4-50) or the VIEW primary command (page 4-69) from any of the
“Relationship Criteria” screens.
Figure 4-42. Extract Scope - Object View
File-AID/RDX ------Command ===>
Extract Scope - Object View
----------- Row 1 to 6 of 6
Scroll ===> PAGE
Primary Commands: EXclude/Unex, Change, Find, Hide, VIew, CHEck, Size, REPort
Line Commands: X = Exclude
A = All
R = Relationship View
: U = Unexclude
P = Passthru
L = Lock
Driving Object: TSOID01.FRSAMP.ORDERTAB
SSID:
Location:
.
Sampling Criteria
Object Name
Cycle MaxRow Nth Status
L
---------------------------------------------- ----- ------ --- ---------- _ 'TSOID01.FRSAMP.CONTACTT'
*
*
*
N
_ 'TSOID01.FRSAMP.CUSTOMER'
*
*
*
N
_ 'TSOID01.FRSAMP.ORDERLIN'
*
*
*
N
_ 'TSOID01.FRSAMP.ORDERTAB'
*
*
*
N
_ 'TSOID01.FRSAMP.PARTTABL'
*
*
*
N
_ 'TSOID01.FRSAMP.SUPPLIER'
*
*
*
N
******************************* Bottom of data ********************************

















Use this screen to specify which, if any, objects to exclude from the extract process and
the maximum number of rows/records that you want extracted from each object. In
addition, you can request to view the relationships for a specific object.
This screen displays a list of all the objects in alphabetical order that are part of the
extract request, including all objects related to the driving object based on the
relationships defined in the relationship file as well as all unrelated objects.
Initially, all objects are displayed. Use the HIDE command to display only select object
types.
If there are more objects on this list than will fit on this screen, you can scroll the list up
and down using standard scrolling commands. See “Scrolling” on page 1-9 for more
information about scrolling.
Extract
4-57
Fixed Display Area
In addition to the screen title, the Command field, and the scroll amount input field, the
top area of the screen contains
– the driving object for which these related objects were retrieved
– the DB2 subsystem and remote location ID where all related DB2 objects reside
– a message indicating the hide/filter status of the display
Scrollable Display Area
This screen areas displays a list of the objects related to the driving object containing the
following columns:
CMD : Enter line commands in this column. See “Line Commands” on page 4-58 for
information about valid commands for this screen.
Object Name : Displays the name of the related or unrelated object included in the
extract request. For DB2 objects, the creator.tablename is displayed here.
Sampling Criteria : Displays the status of the three sampling criteria for each object. You
can change each individual setting simply by typing over a new value or use the
CHANGE primary command to globally change the sampling criteria fields.
Cycle : The cycle count can be set for each individual object in the extract.
When entered for an object, it limits the times an object is accessed during the
extract regardless of the number of relationships.
Max Rows : Specify the maximum number of rows to extract via downward
navigation (direct, indirect and sibling) of this object. The Max Rows profile
value applies to each relationship and each object. The relationship Max Rows
values is processed first; if the count does not exceed the limit, the record is
passed on to check against the object Max Rows value.
NTH : (nth record) Specify how many of the eligible records to be extracted should be
skipped and not be extract (a value of 3 would extract records 1 and 4).
L : Lock Table; indicates whether or not the DB2 object (table) will be locked during
extract. Use the L line command to change the lock status for an individual table.
Note:
The L column is only displayed when you have entered the FUNCTION
LOCK primary command. The FUNCTION LOCK primary command is only
valid if File-AID/RDX was configured at installation to allow locking tables
during extract.
Status : Displays one of the following messages:
Message
Explanation
All
This object will have all of its records extracted, and File-AID/RDX will not chase
any of its relationships. This status is the result of the “A (All)” line command
(page 4-58).
Excl Miss
This object is excluded from the current extract process because the object
does not exist.
Excl Scope
This object is excluded from the current extract process. This status is the result
of a navigation setting or cascading EXCLUDE or ALL command.
Excl User
This object is excluded from the current extract process. This status is the result
of the EXCLUDE primary or line command.
Passthru
This object will not have any of its records extracted, but File-AID/RDX will
chase all of its relationships. This status is the result of the “P (Passthru)” line
command (page 4-58).
Selected
Indicates that this object has been selected for relationship view with the R line
command.
4-58
File-AID/RDX Reference
Message
Explanation
Unrelated
Indicates that this is an unrelated object that has been added with Option “3 Unrelated Objects”, for this extract request.
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
A (All) : Extract all data from this object regardless of the relationships from and to this
object and do not chase any relationships associated with this object. The A line
command acts as a toggle switch: enter it once to set the status, enter it again to
remove it.
Note:
The A (All) and P (Passthru) line commands are mutually exclusive. You must
remove one before you can set the other.
L (Lock Table) : Indicate whether or not a DB2 table will be locked during extract. See
also primary command “FUNCTION LOCK” on page 4-61 that controls whether the L
column displays and the L line command is valid. The “FUNCTION LOCK” command
is not available if File-AID/RDX was configured at installation to prevent locking
tables during extract. In this case, the L column will not be displayed. The L line
command acts as a toggle switch, enter it once and it will set the status to Locked.
Enter L a second time, and the Locked status is removed.
Note:
L locks a table while File-AID/RDX extracts rows from it. This prevents other users
from accessing and updating the table until the extract process is complete.
When you set the DB2 table status to Locked, File-AID/RDX issues the following SQL:
LOCK TABLE XXXXXX IN EXCLUSIVE MODE
If you lock a table that resides in a segmented tablespace, only the table is locked. If
you lock a table that resides in a partitioned tablespace, all of the partitions are
locked. If you lock a table that resides in a simple tablespace, all tables in the
tablespace are locked.
P (Passthru) : Don’t extract any data from this object, but process all relationships as if
records based on the relationship would have been extracted. The P line command
acts as a toggle switch: enter it once to set the status, enter it again to remove it.
Note:
The A (All) and P (Passthru) line commands are mutually exclusive. You must
remove one before you can set the other.
R (Relationship View) : Mark this object to be included in the Relationship View when
the VIEW primary command is entered.
U (Unexclude) : Selects a previously excluded object (using EXCLUDE primary or line
command) to be included in the extract. Remember, you cannot unexclude an
excluded object when its link to the driving object is through another, still excluded
relationship. See also “X (Exclude)”.
Note:
When the excluded status for an object has been set by a navigation control,
it can only be unexcluded with a navigation control, not with the Unexclude
line command.
X (Exclude) : Excludes an object from the extract.
Note:
You cannot exclude the driving object.
When you exclude an object, other relationships or objects might also be excluded as
a result. This occurs when you exclude a relationship and either of the objects in the
excluded relationship is a parent or dependent in another relationship that cannot
Extract
4-59
be linked back to the driving object in any other way. For example, assume three
relationships exist as shown below and ORDER_TABLE is the driving object.
Parent Object
Dependent Object
ORDER_TABLE
ORDER_LINE_TABLE
ORDER_LINE_TABLE
PART_TABLE
PART_TABLE
SUPPLIER_TABLE
When the PART_TABLE object is excluded, the SUPPLIER_TABLE object will also be
excluded as well as the ORDER_LINE_TABLE to PART_TABLE relationship.
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
CHANGE (C) : Change allows global changes to be made to the sampling criteria on a
column-by-column basis. When the CHANGE command is entered with one of the
available parameters CYC=n, MAXROW=n, or NTH=n, all values for the specified
parameter are changed to the new value n. When entered without parameters, specify
the values to change in the “CHANGE Command Window - Object View Sampling
Criteria”.
CHANGE Command Window
When you enter the CHANGE command without parameters, File-AID/RDX will
display the “CHANGE Command Window - Object View Sampling Criteria”as shown
in Figure 4-43.
Figure 4-43. CHANGE Command Window - Object View Sampling Criteria


File-AID/RDX -------------- CHANGE COMMAND ------------------Command ===>
Change ALL occurrences of "from string" value to "to string"
From string ===>
To string
===>
Act on the
Cycle
MaxRow
Nth
Lock
following fields:
===> N
( Y = Yes, N = No)
===> N
===> N
===> N
Primary command:
Change CYCle=n
Change MAXROW=n
Change NTH=n
Change Lock=Y/N
END to process and return

***NOTE: Change will be applied to all qualified objects,
even those that are excluded or hidden. 














Enter the Change ‘From string’ and the Change ‘To string’ values and select the
sampling criteria types you want to change globally for all objects. Then press END
to execute the CHANGE command.
From string : Enter the current From (old) string you want to change to the To (new)
string in the sampling criteria.
To string : Enter the To (new) string you want to replace the From (old) string with
in the specified sampling criteria.
Cycle : Enter Y to apply the change to all matching Cycle values. Enter N if the
change is not to be applied to the Cycle sampling criteria.
MaxRow : Enter Y to apply the change to all matching MaxRow values. Enter N if
the change is not to be applied to the MaxRow sampling criteria.
4-60
File-AID/RDX Reference
Nth : Enter Y to apply the change to all matching Nth values. Enter N if the change
is not to be applied to the Nth sampling criteria.
Lock : Enter Y to apply the change to all matching Lock values. Enter N if the change
is not to be applied to the Lock DB2 Table column.
Note:
Lock is only displayed when you have entered the FUNCTION LOCK
primary command. The FUNCTION LOCK primary command is only
valid if File-AID/RDX was configured at installation to allow locking
tables during extract.
CHECK (CHE) : Use the CHECK command to verify the extract paths after you made
navigation changes. When the path integrity validation processing is complete, the
results are displayed in the “Check Extract Warning” screen (Figure 4-60 on page
4-80) where you can resolve or ignore the findings. File-AID/RDX executes the
CHECK command whenever it returns from the “Extract Scope Detail View” panels.
Note:
CHECK is not valid when when the extract request is built with relationships
in the Direct Plus or All Children Only mode (see “Direct” on page 4-50).
EXCLUDE (EX or X) : The EXCLUDE command allows to exclude all objects or all
objects of a specified object type to be excluded from the extract. EXCLUDE without
parameter displays the “Exclude Command Window” (see Figure 4-44).
Use this command in conjunction with the U (Unexclude) line command or
UNEXCLUDE primary command when you have a long list of relationships displayed
and you want to include only a few relationships in the extract.
Enter the EXCLUDE ALL command to exclude all objects in the list displayed on the
“Extract Scope - Object View” screen from the extract.
The other parameters DB2 and MVS limit the EXCLUDE command to one of the two
object types.
EXCLUDE Command Window
When you enter the EXCLUDE command without parameters, File-AID/RDX displays
the “Exclude Command Window” as shown in Figure 4-44. Select the object types
you want to exclude from the extract, and optionally, hide from the display.
Figure 4-44. Exclude Command Window


------------------- 


Object Types to Exclude:

DB2 objects
===> N
( Y = Yes, N = No
EXclude DB2

MVS objects
===> N
E = Exclude and hide) EXclude MVS


END to process and return

File-AID/RDX -------------- Exclude Command
Command ===>



Select the object types to exclude, then press END to exit the window.
DB2 objects : Enter Y to exclude all DB2 objects/relationships. Enter E to exclude
and hide all DB2 objects/relationships. Enter N if you don’t want to exclude all
DB2 objects/relationships from the extract. N does not unexclude excluded
objects, use the UNEXCLUDE primary or line command.
MVS objects : Enter Y to exclude all MVS objects/relationships. Enter E to exclude
and hide all MVS objects/relationships. Enter N if you don’t want to exclude all
MVS objects/relationships from the extract. N does not unexclude excluded
objects, use the UNEXCLUDE primary or line command.
Extract
4-61
FIND (F) : Searches the object list for the specified string and scrolls the list to display
the first matching entry at the top of the displayed entries. Use RFind to repeat the
search.
FUNCTION LOCK : Enables the “Lock Table during Extract” function for all DB2 objects.
The “Extract Scope - Object View” panel will display and enable the L line command
and display the L status column. See also “L (Lock Table)” on page 4-58. FUNCTION
LOCK is a toggle switch so enter FUNCTION LOCK again to return to the original
format.
Note:
The FUNCTION LOCK primary command is only valid if File-AID/RDX was
configured at installation to allow locking tables during extract.
HIDE (H) : The HIDE command allows less data to be displayed. Included or excluded
objects can be hidden from the display so that the remaining content is more
meaningful. Use the RESET command to return all hidden objects to the display.
HIDE Command Window
When you enter the HIDE command, File-AID/RDX will pop up the Hide Command
Window as shown in Figure 4-49. Select the object status types you want to hide from
the display.
Figure 4-45. Hide Command Window


File-AID/RDX --------------- HIDE COMMAND -------------------Command ===>
Object Status to Hide:
Included
===> N
Excluded
===> N
END to process and return

Primary Command:
Hide INclude
Hide EXclude









Select the object status types to hide or redisplay, then press END to exit the window.
Included : Enter Y to hide all objects/relationships that are included in the extract.
Enter N to display all objects/relationships that are included in the extract.
Excluded : Enter Y to hide all objects/relationships that are excluded from the
extract. Enter N to display all objects/relationships that are excluded from the
extract.
NAVIGATION (NAV) : The NAVIGATION command takes you directly to the
“Relationship Navigation Criteria” screen (see Figure 4-54 on page 4-73).
REPORT (REP) : Prints the logical contents of the display. This report includes all of the
displayable lines formatted like the current view.
RESET (RES) : Use the RESET command to return all hidden objects to the display.
SAMPLE (SAM) : The SAMPLE command takes you directly to the “Relationship
Sampling Criteria” screen (see Figure 4-52 on page 4-70).
SIZE (SI) : Increases the scrollable area to display more entries at a time by hiding some
of the screen header lines. SIze is a toggle switch so enter SIze again to return to the
original display format.
STATUS (STAT) : The STATUS command takes you directly to the “Relationship Criteria”
screen (see Figure 4-47 on page 4-63).
UNEXCLUDE (U) : The UNEXCLUDE command allows you to unexclude all objects or
all objects of a specified object type to be included in the extract. UNEXCLUDE
without parameter displays the “Unexclude Command Window” (see Figure 4-46).
4-62
File-AID/RDX Reference
Use this command in conjunction with the X (eXclude) line command or EXCLUDE
primary command when you have a long list of objects displayed and you want to
reverse a previous EXCLUDE command to include objects in the extract again.
Enter the UNEXCLUDE ALL command to undo a previous EXCLUDE command for
all objects in the list displayed on the “Extract Scope - Object View” screen from the
extract.
The optional parameters DB2 and MVS limit the UNEXCLUDE command to one of
the two object types.
UNEXCLUDE Command Window
When you enter the UNEXCLUDE command without parameters, File-AID/RDX
displays the “Unexclude Command Window” as shown in Figure 4-46. Select the
object types you want to include in the extract again (reverse a previous EXCLUDE
line or primary command).
Figure 4-46. Unexclude Command Window



File-AID/RDX -------------- Unexclude Command ------------------- 
Command ===>


Object Types to Unexclude:

DB2 objects
===> N
( Y = Yes, N = No )
UNEXclude DB2
MVS objects
===> N
UNEXclude MVS

END to process and return





Select the object types to unexclude, then press END to exit the window.
DB2 objects : Enter Y to unexclude all DB2 objects. Enter N if you don’t want to
unexclude all DB2 objects. N does not exclude included objects, use the
EXCLUDE primary or line command.
MVS objects : Enter Y to unexclude all MVS objects. Enter N if you don’t want to
unexclude all MVS objects from the extract. N does not exclude included objects,
use the EXCLUDE primary or line command.
VIEW (VI) : The VIEW command allows you to easily switch between the object and
relationship views. The optional parameters SAMPLE, STATUS (default) and
NAVIGATION can be used to go directly to the corresponding format of the
relationship view. You can also enter these parameters as stand-alone primary
commands although they are not included on the primary command line for the
object view but will be processed if entered.
Extract
4-63
Extract Scope - Relationship Criteria
The “Relationship Criteria” screen shown in Figure 4-47 is displayed when you specify R
in the “Extract Scope Detail View” field of the “Extract Scope Screen” (Figure 4-40 on
page 4-50) or enter the VIEW STATUS primary command in the “Extract Scope - Object
View” (Figure 4-42 on page 4-56) or any of the “Relationship Criteria” screens.
Figure 4-47. Relationship Criteria
----------- Row 1 to 7 of 12 
Scroll ===> PAGE 

Primary Commands: EXclude/Unex, Find, Hide, FILter, CHEck, SIze, SOrt, VIew 
STATus, SAMple, NAVigation, VALidate, GRaphic, REPort

Line Commands: X = Exclude
U = Unexclude
I = Info

Driving Object: FRSAMP.ORDER_TABLE

SSID: DSN
Location: DSNLOCAT

Seq Object Name
Status/Description 
---- ---------------------------------------------- -----------------------
0001 FRSAMP.CUSTOMER_TABLE
Inactive

FRSAMP.CONTACT_TABLE
CONTCUST

0002 FRSAMP.CUSTOMER_TABLE

FRSAMP.ORDER_TABLE
CUSTOMER-ORDER RELATIONS

0003 FRSAMP.ORDER_TABLE

FRSAMP.ORDER_LINE_TABLE
ORDLORD

0004 FRSAMP.PART_TABLE

FRSAMP.ORDER_LINE_TABLE
ORDLPRT

0005 FRSAMP.PART_TABLE
Inactive

FRSAMP.SUPPLIER_TABLE
SUPPPART

0006 FRSAMP.SUPPLIER_TABLE
Excl Scope

'TSOID01.FRSAMP.SUPPLIER'

0007 'TSOID01.FRSAMP.CUSTOMER'
Inactive

'TSOID01.FRSAMP.CONTACTT'
File-AID/RDX -----------Command ===>
Relationship Criteria
This screen displays a list of referential integrity (RI) and application (AR) relationships
defined in the relationship file for the driving object.
A sequence number allows positioning directly to a specific relationship and makes it
easier to see the panel changes when scrolling. The sequence number field is also the line
command field.
The Relationship Name in the Status field for the dependent object makes it easier to tell
the difference between multiple relationships between the same objects.
Use this screen to specify which, if any, relationships to exclude from the extract process
and how many rows from dependent objects to extract from those relationships not
excluded. In addition, you can request information about a specific relationship.
If there are more relationships on this list than will fit on this screen, you can scroll the
list up and down using standard scrolling commands. See “Scrolling” on page 1-9 for
more information about scrolling.
Fixed Display Area
In addition to the screen title, the COMMAND field, and the scroll amount input field,
the top area of the screen contains
– a message indicating how many relationships were retrieved for display
– a message indicating the driving object for which these relationships were
retrieved, including the DB2 subsystem and location IDs
– a message indicating the hide/filter status of the display
Scrollable Display Area
This screen area displays a list of referential integrity and application relationships
containing the following columns:
4-64
File-AID/RDX Reference
Seq : The Sequence column displays the sequence number for the listed relationships for
the current extract request. Enter line commands in this column. See “Line
Commands” on page 4-58 for information about valid commands for this screen.
Object Name (Parent) : Displays the name of the object defined as the parent in a
relationship in the upper row (the row with the Seq number).
Object Name (Dependent) : Displays the name of the object defined as the dependent in
a relationship in the lower row, under its parent.
Status : Displays one of the following messages in the upper row:
Message
Explanation
Excl All
This relationship is excluded from the current extract process as one of the
related objects is marked to extract all of its records and not chase any of its
relationships. This status is the result of the “A (All)” line command (page 4-58)
on the “Extract Scope - Object View” screen.
Excl Miss
This relationship is excluded from the current extract process because at least
one of the related objects does not exist.
Excl Scope
This relationship, with navigation (DPSI) settings of “----”, is excluded as the
result of another relationship’s DPSI settings that make it impossible for the
extract to navigate to this relationship. Any changes you make to this
relationship directly have no affect on the extract. This includes changes to the
sampling criteria and the DPSI settings as well.
Inactive
A relationship with one or more DPSI switches set to “N”. but none to “Y”, is
considered inactive, but still within the scope of the extract as its DPSI settings
can be changed.
Note that in Object View, an object is marked excluded when all of its
relationships are marked inactive.
Excl User
This relationship is excluded from the current extract process. This status is the
result of the EXCLUDE primary or line command.
KEY Undef
For this relationship you still need to define an Output Key file with Extract
Menu Option “6 - Output Key Files” or exclude this relationship from the
current extract process, before you can continue.
KEY Def
An output key file has been defined for this KEY relationship.
KEY Deleted
The output key file definition for this KEY relationship has been deleted.
Relationship Name
The lower, second Status row for each relationship displays the relationship name
(DB2 RI RELNAME or the relationship description for application relationships).
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
I (Relationship Information) : Invokes the Relationship Information window. See
“Relationship Information Window” on page 4-79 for information about the
Relationship Information window.
U (Unexclude) : Selects a previously excluded relationship to be included in the extract.
Remember, you cannot undo an excluded relationship when its link to the driving
object is through another, still excluded relationship. See also “X (Exclude)”.
Note:
When the excluded status for a relationship has been set by a navigation
control, it can only be undone with a navigation control, not with the
Unexclude line command.
X (Exclude) : Excludes a relationship from the extract. When you exclude a relationship,
other relationships might also be excluded as a result. This occurs when you exclude
a relationship and either of the objects in the excluded relationship is a parent or
dependent in another relationship that cannot be linked back to the driving object
Extract
4-65
in any other way. For example, assume three relationships exist as shown below and
ORDER_TABLE is the driving object.
Parent Object
Dependent Object
ORDER_TABLE
ORDER_LINE_TABLE
ORDER_LINE_TABLE
PART_TABLE
PART_TABLE
SUPPLIER_TABLE
When the ORDER_LINE_TABLE to PART_TABLE relationship is excluded, the
PART_TABLE to SUPPLIER_TABLE relationship will also be excluded.
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
CHECK (CHE) : Use the CHECK command to verify the extract paths after you made
navigation changes. When the path integrity validation processing is complete, the
results are displayed in the “Check Extract Warning” screen (Figure 4-60 on page
4-80) where you can resolve or ignore the findings. File-AID/RDX executes the
CHECK command whenever it returns from the “Extract Scope Detail View” panels.
Note:
CHECK is not valid when when the extract request is built with relationships
in the Direct Plus or All Children Only mode (see “Direct” on page 4-50).
EXCLUDE (EX or X) : The EXCLUDE command allows to exclude all relationships or all
relationships of a specified object type to be excluded from the extract. EXCLUDE
without parameter displays the “Exclude Command Window - Relationship View”
(see Figure 4-48).
Use this command in conjunction with the U (Unexclude) line command or
UNEXCLUDE primary command when you have a long list of relationships
displayed and you want to include only a few relationships in the extract.
Enter the EXCLUDE ALL command to exclude all relationships in the list displayed
on the “Relationship Criteria” screens from the extract.
The other parameters DB2, KEY, and MVS limit the EXCLUDE command to one of the
three object types.
EXCLUDE Command Window
When you enter the EXCLUDE command without parameters, File-AID/RDX displays
the “Exclude Command Window - Relationship View” as shown in Figure 4-48. Select
the object types you want to exclude from the extract, and optionally, hide from the
display.
Figure 4-48. Exclude Command Window - Relationship View

File-AID/RDX -------------- EXclude Command
Command ===>
-------------------
Relationships with object types to be excluded

DB2 objects
===> N
( Y = Yes, N = No
EXclude DB2
MVS objects
===> N
E = Exclude and hide) EXclude MVS
KEY files
===> N
EXclude KEY



END to process and return







Select the object types to exclude, then press END to exit the window.
DB2 objects : Enter Y to exclude all relationships involving DB2 objects. Enter E to
exclude and hide all relationships involving DB2 objects. Enter N if you don’t
4-66
File-AID/RDX Reference
want to exclude all relationships involving DB2 objects from the extract. N does
not unexclude excluded relationships, use the UNEXCLUDE primary or line
command.
MVS objects : Enter Y to exclude all relationships involving MVS objects. Enter E to
exclude and hide all relationships involving MVS objects. Enter N if you don’t
want to exclude all relationships involving MVS objects from the extract. N does
not unexclude excluded relationships, use the UNEXCLUDE primary or line
command.
KEY files : Enter Y to exclude all relationships involving KEY files. Enter E to exclude
and hide all relationships involving KEY files. Enter N if you don’t want to
exclude all relationships involving KEY files from the extract. N does not
unexclude excluded relationships, use the UNEXCLUDE primary or line
command.
Note:
If a KEY output file is not to be produced for an extract, the relationship
which defines the KEY file must be excluded from the extract.
FILTER (FIL) : The FILTER command restricts the relationships being displayed to the
relationships for the object(s) that contain the specified object name string. Any
relationship where the specified object is either a parent or a child will be displayed.
The FILTER command can be issued to build a display that contains the relationships
for multiple objects by choosing the option to retain the currently filtered list. For
example, you could issue the FILTER command to display the relationships for PROJ
resulting in a display of only the PROJ relationships. Then issue FILTER again, this
time requesting the relationships for EMP and specifying to retain the currently
filtered list. The resulting display will contain all relationships for PROJ and EMP.
This is the same functionality available from the object view when the R line
command is issued for multiple objects prior to the VIEW command.
FILTER Command Window
When you enter the FILTER command, File-AID/RDX will display the Filter
Command Window as shown in Figure 4-49. Enter the object for which you want to
display all relationships, and specify the other filtered list options.
Figure 4-49. Filter Command Window

Filter Command

Command ===>
Display only the relationships where the object name
contains the following string:


Object Name Field
===>
Include Creator Name ===>
Retain Current Filtered List ===> N
(Y = Yes, N = No)
END to process and return









Specify the object name and filtered list options.
Object Name Field : Enter the name of the object for which to display all
relationships.
File-AID/RDX will display all relationships for the object(s) that contain the
specified object name string.
Include Creator Name : Specify whether the displayed relationships for DB2 objects
should also include the objects’ creator name.
Extract
4-67
Retain Current Filtered List : Enter Y to add the specified object to the current list
of displayed relationships. Enter N to clear the current filtered list and display
only the relationships for the specified object.
FIND (F) : Searches the list of displayed relationships for the specified string and scrolls
the list to display the first matching entry at the top of the displayed entries. Use
RFind to repeat the search.
GRAPHIC (GR) : Enter the GRAPHIC command to invoke the Graphical Relationship
Display screen and show RI and application relationships for the driving object. See
“Graphical Relationship Display” on page 4-76 for more information on the
Graphical Relationship Display screen. There are no operands associated with this
command.
HIDE (H) : The HIDE command allows less data to be displayed. With the parameters
INcluded and EXcluded you can hide relationships from the display so that the
remaining content is more meaningful. Hide without a parameter displays the “Hide
Command Window” as shown in Figure 4-50. Use the RESET command to return all
hidden objects to the display.
HIDE Command Window
When you enter the HIDE command without a parameter, File-AID/RDX displays the
Hide Command Window as shown in Figure 4-50. Select the object status types you
want to hide from the display.
Figure 4-50. Hide Command Window


File-AID/RDX --------------- HIDE COMMAND -------------------Command ===>
Object Status to Hide:
Included
===> N
Excluded
===> N
END to process and return

Primary Command:
Hide INclude
Hide EXclude









Select the object status types to hide or redisplay, then press END to exit the window.
Included : Enter Y to hide all objects/relationships that are included in the extract.
Enter N to display all objects/relationships that are included in the extract.
Excluded : Enter Y to hide all objects/relationships that are excluded from the
extract. Enter N to display all objects/relationships that are excluded from the
extract.
NAVIGATION (NAV) : The NAVIGATION command takes you directly to the
NAVIGATION format of the relationship view (see Figure 4-54 on page 4-73).
REPORT (REP) : Prints the logical contents of the display. This report includes all of the
displayable lines formatted like the current view.
RESET (RES) : Use the RESET command to return all hidden objects to the display.
SAMPLE (SAM) : The SAMPLE command takes you directly to the SAMPLE format of the
relationship view.
SIZE (SI) : Increases the scrollable area to display more entries at a time by hiding some
of the screen header lines. Size is a toggle switch so enter Size again to return to the
original format.
SORT (SO) : Sorts the displayed list of relationships by the specified sequence (column)
name. Valid SORT sequences are:
SEQ : (sequence number)
4-68
File-AID/RDX Reference
PAR : (parent object name)
DEP : (dependent object name)
ST : (status)
DESC : (description)
STATUS (STAT) : The STATUS command switches the display to the “Relationship
Criteria” view.
UNEXCLUDE (U) : The UNEXCLUDE command allows you to unexclude all
relationships or all relationships of a specified object type to be included in the
extract. UNEXCLUDE without parameter displays the “Unexclude Command
Window - Relationship View” (see Figure 4-51).
Use this command in conjunction with the X (eXclude) line command or EXCLUDE
primary command when you have a long list of relationships displayed and you want
to reverse a previous EXCLUDE command to include objects in the extract again.
Enter the UNEXCLUDE ALL command to undo a previous EXCLUDE command for
all objects in the list displayed on the “Relationship Criteria” screens from the
extract.
The optional parameters DB2, KEY, and MVS limit the UNEXCLUDE command to one
of the three object types.
UNEXCLUDE Command Window
When you enter the UNEXCLUDE command without parameters, File-AID/RDX
displays the “Unexclude Command Window - Relationship View” as shown in Figure
4-51. Select the object types you want to include in the extract again (reverse a
previous EXCLUDE line or primary command).
Figure 4-51. Unexclude Command Window - Relationship View



File-AID/RDX -------------- Unexclude Command ------------------- 
Command ===>


Object Types to Unexclude:

DB2 objects
===> N
( Y = Yes, N = No )
UNEXclude DB2
MVS objects
===> N
UNEXclude MVS
KEY files
===> N
UNEXclude KEY

END to process and return




Select the object types to unexclude, then press END to exit the window.
DB2 objects : Enter Y to unexclude all relationships involving DB2 objects. Enter N
if you don’t want to unexclude all relationships involving DB2 objects. N does
not exclude included relationships, use the EXCLUDE primary or line command.
MVS objects : Enter Y to unexclude all relationships involving MVS objects. Enter N
if you don’t want to unexclude all relationships involving MVS objects from the
extract. N does not exclude included relationships, use the EXCLUDE primary or
line command.
KEY files : Enter Y to unexclude all relationships involving KEY files. Enter N if you
don’t want to unexclude all relationships involving KEY files from the extract. N
does not exclude included relationships, use the EXCLUDE primary or line
command.
Note:
If a KEY output file is not to be produced for an extract, the relationship
which defines the KEY file must be excluded from the extract.
Extract
4-69
VALIDATE (VAL) : The VALIDATE command validates all relationships in the current
extract request against the relationship file. The message “No changes” informs you
that all relationships have been successfully validated. If there are inconsistencies,
the “Update Saved Request Window” reports the validation results and gives you the
opportunity to update the saved request or reload the request as last saved. Refer to
“Update Saved Request Window” on page 4-82 for more information.
VALIDATE corresponds to RDX Utilities Option 1, “Update Saved Extract Requests”,
except that it executes online and only on the current request.
Note:
VALIDATE is not valid when the extract request is built with relationships in
the Direct Plus or All Children Only mode (see “Direct” on page 4-50).
VIEW (VI) : The VIEW command allows you to easily switch between the object and
relationship views. VIEW without any parameter displays the “Extract Scope - Object
View” screen. VIEW with one of the parameters SAMPLE, STATUS and NAVIGATION
displays the corresponding format of the relationship view.
4-70
File-AID/RDX Reference
Extract Scope - Relationship Sampling Criteria
The “Relationship Sampling Criteria” screen shown in Figure 4-52 is displayed when you
enter the VIEW STATUS primary command in the “Extract Scope - Object View” (Figure 442 on page 4-56) or any of the “Relationship Criteria” screens.
Figure 4-52. Relationship Sampling Criteria
File-AID/RDX -------Command ===>
--------- Row 1 from 12 
Scroll ===> CSR 

FILter, CHEck, SIze, SOrt 
VALidate, GRaphic, REPort 
Info


Sampling Criteria

Cycle MaxRow Dep Status

----- ------ --- ----------
*
*
*
Inactive
CONTCUST

*
*
*

CUSTOMER-ORDER RELATIONS 
*
*
*

ORDLORD

*
*
*

ORDLPRT

*
*
*
Inactive 
SUPPPART

*
*
*
Excl Scope

*
*
*
Inactive 
Relationship Sampling Criteria
Primary Commands: EXclude/Unex, Change, Find, Hide,
VIew, STATus, SAMple, NAVigation,
Line Commands: X = Exclude
U = Unexclude
I =
Driving Object: FRSAMP.ORDER_TABLE
SSID: DSN
Location: DSNLOCAT
Seq Object Name
---- ---------------------------------------------0001 FRSAMP.CUSTOMER_TABLE
FRSAMP.CONTACT_TABLE
0002 FRSAMP.CUSTOMER_TABLE
FRSAMP.ORDER_TABLE
0003 FRSAMP.ORDER_TABLE
FRSAMP.ORDER_LINE_TABLE
0004 FRSAMP.PART_TABLE
FRSAMP.ORDER_LINE_TABLE
0005 FRSAMP.PART_TABLE
FRSAMP.SUPPLIER_TABLE
0006 FRSAMP.SUPPLIER_TABLE
'TSOID01.FRSAMP.SUPPLIER'
0007 'TSOID01.FRSAMP.CUSTOMER'
'TSOID01.FRSAMP.CONTACTT'
Use this screen to specify which, if any, relationships to exclude from the extract process
and how many rows from dependent objects to extract from those relationships not
excluded. In addition, you can request information about a specific relationship.
This screen displays a list of referential integrity (RI) and application (AR) relationships
defined in the relationship file for the driving object and the sampling criteria setting for
each individual relationship.
If there are more relationships on this list than will fit on this screen, you can scroll the
list up and down using standard scrolling commands. See “Scrolling” on page 1-9 for
more information about scrolling.
Fixed Display Area
In addition to the screen title, the Command field, and the scroll amount input field, the
top area of the screen contains
– a message indicating how many relationships were retrieved for display
– a message indicating the driving object for which these relationships were
retrieved
– DB2 subsystem ID and remote location ID if the extract includes DB2 objects
Scrollable Display Area
This screen areas displays a list of referential integrity and application relationships
containing the following columns:
Seq : The SEQuence column displays the sequence number for the listed relationships for
the current extract request. Enter line commands in this column. See “Line
Commands” on page 4-58 for information about valid commands for this screen.
Object Name (Parent) : Displays the name of the object defined as the parent in a
relationship in the upper row (the row with the SEQ number).
Extract
4-71
Object Name (Dependent) : Displays the name of the object defined as the dependent in
a relationship in the lower row, under its parent.
Sampling Criteria : Displays the status of the three sampling criteria settings for each
relationship. Initially, the sampling criteria are set globally as specified in your
current extract profile. You can change each individual setting simply by typing over
a new value or use the CHANGE primary command to globally change the sampling
criteria fields.
Cycle : Specify the maximum number of cycles for each individual relationship.
Cycle only applies to downward navigation via the Sibling and Indirect paths.
Max Rows : Specify the maximum number of rows to extract via downward
navigation (direct, indirect and sibling) of this relationship. The Max Rows
profile value applies to each relationship and each object. The relationship Max
Rows value is processed first; if the count does not exceed the limit, the record is
passed on to check against the object Max Rows value.
Dep : (Dependents-per-parent) Enter the maximum number of dependent records
to be extracted for each parent record extracted. An asterisk (*) indicates that
File-AID/RDX will extract all dependent records. A value of 2, for example,
specifies to select no more than 2 dependent ORDER records for each extracted
parent CUSTOMER record. For KEY relationships, this field is not applicable.
Status : Displays one of the following messages in the upper row:
Message
Explanation
Excl All
This relationship is excluded from the current extract process as one of the
related objects is marked to extract all of its records and not chase any of its
relationships. This status is the result of the “A (All)” line command (page 4-58)
on the “Extract Scope - Object View” screen.
Excl Miss
This relationship is excluded from the current extract process because at least
one of the related objects does not exist.
Excl Scope
This relationship, with navigation (DPSI) settings of “----”, is excluded as the
result of another relationship’s DPSI settings that make it impossible for the
extract to navigate to this relationship. Any changes you make to this
relationship directly have no affect on the extract. This includes changes to the
sampling criteria and the DPSI settings as well.
Inactive
A relationship with one or more DPSI switches set to “N”. but none to “Y”, is
considered inactive, but still within the scope of the extract as its DPSI settings
can be changed.
Note that in Object View, an object is marked excluded when all of its
relationships are marked inactive.
Excl User
This relationship is excluded from the current extract process. This status is the
result of the EXCLUDE primary or line command.
KEY Undef
For this relationship you still need to define an output key file with Extract
Menu Option “6 - Output Key Files” or exclude this relationship from the
current extract process, before you can continue.
KEY Def
An output key file has been defined for this KEY relationship.
KEY Deleted
The output key file definition for this KEY relationship has been deleted.
Relationship Name
The lower, second Status row for each relationship displays the relationship name
(DB2 RI RELNAME or the relationship description for application relationships).
Line Commands
See “Line Commands” on page 4-64 for the description of the available line commands.
4-72
File-AID/RDX Reference
Primary Commands
See “Primary Commands” on page 4-65 for the description of the available primary
commands not listed here.
CHANGE (C) : Change allows global changes to be made to the sampling criteria on a
column-by-column basis. When the CHANGE command is entered with one of the
available parameters CYC=n, MAXROW=n, or DEP=n, all values are changed to the
new value n. When entered without parameters, specify the values to change in the
“CHANGE Command Window - Relationship Sampling Criteria”.
CHANGE Command Window
When you enter the CHANGE command without parameters, File-AID/RDX will pop
up the “CHANGE Command Window - Relationship Sampling Criteria” as shown in
Figure 4-53.
Figure 4-53. CHANGE Command Window - Relationship Sampling Criteria


File-AID/RDX -------------- CHANGE COMMAND ------------------Command ===>
Change ALL occurrences of "from string" value to "to string"
From string ===>
To string
===>
Act on the
Cycle
MaxRow
Dep
following fields:
===> N
( Y = Yes, N = No)
===> N
===> N
Primary command:
Change CYCle=n
Change MAXROW=n
Change DEP=n
END to process and return

***NOTE: Change will be applied to all qualified objects,
even those that are excluded or hidden. 














Enter the Change ‘from string’ and the Change ‘to string’ values and select the
sampling criteria types you want to change globally for all relationships.
From string : Enter the current From (old) string you want to change to the To (new)
string in the sampling criteria.
To string : Enter the to (new) string you want to replace the from (old) string with in
the specified sampling criteria.
Cycle : Enter Y to apply the change to all matching Cycle values. Enter N if the
change is not to be applied to the Cycle sampling criteria.
MaxRow : Enter Y to apply the change to all matching MaxRow values. Enter N if
the change is not to be applied to the MaxRow sampling criteria.
DEP : Enter Y to apply the change to all matching Dependents-per-parent values.
Enter N if the change is not to be applied to the Dependents-per-parent sampling
criteria.
Extract
4-73
Extract Scope - Relationship Navigation Criteria
The “Relationship Navigation Criteria” screen shown in Figure 4-54 is displayed when
you enter the VIEW NAVIGATION primary command in the “Extract Scope - Object
View” (Figure 4-42 on page 4-56) or any of the “Relationship Criteria” screens.
Figure 4-54. Relationship Navigation Criteria
Relationship Navigation Criteria --------- Row 1 from 12 
Scroll ===> CSR 

Primary Commands: EXclude/Unex, Change, Find, Hide, FILter, CHEck, SIze, SOrt 
VIew, STATus, SAMple, NAVigation, VALidate, GRaphic, REPort 
Line Commands: X = Exclude
U = Unexclude
I = Info

Driving Object: FRSAMP.ORDER_TABLE

SSID: DSN
Location: DSNLOCAT
Navigation Criteria

Seq Object Name
Dir Par Sib Ind Status

---- ---------------------------------------------- --- --- --- --- ---------- 
0001 FRSAMP.CUSTOMER_TABLE
N
Inactive

FRSAMP.CONTACT_TABLE
CONTCUST

0002 FRSAMP.CUSTOMER_TABLE
Y
N

FRSAMP.ORDER_TABLE
CUSTOMER-ORDER RELATIONS 
0003 FRSAMP.ORDER_TABLE
Y

FRSAMP.ORDER_LINE_TABLE
ORDLORD

0004 FRSAMP.PART_TABLE
Y
N

FRSAMP.ORDER_LINE_TABLE
ORDLPRT

0005 FRSAMP.PART_TABLE
N
Inactive 
FRSAMP.SUPPLIER_TABLE
SUPPPART

0006 FRSAMP.SUPPLIER_TABLE
Excl Scope 
'TSOID01.FRSAMP.SUPPLIER'

0007 'TSOID01.FRSAMP.CUSTOMER'
N
Inactive 
'TSOID01.FRSAMP.CONTACTT'
File-AID/RDX ------Command ===>
Use this screen to specify which, if any, relationships to exclude from the extract process
and how many rows from dependent objects to extract from those relationships not
excluded. In addition, you can request information about a specific relationship.
This screen displays a list of referential integrity (RI) and application (AR) relationships
defined in the relationship file for the driving object and the navigation criteria setting
for each individual relationship.
If there are more relationships on this list than will fit on this screen, you can scroll the
list up and down using standard scrolling commands. See “Scrolling” on page 1-9 for
more information about scrolling.
Fixed Display Area
In addition to the screen title, the COMMAND field, and the scroll amount input field,
the top area of the screen contains
– a message indicating how many relationships were retrieved for display
– a message indicating the driving object for which these relationships were
retrieved
Scrollable Display Area
This screen areas displays a list of referential integrity and application relationships
containing the following columns:
Seq : Enter line commands in this sequence column. The sequence number represents
File-AID/RDX internal sequencing of the applicable relationships for the driving
object. See “Line Commands” on page 4-58 for information about valid commands
for this screen.
Parent/ : Displays the name of the object defined as the parent in a relationship in the
upper row (the row with the Seq input field).
4-74
File-AID/RDX Reference
/Dependent : Displays the name of the object defined as the dependent in a relationship
in the lower row, under its parent.
Navigation Criteria : Here you specify the Navigation Criteria on an individual
relationship basis. Initially, they are set as specified globally on the “Extract Scope
Screen” and cascade through all relationships starting with the driving object.
A dash (-) in one of the navigation settings indicates that it is not meaningful for this
relationship. You cannot change the dash unless the navigation setting of a higher
relationship changes it to a Y or N.
Note:
When your profile has navigation criteria Direct set to C or P (see also
“Direct” on page 2-9), all Extract Navigation Criteria fields are protected and
cannot be modified during the extract specification.
To change a setting, type over the displayed value (Y or N) for each relationship:
Dir : (Direct) Y = Extract all of the dependents of the driving object and their
dependents. 
N = Don’t extract any of the dependents of the driving object and their
dependents.
Par : (Parent) Y = Extract parents of all extracted data to maintain the integrity of the
extracted data.
N = Don’t extract any of the parents of this relationship.
Sib : (Sibling) Y = Extract other dependents of the extracted parents from the same
relationships.
N = Don’t extract any of the siblings of this relationship.
Ind : (Indirect) Y = Extract other dependents of the extracted parents from other
relationships.
N = Don’t extract any of the indirect dependents of this relationship.
Status : Displays one of the following messages:
Message
Explanation
Excl All
This relationship is excluded from the current extract process as one of the
related objects is marked to extract all of its records and not chase any of its
relationships. This status is the result of the “A (All)” line command (page 4-58)
on the “Extract Scope - Object View” screen.
Excl Miss
This relationship is excluded from the current extract process because at least
one of the related objects does not exist.
Excl Scope
This relationship, with navigation (DPSI) settings of “----”, is excluded as the
result of another relationship’s DPSI settings that make it impossible for the
extract to navigate to this relationship. Any changes you make to this
relationship directly have no affect on the extract. This includes changes to the
sampling criteria and the DPSI settings as well.
Inactive
A relationship with one or more DPSI switches set to “N”, but none to “Y”, is
considered inactive, but still within the scope of the extract as its DPSI settings
can be changed.
Note that in Object View, an object is marked excluded when all of its
relationships are marked inactive.
Excl User
This relationship is excluded from the current extract process. This status is the
result of the EXCLUDE primary or line command.
KEY Undef
For this relationship you still need to define an output key file with Extract
Menu Option “6 - Output Key Files” or exclude this relationship from the
current extract process, before you can continue.
KEY Def
An output key file has been defined for this KEY relationship.
KEY Deleted
The output key file definition for this KEY relationship has been deleted.
Extract
4-75
Relationship Name
The lower, second Status row for each relationship displays the relationship name
(DB2 RI RELNAME or the relationship description for application relationships).
Line Commands
See “Line Commands” on page 4-64 for the description of the available line commands.
Primary Commands
See “Primary Commands” on page 4-65 for the description of the available primary
commands not listed here.
CHANGE (C) : Change allows global changes to be made to the navigation criteria on a
column-by-column basis. When the CHANGE command is entered with one of the
available parameters DIR=Y or DIR=N, PAR=Y or PAR=N, SIB=Y or SIB=N, IND=Y or
IND=N, the navigation values for all relationships are changed accordingly. When
entered without parameters, specify the navigation controls to change in the
“CHANGE Command Window - Relationship Navigation Criteria”.
CHANGE Command Window
When you enter the CHANGE command without parameters, File-AID/RDX will
display the “CHANGE Command Window - Relationship Navigation Criteria” as
shown in Figure 4-55.
Figure 4-55. CHANGE Command Window - Relationship Navigation Criteria


File-AID/RDX -------------- CHANGE COMMAND -----------------------Command ===>
Extract Navigation Criteria:
Primary command:
Direct
===> Y
( Y = Yes, N = No)
Change DIRect=Y/N
Parents
===> Y
Change PARent=Y/N
Siblings ===> N
Change SIBling=Y/N
Indirect ===> N
Change InDirect=Y/N
END to process and return

***NOTE: Change will be applied to all qualified objects,
even those that are excluded or hidden.










Enter either Y or N for the Navigation criteria settings you want to change globally
for all relationships.
Direct : Y = Extract all of the dependents of the driving object and their dependents. 
N = Don’t extract any of the dependents of the driving object and their
dependents.
Parents : Y = Extract the parent records of all extracted data to maintain the integrity
of the extracted data.
Sibling : Y = Extract other dependents of the extracted parents from the same
relationships.
Indirect : Y = Extract other dependents of the extracted parents from other
relationships.
4-76
File-AID/RDX Reference
Graphical Relationship Display
The Graphical Relationship Display screen shown in Figure 4-56 is displayed when you
enter the GRAPHIC command in one of the three “Relationship Criteria” screens.
Figure 4-56. Graphical Relationship Display Screen
File-AID/RDX ----- Graphical Relationship Display ---------- Row 1 to 18 of 23
COMMAND ===>
SCROLL ===> CSR
TAB to Object and press ENTER for an Option List
* Denotes the object is involved in additional relationships
MVS-'TSOID01.FARDX2.SAMP.ZIPCODE'
|
|__ DB2-CUSTOMER_TABLE
|
|__ MVS-'TSOID01.FARDX2.SAMP.CREDIT'
|
|__ DB2-CONTACT_TABLE
|
|__ MVS-'TSOID01.FARDX2.SAMP.SALEHIST'
|
|__ MVS-'TSOID01.FARDX2.SAMP.INVOICE'
|
|__ DB2-ORDER_TABLE
|
|__ DB2-ORDER_LINE_TABLE *
DB2-PART_TABLE
|
|__ DB2-ORDER_LINE_TABLE *
|
|__ DB2-SUPPLIER_TABLE




























Primary Command
The following File-AID/RDX-specific primary command is valid on this screen:
CREATOR : Enter the CREATOR primary command in the graphical relationship display
and all DB2 objects will include their Creator ID. This command acts as a toggle
command, thus, when entering the command again, DB2 objects will include their
Creator ID only when there is more than one object with the same name.
This screen displays a graphical representation of the relationships in which the driving
object is involved. Read the Graphical Relationship Display as follows:
• Objects are identified by their:
– Object type, either DB2, MVS, or KEY
– Object name
• DB2 objects include the table or view name. The Creator name is displayed
only if necessary to have a unique name or when you enter the CREATOR
primary command (see “CREATOR”primary command).
• MVS objects include the fully qualified file name (quoted).
• KEY objects include the fully qualified KEY record layout file or IMS database
file name (quoted).
• Relationships are arranged such that each object that has no parents is at the top of a
group. Each group consists of an object that has no parents, its dependents, their
dependents, etc. File-AID/RDX displays one group of relationships for each object
that has no parents. For example, in Figure 4-56, MVS'FARDX.V2R0M0.FRSAMP.ZIPCODE' and DB2-PART_TABLE have no parents. They are
at the top of their groups, respectively. There is one group displayed for MVS'FARDX.V2R0M0.FRSAMP.ZIPCODE' and one group displayed for DB2-PART_TABLE
Extract
Note:
4-77
For situations involving cyclical relationships, File-AID/RDX puts the
object for which the most detailed dependent display can be shown at
the top of the group.
• The driving object is highlighted. 
In Figure 4-56, MVS-'FARDX.V2R0M0.FRSAMP.CREDIT' is the driving object and is
therefore highlighted.
• Relationships are displayed as lines that connect the boxes. Lines start at the bottom
of parent objects and end at the left side of dependent objects. 
In Figure 4-56 on page 4-76, MVS-'FARDX.V2R0M0.FRSAMP.ZIPCODE' is a parent of
DB2-CUSTOMER_TABLE. DB2-CUSTOMER_TABLE itself is a parent of MVS'FARDX.V2R0M0.FRSAMP.CREDIT' and four other objects.
• Relationships that have been excluded from the extract are denoted by an X to the
left of the dependent object name. In Figure 4-56 on page 4-76, the occurrence of 
DB2-ORDER_LINE_TABLE under DB2-PART_TABLE has an X to the left of it. This
denotes the exclusion of the PART_TABLE—ORDER_LINE_TABLE relationship from
the extract.
• Objects that are displayed more than once are denoted by an asterisk (*). In Figure 456 on page 4-76, DB2-ORDER_LINE_TABLE is displayed with an asterisk next to it
because it is displayed twice (once as a dependent of DB2-ORDER_TABLE and again
as a dependent of DB2-PART_TABLE).
You can scroll up, down, left, and right to see information that does not fit on a single
screen.
Use the TAB key to move the cursor from object name to object name. When the cursor is
next to an object name, you can press ENTER to display a list of options available as
shown in Figure 4-57. In addition, you can enter the I line command to display the
Relationship Information pop-up window. See “I (Relationship Information)” on page
4-78 for more information about the I line command.
Figure 4-57. Graphical Relationship Display with Option List








File-AID/RDX ----- Graphical Relationship Display ---------- Row 1 to 18 of 23
COMMAND ===>
SCROLL ===> CSR
TAB to Object and press ENTER for an Option List
* Denotes the object is involved in additional relationships
MVS-'TSOID01.FARDX2.SAMP.ZIPCODE'
|
|__ DB2-CUSTOMER_TABLE

Option List for: MVS-'TSOID01.FARDX2.SAMP.CREDIT'

Row 1 to 3 of 3
COMMAND ===>
Enter "S" to select an option
CMD Description
--- ----------------------------------------------------------------_
Display Relationship Information(I)
_
Go to expanded view of dependents
_
Go to dependent of MVS-'TSOID01.FARDX2.SAMP.SALEHIST'
***************************** Bottom of data *****************************














To select an option from the Option List, type an S in the CMD column next to an option
and press Enter.
The options in the Option List are as follows:
Display Relationship Information (I) : Displays the Relationship Information pop-up
window. See “Relationship Information Window” on page 4-79 for more
information.
4-78
File-AID/RDX Reference
Exclude Relationships (X) : Excludes the relationship on which the cursor is positioned.
When you exclude a relationship, other relationships might also be excluded as a
result. This occurs when you exclude a relationship and either of the tables in the
excluded relationship is a parent or dependent in another relationship that cannot
be linked back to the driving object in any other way.
Undo Excluded Relationships (U) : Selects the previously excluded relationship on
which the cursor is positioned to be included in the extract.
Go to expanded view of dependents : Scrolls the display such that the first occurrence
of the selected table is positioned at the top of the display. The first occurrence of a
given table in the Graphical Relationship Display has an expanded display of its
dependents (if it has any). Subsequent occurrences of a given object do not repeat the
expanded display.
In Figure 4-57 on page 4-77, for example, if the cursor was positioned on the
occurrence of ORDER_LINE_TABLE under PART_TABLE, selecting Go to expanded
view of dependents would position the first occurrence of ORDER_LINE_TABLE at
the top of the display. The occurrence of ORDER_LINE_TABLE under ORDER_TABLE
would display any dependents if ORDER_LINE_TABLE had any.
Go to dependent of objectname : Scrolls the display such that the occurrence of the
selected object that is a dependent of objectname is at the top of the display. Use this
option to determine where the object is a dependent in other relationships.
For example, if the cursor was positioned on the second occurrence of
ORDER_LINE_TABLE when you pressed ENTER, the following entry would be
displayed:
Go to dependent of ORDER_TABLE
Selecting this entry would position the occurrence of ORDER_LINE-TABLE under
ORDER_TABLE at the top of the display. If ORDER_LINE_TABLE had additional
parents, there would be an entry on the Option List for each parent.
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen. Enter these
commands when the cursor is positioned next to a table name.
I (Relationship Information) : Displays the Relationship Information pop-up window.
See “Relationship Information Window” on page 4-79 for more information about
the Relationship Information window.
U (Unexclude) : Selects previously excluded relationships to be included in the extract.
X (Exclude) : Excludes a relationship from the extract. When you exclude a
relationship, other relationships might also be excluded as a result. This occurs when
you exclude a relationship and either of the objects in the excluded relationship is a
parent or dependent in another relationship that cannot be linked back to the
driving object in any other way. For example, assume three relationships exist as
shown below and ORDER_TABLE is the driving object.
Parent
Dependent
ORDER_TABLE
ORDER_LINE_TABLE
ORDER_LINE_TABLE
PART_TABLE
PART_TABLE
SUPPLIER_TABLE
When the ORDER_LINE_TABLE to PART_TABLE relationship is excluded, the
PART_TABLE to SUPPLIER_TABLE relationship will also be excluded.
Extract
4-79
Relationship Information Window
The Relationship Information window shown in Figure 4-58 through Figure 4-59 is
displayed when you enter the I line command on the “Extract Scope - Object View”
screen. Depending on whether you choose an RI or AR relationship (indicated in the
Type field on the Relationship Criteria screen), File-AID/RDX displays the RI or AR
version of the pop-up window. Refer to “Relationship Information Screen” on page 3-20
for a description of the fields in this window.
When you select an RI relationship with a status message, the Relationship Information
window is displayed as shown in Figure 4-58.
Figure 4-58. Relationship Information Window — RI Relationship Information



File-AID/RDX
COMMAND ===>

Parent Name:
Relationship Information
LOCATION.FRSAMP.ORDER_TABLE
DB2 Row 1 to 2 of 2
SCROLL
===> CSR 
Type: DB2

Type: DB2



Dependent Name: LOCATION.FRSAMP.ORDER_LINE_TABLE

Relationship Details:
Description:
RI - ORDLORD
Status:
Created:
1997-08-26 16.03.11.035661
User: TSOID01
Last Modified
1997-08-26 16.03.11.035661
User: TSOID01
Parent Columns /Type(Length)
Dependent Columns /Type(Length)
----------------------------------------- ---------------------------------
ORDER_NUMBER
ORDER_NUM
CHAR(6)
CHAR(6)
*** End Of Columns ***
*** End Of Columns ***
When you select an AR relationship, the Relationship Information window is displayed
as shown in Figure 4-59.
Figure 4-59. Relationship Information Screen—MVS to DB2 Application Relationship Information
File-AID/RDX
Relationship Information
DB2 ROW 1 TO 2 OF 2
COMMAND ===>
SCROLL
===> CSR

Parent Name:
’FARDX.V2R0M0.FRSAMP.ZIPCODE’
Type: MVS
Layout Dataset: FARDX.V2R0M0.FRSAMP.LAYOUT
Mbr: SMPZIP
XREF Dataset:
Mbr:
01 Level Name:
Dependent Name: LOCATION.TSOID01.CUSTOMER_TABLE
Type: DB2 



Relationship Details:
Description:
AR - ZIPCODE TO CUSTOMER
Status:
Created:
User:
Last Modified
User:
Parent Fields
/Type(Length)
Dependent Columns /Type(Length)
----------------------------------------- ------------------------------------
PARENT-KEY
CHILD-KEY
INTEGER
INTEGER
*** End Of Fields ***
*** End Of Columns ***
Use the END primary command to return to the Relationship Criteria screen.
4-80
File-AID/RDX Reference
Check Extract Warning
When the CHECK extract path routine (see primary command “CHECK (CHE)” on page
4-65) finds a possibly problematic path, File-AID/RDX displays the “Check Extract
Warning” shown in Figure 4-60.
Review the findings and use the Accept and Ignore primary and line commands to
ACCEPT or IGNORE the suggestions.
Note:
Once the problematic relationship(s) have been ignored or accepted, and you
exited this window, File-AID/RDX retains your choices and you must enter the
CHECK primary command to change the resulting status.
Figure 4-60. Check Extract Warning
File-AID/RDX -----------Command ===>
Check Extract Warning
------------ Row 1 to 1 of 1
Scroll ===> PAGE
Primary Commands: Accept, Ignore, VIew
(END = Ignore)
Line Commands: A = Accept path
I = Ignore path
Driving Object: FRSAMP.ORDER_TABLE
SSID: DSN
Location: DSNLOCAT
Object Name
Status
---------------------------------------------- ------------------------_ FRSAMP.CUSTOMER_TABLE
Excl User
FRSAMP.ORDER_TABLE
Parent path required
******************************* Bottom of data ********************************











Object Name (Parent) : Displays the name of the object defined as the parent in a
relationship in the upper row (the row with the line command input field).
Object Name (Dependent) : Displays the name of the object defined as the dependent in
a relationship in the lower row, under its parent.
Status : Displays one of the navigation status messages as described on page 4-74.
The lower, second Status row for each relationship displays the check extract path
status:
Message
Explanation
Parent path
required
This relationship is required to ensure that extracted dependent records
maintain relational integrity. If ignored, extracted orphan records might not be
loadable without their corresponding parent records.
Parent path
required - Excl
Miss
Because the excluded object is missing you cannot include it with the ACCEPT
line or primary command.
Relational error
ignored
You marked this relationship with the IGNORE line or primary command and
it will remain excluded for the extract.
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
ACCEPT (A) : Accept all suggested relationships to be included in the extract. When you
press Enter, you return to the previous Extract Scope Detailed View screen where you
entered the CHECK command or the Extract Scope screen when you exited the
“Extract Scope Detailed View” screens.
IGNORE (I) : Ignore all suggested relationships, they will not be included in the extract
and their status changes to “Relational error ignored”. You can still use the Accept
Path line command to change the status individually or enter the ACCEPT primary
command.
Extract
4-81
VIEW (VI) : The VIEW command allows you to easily switch between the object and
relationship views. SAMPLE, STATUS and NAVIGATION can be used to go directly to
the corresponding format of the relationship view.
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
A (Accept Path) : Accept an individual relationship to be included in the extract.
I (Ignore Path) : Ignore an individual relationship, it will not be included in the extract
and its status changes to “Relational error ignored”. You can still use the Accept Path
line command to change the status individually or enter the ACCEPT primary
command.
4-82
File-AID/RDX Reference
Update Saved Request Window
When you view a previously saved extract request and enter the VALIDATE command
(“VALIDATE (VAL)” on page 4-69) in the “Relationship Criteria” screens and the
validation routine finds one or more inconsistencies File-AID/RDX displays the Update
Saved Request Window (see Figure 4-61).
Figure 4-61. Relationship Listing — Update Saved Request Window
Relationship Navigation Criteria ---------- Row 1 from 3 
Update Saved Request 
Command ===>
SCR Row 1 to 11 of 22 

Use END to replace the original request with the updated request

CANCEL to revert to the original request


Original Request: TSOID01.FRSAMP45.EXTCRIT(GDGWSEL)


Message Action/Description

-------- ----------------------------------------------------------------- 
RDXEE210 A relationship in the request is no longer in the relati

onship dataset.

RDXEE198 Parent. . .:MVS-TSOID01.GDG.BASE(0)

RDXEE199
Dependent:MVS-TSOID01.GDG.BASE(-1)

RDXEE210 A relationship in the request is no longer in the relati

onship dataset.

RDXEE198 Parent. . .:MVS-TSOID01.GDG.BASE(0)

RDXEE199
Dependent:MVS-TSOID01.GDG.BASE(-3)

RDXEE210 A relationship in the request is no longer in the relati

onship dataset.

RDXEE198 Parent. . .:MVS-TSOID01.GDG.BASE(0)

File-AID/RDX -------


Review the results of the validation and decide whether to update the extract request
with the new information from the relationship file and continue with the extract
request or whether to cancel the update and reload the request as you last saved it.
VALIDATE corresponds to RDX Utilities Option 1, “Update Saved Extract Requests”,
except that it executes online and only on a single request. Refer to “Update Saved
Extract Requests” on page 8-3 for more information on updating an extract request with
current relationship information.
Primary Commands
The following File-AID/RDX-specific primary commands are valid in this window:
END : Updates and saves the extract request with the new information from the
relationship file.
CANCEL : Cancels the update of the extract request and reloads the request as you last
saved it.
Note:
When cancelling the update you lose all changes made to the request since
the last SAVE.
Extract
4-83
Unrelated Object Definition
The “Unrelated Object Definition” screen shown in Figure 4-62 is displayed when you
select Option “3 - Unrelated Objects” on the “Extract Menu” and your extract request
doesn’t include any unrelated objects. It is also displayed when you enter the A line
command in the “Unrelated Object Specification” screen.
Figure 4-62. Unrelated Object Definition



File-AID/RDX ---------- Unrelated Object Definition
Command ===> 
* No unrelated objects defined *
-------------------------
Object Type

===> M
(DB2 or MVS)
Specify DB2 Table for Object:
SSID
===> DSN
(* or pattern for selection list)
Location
===> LOCATION
(* or pattern for selection list)
Creator
===> TSOID01
(* or pattern for selection list)
Table Name
===> DEPT
(* or pattern for selection list)

Specify MVS file for Object:
File name
===> ’TSOID01.FRSAMP.CUSTOMER’
Record layout usage
===>
(S = Single; X = XREF;)
Record layout dataset ===> ’TSOID01.FRSAMP.LAYOUT’
Member name
===>
(Blank or pattern for member list)
XREF file name
===>
Member name
===>
(Blank or pattern for member list)
I/O Exit Name
===>
ENTER to add
Use this screen to add an object, DB2 table or MVS file, to the set of objects to be
extracted. Press Enter to add an object to the list of unrelated objects and stay on this
screen. Enter END after you added all unrelated objects and the “Unrelated Object
Specification” screen (Figure 4-64 on page 4-86) will display the list of all the unrelated
objects for this extract request.
The body of the “Unrelated Object Definition” screen consists of the following fields:
Object Type : Specify the object type of the unrelated object you want to include in the
current extract set.
DB2
DB2 table
MVS
MVS file
Specify DB2 Table for Object Area
Use the fields in this area to specify the unrelated DB2 table to be added to the extract
set. When specifying patterns in the fields, File-AID/RDX presents the “Add Unrelated
DB2 Object” window shown in Figure 4-63 to assist in finding the desired table(s).
SSID : Enter the DB2 subsystem ID where the unrelated table to be extracted resides. This
field is prefilled and protected when other DB2 tables are already part of the extract
set. All DB2 tables in an extract must reside in the same subsystem. 
As long as your extract request does not include DB2 objects the DB2 subsystem ID
from your current profile is prefilled, but the field is not protected.
Location : Enter the DB2 remote location ID where the unrelated table to be extracted
resides. This field is prefilled and protected when other DB2 tables are already part of
the extract set. All DB2 tables in an extract must reside in the same subsystem.
Creator : Specify the authorization ID of the owner of the DB2 table to be added to the
extract set.
4-84
File-AID/RDX Reference
Table Name : Specify the name of the unrelated table or view you want to add to the
extract set.
Note:
Enter an asterisk (*) or pattern in the Creator or Table Name fields to select
one or multiple DB2 objects from a list (see “Add Unrelated DB2 Object”).
Specify MVS File for Object Area
Use the fields in this area to specify the unrelated MVS file you want to include in the
extract set. When specifying patterns in the fields, File-AID/RDX presents selection lists.
File name : Specify the MVS file name of the unrelated object. To complete the
specification of the MVS object you must also specify its record layout information.
Record layout usage : Indicate whether a single record layout (usage "S"), or an XREF
(usage "X") is to be used to define the selection criteria.
You must also supply a Record Layout file and member (Usage=S) or an XREF file and
member (Usage=X).
Record layout file : Specify the record layout file for the unrelated MVS object to be
added to the extract set.
Member name : Specify the member of the record layout file that contains the layout
information for the unrelated MVS object. Leave blank or use a pattern to select a
member from a list.
XREF file name : Only needed if layout usage is X. Specify the XREF file name for the
unrelated MVS object to be added to the extract set.
Member name : Specify the member of the XREF file that contains the layout
information for the unrelated MVS object. Leave blank or use a pattern to select a
member from a list.
I/O Exit Name : Specify the I/O Exit Name for the unrelated MVS object.
You only need to fill in this field when you want File-AID/RDX to use an IO exit
routine when accessing the above MVS file.
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
END : If unrelated objects have been added, END displays the “Unrelated Object
Specification” screen, which lists all unrelated objects to be extracted. If none were
added you would return to the Extract Menu.
MENU : Returns to the Extract Menu.
SQLID : Enter the SQLID primary command to change the current DB2 SQLID. Enter the
SQLID command without an operand to change the current SQLID to match the
current userid. Use the new-sqlid operand to specify any SQLID. See also “Default
SQLID” on page 2-10.
Add Unrelated DB2 Object
The “Add Unrelated DB2 Object” window shown in Figure 4-63 is displayed whenever
you enter an asterisk (*) or pattern in the DB2 Creator or DB2 Table Name fields of the
“Unrelated Object Definition” panel. It displays the results of your DB2 object filter
search and allows you to select all, none, or individual objects to be included in the
extract request as unrelated objects.
Use this window to select the DB2 objects you want to include as unrelated objects.
Extract
4-85
Figure 4-63. Add Unrelated DB2 Object
Add Unrelated DB2 Object 
Row 1 to 13 of 18
Command ===>
SCROLL ===> CSR
Primary Commands: ALL, Find
Line Commands: S = Select
Fi
CO
Ob
Sp
S
L
C
T
Select objects and press END to process
Sp
F
R
R
M
X
M
I

_
_
_
_
_
_
_
_
_
_
_
_
_
Object Name
----------------------------------------------FARDX.CONTACT_TABLE
FARDX.CUSTOMER_TABLE
FARDX.CUSTOMER_1
FARDX.ORDER_LINE_TABLE
FARDX.ORDER_TABLE
FARDX.PART_TABLE
FARDX.PICX_PIC9
FARDX.SUPPLIER_TABLE
FARDX0.EDPMATTRIBUTE
FARDX0.EDPMAUATTRIBUTE
FARDX0.EDPMAUMETADATA
FARDX0.EDPMAUOBJECT
FARDX0.EDPMAUOBJSECURITY
tion
tion
tion
tion
list)
list)
list)
list)
mber list)
mber list)






















After selecting all desired DB2 objects to be included in the unrelated object list, press
END to proceed to the “Unrelated Object Specification”. If you press END without
selecting any objects, you return to the “Unrelated Object Definition” panel.
Object Name : Identifies the names of the DB2 objects that match the specified object
filter.
Line Commands
The following File-AID/RDX-specific line command is valid:
S (Select) : Selects and marks this object to be included in the unrelated object list. Blank
out the S marker for individual objects you don’t want included in the unrelated
object list. Use in conjunction with the ALL primary command to mark your
selections.
Primary Commands
The following File-AID/RDX-specific primary commands are valid:
ALL : Selects and marks all objects listed in the preview to be included in the unrelated
object list. Blank out the S marker for individual objects you don’t want included in
the unrelated object list. Use in conjunction with the S line command to mark your
selections.
FIND (F) : Searches the list for the specified string and scrolls the list to display the first
matching entry at the top of the displayed entries. Use RFind to repeat the search.
4-86
File-AID/RDX Reference
Unrelated Object Specification
The “Unrelated Object Specification” screen shown in Figure 4-64 is displayed when you
select Option “3 - Unrelated Objects” on the “Extract Menu” and your extract request
already includes one or more unrelated objects or after you added unrelated objects in
the “Unrelated Object Definition” screen.
Figure 4-64. Unrelated Object Specification
File-AID/RDX --------- Unrelated Object Specification ------ Row 1 to 2 of 2 
Command ===>
Scroll===>
CSR


Primary Commands: MENU
Line commands: A = Add Object
M = Modify MVS Object
R = Remove
U = Undo Remove

CMD Object Name
Type
Status
--- ------------------------------------------------- ---- ------------------ 
_ LOCATION.FRSAMP.EMP
DB2
_ LOCATION.FADB2.ORDER_1
DB2
******************************* Bottom of data ********************************

This screen lists all unrelated objects that are to be extracted with the current extract
request. Here you can use line commands to add objects or remove them from the list.
Enter MENU or END to return to the “Extract Menu”.
To add sampling criteria to unrelated objects, go to “Extract Scope - Object View” on page
4-56, to add selection criteria, go to “Object Selection Criteria” on page 4-94.
The scrollable area has the following columns:
CMD : Specify whether you want to
•
•
•
•
modify the layout information for an MVS object (M line command)
add an unrelated object (A line command)
remove an unrelated object (R line command)
reverse removing an unrelated object (U line command)
Object Name : Displays a list of the unrelated objects from which data is to be extracted.
Type : Displays the object type of the unrelated object.
DB2
DB2 table.
MVS
MVS file.
Status : Displays the status of the objects to be extracted. If the status message indicates
an error, you must correct the error before proceeding with the extract.
Message
Explanation
Added
The unrelated object has been added to the extract set.
Object not found
The object does not exist.
Extract
Message
Explanation
Removed
The unrelated object has been marked as remove pending with the
R (Remove) line command and will not be extracted when you
END out of the panel. You can reverse the Removed status with the
U (Undo Remove) line command or the CANCEL primary
command.
4-87
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
A (Add) : Adds an unrelated object to the extract set. When you enter the A line
command, File-AID/RDX displays the “Unrelated Object Definition” screen where
you can specify either an MVS file or a DB2 table, see Figure 4-62 on page 4-83.
M (Modify) : Use this command to change the record layout or XREF information for an
MVS object. See Figure 4-65.
R (Remove) : Removes the unrelated object from the extract set.
U (Undo Remove) : Reverses removing the unrelated object from the extract set.
Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:
MENU : Switches from this panel to the full “Extract Menu”.
Modify Unrelated MVS Object Definition
The “Modify Unrelated MVS Object Definition” screen shown in Figure 4-65 is displayed
after you entered the M (Modify) line command for an unrelated MVS object in the
“Unrelated Object Specification” screen.
Use this screen to modify the record layout and/or XREF information for the selected
MVS file.
Figure 4-65. Modify Unrelated MVS Object Definition

File-AID/RDX ---
Command ===>
Modify Unrelated MVS Object Definition
-------------------
Specify MVS File for Object:

File Name..............: 'TSOID01.FRSAMP.CONTACTT'

Record layout usage ===> S
(S = Single; X = XREF)

Record layout File ===> 'TSOID01.FRSAMP.LAYOUTS'

Member name
===> CONTACTT
(Blank or pattern for member list) 
XREF File name
===>

Member name
===>
(Blank or pattern for member list) 
I/O exit name
===> 
After modifying or viewing the MVS object information, press END to return to the
“Unrelated Object Specification” screen.
4-88
File-AID/RDX Reference
Specify MVS File for Object Area
You can change the object definition for the selected unrelated MVS file from which you
want to extract data. When specifying patterns in the fields, File-AID/RDX presents
selection lists.
File name : Displays the file name of the unrelated MVS file from which you want to
extract data.
Record layout usage : Indicate whether a single record layout (usage "S"), or an XREF
(usage "X") had been used to define the selection criteria. Only needed when no
relationships have been defined for the MVS file.
Record layout file : Specify the record layout file for the MVS object from which you
want to extract data. To view a list of layout files, specify a pattern. Valid pattern
character is * (see “Pattern Characters” on page 1-4). If you specify a pattern, the
“MVS Catalog Utility File List” window shown in Figure 4-33 on page 4-40 is
displayed if defined relationships match.
Member name : Specify the member of the record layout file that contains the layout
information for the MVS object. Leave blank or use a pattern to narrow the search.
XREF file name : Only needed if layout usage is X. Specify the XREF file name for the
MVS object from which you want to extract data. Valid pattern character is * (see
“Pattern Characters” on page 1-4). If you specify a pattern, the “MVS Catalog Utility
File List” window shown in Figure 4-33 on page 4-40 is displayed if defined
relationships match.
Member name : Specify the member of the XREF file that contains the layout
information for the MVS object. Leave blank or use a pattern to narrow the search.
I/O Exit Name : Specify the I/O Exit Name for the unrelated MVS file you want FileAID/RDX to use when accessing the MVS file.
Extract
4-89
Input Key File Specification
The “Input Key File Specification” screen shown in Figure 4-66 displays when you select
Option “4 - Input Key File” on the “Extract Menu”.
You can specify an Input Key File for either a DB2 or MVS driving object.
Note:
When an Input Key File is defined against an MVS object with an XREF, you must
select a single layout to use when extracting from the driving object. The selected
layout will be used for all records on the file; XREF processing will not be
invoked against the driving object.
Figure 4-66. Input Key File Specification
File-AID/RDX --------- Input Key File Specification -------------------------
Command ===>


Driving Object: LOCATION.FRSAMP.PART_TABLE

Specify Input Key File Information: 
Extract Driven by Input Key File ===> N
( Yes or No ) 
File Name
===>

Member
===>


Specify Delimited File Information: 
Delimited
===> NO
( Yes or No )
Quotation Marks
===> 1
(1 = Single, 2 = Double) 
Column Delimiter
===> ,

Quotes on Character Data ===> YES (Yes or No)

Quotes on Numeric Data
===> NO
(Yes or No)

If you are not using an Input Key File as input to the selection criteria for the driving
object, simply enter No (default) for the Extract Driven by Input Key File field and press
END to return to the “Extract Menu”.
If, however, you intend to use an Input Key File as input criteria for the driving object,
you must enter Yes for the Extract Driven by Input Key File field, enter the key file’s file
name and specify the key file’s format (standard DB2 or delimited). Then press Enter to
continue.
Note:
The Input Key file can only have data in three formats: CHARACTER, BINARY,
and DECIMAL. For DECIMAL, the length can only be specified in bytes and the
number of decimal places is implied to be 0.
The Output Key files produced from the KEY relationships (see also “Output Key Files” on
page 4-118) can be used as Input (External) Key files within other File-AID/RDX extracts.
This functionality provides solutions for the following:
1. Split the Extract
Some large extracts can be broken up an into multiple jobs so that independent legs
of the related objects can be extracted concurrently. The use of a KEY relationship
provides a technique to accomplish this.
One extract request can be defined to extract the higher level related objects and
produce Output Key files for each independent leg of the related set. Once that
Extract has been run the Output Key files can then be used an Input Keys files for
other extracts.
You must ensure that the relationships in the subsequent extracts are really
independent and do not require additional rows to be extracted from objects in the
original extract. Also, since the Driving object for the subsequent extracts would be a
4-90
File-AID/RDX Reference
dependent object from the first extract, the DPSI switches (see “Extract Navigation
Criteria” on page 4-50) for the parent path of these relationships should be set to N.
2. Unequal Column Lengths
When column lengths are unequal in a relationship, File-AID/RDX logic forces a
tablespace scan due to the unequal column lengths. For example, in a situation
where the dependent value always had trailing blanks and the parent value did not,
KEY file generation could be used for this relationship. Then, in the resulting Output
Key file the parent value could be padded with blanks and the Output Key file could
be used as the Input Key file which would allow for an index scan to be used.
The body of the Key File Specification screen consists of the following fields:
Specify Input Key File Information Area
Extract Driven by Input Key File : Specify Yes only when you are using an Input
(external) Key File as selection input criteria for the driving object. No is the default.
File Name : Specify the name of the file containing the keys you want to use as input
criteria for the driving object.
Note:
The key file must be in sequential or PDS format.
Member : If the file is partitioned, specify the name of the member that contains the key
data.
Specify Delimited File Information Area
Delimited : Specify whether the key file’s format is Standard DB2 (No, default) or
Delimited (Yes). Yes will continue with the Input Key File - Delimited screen as
shown in Figure 4-68 on page 4-92. No will continue with the Input Key File Positional screen as shown in Figure 4-67 on page 4-91.
Note:
The extract will fail if you specify the wrong format.
Review the delimited file format options currently set by File-AID/RDX. Compare
them to the actual delimited key file and modify the format options as needed.
Quotation Marks : Specify which quotation marks, single (’) or double (") are used in the
key file. Enter a 1 for single quotation mark. Enter a 2 for double quotation mark.
Column Delimiter : Specify which character is used as the column delimiter. The
column delimiter marks the end of the previous and the beginning of the next
column. Any displayable character, including blank character, is acceptable.
Quotes on Character Data : Specify whether character data is enclosed by quotation
marks. When set to Yes, File-AID/RDX expects character data to look like
"JONES","MARY". Numbers containing special characters, for example date fields, are
considered character data. For example, if set to Yes the date field could look like this
"1995-09-29". When set to No the data in the key file would look like this:
JONES,MARY or 1995-09-29.
Quotes on Numeric Data : Specify whether numeric data is enclosed by quotation
marks. When set to Yes, the numeric data in the key file should look like
"12345","6789". When set to No, File-AID/RDX expects numeric data to look like
12345,6789.
Input Key File - Positional
When you specify a non-delimited, standard DB2 format Input Key File as selection
criteria for the driving object, the “Input Key File - Positional” screen is displayed as
shown in Figure 4-67.
Enter the key information for the applicable column(s) and press END to exit this screen.
Extract
4-91
Figure 4-67. Input Key File - Positional
File-AID/RDX --------Command ===>
Input Key File - Positional
--------------------------
SCROLL ===> CSR

Driving Object: LOCATION.FRSAMP.ORDER_TABLE


Display Input Key File ===> B
( N = No; B = Browse; E = Edit)

Key-Format Codes available
1 = Display, 2 = Packed Decimal, 3 = Binary

Column Name
Type(Length)
Key-Postion Key-Length Key-Format

-------------------- ------------------ ----------- ---------- ---------
ORDER_NUMBER
CHAR(6)

CUST_NUM
CHAR(6)

SOC_SEC_NUM
CHAR(11)
CREDIT_CARD_NUM
CHAR(16)
ORD_TYPE
CHAR(8)

ORD_DATE
DATE

ORD_STAT
CHAR(8)

ORD_AMOUNT
DEC(9,2)

ORD_DEPOSIT
DEC(9,2)

ORD_LINE_COUNT
INTEGER

SHIP_CODE
CHAR(2)

SHIP_DATE
DATE

ORD_DESCRIPTION
VCHAR(100)

** End of Columns **

Display Input Key File : Specify whether you want to view or edit the contents of the
key file you specified as selection input for the driving object. You may want to
browse or edit the key file to verify the key file’s content.
N
Don’t browse or edit the key file.
B
File-AID/RDX will show you the contents of the key file in browse mode. Use the
standard UP, DOWN, LEFT, or RIGHT scrolling commands to view the file. Press End
to exit the browse mode.
E
File-AID/RDX will show you the contents of the key file in edit mode. Use the
standard ISPF Edit commands to edit the file. Press End to exit the edit mode.
Column Name : Displays the names of the columns in the driving object.
Type(Length) : Displays the data type of each column in the driving object. See Table 44 on page 4-97 for more information about DB2 data types.
Key File Options
When you want to use the values of a key file as selection input (WHERE EQUAL TO) for
a column of the driving object, you must enter all three fields of the Key File Options. For
example, you intend to extract all rows in the DB2 driving table where column
CUST_NUM equals the value(s) of the corresponding column in the key file. In the key
file, the value to use starts in Key-Position 7, has a Key-Length of 6, and Key-Format 1
(Display). File-AID/RDX will open the key file, take the values it finds from position 7 to
12 for all records, and extracts all rows matching the key values.
Note:
Distinct (UDT), large object (CLOB, BLOB, or DBCLOB) and ROWID columns are
not eligible for key file selection.
Key-Position : Specify the starting position of the selection value in the key file that
contains selection criteria values for the corresponding column of the driving object.
Key-Length : Specify the length of the selection value in the key file that contains
selection criteria values for the corresponding column of the driving object. See Table
4-3 for the allowable lengths for each key file format.
4-92
File-AID/RDX Reference
Key-Format : Enter the Key File Format Code that represents the non-delimited key file’s
column type format. The valid codes are listed in the upper section of the screen.
They are
1
Display format.
2
Packed Decimal format.
3
Binary format. Valid only for DB2 INTEGER and
SMALL_INTEGER column types.
When key file options are entered, File-AID/RDX checks that format and length are
compatible with the DB2 column type and length.
Table 4-3 lists the maximum key file lengths allowed for each key file format and the
corresponding DB2 column type.
Table 4-3. Maximum Key File Lengths
DB2 Column
Type
CHAR
Length Display Format 1
Length - Packed
Decimal Format 2
Length - Binary
Format 3
<= DB2 column length <= (DB2 column length)/2 Not allowed
SMALL INTEGER <=6
<=3
=2
INTEGER
<=11
<=6
=4
DECIMAL
<=Precision+2
<=(Precision+1)/2
Not allowed
Input Key File - Delimited
When you specify a delimited format Input Key File as selection criteria for the driving
object, the “Input Key File - Delimited” screen is displayed as shown in Figure 4-68.
Enter the key field number for the applicable column(s) and press END to exit this
screen.
Figure 4-68. Input Key File - Delimited
File-AID/RDX -------Command ===>
Input Key File - Delimited
----------------------------
SCROLL ===> CSR 

Driving Object: LOCATION.FRSAMP.ORDER_TABLE


Display Input Key File ===> B
( N = No; B = Browse; E = Edit)


Column Name
Type(Length)
Field-Number in delimited file

-------------------- ------------------ -----------------------------
ORDER_NUMBER
CHAR(6)

CUST_NUM
CHAR(6)

SOC_SEC_NUM
CHAR(11)
CREDIT_CARD_NUM
CHAR(16)
ORD_TYPE
CHAR(8)

ORD_DATE
DATE

ORD_STAT
CHAR(8)

ORD_AMOUNT
DEC(9,2)

ORD_DEPOSIT
DEC(9,2)

ORD_LINE_COUNT
INTEGER

SHIP_CODE
CHAR(2)

SHIP_DATE
DATE

ORD_DESCRIPTION
VCHAR(100)

** End of Columns **

Extract
4-93
Display Input Key File : Specify whether you want to view or edit the contents of the
key file you specified as selection input for the driving object. You may want to
browse or edit the key file to verify the key file’s content.
N
Don’t browse or edit the key file.
B
File-AID/RDX will show you the contents of the key file in browse mode. Use the
standard UP, DOWN, LEFT, or RIGHT scrolling commands to view the file. Press End
to exit the browse mode.
E
File-AID/RDX will show you the contents of the key file in edit mode. Use the
standard ISPF Edit commands to edit the file. Press End to exit the edit mode.
Column Name : Displays the names of the columns in the driving object.
Type(Length) : Displays the data type of each column in the driving object. See Table 44 on page 4-97 for more information about DB2 data types.
Field Number in Delimited File : When using a delimited Input Key file you specify the
field number from the key file that contains selection criteria values for the
corresponding column(s) of the driving object. For example, you want to extract all
rows in the DB2 driving object where column ORDER_NUMBER equals the value(s) of
Field 2 in the delimited key file.
Note:
Distinct (UDT), large object (CLOB, BLOB, or DBCLOB) and ROWID columns
are not eligible for key file selection.
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
CANCEL (CAN) : Enter the CANCEL command to return to the Selection Criteria
Specification screen without saving any changes. There are no operands associated
with this command.
END : Verifies the SQL syntax and returns you to the Selection Criteria Specification
screen. There are no operands associated with this command.
UDTSWAP (UDTS) : Swaps the display for distinct type columns from UDT name to the
built-in data type and length and vice versa. There are no operands associated with
this command.
UDTTYPE (UDT) : Lists all distinct data types (UDTs) that are part of the extract. The list
displays the schema, UDT name, and the built-in data type and length. There are no
operands associated with this command.
4-94
File-AID/RDX Reference
Object Selection Criteria
The “Object Selection Criteria” screen shown in Figure 4-69 is displayed when you select
Option “5 - Selection Criteria” on the “Extract Menu”.
Figure 4-69. Object Selection Criteria


File-AID/RDX ------------ Object Selection Criteria ---------------------------
Command ===>
SCROLL ===> CSR
Primary Commands: INSert, BACK, FORward, DEL, SOrt
Line Commands
: S = Add/Update Criteria
D = Delete Criteria
Driving Object: FRSAMP.ORDER_TABLE
SSID: DSN
Location: LOCATION
Set
CMD
--_
_
_
_
_
_
_
Object Name
----------------------------------------------FRSAMP.ORDER_TABLE
FRSAMP.CONTACT_TABLE
FRSAMP.CUSTOMER_TABLE
FRSAMP.ORDER_LINE_TABLE
FRSAMP.PART_TABLE
FRSAMP.SUPPLIER_TABLE
'TSOID01.FRSAMP.CUSTOMER'
** End of List **

1
of 1 

Status
--------------------
Driving
Object Excluded
Object Excluded
Unrelated with Criteria
Use this screen to perform the following tasks:
• Define one or more selection criteria sets for this extract.
• View or modify the list of objects from which File-AID/RDX will extract data.
• Select objects for which you want to specify or delete selection criteria.
This screen lists all objects that are part of the extract, including all unrelated objects
specified with Option “3 - Unrelated Objects” in the “Extract Menu” and all excluded
objects. If there are more objects on this list than will fit on this screen, you can scroll
the list up and down using standard scrolling commands. See “Scrolling” on page 1-9 for
more information about scrolling.
In addition to the screen title, the Command field, and the scroll amount input field, the
top area of the screen contains
– the name of driving object for the extract request
– DB2 subsystem ID and remote location ID if the extract includes DB2 objects
The body of this screen consists of:
SET 1 of 1 : This message indicates which selection criteria set of the extract request you
are currently viewing, defining, or modifying. For example, set 1 of 6 means that the
current set is set one out of a total of 6 sets. To switch to another set, or insert, or
delete a set, use one of the set primary commands BACK, FORWARD, INSERT,
REPEAT, or DELETE.
CMD : Specify whether you want to
• add or modify selection criteria (S line command), or
• delete selection criteria (D line command) for a given object
Object Name : Displays a list of objects from which data is to be extracted. When you
use existing extract criteria with DB2 tables this column contains the creators
associated with the tables listed in the extract criteria file. Otherwise, this column
contains the creator associated with the object driving the extract.
Extract
4-95
Status : Displays the status of the objects to be extracted. The following messages are
informational:
Message
Explanation
Driving
Indicates the object selected to drive the extract.
Driving with
Criteria Spec
Indicates that selection criteria has been specified for the driving
object.
Criteria Specified
Indicates that selection criteria has been specified for the object.
Object Excluded
The object has been excluded from the extract request.
All object
Indicates a related object with status ALL.
All object with
Criteria
Indicates that selection criteria has been specified for the related
object with status ALL.
Unrelated Object
Indicates an unrelated object that has been added with option “3
- Unrelated Objects”, for this extract request.
Unrelated with
Criteria
Indicates that selection criteria has been specified for the unrelated
object.
The following messages indicate errors. You must correct these errors before
proceeding with the extract.
Message
Explanation
Col Mis xxxx
The named column is part of the RI or application relationship, but
does not exist in the object you want to extract.
Object not found
The object does not exist.
Col Len xxxx
The column length for the specified column in the relationship file
or extract criteria file is not the same as in the table you want to
extract.
Col Typ xxxx
The column type for the specified column in the relationship file or
extract criteria file is not the same as in the table you want to
extract.
Selection Criteria
Invalid
The selection criteria specified does not match the object.
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
D (Delete) : Deletes existing selection criteria for the specified object.
S (Select) : Use this command to create new selection criteria or update existing
selection criteria.
– When the object is a DB2 table, S invokes the “DB2 Object Selection Criteria”
screen (see Figure 4-70 on page 4-97).
– Invokes the “MVS File Selection Criteria” screen when specified for an MVS file
(see Figure 4-74 on page 4-103).
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
BACK (BA) : Displays the previous selection criteria set in a criteria file (see also “Object
Selection Criteria” on page 4-94). There are no operands associated with this
command.
DELETE : Deletes the current selection criteria set in a criteria file. Valid only on the
Selection Criteria Specification Screen when defining or modifying multiple selection
criteria sets (see “Object Selection Criteria” on page 4-94). There are no operands
associated with this command.
END : Returns to the previous screen. Any newly specified selection criteria will not be
saved. There are no operands associated with this command.
4-96
File-AID/RDX Reference
FORWARD (FOR) : Displays the next selection criteria set in a criteria file. Valid only on
the Selection Criteria Specification Screen when defining or modifying multiple
selection criteria sets (see “Object Selection Criteria” on page 4-94). There are no
operands associated with this command.
INSERT (INS) : Inserts a new selection criteria set after the currently displayed set in a
criteria file. The new set’s id number equals the current set’s number incremented by
1. Example: current id = 3 of 5, id of inserted set= 4 of 6. Any following set id
numbers in the criteria file are of course incremented accordingly, for example 4 of 5
becomes 5 of 6, 5 of 5 becomes 6 of 6. Valid only on the Selection Criteria
Specification Screen when defining or modifying multiple selection criteria sets (see
“Object Selection Criteria” on page 4-94). There are no operands associated with this
command.
REPEAT (REP) : Repeats (duplicates) the current selection criteria set after the currently
displayed set in a criteria file. The new set’s id number equals the current set’s
number incremented by 1. Example: current id = 1 of 5, id of inserted set= 2 of 6. Any
following set id numbers in the criteria file are of course incremented accordingly,
for example 2 of 5 becomes 3 of 6, 3 of 5 becomes 4 of 6, etc.. Valid only on the
Selection Criteria Specification Screen when defining or modifying multiple selection
criteria sets (see “Object Selection Criteria” on page 4-94). There are no operands
associated with this command.
SORT (SO) : Sorts the displayed list of object names by the specified sequence (column)
name. Valid SORT sequences are:
N : (Object Name)
ST : (Status)
Extract
4-97
Object Selection Criteria
The “DB2 Object Selection Criteria” screen shown in Figure 4-70 is displayed when you
select a DB2 object.
Figure 4-70. DB2 Object Selection Criteria
File-AID/RDX --------- DB2 Object Selection Criteria ------------------------
Command ===>
SCROLL ===> CSR 
Set 1 of 1

Specify selection criteria for table FRSAMP.ORDER_TABLE



Column Name
Type(Length)
Where
More: > 
-------------------- ------------------ ----+---10----+---20----+---30---- 
ORDER_NUMBER
CHAR(6)

CUST_NUM
CHAR(6)

SOC_SEC_NUM
CHAR(11)
CREDIT_CARD_NUM
CHAR(16)
ORD_TYPE
CHAR(8)

ORD_DATE
DATE

ORD_STAT
CHAR(8)

ORD_AMOUNT
DEC(9,2)

ORD_DEPOSIT
DEC(9,2)

ORD_LINE_COUNT
INTEGER

SHIP_CODE
CHAR(2)

SHIP_DATE
DATE

ORD_DESCRIPTION
VCHAR(100)

Use the “DB2 Object Selection Criteria” screen to generate a DB2 SQL SELECT statement
to select rows to extract from the DB2 object based on column values.
You can scroll the lower portion of this screen up and down if there are more column
names on the list than will fit on the screen. In addition, you can scroll left and right if
the values in the Where field exceed the screen width. See “Scrolling” on page 1-9 for
more information about scrolling.
Column Name : Displays the names of the columns in the DB2 object.
Type(Length) : Displays the data type of each column in the table. The length of the
data is displayed in parentheses immediately following the data type for CHAR, CH,
VCHAR, VC, GRPH, VGRPH, DEC, FIXPIC, National data types only.
Unicode DB2 character data types are identified as CH(x), VC(x) or LV(x) with a
suffix of U16 or U-8.
See Table 4-4 for more information about DB2 data types.
Notes:
1. Distinct type (UDT) columns show either their built-in data types or their
UDT names, depending on the status of the UDTSWAP primary command. To
switch the display status enter the UDTSWAP command.
2. To view a list of all UDTs that are part of the extract issue the UDTTYPE
command.
3. When entering a WHERE clause for a UDT column you must enter the
appropriate CAST function manually. Example:
=CAST('A01' AS TSOID01.DEPARTMENT)
4. Column types CLOB, BLOB, DBCLOB, ROWID, DECFLOAT, BIGINT, BINARY,
VARBINARY, or XML are not eligible for WHERE clauses.
Table 4-4.
Data Type
Data Type Values
Value
CHAR or CH Fixed-length character strings less than or equal to 254 characters.
4-98
File-AID/RDX Reference
Table 4-4.
Data Type Values (Continued)
Data Type
Value
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
to9223372036854775807, requiring eight bytes of storage.
DEC
Fixed-length, decimal numbers in the range of -10E15 to +10E15.
DECFLOAT
Decimal Floating Point can be either DECFLOAT(16) or DECFLOAT(34) representing either
16 or 34 significant digits. The range of a DECFLOAT(16) number is 10-383 to 10+384 and
the range of a DECFLOAT(34) number is 10-6143 to 10+6144. A DECFLOAT(16) field
occupies 8 bytes and a DECFLOAT(34) occupies 16 bytes.
REAL
Fixed-length, single-precision, floating-point numbers in the approximate range of 5.4E79 to 7.2E+75.
DOUBLE
Fixed-length, double-precision, floating-point numbers in the approximate range of 5.4E79 to 7.2E+75.
DATE
A three-part value (year, month, day) whose format is determined by DB2.
TIME
A three-part value (hour, minute, second) whose format is determined by DB2.
TMSTMP(n) TIMESTAMP: A seven-part value (year, month, day, hour, minute, second, and precision)
whose format is YYYY-MM-DD-HH.MM.SS.TTTTTTTTTTTT. The precision value
(TTTTTTTTTTTT) is variable length and has 0 to 12 digits (up to picosecond) with a default
of 6 (microsecond). TMSTMP(n) specifies the scale (length) with n = 0 through 12. For DB2
Versions prior to Version 10, the length is always 6.
TMESTZ(n)
TIMESTAMP WITH TIME ZONE: An eight-part value (year, month, day, hour, minute,
second, precision, time zone) whose format is YYYY-MM-DDHH.MM.SS.TTTTTTTTTTTT±HH:MM. The precision value (TTTTTTTTTTTT) is variable
length and has 0 to 12 digits (up to picosecond) with a default of 6 (microsecond). The
time zone is the difference in hours and minutes between local time and UTC. The range
of the hour offset is -12 to +14, and the minute offset is 00 to 59. The time zone is specified
in the format ±th.tm, with values ranging from -12.59 to +14.00. TMESTZ(n) specifies the
scale (length) with n = 0 through 12. DB2 Version 10 and higher only.
CLOB
A character large object (CLOB) is a varying-length string with a maximum length of 2 147
483 647 bytes (2 gigabytes minus 1 byte).
DBCLOB
A double-byte character large object (DBCLOB) is a varying-length string with a maximum
length of 1 073 741 823 double-byte characters.
XML
A data type for storage of well formed XML documents.
BLOB
A binary large object (BLOB) is a varying-length string with a maximum length of 2 147
483 647 bytes (2 gigabytes minus 1 byte).
BINARY
BINARY is a fixed length binary string which extends the support for binary strings beyond
BLOBs. Length attribute must between 1 and 255 inclusive.
VARBINARY VARBINARY is a variable length binary string which extends the support for binary strings
beyond BLOBs. Length attribute must between 1 and 32704.
ROWID
Row identifier. A value that uniquely identifies a row. If a table contains a large object it
must also have a ROWID column.
Extract
4-99
Where : Specify values of up to 255 characters in length to limit the rows extracted from
the DB2 object. You can scroll this field left and right.
Note:
For the same column you cannot specify both a value in the Where field
and key file selections. They are mutually exclusive.
The Where column is analogous to the predicate specified in the WHERE clause in an
SQL SELECT statement. The following operators are valid in the Where column:
Operator
Description
Operator
Description
>
is greater than
>
is not greater than
<
is less than
<
is not less than
=
is equal to
IS NULL
has a null value
 = or <>
is not equal to
LIKE
searches for a pattern
>=
is greater than or equal to
IN
in a list of values
<=
is less than or equal to
BETWEEN
within a range of values
AND is implied as the logical operator between columns when multiple columns
have WHERE values specified. Specify OR to override the implied AND. Use NOT to
negate BETWEEN, LIKE, NULL, and IN operators.
Enter the WHERE clause information as you would in an SQL SELECT statement.
Use parentheses to indicate the order of operations.
Notes:
1. When entering a WHERE clause for a UDT column you must enter the
appropriate CAST function manually.
2. Column types CLOB, BLOB, DBCLOB, ROWID, DECFLOAT, BIGINT, BINARY,
VARBINARY, or XML are not eligible for WHERE clauses.
3. When using OR with two or more columns File-AID/RDX generates the
correct SQL but may not redisplay the selection template (see Figure 4-72 on
page 4-101). Use the SQL command to view the SQL and use parentheses to
indicate the order of operations.
4. When “Extract from Image Copy” is set to Yes the selection conditions are
limited to the valid predicates and labeled-duration-expressions in the
WHEN clause of the UNLOAD statement (refer to “Chapter 2-27. UNLOAD”
in the DB2 Universal Database for OS/390 and z/OS: Utility Guide and Reference,
Copyright IBM Corp. 1983, 2001.) Accordingly, some of the functions not
supported are:
•
•
•
•
•
•
Views
Casting
Built-in functions
Column functions
User Defined Functions
Arithmetic Expressions outside of those supported with
CURRENT_DATE and CURRENT_TIMESTAMP
• Exists predicate
• Subselects
• Quantified predicate
Examples:
– To select rows having a numeric column value between 9 and 20, specify:
BETWEEN 9 AND 20
– To select rows having a string, “SMITH,” anywhere in the column, specify:
LIKE '%SMITH%'
4-100
File-AID/RDX Reference
If you want to extract a specific row, Compuware recommends the following:
• Use the equals (=) operator and be as specific as possible when entering
values in the Where field.
• Specify values for columns that are part of an index.
Specifying Mixed Strings When Using DBCS
You can use mixed strings to specify values in the Where field on the Selection
Criteria screen.
Use the following syntax for CHAR, VCHAR, and LVCHAR string:
= ’ sbcs-string > dbcs-string < sbcs-string ’
where,
=
any valid operator (see “Where” on page 4-99 for a list of valid operators)
’(apostrophe) delimiter
>
DB2 shift out character
<
DB2 shift out character
sbcs-string
DBCS data
dbcs-string
DBCS data
Use the following syntax for GRPH, VGRPH, and LVGRPH strings:
=G' > dbcs-string <'
where,
=
any valid operator (see “Where” on page 4-99 for a list of valid operators)
G
constant
’ (apostrophe) delimiter
>
DB2 shift out character
<
DB2 shift out character
dbcs-string
DBCS data
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
CANCEL (CAN) : Enter the CANCEL command to return to the “Object Selection
Criteria” screen without saving any changes. There are no operands associated with
this command.
CAPS : Enter the CAPS command to toggle caps mode on and off.
END : Verifies the SQL syntax and returns you to the Selection Criteria Specification
screen. There are no operands associated with this command.
SQL : Invokes the SQL Edit screen. This screen enables you to edit or specify the selection
criteria in its SQL format. See “SQL Edit” on page 4-101 for more information about
editing your selection criteria in its SQL format. There are no operands associated
with this command.
UDTSWAP (UDTS) : Swaps the display for distinct type columns from UDT name to the
built-in data type and length and vice versa. There are no operands associated with
this command.
UDTTYPE (UDT) : Lists all distinct data types (UDTs) that are part of the extract. The list
displays the schema, UDT name, and the built-in data type and length. There are no
operands associated with this command.
Extract
4-101
Distinct Data Types for This Extract
The Distinct Data Types for This Extract window shown in Figure 4-71 is displayed when
you enter the UDTTYPE command on the Selection Criteria screen.
Figure 4-71. Distinct Data Types for This Extract Window

File-AID/RDX ----------- DB2 Object Selection Criteria -----------------------
COMMAND ===>
Distinct Data Types for This Extract
LL ===> CSR
SET 1 of 1
File-AID/RDX
Row 1 to 1 of 1

Driving Obje
COMMAND ===>
SCROLL ===> CSR

Max rows f

Select eve
Schema
Type
Base Data Type

Extract ro
-------- ------------------ -----------------of No)

Display Ex
TSOID01
DEPARTMENT
CHAR(3)
E = Edit) 
Column Nam
**************** Bottom of data *****************
More: > 
----------+---30----
DEPTNO

DEPTNAME

MGRNO

ADMRDEPT
DEPARTMENT

LOCATION
CHAR(16)

RID
CHAR(4)

TSTAMP
TMSTMP(6)

** End of Columns **

This window displays the list of all UDTs (distinct data types) that are included in the
tables to be extracted. Use the END command to close the window.
Schema : Identifies the UDT’s schema ID.
Type : Identifies the name of the distinct type.
Base Data Type : Displays the built-in data type for the UDT.
Undisplayable Criteria Specified
If you specify an existing extract request containing an SQL SELECT statement that
cannot be displayed in this format, the Selection Criteria screen is displayed as shown in
Figure 4-72. Use the SQL command to view or modify the SQL SELECT statement.
Figure 4-72. Object Selection Criteria Screen — Undisplayable Criteria Specified
File-AID/RDX ----------Command ===>

DB2 Object Selection Criteria
----------------------


Specify selection criteria for table LOCATION.FRSAMP.ORDER_TABLE



Column Name
Type(Length) Where

-------------------- ------------ ----+---10----+---20----+---30---
The existing selection criteria is in error or cannot be displayed in

this format. To view or edit the criteria, enter the SQL command. To

use the criteria, specify option above and enter the END command.



SQL Edit
The SQL Edit screen shown in Figure 4-73 is an ISPF EDIT session on the SQL source
generated by File-AID/RDX using the values you specified on the Selection Criteria
4-102
File-AID/RDX Reference
screen. It is displayed when you enter the SQL command in the COMMAND field on the
Selection Criteria screen and press Enter.
Only the WHERE clause of the SQL statement is displayed as it is the only part of the SQL
statement that can be modified for selection criteria.
Use this screen to view or modify SQL source. This can occur when you change the SQL
source in the extract criteria file from outside of File-AID/RDX.
Figure 4-73. SQL Edit Screen
EDIT - File-AID/RDX Generated SQL --------------------------- COLUMNS 000 000
COMMAND ===>
SCROLL ===> CSR
*NOTE*
*NOTE* All Columns will be extracted FROM FRSAMP.PART_TABLE
*NOTE*
****** ***************************** TOP OF DATA ******************************
000001
WHERE PART_NUMBER > 'PP0000'

000002
OR PART_NUMBER = 'BB4545'

000003
AND EFFECT_DATE = CURRENT_DATE
****** *************************** BOTTOM OF DATA *****************************
The body of the SQL Edit screen consists of a scrollable data editing area.
Line Commands
ISPF edit line commands are valid on the panel.
Primary Commands
ISPF primary commands are valid on this panel.
MVS File Selection Criteria
When you enter the S line command to specify selection criteria for an MVS object in the
“Object Selection Criteria” screen as shown in Figure 4-69 on page 4-94. File-AID/RDX
continues with the Selection Criteria Menu - TEMPORARY and allows you to specify the
selection criteria to be applied to the selected MVS object. The selection criteria will limit
the records to be extracted from the object to those that meet the criteria.
The Temporary Selection Criteria function allows you to create sets of criteria that FileAID/RDX uses to select records in a data file for processing.
File-AID/RDX provides selection criteria options and formatted selection criteria. The
selection criteria options allow you to specify:
•
•
•
•
Where to begin record selection
How to continue (selection intervals)
When to stop
Processing direction.
The selection criteria options can be combined with formatted selection criteria.
Formatted selection criteria allow you to select records based on data within a field as
specified by a record layout.
Temporary selection criteria are valid only for the duration of the extract function.
Temporary selection criteria are not stored for future use unless you explicitly save the
Extract Request file (see “Output Key File Definition” on page 4-119). When you finish
creating the temporary selection criteria, they are applied and you continue with the
Extract utility.
The next section in this chapter discusses the screen presentation order and navigation
commands available for Selection Criteria.
Extract
4-103
Selection Criteria Menu
The Selection Criteria Menu, shown in Figure 4-74, provides access to the selection
criteria options and formatted selection criteria specification.
Figure 4-74. 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 4-105.
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 4-107.
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 condition or several conditions. The conditions
can be ANDed together and several conditions separated by commas create
nested OR conditions within a set.
Primary Commands
The following primary commands are valid on the Selection Criteria Menu:
CANCEL : Returns to the “Object Selection Criteria” and clears all selection fields.
END : Saves the current selection criteria display and exits the Selection Criteria Menu
without clearing the selection fields.
VIEW : Displays the View Criteria screen, which summarizes the options and formatted
selection criteria sets into a scrollable display. See “View Criteria” on page 4-104.
4-104
File-AID/RDX Reference
View Criteria
The View Criteria screen, shown in Figure 4-75, 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 4-75. View Criteria Screen


File-AID/RDX -------------------- View Criteria ----------Command ===>
Use END to exit View Display 
Row 1 to 20 of 35
SCROLL ===> CSR
******************************* TOP OF CRITERIA *****************************
DEFINE BLOCKS=SELECTION, 

DESCRIPTION1="Selection Criteria for Data Driven AR",



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
LAYOUT_DSNAME=,
LAYOUT_MBRNAME=,
Selection Criteria Options
The Selection Criteria Options screen, shown in Figure 4-76 on page 4-105, enables you
to control record selection based on starting record key, RBA, or RRN or record counts
which determine how selection processing is executed and when it stops. File-AID/RDX
determines whether an individual 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.
Extract
4-105
Figure 4-76. Selection Criteria Options

File-AID/RDX ---------Command ===> 
Selection Criteria Options
--------------------------
Specify Selection Criteria Options:
Start at the following record key
(both blank for start of dataset)


Starting record key
- OR Starting RBA or RRN
===>
Initial records to skip
===> 0
===> 
Subsequent Selection Interval:
Records to select
===> 1
Records to skip
===> 0

Number of records to search ===> ALL
OR at the following RBA or RRN
then skip this many records

then repeat the following
- select this many records
- then skip this many records
until
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.
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
4-106
File-AID/RDX Reference
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 4-77 shows an example of the effect of selection criteria options.
Figure 4-77. Selection Criteria Options Example

Initial records to skip
===> 4

Subsequent Selection Interval:
Records to select
===> 2
Records to skip
===> 3
Number of records to search ===> 10
then skip this many records

then repeat the following
- select this many records
- then skip this many records
until
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
Extract
4-107
When the values shown in Figure 4-78 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 4-78. Selection Criteria Options Example. Default - Examines All Records


Initial records to skip
===> 0
Subsequent Selection Interval
Records to select
===> 1
Records to skip
===> 0
Number of records to search ===> ALL
then skip this many records

then repeat the following
- select this many records
- then skip this many records
until
you have read this many records
Formatted Selection Criteria
The Formatted Selection Criteria screen, shown in Figure 4-79, 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, FileAID/RDX displays the Record Layout Specification screen, shown in Figure 4-82 on page
4-115, for entry of the required information.
Figure 4-79. 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
4-108
File-AID/RDX Reference
CO
Contains; scans the specified field for the presence of a data value. CO works on an
equal condition.
NC
Not contains; scans the specified field for the absence of a data value. NC works on
a not equal condition.
BT
Between; within a range of two values (endpoints inclusive). The value is greater than
or equal to the first endpoint and less than or equal to the last endpoint.
NB
Not between; outside a range of two values (endpoints exclusive). The value is less
than the first endpoint or greater than the last endpoint.
VA
Valid numeric or packed data based on the field format.
NO
Bits are not ones (Mask data value only).
MX
Bits are mixed, ones and zeros (Mask data value only).
NV
Not valid numeric or packed data based on the field format.
FM
Field mask. See “Field Mask” on page 4-114 for more information.
Notes:
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.
Extract
4-109
The syntax of the search data is important since File-AID/RDX interprets a comma as an
OR expression. In order to search for a comma as data, enclose the comma in double
quotes (",").
For relational operators BT and NB, enter two values separated by a colon (for example,
BT -100:+100). In most cases, you will have sufficient space to enter the two values.
You can select records with an invalid field value by entering the NV relational operator.
Records with a valid field value can be selected by entering the VA relational operator.
The VA and NV operators can be used for packed decimal, and zoned decimal fields.
Relational operators CO and NC can be used to scan a field within each record for the
presence or absence of a particular value. The value for which you want to search is
entered in the data value column. Trailing blanks in the data value are ignored and not
included in the search string. The CAPS primary command controls whether FileAID/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 4-80. 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 4-80 translate into the following expression:
If ((A or B or C) and D) or E
which can also be stated as:
If (A and D) or (B and D) or (C and D) or E
Primary Commands
The following is a list of the primary commands that are valid on the Formatted Selection
Criteria screen.
ALIGN (AL) : Controls display of ALIGNED/UNALIGNED term for PL/I data.
4-110
File-AID/RDX Reference
ARRAY (AR) : Controls display of array declaration information for PL/I data.
ON : Displays an array definition line for each subscripted item in a record layout.
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.
Note:
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.
CAPS : Sets caps mode. CAPS ON is not case-sensitive in the search to match the
selection criteria. Specify CAPS OFF for a case-sensitive search. This command is valid
only on a new criteria display.
COMPLEX (CMPLX) : Controls display of COMPLEX terms for PL/I data.
DELETE (DEL, D) : Delete a selection set or subset.
DISPLAY (DIS) : Specifies a display format.
MAXREFER : (for PL/I layouts only) Specify the maximum number of occurences to
display. Omission of the DISPLAY MAXREFER command causes PL/I Refers to
default to 1 occurrence.
DOWN : Scrolls down.
END (E) : Terminates display of the Formatted Selection Criteria screen and returns to
the Selection Criteria Menu.
Extract
4-111
FILLER (FILL) : Controls display of FILLER fields.
FORWARD (FWD) : Positions the display to the next criteria. Synonym for RIGHT.
GROUP : Controls the display of occurrences of group-level items.
INPUT/ INSERT (I) : Inputs/inserts a new formatted selection criteria set.
AND : Inserts an ANDed subset of selection criteria (the set counter displays “AND
Set 1.2 of 1”) after (default) or before the current criteria.
LEFT (L) : Positions the display to the previous criteria. Synonym for BACK.
LOCATE (LOC) : Scrolls directly to the specified record layout line.
LR (Locate Record) : Positions the display to the specified criteria number.
OCCURS (OCC) : Controls the display of array declaration items.
ON : Displays an array definition line for each subscripted item in a record layout.
OFF : Does not display an array definition line.
ALL : Displays all occurrences separately with the subscript(s) and any criteria
entered on a specific occurrence will only be applied to that occurrence. This
additional parameter is only valid during Formatted Selection Criteria creation.
ANY : Displays a single entry for the occurrences and any criteria entered for the
ANY occurrence will be applied to all occurrences. The record will meet the
Selection Criteria if any of the occurrences meet the specified criteria. This
additional parameter is only valid during Formatted Selection Criteria creation.
ANY is applied for initial display of Selection Criteria.
Note:
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.
OFFSET : Displays field offsets.
OPT (O, 1) : Displays the Selection Criteria Options screen.
PROFILE (PROF) : Displays profile information lines.
4-112
File-AID/RDX Reference
REFLNG : Controls the display of BIT/CHAR REFER field length reference lines for PL/I
data.
REPEAT (R) : Causes a formatted selection criteria set, including any subsets, to be
repeated (SET 3 of 3 increments to SET 4 of 4; AND SET 3.2 of 3 increases to AND SET
4.2 of 4).
AND : Repeats an ANDed subset of selection criteria. (the set counter displays “AND
Set 1.2 of 1”) after the current criteria.
RETURN : Returns to the Primary Option Menu.
RIGHT : Positions the display to the next criteria. Synonym for FORWARD.
SHOW (SH) : Displays LEVEL, NUMBER, FORMAT, OFFSET, or PICTURE information for
the selection fields.
SYNC : Controls the display of the SYNC term for fields in a COBOL record layout.
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 4-75 on
page 4-104.
ZERO (Z) : Controls the display of leading zeros in the numeric
Selection Criteria Considerations When Data Fields May Be Nonexistent
When defining selection criteria with reference to fields where data might not exist in
some records, File-AID/RDX does not exclude those records from the selection test.
A positive selection operator, such as EQ (equal to), indicates to select the record for
processing if the condition is true.
A negative selection operator, such as NE (not equal to), indicates to select the record for
processing if the condition is false.
Therefore, when using a negative selection operator, File-AID/RDX can select records that
don’t have data in those fields.
A typical case of this is seen with fields that are specified in a record layout with OCCURS
DEPENDING ON. Some records may have several occurrences of the field, while other
records may have only one or none.
For example, consider a record layout called CUSTOMER, having a field called BALANCE
defined with up to 12 occurrences, one per month, depending on another field, called
DURATION-OF-ACCOUNT. The 12th occurrence will not exist for customers who have
had accounts with the company for less than a year.
Example:
Assume you have the following 3 records in your file:
Alice Alvarez has been a customer for 5 months and had monthly balances of 1000, 2000,
3000, 500, and 0.
Bruce Bandler has been a customer for 3 months and had monthly balances of 1000,
2000, and 3000.
Carlos Cramer has been a customer for 5 months and had monthly balances of 1000,
2000, 3000, 0, and 0.
The records look like this:
Extract
4-113
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-OFACCOUNT 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.
4-114
File-AID/RDX Reference
Field Mask
The “Field Mask Criteria” screen, shown in Figure 4-81, 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 4-81. 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

*



Note:
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.
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.
Note:
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.
Note:
Signs (+,-) are excluded when masking numeric fields.
When masking character fields, each mask position corresponds to the identical
position in the original field. The selected positions are passed as a single contiguous
character field.
Extract
4-115
The original format will be replaced by MASK on the Formatted Criteria and
Selection criteria screens, when Field Mask is in effect.
Note:
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.
Selection Criteria Record Layout Specification
File-AID/RDX displays the Record Layout Specification screen, shown in Figure 4-82 on
page 4-115, when a record layout or XREF file was not specified prior to selecting option
2, formatted selection criteria. Specify record layout or XREF information and press Enter
to continue. Use the END primary command (PF3) to return to the Selection Criteria
Menu.
Figure 4-82. Record Layout Specification Screen
File-AID/RDX ---------- Record Layout Specification --------------------------
Command ===> 

Specify Record Layout and XREF Information:
Record layout usage
===> S
(S = Single; X = XREF) 

Record layout dataset ===> FASAMP.LAYOUTS
Member name
===>
(Blank or pattern for member list) 

XREF dataset name
===> FASAMP.XREF
Member name
===>
(Blank or pattern for member list)
Selection Criteria for XREFs and Multiple Record Type Files
Specify an X in the Record layout usage field and XREF file information on the Selection
Criteria - File Specification screen to create new or edit existing formatted selection
criteria for multiple record type files. XREFs are used to specify selection criteria for
multiple record type files and segmented records. The record layout XREFs allow you to
identify the record type(s) for which you want to specify formatted record selection
criteria.
The Display XREF screen, shown in Figure 4-83, lists each layout defined in the specified
XREF. It is displayed when the data file you are selecting from contains more than one
type of record and each record type requires a different record layout (Record layout
usage = X).
Each data file record is classified into a record type category based on certain field values
within the record. In File-AID/RDX, these field values and their record layouts are
associated when the XREF is defined.
4-116
File-AID/RDX Reference
Figure 4-83. Display XREF Screen

File-AID/RDX --- Display XREF - SEGFILE --------------------- ROW 1 TO 6 OF 6
COMMAND ===>
SCROLL ===> CSR
XR113- Selection by Record ID: Enter S or SF for formatted
Member list description ===> SEGFILE XREF__________________ 
Long
===> FILE CONTAINS INS-BASE FOLLOWED BY ANY NUMBER OF ADDITIONAL___
Description ===> TRAILER SEGMENTS IN ANY ORDER - BOAT CAR BUSINESS ETC.________

Cmd
Member
Beginning Data-Name
Description
Status
--- ---------- ------------------------------ ---------------- ----------------
__ SEGRECS
INS-BASE-FILE
BASE
__ SEGRECS
CLI-BOAT-DATA
SEGMENT
__ SEGRECS
CLI-BUSINESS-DATA
SEGMENT
__ SEGRECS
CLI-CAR-DATA
SEGMENT
__ SEGRECS
CLI-HOME-DATA
SEGMENT
__ SEGRECS
CLI-LIFE-DATA
SEGMENT
************************** END OF SELECTION CRITERIA **************************
Cmd : Use the S (Select) or SF (Select Formatted) line command to specify the record
layout you want to use.
If you select a SEGMENT, the BASE associated with that segment is also implicitly
selected. The fields associated with layout selection are automatically set and locked
and flagged with a criteria value of RECORD TYPE FIELD.
Note:
With segmented records, File-AID/RDX selects only the records where
the requested segment immediately follows the base segment.
Member : Name of the record layout member.
Beginning Data-Name : Displays the starting dataname of the record layout.
Description : Short Description of the record layout entered by user when the XREF is
created.
Status : Usage status of the layout (BASE, DEFAULT, or SEGMENT) as defined in the XREF.
After you select a layout on the Display XREF screen, press Enter to display the Formatted
Selection Criteria screen (S or SF).
Use the END command (PF3) to terminate the function and return to the Selection
Criteria Menu.
Use the CANCEL command to terminate the function and return to the Selection Criteria
- File Specification screen. Use the RETURN command (PF4) to return to the FileAID/RDX Primary Option Menu without specifying any criteria.
Primary Commands
The following primary commands are valid on the Display XREF screen:
CANCEL : Terminates the selection criteria specification.
DOWN : Scrolls toward the end of a record layout.
END : Terminates the selection criteria specification.
RETURN : Returns to the File-AID/RDX Primary Option Menu.
UP : Scrolls toward the top of a record layout.
On the Formatted Selection screen the record layout fields that contain the record type
are protected and the intensified message, RECORD TYPE FIELD, is displayed in the data
column, as shown in Figure 4-84. The record type field is treated as if you had entered the
appropriate relational operator and the corresponding record type value(s).
Extract
4-117
Figure 4-84. Formatted Selection Criteria Screen. For Multiple Record Type Files.
File-AID/RDX --- Formatted Selection Criteria ---------------------------
COMMAND ===>
SCROLL ===>
CRITERIA NUMBER: 1 OF 1 ORDER-LINE-DATA-PO
LAYOUT LENGTH:
---- FIELD LEVEL/NAME ------- -FORMAT- RO ----+----1----+----2----+----3-
******************************* TOP OF DATA *****************************
5 RECORD-LENGTH
2/BI
0
5 ORDER-NO
6/AN
5 ORDER-LINE-KEY SYNC
2/GRP
7 LINE-NUMBER
2/AN
5 ORDER-TYPE
2/AN
** RECORD TYPE FIELD **
5 LINE-STATUS
7/AN
5 PART-NO
6/AN
5 DESCRIPTION
30/AN
Once you select a record type for formatted selection criteria, the records matching this
record type are selected even if you do not enter any other field criteria. On the
Formatted Selection Criteria screen, use the DELETE primary command to unselect a
record type. Use the VIEW command to check which XREF record types are active.
4-118
File-AID/RDX Reference
Output Key Files
When you select Option “6 - Output Key Files” from the “Extract Menu” and your extract
request includes only one dependent KEY relationships, the “Output Key File Definition”
panel Figure 4-86 displays.
When you select Option “6 - Output Key Files” from the “Extract Menu” and your extract
request includes more than one dependent KEY relationships, the “Output Key Files”
screen (Figure 4-85) displays.
Output Key File Layout
If the relationship was defined using a DBD, the DBD name will be included. If the
relationship was defined only using a layout, the layout name will appear. The extracted
key value begins in column 10.
Table 4-5.
Output Key File Layout
Field
IMS Segment 

or

Layout Name
Filler
Key Value
Starting Column
Ending Column
1
8
9
10
9
n
Description
Name of the IMS segment, if the
relationship was defined using a
DBD, or the name of the layout
member used to define the
relationship. Left justified.
Filler
The extracted key value.
Output Key Files List
The “Output Key Files” screen (Figure 4-85) displays when you select Option “6 - Output
Key Files” from the “Extract Menu” and your extract request includes more than one
dependent KEY relationships.
For each KEY relationship, it lists the related IMS database(s) and record or segment
layouts for the extract as specified during the relationship definition (see “Specify
Method to Define Output Key File Relationship Area” on page 3-40). You must define an
Output Key File for each KEY relationship with a status of KEY Undefined before the
extract process can continue. File-AID/RDX will store the extracted keys in the specified
file for later extract with File-AID for IMS or as an Input Key File for another File-AID/RDX
extract. You can also specify that the File-AID for IMS extract using the output key files is
to be executed as a step following the File-AID/RDX extract.
Figure 4-85. Output Key Files


File-AID/RDX ------------- Output Key Files ----------------- Row 1 to 3 of 3
Command ===>
Scroll ===> PAGE

Line commands: S = Define or update output key file
I = Information

IMS DBD Layout
Output Key File Name
Status
-------- -------- ----------------------------------------- ----------------
_ PORDR
ORDR010
KEY Undefined

_ PCUST
'TSOID01.PCUST.KEYS'
KEY Defined

_
ORDERTAB 'TSOID01.PORDR.KEYS'
KEY Defined 
******************************* Bottom of data ********************************

On this screen select an IMS DBD or segment layout to specify the Output Key File to
which File-AID/RDX will copy the key values for the selected KEY relation.
Press END to return to the “Extract Menu”.
The body of the Output Key Files panel consists of the following fields:
Extract
4-119
Cmd : Use the S (Select) or I (Information) line command to specify or view the KEY
relationship information.
IMS DBD : Member name of the DBD library (KEY method 2 and 3).
Layout : Member name of the record or segment layout (KEY method 1 and 3).
Output Key File Name : Lists the name of the file to which the extracted key values will
be saved.
Status : Displays one of the following messages:
Message
Explanation
KEY Undefined
For this KEY relationship you still need to define a key file with the S line
command, or exclude the relation from the current extract process, before you
can continue.
KEY Defined
A key file has been defined for this KEY relationship.
KEY Deleted
The key file definition for this KEY relationship has been deleted.
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
I (Relationship Information) : Invokes the Relationship Information pop-up window.
See “Relationship Information Window” on page 4-79 for information about the
Relationship Information window.
S (Select) : Use the S line command for all listed KEY relationships with a status of
Undefined. It brings up the “Output Key File Definition” window as shown in Figure
4-86, so you can define an output key file. After File-AID/RDX has completed the
extract the output key file then includes all of the output keys for this Output Key
file relationship. This file can then be used by File-AID for IMS to extract IMS data. It
can also by used by File-AID/RDX as an Input Key file for another extract.
Output Key File Definition
The “Output Key File Definition” panel Figure 4-86 displays when you enter the S line
command for an Output Key File on the “Output Key Files” screen or when you select
Option “6 - Output Key Files” from the “Extract Menu” and your extract request only
includes one KEY relationship. You must define an Output Key File for all included
relationships with a status of Undefined before the extract process can continue. FileAID/RDX will store the extracted keys in the specified Output Key File.
File-AID/RDX also allows a File-AID for IMS extract to be executed as a step following the
File-AID/RDX extract.
The JCL for the extract job must have been created within File-AID for IMS and saved to a
dataset. The File-AID for IMS extract must have been defined to use Key values in the same
format as the Output Key File produced by File-AID/RDX.
4-120
File-AID/RDX Reference
Figure 4-86. Output Key File Definition



File-AID/RDX -----------Command ===>
Output Key File Definition
------------------------

Parent Object . . .: 'TSOID01.FRSAMP.ORDERTAB'
Record Layout
Member Name .
DBD Library .
DBD Member .
Specify Output
File Name
Member
Disposition
File.: 'TSOID01.FISAMP.COBOLLIB(ORDR010)'
. . .:

. . .: PORDR

. . .: 'TSOID01.FISAMP.DBDLIB'

Key File Information:
===>
===>
(Blank or pattern for member list)
===> NEW
(NEW, OLD, SHR)
Specify File-AID for IMS Extract JCL Information:
Extract IMS ===> N
(Y=Yes, N=No)
File Name
===>
Member
===>
(Blank or pattern for member list)









Use this screen to specify the Output Key File to which File-AID/RDX will copy the key
values for the selected KEY relation. The resulting Output Key File can then be used as an
Input Key File for another File-AID/RDX extract or by File-AID for IMS to extract the
related IMS data. File-AID/RDX calculates and displays the required LRECL value. The
file’s blocksize value must be compatible with the precalculated LRECL. You can also
specify that the File-AID for IMS extract is to be executed as a step following the FileAID/RDX extract.
Press Enter after completing this window.
The body of the Output Key File Definition panel consists of the following fields:
Parent Object : Displays the name of the object defined as the parent in a relationship.
Record Layout File : Dataset name of the record or segment layout file specified during
the KEY relationship definition.
Member : Member name of the record or segment layout file.
DBD Library : Displays the name of the dependent DBD library, if specified.
DBD Member : Displays the member name of the dependent root segment.
Specify Output Key File Information
File Name : Specify the name of the file to which the extracted key values will be saved.
Member : If the file you specified in File Name is partitioned (must be PDSE), you can
enter a member name. If you leave this field blank or specify a pattern, File-AID/RDX
displays a Member List pop-up window containing a list of members that match the
specified pattern. The only valid pattern character is an asterisk (*). You can create
new members by entering the name of the new member in the Member field.
Disposition : Specify the disposition of the record layout file. You can save to existing
files with a disposition of OLD. Specify a disposition of NEW to create a new file.
If you specify NEW in the Disposition field, you must specify the following
allocation parameters in the “Create New File” panel.
Note:
Key files must be written to new or existing sequential datasets, or existing
PDSEs. Allocating a new PDSE is not supported.
Extract
4-121
Specify File-AID for IMS Extract JCL Information
Extract IMS : Specify Y (Yes) when you want the File-AID for IMS extract to be executed
as a step following the File-AID/RDX extract. The JCL for the extract job must have
already been created within File-AID for IMS and saved to a file. The file containing
the File-AID for IMS extract JCL must have a disposition of OLD.
Specify N (No - default) when you don’t want to include the File-AID for IMS extract
JCL in the File-AID/RDX extract.
File Name : Specify the name of the file that contains the File-AID for IMS extract JCL.
Member : If the file you specified in File Name is partitioned, you can enter a member
name. If you leave this field blank or specify a pattern, File-AID/RDX displays a
Member List pop-up window containing a list of members that match the specified
pattern. The only valid pattern character is an asterisk (*).
Allocate New SMS File
The “Create New File” panel (Figure 4-87) displays when you specify NEW in the
Disposition field in the “Output Key File Definition” or any other panel where you can
specify a new file. On this panel, File-AID/RDX allocates SMS-controlled Sequential, PDS,
and PDSE files.
Note:
This option is displayed only when SMS is installed at your site.
Figure 4-87. Create New File


File-AID/RDX ---------------Command ===> 
Create New File
-------------------------------

File name: TSOID01.IMSPPART.KEYFILE
Management Class
Storage Class
Generic unit
Volume serial
Data Class
Space units
Primary quantity
Secondary quantity
Directory blk
Record Format
Record length
Block size
Dataset name type

Extended Attributes
Number of Volumes
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>
===>

SYSDA
TRKS
5
5
5
FB
15

(Blank for default)
(Blank for default)
(Blank for default if unit entered)
(Blank for default)
(BLK; TRK; CYL)
(In above units)
(In above units)
(Use 0 for sequential file)
(Required for Output Key file)
(Required LRECL for Output Key file)
(LIBRARY, PDS, BASIC,
EXTREQ, EXTPREF or blank)
(NO, OPT or blank) 
(2:59, or blank)
When parameters are complete, use END to continue.
Use this screen to specify allocation values for a new file to be created by File-AID/RDX.
Depending on the type of file, File-AID/RDX calculates some of the allocation values and
locks those fields from input. For example, when creating a new extract request file, the
Record format (VB) and Record length (1004) fields are locked and their prefilled values
cannot be changed.
Press END (PF3) to allocate the SMS file, or use the CANCEL command to cancel the
allocation. When allocation is complete, File-AID/RDX displays a message: FILE
ALLOCATED in the upper-right corner of the screen.
Note:
The message “The file will be allocated during execution of the batch job”
appears for files that don’t need to be allocated until execution of the batch job.
File Name : Displays the name of the file to be allocated.
4-122
File-AID/RDX Reference
Management Class : Specify the SMS management class to use for the allocation of the
file. The management class describes the migration, backup, and retention for the
file.
Storage Class : Specify the SMS storage class to use for the allocation of the file. The
storage class describes the hardware requirements of the file.
Generic Unit : Specify the device type on which the new file will reside. The names of
these devices are installation dependent.
Volume serial : Specify the volume serial of the direct access device that contains the
file.
Data Class : Specify the SMS data class to use for the allocation of the file. The data class
describes the attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.
Space units : Specify one of the following storage unit types depending on how the file
size is expressed:
TRK - Tracks
CYL - Cylinders
BLK - Blocks
KB - Kilobytes
MB - Megabytes
Primary quantity : Specify the primary allocation quantity as specified in the space
units field.
Secondary quantity : Specify the secondary allocation quantity as specified in the space
units field.
Directory quantity : For a PDS, specify the number of directory blocks. For a Sequential
file, specify zero (0).
Record format : Specify a value with a combination of the following codes (F, V, or U is
required):
F - Fixed length
V - Variable length
U - Undefined format
B - Blocked
A - ANSI printer control characters
M - Machine code printer control characters
S - For Sequential files only: Standard for F or spanned for V
T - Track-overflow feature
Record length : Specify a logical record length, in bytes, of the records to be stored in
the file. File-AID/RDX validates this value with the record format and block size.
Block size : Specify the physical record length, in bytes, of the blocks to be stored in the
file. File-AID/RDX validates this value with the record format and record length.
Dataset name type : Specify the type of the dataset you wish to create. The type must be
one of these:
LIBRARY : Allocates a Partitioned Dataset Extended (PDSE). This type of partitioned
dataset has unlimited directory blocks and reuses its own space. PDSE libraries do
not need to be compressed.
PDS : Allocates a standard Partitioned Dataset (PDS).
EXTREQ : Indicates that an extended dataset is required.
EXTPREF : Indicates that an extended dataset is preferred.
BASIC : Indicates that neither an extended nor a large format sequential dataset is to
be allocated.
blank : Allocates a partitioned or sequential dataset based on the dataset
characteristics entered.
Extract
4-123
Extended Attributes : Specify one of the following extended attributes:
NO : Dataset cannot have extended attributes or reside in EAS.
OPT : Dataset can have extended attributes and reside in EAS.
blank : Use default based on data type.
Number of Volumes : Specify the number of volumes requested for this dataset (2 to 59),
or leave this field blank for a single volume allocation.
4-124
File-AID/RDX Reference
Extract File Specification
The Extract File Specification screen shown in Figure 4-88 is displayed when you select
Option “7 - Extract File” from the “Extract Menu”.
Figure 4-88. Extract File Specification Screen

File-AID/RDX ------------- Extract File Specification -------------------------
Command ===>

Specify Extract "TO" File Information:
File name
===> FRSAMP.EXTRACT.NEW
Member
===>
(Blank or pattern for member list)
VOLSER
===>

Disposition ===>
(NEW, OLD, SHR)


Extract File Format: 
Compress
===> N
(N = No; V = VARCHAR; C = Compress)
DB2 Format
===> 1
(1 = Unicode; 2 = Convert Unicode)

Capture create DDL during extract for:
Views ===> N
Alias ===> N
Synonyms ===> N
( Y = Yes; N = No)

Use this screen to specify information about the file to which File-AID/RDX will copy
extracted data.
Specify Extract “TO” File Information
File Name : Specify the name of the file to which data will be extracted. See “Extract
File” on page 1-23 and “File-AID/RDX Extract File” on page 4-154 for more
information on the extract file.
Notes:
1. File-AID/RDX will dynamically reallocate a sequential extract file to adjust
to the needed space. Dynamic reallocation is only available for sequential
files (DSORG=PS).
2. File-AID/RDX supports extracting from and loading to Sequential (PS) files
greater than 65,535 tracks (DSNTYPE=LARGE) when the MVS Operating
System also supports them. 
Allocation of a datasets with DSNTYPE=LARGE is not supported. If the
Extract File is to be defined as DSNTYPE=LARGE, it can be pre-allocated.
3. When the specified extract output is to tape or cartridge, File-AID/RDX
automatically creates a summary file on DASD. The name of the summary
file is the one specified in your profile or, if none is specified there, it is the
name of the extract file with SUMMARY appended or a truncated form of the
extract file name with SUMMARY as to not exceed 44 characters. If the
summary file exists, File-AID/RDX will update (overwrite) its content. Refer
to “Extract Summary File” on page 1-24 for more information.
Member : If the file you specified in File Name is partitioned, you can enter a member
name. If you leave this field blank or specify a pattern, File-AID/RDX displays a
Member List pop-up window containing a list of members that match the specified
pattern. The only valid pattern character is an asterisk (*). You can create new
members by entering the name of the new member in the Member field.
Extract
4-125
VOLSER : If the file specified in File Name is non-cataloged or new, specify the volume
serial number of the file. For non-cataloged files, a volume serial number is required.
For new files, a volume serial number is optional.
Disposition : Specify the disposition of the extract "to" file. You can extract to existing
files with a disposition of OLD. Existing files must conform to the format outlined
for the extract file in “File-AID/RDX Extract File” on page 4-154. Specify a disposition
of NEW to create a new sequential file.
If you specify NEW in the Disposition field, you must specify the following
allocation parameters in the “Create New File” screen (Figure 4-87 on page 4-121).
Extract File Format
Compress : Specify one of the compress options for the extracted data in the extract file:
N
File-AID/RDX won’t compress the extracted data. Recommended when extract
file is also to be used outside of File-AID/RDX.
V
VARCHAR compression only affects VARCHAR, LONGVAR, VARGRAPHIC, and
LONGVARGRAPHIC columns of DB2 objects; it will not apply to MVS objects. The
VARCHAR compression option only writes the actual data within each VARCHAR
column without padding the records with trailing blanks; the length of a
VARCHAR column will vary for each row based on the data within the row.
VARCHAR data written to the Extract file using VARCHAR compression will be
readable since only the trailing blanks will be dropped.
File-AID/RDX recognizes these compressed extract files as valid input files for all
functions: Load, Delete, and Disguise.
C
Note:
Compress; The extracted data will be compressed to reduce the file size and
preserve disk space. The entire data record is compressed. This technique
provides the greatest amount of data compression. File-AID/RDX recognizes these
compressed extract files as valid input files for all functions: Load, Delete, and
Disguise.
If you intend to use a compressed extract file outside of File-AID/RDX, for
example to load the extract file via File-AID/EX or manipulate it with FileAID/Data Solutions, you must decompress it beforehand. Use the
Decompress utility provided with the “Extract File Compress Utility” on page
8-20 to decompress a compressed extract file.
DB2 Format : Specify whether data extracted from DB2 tables with Unicode encoding is
written to the extract file in Unicode or EBCDIC format (see also profile value “DB2
Format” on page 2-10).
1
Unicode option will write the data using Unicode encoding.
2
Compatibility format will maintain the EBCDIC encoding used in previous
releases.
Capture create DDL during extract for
File-AID/RDX always captures the DDL for the tables it extracts related data from as well
as the corresponding indexes, tablespaces, and databases. Capturing the DDL for these
additional objects (views, alias, and synonyms) will require additional DB2 resources and
may increase the total extract time.
Views : Specify whether the extract file should include all the DB2 DDL Create View
statements necessary for File-AID/RDX to also create the DB2 views when performing
a load using this extract file. Note that DDL statements for creating views from a
view will not be included.
Yes
Extracts all DB2 Create View DDL statements for the DB2 tables from which data
is being extracted.
No
File-AID/RDX won’t include DB2 DDL Create View statements in this extract file.
4-126
File-AID/RDX Reference
Alias : Specify whether the extract file should include all the DB2 DDL Create Alias
statements necessary for File-AID/RDX to also create Aliases when performing a load
using this extract file.
Yes
Extracts all DB2 Create Alias DDL statements for the DB2 objects from which data
is being extracted.
No
File-AID/RDX won’t include DB2 DDL Create Alias statements in this extract file.
Synonyms : Specify whether the extract file should include all the DB2 DDL Create
Synonym statements necessary for File-AID/RDX to also create synonyms when
performing a load using this extract file.
Yes
Extracts all DB2 Create Synonym DDL statements for the DB2 objects from which
data is being extracted.
No
File-AID/RDX won’t include DB2 DDL Create Synonym statements in this extract
file.
Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:
END : Returns to the “Extract Menu”. There are no operands associated with this
command.
Extract
4-127
Data Privacy Specification
The “Data Privacy Specification” screen shown in Figure 4-89 is displayed when you
select Option “8 - Data Privacy” from the “Extract Menu”.
Figure 4-89. Data Privacy Specification



File-AID/RDX ------------- Data Privacy Specification -------------------------
Command ===>

Select Disguise Method for
Disguise Extract File
DCF: Control File
DPR: Repository Name
Project Name
Extract File:
===> 3
( 1 = Use DCF; 2 = Use DPR; 3 = No)
===> 'TSOID01.FRSAMP.DISGUISE' 
===> 
===> 
Retain pre-disguise file ===> Y
( Y = Yes; N = No)
Create Audit Trail
Audit Trail prefix
( Y = Yes; N = No)
===> N
===>
Use this screen to specify data privacy information for this extract request.
Select Disguise Method for Extract File
Disguise Extract File : Specify whether File-AID/RDX should disguise the extracted data
as part of the extract batch job or not. When set to 1 (DCF) or 2 (DPR), all extracted
objects which have disguise criteria defined in the Disguise Control file (DCF) or in
the Dynamic Privacy Rules Project (DPR) will be disguised.
1
Use DCF. Disguise the extracted data using a disguise control file (DCF). This
option requires installation of Compuware’s File-AID/Data Solutions. 
Before submitting an extract request with the DCF data disguise option, you must
have defined the disguise criteria using Option 5, Data Disguise (see Chapter 7,
“Data Privacy”).
When returning to the Extract Menu, the DISGUISED indicator in front of the
extract file is displayed.
2
Use DPR. Disguise the extracted data using a Dynamic Privacy Rules Project (DPR).
This option requires installation of Compuware’s File-AID/Data Solutions and the
File-AID Data Privacy plugin of the Topaz Workbench.
Before submitting an extract request with the DPR data privacy option, you must
have defined the Dynamic Privacy Rules Project using File-AID Data Privacy.
When returning to the Extract Menu, the DISGUISED indicator in front of the
extract file is displayed.
Note:
3
Before submitting the job, be sure to specify a region size large enough
to run Java (REGION=0M is suggested, 200M is the minimum) in your
jobcard (see also “View JCL” on page 4-134).
No Disguise. The extracted data will not be disguised.
DCF: Control File : Specify the name of Disguise Control File that contains the disguise
criteria for this extract. Required for Disguise Selection option 1. Disguise Control
Files can be created in Option 5, Data Disguise (refer to “Allocate Disguise Control
File” on page 7-60). The disguise criteria is specified using Option 5, Data Disguise
(refer to “1 - Criteria” on page 7-8).
Hints
• Before you submit the disguise job, make sure that the Disguise Control File
includes the desired disguise criteria for the objects included in the extract
file.
• It is also recommended that the relationship information in both the extract
and Disguise Control File matches.
4-128
File-AID/RDX Reference
• Also, when using disguise rules with complex criteria, the object that you
used to define the criteria originally must be included (not excluded) in the
extract file or the disguise may not be successful.
• For related disguise rules, always define the criteria on the object that
contains all of the different unique values (including orphans) to be
extracted.
DPR: Repository Name : Specify the name of the Privacy Rules Repository to be used
with Disguise Selection option 2 for this extract.
Specify the full repository name (up to 128 characters). Or enter an asterisk (*) by
itself for a list of all repositories. Then select the desired repository from the list (see
“Privacy Repository List” on page 2-19).
This field is prefilled with your current profile’s value (see “DPR: Repository Name”
on page 2-18) or global default value (see “Option G—Global User Defaults”).
DPR: Project Name : Specify the name of the Dynamic Privacy Rules Project to be used
with Disguise Selection option 2 for this extract. Dynamic Privacy Rules are created
with the File-AID Data Privacy component of the Topaz Workbench. The Dynamic
Privacy Rules Project keeps track of how to apply the privacy rules to which extracted
data element. This option requires installation of Compuware’s File-AID/Data
Solutions and File-AID Data Privacy.
Specify the full project name (up to 128 characters) or a pattern ending with an
asterisk (*) for a list of matching projects. Asterisk (*) by itself lists all projects. Then
select the desired project from the list (see “Privacy Project List” on page 2-20).
This field is prefilled with your current profile’s value (see “DPR: Project Name” on
page 2-19).
Note:
The specified project must exist in the repository you specified in the “DPR:
Repository Name” field or the message 'Project not found' is displayed.
Retain pre-disguise file : Specify whether or not to retain the extract work file before
data is disguised. The extract work file is always in a masked format to prevent access
to the undisguised data.
Yes
Retain the extract work file before data is disguised.
No
Don’t retain the extract work file before data is disguised.
The extract and the disguise are run as separate job steps. By saving the undisguised
file you can rerun the disguise without having to rerun the extract. The disguise may
need to be rerun because it failed due to an error in the disguise criteria, insufficient
unique replacement values or because the disguise criteria did not produce the
expected results. To rerun a failed disguise, use Option 5.2, “DCF: Disguise Existing
Extract” on page 7-55.
The name assigned to the pre-disguise extract file will use the standard RDX routine
to generate a "temporary" name. The name will be the user PREFIX, the mid-level
qualifier from the Profile, the word "EXTRACT" and finally the current date and time
fields (i.e. D050128.T055709).
Create Audit Trail : Specify whether or not the File-AID/Data Solutions disguise process
should produce an audit trail report for each object whose data is subject to be
disguised.
Yes
Create audit trail reports using File-AID/Data Solutions audit trail exits. Note that
the File-AID/Data Solutions audit trail exits determine if a report is created and
what is reported.
No
Don’t create audit trail reports.
Audit Trail file prefix : Specify the prefix for the File-AID/Data Solutions audit trail
reports for this extract. Prefix plus USERID can be up to 14 positions, the remainder
of the dataset name will follow the above mentioned naming convention. If prefix is
Extract
4-129
blank, only the USERID will be used. Any value specified will be appended to the
USERID. Precede the prefix value with a single quote (‘) to use the value without the
USERID.
Supporting File Specification
The Supporting File Specification screen shown in Figure 4-90 is displayed when you
select Option “9 - Supporting Files” from the “Extract Menu”
Figure 4-90. Supporting File Specification
File-AID/RDX
Supporting File Specification

COMMAND ===>


Specify DB2 Object Record Layout Information:

Create layouts ===> Y
(Y = Yes;
N = No) 
Language
===> 1
(1 = COBOL, 2 = PLI)

File name
===> FRSAMP.MVS.LAYOUTS.NEW

Member
===> EXTRACT1
(Blank or pattern for member list) 
Disposition ===> NEW
(NEW, SHR)


Specify File-AID/MVS XREF for File-AID/RDX Extract File Information:
Create XREF ===> Y
(Y = Yes;
N = No) 
File name
===> FRSAMP.MVS.XREF.NEW

Member
===> EXTRACT1
(Blank or pattern for member list) 
Disposition ===> NEW
(NEW, SHR)

Use this screen to specify information about the record layout file to which File-AID/RDX
will copy the record layouts for all objects to be extracted.
Specify DB2 Object Record Layout File Information
Create layouts : Specify whether or not to create a COBOL or PL/I record layout file for
the extracted DB2 objects when File-AID/RDX performs the extract. Creating a record
layout allows you, for example, to download the extracted data with File-AID/EX at a
later time, or view and compare extract files with File-AID/MVS.
Note:
When you ask File-AID/RDX to create only a record layout (Create XREF =
NO) for MVS objects, the resulting layout is only for the complete extracted
record, not the fields within the record.
Language : Specify whether to create Cobol or PL/I record layouts.
1
Create a COBOL record layout.
2
Create a PL/I record layout.
File Name : Specify the name of the file to which the record layout will be saved.
Note:
When also creating an XREF for the extract file and your extract includes
MVS objects enter the existing source layout file name, the one used
when you defined the relationships. If you specify a different layout file,
be sure to copy the layout members from the source layout file into the
new record layout file before using the XREF file with File-AID/MVS or
File-AID/Data Solutions to access the extract file. The XREF expects all
layout members in the same layout file.
4-130
File-AID/RDX Reference
Member : If the file you specified in File Name is partitioned, you can enter a member
name. If you leave this field blank or specify a pattern, File-AID/RDX displays a
Member List pop-up window containing a list of members that match the specified
pattern. The only valid pattern character is an asterisk (*). You can create new
members by entering the name of the new member in the Member field.
Disposition : Specify the disposition of the record layout file. You can save to existing
files with a disposition of SHR. Specify a disposition of NEW to create a new PDS or
sequential file.
If you specify NEW in the Disposition field, you must specify the allocation
parameters in the “Create New File” screen (Figure 4-87 on page 4-121).
Specify File-AID/MVS XREF for File-AID/RDX Extract File Information
Create XREF : Specify whether or not to create a File-AID/MVS XREF (record layout cross
reference) file when File-AID/RDX performs the extract. File-AID/RDX will create the
record layout cross reference for the data elements (D records) of the extract file.
For DB2 objects, the generated XREF member will point to the detail field level
layout created with the Create Record Layout function.
For MVS objects, the generated XREF member will point to the detail field level
layout that will be left in-place in its source layout file, as specified during the
relationship definition.
Creating an XREF allows you, for example, to use File-AID/Data Solutions and
modify, or disguise, the data in the extract file before loading the extracted data to a
target subsystem.
Yes
Create the XREF. You must also Specify YES in the Creat layouts for DB2 objects
field to create an XREF even if the extract does not include any DB2 objects.
No
Don’t create an XREF (record layout cross reference).
Note:
When your extract includes MVS objects and you ask File-AID/RDX to
create XREF and layout information, File-AID/RDX will create the XREF,
but not a layout for the MVS data. The XREF points to the source layout
as specified when the relationship had been defined.
File Name : Specify the name of the file to which the record layout cross reference
(XREF) will be saved.
Member : The XREF file you specified in File Name must be partitioned. Enter a member
name. If you leave this field blank or specify a pattern, File-AID/RDX displays a
Member List pop-up window containing a list of members that match the specified
pattern. The only valid pattern character is an asterisk (*). You can create new
members by entering the name of the new member in the Member field.
Disposition : Specify the disposition of the file. You can save to existing files with a
disposition of SHR. Specify a disposition of NEW to create a new PDS.
If you specify NEW in the Disposition field, you must specify the allocation
parameters in the “Create New File” screen (Figure 4-87 on page 4-121).
Primary Commands
The following File-AID/RDX-specific primary command is valid on this screen:
END : Saves your input and returns to the “Extract File Specification Screen”. There are
no operands associated with this command.
Extract
4-131
Continue With Load
The “Continue With Load” screen shown in Figure 4-91 is displayed when you select
Option “10- Continue with Load” from the “Extract Menu”. It creates a batch job to
extract the data with an ESR (Execute Saved Request) step that submits the load portion
after the extract is successful.
Note:
The “Continue With Load” option is not available for interactive execution (see
also “MODE” on page 4-47).
Figure 4-91. Continue With Load
File-AID/RDX ------------COMMAND ===>
Continue With Load Menu
--------------------------
SITE Profile: RDXMENU 

Primary commands: menu-number, ALL

Line commands: S or / to create flow through selected options.


Extract File name ===> FRSAMP.EXTRACT

Description
===> DB2-FRSAMP.PART_TABLE


Current Values

_ 1 Load Object Specifications
SSID=DSN, Load Method=DB2 Load

_ 2 Source/Target Mapping
0 of 6 Objects are excluded

_ 3 Target Environment
Create: Tables=6 + DB TS, Files=0

_ 4 Existing Data Options

_ 5 Insert Processing Options

6 Save Load Request
Unavailable

_ 7 View JCL
Unavailable

_ 8 Submit JCL
Unavailable 
The Extract File name and Description fields are protected as it is the extract file of the
current extract request.
Refer to “Load Menu” on page 5-10 for a description of the “Continue With Load”
menu options.
Note:
The options to save the load request, view and submit the JCL are not
available as they are provided on the “Extract Menu”.
Primary Commands
Note:
The REFERENCE and REQUEST primary commands are not available in the
“Continue With Load” menu.
The following File-AID/RDX-specific primary commands are valid on this screen:
ALL : Selects all continue with load options for you to step through in sequence.
END : Saves your input, returns to the “Extract Menu” and sets the current value for
“Continue With Load” to Yes (see “10- Continue with Load” on page 4-46).
4-132
File-AID/RDX Reference
Save Extract Request
The Save Extract Request screen shown in Figure 4-92 is displayed when you select
Option “11- Save Extract Request”, from the “Extract Menu”.
Figure 4-92. Save Extract Request


File-AID/RDX
COMMAND ===>
---------------
Specify Extract
File name
Member
Description
Save Extract Request
Request File Information:
===>
===> 
===>
---------------------------




NOTE: Extract Request includes Relationship and Selection Criteria
CANCEL To Cancel Save Request
END to process and return


Use this screen to save the current extract request information.
Note:
Make sure to select Option “11- Save Extract Request”, from the “Extract Menu”
just before Option 13 in order to save the request as it will be submitted. If you
make changes to the extract request after saving the request, the changes will not
be saved in the request file, only in the temporary extract criteria.
Press Enter to process the file information. The saved request will also appear in your
Extract Reference List (see “Extract Reference List” on page 4-20).
The body of the “Save Extract Request” window consists of the following fields:
File Name : Specify the name of the file where you want to save the extract request. You
can save the request to existing files. Existing files must conform to the format
outlined for the extract request file in “File-AID/RDX Extract/Load/Delete Request
File” on page 4-144.
If you specify a new file, you must specify the following allocation parameters in the
“Create New File” screen (Figure 4-87 on page 4-121).
Note:
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
4-133
SAVE Confirmation
When saving an Extract or Load request File-AID/RDX checks to see if the member
already exists. If the member already exists, the “Save Confirmation window” (Figure 493) displays:
Figure 4-93. Save Confirmation window

File-AID/RDX -------------------- Save Confirmation --------------------
Command ===>
The Following member exists and will be replaced:
Request File . . . .: 'TSOID01.FRSAMP.EXTCRIT'
Member to be saved : MVSKEY








ENTER to confirm Save and replace existing member

END return to Save Request enter a different member name 

Press Enter to confirm overwriting the existing file or member name. Press End to cancel
the Save request and return to the “Save Extract Request” panel where you can enter
another file or member name.
4-134
File-AID/RDX Reference
View JCL
The ISPF/PDF Edit screen shown in Figure 4-94 is displayed when you select Option “12 View JCL”, from the “Extract Menu”.
Figure 4-94. ISPF/PDF EDIT Screen—File-AID/RDX-generated JCL

EDIT - File-AID/RDX Generated JCL
COLUMNS 001 072
Command ===>
SCROLL ===> CSR
You are now viewing the JCL that File-AID/RDX has generated to perform
the required function. Change this JCL as desired before submitting. 
******
000001
000002
000003
000004
000005
000006
000007
000008
000009
000010
000011
000012
000013
000014
000015
000016
000017
000018
***************************** TOP OF DATA ******************************
//TSOID01 JOB ('XXXXXXX.0XXX'),
//
'INSTALL FR 16.3',
//
MSGCLASS=X,NOTIFY=TSOID01,CLASS=A
//*
XFRJXTRT
//EXDRV
EXEC PGM=XFREXEC,REGION=8192K,MEMLIMIT=4G,
//
PARM=(FR,2,B)
//STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ160.CXVJLOAD
//
DD DISP=SHR,DSN=CPWR.MXVJ160.SXVJLOAD
//
DD DSN=DSNA10.SDSNEXIT,DISP=SHR
//
DD DSN=DSNA10.SDSNLOAD,DISP=SHR
//RDXMLIB DD DSN=CPWR.MXVJ160.SXVJMENU,DISP=SHR
//RDXEC
DD DSN=TSOID01.RDX.EXTCRIT.D130314.T155100,
//
DISP=SHR
//EXTRACT DD DSN=TSOID01.FDSAMP.EXTRPDS(CUSTOMER),

//
DISP=OLD

//EXTPARMS DD DSN=TSOID01.RDX.PARMS.D130314.T155100,

//
DISP=SHR

//* 
Use this screen to view or edit the extract JCL generated by File-AID/RDX. Use the
SUBMIT command to submit the extract request for execution. If you want to save this
JCL, use the ISPF/PDF CREATE or REPLACE command before you exit the panel. If you
did not save the extract request with Option “11- Save Extract Request”, File-AID/RDX
deletes the temporary extract criteria work file after extract execution.
Notes:
1. If your extract request includes disguising the extracted data, see also “Set
Incomplete Disguise Continuation Indicator” on page 7-57 to determine whether
you want to change the default disguise EXEC parameter.
2. You receive the informational message “I321 RDX CNTL PDSE's not deleted, ISPF
SUBMIT or CREATE command issued during VIEW of JCL” to remind you that some
extract work files were not deleted and to clean up the extract work files when you
don’t need them any longer.
3. When disguising the extract with File-AID Data Privacy defined Dynamic Privacy
Rules (DPR), specify a region size large enough to run Java (REGION=0M is suggested,
200M is the minimum) in your jobcard. See also “Disguise Extract File” on page
4-127, option 2, Use DPR.
4. The FARULES DD identifies the Privacy Rules Repository name and Dynamic Privacy
Rules Project ID. 
The FARULES DD may be allocated to a sequential file or a member of a PDS. The
record length must be fixed 80 bytes.
Override Data Privacy Environment Parameters
If you need to, you can override the Data Privacy Environment parameters listed in Table
4-6 (established with your site’s PARM module XVJOPDPR (refer to “Step 3.3. Specify
File-AID Data Privacy (Option 3)” in the File-AID Single Install Image Installation and
Extract
4-135
Configuration Guide).
Table 4-6.
Data Privacy Environment Parameter Overrides
Parameter in XVJOPDPR
DD statement
z/OS UNIX Path Name for Java Virtual Machine (JVM)
FAJPATH
Java (JVM) Options
FAJOPTS
File-AID Data Privacy IP address and execution port
FAIPADDR
Path Name for File-AID Rules Engine (FARE, formerly
Common Disguise Engine, or CDE)
FAEXPATH
To do so, insert any of these FAJPATH, FAJOPTS, FAIPADDR, and FAEXPATH DD
statements as needed. For example:
//FAIPADDR DD * 
127.372.322.101 :4180
/* 
//FAJPATH DD * 
/usr/lpp/java/J7.1_64.bld111513/
/*
It is also possible to specify more than one debug parameter inline. For example:
//FADEBUG DD *
Level=FINER

Filename=/u/userid/
/*
Override Execution Parameter in a Data Privacy Project
In order to override an execution parameter (public variable or translate table) in a Data
Privacy Project, add a DPRPARMS DD statement to your JCL. This DD can point to a file
or a PDS member containing the override values (maximum record length is 512 bytes).
The override values can also be specified inline. Specify override values in the following
way:
executionParm=overrideValue
The execution parameter must have been defined in the Topaz Workbench user interface
for the project.
Example:
Your DPR project ‘project1’ includes:
• 2 translate tables, ‘Title table’ and ‘Titles for HR dept’ (Figure 4-95)
– The source table for ‘Title table’ is file ‘ABC.TRANS’.
• 2 public variables, ‘scramvar’ and ‘altscram‘ (Figure 4-96 on page 4-136)
– The initial value for ‘scramvar’ is string ‘123abc’.
• 2 execution parameters, ‘Parameter1’ identifies the translate table ‘Title table’ and
‘Param2Variable’ identifies variable ‘scramvar’ (Figure 4-97 on page 4-137).
At execution time, however, you want to override the defined execution parameters for
translate table ‘Title table’ with the new translate table ‘ABC.NEWTRANS’ and the initial
value of variable ‘altscram‘ with the new string ‘789xyz’. The new translate table must
have the same characteristics as the original one.
To do so, insert the following DPRPARMS DD statement in the JCL (inline example):
4-136
File-AID/RDX Reference
//DPRPARMS DD * 
Parameter1=ABC. NEWTRANS
Param2Variable=789xyz
/*
Figure 4-95. Manage Translate Tables
Figure 4-96. Process Variables
Extract
4-137
Figure 4-97. Manage Execution Parameters
Execution Parameter List of Values
If the execution parameter variable type is either a String List or Numeric List, you can
also override the list of values.
Specify a list of values in the following way:
executionParm=LIST(X)=overrideValueXoverrideValueXoverrideValue
The X variable inside the =LIST( )= parentheses defines the delimiter for the list of values.
The delimiter can be any character. Connect each overridevalue with the defined delimiter.
For example, insert the following DPRPARMS DD statement in the JCL (inline example)
to override the values of the String List named STATE (* is the defined delimiter):
//DPRPARMS DD * 
STATE=LIST(*)=MI*OH*RI*CA*MO*IN
/*
Multiple Origins for a Data Privacy Rule
Normally, when a Data Privacy Rule is applied to a related field, one object1 in the
relationship thread is chosen as the “origin”. For every record in the origin, the Data
Privacy Rule is applied to the related field and the BEFORE and AFTER values are saved.
For every record in a “non-origin”, the Data Privacy Rule is not applied. Rather, the
appropriate AFTER value is retrieved from where it was saved. This guarantees
relationship integrity.
This methodology is efficient and sufficient in most scenarios, but there are some
scenarios where no single origin contains all of the values required by the non-origins.
When this occurs, it is possible to direct File-AID to use all objects that contain the
necessary fields referenced by the Data Privacy Rule as origins. This directive is specified
by adding to your JCL:
1. An object is a DB2 table, an MVS file, or an IMS segment.
4-138
File-AID/RDX Reference
//MULTISRC DD DUMMY
Note:
The use of multiple origins degrades job execution performance, so it is not
recommended as a default behavior.
Special Instructions for Oracle Translate Table
If your Data Privacy job uses Data Translation with an Oracle Translate Table and your
Data Privacy parameter module XVJOPDPR does not include the following JAVA options
(refer to “Step 3.3. Specify File-AID Data Privacy (Option 3)” in the File-AID Single Install
Image Installation and Configuration Guide), insert the following FAJOPTS DD statement:
//FAJOPTS DD * 
-verbose:sizes
-Dfile.encoding=UTF-8
-Dlog.encoding=IBM1047
If the JAVA options in the Data Privacy module XVJOPDPR include other site specific
JAVA options, also add them to the FAJOPTS DD statement before submitting the job.
Adding the above FAJOPTS DD statement will override the JAVA options in the Data
Privacy module XVJOPDPR and make it possible to run an Oracle translation while the
log will be generated in EBCDIC.
An indicator that you need to make this JCL change is when the Data Privacy job ended
with the following error:
Method execPrivacyRules failed (RC=8) at line nnn in file EXECDPR.C.
However, this general message is not conclusive. Your error log file should have
something like the following:
Throwable occurred: java.sql.SQLException: Internal - Unexpected value
at oracle.jdbc.driver.T4CTTIoauthenticate.processRPA(T4CTTIoauthenticate.java:516)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:295)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)
at oracle.jdbc.driver.T4CTTIoauthenticate.doOSESSKEY(T4CTTIoauthenticate.java:390)
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:356)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:531)
at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:221)
at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:503)
at java.sql.DriverManager.getConnection(DriverManager.java:322)
at java.sql.DriverManager.getConnection(DriverManager.java:358)












If you see the above, then you need to insert the FAJOPTS DD statement.
Redirect File-AID/Data Solutions Report (Data Disguise with DCF only)
When using a Disguise Control File (DCF) to disguise extracted data, you can choose to
redirect the disguise report output produced by File-AID/Data Solutions to FADSPRNT DD
by simply adding it to the JCL in the disguise step. The FADSPRNT DD can point at a file
or at SYSOUT. When it points at a file and multiple objects are being disguised, use
DISP=MOD.
Since the use of FADSPRNT splits the File-AID/Data Solutions report output away from
the File-AID/RDX report output, FADSPRNT and SYSPRINT must be looked at together to
get a complete picture of the job.
Control Card Cleanup
The last step, CLEANEXT, in the extract jobs deletes the File-AID/RDX EXTPARMS
parameter file. Whether step CLEANEXT is commented out or executed is determined by
the global job option “Delete in-stream data datasets at EOJ” (page 2-26). If the job
option is set to NO, File-AID/RDX EXTPARMS parameter files created in the extract jobs
Extract
4-139
will NOT be deleted. Keeping the datasets until all steps run successfully allows for the
restarting of the JCL at any step.
Periodically, you may want to manually delete the EXTPARMS parameter files that are no
longer needed for saved jobs to be resubmitted.
View REXX
The ISPF/PDF Edit screen shown in Figure 4-98 is displayed when you select Option 12,
from the “Extract Menu” and the Execute Extract online status has been set to ON with
the MODE primary command.
Figure 4-98. ISPF/PDF EDIT Screen—File-AID/RDX Generated REXX



VIEW - File-AID/RDX Generated REXX
COLUMNS 001 072
Command ===>
SCROLL ===> CSR
You are now viewiing the REXX that File-AID/RDX has generated to perform
the required function. 
******
000001
000002
000003
000004
000005
000006
000007
000008
000009
000010
000011
000012
000013
000014
000015
000016
***************************** Top of Data ******************************
/* REXX */

/* TRACE R */

MSG_STAT = MSG("OFF")

ADDRESS TSO

'FREE FI(DFSPARM)' 
'FREE FI(SYSOUT)' 
'FREE FI(RDXEC) ' 
'FREE FI(RDXMLIB) '
'FREE FI(EXTRACT) '
'FREE FI(X37MSG)' 
'FREE FI(PROGRESS)'
'FREE FI(REPORT) ' 
'FREE FI(RDXSQLCD)'
'FREE FI(SYSTERM) '
'FREE FI(SYSPRINT)'
'FREE FI(TPTPRINT)'
Use this screen to view or edit the extract REXX statements generated by File-AID/RDX. If
you want to save these Rexx statements, use the ISPF/PDF CREATE or REPLACE
command before exiting this panel. Otherwise, File-AID/RDX deletes this file after
extract execution.
Submit JCL
Select Option “13 - Submit JCL”, from the “Extract Menu” after you have completed
specifying all your extract options, selection criteria, and output files to submit your
extract request to perform the extract.
You will receive a confirmation message that your job has been submitted.
Execute Rexx
When the Execute Extract Interactively (online) status has been set to ON with the
MODE primary command, select Option 13, from the “Extract Menu” after you have
completed specifying all your extract options, selection criteria, and output files to
execute your extract request to perform the interactive extract.
You can then follow the extract execution online. Status messages inform you about the
progress. The extract is complete when you receive a completion message.
4-140
File-AID/RDX Reference
Interactive Extract Execution
When the Execute Extract Interactively (online) status has been set to ON with the
MODE primary command, and you selected Option 13 from the “Extract Menu” you can
follow the extract execution interactively. Extracted row count messages inform you
about the progress (see Figure 4-99 on page 4-140).
Note:
Press the ESC key to terminate the interactive extract. If you terminate the
execution before the completion message your extract file will not be loadable as
it is incomplete and lacking extract information and data. You also may need to
manually delete any working files created during the extract execution.
Figure 4-99. Interactive Extract Execution
------ Row 1 to 12 of 12 


Hit ATTN to terminate Load Processing


Load Object
Row Count Time

---------------------------------------------- --------- ---------
FRSAMP.ORDER_TABLE
3
11:24:51

FRSAMP.ORDER_LINE_TABLE
5
11:24:51

FRSAMP.PART_TABLE
5
11:24:51

FRSAMP.SUPPLIER_TABLE
7
11:24:51

FRSAMP.ORDER_TABLE
3
11:24:52

FRSAMP.CUSTOMER_TABLE
1
11:24:52

FRSAMP.ORDER_LINE_TABLE
3
11:24:52

FRSAMP.PART_TABLE
3
11:24:52

FRSAMP.SUPPLIER_TABLE
2
11:24:52

FRSAMP.ORDER_TABLE
1
11:24:53

FRSAMP.CUSTOMER_TABLE
1
11:24:53

FRSAMP.CONTACT_TABLE
1
11:24:53

******************************* Bottom of data ********************************



File-AID/RDX -------Option ===>
Online Load Processing Status
Interactive Extract Reports
The extract is complete when the extract reports display (see Figure 4-100). Use standard
scrolling commands to view the reports. Return to the “Extract Menu” with the END
command.
Extract
4-141
Figure 4-100. Interactive Extract Reports
Menu Utilities Compilers Help

-------------------------------------------------------------------------------
BROWSE
TSOID01.RDX.EXTRACT.OUTPUT
Line 00000021 Col 001 080 
Command ===>
Scroll ===> CSR 
1File-AID/RDX 16.3
Extract Progress Report
PAGE
1
DATE 2006-02-12
TIME
11.38.30

Extract File: TSOID01.FRSAMP.EXTRACT

Member:
EXCLD


Extract Object
Row Count Time

---------------------------------------------- --------- ---------
FRSAMP.ORDER_TABLE
33
11:43:17

FRSAMP.ORDER_LINE_TABLE
49
11:43:18

FRSAMP.PART_TABLE
28
11:43:19

FRSAMP.CUSTOMER_TABLE
15
11:43:19

1File-AID/RDX 4.0
Relationship Criteria Report



0Location:
LOCATION

0Relationships for object:
FRSAMP.ORDER_TABLE
Ext
0

Parent Object
Dependent Object 
4-142
File-AID/RDX Reference
Miscellaneous Extract Topics
This section provides information about the following topics:
•
•
•
•
•
•
•
•
“Extract JCL”
“DB2 Privileges”
“File-AID/RDX Extract/Load/Delete Request File”
“File-AID/RDX Extract File”
“File-AID/RDX Encryption Exit”
“Record Layout and File-AID/MVS XREF JCL”
“File-AID/RDX Record Layout File”
“File-AID/MVS XREF File”
Extract JCL
The extract JCL shown in Figure 4-101 performs the batch portion of the extract process
and generates the appropriate reports. The extract JCL can be coded and executed
separately in a batch job. In addition, File-AID/RDX can automatically generate the JCL
through the online extract screens.
Figure 4-101. Extract JCL
//EXDRV
EXEC PGM=XFREXEC,REGION=8192K,MEMLIMIT=4G,
//
PARM=(FR,2,B)
//STEPLIB DD DSN=Combined-File-AID/RDX-load-libraries,DISP=SHR
//
DD DSN=DB2-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID-message-library,DISP=SHR
//RDXEC
DD DSN=extract-criteria-file(member),DISP=SHR
//EXTRACT DD DSN=extract-to-file-name,DISP=SHR
//EXTPARMS DD DSN=extract-parms-file,DISP=SHR
//*
//DDxxx
DD DSN=file-name-of-MVS-object-xxx,DISP=(SHR)
//LAYxxx
DD DSN=layout-file-name-for-MVS-object-xxx,DISP=(SHR)
//XREFxxx DD DSN=XREF-file-name-for-MVS-object-xxx,DISP=(SHR)
//KEYxxxxx DD DSN=output key file-name,DISP=OLD
//SORTWK01 DD UNIT=SYSDA,
//
SPACE=(19069,(00003),,,ROUND),
//
DISP=(NEW,DELETE,DELETE)
//SORTWK02 DD UNIT=SYSDA,
//
SPACE=(19069,(00003),,,ROUND),
//
DISP=(NEW,DELETE,DELETE)
//SORTWK03 DD UNIT=SYSDA,
//
SPACE=(19069,(00003),,,ROUND),
//
DISP=(NEW,DELETE,DELETE)
//DFSPARM DD UNIT=SYSDA,

//
DCB=(RECFM=FB,LRECL=80,BLKSIZE=8000,DSORG=PS),
//
SPACE=(TRK,(1,1),RLSE),

//
DISP=(NEW,DELETE,DELETE)

//* 
//X37MSG
DD SYSOUT=(*)
//PROGRESS DD SYSOUT=(*)
//REPORT
DD SYSOUT=(*)
//RDXSQLCD DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//IXRPT
DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*)
//TPTPRINT DD SYSOUT=(*)
//SYSOUT
DD SYSOUT=(*)
//SORTLST DD SYSOUT=(*)
//IDCAMLST DD SYSOUT=(*)
//SYSUDUMP DD SYSOUT=(*)
//DPARMS
DD *
CYL
1
1
//* 
//CLEANEXT EXEC PGM=IDCAMS,COND=(4,LT),DYNAMNBR=2048
XFRJCLXT 
//SYSPRINT DD SYSOUT=*
//SYSIN
DD *
IDCAMS DELETE STATEMENTS FOLLOW
DELETE extract-parms-file,
SET MAXCC=0
SET LASTCC=0
//* 
//*
/*XFRJCLXT*/
Extract
4-143
XFREXEC is the File-AID/RDX program name.
The parameter information in the PARM field in the EXEC statement must have the
format as shown in Table 4-7:
Table 4-7.
EXEC Statement PARM Field—Extract Step
Parameter
Default
Value
Length
Description
Product
FR
2
File-AID/RDX
Option
2
1
File-AID/RDX option number.
Operating Mode
B
1
B : Batch
Extract from DB2 Image Copy
For an extract from DB2 Image Copy the program name is XFRIMAGE and requires that
the File-AID/RDX load library be authorized.
Note:
File-AID/RDX Release 16.03 does not support executing XFRIMAGE with JCL
parameters generated by prior releases of File-AID/RDX. It is recommended that
the JCL for Extract from DB2 Image Copy be generated in File-AID/RDX Release
16.03.
Figure 4-102. Extract JCL XFRIMAGE Parm statement
//EXDRV
//
EXEC PGM=XFRIMAGE,REGION=8192K,MEMLIMIT=4G,
PARM=(FR,2,B)
The parameter information in the PARM field in the EXEC statement must have the
following format:
Table 4-8.
EXEC Statement PARM Field—Extract Step for Image Copy
Parameter
Default
Value
Length
Description
Product
FR
2
File-AID/RDX
Option
2
1
File-AID/RDX option number.
Operating Mode
B
1
B : Batch
DD statements
The following DD statements are required for extract:
Table 4-9.
DD Statements—Extract
DD Statement
STEPLIB
RDXMLIB
RDXEC
EXTRACT
EXTPARMS
DDxxx
LAYxxx
KEYxxxxx
XREFxxx
SYSOUT
RDXSQLCD
SYSTERM
SYSPRINT
Description
File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD) and DB2 load libraries
Library containing File-AID/RDX messages.
Library containing the File-AID/RDX extract criteria (only required if extract criteria is
being applied).
File to which extracted data is written.
File containing the extract parameters (see “EXTPARMS File” on page 4-144).
File name of the MVS object xxx; only applicable when extracting MVS objects.
File name of layout file for the MVS object xxx; when extracting MVS objects.
File name of the defined Output Key file; when extracting KEY relationships.
File name of XREF file for the MVS object xxx; when extracting MVS objects.
Output class for SORT utility.
Output class for detailed SQL error information from DB2.
Output class for runtime errors.
Standard output stream.
4-144
File-AID/RDX Reference
Table 4-9.
DD Statements—Extract (Continued)
DD Statement
SYSIN
SORTWK01
SORTWK02
SORTWK03
X37MSG
REPORT
PROGRESS
IXRPT
IDCAMLST
DPARMS
Description
Control card used by File-AID/RDX to sort data during the extract process.
Work files required by the SORT utility.
Output class for error messages and reports.
Parameters for temporary extract files for XML and MVS objects.
Space allocation parameters for temporary extract files.
Note:
File-AID/RDX will dynamically reallocate temporary work files, key tree
and chase key files only when running extracts using 64 bit memory
(above the bar) processing support. See also parameter variable
“EXTADDR” in the File-AID Single Install Image Installation and
Configuration Guide.
EXTPARMS File
The EXTPARMS file contains the relevant parameters to execute File-AID/RDX programs.
Each program function, Extract, Load, Disguise, etc. generates different parameters that
are necessary for that function to run correctly. Do NOT change any of the parameters in
the EXTPARMS file, unless instructed to do so by Compuware customer support for
diagnostic purposes. The TEST mode indicator (N or Y) is used for debugging purposes.
Return Codes
An execution return code (RC) appears in the output listing. For return codes other than
0, an error code and message indicating the specific problem also appear in the listing. In
general, the return codes can be summarized as follows:
Return Code
Description
0
Job ran to completion.
4
Job ran to completion, warnings issued.
8
Job completed with error.
16
Severe error, job aborted.
DB2 Privileges
During extract, the SELECT privilege is required for all tables included in the extract. The
plan being used to execute File-AID/RDX requires the SELECT privilege for the DB2
system catalog tables.
You must have one of the following authorization privileges to extract data from DB2
Image Copy:
• RECOVERDB privilege for the database
• DBADM, or DBCTRL authority for the database
• SYSCTRL or SYSADM authority
File-AID/RDX Extract/Load/Delete Request File
The Extract/Load/Delete Request file contains records that reflect the values you specified
in the during the interactive phase of the extract, load, or delete process. The
Extract/Load/Delete Request file evolved from the Extract Criteria file from earlier
versions of File-AID/RDX.
Figure 4-103 on page 4-146 shows a sample request file. Note that in the figure the
reserved spaces for DB2 creator ID and table names (up to 128 spaces for each) have been
Extract
4-145
reduced to fit into this figure. When viewing the request file online, use the RIGHT and
LEFT scroll commands to view the DB2 object names at the end of the records.
The request file has the following characteristics:
File organization
Either partitioned or sequential (DSORG=PO or DSORG=PS)
Record format
Variable-blocked (RECFM=VB)
Logical record length
Maximum LRECL determined by File-AID/RDX (default is 1004)
Note:
Pre-Release 4.3 extract/load request files have fixed or fixed-blocked (RECFM=F
or RECFM=FB) record format (see also “Save Extract Request” on page 4-132).
The first two bytes of each record contains either blanks or “--.” Records with blanks in
positions 1 and 2 are processed by SPUFI. Records that start with the characters “--” are
considered comments by SPUFI and are, therefore, ignored.
The third and fourth bytes of each record contain the record’s type.
File-AID/RDX Reference
--00FILE-AID/RDXVERSION 10 RELEASE 00 MOD 00 SUB 26
EP
--401 NN
--281
TSOID01.FRSAMP.EXTRACT
OLD
-
--291SYSDA
TRK0010005000VB 027994027998
--282
TSOID01.FRSAMP.EXTCRIT2
PCUST
NOLD
-
--27DESCRIPTION: DB2-FRSAMP.ORDER_TABLE
--292SYSDA
TRK0004004010FB 000080000000
--286
TSOID01.FRSAMP.RELATION
OLD
-
--296
CYL
--287
TSOID01.RDX.PROFILE
OLD
-
--297
CYL
--28B
TSOID01.FRSAMP.DISGUISE
OLD
-
--29B
CYL
--56DRIVING:
LOCK =N D701DD701CW01
FRSAMP
ORDER_TABLE
--14
C=*
M=*
N=*
X=N P=NONE
I=Y
001/001
--57MODEL:
D801DD801CW01
FRSAMP
ORDER_TABLE
--70 DISG=3 RETAIN=Y AUDIT=N PREFIX=KFL
8
--56RELATED:
LOCK =N D701DD701CW01
FRSAMP
CUSTOMER_TABLE
--15
C=*
M=*
N=*
X=N P=NONE
U=N I=Y
001/001
--56RELATED:
LOCK =N D701DD701CW01
FRSAMP
CONTACT_TABLE
--15
C=*
M=*
N=*
X=Y4 P=NONE
U=N I=Y
001/001
--56RELATED:
LOCK =N D701DD701CW01
FRSAMP
ORDER_LINE_TABLE
--15
C=*
M=*
N=*
X=N P=NONE
U=N I=Y
001/001
--56RELATED:
LOCK =N D701DD701CW01
FRSAMP
PART_TABLE
--15
C=*
M=*
N=*
X=N P=NONE
U=N I=Y
001/001
--56RELATED:
LOCK =N D701DD701CW01
FRSAMP
SUPPLIER_TABLE
--15
C=*
M=*
N=*
X=Y4 P=NONE
U=N I=Y
001/001
--06CHASE ALL RELS: Y
--07DPSI=YYNN C=*
M=*
MAX=Q UR=Y IMAGE=N F2
V=N A=N S=N COMPRESS=N KT_EMEM=E CK_EMEM=E KT_DEGR=9
--52P D
0
D701CW01
FRSAMP
CUSTOMER_TABLE
--53D7017100
--52D D
0
D701CW01
FRSAMP
ORDER_TABLE
--53D7017100
--13DPSI=-YN- C=*
M=*
D=*
X=N E=NN A
--16MISCDB2:2005-07-14 10.11.36
TSOID01
--50SOURCE COLUMN=CUSTOMER_NUMBER
TYPE=CHARACTER LENGTH= 00006
--51OFFSET= 00000SUB1=00000SUB2=00000SUB3=00000NOSUB=00000PREC=00000SCALE=00000
--50TARGET COLUMN=CUST_NUM
TYPE=CHARACTER LENGTH= 00006
--51OFFSET= 00000SUB1=00000SUB2=00000SUB3=00000NOSUB=00000PREC=00000SCALE=00000
--52P D
1
D701CW01
FRSAMP
CUSTOMER_TABLE
--53D7017100
--52D D
1
D701CW01
FRSAMP
CONTACT_TABLE
--53D7017100
--13DPSI=---N C=*
M=*
D=*
X=N E=
RCONTCUST
--16MISCDB2:2005-07-08-09.39.50.880402
2005-07-08-09.39.50.880402
--50SOURCE COLUMN=CUSTOMER_NUMBER
TYPE=CHARACTER LENGTH= 00006
--51OFFSET= 00000SUB1=00000SUB2=00000SUB3=00000NOSUB=00000PREC=00000SCALE=00000
--50TARGET COLUMN=CUSTOMER_NUMBER
TYPE=CHARACTER LENGTH= 00006
--51OFFSET= 00000SUB1=00000SUB2=00000SUB3=00000NOSUB=00000PREC=00000SCALE=00000
--52P D
2
D701CW01
FRSAMP
CUSTOMER_TABLE
--53D7017100
--52D I
2
IX.FISAMP.DBDLIB
PCUST
--13DPSI=YYNN C=*
M=*
D=*
X=N E=
A
--59C TSOID01.FRSAMP.CONDAR
P0000001
--16MISCDB2:2005-07-14 10.13.52
TSOID01
4-146
Figure 4-103. Sample Extract/Load Request File
FRSAMP
FRSAMP
FRSAMP

Extract
4-147
A request file could contain the following different record types as follows:
Record Type
Description
00
This record type indicates the version, release, modification level, subrelease of FileAID/RDX that created the file. It also indicates the request type: E=extract, L=load,
B=both extract and load, or D=delete, whether it is a P=permanent (saved) or
T=temporary request, and Y flags the request as Nonexecutable.
blank
This record type contains the DB2 SELECT statement(s) generated by the “DB2
Object Selection Criteria” screen. This record type has no record-type number
associated with it.
40n
This record type provides information whether the request includes an Input
(external) Key file and/or summary file, creates a record layout and/or XREF file,
which layout language is to be used. It also includes the CCSID of the terminal saving
request, and whether to use DB2 parallelism. The third digit n specifies the file type.
See type 28 for a list of the file types.
28n
This record type specifies file name and disposition information for the different files
in the current request. The third digit n specifies the file type:
n
1 = Extract file
2 = Request file
3 = Extract summary file
4 = Record layout file
5 = XREF file
6 = Relationship file
7 = Profile file
8 = Input (External) Key file
B = Disguise Control file (DCF)
27
This record type contains the request description (50 bytes).
29n
This record type specifies file allocation information for the corresponding type 28
files in the current request. The third digit n specifies the file type. See type 28 for a
list of the file types.
56
56 DRIVING: This record type identifies the driving object type (D=DB2, M=MVS),
and object name of the driving object at the end of the record to accomodate long
object names. For DB2 objects it also includes the location and creator ID, each
providing space for the maximum length. In addition, the type 56 record contains
the value specified in the Lock Table field on the “Extract Scope - Object View”
screen, with FUNCTION LOCK enabled (see also “L (Lock Table)” on page 4-58 and
“FUNCTION LOCK” on page 4-61) and the DB2 subsystem ID.
54
This record type is only included if record type 56, 52P or 52D is an MVS object. It
follows each MVS 56, 52P or 52D record to identify the object’s layout type
(S=Single, X=XREF), layout file name, member name, and IO exit name.
54A
This record type is a continuation record for record type 54. It identifies the 01 level
record name.
55
This record type is only included if the preceding record type 54 is an XREF type
(54X). It follows each 54X or 54A record to identify the object’s XREF file name, and
member name.
44
This record type identifies the location, subsystem, creator, and table name of the
base table associated with the view you specified as the driving table. This record
type occurs only when you specify a view as the driving table. When the 44 record
type occurs, it follows the 56 Driving: record type and precedes the 56 Related:
record type.
18
This record type identifies the type and name of the Input (external) Key file specified
as selection input to the driving object. Valid types are Standard and Delimited.
For delimited key files type 18 record includes the delimiter options as specified
during the selection criteria specification: 1 or 2 for single (1) or double (2) quotation
marks, the column delimiter (, is default), Y or N for quotes on character data, and
Y or N for quotes on numeric data. See also “Input Key File Specification” on page
4-89.
4-148
File-AID/RDX Reference
Record Type
14
Description
DB2 Driving object only. This record type contains
•
•
•
•
C= cycle limit for the object;
M= maximum number of records to extract from this object;
N= select every n th record from this object;
X= object excluded status:
N object not excluded;
Y1 object excluded by user;
Y2 object excluded by line command "A" (All);
Y3 object excluded by object not found;
Y4 object excluded by scope;
• P= Passthru status:
ALL extract all records (line command "A");
PASSTHRU don’t extract records (line command "P");
NONE extract related records as applicable;
• I= satisfy AR/RI indicator Y or N
• nnn/nnn Set number of Total Set number;
57
57 MODEL: This record type identifies the DB2 object that the driving object used
for its relationships even though no relationships were defined for the DB2 driving
object.
70
Identifies the data disguise information for this extract request.
•
•
•
•
DISG=disguise extract option 1 (DCF), 2 (DPR) or 3 (no)
RETAIN= retain pre-disguise extract file Yes or No
AUDIT= create data disguise audit trail files Yes or No
PREFIX= identifies the prefix for the data disguise audit trail files
45
Identifies the File-AID Data Privacy Dynamic Privacy Rules Project name and ID as well
as the Privacy Rules Repository name for this extract request.
17
This record type contains the part of the SELECT statement generated by the key file
selection input to the driving object. It contains the DB2 column or MVS field name
and the location and type of the selection value in the key file. For delimited files, the
INDSN parameter specifies the field number, for standard files, it specifies the starting
position, length, and type.
56
56RELATED: This record type identifies the object type (D=DB2, M=MVS), and
object name of a related object at the end of the record to accomodate long object
names. For DB2 objects it also includes the location and creator ID, each providing
space for the maximum length. In addition, the type 56 record contains the value
specified in the Lock Table field on the “Extract Scope - Object View” screen, with
FUNCTION LOCK enabled (see also “L (Lock Table)” on page 4-58 and “FUNCTION
LOCK” on page 4-61) and the DB2 subsystem ID. A type 56 Related: record exists for
every related object included in the extract.
Extract
4-149
Record Type
Description
58
58Clone: This record type identifies the cloned objects. There can be many 58 record
types listed per request. They list the original and new names. The type of clone
change is identified with a five digit code XYnnn, where:
X is the major type:
G = global parameter 
U = object identification
S = SSID
L = location
Y is the minor type:
D = DSN change
N = object name
L = layout
X = XREF
I = IMS and Output key file
nnn only applies to major/minor type GD 
000 = Extract file
001 = Extract request file
002 = Extract summary file
003 = Extract Record layout file
004 = Extract XREF file
005 = Relationship file
006 = Profile file
007 = Input (External) Key file
008 = Disguised Extract file
009 = Disguise Criteria file
010 = Disguise Control file (DCF)
011 = Business Rules file
15
DB2 Non-Driving objects. This record type contains
•
•
•
•
•
•
•
•
C= cycle limit for the object;
M= maximum number of records to extract from this object;
N= select every n th record from this object;
X= object excluded status:
N object not excluded;
Y1 object excluded by user;
Y2 object excluded by line command "A" (All);
Y3 object excluded by object not found;
Y4 object excluded by scope;
P= Passthru status:
ALL extract all records (line command "A");
PASSTHRU don’t extract records (line command "P");
NONE extract related records as applicable;
U= unrelated object Y or N
I= satisfy AR/RI indicator Y or N
nnn/nnn Set number out of Total Sets
4-150
File-AID/RDX Reference
Record Type
07
Description
This record type contains global navigation and sampling controls as well as other
extract options.
• DPSI= The status Y, N, or - (not relevant) is given for the global
Navigation controls DPSI (Direct Path, Parent Path, Sibling Path, and
Indirect Path). Direct Path status can also be C for All Children only
and P for Plus (see also “Direct” on page 2-9).
• C= global cycle limit;
• M= maximum number of records to extract for entire execution;
• MAX= Q (Quiesce) or S (Stop);
• UR= uncommitted read (Y or N)
• IMAGE= image copy (Y or N)
• V= capture View DDL (Y or N)
• F= DB2 Format (1=Unicode, 2=Conversion to EBCDIC, default)
• A= capture Alias DDL (Y or N)
• S= capture Synonym DDL (Y or N)
• COMPRESS= compress extract file (C, V or N)
• KT_EMEM= key tree in 64 bit memory (E or blank)
• CK_EMEM= chase keys in 64 bit memory (E or blank)
• KT_DEGR= key tree usage degree n (1-9)
09
This record type contains Temporal Table Business or System Time information .
•
•
•
•
•
•
B or S Business Time or System Time
D Dual (Bi-temporal)
1, 2, or 3 Time period: AS OF (1), FROM (2), or BETWEEN (3)
Y active or N inactive
Date/Timestamp 1
Date/Timestamp 2
A group of record types 52P or 11, 10, 52D or 12, 13, 16, 50S or 21, 50T or 22, 51, 53, 54,
30, 31, and 32 will be present for each relationship being processed, dependent also on
the respective object type.
Record Type
Description
52P
This record type contains information about the source object that is related to the
object described by the type 52D record immediately following this type 52P record.
The type 52P record identifies the source object’s object type (D=DB2, M=MVS), FileAID/RDX generated unique object sequence number, and fully qualified name at the
end of the record to accommodate long object names. If the driving object is a DB2
object, the creator ID of the relationship definition used (model creator ID) is also
included.
53
This record type exists only if record type 52P or 52D is a DB2 object. It follows each
DB2 52P or 52D record to identify the DB2 object’s subsystem, DBMS version,
release, modification level, and delimiter identifier.
52D
This record type contains information about the target object that is related to the
object described by the type 52P record immediately preceding this type 52D
record. The type 52D record identifies the target object’s object type (D=DB2, I=KEY,
M=MVS), File-AID/RDX generated unique object sequence number, and fully
qualified name at the end of the record to accommodate long object names.
Extract
Record Type
13
4-151
Description
This record type contains the individual navigation and sampling controls for each
relationship as well as other extract options.
• DPSI= The status Y, N, or - (not relevant) is given for the Navigation
controls DPSI (Direct Path, Parent Path, Sibling Path, and Indirect
Path) for each relationship.
• C= cycle limit for the relationship;
• M= maximum number of records to extract for this relationship;
• D= select n dependents from this parent;
• X= relationship excluded status:
N relationship not excluded;
Y1 relationship excluded by user;
Y2 relationship excluded by line command "A" (All);
Y3 relationship excluded by object not found;
Y4 relationship excluded by scope;
• E=YY check extract validation status:
Y_ (first Y) possible RI violation;
_Y (second Y) ignore parent missing;
• A or R identifies relationship type:
A application relationship (AR);
R DB2 RI;
• The remaining characters identify either the RELNAME (8 bytes) if the
relationship is DB2 RI, or the relationship description for AR.
59C
This record type identifies a conditional application relationship (AR-C) and
includes the name of the conditional AR Criteria dataset and parent criteria member
name (Pnnnnnnn).
16
This record type contains the relationship’s creation and last modified time, date, and
user ID.
A group of record types 50Source and 50Target (old 21 and 22, or 30 to 32) will be present
for each pair of source and target columns in the relationship.
Record Type
Description
50
Source column. This record type contains information about the source object
column or field that participates in a column/field relationship with the target object
column/field described by the type 50Target column immediately following the
type 51 record for the source column/field. The type 50Source column record
identifies the source object’s column/field name, data type, and length.
51
This record type is a continuation record for all type 50 records. The type 51 record
identifies the column/field offset, values for subscripts 1, 2, and 3, the total number
of subscripts (0, 1, 2, or 3), precision, and scale defined for the relationship.
50
Target column. This record type contains information about the target object
column or field that participates in a column/field relationship with the source object
column/field described by the type 50Source column immediately preceding the
type 51 record for the source column/field. The type 50Target column record
identifies the target object’s column/field name, data type, and length. It is always
followed by a 51 record type to specify the column/field values for offset and
subscripts.
31
This record type contains the relationship description for this KEY relationship.
32
This record type contains the name of the extract Output Key File for this KEY
relationship. It also includes the dataset name containing the JCL for the File-AID for
IMS extract if it is to be executed as a step following the File-AID/RDX extract.
33
This record type contains the Output Key File dataset details.
4-152
File-AID/RDX Reference
Load/Delete Request Record Types
A request file could also contain these different load or delete request record types:
Record Type
Description
60n
This record type specifies the extract file type for the load in the current request. The
third digit n specifies the file type:
n
1 = Extract file
2 = Extract summary file (tape control file)
3 = Request file
4 = Discard file
61
This record type contains the following global load parameters: 
DB2 load option S=SQL Insert, D=DB2 load utility;
Automatic Space Calculation (MVS only);
Commit interval:
Discard options;
DB2 Lock and Log options;
Image copy;
Repair
Auto create only
62
This record type contains the Target Object Names.
63
This record type contains the source to target Column Mapping information.
64
This record type contains the index auto create information.
65
This record type contains the index detail information.
66
This record type contains the discard file information.
67
This record type contains the partitioned index limitkey value information.
68
This record type contains the DB2 Alias, Synonyms, and View information.
69
This record type contains the DB2 Target Database information.
70
This record type contains the DB2 Target Tablespace information (obsolete, replaced
with record type 73).
71
This record type contains the DSATT information for MVS objects.
72
This record type contains the Index detail specifications information for MVS objects.
73
This record type contains the DB2 Target Tablespace information.
Obsolete Record Types
An extract criteria file saved with an earlier File-AID/RDX Release than 4.0 could contain
the following record types. When processed with File-AID/RDX Release 16.03 or later,
these record types will be replaced by their corresponding Release 16.03 record types.
Record Type
Description
01
This record type contains the value specified in the Maximum rows to select from
Driving object field on the Selection Criteria Specification screen. For multiple
selection criteria sets, the set number is located on the right, for example 001/003
(set# out of total sets).
02
This record type contains the request description.
03
This record type contains the value specified in the Maximum rows from all tables
field on the “Extract Scope Screen” screen.
08
The Max Cycles record type corresponds to the values specified in the Cycle Control
window. It lists the number of allowed extract cycles and whether orphan records are
acceptable (Get Parents of Orphans:N) or (Get Parents of Orphans:Y).
02
This record type contains the value specified in the Select every nth row from
driving table field on the Selection Criteria screen. This record type exists only in
extract criteria files created using File-AID/RDX version 1.1 and earlier and will be
replaced by record type 14 when saving the extract criteria with a current release of
File-AID/RDX.
Extract
4-153
Record Type
Description
04
This record type exists only in extract criteria files created using File-AID/RDX version
1.6 and earlier. When saving the selection criteria with File-AID/RDX version 2.0 and
later it will be replaced with type 56 record.
This record type identifies the location, subsystem, creator, and table name
associated with the driving table. In addition, the type 04 record contains the value
specified in the Lock Table field on the Selection Criteria Specification screen.
If you specified a view as the driving table, this record type identifies the location,
subsystem, creator, and view name associated with the view. Record type 44
identifies the location, subsystem, creator, and the view’s base table name.
05
This record type exists only in extract criteria files created using File-AID/RDX version
1.6 and earlier. When saving the selection criteria with File-AID/RDX version 2.0 and
later it will be replaced with type 56 record.
This record type identifies the location, subsystem, creator, and table name
associated with a related table. In addition, the type 05 record contains the value
specified in the Lock Table field on the Selection Criteria Specification screen. A type
05 record exists for every related table included in the extract.
06
This record type corresponds to the value specified in the Display all relationships
field on the Extract Specification screen in File-AID/RDX versions prior to 3.0.
11
This record type exists only in extract criteria files created using File-AID/RDX version
1.6 and earlier. When saving the extract criteria with File-AID/RDX version 2.0 and
later it will be replaced with type 52P and 53 records.
This record type contains information about the source table that is related to the
table described by the type 10 or 12 record immediately following this type 11
record. The type 11 record identifies the source table’s location; subsystem; creator;
table name; and DBMS version, release, and modification level.
10
This record type exists only in extract criteria files created using File-AID/RDX version
1.6 and earlier. When saving the extract criteria with the File-AID/RDX version 2.0
and later it will be replaced with type 52D records.
This record type identifies the target IMS database (DBDLIB) and the target member
that is related to the table described by the type 11 record immediately preceding
this type 10 record.
12
This record type exists only in extract criteria files created using File-AID/RDX version
1.6 and earlier. When saving the extract criteria with File-AID/RDX version 2.0 and
later it will be replaced with type 52D and 53 records.
21
This record type exists only in extract criteria files created using File-AID/RDX version
1.6 and earlier. When saving the extract criteria with File-AID/RDX version 2.0 and
later it will be replaced with type 50Source Column records.
This record type contains information about the source table column that
participates in a column relationship with the target table column described by the
type 22 record immediately following this type 21 record. The type 21 record
identifies the source table column’s name, data type, length, and offset, if any.
22
This record type exists only in extract criteria files created using File-AID/RDX version
1.6 and earlier. When saving the extract criteria with File-AID/RDX version 2.0 and
later it will be replaced with type 50Target Column records.
This record type contains information about the target table column that participates
in a column relationship with the source table column described by the type 21
record immediately preceding this type 22 record. The type 22 record identifies the
target table column’s name, data type, length, and offset, if any.
30
This record type exists only in extract criteria files created using File-AID/RDX version
1.6 and earlier. When saving the extract criteria with File-AID/RDX version 2.0 and
later it will be replaced with type 50Target Column records.
This record type contains information about the IMS target root segment that
participates in a column relationship with the source table column described by the
type 21 record immediately preceding this type 30 record. The type 30 record
identifies the IMS target root segment’s name, data type, length, and offset, if any.
4-154
File-AID/RDX Reference
File-AID/RDX Extract File
During the extract process, File-AID/RDX writes all extracted data to the extract file. This
is the file that File-AID/RDX uses in the load process to load all or only selected data.
In order to increase data security the File-AID/RDX extract file no longer includes DDL
statements in readable form. The DB2 source environment information is now captured
in a masked format.
The extract file has the following characteristics:
File organization : Partitioned (DSORG=PO) or sequential (DSORG=PS)
Record format : Variable-blocked (RECFM=VB)
Logical record length : Maximum LRECL determined by File-AID/RDX (default = 27994)
Note:
File-AID/RDX will dynamically reallocate a sequential extract file to adjust to
the needed space. Dynamic reallocation is only available for sequential files
(DSORG=PS).
The first four bytes at the beginning of each record indicate the record’s type and the
corresponding header record.
After a successful extract is performed, the extract file contains the following types of
records:
•
•
•
•
•
product record;
header record;
DB2 create records;
MVS file create records;
map records;
•
•
•
•
•
relationship records;
data records;
DB2 XML/LOB data records;
order records; and
trailer records.
Product Record — 0
The product record indicates the release of File-AID/RDX used to create the file. This is
always the first record in the file. It also includes the DBMS type and version, DB2 image
copy, sort, and compress indicators (C = compress all data, V = compress only DB2
variable column data, or blank = no compression), date format, data status (E = Encrypted
(Masked), D = Disguised), as well as the Autocreate disabled?, D record supplement
indicators, and DB2 extract format Unicode or Conversion. The format of the product
record is shown in Figure 4-104.
Extract
4-155
Figure 4-104. Product Record Layout
01

05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
PRODUCT-RECORD.
RCD-TYPE
PIC
RCD-TYPE-NO PIC
PROD-LIT
PIC
VERSION
PIC
PERIOD1
PIC
RELEASE
PIC
PERIOD2
PIC
MOD
PIC
PERIOD3
PIC
SUBRELEASE
PIC
FILLER
PIC
TIMESTAMP
PIC
DEC_IND
PIC
FILLER
PIC
DBMS-TYPE
PIC
DBMS-VERSION PIC
FILLER
PIC
IMAGE-COPY
PIC
SORT_IND
PIC
COMPRESS-IND PIC
DATE_FORMAT PIC
DATA_STATUS PIC
AUTOC_DISABL PIC
D_REC_SUPPLM PIC
DB2_FORMAT
PIC
X(1) VALUE '0'.
X(3) VALUE '000'.
X(13) VALUE 'File-AID/RDX'.
X(2) VALUE '04'.
X(1) VALUE '.'.
X(2) VALUE '07'.
X(1) VALUE '.'.
X(2) VALUE '00'.
X(1) VALUE '.'.
X(2) VALUE '00'.
X(1).
X(26).
X(1).
X(1).
X(8).
X(8).
X(1).
X(1) VALUE_’Y’_or’N’
X(1) VALUE_’Y’_or’N’
X(1) VALUE_’C’ or’V’
X(4)_VALUE_’ISO’,‘USA’,’JIS’,’LOC’,’EUR’, or ‘ISOM’
X(1) VALUE_’E’ or’D’
X(1) VALUE_’Y’
X(1) VALUE_’Y’_or’N’
X(1) VALUE_’1’_or’2’
Header Record — H
A header record will be present for each object included in the extract process. The
format of the header record is shown in Figure 4-105.
Figure 4-105. Header Record Layout
01
HEADER-RECORD.
RCD-TYPE
RCD-TYPE-NO
SUBSYS
OBJECT_TYP
OBJECT_NAME
10 LOCATION
10 CREATOR
10 TBNAME
10 FILLER
05 RI-DEP-IND
05 FILLER
05 BPOOL
05 FILLER
05 SUPPL_SW
05 CCSID
05 OBJECT_NAME_LONG
10 LOCATION
10 CREATOR
10 TBNAME
05 ORIG_OBJ_NAME
10 LOCATION
10 CREATOR
10 TBNAME
05
05
05
05
05
PIC X(1) VALUE 'H'.
PIC X(3) VALUE 'nnn'.
PIC X(4).
PIC X(1).
PIC X(52).
PIC X(16).
PIC X(8).
PIC X(18).
PIC X(10).
PIC X(1).
PIC X(1).
PIC X(9).
PIC X(2).
PIC X(1)
PIC X(5)
PIC X(272).
PIC X(16).
PIC X(128).
PIC X(128).
PIC X(272).
PIC X(16).
PIC X(128).
PIC X(128).
The following is an explanation of the fields contained in the header layout:
RCD-TYPE : A value of ’H’ will be present in this field. The value ’H’ indicates that this is
a header record.
RCD-TYPE-NO : A three-digit alphanumeric ID that identifies the record in the file. This
field is referenced by create records and data records that contain the same threedigit alphanumeric ID in the RCD-TYPE-NO field.
SUBSYS : The DB2 subsystem on which the table name identified in the CREATOR and
TBNAME field exists. Blank for MVS objects.
4-156
File-AID/RDX Reference
OBJECT_TYPE : Identifies the object type: D = DB2, M = MVS.
OBJECT_NAME : Identifies the object name. If object type is M the full MVS file name is
listed. If object type is D the location, creator and table names are listed instead:
LOCATION
The location at which the DB2 table name identified in the CREATOR and
TBNAME fields exists.
CREATOR
The authorization ID of the owner of the table in the TBNAME field (blank,
if DB2 long object name).
TBNAME
The name of the table to which this header record corresponds (blank, if
DB2 long object name).
RI-DEP-IND : A value of 'Y' indicates that the DB2 table identified by the CREATOR and
TBNAME fields is a dependent in a DB2 RI relationship.
BPOOL : Buffer pool where creator.tbname resides. Only used when table contains
either LVCHAR or LVGRPH columns.
SUPPL_SW : If the D record supplement indicator is set to Y, the D record also includes a
record number that ensures that data extracted from an MVS file without an index
but with an XREF, will be loaded to the target in the sequence in which they were
read.
CCSID : Identifies the CCSID for an MVS object.
OBJECT_NAME_LONG : Identifies the object name; if object type is M the full MVS file
name is listed; if object type is D the location, creator and table names are listed
instead:
LOCATION
The location at which the DB2 table name identified in the CREATOR and
TBNAME fields exists.
CREATOR
The authorization ID of the owner of the table in the TBNAME field.
TBNAME
The name of the table to which this header record corresponds.
ORIG_OBJ_NAME : Identifies the original object name if the extract request has been
cloned. If object type is M the full MVS file name is listed; if object type is D the
location, creator and table names are listed instead:
LOCATION
The location at which the DB2 table name identified in the CREATOR and
TBNAME fields exists.
CREATOR
The authorization ID of the owner of the table in the TBNAME field.
TBNAME
The name of the table to which this header record corresponds.
Base Table Record — B
(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
A base table record will be present for each DB2 view included in the extract process.
Each base table record will share a record-type number with a header record. Together,
the header and base table records provide information about the view and its base table.
The format of the base table record is shown in Figure 4-106.
Figure 4-106. Base Table Record Layout
01
05
05
05
05
05
05
05
05
05
BASE-RECORD.
RCD-TYPE
RCD-TYPE-NO
SUBSYS
LOCATION
CREATOR
TBNAME
RI-DEP-IND
FILLER
BPOOL
PIC
PIC
PIC
PIC
PIC
PIC
PIC
PIC
PIC
X(1) VALUE 'B'.
X(3) VALUE 'nnn'.
X(4).
X(16).
X(8).
X(18).
X(1).
X(1).
X(9).
Extract
4-157
The following is an explanation of the fields contained in the base table record layout:
RCD-TYPE : A value of ’B’ will be present in this field. The value ’B’ indicates that this is
a base table record.
RCD-TYPE-NO : A three-digit number that identifies the record in the file. This field is
referenced by create records and data records that contain the same three-digit
number in the RCD-TYPE-NO field.
SUBSYS : The DB2 subsystem on which the table name identified in the CREATOR and
TBNAME field exists.
LOCATION : The location at which the table name identified in the CREATOR and
TBNAME fields exists.
CREATOR : The authorization ID of the owner of the table in the TBNAME field.
TBNAME : The name of the table to which this base table record corresponds.
RI-DEP-IND : A value of ’Y’ indicates that the table identified by the CREATOR and
TBNAME fields is a dependent in a DB2 RI relationship.
BPOOL : Buffer pool where creator.tbname resides. Only used when table contains
either LVCHAR or LVGRPH columns.
Database Create Record — F
(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The database create record is generated when your extract includes DB2 objects. It
contains DB2 DDL statements related to the extracted DB2 objects. The format of the
create record is shown in Figure 4-107.
Figure 4-107. Database Create Record Layout
01
05
05
05
CREATE-RECORD.
RCD-TYPE
PIC X(1) VALUE 'F'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
CREATE-TEXT PIC X(76).
The following is an explanation of the fields contained in the database create record
layout:
RCD-TYPE : A value of 'F' will be present in this field. The value 'F' indicates that this is a
database create record.
RCD-TYPE-NO : A three-digit sequence number that keeps track of the number of
databases in the extract. For example, a value of '002' indicates it is the second
database in the extract.
CREATE-TEXT : Contains the DB2 DDL required to create or alter databases.
Tablespace Create Record — G
(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The tablespace create record is generated when your extract includes DB2 objects. It
contains DB2 DDL statements captured during extract processing to create and alter
tablespaces that File-AID/RDX uses to generate load JCL. The format of the create record
is shown in Figure 4-108.
4-158
File-AID/RDX Reference
Figure 4-108. Tablespace Create Record Layout
01
05
05
05
CREATE-RECORD.
RCD-TYPE
PIC X(1) VALUE 'G'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
CREATE-TEXT PIC X(76).
The following is an explanation of the fields contained in the tablespace create record
layout:
RCD-TYPE : A value of 'G' will be present in this field. The value 'G' indicates that this is
a tablespace create record.
RCD-TYPE-NO : A three-digit sequence number that keeps track of the number of
tablespaces in the extract. For example, a value of '002' indicates it is the second
tablespace in the extract.
CREATE-TEXT : Contains the DB2 DDL required to create or alter tablespaces.
DB2 Source Environment Record — C
The DB2 Source Environment record is generated when you extract records from a DB2
object. It contains DB2 catalog information captured during extract processing to create
and alter DB2 objects that File-AID/RDX uses to generate load JCL. The format of the DB2
Source Environment record is shown in Figure 4-109.
In order to increase data security the File-AID/RDX extract file no longer includes DDL
statements in readable form. The DB2 source environment information is now captured
in a masked format.
Figure 4-109. DB2 Source Environment Record Layout
01
05
05
05
CREATE-RECORD.
RCD-TYPE
PIC X(1) VALUE 'C'.
RCD-TYPE-NO PIC X(3) VALUE '001'.
CREATE-ATTR BIN X(..).
The following is an explanation of the fields contained in the DB2 Source Environment
record layout:
RCD-TYPE : A value of 'C' will be present in this field. The value 'C' indicates that this is
a DB2 Source Environment record.
RCD-TYPE-NO : A value of '001' will be present in this field. The value '001' indicates
that this is a DB2 Source Environment record.
CREATE-ATTR : Contains the DB2 Source Environment information for the extracted
DB2 object in a masked format.
MVS File Create Record — E
The MVS File create record is generated for each extracted MVS object. It contains file
allocation and filed mapping information captured during extract processing to create
and alter objects that File-AID/RDX uses during the load process to support autocreate.
The format of the MVS file create record is shown in Figure 4-110.
Extract
4-159
Figure 4-110. MVS File Create Record Layout
01
05
05
05
CREATE-RECORD.
RCD-TYPE
PIC X(1) VALUE 'E'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
CREATE-ATTR BIN X(..).
The following is an explanation of the fields contained in the MVS file create record
layout:
RCD-TYPE : A value of 'E' will be present in this field. The value 'E' indicates that this is a
MVS file create record.
RCD-TYPE-NO : A three-digit alphanumeric ID that corresponds to the header record
number indicating the object to which this record corresponds. For example, if a
value of '002' is present, look at record type 'H002' to determine the object to which
this record corresponds.
CREATE-ATTR : Contains the binary records for allocation information for the file,
alternate indexes information, path definitions, and map data. All data is related to
the object identified in the corresponding 'Hnnn' record.
View Create Record — V
(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The view create record is generated when you specify YES in the “Views” field in the
“Extract File Specification Screen” (Figure 4-88 on page 4-124) to capture all create view
DDL related to the extracted DB2 objects. The format of the create record is shown in
Figure 4-111.
Figure 4-111. View Create Record Layout
01
05
05
05
CREATE-RECORD.
RCD-TYPE
PIC X(1) VALUE 'V'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
CREATE-TEXT PIC X(76).
The following is an explanation of the fields contained in the view create record layout:
RCD-TYPE : A value of 'V' will be present in this field. The value 'V' indicates that this is
a view create record.
RCD-TYPE-NO : A three-digit alphanumeric that corresponds to the header record
number indicating the view to which this record corresponds. For example, if a value
of '002' is present, look at record type 'H002' to determine the view to which this
record corresponds.
CREATE-TEXT : Contains the DB2 DDL required to create views. All DDL is related to the
view identified in the corresponding 'Hnnn' record.
Alias Create Record — A
(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The alias create record is generated when you specify YES in the “Alias” field in the
“Extract File Specification Screen” (Figure 4-88 on page 4-124) to capture all create alias
DDL related to the extracted DB2 objects. The format of the create record is shown in
Figure 4-112.
4-160
File-AID/RDX Reference
Figure 4-112. Alias Create Record Layout
01
05
05
05
CREATE-RECORD.
RCD-TYPE
PIC X(1) VALUE 'A'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
CREATE-TEXT PIC X(76).
The following is an explanation of the fields contained in the alias create record layout:
RCD-TYPE : A value of 'A' will be present in this field. The value 'A' indicates that this is
a alias create record.
RCD-TYPE-NO : A three-digit sequence number that keeps track of the number of aliases
in the extract. For example, a value of '002' indicates it is the second alias in the
extract.
CREATE-TEXT : Contains the DB2 DDL required to create or alter aliases.
Synonym Create Record — S
(Obsolete - only applies to extracts created with File-AID/RDX Release 4.5 or earlier.) 
The create record is generated when you specify YES in the “Synonyms” field in the
“Extract File Specification Screen” (Figure 4-88 on page 4-124) to capture all create
synonym DDL related to the extracted DB2 objects. The format of the create record is
shown in Figure 4-113.
Figure 4-113. Synonym Create Record Layout
01
05
05
05
CREATE-RECORD.
RCD-TYPE
PIC X(1) VALUE 'S'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
CREATE-TEXT PIC X(76).
The following is an explanation of the fields contained in the synonym create record
layout:
RCD-TYPE : A value of 'S' will be present in this field. The value 'S' indicates that this is a
synonym create record.
RCD-TYPE-NO : A three-digit sequence number that keeps track of the number of
synonyms in the extract. For example, a value of '002' indicates it is the second
synonym in the extract.
CREATE-TEXT : Contains the DB2 DDL required to create or alter synonyms. All DDL is
related to the table identified in the corresponding ’Hnnn’ record.
Map Record — M
(Obsolete - only applies to extracts created with File-AID/RDX Release 2.5.1 or earlier.)
The map record is only generated when you specify NO in the Capture Table and Index
DDL for the LOAD Auto Create feature field in the LOAD Related Processing Options
pop-up window. The map record is similar to the create record except that the map
record is only used during load processing for column mapping. The format of the map
record is shown in Figure 4-114 on page 4-161.
Extract
4-161
Figure 4-114. Map Record Layout
01
05
05
05
MAP-RECORD.
RCD-TYPE
PIC X(1) VALUE 'M'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
MAP-TEXT
PIC X(76).
The following is an explanation of the fields contained in the map record layout:
RCD-TYPE : A value of 'M' will be present in this field. The value 'M' indicates that this is
a map record.
RCD-TYPE-NO : A three-digit number that corresponds to the header record number
indicating to which table this record corresponds. For example, if a value of '002' is
present, look at record type 'H002' to determine to which table this record
corresponds.
MAP-TEXT : Contains the DB2 DDL used during load processing for column mapping.
All DDL is related to the table identified in the corresponding 'Hnnn' record.
Relationship Record — R
The relationship record is generated when your extract includes related objects. It
contains the relationship information for the related objects when the extract was
created. File-AID/RDX uses this information when disguising the extract using the FileAID Data Privacy plugin of the Topaz Workbench. The format of the relationship record
is shown in Figure 4-115.
In order to increase data security of the File-AID/RDX extract file the relationship
information is not in readable form.
Figure 4-115. Relationship Record Layout
01
05
05
05
RELATIONSHIP-RECORD.
RCD-TYPE
PIC X(1) VALUE 'R'.
RCD-TYPE-NO PIC X(3) VALUE '001'.
CREATE-ATTR BIN X(..).
The following is an explanation of the fields contained in the relationship record layout:
RCD-TYPE : A value of 'R' will be present in this field. The value 'R' indicates that this is
a relationship record.
RCD-TYPE-NO : A value of '001' will be present in this field. The value '001' indicates
that this is a relationship record.
CREATE-ATTR : Contains the relationship information for the extracted DB2 objects in a
masked format.
Data Record — D
The data record contains the actual data extracted from DB2 and MVS objects. The
format of the data record is shown in Figure 4-116.
Figure 4-116. Data Record Layout
01
05
05
05
DATA-RECORD.
RCD-TYPE
PIC X(1) VALUE 'D'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
ROW-DATA
PIC X.
4-162
File-AID/RDX Reference
The following is an explanation of the fields contained in the data record layout:
RCD-TYPE : A value of 'D' will be present in this field. The value 'D' indicates that this is
a data record.
RCD-TYPE-NO : A three-digit alphanumeric that corresponds to the header record
number, indicating the table from which this record was extracted. For example, if a
value of '002' was present, look at record type 'H002' to determine the table from
which this record was extracted.
ROW-DATA : Contains the contents of the row. The length of this field depends on the
length of the row. Data records are in compressed form if the extract file was created
with the compression option (see also “Compress” on page 4-125).
If the D record supplement indicator in the product record (see “Product Record — 0”
on page 4-154) is set to Y, the D record also includes a record number that ensures
that data extracted from an MVS file without an index but with an XREF, will be
loaded to the target in the sequence in which they were read.
XML/LOB Data Record — x
The XML/LOB data record contains the actual XML or LOB data extracted from DB2
objects. The format of the XML/LOB data record is shown in Figure 4-117.
Figure 4-117. XML/ LOB Data Record Layout
01
05
05
05
DATA-RECORD.
RCD-TYPE
PIC X(1) VALUE 'x'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
ROW-DATA
PIC X.
The following is an explanation of the fields contained in the XML/LOB data record
layout:
RCD-TYPE : A value of 'x' will be present in this field. The value 'x' indicates that this is a
XML or LOB data record.
RCD-TYPE-NO : A three-digit alphanumeric ID that corresponds to the header record
number, indicating the table from which this record was extracted. For example, if a
value of '002' was present, look at record type 'H002' to determine the table from
which this record was extracted.
ROW-DATA : Contains the contents of the row. The length of this field depends on the
length of the row. XML/LOB data records are in a masked format to provide data
security.
Order Record — O
The order records are used to record the order in which objects were extracted. The
format of the data record is shown in Figure 4-118.
Figure 4-118. Order Record Layout
01
05
05
05
ORDER-RECORD.
RCD-TYPE
PIC X(1) VALUE 'O'.
RCD-TYPE-NO PIC X(3) VALUE 'nnn'.
NBR_ENTS
PIC S9(9) COMP.
The following is an explanation of the fields contained in the order record layout:
Extract
4-163
RCD-TYPE : A value of 'O' will be present in this field. The value 'O' indicates that this is
an order record.
RCD-TYPE-NO : A three-digit alphanumeric that corresponds to the header record
number, indicating the table from which this record was extracted. For example, if a
value of '002' was present, look at record type 'H002' to determine the object from
which this record was extracted.
NBR_ENTS : The first ‘O’ record and the last ‘O’ record identify the total number of ‘O’
records in this extract in binary.
Trailer Record — T
A trailer record will be present for each header record in the extract. The format of the
trailer record is shown in Figure 4-119.
Figure 4-119. Trailer Record Layout
01
TRAILER-RECORD.
RCD-TYPE
RCD-TYPE-NO
SUBSYSTEM
OBJECT_NAME
10 LOCATION
10 CREATOR
10 TABLE-NAME
10 FILLER
05 ROW-COUNT
05 OBJECT_TYP
05 RCD_LENGTH
05 NUM_PARTITIONS
05 PARTKEYCOLNUM
05 SECURITY_LABEL
05 SPLIT_ROWS
05 FILLER
05 OBJNAME_DB2V8
10 LOCATION
10 CREATOR
10 TABLE-NAME
05 XML_TOT
05 XML_MAX
05
05
05
05
PIC X(1) VALUE 'T'.
PIC X(3) VALUE 'nnn'.
PIC X(4).
PIC X(52).
PIC X(16).
PIC X(8).
PIC X(18).
PIC X(10).
PIC X(8).
PIC X(1).
PIC X(8). 
PIC X(1) VALUE 'Y'.
PIC X(1) VALUE 'Y'.
PIC X(1) VALUE 'Y'.
PIC X(1) VALUE 'Y'.
PIC X(9).
PIC X(272).
PIC X(16).
PIC X(128).
PIC X(128).
PIC S9(09) COMP-5.
PIC S9(09) COMP-5.
The following is an explanation of the fields contained in the trailer record layout:
RCD-TYPE : A value of 'T' will be present. The value 'T' indicates that this is a trailer
record.
RCD-TYPE-NO : A three-digit alphanumeric that corresponds to the header record
number, indicating the object to which this record refers. For example, if a value of
'002' was present, look at record type 'H002' to determine the object to which this
record refers.
SUBSYSTEM : The DB2 subsystem in which the object corresponding to this record
exists. Blank for MVS objects.
OBJECT_NAME : Identifies the object name; if object type is M the full MVS file name is
listed; if object type is D the location, creator and table names are listed instead:
LOCATION
The location at which the table corresponding to this record exists.
CREATOR
The authorization ID of the owner of the table corresponding to this
record (blank, if DB2 long object name).
TABLE-NAME
The name of the table to which this record corresponds (blank, if DB2
long object name).
FILLER
Filler.
ROW-COUNT : The number of rows extracted from the table that corresponds to this
record.
4-164
File-AID/RDX Reference
OBJECT_TYPE : Identifies the object type: D = DB2, M = MVS.
RCD_LENGTH : The maximum record length extracted from the object that corresponds
to this record.
OBJ_SIZE : The number of bytes (Kilobytes?) per object extracted from the object that
corresponds to this record.
NUM_PARTITIONS : If the number of tablespace partitions is greater than 254, this
indicator is set to Y (Autocreate disabled).
PARTKEYCOLNUM : If table controlled partitioning is used, this indicator is set to Y
(Autocreate disabled).
SECURITY_LABEL : If the security_label is R, this indicator is set to Y (Autocreate
disabled).
SPLIT_ROWS : If split rows is enabled, this indicator is set to Y (Autocreate disabled).
OBJNAME_DB2V8 : Identifies the object name in its full length; if object type is M the
full MVS file name is listed; if object type is D the location, creator and table names
are listed instead:
LOCATION
The location at which the table corresponding to this record exists.
CREATOR
The authorization ID of the owner of the table corresponding to this
record (up to 128 characters).
TABLE-NAME
The name of the table to which this record corresponds (up to 128
characters).
XML_TOT : Total length in Kilobytes (in binary format) of all XML or LOB columns for
the table that corresponds to this record.
XML_MAX : Maximum size in Kilobytes (in binary format) of an XML or LOB value for
the table that corresponds to this record.
Work files
During an extract, File-AID/RDX creates some work files that it deletes after extract
execution.
The work files have the following format::
userid.prefix.*.Dnnnnnn.Tnnnnnn.suffix
Where prefix is set by the profile variable “File Prefix” (see “File Prefix” on page 2-24),
and * is either EXTCRIT or PARMS, and suffix is set by the profile variable “File Suffix”
(see “File Suffix” on page 2-25).
Periodically, you may want to manually delete any left-over work files from incomplete
extracts that are no longer needed.
File-AID/RDX Encryption Exit
File-AID/RDX’s encryption exit, XFRENXT, is called prior to writing row data to the
extract file during batch execution of a File-AID/RDX extract. XFRENXT can be tailored
to your site’s requirements to protect sensitive data being extracted. Your user-defined
encryption exit also can pass an error code back to File-AID/RDX to terminate processing
with a return code of 16 and the File-AID/RDX error message XFRE000. The return code
passed from your encryption exit will be part of the File-AID/RDX error message,
XFRE000.
If you require information about your encryption exit, contact the person at your site
responsible for File-AID/RDX.
Extract
4-165
Encryption Exit Parameters
The following table describes the output parameter your encryption exit can return to
File-AID/RDX:
Table 4-10. File-AID/RDX Encryption Exit Output Parameters
Field
Position
Length
Format
Description
ERROR-CODE
1
4
binary
Error code that can be set
by the user-written exit
and returned to FileAID/RDX.
Table 4-11. File-AID/RDX Encryption Exit Input Parameters
Field
Position
Length
Format
Description
USER_ID
5
7
CHAR
TSO user ID.
SUBSYS
12
4
CHAR
DB2 subsystem ID.
LOC
16
16
CHAR
Location.
CREATOR
32
8
CHAR
Creator of the table whose
row is being passed.
TBNAME
40
18
CHAR
Name of the table whose
row is being passed.
NULL-INDS
58
1500
CHAR
Null indicators for each of
the columns defined in the
table whose row is being
passed.
ROW-DATA
1558
32714
CHAR
The actual row of data
from the table whose rows
are being written to the
extract file.
ROW-LGTH
34272
2
binary
The length of the row
being passed.
Record Layout and File-AID/MVS XREF JCL
The JCL shown in Figure 4-120 is added to the extract JCL (see “Extract JCL” on page
4-142) when you specify for File-AID/RDX to create a record layout file or a record layout
file and a File-AID/MVS XREF (record layout cross reference) file in “Extract File
Specification Screen” on page 4-124.
Figure 4-120. Record Layout JCL
//EXFLC
EXEC PGM=XFREXEC,REGION=8192K,MEMLIMIT=4G,
//
PARM=(FR,N,B)
//STEPLIB DD DSN=Combined-File-AID/RDX-load-library,DISP=SHR
//RDXMLIB DD DSN=File-AID/RDX-message-library,DISP=SHR
//EXTPARMS DD DSN=extract-parms-file,DISP=SHR
//EXTRACT DD DSN=extract-to-file-name,
//
DISP=old or new or SHR
//CLAYOUT DD DSN=record-layout-file-name,
//
DISP=old or new or SHR
//XREF001 DD DSN=XREF-file-name,
//
DISP=old or new or SHR
//*
//SYSOUT
DD SYSOUT=(*)
//SYSTERM DD SYSOUT=(*)
//SYSPRINT DD SYSOUT=(*) 
XFREXEC is the File-AID/RDX program name.
4-166
File-AID/RDX Reference
The parameter information in the PARM field in the EXEC statement must have the
format as shown in Table 4-7:
Table 4-12. EXEC Statement PARM Field—Extract Step
Parameter
Default
Value
Length
Description
Product
FR
2
File-AID/RDX
Option
N
1
File-AID/RDX option number.
Operating Mode
B
1
B : Batch
The following DD statements are required for record layout:
Table 4-13. DD Statements—Record Layout
DD Statement Description
STEPLIB
File-AID/RDX load libraries (CXVJLOAD and SXVJLOAD)
RDXMLIB
File-AID/RDX message library
EXTPARMS
File containing the extract parameters (see “EXTPARMS File” on page 4-144).
EXTRACT
File to which extracted data is written.
CLAYOUT
File to which record layout is written.
XREF001
File to which the record layout cross reference (XREF) for the extract file is written.
SYSOUT
Output class.
SYSTERM
Output class for runtime errors.
SYSPRINT
Standard output stream.
Return Codes
An execution return code (RC) appears in the output listing. For return codes other than
0, an error code and message indicating the specific problem also appear in the listing. In
general, the return codes can be summarized as follows:
Return Code
Description
0
Job ran to completion.
4
Job ran to completion, warnings issued.
8
Job completed with error.
16
Severe error, job aborted.
File-AID/RDX Record Layout File
During the record layout generation process, File-AID/RDX writes to the record layout
file.
The record layout file has the following characteristics:
File organization : Partitioned (DSORG=PO) or sequential (DSORG=PS)
Record format : Fixed-blocked (RECFM=FB)
Logical record length : 80
If you specify a new file (DISP=NEW), the file organization can be sequential or
partitioned.
The record layout file includes the layout for all extracted objects, either in COBOL or
PL/I format.
Extract
4-167
Notes:
1. When you ask File-AID/RDX to create only a record layout (Create XREF = NO) for
MVS objects, the resulting layout is only for the complete extracted record, not the
fields within the record (see layout for object FARDX.SAMP.OBJA.KSDS shown in
Figure 4-123 on page 4-169).
2. When the record layout is requested together with an XREF for the extract file, record
layouts are only created for all DB2 objects. For MVS objects, the XREF points to the
source layout, the one used when the relationship was defined. The XREF assumes
that it is the layout file specified with the Create Record Layout function (see “MVS
File Create Record — E” on page 4-158). Also, the generated record layout includes a
default layout for all non-data records (see Figure 4-122 on page 4-168 and Figure 4123 on page 4-169).
Sample COBOL Record Layout
Figure 4-121 shows a sample COBOL record layout. It identifies each object by its name
and lists null indicators and column/field names with column/field type and length.
When you requested to only create a record layout (Create XREF=NO), the layout
includes the extract record ID (Dnnn).
Figure 4-121. Sample COBOL Record Layout (Create XREF=NO)
****************************************************************
* COBOL RECORD LAYOUT FOR TABLE TSOID01 CUSTOMER_TABLE
*
****************************************************************
01 TSOID01-CUSTOMER-TABLE.
05 RECORD-ID-D001
PIC X(4) .
05 NULL-INDICATORS.
10 CONTACT-TITLE-NULL
PIC S9(4) COMP.
10 CONTACT-ADDR-NULL
PIC S9(4) COMP.
10 CONTACT-CITY-NULL
PIC S9(4) COMP.
10 CONTACT-STATE-NULL
PIC S9(4) COMP.
10 CONTACT-ZIP-NULL
PIC S9(4) COMP.
10 CONTACT-COUNTRY-NULL
PIC S9(4) COMP.
10 CONTACT-AREA-CD-NULL
PIC S9(4) COMP.
10 CONTACT-TELEPHONE-NULL
PIC S9(4) COMP.
05 COBOL-CUSTOMER-TABLE.
10 CUSTOMER-NUMBER
PIC X(6).
10 COMPANY-NAME
PIC X(30).
10 ADDRESS
PIC X(30).
10 CITY
PIC X(25).
10 STATE
PIC X(2).
10 ZIP-CODE
PIC X(9).
10 COUNTRY
PIC X(20).
10 AREA-CODE
PIC X(3).
10 TELEPHONE-NUM
PIC X(7).
10 CONTACT-NAME
PIC X(30).
10 CONTACT-TITLE
PIC X(30).
10 CONTACT-ADDR
PIC X(30).
10 CONTACT-CITY
PIC X(25).
10 CONTACT-STATE
PIC X(2).
10 CONTACT-ZIP
PIC X(9).
10 CONTACT-COUNTRY
PIC X(10).
10 CONTACT-AREA-CD
PIC X(3).
10 CONTACT-TELEPHONE
PIC X(7).

4-168
File-AID/RDX Reference
Sample PL/I Record Layout
Figure 4-122 shows a sample PL/I record layout. It identifies each object by its name and
lists null indicators and column/field names with column/field type and length. When
you requested to create a record layout and XREF (Create XREF=YES), the layout file
includes a default layout for all non-data records.
Figure 4-122. Sample PL/I Record Layout (created with XREF=YES)
/******************************************************************/
/* PLI RECORD LAYOUT FOR TABLE TSOID01 CUSTOMER_TABLE
*/
/******************************************************************/
DCL 1 TSOID01_CUSTOMER_TABLE UNALIGNED,
5 NULL_INDICATORS UNALIGNED,
10 CONTACT_TITLE_NULL
BIN FIXED(15),
10 CONTACT_ADDR_NULL
BIN FIXED(15),
10 CONTACT_CITY_NULL
BIN FIXED(15),
10 CONTACT_STATE_NULL
BIN FIXED(15),
10 CONTACT_ZIP_NULL
BIN FIXED(15),
10 CONTACT_COUNTRY_NULL
BIN FIXED(15),
10 CONTACT_AREA_CD_NULL
BIN FIXED(15),
10 CONTACT_TELEPHONE_NULL
BIN FIXED(15),
5 PLI_CUSTOMER_TABLE UNALIGNED,
10 CUSTOMER_NUMBER
CHAR(6),
10 COMPANY_NAME
CHAR(30),
10 ADDRESS
CHAR(30),
10 CITY
CHAR(25),
10 STATE
CHAR(2),
10 ZIP_CODE
CHAR(9),
10 COUNTRY
CHAR(20),
10 AREA_CODE
CHAR(3),
10 TELEPHONE_NUM
CHAR(7),
10 CONTACT_NAME
CHAR(30),
10 CONTACT_TITLE
CHAR(30),
10 CONTACT_ADDR
CHAR(30),
10 CONTACT_CITY
CHAR(25),
10 CONTACT_STATE
CHAR(2),
10 CONTACT_ZIP
CHAR(9),
10 CONTACT_COUNTRY
CHAR(10),
10 CONTACT_AREA_CD
CHAR(3),
10 CONTACT_TELEPHONE
CHAR(7);
/********************************************************************/
/* PLI RECORD LAYOUT FOR
*/
/*
OBJECT:
NON-DATA-RECORDS
*/
/*
LAYOUT DSN:
NOT.APPLICABLE
*/
/*
LAYOUT MEMBER: DEFAULT
*/
/*
01 LEVEL NAME: OBJECT_DFLT
*/
/********************************************************************/
DCL 1 OBJECT_DFLT,
5 RECORD_ID_DFLT_DATA CHAR(27990);
File-AID/MVS XREF File
During the XREF generation process, File-AID/RDX writes to the record layout cross
reference information for the extract file into the specified File-AID/MVS XREF file.
The XREF file has the following characteristics:
File organization : Partitioned (DSORG=PO)
Record format : Variable-blocked (RECFM=VB)
Logical record length : 300
The XREF file includes the record layout cross reference information for all extracted
objects.
Sample XREF for Extract File
Figure 4-123 on page 4-169 shows a sample XREF output. It identifies the record layout
cross references for the extracted data records in the extract file.
Extract
Figure 4-123. Sample XREF for DB2 and MVS objects
/*
/* CAUTION: If manually editing this member, STATS must be OFF
/* when saving it. Statistics will overlay information in the
/* directory entry needed by File-AID when loading Selection
/* Criteria and XREFs, rendering the member unusable.
/*
/* COMPUWARE assumes no liability for results of using members
/* that have been edited manually.
/*
DEFINEBLOCKS=XREF, 

DESCRIPTION ="FILE-AID/RDX GENERATED XREF", 

LAYOUT_DSNAME=TSOID01.LAYOUT.PLI,
LAYOUT_FILLER=4 

SELECT SET=1,LAYOUT=FRSAMP_CUSTOMER_TABLE,
LAYOUT_MBRNAME=PLIXREF,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D007 

SELECT SET=1,LAYOUT=FRSAMP_CONTACT_TABLE,
LAYOUT_MBRNAME=PLIXREF,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D008 

SELECT SET=1,LAYOUT=PROD001_PART_TABLE,
LAYOUT_MBRNAME=PARTTABL,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D001 

SELECT SET=1,LAYOUT=PROD001_SUPPLIER_TABLE,
LAYOUT_MBRNAME=SUPPLIER,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D002 

SELECT SET=1,LAYOUT=PROD001_CUSTOMER_TABLE,
LAYOUT_MBRNAME=CUSTOMER,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D003 

SELECT SET=1,LAYOUT=PROD001_ORDER_TABLE,
LAYOUT_MBRNAME=ORDERTAB,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D004 

SELECT SET=1,LAYOUT=PROD001_ORDER_LINE_TABLE,
LAYOUT_MBRNAME=ORDERLIN,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D005 

SELECT SET=1,LAYOUT=PROD001_CONTACT_TABLE,
LAYOUT_MBRNAME=CONTACTT,
LAYOUT_TYPE=BASE
IF
POSITION=1,LENGTH=4,OPERATOR=EQ,
TYPE=T,VALUE=D006 

SELECT SET=1,LAYOUT=OBJECT_DFLT,
LAYOUT_MBRNAME=PLIXREF,
LAYOUT_TYPE=DEFAULT 
4-169
4-170
File-AID/RDX Reference
Extract Reports
After the extract job is submitted and executed, an extract report is printed. This report
consists of the following parts:
•
•
•
•
•
•
•
•
•
“Extract Progress Report”
“Relationship Navigation and Sampling Report”
“Relationship Navigation and Sampling Excluded Object Report”
“Object Sampling and Selection Criteria Report”
“Object Sampling and Selection Criteria Excluded Object Report”
“Extract Summary Report”
“Summary of Objects with Zero Rows Extracted”
“Create Record Layout Report”
“DB2 Index Report”
Extract Progress Report
The Extract Progress Report shown in Figure 4-124 displays which objects are being
accessed during the extract and includes the number of rows (records) extracted for each
object.
Figure 4-124. Extract Progress Report
File-Aid/RDX
16.03.00
Extract Progress Report
PAGE 1
DATE 2014-09-02
Extract File. . : TSOID01.R42.EXTRACT(Member)
TIME 09.01.06
Extract Request : TSOID01.RDX.EXTCRIT.D050815.T090104
SSID DSN
Driving Object. : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___


Time
Rows Extracted Object

-------- ---------- --------------------------------------------------------------------------------------------------------------
09:01:07
25 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_
____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____
7____+____8____+____9____+___10____+___11____+___12____+___

09:01:08
18 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_
____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____
7____+____8____+____9____+___10____+___11____+___12____+___

09:01:08
3 M-TSOID01.FASAMP.EMPMAST

09:01:09
8 D-DSNLOCAT.TSOID01.DEPT

09:01:09
1 D-DSNLOCAT.TSOID01.DEPT


The Extract Progress Report displays the extract progress for each object. It includes the
following information:
Time : Shows the time when the progress report for this object was written.
Rows : The number of rows (records) extracted from the current object so far. The update
interval can be set with the User Parm "Table Progress Row Count" (see also “Option
0—Profile” on page 2-1). In this example the progress row count parameter was set at
25.
Extracted Object : The name of the object from which data has been extracted so far.
Extract
4-171
Relationship Navigation and Sampling Report
The “Relationship Navigation and Sampling Report” shown in Figure 4-125 contains the
relationship criteria specified for the extract that produced the report.
Figure 4-125. Relationship Navigation and Sampling Report
File-AID/RDX
16.03.00
Extract File. .
Extract Request
Relationships
Driving Object.
:
:
:
:
Relationship Navigation and Sampling Report
Y Y N -
*
*
*
Y - - N
*
*
*

Relationship 
------------------------------------------------------------------------------------------- 
RI RELNAME: DESCRIPTION___+____2____+____3____+____4____+____5____+____6____+____7____+___
_8____+____9_____+___10____+___11____+___12____+___
Parent: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____
6____+____7____+____8____+____9_____+___10____+___11____+___12____+___.TABLE
____1____+____2____+____3____+____4____+____5____+____6____+____7____+____8_
___+____9____+___10____+___11____+___12____+___

Dependent: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____
6____+____7____+____8____+____9_____+___10____+___11____+___12____+___.TABLE
____1____+____2____+____3____+____4____+____5____+____6____+____7____+____8_
___+____9____+___10____+___11____+___12____+___

RI RELNAME: RDD

Parent: D-DSNLOCAT.TSOID01.DEPT

Dependent: D-DSNLOCAT.TSOID01.DEPT

AR

Desc:

Parent: D-DSNLOCAT.TSOID01.EMP
Dependent: M- TSOID01.FASAMP.EMPMAST


Y Y N N
*
*
*
RI
RELNAME: EMP

Parent: D-DSNLOCAT.TSOID01.EMP
Dependent: D-DSNLOCAT.TSOID01.EMPPROJACT
Y Y N N
*
*
*
RI
RELNAME: EMPPROJ
Parent: D-DSNLOCAT.TSOID01.EMP
Dependent: D-DSNLOCAT.TSOID01.PROJ




*
*
*
AR
Desc: This is the AR description
Parent: D-DSNLOCAT.TSOID01.EMP
Dependent: D-DSNLOCAT.TSOID01.DEPT
Y - - N
*
*
*
AR
Desc:

Parent: D-DSNLOCAT.TSOID01.EMP
Dependent: D-DSNLOCAT.TSOID01.CONTACT_TABLE

Desc:

Parent: D-DSNLOCAT.TSOID01.EMP
Dependent: D-DSNLOCAT.TSOID01.DEPT



*
*
*
AR
* * *
END OF REPORT



- Y N -
Y Y N N
1
2014-09-02
09.01.06
DSN
TSOID01.FR44.EXTRACT(Member)
TSOID01.RDX.EXTCRIT.D050815.T090104
TSOID01.FR44.RELATION
D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___ 

Status
D P S I Cycle MaxRows Deps
---------- - - - - ------ ------- ----- Y N *
*
*

PAGE
DATE
TIME
SSID





* * *
This report shows the name of the extract file, extract request file, relationship file,
driving object, input key file (if specified), and a list of the referential integrity and
application relationships used in the extract process. In addition, the DB2 subsystem ID
or its remote location ID is shown.
This report does not include any excluded objects. Excluded objects are listed separately
in the “Relationship Navigation and Sampling Excluded Object Report”.
For each relationship listed, the following information is shown:
Status : Displays the Excluded status for each relationship excluded from the current
extract process.
Navigation Information:
D (Direct) : Y = Extract all of the dependents of the driving object and their dependents. 
N = Don’t extract any of the dependents of the driving object and their dependents. 
- (dash) = Not meaningful for this relationship, it’s not the driving object or a direct
dependent.
P (Parent) : Y = Extract parents of all extracted data to maintain the integrity of the
extracted data.
4-172
File-AID/RDX Reference
S (Sibling) : Y = Extract other dependents of the extracted parents from the same
relationships.
I (Indirect) : Y = Extract other dependents of the extracted parents from other
relationships.
Sampling Information:
Cycle : The maximum number of cycles for all relationships leading from the object.
Cycle count only applies to downward navigation via the Sibling and Indirect
paths.
Max Rows : the maximum number of rows to extract via downward navigation (direct,
indirect and sibling) of this relationship.
Deps : The maximum number of dependent records to be extracted for each parent
record extracted. An asterisk (*) indicates that File-AID/RDX extracted all dependent
records. This value is used only when extract processing proceeds from a parent
object to a dependent object.
Relationship Information:
Type : The kind of relationship that exists between each pair of corresponding tables.
RI
DB2-defined referential integrity relationship
AR
User-defined application relationship
RELNAME or Desc : Displays the RELNAME for RI relationships or the defined
description for application relationships (AR).
Parent : The name of the object defined as the parent in an RI or application
relationship.
Dependent : The name of the object defined as the dependent (child) in an RI or
application relationship.
Layout : The name of the record layout file defined in a KEY relationship.
Relationship Navigation and Sampling Excluded Object Report
This report is the same report as the “Relationship Navigation and Sampling Report” but
it includes only the excluded objects.
Figure 4-126. Relationship Navigation and Sampling Excluded Object Report
File-AID/RDX
16.03.00
Extract File. .
Extract Request
Relationships
Driving Object.
:
:
:
:
PAGE
DATE
TIME
SSID
1
2014-09-02
09.01.06
DSN
TSOID01.FR44.EXTRACT(Member)
TSOID01.RDX.EXTCRIT.D050815.T090104
TSOID01.FR44.RELATION
D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___ 

Status
D P S I Cycle MaxRows Deps
---------- - - - - ------ ------- ----Excl User - - - *
*
*

Relationship Navigation and Sampling Excluded Object Report
Relationship 
------------------------------------------------------------------------------------------- 
AR
Desc:

Parent: D-DSNLOCAT.TSOID01.EMP

Dependent: D-DSNLOCAT.TSOID01.DEPT

* * *
END OF REPORT
* * *
Refer to “Relationship Navigation and Sampling Report” for the description of the report
fields.
Extract
4-173
Object Sampling and Selection Criteria Report
The “Object Sampling and Selection Criteria Report” shown in Figure 4-127 contains the
selection criteria specified for the extract that produced the report.
Figure 4-127. Object Sampling and Selection Criteria Report
File-AID/RDX
16.03.00
Object Sampling and Selection Criteria Report
PAGE 1
DATE 2014-09-02
Extract File. . . : TSOID01.FR44.EXTRACT(Member)
TIME 09.01.06
Extract Request .: TSOID01.RDX.EXTCRIT.D050815.T090104
SSID DSN
Relationships
: TSOID01.FR44.RELATION
Driving Object. . : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9___
__+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7___
_+____8____+____9____+___10____+___11____+___12____+___ 
Input Keys File: TSOID01.R43.KEYS(EMPKEYS)
---------------------------------------------------- Extract Scope Information -----------------------------------------------------
Cycle count. . . . . . . . . . . . . . . . . . . : * (* for no maximum)
Maximum total rows/objects from all objects. . . : *
Action when maximum rows/records count is reached: QUIESCE
Extract from DB2 using Uncommitted Reads. . . . .: YES
Extract from Image Copy. . . . . . . . . . . . . : NO 
Temporal Parameters:

Temporal Table Present . . . . . . . . . . . . . : D

Use Business Time. . . . . . . . . . . . . . . . : Y

Type of Business Time Criteria . . . . . . . . . : AS OF

Business Start . . . . . . . . . . . . . . . . . : 2011-07-23

Business End . . . . . . . . . . . . . . . . . . :

Use System Time. . . . . . . . . . . . . . . . . : Y

Type of System Time Criteria . . . . . . . . . . : AS OF

System Start . . . . . . . . . . . . . . . . . . : 2011-07-23-00.00.01

System End . . . . . . . . . . . . . . . . . . . :

------------------------------------------------ Criteria Set 1 of 2 - Object Information -------------------------------------------
Status
Cycle MaxRows NTH Object Criteria
---------- ------ ------- ---- -----------------------------------------------------------------------------------------------------
*
*
* D-DSNLOCAT.TSOID01.EMP 
SQL: SELECT * FROM TSOID01.EMP

WHERE EMPNO > '000001'


*
*
* M-TSOID01.FASAMP.EMPMAST
Layout. . . .: TSOID01.FASAMP.LAYOUTS(EMPLOYEE)
01 Level Name: EMPLOYEE-MASTER-FILE

*
*
* D-DSNLOCAT.TSOID01.PROJ


*
*
* D-DSNLOCAT.TSOID01.PROJACT


*
*
* D-DSNLOCAT.TSOID01.EMPPROJACT


*
*
* D-DSNLOCAT.TSOID01.DEPT 
SQL: SELECT * FROM TSOID01.DEPT
WHERE DEPTNO < 'ZZZ'


*
*
* D-DSNLOCAT.TSOID01.CUSTOMER_TABLE


*
*
* D-DSNLOCAT.TSOID01.CONTACT_TABLE 


------------------------------------------------ Criteria Set 2 of 2 - Object Information -------------------------------------------
Status
Cycle MaxRows NTH Object Criteria
---------- ------ ------- ---- -----------------------------------------------------------------------------------------------------
*
*
* D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8__
__+____9_____+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5_
___+____6____+____7____+____8____+____9____+___10____+___11____+___12____+___ 
----+----1----+----2----+----3----+----4----+----5----+----6----+----7-- 
SQL: SELECT * FROM CREATOR__1____+____2____+____3____+____4____+____5____+___
_6____+____7____+____8____+____9_____+___10____+___11____+___12____+___.
TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7__
_+____8____+____9____+___10____+___11____+___12____+___ 

*
*
* M-TSOID01.FASAMP.EMPMAST
Layout. . . .: TSOID01.FASAMP.LAYOUTS(EMPLOYEE)
01 Level Name: EMPLOYEE-MASTER-FILE

Selection criteria used for the object:


DEFINE BLOCKS=SELECTION,


LAYOUT_DSNAME=TSOID01.FASAMP.LAYOUTS,

LAYOUT_MBRNAME=EMPDUP,


INITIAL_SKIP=0,

THEN_SELECT=1,

THEN_SKIP=0,


MAXIMUM_TO_SEARCH=ALL,

MAXIMUM_TO_SELECT=ALL


SELECT SET=1,LAYOUT=EMPLOYEE-MASTER-FILE

IF

FIELD_NAME=EMP-MID-INIT,

POSITION=31,LENGTH=1,OPERATOR=EQ,

TYPE=T,VALUE=R 

4-174
File-AID/RDX Reference
This report does not include any excluded objects. Excluded objects are listed separately
in the “Object Sampling and Selection Criteria Excluded Object Report”.
This report consists of three parts. The first part shows the following:
• The name of the extract file. If the extract file is a PDS, the member name is also
displayed.
• The DB2 subsystem ID and the DB2 remote location ID.
• The name of the extract request file. If the extract request file is a PDS, the member
name is also displayed.
• The name of the relationship file.
• The name of the extract’s driving object.
• The name of the Input (External) Keys File, if one is used for the extract.
The second part shows the values specified for the following extract scope parameters:
•
•
•
•
•
•
The global cycle count.
The total number of rows (records) to extract from all objects.
Action when maximum rows/records count is reached: QUIESCE or STOP.
Extract from DB2 using Uncommitted Reads indicator.
Extract from DB2 Image Copy indicator.
The defined temporal table parameters, if specified for the extract. Temporal Table
Present identifies the temporal table type: B=Business Time, S=System Time,or
D=both, Business and System Time.
The third part shows a list of the criteria sets in the extract including the following for
each set:
•
•
•
•
•
•
•
•
Object status, ALL or PASSTHRU, as applicable.
Cycle count for the object.
The total number of rows (records) to extract from the object.
The value specified in the Select every nth row from object field.
Object name.
Record layout name, if object is an MVS file.
01 Level name, if object is an MVS file.
Any SELECT statement generated for the object.
Extract
4-175
Object Sampling and Selection Criteria Excluded Object Report
The “Object Sampling and Selection Criteria Excluded Object Report” shown in Figure 4128 contains the excluded objects, including exclusion reason, for the extract that
produced the report.
Figure 4-128. Object Sampling and Selection Criteria Excluded Object Report
File-AID/RDX
16.03.00
Object Sampling and Selection Criteria Excluded Object Report
PAGE 1
DATE 2014-09-02
Extract File. . . : TSOID01.FR44.EXTRACT(Member)
TIME 09.01.06
Extract Request .: TSOID01.RDX.EXTCRIT.D050815.T090104
SSID DSN
Relationships
: TSOID01.FR44.RELATION
Driving Object. . : D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9___
__+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7___
_+____8____+____9____+___10____+___11____+___12____+___ 
Input Keys File: TSOID01.R43.KEYS(EMPKEYS)
---------------------------------------------------- Extract Scope Information -----------------------------------------------------
Cycle count. . . . . . . . . . . . . . . . . . . : * (* for no maximum)
Maximum total rows/objects from all objects. . . : *
Action when maximum rows/records count is reached: QUIESCE
Extract from DB2 using Uncommitted Reads. . . . .: YES
Extract from Image Copy. . . . . . . . . . . . . : NO 
Temporal Parameters:

Temporal Table Present . . . . . . . . . . . . . : D

Use Business Time. . . . . . . . . . . . . . . . : Y

Type of Business Time Criteria . . . . . . . . . : AS OF

Business Start . . . . . . . . . . . . . . . . . : 2011-07-23

Business End . . . . . . . . . . . . . . . . . . :

Use System Time. . . . . . . . . . . . . . . . . : Y

Type of System Time Criteria . . . . . . . . . . : AS OF

System Start . . . . . . . . . . . . . . . . . . : 2011-07-23-00.00.01

System End . . . . . . . . . . . . . . . . . . . :

------------------------------------------------ Criteria Set 1 of 2 - Object Information -------------------------------------------
Status
Cycle MaxRows NTH Object Criteria
---------- ------ ------- ---- -----------------------------------------------------------------------------------------------------
*
*
* D-DSNLOCAT.TSOID01.ACT 
***** This object was excluded from extract by the user *****

*
*
* M-TSOID01.FASAMP.EMPLOYEE
***** This object was excluded from extract due to extract scope
*****

Layout. . . .: TSOID01.FASAMP.LAYOUTS(EMPLOYEE)
01 Level Name: EMPLOYEE-MASTER-FILE
------------------------------------------------ Criteria Set 2 of 2 - Object Information -------------------------------------------
Status
Cycle MaxRows NTH Object Criteria
---------- ------ ------- ---- -----------------------------------------------------------------------------------------------------
*
*
* M-TSOID01.FASAMP.EMPMAST
***** This object was excluded from extract by the user *****

*
*
* M-TSOID01.FASAMP.EMPLOYEE
***** This object was excluded from extract due to extract scope
*****

Layout. . . .: TSOID01.FASAMP.LAYOUTS(EMPLOYEE)
01 Level Name: EMPLOYEE-MASTER-FILE

* * * END OF REPORT * * *
Refer to “Object Sampling and Selection Criteria Report” for the description of the report
fields.
4-176
File-AID/RDX Reference
Extract Summary Report
The “Extract Summary Report” shown in Figure 4-129 summarizes the results of the
extract.
Figure 4-129. Extract Summary Report
File-AID/RDX
16.03.00
Extract Summary Report
Extract File. . :
Extract Request :
Compression Type:
Driving Object. :
PAGE
DATE
TIME
SSID
1
2014-09-02
09.01.06
DSN
TSOID01.FR44.EXTRACT(Member)
TSOID01.RDX.EXTCRIT.D050815.T090104
Variable field
D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___


ID
Rows Extracted Objects and Relationships

---- ---------- -------------------------------------------------------------------------------------------------------------------
D001
24 D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____+
___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+____
8____+____9____+___10____+___11____+___12____+___ 
*** Maximum row/record count has been met for this object ***


D002
3 M-TSOID01.FASAMP.EMPMAST

99,999,999 Rows from relationship Parent: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5__
__+___ _6____+____7____+____8____+____9_____+___10____+___11____+___1
2____+___.TABLE____1____+____2____+____3____+____4____+____5____+____
6____+____7____+____8____+____9____+___10____+___11____+___12____+___

Dependent: M-TSOID01.FASAMP.EMPMAST


D006
9 D-DSNLOCAT.TSOID01.DEPT
1 Rows from relationship Parent: D-DSNLOCAT.TSOID01.DEPT

Dependent: D-DSNLOCAT.TSOID01.DEPT

8 Rows from relationship Parent: D-DSNLOCAT.TSOID01.EMP

Dependent: D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5__ 
__+___ _6____+____7____+____8____+____9_____+___10____+___11____+___1
2____+___.TABLE____1____+____2____+____3____+____4____+____5____+____
6____+____7____+____8____+____9____+___10____+___11____+___12____+___

*****
36 TOTAL rows extracted from
8 objects ***** 

* * * END OF REPORT * * *

The “Extract Summary Report” consists of two parts. The first part shows the following:
• The name of the extract file. If the extract file is a PDS, the member name is also
displayed.
• The DB2 subsystem ID and the DB2 remote location ID.
• The name of the extract request file. If the extract request file is a PDS, the member
name is also displayed.
• The compression type.
• The name of the extract’s driving object.
• The name of the Input (External) Keys File, if one is used for the extract.
• The view/base table summary, if DB2 views are part of the extract.
The second part of the report shows the following statistics for each object from which
data was extracted.
ID : The extract object ID (Dnnn) of the object from which data was extracted.
Rows : The number of rows extracted from the object listed in the Extracted Objects
and Relationships column.
Extracted Objects and Relationships : Lists the name of the object from which data was
extracted along with the following information:
n Rows From Relationship: Parent/Dependent : Shows the number of rows
extracted from each relationship from which data was extracted for each
extracted object.
Parent
Displays the name of the parent object for the relationship on this line.
Dependent
Displays the name of the dependent object corresponding to the above
parent object.
n Rows Keys written to Output Key File : Shows the number of keys written to the
specified Output Key File for each extracted object. The reported number
Extract
4-177
includes duplicates which will be removed from the final Output Key File. Only
applicable if the extracted object has a dependent KEY relationship.
Additional Messages : Lists any additional extract message that applies to the
extracted object. Possible Messages include:
*** Selection Criteria applied ***
** Maximum row/record count has been met for this object ***
Info: Key not found - 000040
nnnnn Total Rows Extracted from n objects : This entry is the total number of rows or
records extracted for this extract. It also shows the total number of objects in this
extract.
Summary of Objects with Zero Rows Extracted
The “Summary of Objects with Zero Rows Extracted” list all the objects from which zero
rows (records) were extracted.
Figure 4-130. Summary of Objects with Zero Rows Extracted
File-AID/RDX
16.03.00
Summary of Objects with Zero Rows Extracted
PAGE 1
DATE 2014-09-02
TSOID01.FR44.EXTRACT(Member)
TIME 09.01.06
TSOID01.RDX.EXTCRIT.D050815.T090104
SSID DSN
Variable field
D-LOCATION_1____+_.CREATOR__1____+____2____+____3____+____4____+____5____+____6____+____7____+____8____+____9_____
+___10____+___11____+___12____+___.TABLE____1____+____2____+____3____+____4____+____5____+____6____+____7____+__
__8____+____9____+___10____+___11____+___12____+___


ID
Rows Extracted Objects and Relationships

---- ---------- -------------------------------------------------------------------------------------------------------------------
D003
0 D-DSNLOCAT.TSOID01.PROJ


D004
0 D-DSNLOCAT.TSOID01.PROJACT


D005
0 D-DSNLOCAT.TSOID01.EMPPROJACT


D007
0 D-DSNLOCAT.TSOID01.CUSTOMER_TABLE


D008
0 D-DSNLOCAT.TSOID01.CONTACT_TABLE


***** 5 objects had zero rows extracted.

* * * END OF REPORT * * *

Extract File. . :
Extract Request :
Compression Type:
Driving Object. :
Refer to “Extract Summary Report” for the description of the report fields.
n objects had zero rows extracted : This message shows how many objects in this
extract had zero rows or records extracted.
Create Record Layout Report
The “Create Record Layout Report” shown in Figure 4-131 summarizes for which objects
File-AID/RDX created record layouts during the extract. When applicable, it also lists the
names of the created layout and XREF files.
4-178
File-AID/RDX Reference
Figure 4-131. Create Record Layout Report
FileAID/RDX

2014-09-02
16.40.48 

Record Layout Output File: TSOID01.FRSAMP2.LAYOUTS(LAYOUT1)

XREF Output File. . . . .: TSOID01.FRSAMP.XREF(LAYOUT1 )


ID
COBOL Formatted Record Layouts were created for the following DB2 Objects

---- ------------------------------------------------------------------------------------------------------------------------------
E001 D-LOCATION.FRSAMP.PART_TABLE

E002 D-LOCATION.FRSAMP.SUPPLIER_TABLE

E003 D-LOCATION.FRSAMP.CUSTOMER_TABLE

E004 D-LOCATION.FRSAMP.ORDER_TABLE

E005 D-LOCATION.FRSAMP.ORDER_LINE_TABLE

E006 D-LOCATION.FRSAMP.CONTACT_TABLE

* * * END OF REPORT * * *
16.3
Extract File. . :
Create Record Layout Report
PAGE
TSOID01.FRSAMP.EXTRACT
1
DATE
TIME
DB2 Index Report
The “DB2 Index Report” shown in Figure 4-132 should be empty when an extract runs
well. When File-AID/RDX recognizes that DB2 index utilization could be improved, it
summarizes which if any DB2 indexes were available and used during an extract with
DB2 objects. It contains information about the index configuration that can be used to
improve the performance of an extract by adding or changing an index.
Note:
This report does not address the situation where an index is damaged (advisory
REORG pending).
The report includes:
• Name of the object
• Table cardinality and number of indexes
• Relationship information (RELNAME or AR description)
• Relationship columns
• Index used for SQL SELECT statement generation (if an index exists)
• Description of issues associated with the index
• Action suggested
Extract
4-179
Figure 4-132. DB2 Index Report


Index info for table: DSN8910.PROJ

table cardinality = 20 number of indexes 2

Dependent in relationship (name): RPP

Relationship columns are:

MAJPROJ

Index definition used for SQL generation is no index available, no acceptable index 
Possible usage = tscan only, version:

Action suggested: create an index using the relationship columns if a TSCAN is to be avoided.
It is suggested that a column with high cardinality be the first column of the index.


Index info for table: DSN8910.PROJACT

table cardinality = 77 number of indexes 1

Dependent in relationship (name): RPAP

Relationship columns are:

PROJNO

Index definition used for SQL generation is DSN8910.XPROJAC1, index cardinality: 77 unique 
Possible usage = high level partial, relationship cardinality = 86, version: 2

All relationship columns are included in the index (high order columns) but there are

columns after the relationship columns that reduce the effectiveness of the index. 
Index info for table: DSN8910.EMPPROJACT

table cardinality = 74 number of indexes 2

Dependent in relationship (name): REPAPA

Relationship columns are:

PROJNO

ACTNO

EMSTDATE

Index definition used for SQL generation is DSN8910.XEMPPROJACT1, index cardinality: 74 unique
Possible usage = high level partial, relationship cardinality = 27, version: 2

All relationship columns are included in the index (high order columns) but there are 
columns after the relationship columns that reduce the effectiveness of the index. 
Index Report
RDX Hybrid Scan
The DB2 Index Report includes a RDX Hybrid Scan section (Figure 4-133) when either
situation is detected:
• Presence of a column in the index that cannot be used for the particular relationship
being traversed. This makes any subsequent columns in the index unusable.”
• Unmatched relationship column.
Figure 4-133. DB2 Index Report with Hybrid Scan
RDX "hybrid" scan is possible. This is caused when an index is available but at least
one relationship column is not properly positioned in the index.

FK_LCBS_SPEC_YR cardinality = 5 match

FK_LCBS_SPEC_JUL cardinality = 100 match

FK_LCBS_SPEC_ACC cardinality = 154 match

FK_LCBS_SPEC_SEQ cardinality = 800 match

FK_LCBS_SPEC_SUF cardinality = 8 match

FK_LAB_TYPE_CD cardinality = 1 not matched

FK_POS_LAB_CD cardinality = 60 not matched

This index is missing 1 relationship columns.

4-180
File-AID/RDX Reference
5-1
Chapter 5.
Load
Chap 5
Overview
This chapter describes Option 3, Load. The Load option is used to load data from the FileAID/RDX extract DASD or tape file into multiple related objects. The objects can be MVS
files and/or DB2 tables. The Load option consists of an interactive phase and an
execution phase.
Note:
Before you can load an extract file on tape you must specify an extract summary
file, previously known as an extract tape control file (see “Extract File
Specification” on page 5-8).
The interactive phase takes place online and consists of a File-AID/RDX Load menu that
allows you to provide information about the following:
• The DASD or tape file from which to load data.
• The target objects.
• DB2 LOAD or SQL Insert processing options.
Using this information, File-AID/RDX builds a series of steps to be performed during the
execution phase. You can then edit and save the load JCL created by File-AID/RDX before
you submit it. Your installation may also permit interactive (online) execution of the
load.
In addition, you can create a single request member combining extract and load
specifications. See Chapter 4, “Extract” and “Continue With Load” on page 4-131 for
more information about combining extract and load specifications.
During the execution phase, you can load data into objects that contain data or load it
into empty objects. When loading into DB2 objects you have the choice of using either
IBM’s DB2 LOAD utility or SQL INSERT processing.
Target objects that do not exist can be created automatically as long as their create
information was obtained during the extract.
You can delete all existing data before loading, replace existing rows with records from
the extract file, or leave existing rows intact, only adding rows to the object. You can
perform column-to-column mapping to insert or load data to objects that are defined
differently from the extracted objects.
File-AID/RDX verifies user authority before performing certain operations. See “DB2
Privileges” on page 5-118 for more information.
Support for DB2 XML and LOB Data Type
You can load extracted data from XML and/or LOB columns to target objects using either
SQL Insert or DB2 Load options. When loading an extract disguised with DCF (see also
“Using File-AID/RDX with File-AID/Data Solutions (Using DCF)” on page 7-2), be aware
that the extracted XML and/or LOB data is not disguised and will be loaded unmasked in
its proper format.
5-2
File-AID/RDX Reference
Support for DB2 Temporal Tables
Temporal Table support requires DB2 Version 10 Release 1 or higher. You can load
extracted data from Temporal Tables to existing target Temporal Tables using DB2 Load
Method only. You can specify whether File-AID/RDX generates the PERIODOVERRIDE
clause when loading data to SYSTEM TEMPORAL tables (see “Preserve Temporal” on page
5-13).
GDG Considerations
The name displayed for the source object is the absolute generation of the GDS extracted.
File-AID/RDX generates relative generation numbers for objects in the target
environment, keeping the generations in the same order as they were in the source
environment. You may overtype the generated name with a different name. The target
object can be a GDS with either a relative or absolute generation or it can be a regular
non-GDG dataset. Specifying the GDG base without a version is invalid for a Target
object.
Note:
File-AID/RDX does not support extracting from and loading to tape datasets.
Load Reference List
The Load Reference List screen shown in Figure 5-1 on page 5-3 is displayed when your
profile set it as the first load panel and you
• Select Option 3, Load, from the “File-AID/RDX Primary Option Menu”
or
• Enter the REFERENCE command on a load panel
The reference lists for Load and Delete share the same entries. Delete requests are not
eligible for load processing.
Use this screen to select a load request from the list or start a new load request. FileAID/RDX adds a load request to the list when a request is saved from the “Load Menu”.
In addition, whenever you have successfully executed an extract, File-AID/RDX places an
entry with the extract file name into the load reference list. However, extracts that
originate from the “Single Panel Extract” function are not included in the “Load
Reference List”.
You can also create a new load request with the NEW command, or open a saved load
request file with the REQUEST command.
Note:
If your reference list is empty, File-AID/RDX will display the “Request File
Member List” screen, listing the members of the request file specified in your
profile, or if none is in your profile, display the “Extract File Specification”
screen so you can create a new load request.

The reference list is stored in your personal USER profile. If your USER profile file
(‘userid.midlevlqualifier.PROFILE’) does not exist, File-AID/RDX will create your
USER profile when you are saving an extract or load request.
Refer to “Option G—Global User Defaults” on page 2-26 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.
Load
5-3
Figure 5-1. Load Reference List
File-AID/RDX -------------Command ===>


Load Reference List
-----------
Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go
S = Select
I = Info D = Delete from list

L = Lock
Row 1 to 5 of 5
Scroll ===> CSR
U = Unlock

Request Extract File Name
RT L YY/MM/DD
-------- ------------------------------------------------------ -- - --------
_
TSOID01.FRSAMP.CUSTDB.EXTRACT
10/02/02
_
TSOID01.FRSAMP.EXTRACT
L L 10/02/01
_
TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST)
09/01/24
_ DIEBLD
TSOID01.FRSAMP.CUST.EXTRACT.NODB2
EL L 09/01/14
_ TEST2
TSOID01.FRSAMP.TEST2.EXTRACT
L L 09/01/04
******************************* Bottom of data ********************************
The lower part of the screen displays a listing of your recently referenced load requests.
Use one of the line command to either resubmit one of the requests or model a new
request after it.
Request : Name of the load request (member name in the saved load request file). A
blank entry means the request was saved to a sequential file or that it is an automatic
entry after executing an extract.
Extract File Name : Name of the file containing the extracted data. If saved to a PDS the
member name is displayed in parentheses.
RT : Request Type. Identifies the extract request type:
EL : Extract and Continue with Load request. When selected in the “Load Reference
List” only the load will be performed.
L : Load only request.
L : Locked Entry. Identifies whether the request is locked in the reference list or
whether it is allowed to roll off.
blank : not protected from roll over.
L : Locked in reference list; entry will not roll off the list.
YY/MM/DD : Date when the load request was last saved or the extract was completed.
The list entries are ordered with the most recent date placed on top of the list.
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
D (Delete from list) : Removes this request from the load reference list.
G (Go) : Submits this load request without any changes. File-AID/RDX validates the
request before submitting the JCL for the load request.
I (Info) : Displays the “Request Details” screen, which provides more comprehensive
information about the load request. See Figure 5-2 for an example.
5-4
File-AID/RDX Reference
Figure 5-2. Request Details
File-AID/RDX ---------------- Request Details -------------------------------
Command ===>

Request Information:

Request File Name : TSOID01.FRSAMP.REQUEST

Member Name . . . : TEST2

Request Type . . . : LOAD

Description . . . : FRSAMP Delete request test 2

Reference Date . . : 2009/01/04
Reference Time: 00:00:07 

Driving Object Information:

SSID . . . . . . . :

Name . . . . . . . :


Extract Information:

Extract File Name : TSOID01.FRSAMP.TEST2.EXTRACT

Summary File Name :

Disguise Control File:

Repository Name:

Project Name:

Extract Date . . . : 2009/01/04
Extract Time : 00:00:07 

Relationship Information:

File Name . . . . : TSOID01.FRSAMP.RELATION

L (Lock) : Protects this entry from rolling off the load reference list.
S (Select) : Selects this load request and displays the Load Menu prefilled with all the
information from this request.
U (Unlock) : Does not protect this entry from rolling off the load reference list.
V (View JCL) : Displays the JCL for this load request. File-AID/RDX shows the Generated
JCL panel where you review and modify the load JCL.
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
DETAIL (D) : Expands the one-line display for each request into a two-line display. The
additional line shows the request description. See Figure 5-3 for an example. Detail is
a toggle switch so enter Detail again to return to the original format.
Figure 5-3. Load Reference List - DETAIL Screen
File-AID/RDX -------------Command ===>

Load Reference List
-----------
Primary commands: New, Find, Size, Detail, REQuest 
Line commands: G = Go
S = Select
I = Info D = Delete from list

L = Lock
Row 1 to 5 of 5
Scroll ===> CSR 
U = Unlock

Request Extract File Name
RT L YY/MM/DD
-------- ----------------------------------------------------- -- - --------
_
TSOID01.FRSAMP.CUSTDB.EXTRACT
02/02/02
Description: DB2-TSOID01.CUSTOMER 
_
TSOID01.FRSAMP.EXTRACT
L L 02/02/01
Description: DB2-FRSAMP.CUSTOMER 
_
TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST)
02/01/24
Description:
MVS-TSOID01.CUSTOMER 
_ DIEBLD
TSOID01.CUST.EXTRACT.NODB2
EL
02/01/31
Description: Auto create all files and load 
_ TEST2
TSOID01.FRSAMP.TEST2.EXTRACT
L L 09/01/04
Description:
DB2-FRSAMP.ORDER
******************************* Bottom of data ********************************
Load
5-5
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 load request from an existing extract file. Use the NEW command
to open extract files created with File-AID/RDX prior to Release 3.0.
REQUEST (REQ) : Opens a saved extract or load request file. Refer to “Request File
Member List” on page 5-5 for more information.
File-AID/RDX uses the default value as specified in your current profile. If your
profile doesn’t include a request file, File-AID/RDX prompts for one.
SIZE (S) : Increases the scrollable area to display more entries at a time by hiding some of
the screen header lines. See Figure 5-4 for an example. SIZE is a toggle switch so enter
SIZE again to return to the original format.
Figure 5-4. Load Reference List - SIZE Screen
File-AID/RDX ------------- Load Reference List --------- Row 1 to 6 of 6
Command ===>
Scroll ===> CSR 
Request--Extract File Name-------------------------------------RT-L-YY/MM/DD
_
TSOID01.FRSAMP.CUSTDB.EXTRACT
02/02/02
_
TSOID01.FRSAMP.EXTRACT
L L 02/02/01
_
TSOID01.FRSAMP.PDS.EXTRACT(EXTCUST)
02/01/24
_ DIEBLD
TSOID01.FRSAMP.CUST.EXTRACT.NODB2
EL L 02/01/14
_ TEST2
TSOID01.FRSAMP.TEST2.EXTRACT
L L 02/01/04
****************************** Bottom of data ********************************
Request File Member List
The “Request File Member List Screen” shown in Figure 5-5 on page 5-6 is displayed when
you
• Select Option 3, Load, from the “File-AID/RDX Primary Option Menu” and your
profile set it as the first load panel
or
• Enter the REQUEST primary command on a load panel
This screen displays the member list of a saved extract or load request file. Use one of the
line commands to select a member for your load request.
If you select a member that does not contain valid load request information, FileAID/RDX will issue a message. Select a different member or issue the NEW or REFERENCE
command to start another load request.
Note:
If you want to load from an extract file created prior to Release 3.0, use the NEW
command to initiate a new load request. Then you specify the name of the
extract file.
5-6
File-AID/RDX Reference
Figure 5-5. Request File Member List Screen


File-AID/RDX ------------ Request File Member List ------- Row 1 to 8 of 8 
Command ===>
Scroll ===> CSR

Primary commands: New, Find, Size, REFerence
Line commands: G = Go S = Select, D = Delete R = Rename
Request File ===> FRSAMP.EXTCRIT 
Member
Description
Changed
-------- -------------------------------------------------- ---------- 
_ DB2VSAM
db2 to vsam extract
2004/06/01
_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE
2004/08/13 
_ MIKE1
Member List
2004/05/10 
_ NODB2
mcust with db2 deleted
2004/01/25 
_ ORDER
DB2 - LOCATION.TSOID01.CUSTOMER
2004/08/30
_ PART1
Member List
2003/02/11
_ SELCUST
test select customer
2002/01/28 
_ TESTA
test saving the criteria
2001/04/12
******************************* Bottom of data ********************************
Request File : If you didn’t specify a name with the REQUEST command, the request file
name comes from your current profile. Enter a new file name to change to a different
saved request file and File-AID/RDX will display its member list.
The lower part of the screen displays a listing of the file’s members.
Member : Member name in the saved extract request file. The member names are
displayed in alphabetical order.
Description : Text that was entered in the Description field when the extract or load
request was created. If you left the field blank File-AID/RDX sets the description to
the driving object type and name.
Changed : Date when the member was last saved.
Line Commands
The following File-AID/RDX-specific line commands are valid on this screen:
D (Delete) : Delete this member from the request file. Displays the “Delete Confirmation
window” (Figure 5-6).
Figure 5-6. Delete Confirmation window
Delete Confirmation 
COMMAND ===>
Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’

Member to be Deleted: TESTA
ENTER to confirm delete
END to return to Request File Member List










G (Go) : Submits this load request without any changes. File-AID/RDX validates the
request before submitting the JCL for the load request.
R : Rename the request member. The “Rename Confirmation window” (Figure 5-7)
allows you to enter a new name for the request file member.
Load
5-7
Figure 5-7. Rename Confirmation window
Rename Confirmation 
COMMAND ===>
Request File ....: ‘TSOID01.FRSAMP.EXTCRIT’
Member to be Renamed: TESTA
New Member name ===>
ENTER to confirm rename
END to return to Request File Member List













S (Select) : Selects this load request and displays the Load Menu prefilled with all the
information from this request.
V (View JCL) : Displays the JCL for this load request. File-AID/RDX shows the Generated
JCL panel where you review and modify the load JCL.
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
FIND (F) : Searches the list for the specified string and scrolls the list to display the first
matching entry at the top of the displayed entries. Use RFIND to repeat the search.
NEW (N) : Starts a new load request from an existing extract file (see “Extract File
Specification” on page 5-8).
REFERENCE : opens your Load Reference List file. Refer to Figure 5-1 on page 5-3 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 5-8 for an example. SIZE is a toggle switch so enter
SIZE again to return to the original format.
Figure 5-8. Request File Member List - SIZE Screen
File-AID/RDX ------------ Request File Member List --------- Row 1 to 8 of 8 
Command ===>
Scroll ===> CSR
Member
Description

_ DB2VSAM db2 to vsam extract

_ MCUST0DB MVS - TSOID01.CUSTOMER.FILE

_ MIKE1
Member List

_ NODB2
mcust with db2 deleted

_ ORDER
DB2 - LOCATION.TSOID01.CUSTOMER

_ PART1
Member List

_ SELCUST test select customer

_ TESTA
test saving the criteria

******************************* Bottom of data ********************************
5-8
File-AID/RDX Reference
Extract File Specification
The “Extract File Specification” screen shown in Figure 5-9 is displayed when you
• Enter the NEW command in either the “Load Reference List” or the “Request File
Member List Screen”
Figure 5-9. Extract File Specification
File-AID/RDX ----------Command ===>

-------------------------



Please specify an Extract File or a pattern name (in order to select an

Extract File from a list).


Extract File ===> FRSAMP.EXTRACT






* * * * When the Extract File is on TAPE, a Summary File is REQUIRED. * * * * 
* * * * When the Extract File is on DISK, a Summary File is OPTIONAL. * * * * 

Summary File usage ===> N (N = None; E = Existing; C = Create; U = Update) 
Summary File ===>

Note:
Extract File Specification
Creating or updating a Summary File requires the submission of

a BATCH job. Upon completion of this batch job, the Summary File 
will be available for your use.
Use this screen to specify the name of the extract file from which you want to load data
and optionally, the summary file. Press ENTER to continue to the “Load Menu”
(Summary File usage = N or E), “Create New File” (Summary File usage = C), or the
“ISPF/PDF EDIT Screen” (Summary File usage = U).
Extract File : Specify the name of the File-AID/RDX extract file from which you want to
load data. An asterisk (*) or pattern displays a selection list. The extract file must be
in the format that File-AID/RDX creates during extract. See “Extract File” on page
1-23 and “File-AID/RDX Extract File” on page 4-154 for information about the format
of the extract file.
Summary File usage : Specify whether your load request should utilize the summary file.
The summary file is required for extract files on tape or cartridge, it’s optional for
extract files on disk. Starting with Release 4.8 of File-AID/RDX, a summary file is
created automatically during the extract to tape process (see “Specify Extract “TO”
File Information” on page 4-124). For a multi-volume disk extract file, a summary file
can speed up processing as it contains the header and trailer information for the
extract.
N
None - Specify N when the extract file is on disk and a summary file is not needed.
E
Existing - Specify E when the summary file for this particular extract file already exists.
File-AID/RDX continues with the “Load Menu”.
C
Create - Specify C when you want File-AID/RDX to create the summary file for the above
extract file. File-AID/RDX then starts a batch job that extracts header and trailer
information from the extract file. After the batch job to create the summary file has
finished, you can continue the load request for this extract file.
File-AID/RDX will display the “Create New File” screen (see Figure 4-87 on page 4-121)
to allocate the new file.
Load
U
5-9
Update - Specify U when you want File-AID/RDX to update an existing summary file for
the above extract file. File-AID/RDX then starts a batch job that extracts header and trailer
information from the extract file. After the batch job to update the summary file has
finished, you can continue the load request for this extract file.
Summary File : Specify the name for the summary file (previously known as tape control
file) that contains the information for the above extract file that’s stored on tape,
cartridge, or disk. The summary file is required for extract files on tape or cartridge,
it’s optional for extract files on disk. If your extract file is a multi-volume file, a
summary file can speed up processing as it contains the header and trailer
information for the extract. An asterisk (*) or pattern displays a selection list.
Note:
The summary file is the same for both Load and Delete processes. Therefore, you
may use a summary file created with the DELETE Option for loading data based
on the same extract tape file.
Edit JCL for Summary File
The “ISPF/PDF EDIT Screen” shown in Figure 5-10 is displayed when you select to have
File-AID/RDX create or update the summary file on the “Extract File Specification”
screen.
Figure 5-10. ISPF/PDF EDIT Screen


VIEW - File-AID/RDX Generated JCL --------------------------- COLUMNS 001 072
COMMAND ===>
SCROLL ===> CSR
You are now editing the JCL that File-AID/RDX has generated to perform
the required function. Change this JCL as desired before submitting. 

000004
000005
000006
000007
000008
000009
000010
000011
000012
000013
000014
000015
000016
000017
000018
000019
000020
//*
XFRJSUMM
//*--------------------------------------------------------------------
//* THIS STEP WILL BUILD A SUMMARY FILE BY READING THE HEADER RECORDS 
//* AND TRAILER RECORDS OF YOUR EXTRACT FILE.

//* 
//SUMMARY EXEC PGM=XFREXEC,REGION=4096K,
//
PARM=(FR,A,B)
//STEPLIB DD DISP=SHR,DSN=CPWR.MXVJ160.CXVJLOAD, 
//
DD DISP=SHR,DSN=CPWR.MXVJ160.SXVJLOAD 
//RDXMLIB DD DSN=CPWR.MXVJ160.CXVJMENU,DISP=SHR
//EXTPARMS DD DSN=TSOID01.RDX.PARMS.1300827.T094308,DISP=SHR
//EXTRACT DD DSN=TSOID01.FRSAMP.EXTRACT,
//
DISP=SHR
//*
//CONTROL DD DSN=TSOID01.RDX.SUMMARY,
//
DCB=(RECFM=VB,LRECL=32756,BLKSIZE=32760),
//
DISP=(NEW,CATLG,DELETE),
Use this screen to edit and submit the extract summary JCL generated by File-AID/RDX.
If you want to save this JCL, use the ISPF/PDF CREATE or REPLACE command before you
exit this screen. Otherwise, File-AID/RDX deletes this file.
Submit this JCL to create the summary file with the extract header and trailer
information. File-AID/RDX will return to the “Load Reference List” or “Request File
Member List Screen” where you entered the NEW command.
5-10
File-AID/RDX Reference
Load Menu
After you selected a load request from either the “Load Reference List” or the “Request
File Member List”, completed the “Extract File Specification”, or whenever you enter the
MENU command within the load option, File-AID/RDX displays the “Load Menu” as
shown in Figure 5-11.
Note:
Your profile’s selected load flow (see “Panel Customization” on page 2-16) might
not show the “Load Menu” initially. Just issue the MENU command to display it
from any of the load option panels.
The “Load Menu” provides a quick overview of your current load request and its status
fields are immediately updated upon return from its suboptions. This allows you to
selectively access any of the options or to submit the load request when all load options
are set to your liking.
After completing all load specifications, simply select Option 8 and File-AID/RDX
submits this load job.
Figure 5-11. Load Menu





File-AID/RDX -------------------- Load Menu ---------------------------------
Option ===>
SITE Profile: RDXMENU 

Primary commands: menu-number, ALL, REFerence, REQuest, MODE, SAVE
Line commands: S or / to create flow through selected options.
Extract file name ===> TSOID01.FRSAMP.EXTRACT 
Description
===> 

Current Values
_ 1 Load Object Specifications
SSID=DSN, Load method=DB2
_ 2 Source to Target Mapping
0 of 6 Objects are excluded
_ 3 Target Environment
Create: Tables=6 + DB TS, Files=1
_ 4 Existing Data Options
DB2=Global setting, MVS=By object
_ 5 Insert Processing Options
Log requested 
_ 6 Save Load Request
TSOID01.EXTCRIT(member) 
_ 7 View JCL

_ 8 Submit JCL

The top of this screen consists of the following fields:
Extract File Name : Name of the file that contains the extracted related data to be
loaded.
Description : Displays the description text for the current load request as entered with
the Save Load Request option. Using this description is a helpful way to document
your load request.
Load Menu Options
Enter the option number (1 - 8) to select the desired option or enter ALL to step through
all options in sequence. Alternatively, you may also select one or more options with the S
or / line command.
Note:
Options 6, 7, and 8 are not available for the “Continue With Load” Extract
option (see also “Continue With Load” on page 4-131).
Load
5-11
The Current Values are display fields only and are updated upon return from each of the
load menu options to reflect the current status and value for the option.
1 - Load Object Specifications : Displays the “Load Object Specifications” where you
can specify DB2 target information such as DB2 subsystem, location, load method,
and preserve temporal information, and global object name modifiers for DB2
Creator, DB2 Index name pre- and suffix, MVS high-level qualifier and MVS file name
suffix. The option to revert to source names undoes all applied object name modifiers
without having to exit the Load function.
Current Values shows the target SSID (DB2 subsystem ID) for all DB2 objects that are
part of this load request as well as the load method (DB2 load utility or SQL INSERT
statements).
2 - Source to Target Mapping : Displays the Source to Target Mapping panel where you
invoke the process of mapping columns between source and target objects. From this
panel you also can modify information about the target objects (creator, and tables
for DB2 objects; fully qualified file names for MVS objects) to which data in the
extract file will be loaded. In the list of objects you can mark objects to be excluded
from the load process.
Note:
MVS file with I/O exit: If you want to load an MVS file using an I/O exit,
you must select the MVS file in the Source to Target Mapping panel to invoke
the exit.
Current Values shows how many objects have been excluded from the load process.
3 - Target Environment : Displays the Target Environment panel that lists all target
objects to be loaded including those that don’t exist yet but will be created using the
create information from the extract file. For objects to be created you can then edit
the create information to fit your specific target environment. Optionally, you can
size the objects to be created based on the extract data as opposed to the original
source create information.
Current Values displays the number of MVS and DB2 target objects to be created.
4 - Existing Data Options : Displays the Existing Data Options panel where you specify
what to do with the existing data of the target objects, whether to delete all records,
or replace existing records.
Current Values displays the specified options.
5 - Processing Options : Displays the Processing Options panel where you can specify
DB2 load as well as discard processing options.
Current Values displays the specified option.
6 - Save Load Request : Specify whether to save this load request in a file. File-AID/RDX
presents the Save Load Request panel where you identify the load request file to save
your request to.
Current Values displays None or the name of the load request file.
7 - View JCL : Select this option to view the JCL for this load request. File-AID/RDX
shows the Generated JCL panel where you review and modify the load JCL.
Note:
Option “7 - View JCL” switches to Option “7 - View REXX” when the MODE
primary command has set the execute load mode to INTERACTIVE (online)
(see Figure 5-12). Interactive load execution is an installation option and is
only available if specifically installed at your site.
8 - Submit JCL : Submits the JCL for this load request. Watch for the message that the
job has been submitted and later for the completion message.
Note:
Option “8 - Submit JCL” switches to Option “8 - Execute REXX” when the
MODE primary command has set the execute load mode to INTERACTIVE
5-12
File-AID/RDX Reference
(online) (see Figure 5-12). Interactive load execution is an installation option
and is only available if specifically installed at your site.
Primary Commands
The following File-AID/RDX-specific primary commands are valid on this screen:
ALL : Selects all available load menu options for you to step through in sequence. ALL
does not include option “8 - Submit JCL”. To submit the load JCL, select option “8 Submit JCL” separately or enter the SUBMIT command in the View JCL panel.
MODE : Enter the MODE command in the Command field to enable execution of the
load request interactively (online). Load Menu options “7 - View JCL” and “8 Submit JCL” will change to “7 - View REXX” and “8 - Execute REXX” (see Figure 5-12)
to show that the load will be executed interactively when selecting Option “8 Execute REXX”. MODE acts as a toggle switch.
MODE command is only valid when variable “OLLOAD” is set to Y (see “OLLOAD” of
the File-AID Single Install Image Installation and Configuration Guide).
Notes:
1. INTERACTIVE (online) load is an installation option and is only available if
specifically installed at your site.
2. Interactive mode is not allowed with DB2 Load Utility.
3. Interactive mode is not allowed for an extract with Continue with Load.
Figure 5-12. Load Menu - ONLINE Mode

_
_
_
_
_
4
5
6
7
8
Existing Data Options
Insert Processing Options
Save Load Request
View REXX
Execute REXX
DB2=Global setting, MVS=By object
Log requested 
TSOID01.EXTCRIT(member) 

*** INTERACTIVE_LOAD MODE ACTIVE ***

REFERENCE (REF) : Returns to your load reference list file to start another load request.
Refer to Figure 5-1 on page 5-3 for more information.
REQUEST (REQ) : Returns to a saved load request file to start another load request. Refer
to Figure 5-5 on page 5-6 for more information.
Note:
The REF and REQ commands are not available for the “Continue With Load”
Extract option.
SQLID : Enter the SQLID primary command to change or view the DB2 SQLID for the
current load session. Each load session starts with the default SQLID as specified in
the load profile (see also “Default SQLID” on page 2-14). In the Set SQLID window,
enter the desired SQLID. USER is a valid entry and changes the SQLID to match the
current userid. If you blank out the SQLID, it defaults to the SQLID as specified in the
load profile.
Load
5-13
Load Object Specifications
The “Load Object Specifications” screen shown in Figure 5-13 is displayed when you
select Option 1 from the “Load Menu”.
Figure 5-13. Load Object Specifications

File-AID/RDX --------------- Load Object Specification ------------------------
Command ===>


Specify Target DB2 Environment:

SSID
===> DSN 
Location
===> DSNLOCAT
DB2 Load Method
===> DB2
(SQL = SQL Insert Statement;
DB2 = IBM DB2 Batch Load Utility)
Preserve Temporal
===> N
Retain original temporal time data?
(Y/N) 
Specify Object Name Modifiers:
(/ entry to apply modification)
_ DB2 Creator
===> TSOID01 (Creator for ALL DB2 objects)
_ DB2 Index name prefix
===>

_ DB2 Index name suffix
===>

_ MVS high level qualifier ===> TSOID01 (HLQ for ALL MVS objects)
_ MVS file name suffix
===> NEW


_ Revert to source names
===>
(D = DB2 objects; 
M = MVS objects; 
B= Both)
Use this screen to specify information about the objects (location, subsystem, creator,
tables, and index name modifier for DB2 objects, high level qualifier and file name
modifier for MVS objects) to which data from the extract file will be loaded. You also
specify which load method (DB2 load utility or SQL Insert) to use for the load of DB2
data.
Specify Target DB2 Environment Area
SSID : Specify the name of the DB2 subsystem to which DB2 data will be loaded. If you
leave the Location field blank, the tables you specify to be loaded must exist in the
DB2 subsystem displayed in this field.
Location : Specify the location of the tables you want to load if they are in a remote DB2
subsystem. The location you enter must be defined in the DB2 system catalog table
SYSIBM.LOCATIONS. You must use the SQL Insert Load Option to use the remote
location.
Leave this field blank if the tables you want to load reside in the DB2 subsystem
displayed in the target SSID field.
DB2 Load Method : Specify whether you want to load DB2 data using SQL INSERT
statements or the IBM DB2 Batch Load Utility. See also “SQL Insert and DB2 Load
Utility Load Options” on page 5-15.
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.
Note:
Interactive mode is not allowed with DB2 Load Utility.
Preserve Temporal : Specify whether to generate the PERIODOVERRIDE clause when
DB2 loads data to SYSTEM TEMPORAL tables.
Y : For all SYSTEM TEMPORAL tables in this load, preserve the contents of the
source base and history table regarding the versioning timestamp columns,
ignoring the GENERATE ALWAYS clause.
5-14
File-AID/RDX Reference
N : For all SYSTEM TEMPORAL tables in this load, adhere to the GENERATE ALWAYS
clause on the versioning timestamp columns, consequently updating those
columns as the rows are loaded.
Note:
DB2 Load Method (see “DB2 Load Method” on page 5-13) must be set to
DB2 for Temporal Table support.
Specify Object Name Modifiers
The f