pdlogadpf (Allocate log file)

The pdlogadpf command allocates during HiRDB operation a physical file to a file group specified in the HiRDB system definition. The physical file must have been created with the pdloginit command before the pdlogadpf command is executed.

Once the pdlogadpf command is executed, the file group becomes available to the active HiRDB system when it is opened by the pdlogopen command.

(2) Executor

(3) Format

(a) HiRDB single server configuration

 
 pdlogadpf -d spd [-s server-name] -g file-group-name
           -a primary-physical-file-name [-b secondary-physical-file-name]

(b) HiRDB parallel server configuration

 
 pdlogadpf -d spd -s server-name -g file-group-name
           -a primary-physical-file-name [-b secondary-physical-file-name]

(4) Options

(a) -d spd

Specifies that a physical file is to be allocated as a synchronization point dump file.

(b) -s server-name ~<identifier> ((1-8))

Specifies the name of the server corresponding to the file group.

(c) -g file-group-name ~<identifier> ((1-8))

Specifies the name of the file group to which the physical file is to be allocated. This file group name must have been specified in a single server definition, front-end server definition, back-end server definition, or dictionary server definition.

(d) -a primary-physical-file-name ~<pathname> ((up to 167 characters))

Specifies the absolute path name of the primary physical file that is to be allocated to the file group. Specify the physical file name in the format HiRDB-file-system-area-name/HiRDB-file-name.

(e) -b secondary-physical-file-name ~<pathname> ((up to 167 characters))

Specifies the absolute path name of the secondary physical file that is to be allocated to the file group. Specify the physical file name in the format HiRDB-file-system-area-name/HiRDB-file-name.

This option is required when dual synchronization point dump files are used. If dual synchronization point dump files are not used, specifying this option will result in an error.

If you use dual synchronization point dump files and specify both the -a and the -b options, and if an allocation error occurs on either the primary or secondary file, a command error results.

(5) Rules

(6) Notes

Executing the pdlogadpf command for a file group to which a physical file has already been allocated results in an error.
The result of the pdlogadpf command can be determined from the command's return code, an error message (if any), or the message log. Return code 0 for this command indicates normal termination, 4 indicates abnormal termination, and 8 indicates abnormal termination (such as invalid option or rsh error).
If you use Real Time SAN Replication based on the log-only synchronous method, the synchronization point dump file to be allocated depends on the site where the command is executed:
- At the transaction execution site
  The synchronization point dump file for transaction processing is allocated. The synchronization point dump file for log application processing cannot be allocated.
- At the log application site
  The synchronization point dump file for log application processing is allocated. The synchronization point dump file for transaction processing cannot be allocated.

(7) Examples

Allocate a physical file to a file group specified in the system definition.

Name of file group
spdfgf15
Name of physical file
```
/svr01/spdf15
```

HiRDB single server configuration

 
 pdlogadpf -d spd                                    1
           -g spdfgf15                               2
           -a /svr01/spdf15                          3

Explanation

Type of log file: spd (synchronization point dump file)
Name of file group: spdfgf15
Name of physical file: /svr01/spdf15

HiRDB parallel server configuration

 
 pdlogadpf -d spd                                    1
           -s bes1                                   2
           -g spdfgf15                               3
           -a /svr01/spdf15                          4