The jobname in the JCL JOB statement in the APPC/MVS transaction
program (TP) profile.
CB
The method name, for example, GET, POST, or DELETE. For more
information, see WebSphere® Application Server
for z/OS: Installation and
Customization.
CICS®
A parameter on many CICS commands.
It is often referred to as the CICS transaction
identifier, or tranid. For more information,
see CICS/ESA Resource
Definition Guide.
DB2®
The transaction or job name associated with the originator of
the query; for example, the job name from JES.
IMS™
The CODE= parameter on the IMS TRANSACT
macro. For more information, see IMS/ESA® System Definition
Reference.
IWEB
The method name, for example, GET, HEAD, POST, DELETE, or PUT.
JES
The jobname of the JES managed job. For example, you may run
a CICS region as a batch job
in your installation. You would define it in classification rules
as a transaction name in the JES subsystem type.
LDAP
The z/OS® LDAP server's
enclave transaction name:
Any transaction name that is also defined in the configuration
file of the directory server.
GENERAL for all LDAP work that is not assigned a user-defined
exception class.
For further information, refer to z/OS IBM® Tivoli® Directory
Server Administration and Use for z/OS.
LSFM
One of the following:
LSFMMMTX - multi-media transactions
LSFMFITX - file transactions
LSFMAMTX - administration transactions
LSFMCMTX - communication transactions
MQ
The MQWIH_ServiceStep value from the message's work information
header.
NETV
The NetView® subtask
module name. For more information, see the NetView TASK statement description in the Tivoli NetView Administration
Reference.
OMVS
The jobname for the z/OS UNIX System Services address space.
By default, fork and spawn set jobname values to the user ID with
a number (1-9) appended. However, daemons or users with appropriate
privileges can set the _BPX_JOBNAME environment variable to change
the jobname for forked or spawned children. In this way, servers and
daemons in z/OS UNIX System Services address spaces
can easily be assigned performance attributes different than other z/OS UNIX System
Services address spaces.
STC
One of the following:
The name as specified on the JOBNAME= parameter of the START command
The name specified on the MOUNT command
The system address space name
The name on the JOB statement.
For example, you may run your IMS regions
as started tasks in your installation. You would define these as
transaction names in your STC subsystem type in classification rules.
However, if IMS V5.1 is present,
the STC rule for IMS is ignored
and the rules for the IMS subsystem
type are used when IMS becomes
a server.
TCP
The z/OS Communications
Server transaction name associated with data traffic being processed
by z/OS Communications Server
on an independent enclave that has been active for a relatively long
period of time. Currently the only transaction name supported by z/OS Communications Server is TCPENC01
for IPSec traffic. For further information, refer to z/OS Communication
Server IP Configuration Guide.