REACTLOG: Reactivating Command Logging

#### Search Results

Search

# REACTLOG: Reactivating Command Logging

The REACTLOG function allows you to reactivate command logging in an active nucleus where it had been disabled previously as a result of an I/O error. The cause of the I/O error needs to be corrected before running this utility function or command logging will simply fail again and will not be reactivated.

This document covers the following topics:

- Optional Parameters

- Example

## Optional Parameters

> NOUSERABEND: Termination without Abend

>   When a parameter error or a functional error occurs while this utility function is running, the utility ordinarily prints an error message and terminates with user abend 34 (with a dump) or user abend 35 (without a dump). If NOUSERABEND is specified, the utility will not abend after printing the error message. Instead, the message "utility TERMINATED DUE TO ERROR CONDITION" is displayed and the utility terminates with condition code 20.

>   Note
>   When NOUSERABEND is specified, we recommend that it be specified as the first parameter of the utility function (before all other parameters). This is necessary to ensure that its parameter error processing occurs properly.

> TEST: Test Syntax

>   The TEST parameter tests the operation syntax without actually performing the operation. Only the syntax of the specified parameters can be tested; not the validity of values and variables. See Syntax Checking with the TEST Parameter for more information on using the TEST parameter in ADADBS functions.

## Example

    ADADBS REACTLOG

This example reactivates command logging after the problem that caused it to be disabled has been resolved.

### On this page

- Optional Parameters
- Example