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 is displayed.
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 is displayed.
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.
Output Key File Layout
Field | Starting Column | Ending Column | Description |
|---|---|---|---|
IMS Segment | 1 | 8 | 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 | 9 | 9 | Filler |
Key Value | 10 | n | The extracted key value. |
Output Key Files List
The following figure displayed when you select Option 6 - Output Key Files from 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 in section Add Relationships — Db2 to IMS and Output Key Files). 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 BMC AMI DevX File-AID for IMS extract using the output key files is to be executed as a step following the File-AID/RDX extract.
Output Key Files
Command ===> Scroll ===> PAGE
Line commands: S = Define or update output key file I = Information
IMS DBD Layout Output Key File Name Status
-------- -------- ----------------------------------------- ----------------
_ PORDR ORDR010 KEY Undefined
_ PCUST 'TSOID01.PCUST.KEYS' KEY Defined
_ ORDERTAB 'TSOID01.PORDR.KEYS' KEY Defined
******************************* Bottom of data ********************************
On this screen select an IMS DBD or segment layout to specify the Output Key File to which File-AID/RDX will copy the key values for the selected KEY relation.
Press END to return to the Extract Menu.
The body of the Output Key Files panel consists of the following fields:
Cmd
Use the S (Select) or I (Information) line command to specify or view the KEY relationship information.
IMS DBD
Member name of the DBD library (KEY method 2 and 3).
Layout
Member name of the record or segment layout (KEY method 1 and 3).
Output Key File Name
Lists the name of the file to which the extracted key values will be saved.
Status
Displays one of the following messages:
Message | Explanation |
|---|---|
KEY Undefined | For this KEY relationship you still need to define a key file with the S line command, or exclude the relation from the current extract process, before you can continue. |
KEY Defined | A key file has been defined for this KEY relationship. |
KEY Deleted | The key file definition for this KEY relationship has been deleted. |
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. For more information, see 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 the following figure, 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 BMC AMI DevX 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 following figure is displayed when you enter the S line command for an Output Key File on the Output Key Files screen or when you select Option 6 - Output Key Files from the Extract Menu and your extract request only includes one KEY relationship. You must define an Output Key File for all included relationships with a status of Undefined before the extract process can continue. File-AID/RDX will store the extracted keys in the specified Output Key File.
File-AID/RDX also allows a BMC AMI DevX 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 BMC AMI DevX File-AID for IMS and saved to a data set. The BMC AMI DevX 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.
Output Key File Definition
Command ===>
Parent Object . . .: 'TSOID01.FRSAMP.ORDERTAB'
Record Layout File.: 'TSOID01.FISAMP.COBOLLIB(ORDR010)'
Member Name . . . .:
DBD Library . . . .: PORDR
DBD Member . . . .: 'TSOID01.FISAMP.DBDLIB'
Specify Output Key File Information:
File Name ===>
Member ===> (Blank or pattern for member list)
Disposition ===> NEW (NEW, OLD, SHR)
Specify File-AID for IMS Extract JCL Information:
Extract IMS ===> N (Y=Yes, N=No)
File Name ===>
Member ===> (Blank or pattern for member list)
Use this screen to specify the Output Key File to which File-AID/RDX will copy the key values for the selected KEY relation. The resulting Output Key File can then be used as an Input Key File for another File-AID/RDX extract or by BMC AMI DevX 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 BMC AMI DevX File-AID for IMS extract is to be executed as a step following the File-AID/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
Data set 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 Create New File panel.
Specify File-AID for IMS Extract JCL Information
Extract IMS
Specify Y (Yes) when you want the BMC AMI DevX 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 BMC AMI DevX File-AID for IMS and saved to a file. The file containing the BMC AMI DevX File-AID for IMS extract JCL must have a disposition of OLD.
Specify N (No - default) when you don’t want to include the BMC AMI DevX File-AID for IMS extract JCL in the File-AID/RDX extract.
File Name
Specify the name of the file that contains the BMC AMI DevX 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 following figure is displayed when you specify NEW in the Disposition field in 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.
Create New File
Command ===>
File name: TSOID01.IMSPPART.KEYFILE
Management Class ===> (Blank for default)
Storage Class ===> (Blank for default)
Generic unit ===> SYSDA
Volume serial ===> (Blank for default if unit entered)
Data Class ===> (Blank for default)
Space units ===> TRKS (BLK; TRK; CYL)
Primary quantity ===> 5 (In above units)
Secondary quantity ===> 5 (In above units)
Directory blk ===> 5 (Use 0 for sequential file)
Record Format ===> FB (Required for Output Key file)
Record length ===> 15 (Required LRECL for Output Key file)
Block size ===>
Dataset name type ===> (LIBRARY, PDS, BASIC,
EXTREQ, EXTPREF or blank)
Extended Attributes ===> (NO, OPT or blank)
Number of Volumes ===> (2:59, or blank)
When parameters are complete, use END to continue.
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.
File Name
Displays the name of the file to be allocated.
Management Class
Specify the SMS management class to use for the allocation of the file. The management class describes the migration, backup, and retention for the file.
Storage Class
Specify the SMS storage class to use for the allocation of the file. The storage class describes the hardware requirements of the file.
Generic Unit
Specify the device type on which the new file will reside. The names of these devices are installation dependent.
Volume serial
Specify the volume serial of the direct access device that contains the file.
Data Class
Specify the SMS data class to use for the allocation of the file. The data class describes the attributes of the file such as RECORG, KEYLEN, KEYOFF, SPACE, etc.
Space units
Specify one of the following storage unit types depending on how the file size is expressed:
TRK - Tracks
CYL - Cylinders
BLK - Blocks
KB - Kilobytes
MB - Megabytes
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 data set 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 data set is required.
EXTPREF
Indicates that an extended data set is preferred.
BASIC
Indicates that neither an extended nor a large format sequential data set is to be allocated.
blank
Allocates a partitioned or sequential data set based on the data set characteristics entered.
Extended Attributes
Specify one of the following extended attributes:
NO
Data set cannot have extended attributes or reside in EAS.
OPT
Data set 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 data set (2 to 59), or leave this field blank for a single volume allocation.
Related topics