o The First and Last qualifiers have been added to make dumping portions of the .aij file easier. The Start and End qualifiers were intended to provide similar functionality, but are difficult to use because you seldom know, nor can you determine, the AIJ record number prior to issuing the command. o Be careful when searching for TSNs or TIDs as they are not ordered in the AIJ journal. For example, if you want to search for a specific TSN, use the Only qualifier and not the First and Last qualifiers. For example, assume the AIJ journal contains records for TSN 150, 170, and 160 (in that order). If you specify the First=TSN=160 and Last=TSN=160 qualifiers, nothing will be dumped because TSN 170 will match the Last=TSN=160 criteria. o To use the RMU Dump After_Journal command for an .aij file, you must have the RMU$DUMP privilege in the root file access control list (ACL) for the database or the OpenVMS SYSPRV or BYPASS privilege. o You receive a file access error message regarding the database's .aij file if you issue the RMU Dump After_Journal command with the active .aij file when there are active processes updating the database. To avoid the file access error message, use the RMU Close command to close the database (which stops entries to the .aij file), then issue the RMU Dump After_Journal command. o See the Oracle Rdb Guide to Database Maintenance for information on the steps Oracle RMU follows for tape label checking when you execute an RMU Dump After_Journal command using magnetic tapes. o Use of the wrong value for the Format qualifier typically results in a failure, but sometimes may produce unintelligible results. o The RMU Dump After_Journal command does not validate the file being dumped. If the file is not an .aij file or a backup of an .aij file, the RMU Dump After_Journal command produces unintelligible output.