Program Commands

INUTIL Program

The Intact Dynamic Rollback utility program is the main interface between Intact Dynamic Rollback and the Intact Dynamic Rollback operator. The user must have SM, OP or PM capability to run INUTIL.

INUTIL is used to do the following:

Add or delete databases from the list of databases maintained by Intact Dynamic Rollback.

Enable and disable databases for Intact Dynamic Rollback rollback.

Specify the type of rollback required.

Report the status of databases maintained by Intact Dynamic Rollback.

Determine the version of Intact Dynamic Rollback and INUTIL.

Send report files to the system printer and other destination devices.

Specify the type of report to be sent to each report destination.

To run the utility program, type:

:RUN INUTIL.PUB.SYS

INUTIL Commands

The INUTIL program requires keywords and parameters. The commands (keywords) and a short description of each are listed in the following table:

Command	Function
:	To perform MPE commands from within INUTIL.
BMESSAGE	To set up particular database messages to display when any program aborts.
DELETE	To delete databases from the CONFIG.INTACTIX.LPS file.
DISABLE	To disable a database for Intact Dynamic Rollback rollback.
ENABLE	To enable a database for Intact Dynamic Rollback rollback to either DBBEGIN or DBOPEN.
ENTER	To enter databases to the CONFIG.INTACTIX.LPS file.
GMESSAGE	To set up a global message to display when any program aborts.
HELP	To obtain help on the INUTIL commands.
REDO	To edit the previous command, similarly to the MPE command.
REINFORCE	To report instances when a program aborts and Intact Dynamic Rollback does not perform a rollback.
REPORT	To print the report files.
RFILE	To specify where to produce the report disc files (which file or group and account).
RMODE	To specify the report modes (the amount of information displayed to each report destination).
SHOW	To show the global or individual report settings for any of the databases.
VERSION	To verify the version of Intact Dynamic Rollback and INUTIL currently in use.

GMESSAGE Command

The GMESSAGE command of INUTIL enables global level messages.

Syntax

GM[ESSAGE]		|	[DBU[NDO]]	|
		|	[NOD[BUNDO]]	|

Function

The GMESSAGE command sends a global message to the users’ terminals and the operator’s console whenever a program aborts and leaves an open database. When a program aborts, this message will display advising users to take specific action, such as, “Call Jim at ext 9430 if this message appears.”

Only one global message may be established.

You have the option to disallow the message for DBUNDO reports.The default setting is to produce one global message during user-requested (DBUNDO) rollout. This can be changed by adding NODBUNDO to the end of the command line.

Examples

GMESSAGE

Once you enter the GMESSAGE command and press the ENTER key, you may enter up to 80 characters at the prompt.

>GMESSAGE

#Your program has just aborted. Please call Jane at ext 405

To reset the global message, press the ENTER key immediately after the “#” prompt appears.

GMESSAGE DBUNDO

To send a global message during user-requested rollout, enter:

>GMESSAGE DBUNDO

#Message

GMESSAGE NODBUNDO

To set the global message and disallow it for DBUNDO, enter:

>GMESSAGE NODBUNDO

#If rollout occurred, please make note of the RFILE name

BMESSAGE Command

The BMESSAGE command of INUTIL enables database level messages.

Syntax

BM[ESSAGE]	dbname	|	[G[LOBAL]]	|	|	[DBU[NDO]]	|
		|	[NOG[LOBAL]]	|	|	[NOD[BUNDO]]	|

Function

With the BMESSAGE command, you can set up a base message for each individual database maintained by Intact Dynamic Rollback. When a program aborts, the users will see a message that relates specifically to the database they are working on.

You can specify whether an abort of a program assessing that database is to receive the global message.

You can show the base message or not when DBUNDO is utilized. The default is Yes (the message will display).

Examples

BMESSAGE dbname

To set the database level message for the database, MAILDB.PUB.PFIM, enter:

>BMESSAGE MAILDB.PUB.PFIM

#There has been an abort accessing MAILDB. Call Sylvia x35

BMESSAGE dbname GLOBAL

To set a global message for the database, ACCTGPUB.MAINT, enter:

>BMESSAGE ACCTGPUB.MAINT GLOBAL

#Message

BMESSAGE dbname NOGLOBAL

To set a message for the database, ACCTGPUB.MAINT, and not allow it to display globally, enter:

>BMESSAGE ACCTGPUB.MAINT NOGLOBAL

#Message

BMESSAGE dbname DBUNDO

To establish a database level message for user-defined rollout, enter:

>BMESSAGE MAILDB.PUB.PFIM DBUNDO

#Message

BMESSAGE dbname NODBUNDO

To set the database level message and not allow it to display when DBUNDO is utilized, enter:

>BMESSAGE MAILDB.PUB.PFIM NODBUNDO

#Message

ENTER Command

The ENTER command adds a database to the list of databases maintained by Intact Dynamic Rollback.

Syntax

ENT[ER]

|

dbname

|

Function

Each database that is to be maintained by Intact Dynamic Rollback must be listed in the CONFIG.INTACTIX.LPS file. The ENTER command enters the database to the list. (The database name must be fully qualified.)

The database must be entered to the list of Intact Dynamic Rollback-maintained databases before rollback modes or reporting modes can be set up for it.

An entered database will automatically contain the default settings. (Refer to "RMODE Command" for information about default settings.)

A database name cannot be entered more than once. The maximum number of databases maintained by Intact Dynamic Rollback is 50.

You must verify the database name is valid. INUTIL does not verify this for you.

An entered database is not automatically enabled for Intact Dynamic Rollback.

Example

ENTER dbname

To enter the database, MAILDB.PUB.PFIM, to CONFIG.INTACTIX.LPS, type:

>ENTER MAILDB.PUB.PFIM

DELETE Command

The DELETE command is essentially the opposite of the ENTER command.

Syntax

DEL[ETE]	|	dbname	|
	|	@	|

Function

The DELETE command clears a database from the list of databases maintained by Intact Dynamic Rollback. This is useful when a database name is misspelled or when a database should be purged from the system.

Users are allowed to delete all databases from the Intact Dynamic Rollback list.

The user is prompted to confirm the delete request.

A database does not have to be disabled from Intact Dynamic Rollback in order to be deleted.

Examples

DELETE dbname

To delete the database, MAILDB.PUB.PFIM, from the list of databases maintained by Intact Dynamic Rollback, enter:

>DELETE MAILDB.PUB.PFIM

Do you really want to delete MAILDB.PUB.PFIM? Y

DELETE @

To delete all databases from the Intact Dynamic Rollback list, enter:

>DELETE @

Do you really want to delete ALL DATABASES? N

ENABLE Command

Once a database has been entered to the list of databases maintained by Intact Dynamic Rollback, the user can enable the database for Intact Dynamic Rollback rollback with the ENABLE command.

Syntax

ENA[BLE]	|	dbname	|	|	[;DBB[EGIN]]	|
				|	[;DBO[PEN]]	|
				|	[;DBL[OCK]]

Function

There are three types of rollback:

Rollback to DBBEGIN

This is the default rollback specification.

Rollback to DBOPEN

To enable the database to rollback to DBOPEN, the user must specify DBOPEN in the ENABLE command.

Rollback to DBLOCK

The third type of rollback is DBLOCK. DBLOCK is used to rollback to DBBEGIN in situations that involve softlocking. When a no-lock error occurs, Intact Dynamic Rollback gives away all existing locks on the database and tries to obtain a set lock for the affected dataset. Once that lock is obtained, it continues with the rollback to DBBEGIN.

The database can be disabled from Intact Dynamic Rollback maintenance by the DISABLE command (see "DISABLE Command"). A database that is enabled from a disabled state will assume all the characteristics (rollback modes, report modes, etc.) previously specified.

Examples

ENABLE dbname;DBBEGIN

To enable the database, ACCTGPUB.MAINT, for rollback to DBBEGIN, assuming this database has never been enabled for Intact Dynamic Rollback maintenance before, enter:

>ENABLE ACCTPUB.MAINT

or

>ENABLE ACCTGPUB.MAINT;DBBEGIN

ENABLE dbname;DBOPEN

To enable the database, MAILDB.PUB.PFIM, for rollback to DBOPEN, enter:

>ENABLE MAILDB.PUB.PFIMR;DBOPEN

ENABLE dbname;DBLOCK

To enable MAINT.PUB.ACCT for rollback to DBLOCK, enter:

>ENA MAINT.PUB.ACCT;DBLOCK

DISABLE Command

Once a database has been enabled for rollback, it can be disabled with the DISABLE command (the database name must be fully qualified).

Syntax

DIS[ABLE]	|	dbname	|	|	[;DBB[EGIN]]	|
			|	|	[;DBO[PEN]]	|
			|	|	[;DBL[OCK]]	|

Function

The DISABLE command does not remove the database from the list of Intact Dynamic Rollback databases, it just tells the Intact Dynamic Rollback program to ignore the database.

Use the ENABLE command to enable the database again (see "REINFORCE Command").

Examples

DISABLE dbname

To disable the database, MAILDB.PUB.PFIM, from Intact Dynamic Rollback maintenance, enter:

>DISABLE MAILDB.PUB.PFIM

DISABLE dbname;DBBEGIN

To disable the database, MAILDB.PUB.PFIM for roll back to DBBEGIN, enter:

>DISABLE MAILDB.PUB.PFIM;DBBEGIN

DISABLE dbname;DBOPEN

To disable the database, ACCTGPUB.MAINT, and change the rollback mode to DBOPEN:

>DISABLE ACCTGPUB.MAINT;DBOPEN

DISABLE dbname;DBLOCK

To disable the database, ACCTGPUB.MAINT, and change the rollback mode to DBLOCK, enter:

>DISABLE ACCTGPUB.MAINT;DBLOCK

REINFORCE Command

When an abort occurs and Intact Dynamic Rollback does not perform a rollout, reports, called reinforcement reports, are produced to show that no action was taken. The REINFORCE command is used to control the reinforcement reporting mode.

Syntax