File modes usable by utilities

All HiRDB utilities use regular files as I/O files unless otherwise specified; the file mode is single-file, single-volume

Some utilities can handle file modes other than single-file, single-volume. The table below lists the utilities that can handle I/O files other than single-file, single-volume regular files.

Table 1-3 Utilities that can handle I/O files other than single-file, single-volume regular files

Utility	File type	Single-file, multi-volume regular files	Tape device^#1	EasyMT		HiRDB files
Utility	File type	Single-file, multi-volume regular files	Tape device^#1	Single-files	Multi-files	HiRDB files
Database load utility (pdload)	Input data files, LOB input files, LOB input files by column	C^#2	V	C^#3 -f easymt	C^#3 -f easymt	N
Database reorganization utility (pdrorg)	Unload data files, LOB data unload files		C	C^#3 -f easymt	C^#3 -f easymt	C -f hirdb
Database copy utility (pdcopy)	Backup files			C -k m or -k e^#3	N	C -k i
Database recovery utility (pdrstr)	Backup files			C -k m or -k e^#3	N	C -k i
Dictionary import/export utility (pdexp)	Export files	N		N	N	N

Legend:

C:: The files can be used. If a specification on the command line is required, the option is also shown; in such a case, all file-specific information must be specified in addition to the command options. For details about the options, see the explanations of the commands.

V:: Variable-length blocked mode can be used; DAT format can be used in the fixed-length blocked mode (extended DAT format is not supported). The binary format cannot be used. For details, see Appendix E. Creation of Input Data Files for the Database Load Utility.

N:: Not supported.

#1: In the Linux edition, pdload, pdcopy, pdrstr, and pdrorg do not support fixed-length blocked tape.

#2: NFS files cannot be used when multiple files are to be output with the pdrorg or pdcopy command as regular files, or in the single-file, multi-volume mode. In the case of output with the pdrorg or pdcopy command to regular files, or in the single-file, multi-volume mode, files in a file system for which the size of each volume does not exceed 2 gigabytes must be specified.

#3

If MTguide has been installed and is usable, it is used for volume management for single volumes only. If volumes are not managed by MTguide, the following must be specified:

pdload or pdrorg: Specify mtguide nouse in the control information file.
pdcopy or pdrstr: Specify -k e on the command line

Organization of this subsection: (1) Tape devices; (2) EasyMT and MTguide; (3) HiRDB files

(1) Tape devices

The table below lists the tape devices supported by the utilities.

Table 1-4 Tape devices supported by the utilities

Device name	Direct input/output by the utilities
CMT	N
DAT	Y
OMT	N
CGMT	N
8mm	Y
DLT	Y
LTO	Y

Legend:: Y: Can be used.; N: Cannot be used.

Note: If you use EasyMT, see the manual EasyMT for details about the supported tape devices.

When the utilities access the tape device for direct input/output, they assume a single volume and access the device as a single tape drive. They do not provide Autoloader or Tape Library control.

We recommend that you use the tape device in the variable-length blocked mode.

You can reduce the number of input/output operations in the variable-length blocked mode, in which the utilities input/output data in units of 32 kilobytes while they input/output data in units of 512 bytes in the fixed-length blocked mode. When using the fixed-length blocked mode, make sure that the block size is 512 bytes.

For details about each tape device, see the applicable OS manual.

If you use a tape device with pdrorg, pdload, or pdrstr, do not specify the device driver's minor number in such a manner that the tape will not be rewound during close processing. If you execute the utility without rewinding the tape, you must rewind the tape using a command such as mt (magnetic tape manipulation program) after the utility has terminated.

To save multiple backups on the same medium, use the utility to output the backups to files and then copy them onto the desired medium by using a command such as tar.

(2) EasyMT and MTguide

When the EasyMT program product is installed and the appropriate option shown in Table 1-3 Utilities that can handle I/O files other than single-file, single-volume regular files is specified, labeled magnetic tapes can be handled by a variable-length blocked mode tape device. Tapes created by the HITAC M Series can also be handled.

By combining EasyMT with HiRDB utilities, tape devices can be handled in the following modes (single-volume support):

Single-file, single-volume
Multi-file, single-volume

See the following manuals for details about EasyMT and MTguide:

EasyMT
Magnetic Tape Operation Support: JP1/Magnetic Tape Access or Magnetic Tape Basic Access Method: EasyMT
MTguide
Magnetic Tape Mount Management: JP1/Magnetic Tape Library

(3) HiRDB files

HiRDB utilities cannot handle directly the character special files of hard disk devices as I/O files, but are able to handle them by making them into HiRDB file system areas.

Even a regular file can be handled as a HiRDB file if it is initialized as a HiRDB file system.

To use a HiRDB file as an I/O file, a HiRDB file system must first be created with the pdfmkfs command in which -k UTL is specified, and the appropriate option shown in Table 1-3 Utilities that can handle I/O files other than single-file, single-volume regular files must be specified when the HiRDB utility is executed.

HiRDB utilities use HiRDB files in the following modes:

Single-file, single-volume
Single-file, multi-volume

For details about HiRDB files, see the HiRDB Version 9 Installation and Design Guide.

1.4.2 File modes usable by utilities

(1) Tape devices

(2) EasyMT and MTguide

(3) HiRDB files