A list is not deleted even after the UAP is disconnected from the HiRDB system. To delete a list, either use the DROP LIST statement or stop the HiRDB system to delete all lists.

In a search that uses a list, rows that were present in the list when the list was created but then later deleted are not searched. If a row is updated after the list is created, the updated data is fetched.

In a search that uses a list, rows that were inserted after the list was created and after rows in the base table were deleted are sometimes searched.

If the ASSIGN LIST statement is executed for a row partitioned table and the table cannot be searched because of shutdown of some of the RDAREAs in the base table, an error occurs even if the data of an RDAREA that can be searched is specified in a search condition for a partitioned column.

The same user cannot connect to multiple HiRDB systems simultaneously and operate a list.

With a HiRDB/Parallel Server, if the dictionary server or the unit that contains the dictionary server is stopped, the list management information is lost. As a result, operations (search, deletion, and update) become disabled for all lists that were created up to that point. (An error occurs if a list is operated.) To use a list that triggered an error when operated, use the ASSIGN LIST statement to create a new list that has the same list name as the previous list.

If the dictionary server is restarted, the KFPA11998-E error (list operation while transaction is undetermined) may be displayed for processes that use a list. This error may be displayed until recovery is completed for all list-using transactions of other users that were started before the server was stopped.

If a log is used to recover a list base table to its latest status, the lists that were created can be used without modification. However, for a recovery that uses only a backup, a time-specification recovery that uses a log, or a recovery that does not use the latest log, use one of the following methods to delete or re-create all lists that were based on the recovered table:

If you want to use the lists:

Use the ASSIGN LIST statement to create lists that have the same list names as the previous lists.

If you do not want to use the lists:

Use the DROP LIST statement to delete the lists, or terminate and restart HiRDB to delete all created lists.

Use one of the following methods to delete or re-create all lists that are based on a list stored in a reinitialized RDAREA:

If you want to use the lists:

Use the ASSIGN LIST statement to create lists that have the same list names as the previous lists.

If you do not want to use the lists:

Use the DROP LIST statement to delete the lists, or terminate and restart HiRDB to delete all created lists.

Executing reorganization, creation mode download, or the PURGE TABLE statement on a list base table invalidates previously obtained search results for lists that were created based on that table. To use the lists, you must use the ASSIGN LIST statement to re-create the lists.

When you use the inner replica facility and also use the pddbchg command or PDDBACCS in the client environment definitions to switch the RDAREA to be accessed, the search results become invalid unless one of the following conditions is satisfied:

• The RDAREA to be accessed during list retrieval matches the RDAREA to be accessed during list creation.
• The RDAREA to be accessed during list retrieval contains data that was copied from the RDAREA to be accessed during list creation.

To use a list, perform one of the following:

• Use the RDAREA to be accessed during list creation.
• Use the access-target RDAREA to which data was copied from the RDAREA to be accessed during list creation.
• Re-create the list in the RDAREA that is currently being accessed.