Version 7.4.4	SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT

User exit 4 is called immediately before an Adabas command log record is to be written. It may be used to generate any required user log data (SMF records) special statistics, or to suppress writing a log record.

Note:
User exit 4 is still called even if ADARUN LOGGING=NO. The only way to disable user exit 4 is to remove the ADARUN UEX4 parameter from the Adabas run.

This document covers the following topics:

• Command Log Format

• PRILOG : Printing the Command Log

Command Log Format

Adabas supports two different command log formats. The ADARUN CLOGLAYOUT parameter determines which format is used:

• CLOGLAYOUT=4 (the default) specifies the older format. This format has been in use since Adabas version 4.

  Note:
  Some Adabas releases using this older format are no longer supported by Software AG. Future releases of Adabas will no longer support this older format.

• CLOGLAYOUT=5 specifies the new format, which is supported only in Adabas versions 5.2 and above.

Both formats are shown in Command Log Formats.

Ensure that your user exit and command log evaluation programs recognize the format in use before switching to it.

User-Generated Log Data User Exit (4) Parameters

The record to be logged may be modified by the user exit. The record's address in 4(R1) may also be modified. The logging action code must always be specified before returning to the Adabas nucleus.

Warning: When modifying the record, do not exceed the end address of the ADALOG I/O area contained in 8(R1).

PRILOG : Printing the Command Log

Adabas provides the PRILOG print program to read and report the contents of Adabas command logs in either version 4 or version 5 command log layout format.

Note:
For version 5 command log layouts, the volume names of enhanced I/O-Lists may also be reported.

PRILOG reads a sequential Adabas command log that has been produced directly by the Adabas nucleus (DD/LOG file) or by the ADARES CLCOPY utility when the Adabas nucleus uses dual or multiple comand logging.

PRILOG is supplied in both source and object form.

Note:
Although PRILOG can be customized, Software AG does not support the program when it has been modified by the user.

In source form, three modules (PRILOG, CCSTCK, and PRILOGD) are supplied for the z/OS, VSE/ESA, and BS2000 operating systems. These modules replace all PRILOG versions supplied with earlier versions of Adabas.

Two of the PRILOG modules are system-independent components and one is specific to a particular operating system:

Print Program Input

As input, the PRILOG program requires CLOG records and control cards.

Control cards must begin with the program name "PRILOG6" in columns 1 through 7; at least one space must follow the program name before parameters are entered.

Parameters can be entered up to column 71. No continuation or parameter splitting is permitted. Additional parameters can be entered on a separate PRILOG6 card.

A comment line begins with an asterisk (*). Comments may also be added to the right side of the parameter string as long as the comment is separated from the parameter value by at least one space.

Control Card Parameters

Two parameters can be entered on the control cards:

CLOGLAYOUT={ 4 | 5}

CLOGLAYOUT indicates the format of the CLOG records being used as input to the PRILOG program. Valid values are 4 and 5; the default value is 5.

FIELDS= { ( item, ... ) | ( LIST) }

FIELDS indicates the item (or items) from the CLOG records that are to be printed where "item" is one of the following:

The default value is LIST. Multiple "items" can be listed in any order.

If a data item listed in the FIELDS parameter is not being captured during the ADALOG session and is therefore not present in the CLOG record, the request to print that data item is ignored.

PRILOG6 Messages

PRILOG6 messages are documented in the Adabas Messages and Codes manual as "PL6nnna" (independent) and "PL6ann" (system-dependent) messages.

Installing and Using PRILOG under VSE/ESA

The following components comprise the PRILOG print program for VSE/ESA:

The PRILOG.PHASE may be executed from the library without additional preparation. However, if it becomes necessary to reassemble and relink the PRILOG.PHASE, the following points must be observed:

• The PRILOG.A, CCSTCK.A, and PRILOGD.A modules must be assembled using the IBM high-level Assembler (ASMA90).

• When linking PRILOG.PHASE, set the phase AMODE and RMODE attributes to 24-bit (AMODE(24) RMODE(24)).

• The provided sample JCS members ASMPLOG.X and LNKPLOG.X must be modified to suit your site's requirements. Check the LDEST, DEST, volume, and extent information as well as the library and sublibrary information provided in the JCS members.

Executing PRILOG under VSE/ESA

Execute the PRILOG print program by running the PRILOG.PHASE in either a static or dynamic partition.

The PRILOG program uses three files:

Notes:

1. The PRILOG control cards must be available from SYSIPT. If on disk or tape, they must be 80-byte records with FIXED record format.
2. The PRILOG report file must be written to SYSLST. If assigned to disk or tape, the output records are 121 bytes in length with FIXED record format. ASA control characters are used for printer control and are in the first byte of each print record.
3. The sequential command log file must be assigned to SYS001. The file may be on disk or tape and may not have a block size greater than 32,760 bytes. The record format is VARBLK.

The provided RUNPLOG.X JCS member may be modified according to your installation's requirements to execute the PRILOG print program. Modify the DEST, extent, DLBL, sublibrary, and volume information before submitting the job.

Installing and Using PRILOG under OS/390 or z/OS

The following components comprise the PRILOG print program for OS/390 oe z/OS:

The PRILOG program uses three files:

www.softwareag.com

Copyright © Software AG 1971-2009. All rights reserved.

SEARCH   INDEX   CONTENTS   |   PDF PAGE   PDF BOOKS   |   HOME   UP   PREV   NEXT