The table below shows the action to take in response to each cause of a system log file shortage. If there are multiple causes, take action to eliminate all of them.

Table 20-22 Action to take in response to each cause of a system log file shortage

No.	Cause of system log file shortage	Action
1	Because the automatic log unloading facility stopped, the number of files waiting to be unloaded increased, causing a system log file shortage.	The KFPS01150-E message is output. Take the action prescribed in this message to eliminate the factor that caused the automatic log unloading facility to stop. Also see 3.8.5 Error handling.
2	Because system log files were not unloaded or their status was not changed, the number of files waiting to be unloaded increased, causing a system log file shortage.	Unload the system log files that are waiting to be unloaded. For details about how to perform this operation, see 20.17.5 Changing a system log file to unloaded status.
3	Because the system log extraction process fell behind during linkage with HiRDB Datareplicator, the number of files in extracting status increased, causing a system log file shortage.	For details about the action to take, see 20.17.9 Action to take when there are system log files that are in extracting status.
4	Because transactions were not committed for a long time, the number of files that are overwrite disabled increased, causing a system log file shortage.	Take action by performing the following steps: Determine the number of records necessary for unit restart. For details, see 20.17.6 Determining the number of records necessary for unit restart. Add at least the number of system log files determined in step 1. For details, see 20.17.7 Adding system log files.
5	Because synchronization point dump validation processing was skipped, the number of files that are overwrite disabled increased, causing a system log file shortage.
6	During updatable online reorganization, the number of files in the overwriting denied status for online reorganization increased, causing a system log file shortage.
7	Because an error occurred in a system log file, there was no file that could be made a swappable target, and this caused a system log file shortage.

Perform the tasks explained here only after you have taken the action described in steps 1 through 3 in Table 20-22 Action to take in response to each cause of a system log file shortage.

Check whether the system log file capacity required for unit restart is available. The checking method follows.

Procedure

1. Execute the pdlogls -d sys -e command to check whether swappable system log files are available.
   If you have taken the action under No. 1 (the action to take when the automatic log unloading facility stops) in Table 20-22 Action to take in response to each cause of a system log file shortage, the automatic log unloading facility runs during unit restart and unloads the system log files, and therefore you can consider all system log files to have been unloaded.
   
2. Total the number of records in the swappable system log files. Refer to the execution result of the pdlogls -d sys -e command and total the value (system log file record count) on the right side of Record count for all swappable system log files.
3. See 20.17.6 Determining the number of records necessary for unit restart and calculate the number of records that are required for unit restart.

Compare the record counts obtained in steps 2 and 3 above, and if the following conditional expression is satisfied, proceed to (3) below.

• Number of records in swappable system log files (the record count determined in step 2) Number of records that are required for unit restart (the record count determined in step 3)

If the above conditional expression is not satisfied, add system log files in which the number of additional records needed is defined. For details about how to add system log files, see 20.17.7 Adding system log files.

Execute the pdstart command to restart the unit.

After the unit restarts, transactions can be accepted. However, the system logs that are output by processing of new transactions might cause a system log file shortage again. Therefore, resume the job only after the operation in step (5) is completed.

Confirm that synchronization point validation processing is complete. For details about the confirmation procedure, see 20.17.1(6) Confirm that the synchronization point validation process has completed.

If the number of system log files is insufficient during a restart, the unit will terminate abnormally again before the validation process for the synchronization point dump completes. In this case, take the action described in the error message that is output to syslogfile or the message log file. If the system log file shortage still has not been resolved, see 20.17.3 Unit-restarting procedure (restarting the unit after identifying the cause) and identify the cause.

Take the following steps before resuming the job:

• Check whether there are a sufficient number of swappable system log files.
  Execute the pdlogls command to determine the number of swappable system log files. Make sure at least 2/3 of the total files are available. If the number is not sufficient, increase the number of swappable system log files by taking an action such as unloading system log files.
  
• Check whether the automatic log unloading facility is running.
  If the automatic log unloading facility is being used, execute the pdlogatul -d sys -i command to check whether this facility is running.
  If the automatic log unloading facility is stopped, check the KFPS01150-E message, which is output after unit restart, and take the action prescribed in the message. Then, execute the pdlogatul -d sys -b command to restart the automatic log unloading facility.
  
• Acquire backup information and log point information.
  If operation without unloading system log is being used, use the pdcopy command to back up all RDAREAs within the server. When doing so, specify the -z option to collect the log point information file.
  After making a backup, execute the pdlogchg -z command to change the system log file status to unloaded status.
  

After you have eliminated the system log file shortage, take the actions described in 20.17.10 Actions to take after eliminating the system log file shortage.