Controls request logging
Scope of validity
DBH administration
Function
You use the SET-TUNING-TRACE statement to control the request logging of the DBH. You can turn request logging on or off and specify the volume for the request log file (CO-LOG) to which the DBH writes its data. You can also specify that the CPU time is to be measured.
When request logging is turned on, the DBH opens the CO-LOG file in order to log the data in it. If you turn request logging off, the CO-LOG file is closed, even when there are requests still open.
As soon as the CO-LOG file is closed, the SESCOSP utility edits and outputs the data collected (see chapter “Evaluating request logging with SESCOSP”).
Each time request logging is turned on, the file count (iiii) in the default filename of the CO-LOG file (SESAM.CO-LOG.ssss.iiii) is incremented by 0001. The placeholder ssss stands for the session ID, which corresponds by default to the BS2000 task sequence number, TSN (see the “ Core manual”).
In contrast to the recording of operational data with the SESMON performance monitor (see chapter “Outputting operational data with SESMON”), this type of request logging uses the resources of the DBH.
The USER-SELECT parameter allows you to restrict request logging to individual users. This makes it possible to carry out logging for extended periods without subjecting the DBH to excessive loads. When evaluating data with SESCOSP, note that the users defined in SESCOSP represent a genuine subset of the users defined in USER-SELECT. In SESCOSP the users to be evaluated can be further restricted by means of the SELECT parameter USERS (see "The SELECT parameter USERS").
SET-TUNING-TRACE | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
1The *TAPE operand of older SESAM/SQL versions is no longer available.
Operands
TRACE = *ON(...)
Turns on request logging.
CPU-TIME = *NO / *YES
Specifies whether or not the CPU time is to be recorded. The default is NO, the CPU time is not recorded.
PROTOCOL = *STD / *LONG
Specifies the type of logging.
The following applies to the PROTOCOL=*STD:
language-specific parts of the SQL statement are only logged to a limited degree; SQL descriptors are not logged.
specific parts of CALL-DML are only logged to a limited degree (statement, query area and response area).
Unlogged parts cannot be evaluated with SESCOSP (see "Evaluating request logging with SESCOSP").
The setting PROTOCOL=*LONG enables full logging. In this case, the protocol generation loads the DBH still further and the CO-LOG file is made much larger. The setting of the PRIMARY and SECONDARY ALLOCATION must be adapted to the CO-LOG file where necessary.
USER-SELECT = *ALL / <user-identification>
Restricts the statement to a group of users. This partial qualification can have more than one match. The syntax of the parameter is described in section “Syntax for the identification of users”. The default is *ALL (no restriction applies).
* (asterisk) enables you to select a subset in the suboperands HOST-NAME, APPLICATION-NAME and CUSTOMER-NAME of the <user-identification>. The hosts, users and applications whose names begin with the specified string (up to the first *) are selected.Examples:
HOST-NAME=D016* selects all hosts whose names begin with D016.
APPLICATION-NAME=UTM* selects all applications whose names begin with UTM.
CUSTOMER-NAME=UPIC* selects all users whose names begin with UPIC.
...-NAME=* selects all hosts, applications or users.
SUPPORT =
Specifies the volume for the CO LOG file.
SUPPORT = *PUBLIC-DISK(...)
Causes the CO LOG file to be created on a public disk.
CAT-ID = *STD / <cat-id>
Catalog ID of the pubset on which the file is to be stored. The default is the DBH catalog ID.
PRIMARY-ALLOCATION = 192 / <integer 1..16777215>
Number of PAM pages for the initial allocation of memory space. The specified number of PAM pages is reserved immediately.
SECONDARY-ALLOCATION = 24 / <integer 0..32767>
Number of PAM pages for subsequent extensions to files
SUPPORT = *PRIVATE-DISK(...)
Causes the CO LOG file to be created on a private disk. To do this, you must make an entry for DEVICE-TYPE.
CAT-ID = *STD / <cat-id>
Catalog ID of the pubset on which the file is to be stored.
PRIMARY-ALLOCATION = 192 / <integer 1..16777215>
Number of PAM pages for the initial allocation of memory space.
The specified number of PAM pages is reserved immediately.
SECONDARY-ALLOCATION = 24 / <integer 0..32767>
Number of PAM pages for subsequent extensions to files
DEVICE-TYPE = <structured-name 1..8>
BS2000 device type to which the required disks are assigned.If you make an incorrect entry, the system prompts you in interactive mode to make the entry again (see the device type table in the BS2000 manual “ Commands”).
VOLUME = list-poss(6): <alphanum-name 1..6>
VSNs of the disks on which the file is to be created. Up to six VSNs are permitted. You can enter each VSN only once.
TRACE = *OFF
Turns request logging off.
Administration command in ISP format and at the CALL DML interface
The COS administration command corresponds to the SET-TUNING-TRACE administration statement here.
COS,TP={ON[,CPU][,L[ONG]][,user-identification][,file-spec] | OFF}
file-spec ::= V[OL]=(vsn)[,D[EV]=device]
[,S[PACE]=(space)][,C[ATID]=cat-id]
The partial qualification for user-identification can have more than one match.
* (asterisk) enables you to select a subset in the suboperands
host
,
appl
and
user
of the
user-identification
, see the description above under USER-SELECT.In INFORM-PROGRAM administration you must adhere to the permissible length for filespec (see section “Administration using INFORM-PROGRAM”).
No tape device type may be specified for file-spec.