2.13 pdcat [-d sts specified]

Organization of this section
(1) Function
(2) Executor
(3) Format
(4) Options
(5) Rules
(6) Output format

(1) Function

Outputs status file contents to the standard output.

(2) Executor

Any user (with or without privileges)

(3) Format

(a) Unit status files

pdcat -d sts [{-x host-name| -u unit-identifier}]
      -f physical-filename [-v][-e]

(b) Server status files

pdcat -d sts -s server-name -f physical-filename [-v][-e]

(4) Options

(a) {-x host-name | -u unit-identifier}

Specifies the identifier of the unit or the name of the host corresponding to the unit status file. If this option is omitted, the information for the entire HiRDB system is displayed.

-x host-name ~<identifier> ((1-32))
Specifies the name of the host corresponding to the unit status file.
-u unit-identifier ~<identifier> ((4 characters))
Specifies the identifier of the unit corresponding to the unit status file.
(b) -s server-name ~<identifier> ((1-8))

Specifies the server name corresponding to the server status file. Even though there is only one HiRDB server in a HiRDB single server configuration, it must be specified in order to identify the object of server status file operations.

(c) -f physical-filename ~<pathname> ((up to 167 characters))

Specifies the absolute pathname of the physical file. A physical file name must be specified as HiRDB-file-system-area-name/HiRDB-file-name.

In the case of a HiRDB that uses Real Time SAN Replication based on the log-only synchronous method, either the status file for transaction processing or the status file for log application processing can be specified. Note that the volume containing the physical file must be readable.

(d) -v

Specifies that the following items concerning the status file are to be checked:

If checking detects an error, an error message is output after the contents of the specified status file have been displayed.

If this option is omitted, status file checking is not performed.

(e) -e

Specifies that the status file is to be opened in the lock mode. If the pdcat command is executed with this option specified at the time the unit or server is being started, HiRDB may terminate abnormally due to a lock error.

When this option is omitted, the status file is not opened in the lock mode, and the correct status may not be displayed if the specified status file is being used by the HiRDB.

(5) Rules

  1. The pdcat command can be executed at any time, whether or not HiRDB is active. However, it cannot be executed during HiRDB startup or termination processing.
  2. The pdcat command can be executed from any server machine except one that contains a utility special unit.

(6) Output format

Path name:aa...a
 Initial_time Current_time  R_le  R_co   factor Available Manage  Assign-Seq
 bb...b       cc...c        ddddd ee...e fff%   gg...g    hh...h  ii...i

Explanation
aa...a
Name of the physical file (up to 63 digits)
bb...b
Initialization date and time (in the format year/month/date hour:minute:second)
cc...c
Current date and time (in the format year/month/date hour:minute:second)
If not being used as the current file --/--/-- --:--:-- is displayed.
ddddd
Record length (decimal)
ee...e
Records count (decimal)
fff
Record utilization in the file (%)
gg...g
Number of contiguous free records in the file (decimal)
hh...h
Number of management records in the file (decimal)
ii...i:
Internal information used by the system (decimal)

The information displayed for a file that has been corrupted or in which an error has occurred may not be correct.