The pdlogatul command controls the automatic log unloading facility as follows:

• Restarting the automatic log unloading facility that was terminated during HiRDB operation
• Cancelling the automatic log unloading facility during execution
• Displaying the status of the automatic log unloading facility

For details about the automatic log unloading facility, see the HiRDB Version 9 System Operation Guide.

HiRDB administrator

(a) HiRDB single server configuration

 
 pdlogatul -d sys [-s server-name] [{-i | -b | -t[-w]}]
 

(b) HiRDB parallel server configuration

 
 pdlogatul -d sys -s server-name [{-i | -b | -t[-w]}]
 

(a) -d sys

Specifies that the system log files are to be manipulated.

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

Specifies the name of the server to be manipulated.

(c) -i

Specifies that the status of the automatic log unloading facility is to be displayed.

(d) -b

Specifies that the automatic log unloading facility is to be restarted.

(e) -t

Specifies that the automatic log unloading facility is to be cancelled.

(f) -w

If the -t option is specified to cancel the automatic log unloading facility, this option specifies that the command termination is to be delayed until the current log unloading process is completed. The -w option takes effect only when the -t option is specified. If you specify the -t option, but omit the -w option, the system cancels the automatic log unloading facility immediately after the pdlogatul command is executed, forcibly terminating the ongoing unloading process.

When this option is specified, completion of unloading process is delayed by about nine hours (32,768 seconds). If the unloading process is not completed within this period of time, the system cancels the automatic log unloading facility, in which case the unloading process will be terminated forcibly.

By specifying this option, you can eliminate the incomplete unload log files (which usually result from cancellation of the automatic log unloading facility) and input all the current unload log files with pdrstr.

1. You can execute the pdlogatul command while HiRDB is active. If you specify the -i or -t option, you can execute the command even during the HiRDB termination processing (during the execution of the pdstop command). If HiRDB was started by the pdstart -r command (including while HiRDB is under start or termination processing), the pdlogatul command cannot be executed regardless of whether the -i or -t option is specified.
   The following table shows when the -b, -t, and -t -w options can be specified, depending on the combination of the HiRDB status and the automatic log unloading facility status:
   

   No.	HiRDB status	Automatic log unloading facility status	Option
   			-b	-t	-t -w
   1	Active	ACTIVE	N	Y	Y
   2		STOP	Y	N	N
   3		STOP (E)	Y	Y	Y
   4		STOPPING	Y	Y	N
   5		--	N	N	N
   6	During stop processing	ACTIVE	N	Y	Y
   7		STOP	N	N	N
   8		STOP (E)	N	Y	Y
   9		STOPPING	N	Y	N
   10		--	N	N	N
   11	Other	All statuses	N	N	N

   Legend:

   Y: Can be specified.

   N: Cannot be specified.

   --: The automatic log unloading facility cannot be used.

2. Execute the pdlogatul command at the server machine containing the single server or the server machine where the system manager is located.
3. If there is a current log generation, its log file group information is output.
4. If the pdlogatul -t -w command terminates with return code 4, there may be an incomplete unload log file. In these cases, check the nature of the error on the basis of the output error message, take an appropriate action, and re-execute the pdlogatul -b command. Then, execute the pdlogatul -t -w command.

1. The following shows the pdlogatul command's return code:
   0: Normal termination
   4: One of the following:
   
   • If the -t and -w options were specified, the system forcibly terminated unloading process and cancelled the automatic log unloading facility because the unloading process was not completed within the waiting period (32,768 seconds).
   • If the -t and -w options were specified, the system cancelled the automatic log unloading facility while monitoring the completion of unloading process for one of the following reasons:
   • None of the directories for unload log files was available.
   • The name of the unload log file was duplicated.
   • There were not enough resources (such as a memory shortage or too many active processes).
   8: Command error
   

 
HOSTNAME : aa...a(bb...b)
SERVER_NAME : cc...c
AUTO_LOG_UNLOAD  NOW_UNLOAD_LOG_GROUP  CREATE_DIR
dd...d           ee...e                ff...f
CURRENT LOG GENERATION INFO.
LOG_GROUP  GEN_NO. SERVER_RUN_ID  RUN_ID  UNLOAD_FILE_NAME
gg...g     hh...h  ii...i         jj...j  kk...k
 

Explanation

aa...a

Host name

bb...b

The time pdlogatul was executed (in the format hour:minute:second)

cc...c

Server name

d

Status of the automatic log unloading facility:

ACTIVE: Active

STOP: Inactive

STOP (E): Stopped due to an error

STOPPING: Waiting for unloading process during termination

-: Automatic log unloading facility unavailable

ee...e

File group name for the system log file that is currently unloaded

If the automatic log unloading facility is not active, **** is displayed.

ff...f

Directory name for the unload log file in use

gg...g

File group name for the current generation of system log files

hh...h

Generation number of the current generation of system log

ii...i

Run ID of the current generation of server

jj...j

Run ID of the current generation of system log

kk...k

Name of the file created when the current generation of log was automatically unloaded