CBLDCPRF('PRFPUT ') - Acquire user-specific performance verification traces

OpenTP1 Version 7 Programming Reference COBOL Language

CBLDCPRF('PRFPUT ') - Acquire user-specific performance verification traces

Format

PROCEDURE DIVISION specification

CALL 'CBLDCPRF' USING unique-name-1 unique-name-2

PROCEDURE DIVISION specification

01 unique-name-1.
   02 data-name-A  PIC X(8) VALUE 'PRFPUT  '.
   02 data-name-B  PIC X(5).
   02 FILLER      PIC X(3).
   02 data-name-Z  PIC S9(9) COMP VALUE ZERO.
01 unique-name-2.
   02 data-name-C  PIC 9(4) COMP.
   02 data-name-D  PIC 9(4) COMP.
   02 data-name-E  PIC X(n).

Description

CBLDCPRF('PRFPUT ') acquires a user-specific performance verification trace (prf trace).

Data areas whose values are set in the UAP

data-name-A

Specify VALUE 'PRFPUT [Figure] ' for the request code indicating acquisition of a user-specific performance verification trace.

data-name-Z

Specify 0.

data-name-C

Specify the event ID of the event to be acquired. The range of available event IDs is 0x0001 to 0x0040.

data-name-D

Specify the data length of the trace data to be acquired. The specifiable data length is 4 bytes to 256 bytes. The data length must be a multiple of 4 bytes.

data-name-E

Specify the trace data to be acquired. Data that fits within the length specified for data-name-D is valid as trace data.

Data area to which a value is returned from OpenTP1

data-name-B

A status code of 5 digits is returned.

Status codes

Status code	Explanation
00000	Normal termination.
04601	The value specified for the data name is invalid.This status code includes cases in which the request code (data-name-A) is invalid.

Note

Even if CBLDCPRF('PRFPUT ') returns the status code 00000, the trace has not necessarily been properly acquired. This is because data may be lost during trace acquisition processing if multiple processes issue acquisition requests simultaneously because no lock is used.