This subsection provides important information about updating to the HiRDB update version.

• Global buffers allocated using the database structure modification utility (pdmod) become invalid. The global buffers must be reallocated after the update is completed.
• The count startup point of the pd_spool_cleanup_interval operand is reset at the time of the update.
• If the pd_spool_cleanup operand is set to normal or force, any troubleshooting information output from completion of the update is deleted.
• If the pdstbegin command or the pdstend command is to be used to set collection conditions for statistical information to values different from the settings of the pd_statistics operand or the pdstbegin operand, use the following method:
  
  • If statistical information was collected with the pdstbegin command in an environment that was activated without setting the pd_statistics operand or the pdstbegin operand, statistical information will not be collected after the update. In such a case, the pdstbegin command will have to be re-executed.
  • If statistical information collection was terminated with the pdstend command in an environment that was activated where the pd_statistics operand was specified as Y or where the pdstbegin operand was specified, or if the pdstbegin command was executed to change the type of statistical information to be collected, the collection of statistical information after the update will be as specified in the system common definition. Therefore, the pdstend command and the pdstbegin command must be re-executed.
• Because the list used in any narrowed search will disappear, such a list must be re-created with the ASSIGN LIST statement after the update.
• Because the number of resident processes altered by the pdchprc command returns to the number of processes specified by the HiRDB system definition, the pdchprc command must be re-executed after the update.
• The system log file is replaced during updating to the HiRDB update version. Before updating, check that there are swappable system log files. If system log files are needed, perform the following:
  
  • If there are no swappable system log files
    If there are files in unload wait status, unload them. If there are no files in unload wait status, use the pdchgconf system reconfiguration command to add swappable log files. For details about the system reconfiguration command, see the manual HiRDB Version 8 System Operation Guide.
    If the update is performed when there are no swappable system log files, you must terminate HiRDB with the Psjnf07 or Psjn381 code once the KFPS01256-E message has been output. In such a case, prepare swappable files, and then use the pdstart command to start HiRDB.
    
  • If there is only one swappable system log file
    It is possible to update to the HiRDB update version in such a case, although the KFPS01224-I message will be output during the update to indicate that there are no log files. After the update, prepare swappable system log files.
    
• The message log file is replaced during updating to the HiRDB update version. However, the KFPS01910-I message notifying you that the message log file has been replaced is not output. If you want to save the messages in the message log file, back up the file prior to updating.
• When updating to the HiRDB update version, the service of the updating HiRDB and the Microsoft Cluster Server (MSCS) resource are terminated temporarily or are taken offline.