FILEOUT (Define Output Data Sets)

The FILEOUT function is used to define output data sets, for example to define one or more output data sets used by the EXTBKUP function (see EXTBKUP (Extract from Backup File)). If the table is empty, FILEOUT creates a valid null output data set.
datacom
The FILEOUT function is used to define output data sets, for example to define one or more output data sets used by the EXTBKUP function (see EXTBKUP (Extract from Backup File)). If the table is empty, FILEOUT creates a valid null output data set.
 When used to define one or more output data sets used by the EXTBKUP function, all FILEOUT statements must precede the EXTBKUP statement.
When to Use FILEOUT
Use the FILEOUT function when you want to define output data sets.
How to Use FILEOUT
The MUF must be active when you execute this command. Execute the FILEOUT function using the following command format:
►►─ FILEOUT DDNAME=
dddddddd
,TABLE=
t
──────────────────────────────────────────►◄
 
Command
 
  •  
    FILEOUT
    Invokes the function to define output data sets.
 
Required Keywords
 
  •  
    DDNAME=
    Specifies the name of the first/next extract output file.
    Each table specified in a FILEOUT must be found in the control records for the input backup file. If any of the specified tables are not found in the control records for the input backup file, a message in the report indicates the invalid table name, and the utility terminates as a failure.
    A DDNAME is not acceptable
     
    for sequential input or output files if it is a name reserved for a 
    Datacom
     area. Names with the following patterns are therefore not acceptable for DDNAME=:
  • 3-byte names that end with XX, meaning they are reserved as either current or future 
    Datacom
     control areas.
  • 6-byte names that end with what could be a database ID from 001 through 999.
  • 7-byte names that end with what could be a database ID from 1000 through 9999.
    The DDNAME= value is verified for acceptability to protect you from unintentionally causing data corruption. The DDNAME check is the default but optional. You can prevent the DDNAME check by using a DBSIDPR parameter (DBUTLTY_EDIT_DATA_SET=) for individual MUF environments. However, we recommend that you allow the DDNAME check.
    The data corruption risk involves not the DDNAME itself but the content of the data set. For example, suppose that you used the CXX DDNAME as the output of a backup. You then copied the CXX DD statement and changed the DDNAME of the copy to be acceptable, avoiding the DDNAME= error. The backup would, however, then overlay the CXX data set, which is not the intent of a backup.
    If you specify an unacceptable name for DDNAME=, message DB10059E is generated. 
     We recommend that you allow DDNAME= check protection. You can, however, disable DDNAME= protection. To disable protection, assemble the DBSIDPR module used for this 
    Datacom
     environment and specify NONE for the DBUTLTY_EDIT_DATA_SET= parameter. The default is DBUTLTY_EDIT_DATA_SET=FULL_1, which allows DDNAME= protection.
  •  
    ,TABLE=
    Specifies the name of an individual table from which to define the output data set.
    Each table specified in a FILEOUT must be found in the control records for the input backup file. If any of the specified tables are not found in the control records for the input backup file, a message in the report indicates the invalid table name, and the utility terminates as a failure.
    •  
      Valid Entries:
      DATACOM-NAME of the table
    •  
      Default Value:
      (No default)
FILEOUT Examples
For sample JCL showing the use of the FILEOUT statement in the EXTBKUP function, see EXTBKUP (Extract from Backup File) 
For a sample EXTBKUP report showing the use of the FILEOUT statement, see Sample Report: EXTBKUP.