PRINT JOURNAL

The PRINT JOURNAL utility reports on transaction checkpoints in an archive journal file.
idmscu19
The PRINT JOURNAL utility reports on transaction checkpoints in an archive journal file.
The following topics are discussed on this page:
2
2
Authorization
To
You need this privilege
On
Report on checkpoints for a journal file
USE
The DMCL associated with the journal file
Syntax
  ►►─── PRINT JOURNAL ──────────────────────────────────────────────────────────►  ►─┬─────────┬────────────────────────────────────────────────────────────────►    └─ UTC────┘  ►─┬──────────────────────────────────┬───────────────────────────────────────►    └─ START AT ' ─┬─ date ──────┬─ ' ─┘                   ├─ date-time ─┤                   └─ time ──────┘    ►─┬─────────────────────────────────┬────────────────────────────────────────►    └─ STOP AT ' ─┬─ date ──────┬─ ' ─┘                  ├─ date-time ─┤                  └─ time ──────┘  ►──┬──────────────────────┬──────────────────────────────────────────────────►◄     └─ REPORT ─┬─ FULL ◄───┤                ├─ TERSE ───┤                └─ SUMMARY ─┘  
Parameters
  • START AT
    Directs the PRINT JOURNAL utility to report only on checkpoints written for transactions that started on or after the indicated date and time.
    By default, if you do not specify a start date or date and time, processing begins with the first checkpoint written in the archive journal file.
  • STOP AT
    Directs the PRINT JOURNAL utility to report on checkpoints written only for transactions that started on or before the indicated date and time.
    By default, if you do not specify a stop date or date and time, processing ends with the last checkpoint written to the archive journal file.
  • date
    Specifies the date, in one of the following formats:
    • yyyy-mm-dd
    • mm/dd/yyyy
    In these formats, the following rules apply:
    • yyyy
      specifies the year.
      yyyy
      must be an integer in the range 0001 through 9999. Leading zeros are optional.
    • mm
      specifies the month within the year.
      mm
      must be an integer in the range 01 through 12. Leading zeros are optional.
    • dd
      specifies the day within the month.
      dd
      must be an integer in the range 01 through 31. Leading zeros are optional.
    The combined values of
    yyyy
    ,
    mm
    , and
    dd
    must represent a valid date. For example, 1988-02-29 is a valid date. 1989-02-29 is not.
  • date-time
    Specifies the date and time, where:
    • The format for specifying the date and time are:
      yyyy-mm-dd-hh.mm.ss.ffffff
    • The rules for specifying the date component of DATE-TIME are the same as for the DATE option described previously. Rules for specifying the TIME component are:
      • Hh
        specifies the hour on a 24-hour clock.
        hh
        must be an integer in the range 00 through 23. Leading zeros are optional.
      • mm
        specifies the number of minutes past the hour.
        mm
        must be an integer in the range 00 through 59. Leading zeros are optional.
      • ss
        specifies the number of seconds past the minute.
        ss
        must be an integer in the range 00 through 59. Leading zeros are optional.
      • ffffff
        specifies the number of millionths of a second past the specified second.
        ffffff
        is optional; if you include it, it must be an integer in the range 000000 through 999999. The default value is 000000. Trailing zeros are optional.
  • time
    Specifies the time, in the following format:
    • hh:mm:ss
    The rules for specifying
    time
    are the same as those listed for DATE-TIME.
    When specifying
    time
    , the date defaults to the current date.
  • REPORT
    Specifies the amount of detail that is to appear on the report.
  • FULL
    Specifies that all details are to be reported. For every transaction, this includes 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.
  • UTC
    Specifies that Start and Stop times are interpreted as UTC times instead of local times.
Usage
How to submit the PRINT JOURNAL statement
You submit the PRINT JOURNAL statement only through the batch command facility. When submitting PRINT JOURNAL statements, you must run the batch command facility in local mode.
PRINT JOURNAL and Distributed Transactions
PRINT JOURNAL 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 PRINT JOURNAL statement to CA IDMS/DB through the batch command facility, the JCL to execute the facility must include statements to define the archive journal file.
To use a manual recovery input control file, include a CTRLIN file definition or DD statement in the IDMSBCF execution JCL. To use a manual 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.
Example
The following example directs the PRINT JOURNAL utility to report on all transaction checkpoints in the archive journal file beginning with the first checkpoint.
print journal;
Sample Output
The PRINT JOURNAL utility produces the following report.
 IDMSBCF                                              IDMS Batch Command Facility                            mm/dd/yy   PAGE 1     PRINT JOURNAL;   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: yyyy-mm-dd-hh.mm.ss.ffffff  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 and transaction checkpoints, see the
CA IDMS Database Administration Section
.