Running FILEDATA with a Request to Access Headers from a Library Maintenance Tape

If you run FILEDATA with a request to report disk file header attributes, then by default FILEDATA accesses the disk file headers of files on the tape. The TAPE modifier causes the full library tape to be read when used with the following requests:

  • ATTRIBUTES

  • CODEFILEINFO

  • COMPATIBILITY

  • HEADERCONTENTS

  • INCOMPATIBILITY

    The TAPE modifier causes FILEDATA to access only the directory of a library maintenance tape when used with the following requests:

  • FILENAMES

  • COPYDECK

  • NOREPORTS

An additional modifier, TAPEHEADERS, can be used to enable FILENAMES, COPYDECK, and NOREPORTS to access the full library maintenance tape. The TAPEHEADERS modifier causes a complete database to be created and displays all fields in the FILENAMES report. TAPEHEADERS also can be used with requests that require disk file header attributes.

When FILEDATA calls library maintenance to read the full tape or CD-ROM, library maintenance can issue error messages. These messages do not appear in the report that FILEDATA prints but can be found in the job summary.

When the full library maintenance tape is read, FILEDATA uses the DIRECTORY or TITLE modifier to select files. The DIRECTORY or TITLE modifier is specified using library maintenance syntax. When no DIRECTORY or TITLE modifier is specified, the default is an equal sign (=). If FILEDATA is run under a privileged usercode, ‘‘*='' must be specified to see all files on a tape.

Only files that can be copied under the user's security are accessed by FILEDATA. A directory is written to the library maintenance tape before files are written to the tape. As a result, files can appear in the library maintenance directory but not be on the tape. When the full tape is accessed, files are reported only if they are on the tape and in the order they were copied. Refer to the Work Flow Language (WFL) Programming Reference Manual for more information on how library maintenance selects files when you copy files from tape.

Examples

The following commands produce file information on all the files on the library maintenance tape DEMOTAPE if one the following conditions applies to the program:

  • It is being run under a privileged usercode (specify the directory using ‘‘*='')

    RUN *SYSTEM/FILEDATA("ATTRIBUTES: DIR = *= 
                         TAPE=DEMOTAPE ALTERDATE CREATIONDATE")
  • It is being run from an ODT

RUN *SYSTEM/FILEDATA("DEFINEOUTPUT:MEDIATYPE=SPO; 
                     ATTRIBUTES:TAPE=DEMOTAPE ALTERDATE CREATIONDATE")

The following example shows how any user running under a usercode, privileged or not, can obtain file information about his files on a library maintenance tape.

RUN *SYSTEM/FILEDATA("ATTRIBUTES: TAPE=DEMOTAPE ALTERDATE
                     CREATIONDATE")