BPE UPDATE TRACETABLE command

Subsections:

• Syntax
• Keywords
• Output
• Examples

Syntax

Use this command to change the trace level setting for the requested trace tables.

Keywords

UPDATE | UPD

A required parameter, which specifies that the action against the trace table is to update its attributes.

TRACETABLE | TRTAB

A required parameter, which specifies that the resource type being acted upon is a BPE-managed trace table.

NAME(trace_table_name)

A required parameter that specifies the name of the trace table type or types that you want to update. You can specify a single trace table name or a list of trace table names separated by commas. Trace table names can contain wildcard characters. Trace table names can be BPE-defined trace tables or IMS component-defined trace tables.

Note: Trace table types that require explicit commands, for example the HWS RCTR table, is not processed if a generic name, NAME(*), or wildcard pattern, NAME(R%%%), is specified for the trace table name. Trace table types that require explicit commands are processed only when they have been explicitly specified with the NAME parameter: NAME(RCTR).

You can update BPE-defined trace tables for any IMS component address space that is using BPE. These BPE-defined trace table types are available:

AWE

Asynchronous work element (AWE) trace table

CBS

Control block services trace table

CMD

Command trace table

DISP

Dispatcher trace table

ERR

BPE Error trace table

ERRV

BPE error variable trace table

HASH

Hash trace table

LATC

Latch trace table

MISC

Miscellaneous trace table that is used only by IMS Service for trap traces

SSRV

System services trace table

STG

Storage service trace table

USRX

User exit routine trace table

You can update CQS-defined trace tables only for CQS address spaces. These CQS-defined trace table types are available:

CQS

CQS trace table

ERR

CQS error trace table

INTF

CQS interface trace table

OFLW

CQS structure overflow trace table

SEVT

CQS structure event trace table

STR

CQS client activity trace table

Note: A CQS client activity trace table contains trace records from only one CQS structure.

You can update IMS Connect-defined trace tables only for IMS Connect address spaces. These IMS Connect-defined trace table types are available:

ADPT

Adapter trace table

CMDT

IMS Connect command activity trace table

CPDR

CICSPORT driver trace table

CPRT

CICSPORT communication trace table

ENVT

Environment trace table

ERRV

IMS Connect error variable trace table

GSVC

General service trace table

HWSI

IMS Connect to OTMA driver trace table

HWSN

IMS Connect to local option driver trace table

HWSO

IMSplex driver (IPDC) trace table

HWSW

IMS Connect to TCP/IP driver trace table

ICDR

IMS Connect to IMS Connect driver trace table

ICNC

IMS Connect to IMS Connect communication trace table

ISCC

ISC communication trace table

ISDR

ISC driver trace table

LEPS

Language Environment® (LE) preinitialization services trace table

MSCC

MSC communication trace table

MSDR

MSC driver trace table

ODBM

ODBM communication trace table

ODDR

ODBM driver trace table

OMDR

Communication protocol activity (SCI calls) trace table

OSDR

ODBM socket driver trace table

OSOC

ODBM socket communication trace table

OTMA

OTMA communication driver trace table

PCDR

Local option driver trace table

PCIF

PC interface trace table

RCDR

RMTCICS driver trace table

RCIC

RMTCICS communication trace table

RCTR

Recorder trace table

Note: The Recorder trace table requires explicit commands.

RRSI

RRS interface trace table

TCPI

TCP/IP communication driver trace table

You can update OM-defined trace tables only for OM address spaces. These OM-defined trace table types are available:

CSL

CSL trace table

ERR

OM error trace table

OM

OM processes trace table

PLEX

IMSplex trace table for OM processing for a specific IMSplex

You can update RM-defined trace tables only for RM address spaces. These RM-defined trace table types are available:

CSL

CSL trace table

ERR

RM error trace table

PLEX

IMSplex trace table for RM processing for a specific IMSplex

REPO

RM repository services trace table

RM

RM processes trace table

You can update SCI-defined trace tables only for SCI address spaces. These SCI-defined trace table types are available:

CSL

CSL trace table

ERPL

SCI error parameter list trace table

ERR

SCI error trace table

INTF

SCI interface trace table

INTP

SCI interface parameter trace table

PLEX

IMSplex trace table for SCI processing for a specific IMSplex

SCI

SCI processes trace table

You can update DBRC-defined trace tables only for DBRC address spaces. These DBRC-defined trace table types are available:

ERR

DBRC error trace table

GRPS

DBRC group services trace table

MODF

DBRC module flow trace table

RQST

DBRC request trace table

You can update ODBM-defined trace tables only for ODBM address spaces. These ODBM-defined trace table types are available:

CSL

CSL trace table

ERR

Error trace table

ODBM

ODBM trace table

PLEX

IMSplex trace table

You can update Repository Server-defined trace tables only for REPO address spaces. These Repository Server (RS) trace table types are available:

DIAG

Repository Server diagnostics trace table

OWNER

An optional parameter that specifies the owner of the trace table type or types that you want to update. You can specify one of the following values:

BPE

For all IMS components that are running in a BPE address space

CQS

For CQS address spaces only

DBRC

For DBRC address spaces only

HWS

For HWS address spaces only

ODBM

For ODBM address spaces only

OM

For OM address spaces only

REPO

For RS address spaces only

RM

For RM address spaces only

SCI

For SCI address spaces only

The OWNER parameter acts as a filter to help you select which trace tables you want to update. For example, you can specify NAME(*) OWNER(CQS) to update all of the CQS-defined trace table types (CQS, ERR, STR, OFLW, SEVT, and INTF) in a CQS address space. You can specify NAME(*) OWNER(BPE) to update all of the BPE-defined trace table types in any BPE-managed address space. If OWNER is omitted, then both BPE and component trace tables might be updated (depending on the tables that are specified on NAME).

LEVEL(level)

An optional parameter that sets the new tracing level for the specified trace tables. If LEVEL is omitted, the level of the specified trace tables is not changed. These levels are possible:

NONE

No trace data is being written to the table.

ERROR

Only traces for error or exception conditions are being written into the table.

LOW

Only major event trace entries are written into the table.

MEDIUM

Major event trace entries and some minor event trace entries are written into the table.

HIGH

All trace entries are written into the table.

Important: You cannot change the level for the trace table type ERR. BPE forces the level to HIGH to ensure that error diagnostics are captured. Any level that you specify for the ERR trace table is ignored.

EXTERNAL

Specifies whether trace entries for the trace tables that are specified by the NAME keyword should be written to the external trace data set. Values are YES or NO.

YES

Specifies that trace entries are written both to the external trace data set and to memory. Trace entries are written to the external data set only if you define that data set to IMS by including the EXTTRACE statement in the BPE configuration parameter member (BPECFG=) of the IMS PROCLIB data set.

NO

Specifies that trace entries are written only to memory.

If you do not include the EXTERNAL keyword when you issue the command, IMS does not change the current external trace setting (if any) for the affected tables.

You must create or define the data set specified on the EXTTRACE statement. If you do not create or define the data set, an error is generated when you try to open the data set.

OPTION(REREAD)

Specifies that the BPE configuration PROCLIB member that was specified on the BPECFG= parm of the job is reread to obtain updated EXTTRACE settings. Only the BPE configuration PROCLIB member is reread.

The EXTTRACE parameter values in the PROCLIB member at the time it is reread replace the values that were read during initialization. If there is a current external trace data set open, it is closed and deallocated. A new external trace data set is then allocated and opened using the updated EXTTRACE parameters. Other parameters within BPE PROCLIB member are not reprocessed when the member is reread.

With OPTION(REREAD) you can either specify a new external trace data set or modify the characteristics of an existing trace data set without bringing down the address space.

OPTION(REREAD) requires that the address space was started with BPECFG= that specifies a BPE configuration PROCLIB member. If no member was specified, there is no member to reread, and the command will be rejected. If the BPE configuration PROCLIB member is reread and no EXTTRACE statement is found that applies to the current address space, the command is rejected and the existing external trace settings, if any, are kept. If the member is reread and errors occur during allocation or open of the new external trace data set (for example, if the specified data set name does not exist), BPE external trace is stopped. Edit the BPE PROCLIB member and correct the EXTTRACE statement. You can then re-enable BPE external trace by reentering the UPDATE TRACETABLE command with OPTION(REREAD).

Output

The UPDATE TRACETABLE command output consists of message BPE0032I indicating that the command has completed:

   BPE0032I UPDATE TRACETABLE COMMAND COMPLETED