FIX ARCHIVE

The FIX ARCHIVE utility rewrites a tape journal file. Typically, you rewrite a tape journal file in use at the time of an abnormal system shutdown to make the file usable by the ROLLBACK utility.
idmscu19
The FIX ARCHIVE utility rewrites a tape journal file. Typically, you rewrite a tape journal file in use at the time of an abnormal system shutdown to make the file usable by the ROLLBACK utility.
This article describes the following information:
2
2
Authorization
To
You need this privilege
On
Rewrite a tape journal file
USE
The DMCL
Syntax
  ►►── FIX ARCHIVE ─┬───────────────────────┬───────────────────────────────────►◄                   └─ REPORT ─┬─ FULL ◄────┤                              ├─ TERSE ────┤                              └─ SUMMARY ──┘  
Parameters
  • REPORT
    Specifies the amount of detail that is to appear on the report.
  • FULL
    Specifies that all details are to be reported. This includes for every transaction: checkpoints, database statistics, and area usage. All details of a distributed transaction record are reported. This includes local transaction ids with program names; external transaction ids, and resource manager interests. Additionally, transactions active at the end of the process are listed and the time of the last global quiesce point is identified. FULL is the default if no REPORT option is specified.
  • TERSE
    Indicates that only transaction checkpoints and summary information is produced. For distributed transaction records: external transaction ids, and resource manager interests are not included in the report.
  • SUMMARY
    Indicates that only final summary information is produced.
Usage
How to submit the FIX ARCHIVE statement
You submit the FIX ARCHIVE statement to CA IDMS/DB only through the batch command facility. You must run the batch command facility in local mode.
How CA IDMS/DB rewrites a tape journal file
When rewriting a tape journal file, CA IDMS/DB:
  • Writes an end-of-file marker on the output tape
  • Writes ABRT checkpoints for all run units active at the time of the abnormal termination
  • Prints checkpoints and program statistics for run units whose activity is recorded in the journal file
  • Identifies quiesce points for use in a rollback or rollforward operation
  • Writes additional checkpoint records to the output tape
    • For incomplete distributed transactions whose state is InDoubt at the time of the abnormal termination, additional distributed and local checkpoint records will be written to the output file to complete the transaction if a matching section recovery control input file entry is provided.
    • For local (that is, non-distributed) transactions still active at the time of the abnormal termination, an ABRT checkpoint record will be added to the output file.
Multivolume journal files
The FIX ARCHIVE statement must process all unarchived volumes of a tape journal file in a single run.
Archived journal files
In most cases, you do not have to run the FIX ARCHIVE utility statement against archived journal files. Here are some exceptions:
  • To identify incomplete distributed transactions whose state is InDoubt at the end of the input file. (PRINT JOURNAL can also be used for this purpose.)
  • To complete transactions by writing additional checkpoint records to the output file.
    • For incomplete distributed transactions whose state is InDoubt at the end of the input file, additional distributed and local checkpoint records will be written to the output file if a matching section recovery control input file entry is provided.
    • For local (that is, non-distributed) transactions still active at the time of the abnormal termination, an ABRT checkpoint record will be written.
  • To merge multiple journal tapes onto one tape for certain rollback and rollforward operations that require multiple journal tapes to be one contiguous file
FIX ARCHIVE and Distributed Transactions
FIX ARCHIVE reports on distributed transactions and supports the use of input and output section recovery control files. The input section recovery control file is used to complete InDoubt distributed transactions. If an output section recovery control file is included in the JCL, an entry will be written for each incomplete distributed transaction encountered. For more information, see JCL Considerations and the "Common Facilities for Distributed Transactions" section.
For considerations associated with distributed transactions during recovery operations, see the
CA IDMS Database Administration Section
.
JCL Considerations
When you submit a FIX ARCHIVE statement to CA IDMS/DB through the batch command facility, the JCL to execute the facility must include statements to define:
  • The tape journal file to be rewritten, which is on SYS001
  • The rewritten tape journal file, which is on SYS002
To use a section recovery input control file, include a CTRLIN file definition or DD statement in the IDMSBCF execution JCL. To use a section recovery output control file, include a CTRLOUT file definition or DD statement in the IDMSBCF execution JCL. The format of both of these files is fixed block with a record length of 80.
For more information about the generic JCL used to execute the batch command facility, see the section for your operating system in this section.
Examples
The following statement directs the FIX ARCHIVE statement to rewrite a tape journal file.
fix archive;
Sample Output
When the FIX ARCHIVE utility runs successfully, the following listing is produced:
 IDMSBCF                                              IDMS Batch Command Facility                            mm/dd/yy   PAGE 1     FIX ARCHIVE;   RU_ID         1  PGM_ID  EMPLOAD   QUIESECE LEVELS  1  UPD  0   BGIN  yyyy-mm-dd-hh.mm.ss.ffffff   RU_ID         1  PGM_ID  EMPLOAD   QUIESECE LEVELS  0  UPD  0   ENDJ  yyyy-mm-dd-hh.mm.ss.ffffff    STATISTICS  FOR  EMPLOAD      RU_ID         1     PAGES READ               969    PAGES WRITTEN            847    PAGES REQUESTED         2567    CALC TARGET           186     CALC OVERFLOW              0    VIA TARGET               439    VIA OVERFLOW               0    LINES REQUESTED      6042     RECS CURRENT            1307    CALLS TO IDMS           1461    FRAGMENTS STORED           0    RECS LOCATED            0     LOCKS REQUESTED            0    SELECT LOCKS               0    UPDATE LOCKS               0     START TIME: 1999-09-18-15.52.35.481748  TIME OF LAST COMMIT: NONE                        NUMBER OF COMMITS:        0                                                               SINCE LAST COMMIT     TABLESPACES OPENED                BEFORE       AFTER      BEFORE       AFTER        USAGE MODE     EMPDEMO.ORG-DEMO-REGION              825         825         825         825    SHARED UPDATE     EMPDEMO.INS-DEMO-REGION              115         115         115         115    SHARED UPDATE     EMPDEMO.EMP-DEMO-REGION             1314        1314        1314        1314    SHARED UPDATE     BLOCK COUNT      702  RECORD COUNT     5512     DATABASE IN QUIESCE AT END OF FILE     DATABASE IN UPDATE QUIESCE AT END OF FILE     ACTIVE PROGRAMS AT STOP TIME WERE:     NONE     DATA BASE MAY NOT NEED TO BE RECOVERED  Status = 0  AutoCommit will COMMIT transaction  Command Facility ended with no errors or warnings
For more information about journaling, see the
CA IDMS Database Administration Section
.