TOCPREVNEXTINDEX

Lund Performance Solutions


Report Modes

Overview

Intact Dynamic Rollback creates a report of its activities according to either default or user- defined specifications. Reports are created immediately after a program abort, if the program left databases open.
Reports might be delayed in the following instances:
  • If many transactions have to be rolled back to a DBOPEN.
  • If many single transactions occurred after the most recent DBBEGIN.
  • Ask yourself the following questions about Intact Dynamic Rollback reports:
  • Do you want the user whose program aborted to take any action?
  • For some databases and not others?
    How much information does the user need to see?
  • Do you want the operator to be informed of rollbacks?
  • Do you want to know about program aborts that invoke Intact Dynamic Rollback, but do not require rollout?
  • Do you want all rollback reports for a particular database listed in one file or multiple files?
  • The information provided in this chapter will help you set up Intact Dynamic Rollback reports.

    Report Modes

    Intact Dynamic Rollback offers four types of report modes:
  • Off (no report)
  • Terse
  • Regular
  • Detailed
  • Off (No Report)

    No report is produced when the Off mode is enabled. The destination specified with this report type will not receive any report.

    Terse Report

    A terse report simply notes that Intact Dynamic Rollback has been invoked and identifies the associated user and program. TERSE is the default report mode for both the console and the log file destinations. The following example reports that the user, MGR.PFIM, experienced an abort when running the program, PROGRAM.Dynamic RollbackEX.RGTNN. The current logon group for MGR.PFIM is PUB.


    INTACT invoked for MGR.PUB.PFIM in PROGRAM.Dynamic RollbackEX.RGTNN

    Regular Report

    A regular report contains information such as the name of the Rfile, the date and time of the abort, the user and the program, the logical device and the number of DBPUT’s DBDELETE’s and DBUPDATE’s rolled out.


    The following are examples of a regular report:

    Example 1

    INTACT A.01.02
    WED, SEPT 02, 1998 2:45 PM
    FILE INTREPT.INTACTRP.INTACT
    USER MGR.PUB.PFIM
    PROGRAM PRIUPDT.PGRM.PFIM
    STDIN 41
    DATA BASE ADMIND.PUB.PFIM
    Beginning Rollback DBBEGIN mode. Logfile: LOGFL.DAT.INTACT
    Dbputs 0
    Dbdeletes 1
    Dbupdates 1
    Ending Rollback Successfully
    This is the Base level message.
    This is the Global level message.
    DATA BASE MAILDB.PUB.PFIM
    Beginning Rollback DBBEGIN mode. Logfile: LOGFL.DAT.INTACT
    Dbputs 3
    Dbdeletes 0
    Dbupdates 0
    Ending Rollback Successfully
    This is the Global level message.
    END OF INTACT REPORT


    This report shows:
  • The user, MGR.PFIM experienced an abort at 2:45 in the afternoon.
  • The report was appended to the file, INTREPT, in the group, INTACTRP, of the account, INTACT.
  • The user was running the program, PRIUPDT.PRGM.PFIM on logical device 41 when the abort occurred.
  • The program accessed two databases and rollback was performed on each of them. One (1) DBDELETE and one (1) DBUPDATE were rolled back from the first database. Three (3) DBPUT’s were removed from the second database.
  • The global message was set to appear for both databases, but only the first database had a specific base level message assigned to it.
  • The rollout was successful from both databases.
  • Example 2

    INTACT A.01.02
    MON, AUG 31, 1998 10:22 PM
    FILE R0461022.INTGROUP.MANUF
    USER MGR.PUB.MANUF
    PROGRAM UPDAT.PGRM.MANUF
    STDIN 86
    DATA BASE ADMIND.PUB.PFIM
    No transaction in progress.
    Rollback not required.
    If report indicates rollback is needed, call Karen X345.
    END OF INTACT REPORT


    This report shows that the program abort did not affect the database at all. That is, no transaction was in progress at the time of the report and the database is consistent.
    This reporting option can be disabled (see "REINFORCE Command").

    Example 3

    INTACT A.01.02
    MON, AUG 31, 1998 10:22 PM
    FILE R0461022.INTGROUP.MANUF
    USER MGR.PUB.MANUF
    PROGRAM UPDAT.PGRM.MANUF
    STDIN 86
    DATA BASE ADMIND.PUB.PFIM
    Record has been modified.
    Rollback unable to complete.
    If report indicates rollback is needed, call Karen X345.
    END OF INTACT REPORT
    This information is reported when any irregular circumstances occur. An irregular circumstance might be two or more users modifying the same field without locking, or an application that is improperly locking or not locking at all. The incomplete transaction may have been only partially rolled out when the unusual situation occurred. It is a good idea to alert the system manager or the database administrator when this information is reported.

    Detailed Report

    A detailed report is a comprehensive list of the actual information rolled out of the database.
    The following is an example of a detailed report:


    INTACT A.01.02
    WED, SEPT 02, 1998 2:45 PM
    FILE R0301445.PUB.PFIM
    USER MGR.PUB.PFIM
    PROGRAM PRIUPDT.PGRM.PFIM
    STDIN 41
    DATA BASE ADMIND.PUB.PFIM
    Beginning Rollback DBBEGIN mode. Logfile: LOGFL.DAT.PFIM DBDELETE D-INVOICES (Detail), Mode 1, added back 1457 123998 Jan 31, 1998 Company ABC $1,450.50
    DBUPDATE D-INVOICES (Detail), Mode 1, reversed 1448 $1450.50 $1,550.50
    DBBEGIN
    Dbputs 0
    Dbdeletes 1
    Dbupdates 1
    Ending Rollback Successfully
    This is the Base level message.
    DATA BASE MAILDB.PUB.PFIM
    Beginning Rollback DBBEGIN mode. Logfile: LOGFL.DAT.PFIM DBPUT D-COMPANY (Detail), Mode 1, deleted 1322 Company XYZ 1200 Warne St Ottawa
    DBPUT M-REGION (Master), Mode 1, deleted 1316 ONT Ontario
    DBPUT M-REGION (Master), Mode 1, deleted 1308 CA California
    DBBEGIN
    Dbputs 3
    Dbdeletes 0
    Dbupdates 0
    Ending Rollback Successfully
    This is the Global level message.
    END OF INTACT REPORT


    This detailed report shows the same rollout as the regular report (page 18) with the following differences:
  • A separate Rfile, called R0301445.PUB.PFIM, was created to contain this report. This indicates that both of the databases listed have the default reporting destination (logon group and account), since the user was logged on as MGR.PUB.PFIM and since only one file was created.
  • The additional detail included in this report concerns the actual information rolled out of the database. For example, the first DBDELETE indicates an invoice number, 123998, followed by the date, Jan 31, 1998. Information in the Intact Dynamic Rollback report appears exactly as it was entered into the database. If the numbers were stored in a binary format, they will appear as “....” on the report.
  • The database, ADMIND.PUB.PFIM, has both a global message and a database level message. The database, MAILDB.PUB.PFIM, has only the global message.
  • Report Destinations

    Intact Dynamic Rollback can send reports of rollback activity to any of the following locations:
  • STDLIST of USER
  • Operator’s console
  • Disc file (Rfile)
  • Log file
  • STDLIST of USER

    After a program abort, the program user can receive a report on the user’s terminal indicating that Intact Dynamic Rollback was called. The default report lists the following information:
  • The Intact Dynamic Rollback version number
  • The name of the disc file created
  • The user logged on
  • The program name
  • The STDIN device
  • The name of the database
  • Messages regarding the status of the rollback and its success or failure
  • If a program within a job aborts, the report will be sent to the line printer which is the STDLIST device for all jobs.

    Operator’s Console

    The operator’s console also receives a report after a program abort. The default report, a terse report, consists of a single line indicating both the user and the program name. The report is created through TELLOP’s.

    Disc File (Rfile)

    After a program abort, Intact Dynamic Rollback creates a file on disc and begins the rollback. The default report file (a detailed report) shows the number of DBPUT’s, DBDELETE’s and DBUPDATE’s rolled out of the database and information regarding each.


    For instance, if a DBDELETE was rolled out, the detailed report file will identify the dataset and provide details about the transaction. If the database is enabled for rollback to DBOPEN and 500 transactions were completed, the report could be lengthy.
    Disc File Code
    The Intact Dynamic Rollback session Rfiles are easily identified, because they have a file code of 825. Each file has a record width of 132 bytes and can have a maximum of 10,000 records.


    NOTE Files set up for APPEND access in Intact Dynamic Rollback reporting do not need to have a file code of 825. The names of these files can be listed by executing the SHOW command


    Disc File Name
    The disc file name indicates the initialization of the report file in the format, Rdddhhmm, where “ddd” is the Julian day of the year, “hh” is the hour of the day in a 24-hour clock and “mm” is the minutes.


    For example, the file called “R0321320” would be a file created on February 1 at 1:20 in the afternoon. If two aborts occur in the same minute by the same user, the minute would be augmented by one (R0321321).

    Log File

    The default report sent to the log file is a terse report. It consists of one line, indicating only the user and the program name.

    Report Commands

    There are six INUTIL program commands used to set up the Intact Dynamic Rollback rollback reports:
  • BMESSAGE
  • GMESSAGE
  • REINFORCE
  • REPORT
  • Rfile
  • RMODE
  • INUTIL commands and others are explained in detail in Chapter 5, "Program Commands".

    Report Mode Defaults

    Default Report Modes for Auto Rollback and DBUNDO

    The default rollback mode report settings are listed in the following table:


    Auto Rollback Report
    DBUNDO Report
    Report Destination
    Regular
    Terse
    STDLIST/USER
    Terse
    Off (no report)
    Console
    Detailed
    Off (no report)
    Rfile
    Terse
    Terse
    Log file


    Default Report Modes for Rollback to DBBEGIN

    Default report settings for rollback to DBBEGIN are listed below:


    Default Rollback Report
    DBBEGIN
    Global message
    No default message. Once set up, it will display with any report produced and sent to any destination. It displays with the DBUNDO message as well.
    Base message
    No default message. Once set up for a particular database, it will always display. It will display for DBUNDO as well.
    REINFORCE
    Reports are produced (On).
    Rfile
    Default is the logon group and account of the user running the program.



    Lund Performance Solutions
    www.lund.com
    Voice: (541) 812-7600
    Fax: (541) 81207611
    info@lund.com
    TOCPREVNEXTINDEX