Glossary of Report Form field names
This glossary lists all the fields available to IMS Performance Analyzer form-based list and summary reports.
- Report Forms
- Use the IMS Performance Analyzer ISPF dialog to construct a Report Form containing fields from the list below. The dialog can be used to generate batch report commands. For more information, see the IMS Performance Analyzer User's Guide.
- Batch
- You can also specify these fields with the following batch report commands using the
FIELDS operand as
follows:
IMSPALOG LIST(...,FIELDS(field1,...)) IMSPACEX LIST(...,FIELDS(field1,...)) IMSPALOG SUMMARY(...,FIELDS(field1,...)) IMSPACEX SUMMARY(...,FIELDS(field1,...))
- A description of the field.
- The source of the reporting field: IMS, IMS Connect, or both.
- The column heading that is displayed in reports and extracts.
- Where applicable, the corresponding global field used when browsing IMS logs and IMS Connect Extensions journals in IMS Problem Investigator.
A
- ABEND Code
- See COMPCODE
- ABENDCNT
- For Form-based summary reporting only, the number of abending transactions that were accumulated
in the key range. See also
TRANCNT.
Source: IMS
Column heading: Abend Count
- ACKREAD
- Acknowledgment read socket time. The total elapsed time for all read Socket Events issued after
the response from OTMA has been sent to the client. This is the time taken to read the
acknowledgment from the client.
Source: IMS Connect
Column heading: ReadSock Ack Time
- ALIAS
- Original ODBM alias name. For Open Database workloads in IMS Connect, this is the name of the
ODBM alias specified in the DRDA request. See also
OUTALIAS.
Source: IMS Connect
Column heading: Alias Name
- APPC
- APPC indicator. Indicates whether the transaction originated from APPC. Reported values are:
- APPC
- Implicit APPC using the IMS message queue
- CPIC
- Explicit CPI-CI APPC using program schedule and APPC verbs
- blank
- Transaction is not APPC
Source: IMS
Column heading: APPC
- Applictn Grp Name
- See APPLNAME
- APPLNAME
- Application grouping name provided by the Transaction Substitution exit.
Source: IMS
Column heading: Applictn Grp Name
- ApplResp Time(R0)
- See R0TIME
- ASIO Waits
- See FPASIOWT
- ASYNC Rd-Ahead
- See FPASIORA
B
- BALG Q Count
- See FPBALGCT
- BMPCHKID
- The BMP user checkpoint id.
Column heading: BMP Chkpt ID
- BMPCHKPT
- The number of checkpoints issued by the BMP, or the unit of work.
See also BMPSYNCP
Column heading: BMP Chkpt Ct
- BMPSYNCP
- The number of syncpoints issued by the BMP, or the unit of work.
See also BMPCHKPT
Column heading: BMP Sync Cnt
C
- CEXcm Level
- See COMPLVLC
- CEXHICOD
- IMS Connect log code associated with the highest reported return code (RC). No value is reported
if the return code is zero (0). See also CEXHIRC and CEXHIRSN.
Source: IMS Connect
Column heading: High Code
- CEXHIRC
- Highest return code (RC) found in the IMS Connect transaction. See also CEXHICOD and CEXHIRSN.
Source: IMS Connect
Column heading: CEX High RC
- CEXHIRSN
- Reason code associated with the highest reported return code (RC) found in the IMS Connect
transaction. No value is reported if the return code is zero (0). See also CEXHICOD and CEXHIRSN.
Source: IMS Connect
Column heading: CEX High RSN
- CEXTYPE
- IMS Connect transaction type.
- OTMA
- Open Transaction Manager Access (OTMA) transaction
- ODBM
- Open Database transaction
- blank
- Unknown transaction type
Source: IMS Connect
Column heading: Tran Type
- CI Lock WAITS
- See FPCILWT
- CICSAPPL
- CICS® generic APPLID.
For CICS-DBCTL only, the generic APPLID of the CICS region that scheduled this thread.
The APPLID is extracted from the first 8 characters of the IMS recovery token.
- CICSTASK
- CICS task number. For CICS-DBCTL only, the task number of the CICS
transaction that scheduled this DBCTL thread.
In CICS Performance Analyzer, the associated CMF field is TRANNUM DFHTASK P031 and is reported using field name TASKNO.
You can use the CICS task number to match transactions in the CICS and IMS reports.
The CICS transaction name and task number are available in the IMS 08 log record. For details, see the IMS-supplied macro SDFSMAC(DFSLOG08).
Source: IMS
Column heading: CICS Task ID
- CLASS
- Transaction Class. Transaction class as specified in the TRANSACT macro MSGTYPE parameter.
Source: IMS
Column heading: Cls
- CLIACK
- Client acknowledgment indicator. Indicates how the IMS Connect transaction client acknowledged the transaction results from IMS. Reported values are:
- ACK
- Client positively acknowledged (ACK)
- NAK
- Client negatively acknowledged (NAK)
- NAKP
- Client NAK with Purge if non-deliverable
- NAKR
- Client NAK with Re-route
- blank
- Transaction was not Synch Level=CONFIRM
Source: IMS Connect
Column heading: Cli ACK
- CLIENTID
- IMS Connect Client ID.
Source: IMS Connect
Column heading: Client ID
IMS Problem Investigator global field: ClientID
- Cls
- See CLASS
- CM0DELAY
- OTMA Commit Mode 0 (Commit-Then-Send) client ACK time. For OTMA Commit Mode 0 transactions only,
the time it takes the client to acknowledge the response back to IMS. The elapsed time is calculated from when the output message is sent
(Comms 31) to when the client acknowledgment is received and dequeued (36). This is a part of
transaction processing time and can include the following:
- XCF overhead
- OTMA client (IMS Connect) processing overhead and wait for client acknowledgment
Source: IMS
Column heading: CM0Delay Time
- CM1DELAY
- OTMA Commit Mode 1 (Send-Then-Commit) delay time. For OTMA Commit Mode 1 transactions only, the
delay in processing after the output message has been sent to OTMA. The delay elapsed time is from
when the output message is sent (03/31) to when the transaction commences syncpoint processing
(5610). This delay is a part of transaction processing time and can include the following:
- XCF overhead
- For Synch Level=CONFIRM only, OTMA client (IMS Connect) processing overhead and wait for client acknowledgment
Source: IMS
Column heading: CM1Delay Time
- COMMITMD
- IMS Connect Commit mode. Reported values
are:
- 0
- Commit mode 0 (Commit-Then-Send)
- 1
- Commit mode 1 (Send-Then-Commit)
- blank
- Not an IMS Connect transaction
Source: IMS Connect
Column heading: Commit mode
- Commit SDEP CIs
- See FPSDEPCI
- Commit SDEP Seg
- See FPSDEPSG
- COMPCODE
- Transaction abend completion code.
Source: IMS
Column heading: ABEND Code
- COMPLVL
- IMS transaction completion level. IMS Performance Analyzer assigns a completion level to every transaction. IMS Performance Analyzer form-based reporting can specify a minimum completion level
allowing you to report only those transactions that have reached this level of completion. The IMS transaction completion levels are:
- 0
- IMS message is a message switch or generated output message, not a transaction. Use Completion level 0 to analyze all message queue activity, not when transaction transit information is required.
- 1
- Transaction input message enqueued onto the IMS message queue. Use Completion level 1 to analyze transaction message queue activity, not when transaction transit information is required.
- 2
- Transaction has started processing in the dependent region but has not completed processing. Only input queue time is available for reporting.
- 3
- Transaction has finished processing in the dependent region but has not sent the output message to the destination LTERM. Input queue and processing times are available for reporting.
- 4
- Transaction has ended but resource utilization statistics (from the type 07 application
termination record) are not available, possibly due to WFI processing (schedule
not ended). Input queue, processing, output queue and total times are available
for reporting.Note: When processing logs from shared queues subsystems, transactions are possibly assigned completion level 4, even though IMS is writing 56FA transaction-level accounting records. 56FA records result in completion level 6; however, these records can be on the log from an IMS subsystem that was not selected for the report. For transactions to be assigned completion level 6, logs from all IMS subsystems participating in the same shared queues environment must be selected.
For example, suppose a transaction message is received into IMS1, put on the shared queue, read from the shared queue by IMS2, and processed by IMS2. Completion level 4 is assigned because IMS2 might have written the 57FA transaction-level accounting record.
To achieve completion level 6, you can create a Group definition that contains IMS1 and IMS2. Then, run the report for the Group so that IMS PA can merge the logs from both subsystems. For more information refer to the Shared Queue merge processing section in the User's Guide..
- 5
- Transaction has ended and resource utilization statistics (from the type 07 application termination record) are available, and are approximations only. Type 07 application termination record statistics are apportioned equally amongst all transactions processed by the program schedule. All application statistics fields are available for reporting.
- 6
- Transaction has ended and accurate resource utilization statistics are
available. For Unit-of-Recovery () transactions, resource utilization statistics
are derived from the type 56FA transaction-level accounting record. This record
provides accurate and reliable information for each Unit-of-Recovery (). Resource
statistics for transactions reported over the entire schedule are taken from the
type 07 record. This includes DBCTL, ODBM, CPIC, and non-message driven BMP
transactions.
All application statistics fields are available for reporting.
Source: IMS
Column heading: Comp Level
- COMPLVLC
- IMS Connect transaction completion level.
IMS Performance Analyzer assigns a completion level to every transaction.
IMS Performance Analyzer form-based reporting can specify a minimum
completion level allowing you to report only those transactions that have reached this level of
completion. The IMS Connect transaction completion levels are:
- 0
- For transactions that specified a transaction socket type, either IMS Connect rejected the transaction request message before calling the user message exit or that exit abended. For other transactions, Resume-Tpipe transaction completed. Use Completion level 0 to analyze all activity.
- 1
- For transactions that specified a transaction socket type, the IMS Connect user message exit rejected the transaction request. Use Completion level 1 to analyze messages rejected by the message exit.
- 2
- IMS Connect Message sent to OTMA for processing.
- 3
- IMS Connect Message received from OTMA. This level may also indicate an OTMA timeout or error.
- 4
- Transaction has completed IMS Connect processing. This level may also indicate an OTMA timeout or error.
Source: IMS Connect
Column heading: CEXcm Level
- CONFIRM
- Client Confirm time. For Sync Level CONFIRM transactions only, the elapsed time from when OTMA
completed processing the input message to when the ACK response from the client is sent back to
OTMA.
Source: IMS Connect
Column heading: Confirm Time
- CONFOTMA
- OTMA ACK processing time. For Sync Level CONFIRM transactions, the time IMS Connect waits for
the ACK transaction to be processed by IMS and
send the response back.
Source: IMS Connect
Column heading: OTMAconf Time
- Conn RTp Time
- See OUTRTCON
- Connect Logon Token
- See CONNLTOK
- Connect System
- See HWSID
- CONNLTOK
- IMS Connect Logon token. When used as a key field in IMS Connect summary reports, only
persistent socket transactions will be reported.
Source: IMS and IMS Connect
Column heading: Connect Logon Token
IMS Problem Investigator global field: LogToken
- CONNOTOK
- IMS Connect Resume-Tpipe Orig Message logon token. IMS Connect logon token of the originating input message taken from the first
IMS Connect event 58 (IMS Hold Queue Compensation) record encountered in the IMS Connect transaction.
Source: IMS Connect
Column heading: Resume Tpipe Orig Msg Token
- CON Resp Time
- See RESPCON
- CON Tran Start
- See STARTCON
- Conv
- See CONVERS
- CONVERS
- Conversational transaction indicator. Indicates whether a transaction is conversational as
defined in the TRANSACT macro SPA parameter. Reported values are:
- C
- Conversational
- N
- Non-conversational
- blank
- Not a message queue transaction
Source: IMS
Column heading: Conv
- CPUSU
-
Program execution CPU time reported in service units. The service unit normalizes the reporting of CPU time to allow for performance comparisons between, for example, an older processor and a newer processor in terms of CPU effort. CPU service unit reporting is only available in Form-based transit reports.
The CPUSU is calculated as CPUTIME * conversion factor. When IMS Performance Analyzer is running on the same system that generated the IMS log input file, the conversion factor can be calculated at run-time. Otherwise the conversion factor must be supplied to IMS Performance Analyzer in the command input as
IMSPALOG SYSTEM(name,Vvrm,factor)
.The conversion factor for each IMS system should be specified in your batch JCL:- Use the IPICPUSU REXX EXEC located in the SIPIEXEC library to calculate the conversion factor
and generate the batch
command:
You can specify a conversion factor of* IBM IMS Performance Analyzer: CPU time to Service Units conversion * * SYSID: XYZ1 * * CPU VV --ID-- Model Speed Specialty * 0 00 039A37 2818 1.000 * 1 00 039A37 2818 1.000 * 2 00 039A37 2818 1.000 zIIP * * Adjustment values: RMCTADJC=718 RMCTCPU=4097 * * Formula: SUSEC = 1000000 / (RMCTADJC * 256 / RMCTCPU) * Result : 1 CPU second = 22289.563 Service Units * * The following IMSPA batch command will convert CPU time to SUs: IMSPALOG SYSTEM(name,Vvrm,22289.563)
CURRENT
to instruct IMS Performance Analyzer to calculate the conversion factor at run time, based on the processor where IMS PA is executing. If you do not specify a conversion factor, IMS Performance Analyzer will useCURRENT
. - Specify the command generated by step 1 in your batch JCL, for example:
//IMSPA JOB (ACCOUNT),'NAME' //* //IMSPA EXEC PGM=IPIMAIN,PARM='V152' //STEPLIB DD DISP=SHR,DSN=IMSPA.V4R5M0.SIPILINK //SYSPRINT DD SYSOUT=* //LOLD1001 DD DISP=SHR,DSN=IMS.OLD1.SLDS //LNEW1001 DD DISP=SHR,DSN=IMS.NEW1.SLDS //IPIOPTS DD * * IMS System Definitions IMSPALOG SYSTEM(OLD1,V151,14637.212) IMSPALOG SYSTEM(NEW1,V152,22289.563) /* //IPICMD DD * IMSPALOG LIST(SECGROUP,FIELDS(...,CPUSU,...)) IMSPALOG SUMMARY(SECGROUP,FIELDS(...,CPUSU,...)) IMSPALOG EXECUTE /*
You must execute this REXX on the same system that created the IMS log file. The command generated by this REXX is then input into the IMS Performance Analyzer batch process.Note: There is no provision for specialty processors.Source: IMS
Column heading: CPUSU
- Use the IPICPUSU REXX EXEC located in the SIPIEXEC library to calculate the conversion factor
and generate the batch
command:
- CPUTIME
- Program execution CPU time, approximation only at completion level 5, accurate at completion
level 6.
At completion level 5 resource usage metrics are obtained from the type 07 application termination record and apportioned equally among all transactions that executed under that schedule, regardless of their respective processing times.
At completion level 6, resource usage metrics for Unit-of-Recovery () transactions are obtained from the type 56FA transaction accounting record. Metrics for transactions reported over the entire schedule are obtained from the type 07 record. This includes DBCTL, ODBM and non-message driven BMP transactions (with BMPSYNC(NO)).
For Fast Path transactions, CPU time is available only at completion level 6 from the 56FA record.
Source: IMS.
Column heading: CPU Time
- CPUZIIP
- zIIP execution time.
Source: IMS
Column heading: zIIP CPU Time
D
- DATABASE
- The DBD name of the database updated by the transaction.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Note: The IMS log only keeps database update activity records (log codes 50 and 5950). Databases accessed by the transaction for read-only will not be reported.Source: IMS
Column heading: Database DBD Name
- Database DBD Name
- See DATABASE
- DB AccM
- See DBACMETH
- DB Lock Time
- See LOCKTIME
- DB Org Type
- See DBORGTYP
- DBACMETH
- Database access method. Reported values are:
- CHKP
- BMP user checkpoint. CHKP is an indicator that the database has been read by the BMP.
- DEDB
- Fast path data entry database
- ESDS
- Entry-sequenced data set (VSAM)
- KSDS
- Key-sequenced data set (VSAM)
- OSAM
- Overflow sequential access method
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: DB AccM
- DBBLKDEL
- The number of block deletes for the database.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: DB Block Deletes
- DBBLKINS
- The number of block inserts for the database.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: DB Block Inserts
- DBBLKREP
- The number of block replaces for the database.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: DB Block Replaces
- DBBLKUPD
- The number of block updates for the database.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: DB Block Updates
- DBCALLS
- Full function database call count, approximation only at completion level 5, accurate at
completion level 6. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB Call Count
- DBCTLPRE
- The elapsed time between the start of the CICS
transaction and the IMS PSB being scheduled
and ready to process DLI calls.
For programs that issue the EXEC DLI SCHEDULE at the start of processing, this measurement can provide an estimate of the time for a DBCTL thread to become available, and for IMS to schedule it.
This time is calculated as 08 suffix STCK - IMS recovery token STCK.
For CICS-DBCTL, the IMS recovery token is generated by CICS, and consists of two parts:
- CICS APPLID
- Unique recovery UOW identifier (STCK value recorded in CMF field RMUOWID DFHTASK T132)
- DBDEQ
- The number of DL/I DB DEQ calls.
Source: IMS
Column heading: DB DEQ Count
- DBDLET
- Database DLET call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB DLET Count
- DBGETS
- Full function database get call count, approximation only at completion level 5, accurate at
completion level 6. Get calls are Get Unique (GU), Get Next (GN), Get Next in Parent (GNP), Get Hold
Unique (GHU), Get Hold Next (GHN), and Get Hold Next in Parent (GHNP). At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB Get Count
- DBGHN
- Database Get Hold Next (GHN) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB GHN Count
- DBGHNP
- Database Get Hold Next in Parent (GHNP) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB GHNP Count
- DBGHU
- Database Get Hold Unique (GHU) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB GHU Count
- DBGN
- Database Get Next (GN) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB GN Count
- DBGNP
- Database Get Next in Parent (GNP) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB GNP Count
- DBGNS
- Total database Get Next (GN), Get Next in Parent (GNP), Get Hold Next (GHN), and Get Hold Next
in Parent (GHNP) calls. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB GNx Count
- DBGU
- Database Get Unique (GU) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB GU Count
- DBGUR
- The number of DL/I GUR calls.
Source: IMS
Column heading: DB GUR Count
- DBGUS
- Total database Get Unique (GU) and Get Hold Unique (GHU) calls. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB GUx Count
- DBIOCALL
- Total OSAM and VSAM database IO count, approximation only at completion level 5, accurate at
completion level 6. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: Total IO Count
- DBIOTIME
- Database IO elapsed time, approximation only at completion level 5, accurate at completion level
6. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB IO Time
- DBIR
- The number of DL/I IR calls.
Source: IMS
Column heading: DB IR Count
- DBISRT
- Database ISRT call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB ISRT Count
- DBMR
- The number of DL/I MR calls.
Source: IMS
Column heading: DB MR Count
- DBORGTYP
- Database organization type. Reported values are:
- HDAM
- Hierarchical Direct Access Method
- HIDAM
- Hierarchical Indexed Direct Access Method
- DEDB
- Data Entry Database
- INDEX
- Primary or secondary index
- HISAM
- Hierarchical Indexed Sequential Access Method
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: DB Org Type
- DBREPL
- Database REPL call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB REPL Count
- DBRLSE
- The number of DL/I DB RLSE calls.
Source: IMS
Column heading: DB RLSE Count
- DBUPDATS
- Full function database update call count, approximation only at completion level 5, accurate at
completion level 6. Update calls are ISRT, DLET, REPL. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB Updat Count
- DBUPRATE
- The number of database updates per second.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: Updates/Second
- DBWAITS
- Full function database wait count, approximation only at completion level 5, accurate at
completion level 6. Waits can be for Test enqueues, Queue commands, Update and enqueues, and
Exclusive enqueues. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB Wait Count
- DCAUTH
- The number of DL/I message queue AUTH calls.
Source: IMS
Column heading: DC AUTH Count
- DCCALLS
- DC message queue call count, approximation only at completion level 5, accurate at completion
level 6. DC calls are Get Unique (GU), Get Next (GN), Insert (ISRT), and PURGE. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC Call Count
- DCCHNG
- Message queue Change (CHNG) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC CHNG Count
- DCCMD
- Message queue Command (CMD) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC CMD Count
- DCGCMD
- Message queue Get Command (GCMD) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC GCMD Count
- DCGN
- Message queue Get Next (GN) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC GN Count
- DCGU
- Message queue Get Unique (GU) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC GU Count
- DCISRT
- Message queue Insert (ISRT) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC ISRT Count
- DCPURG
- Message queue Purge (PURG) call count. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC PURG Count
- DCSETO
- The number of DL/I message queue SETO calls. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DC SETO Count
- DDNAME
- Input log ddname. The name specified in the JCL for the log containing the start record (usually
X'01') for this transaction.
Source: IMS
Column heading: IMS log DDname
- DEDBAREA
- The DEDB area name of the database.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: DEDB Area
- DEDB Get Count
- See FPDEGET
- DEDB Put Count
- See FPDEPUT
- Dest Tmember
- See TMEMBERD
- DLAYOTMA
- OTMA delay time. The delay attributable to OTMA for an IMS Connect transaction. This elapsed time is a combination of two times:
- From when IMS Connect sends the transaction message to OTMA, to when the message is enqueued onto the IMS message queue.
- From when the IMS transaction sends the response back to OTMA, to when IMS Connect receives the response back.
Important: OTMA delay time can only be calculated when IMS Connect Extensions journal and IMS log data is available. This is because both IMS Connect Extensions journal records and IMS log records are required to calculate the elapsed time delay.Source: IMS Connect and IMS
Column heading: OTMADlay Time
- DLICOMTM
- The ODBM unit of work (UOW) commit elapsed time.
Source: IMS Connect
Column heading: DLI UOW Commit
- DLIDBNM
- Database name associated with the ODBM DL/I function call.
Source: IMS Connect
Column heading: DLI DB Name
- DLIDISP
- ODBM Unit of Work (UOW) disposition.
- COMT
- Committed
- ROLB
- Rolled back
- blank
- Unknown
Source: IMS Connect
Column heading: UOW Disp
- DLIFROWS
- Count of rows updated for the ODBM DL/I function call.
Source: IMS Connect
Column heading: DLI Rows Updated
- DLIFUNC
- Type of DL/I function call made by the ODBM transaction.
- ISRT
- Insert
- DLET
- Delete
- REPL
- Replace
- GHU
- Get Hold Unique
- GU
- Get Unique
- GUR
- Get Unique Record
- GHN
- Get Hold Next
- GN
- Get Next
- GHNP
- Get Hold Next Within Parent
- GNP
- Get Next Within Parent
- DELE
- Batch Delete
- UPDA
- Batch Replace
- RETR
- Batch Retrieve
Source: IMS Connect
Column heading: DLI Func
- DLIFUNCT
- Count of each type of DL/I function call made by the ODBM transaction.
Source: IMS Connect
Column heading: DLI Func Count
- DLIMSGTM
- The elapsed time taken by all messages in the DL/I function call for an ODBM
transaction.
Source: IMS Connect
Column heading: DLI Msg Time
- DLIPCBNM
- PCB name associated with the DL/I function call for an ODBM transaction.
Source: IMS Connect
Column heading: DLI PCB Name
- DLIUOWSQ
- ODBM UOW relative sequence number. UOW sequence number for this DLI call aggregation, a relative
count starting at 1. Usually equates to the IMS Recovery Token COMN+1.
Source: IMS Connect
Column heading: UOW Seq#
- DSAPSB
- The number of DL/I APSB calls.
Source: IMS
Column heading: DS APSB Count
- DSCHKP
- The number of DL/I CHKP calls.
Source: IMS
Column heading: DS CHKP Count
- DSDPSB
- The number of DL/I DPSB calls.
Source: IMS
Column heading: DS DPSB Count
- DSGMSG
- The number of DL/I GMSG calls.
Source: IMS
Column heading: DS GMSG Count
- DSICMD
- The number of DL/I ICMD calls.
Source: IMS
Column heading: DS ICMD Count
- DSINIT
- The number of DL/I INIT calls.
Source: IMS
Column heading: DS INIT Count
- DSINQY
- The number of system service inquiry (INQY) calls. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DS INQY Count
- DSLOG
- The number of system service log (LOG) calls. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DS LOG Count
- DSRCMD
- The number of DL/I RCMD calls.
Source: IMS
Column heading: DS RCMD Count
- DSROLB
- The number of DL/I ROLB calls.
Source: IMS
Column heading: DS ROLB Count
- DSROLS
- The number of DL/I ROLS calls.
Source: IMS
Column heading: DS ROLS Count
- DSSETS
- The number of DL/I SETS calls.
Source: IMS
Column heading: DS SETS Count
- DSSETU
- The number of DL/I SETU calls.
Source: IMS
Column heading: DS SETU Count
- DSXRST
- The number of DL/I XRST calls.
Source: IMS
Column heading: DS XRST Count
E
- ESAFCALL
- Total ESAF call count, approximation only at completion level 5, accurate at completion level 6.
At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: ESAFcall Count
- ESAFCCON
- The time of day when the external subsystem completed Commit Continue processing during the
transaction syncpoint.
A transaction can use more than one external subsystem (for example, Db2 and the IBM® MQ adapter). In this case there will be additional report lines for each subsystem used by the transaction.
Recommendation: When requesting this field, also include the ESAFNAME field in the form. This will identify the subsystem to which this field applies.Source: IMS
Column heading: ESAF CC End
- ESAFCOMT
- The elapsed time it took for the external subsystem to complete Commit processing during the
transaction syncpoint.
A transaction can use more than one external subsystem (for example, Db2 and the IBM MQ adapter). In this case there will be additional report lines for each subsystem used by the transaction.
Recommendation: When requesting this field, also include the ESAFNAME field in the form. This will identify the subsystem to which this field applies.Source: IMS
Column heading: ESAF SP Time
- ESAFNAME
- The name of the external subsystem used by the transaction.
A transaction can use more than one external subsystem (for example, Db2 and the IBM MQ adapter). In this case there will be additional report lines for each subsystem used by the transaction.
Source: IMS
Column heading: ESAF Name
- ESAFPRE
- ESAF Commit Prepare start time. The time of day when the external subsystem started Commit
Prepare processing during the transaction syncpoint.
A transaction can use more than one external subsystem (for example, Db2 and the IBM MQ adapter). In this case there will be additional report lines for each subsystem used by the transaction.
Recommendation: When requesting this field, also include the ESAFNAME field in the form. This will identify the subsystem to which this field applies.Source: IMS
Column heading: ESAF CP Start
- EXCLDEQ
- The number of DL/I exclusive dequeue calls.
Source: IMS
Column heading: Excl Dequeues
- EXCLENQ
- The number of DL/I exclusive enqueue calls.
Source: IMS
Column heading: Excl Enqueues
- EXCLWAIT
- The number of DL/I waits on DL/I exclusive enqueue calls.
Source: IMS
Column heading: Waits on Excl Enq
- EXITNAME
- The user message exit name for an IMS
Connect transaction. This exit name is extracted from the first
message exit returned from READ
event record (log code 3E) for the transaction.Source: IMS Connect
Column heading: Connect Exit
- EXPRESS
- Indicates the type of Express program. Reported values are:
- MSG
- EXPRESS=YES message.
- PGM
- EXPRESS program switch transaction.
- blank
- Not an EXPRESS Message/Program.
- -
- Unknown
F
- FAILED
- Transaction failure indicator. The reason for an IMS or IMS Connect transaction failure. Reported values are:
- blank
- Transaction did not fail.
- ABEND
- Transaction abend (abnormal end of task).
- CANCEL
- Transaction cancelled.
- REJECT
- Transaction rejected.
- SESSION
- Connect transaction failed due to a session error.
- SF=?
- Fast Path Syncpoint Failure, code = ?
Source: IMS, and Connect
Column heading: Failure Reason
- Failure Reason
- See FAILED
- FFCHGN
- The number of full function Lock Change requests.
Source: IMS
Column heading: FFChange count
- FFDB50
- The number of associated full-function database update (type 50) log records.
Source: IMS
Column heading: FF DBUpd count
- FFLOCK
- The number of full function Lock requests.
Source: IMS
Column heading: FF Lock count
- FFUNLK
- The number of full function Unlock requests.
Source: IMS
Column heading: FFUnlock count
- FLD Call Count
- See FPFLD
- FP SyncP Count
- See FPSYNCCT
- FPASIORA
- Fast Path ASYNC Read-aheads. The number of UOW asynchronous read-aheads by HSSP or the High
Speed DEDB Direct Reorganization utility in a transaction (one unit of work).
Source: IMS
Column heading: ASYNC Rd-Ahead
- FPASIOWT
- Fast Path Waits for ASIO. The number of UOW asynchronous read-aheads to complete by HSSP or the
High Speed DEDB Direct Reorganization utility in a transaction (one unit of work). This number
should be either zero or one.
Source: IMS
Column heading: ASIO Waits
- FPBALGCT
- Fast Path BALG Queue Count at Syncpoint. The number of transactions in the balancing group
(BALG) queue when this transaction entered sync point processing.
Source: IMS
Column heading: BALG Q Count
- FPBFOTHR
- Fast Path Buffers sent to OTHREAD. The number of Fast Path buffers sent to OTHREAD.
Source: IMS
Column heading: OTHREAD Buffers
- FPBFSTL
- Fast Path Buffer steals per Tran. The number of times buffer stealing is invoked by this
transaction.
Source: IMS
Column heading: FPBuffer Steals
- FPBFWT
- Fast Path Waits for Buffer. The number of times the transaction waited for a buffer to become
available.
Source: IMS
Column heading: FPBuffer Waits
- FPBUFFER Steals
- See FPBFSTL
- FPCALLS
- Fast Path database call count. FP DB calls are Get Unique (GU), Get Next (GN), Get Next in
Parent (GNP), Get Hold Unique (GHU), Get Hold Next (GHN), Get Hold Next in Parent (GHNP), Insert
(ISRT), Delete (DLET), Replace (REPL), Field (FLD), and Position (POS). Fast Path resource usage
statistics are accurate, not approximations. Fast Path writes a 5937 syncpoint record for every
Message Processing Program (MPP) transaction that uses a Fast Path database.
Source: IMS
Column heading: FP Call Count
- FPCHGN
- The number of Fast Path Lock Change requests.
Source: IMS
Column heading: FPChange count
- FPCILWT
- Fast Path CI Lock IWAITs.
Source: IMS
Column heading: CI Lock WAITS
- FPCOMB
- Fast Path count of combinations logged.
Source: IMS
Column heading: FP COMB Count
- FPDB5950
- The number of associated Fast Path database update (type 5950) log records.
Source: IMS
Column heading: FP DBUpd count
- FPDDEPU
- The number of Direct Dependent Segment updates for the Fast Path database.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: DDEP Updates
- FPDECL
- Fast Path DEDB call count. DL/I calls to DEDB databases.
Source: IMS
Column heading: DEDB Calls
- FPDEGET
- Fast Path DEDB Get count.
Source: IMS
Column heading: DEDB Get Count
- FPDEPUT
- Fast Path DEDB Put count.
Source: IMS
Column heading: DEDB Put Count
- FPDEQ
- Fast Path DEDB Dequeue (DEQ) count.
Source: IMS
Column heading: FP DEQ Count
- FPDLET
- Fast Path database Delete (DLET) call count.
Source: IMS
Column heading: FP DLET Count
- FPFLD
- Fast Path Field (FLD) call count.
Source: IMS
Column heading: FLD Call Count
- FPGETS
- Fast Path database get call count. Fast Path DB get calls are Get Unique (GU), Get Next (GN),
Get Next in Parent (GNP), Get Hold Unique (GHU), Get Hold Next (GHN), Get Hold Next in Parent
(GHNP). Fast Path resource usage statistics are accurate, not approximations. Fast Path writes a
5937 syncpoint record for every MPP transaction that uses a Fast Path database.
Source: IMS
Column heading: FP Get Count
- FPGHN
- Fast Path database Get Hold Next (GHN) call count.
Source: IMS
Column heading: FP GHN Count
- FPGHNP
- Fast Path database Get Hold Next in Parent (GHNP) call count.
Source: IMS
Column heading: FP GHNP Count
- FPGHU
- Fast Path database Get Hold Unique (GHU) call count.
Source: IMS
Column heading: FP GHU Count
- FPGN
- Fast Path database Get Next (GN) call count.
Source: IMS
Column heading: FP GN Count
- FPGNP
- Fast Path database Get Next within Parent (GNP) call count.
Source: IMS
Column heading: FP GNP Count
- FPGNS
- Sum of Fast Path database Get Next (GN), Get Next in Parent (GNP), Get Hold Next (GHN) and Get
Hold Next in Parent (GHNP) calls.
Source: IMS
Column heading: FP GNx Count
- FPGU
- Fast Path database Get Unique (GU) call count.
Source: IMS
Column heading: FP GU Count
- FPGUS
- Sum of Fast Path database Get Unique (GU) and Get Hold Unique (GHU) calls.
Source: IMS
Column heading: FP GUx Count
- FPISRT
- Fast path database Insert (ISRT) call count.
Source: IMS
Column heading: FP ISRT Count
- FPLGCI
- Fast path count of whole control intervals (CIs) logged.
Source: IMS
Column heading: FP CI Count
- FPLOCK
- Number of Fast Path Lock requests.
Source: IMS
Column heading: FP Lock count
- FPMSCL
- Fast Path MSDB call count. DL/I calls to MSDB databases.
Source: IMS
Column heading: MSDB Calls
- FPNBFS
- The Fast Path normal buffer allocation (NBA) value specified in the region startup
procedure.
Source: IMS
Column heading: NBA Buffers
- FPNBFU
- Number of Fast Path normal buffer allocation (NBA) buffers used.
Source: IMS
Column heading: NBA Used
- FPNRDBFU
- Fast Path main storage database (MSDB) and sequential dependent segment (SDEP) buffers
used.
Source: IMS
Column heading: SDEP Buf Used
- FPOBFS
- The Fast Path overflow buffer allocation (OBA) value specified in the region startup
procedure.
Source: IMS
Column heading: OBA Buffers
- FPOBFU
- Number of Fast Path overflow buffer allocation (OBA) buffers used.
Source: IMS
Column heading: OBA Used
- FPOTELAP
- For transactions that update Fast Path DEDBs, the time taken to complete output thread (OTHREAD)
processing. OTHREAD is an asynchronous process that performs the updates to the Fast Path databases.
Depending on delays, OTHREAD can complete before or after the end of transaction processing, but
always independently. It is calculated as 5612 suffix STCK - TPCPCLCK.
Source: IMS
Column heading: Othread Time
- FPPBFU
- The number of private buffers used by High-Speed Sequential Processing (HSSP) or the High Speed
DEDB Direct Reorganization utility in a transaction (one unit of work).
Source: IMS
Column heading: PVT Buff Used
- FPPBFWT
- The number of waits for private buffers by High-Speed Sequential Processing (HSSP) or the High
Speed DEDB Direct Reorganization utility in a transaction (one unit of work).
Source: IMS
Column heading: PVT Buff Waits
- FPPH1PH2
- Sum of Fast Path Syncpoint Phase 1 and Phase 2 time.
Source: IMS
Column heading: PH1+PH2 FP Time
- FPPOS
- Fast Path Position (POS) call count.
Source: IMS
Column heading: POS Call Count
- FPPRCTYP
- Fast Path Process type from the 5937/38 log record. Reported values are:
- HSSP
- High-Speed Sequential Processing (HSSP)
- Non-HSSP
- Non-HSSP
- Data-Cap
- Data Capture Log written
- Abort
- APPL Abort (Sent DFS2766I)
- Java™
- JAVA Application
Source: IMS
Column heading: Process Type
- FPREPL
- Fast Path database Replace (REPL) call count.
Source: IMS
Column heading: FP REPL Count
- FPRLSE
- Fast Path Release Locks (RLSE) call count.
Source: IMS
Column heading: FP RLSE Count
- FPRTCODE
- Fast Path Routing Code.
Source: IMS
Column heading: Routing Code
- FPSDEPCI
- Commit sequential dependent segment (SDEP) control interval (CI) number used.
Source: IMS
Column heading: Commit SDEP CIs
- FPSDEPI
- The number of sequential dependent segment (SDEP) inserts for the Fast Path database.
A transaction can update more than one database. In this case there will be additional report lines for each database used by the transaction.
Recommendation: When requesting this field, also include the DATABASE field in the form. This will identify the database to which this field applies.Source: IMS
Column heading: SDEP Inserts
- FPSDEPSG
- Commit sequential dependent segment (SDEP) segments used.
Source: IMS
Column heading: Commit SDEP Seg
- FPSEMHQI
- Fast Path shared expedited message handler (EMH) queue input time. Shared EMHQ input time is the
elapsed time a transaction input message spends on the shared EMH queue.
Source: IMS
Column heading: SEMHQ Input
- FPSEMHQO
- Shared expedited message handler (EMH) queue output time is the elapsed time a transaction
output message spends on the shared EMH queue.
Source: IMS
Column heading: SEMHQ Output
- FPSYNCCT
- The number of Fast Path synchronization points for a transaction. This value is a count of the
following IMS log records for a transaction:
- X'5937' Fast Path synchronization point operation completed
- X'5938' Fast Path synchronization point operation was unsuccessful
Source: IMS
Column heading: FP SyncP Count
- FPTOTIME
- Fast Path Terminal Output time. Terminal output time is the elapsed time that the Fast Path
transaction output message took to be sent to the terminal.
Source: IMS
Column heading: OutTermQ Time
- FPUNLK
- The number of Fast Path Unlock requests.
Source: IMS
Column heading: FPUnlock count
- FPUOWLWT
- Fast Path UOW Lock IWAITs.
Source: IMS
Column heading: UOW Lock WAITS
- FPUPDATS
- Fast Path database update call count. Fast Path database update calls are Insert (ISRT), Delete
(DLET), and Replace (REPL). Fast Path resource usage statistics are accurate, not approximations.
Fast Path writes a 5937 syncpoint record for every MPP transaction that uses a Fast Path
database.
Source: IMS
Column heading: FP Updat Count
- FPVSORFD
- Virtual Storage Option (VSO) reads from dataspace. The number of control interval (CI) read
requests satisfied from a dataspace or coupling facility structure.
Source: IMS
Column heading: VSO Read Dataspce
- FPVSREAD
- Virtual Storage Option (VSO) reads from DASD. The number of control intervals (CIs) read from
DASD into a dataspace or coupling facility structure.
Source: IMS
Column heading: VSO Read DASD
- FPVSWRIT
- Virtual Storage Option (VSO) writes to DASD. The number of control intervals (CIs) with updates
to a dataspace or coupling facility structure. This number represents the number of CIs that would
have been sent to the output thread (OTHREAD) if the areas were non-VSO.
Source: IMS
Column heading: VSOWrite DASD
- FPWAITS
- Fast Path database wait count. Fast Path database waits include waits for data entry database
(DEDB) buffers, control interval (CI) locks, and unit of work (UOW) locks. Fast Path resource usage
statistics are accurate, not approximations. FP cuts a 5937 syncpoint record for every MPP
transaction that uses a Fast Path database.
Source: IMS
Column heading: FP Wait Count
- FPWTNOC
- Fast Path IRLM internal suspend count, or suspends not related to lock requests.
Source: IMS
Column heading: FP IRLM Susp Cnt
H
- HWSID
- IMS Connect system name.
Source: IMS Connect
Column heading: Connect System
I
- ICALCNT
- Sync Callout Message count. The number of IMS calls (DL/I ICAL calls) made by this transaction. This number is taken from either the
application terminate accounting (log code 07) record or the transaction-level statistics (log code
56FA) record.
Source: IMS
Column heading: ICAL Count
- IMSACK
- IMS acknowledgment indicator. Indicates
how the IMS Connect transaction was
acknowledged by IMS. Reported values are:
- ACK
- IMS positively acknowledged (ACK)
- NAK
- IMS negatively acknowledged (NAK)
- blank
- Transaction was not acknowledged by IMS
Source: IMS Connect
Column heading: IMS ACK
- IMSID
- Processing IMS ID. IMS subsystem ID where the transaction was processed. Source: IMSTip: To control the source of the IMS Processing ID, see Log Global Options in the IMS Performance Analyzer User's Guide.
Column heading: Proc IMS ID
IMS Problem Investigator global field: IMSID
- IMS log DD name
- See DDNAME
- IMSRel
- See IMSVER
- IMS Resp Time
- See RESPIMS
- IMS RTp Time
- See OUTRTIMS
- IMS RTp Tot Time
- See TOTRTIMS
- IMS Tran Start
- See STARTIMS
- IMSVER
- Processing IMS Version. IMS Version of the system where the IMS transaction was processed.
Source: IMS
Column heading: Proc Vers
IMS Problem Investigator global field: IMSRel
- Input Msg Len
- See MSGLIN
- INPUTQ
- Input queue time. The elapsed time from when the input message is enqueued onto the message
queue (01/35) to when the program starts processing the transaction (31 DLI).
Source: IMS
Column heading: InputQ Time
- INREAD
- Input read Socket time. The elapsed time taken for IMS Connect to read the incoming message from when the transaction input
message enters IMS Connect (Read Prepare) to
when IMS Connect has completed reading the
message (final Read Socket).
Source: IMS Connect
Column heading: ReadSock In Time
- IPADDR
- Client IP address, either IPv4 dot-decimal notation or IPv6 format.
Source: IMS Connect
Column heading: IP Address
J
- JOBNAME
- Job name of the dependent region that processed the transaction.
Source: IMS, ATF
Column heading: Jobname
L
- LOCKMAX
- The high water lock count for the Unit of Recovery. This shows the maximum number of locks held
at any one time by a transaction, and can provide an insight as to whether database contention could
be the cause of transaction delays. In the case of a non-message driven BMP, the value is an
aggregate count for the schedule, unless the
BMPSYNC(YES)
option is specified, in which case the lock count is for each BMP syncpoint interval. For a Fast Path transaction, the lock count is obtained from the x'5937' SYNCLKS field, otherwise the count is obtained from the x'3730' XFERLHLD field. In the case of an abended transaction the lock count is obtained from either the x'3801' QLRILHLD field or the x'5938' SYNCLKS field, depending on the transaction type.Source: IMS
Column heading: High Lock Cnt
- LOCKTIME
- Database Locking elapsed time, approximation only at completion level 5, accurate at completion
level 6. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: DB Lock Time
- LogToken
- See CONNLTOK
- LTERM
- Input LTERM. The logical terminal (LTERM) from where the incoming transaction was initiated. For
a generated message, the LTERM is unavailable and the Userid is reported.
Source: IMS, ATF
Column heading: Input LTERM
IMS Problem Investigator global field: LTerm
- LTERMOUT
- Output LTERM. The logical terminal (LTERM) to where the output message from the transaction is
sent.
Source: IMS
Column heading: Output LTERM
- LTERMOVR
- Override LTERM. Override logical terminal (LTERM) to where the output message from the
transaction is sent.
Source: IMS and IMS Connect
Column heading: Override LTERM
M
- MODE
-
Description: Transaction Mode indicator
Transaction Mode indicator. Specifies when database updates and non-express output messages are committed.
Reported values are:- M
- MODE=MULT transaction
- S
- MODE=SNGL transaction
- blank
- Not a message queue transaction
Note: The MODE keyword of the TRANSACT macro is equivalent to CMTMODE for the CREATE|UPDATE TRAN|TRANDESC dynamic definition commands.Source: IMS
- MSC
- Indicates whether the transaction involved Multiple Systems Coupling (MSC). Reported values are:
- FE
- Front-end MSC transaction, where the transaction originated.
- BE
- Back-end MSC transaction, where the transaction was processed.
- blank
- Not an MSC transaction.
Source: IMS
Column heading: MSC
- MSDB Calls
- See FPMSCL
- MSGLIN
- Input message length, including the message prefix. All type 01 records for the transaction
input messages are accumulated to obtain the total input message length.
Source: IMS, ATF
Column heading: Input Msg Len
- MSGLOUT
- Output message length, including the message prefix. All type 03 records for output messages
issued by the transaction are accumulated to obtain the total output message length.
Source: IMS, ATF
Column heading: Output Msg Len
N
O
- OBA Buffers
- See FPOBFS
- OBA Used
- See FPOBFU
- ODBALPSB
- ODBM allocate PSB elapsed time.
Source: IMS Connect
Column heading: Allocate PSB Time
- ODBCORTK
- ODBM correlation token.
Source: IMS Connect
Column heading: ODBM Correlation Token
- ODBDEPSB
- ODBM deallocate PSB elapsed time.
Source: IMS Connect
Column heading: Dealloc PSB Time
- ODBMNAME
- ODBM name.
Source: IMS Connect
Column heading: ODBM Name
- ODBMSGTM
- The elapsed time taken by all messages in the ODBM transaction.
Source: IMS Connect
Column heading: ODBM Msg Time
- OLR
- Indicates that a batch message processing (BMP) region is scheduled for Online Reorganization.
Reported values are:
- Y
- BMP is scheduled for Online Reorg
- N
- Not an Online Reorganization (OLR) BMP
- -
- Unknown
Source: IMS
Column heading: OLR
- ORGIMS
- IMS subsystem ID where the IMS transaction originated. Note: For shared queue transactions, the transaction was processed by the IMS subsystem in field IMSID.
Source: IMS and IMS Connect
Column heading: Org IMS ID
- ORGLTERM
- Originating LTERM. Input logical terminal (LTERM) of the originating transaction in the program
switch sequence. For the first transaction in a program switch sequence, ORGLTERM is the input
LTERM. For subsequent transactions in the program switch sequence, ORGLTERM will be blank for List
reports, and the originating LTerm for Summary reports.
Use ORGLTERM for Transit List-style reporting where you want to see the start of a program switch sequence, followed by the program switches in sequence.
ORGLTERM has special values for non-message driven transactions:- CICS-DBCTL
- CICS APPLID (taken from the IMS recovery token)
- BMP
- Job name
Source: IMS
Column heading: Org LTERM
- ORGRGTYP
-
Region type of the originating transaction in the program switch sequence. Reported values are:
- AER
- IMS Application Execution Region (AER)
- BAT
- Batch Application
- BMP
- Batch message processing (BMP) region
- DBC
- IMS DBCTL region
- IFP
- IMS Fast Path Message-Driven region
- JBP
- Java batch processing (JBP) region
- JMP
- Java message processing (JMP) region
- MPP
- Message processing program (MPP) region
- MSC
- Multiple Systems Coupling (MSC) transaction sent to a remote IMS system for processing
- ODB
- Open Database (ODBM/ODBA)
- SWI
- Message switch or generated output message, not a transaction
- TRK
- Tracking thread
- UTI
- Utility
Source: IMS
Column heading: Org Reg
- ORGTRAN
- Transaction Code of the originating transaction in the program switch sequence. Tip: Use ORGTRAN, PARTRAN, TRANCODE and PGMSWIT (hidden) as keys for Form-based summary reporting when transit analysis is required. IMS Performance Analyzer will summarize transaction transit activity by grouping all transactions involved in program switching, in the sequence that they are processed. For an example of this kind of report, see SWITSUMM : Program Switch Summary summary report.
Source: IMS and IMS Connect
Column heading: Org Trancode
- ORGUOWID
- Originating tracking unit of work (UOW) ID. Only the tracking token is reported, as this
uniquely identifies a transaction in a sysplex. Tip: Field ORGIMS contains the UOW originating IMS subsystem ID.
Source: IMS
Column heading: Originating UOW ID
IMS Problem Investigator global field: OrgUOWID
- ORGVER
- Version of the IMS where the transaction originated.
Source: IMS
Column heading: Org Vers
- ORIGDS
- Original IMS data store ID. For Open Transaction Manager
Access (OTMA) workloads in IMS Connect, this is the name of the
IMS data store specified in the IMS destination ID field (IRM_IMSDESTID) of the IMS request message (IRM). See also
TARGDS.
Source: IMS Connect
Column heading: Original Datastor
- Orig Tmember
- See TMEMBERO
- OSAMREAD
- Overflow sequential access method (OSAM) data set read IO count, approximation only at
completion level 5, accurate at completion level 6. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: OSAMRead Count
- OSAMWRIT
- Overflow sequential access method (OSAM) data set write IO count, approximation only at
completion level 5, accurate at completion level 6. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: OSAMWrit Count
- OTHREAD Buffers
- See FPBFOTHR
- OTMA
- Indicates whether the transaction originated from Open Transaction Manager Access (OTMA).
Reported values are:
- CONNECT
- Transaction originated from OTMA via IMS Connect.
- MQ
- Transaction originated from OTMA via IBM MQ.
- OTMA
- Transaction originated from OTMA via an unknown client.
- blank
- Transaction did not originate from OTMA.
Source: IMS
Column heading: OTMA
- OTMAconf Time
- See CONFOTMA
- OTMADlay Time
- See DLAYOTMA
- OTMAproc Time
- See PROCOTMA
- OUTALIAS
- Target ODBM alias name. For Open Database workloads in IMS Connect, this is the name of the ODBM
alias that processed the request. See also
ALIAS
Source: IMS Connect
Column heading: Out Alias
- OUTDEQ
- The number of output messages sent (dequeued) by the transaction. Tip: Outstanding output messages can fill up the message queue, causing IMS to fail. Use OUTDEQ with OUTENQ to ensure that output messages issued by transactions are being sent to the destination LTERM (dequeued).
Source: IMS
Column heading: Out DEQ Count
- OUTENQ
- The number of output messages issued (enqueued) by the transaction.Tip: Outstanding output messages can fill up the message queue, causing IMS to fail. Use OUTENQ with OUTDEQ to ensure that output messages issued by transactions are being sent to the destination LTERM (dequeued).
Source: IMS
Column heading: Out ENQ Count
- OUTODBNM
- ODBM name.
Source: IMS Connect
Column heading: Output ODBMName
- OUTPUTG
- SMQ global output queue time. The elapsed time from when the output message is put onto the
shared message queue (SMQ) by the back-end system to when it is read off the queue by the front-end
system.
Source: IMS
Column heading: SMQ Glob OutQTime
- OUTPUTL
- SMQ local output queue time. The elapsed time from when the output message is read from the
shared message queue (SMQ) to when it is sent to the output logical terminal (LTERM).
Source: IMS
Column heading: SMQ Locl OutQTime
- Output LTERM
- See LTERMOUT
- Output Msg Len
- See MSGLOUT
- OUTPUTQ
- Output queue time. The elapsed time from when the transaction ends to when the output message is
sent back to the logical terminal (LTERM).
Source: IMS
Column heading: OutputQ Time
- OUTRTCON
- IMS Connect Resume-Tpipe time. Calculated
as the elapsed time between the IMS Connect 48 Trigger Event that terminates the Send-Only Connect
transaction and the subsequent IMS Connect 42 OTMA Message Received Event after the Resume-Tpipe
transaction has commenced.
Source: IMS Connect
Column heading: Conn RTp Time
- OUTRTIMS
- IMS Resume Tpipe output time. The elapsed
time from when the transaction output message is queued and eligible to be sent (transaction 35
COMMS when QLNQCTMP=0, otherwise 3730) to when the output message is sent to its final destination
(transaction 31 COMMS).
Source: IMS
Column heading: IMS RTp Time
- OutTermQ Time
- See FPTOTIME
P
- P2P
- Program-switch indicator. Indicates whether the transaction is a program switch. The reported
values are:
- Y
- Program switch transaction.
- N
- Not a program switch transaction, but may be the originating transaction in a program switch sequence.
- -
- Unknown. Typically a SL=2 transaction started with a type 31 (DLI GU) record.
Source: IMS
Column heading: P2P
- PARRGTYP
-
Region type of the parent transaction in a program switch sequence. Reported values are:
- AER
- IMS Application Execution Region (AER)
- BAT
- Batch Application
- BMP
- Batch message processing (BMP) region
- DBC
- IMS DBCTL region
- IFP
- IMS Fast Path Message-Driven region
- JBP
- Java batch processing (JBP) region
- JMP
- Java message processing (JMP) region
- MPP
- Message processing program (MPP) region
- MSC
- Multiple Systems Coupling (MSC) transaction sent to a remote IMS system for processing
- ODB
- Open Database (ODBM/ODBA)
- SWI
- Message switch or generated output message, not a transaction
- TRK
- Tracking thread
- UTI
- Utility
Source: IMS
Column heading: Par Reg
- PARTOKEN
- The last 8 hexadecimal bytes (unique part) of the IMS unit of recovery token of the parent
transaction in the program switch sequence, identifying the system where the parent transaction is
processed. For CICS-DBCTL only, the recovery token ends in the 8-byte RMUOWID (a STCK value). Tip: To report the full recovery token, use PARTOKEN with PARTOKID.
Source: IMS
Column heading: Parent Rectoken
- PARTOKID
- The first 8 characters of the IMS unit of recovery token of the parent transaction in the
program switch sequence, identifying the system where the parent transaction is processed. For
CICS-DBCTL only, the first 8 characters of the recovery token is the CICS generic APPLID. Tip: To report the full recovery token, use PARTOKID with PARTOKEN.
Source: IMS
Column heading: Parent RecTokID
- PARTRAN
- The transaction code of the parent transaction in the program switch sequence.
Source: IMS
Column heading: Parent Trancode
- PGMSWIT
- Transaction number in program switch sequence. The sequence number of the transaction in the
program switch sequence. The originating transaction starts the sequence at position 0. Tip: Use ORGTRAN, PGMSWIT (hidden) and TRANCODE as keys for form-based summary reporting when transit analysis is required. IMS Performance Analyzer will summarize transaction transit activity by grouping all transactions involved in program switching, in the sequence that they are processed.
Source: IMS
Column heading: Prog Swit#
- PgmSwtch Time
- See SWITTIME
- PH1+PH2 Time
- See FPPH1PH2
- PORT
- IMS Connect TCP/IP port number.
Source: IMS Connect
Column heading: Port
IMS Problem Investigator global field: Port
- PORTDEP
- Port depth. The number of concurrently open sockets on the port from which the transaction was
received. This field can be used to monitor the socket usage at the time the individual transactions
were received by IMS Connect.
Source: IMS Connect
Column heading: Port Depth
- PORTTYPE
- Port type. Indicates whether a transaction is using a TCP/IP or local port connection. Reported
values are:
- T
- TCP/IP
- L
- Local
- blank
- Not an IMS Connect transaction
Source: IMS Connect
Column heading: Port Type
- POS Call Count
- See FPPOS
- POSTOTMA
- Total post-OTMA output time. For Sync Level NONE transactions, the elapsed time from when OTMA
completed processing the input message to when the transaction terminates (trigger event). For Sync
Level CONFIRM transactions, the elapsed time from when OTMA completed processing the ACK response to
when the transaction terminates (trigger event).
Source: IMS Connect
Column heading: PostOTMA Time
- PREOTMA
- Total pre-OTMA input time. The elapsed time from when the transaction input message enters IMS Connect (Read Prepare) to when the transaction
is sent to IMS (OTMA) for
processing.
Source: IMS Connect
Column heading: PreOTMA Time
- PRIORITY
- Transaction priority as specified in the TRANSACT macro PRTY parameter.
Source: IMS
Column heading: Pr
- PROCESS
- Processing time. The elapsed time the transaction spends processing in the dependent region.
Source: IMS
Column heading: Process Time
- Processing UOW ID
- See PROUOWID
- Process Start
- See STARTDEP
- Process Type
- See FPPRCTYP
- Proc IMS ID
- See IMSID
- PROCOTMA
- OTMA processing time. The elapsed time OTMA spent processing the transaction, from when the
message is sent to IMS (OTMA) to when the
response is received back from OTMA. Transaction messages are sent to OTMA for processing. For Sync
Level CONFIRM transactions, the ACK response from the client is also sent to OTMA for processing,
but this elapsed time is not included in OTMA procession time.
Source: IMS Connect
Column heading: OTMAproc Time
- PROGRAM
- Program or PSB name.
Source: IMS, ATF
Column heading: Program
IMS Problem Investigator global field: Program
- Program exec time
- See PROCESS
- Prog Swit#
- See PGMSWIT
- PROUOWID
- Processing tracking unit of work (UOW) ID.
Source: IMS
Column heading: Processing UOW ID
- PSBNAME
- PSB name.
Source: IMS Connect
Column heading: PSB Name
- PSTID
- The PST ID of the dependent region that processed the transaction.
Source: IMS
Column heading: PST
IMS Problem Investigator global field: Region
- PVT Buff Used
- See FPPBFU
- PVT Buff Waits
- See FPPBFWT
Q
- QCMDDEQ
- The number of DL/I queue command dequeues.
Source: IMS
Column heading: Q Cmd Dequeues
- QCMDENQ
- The number of DL/I queue command enqueues.
Source: IMS
Column heading: Queue Type
- QCMDWAIT
- The number of DL/I waits on queue command enqueues.
Source: IMS
Column heading: Queue Type
- QTYPE
- Message queue type. Indicates the type of message queue from where the transaction was taken to
be processed. Reported values are:
- MSGQ
- IMS message queue
- LOCALF
- Local-first (always processed by the same system where the message was queued)
- LOCAL
- IMS shared message queue (SMQ) processed locally by the front-end IMS system
- GLOBAL
- IMS shared message queue (SMQ) processed globally by another back-end IMS system
- NONMSG
- Non-message driven BMP
- CPI-CI
- CPI-CI APPC transaction scheduled in message region
Tip: Use QTYPE with TRANCODE as keys for form-based summary reporting when transit analysis of input queue time is required. For shared message queues, you will be able to compare input queue times for globally and locally processed transactions.Source: IMS
Column heading: Queue Type
R
- R0TIME
- Internal application response time. The sum of the input queue time and processing
time.
Source: IMS
Column heading: ApplResp Time(R0)
- R1TIME
- Total response time. The sum of the input queue time, processing time, and output queue time.
Source: IMS
Column heading: Tot Resp Time(R1)
- RATEMIN
- Transaction rate / Minute. For form-based summary reporting only, the transaction rate per
minute.
Source: IMS and IMS Connect
Column heading: Rate/Min
- RATESEC
- Transaction rate / Second. For Form-based summary reporting only, the transaction rate per
second.
Source: IMS and IMS Connect
Column heading: Rate/Sec
- READEXIT
- Read message Exit time. The elapsed time the input message spent being processed by the READ
Message Exit. For Sync Level NONE transactions, the READ Message Exit is called once for the input
message. For Sync Level CONFIRM transactions, the READ Message Exit is called twice, initially for
the input message and a second time for the ACK response from the client.
Source: IMS Connect
Column heading: ReadExit Time
- ReadSock Ack Time
- See ACKREAD
- ReadSock In Time
- See INREAD
- RECOVER
- Recoverable transaction indicator. Indicates whether a transaction is recoverable or
non-recoverable as defined in the TRANSACT macro INQUIRY parameter. Reported values are:
- R
- Recoverable
- N
- Non-recoverable
- blank
- Not a message queue transaction
Source: IMS
Column heading: Rec
- RECTOKEN
- The last 8 hexadecimal bytes (unique part) of the 16-byte IMS unit of recovery token that uniquely identifies a unit of work. The
reported value consists of the following fields:
- OASN
- 4-byte origin application sequence number assigned at schedule time. OASN is unique and reset back to zero at cold start.
- COMN
- 4-byte commit number initialized to zeros and incremented each time the application goes through commit processing.
Tip: To report the full recovery token, use RECTOKEN with RECTOKID.Source: IMS, ATF
Column heading: Recovery Token
IMS Problem Investigator global field: RecToken
- RECTOKID
- The first 8 characters of the IMS unit of
recovery token containing the ID of the IMS subsystem where the transaction is processed. For CICS-DBCTL only, CICS
generic APPLID is reported from first 8 bytes of the CICS-generated recovery token.Tip: To report the full recovery token, use RECTOKID with RECTOKEN.
Source: IMS, ATF
Column heading: Recovery Token ID
- Region
- See PSTID
- REGOCCUP
- Region occupancy time. The elapsed time that an MPP transaction spends in the dependent region,
from when it is scheduled, or starts processing, to when the next transaction is eligible for
processing.
Source: IMS
Column heading: Region Occ Time
- REGTYPE
- Region type.
The type of region that processed the transaction. Reported values are:
- AER
- IMS Application Execution Region (AER)
- BAT
- Batch Application
- BMP
- Batch message processing (BMP) region
- DBC
- IMS DBCTL region
- IFP
- IMS Fast Path Message-Driven region
- JBP
- Java batch processing (JBP) region
- JMP
- Java message processing (JMP) region
- MPP
- Message processing program (MPP) region
- MSC
- Multiple Systems Coupling (MSC) transaction sent to a remote IMS system for processing
- ODB
- Open Database (ODBM/ODBA)
- SWI
- Message switch or generated output message, not a transaction
- TRK
- Tracking thread
- UTI
- Utility
Note: To report on CPI, see APPC.Source: IMS
Column heading: Reg Typ
- REJECT
- Transaction rejected indicator. Indicates whether an IMS Connect transaction has been rejected. Reported values are:
- R
- Transaction rejected
- blank
- Transaction not rejected
Source: IMS Connect
Column heading: Rej
- REROUTNM
- IMS Connect Reroute name. The name used on a NAK Reroute request to specify the new destination
for the message that is to be negatively acknowledged.
Source: IMS Connect
Column heading: Reroute Name
- RESPCON
- Connect response time. The elapsed time from when the transaction input message enters IMS Connect (Read Prepare) to when the transaction
terminates (trigger event).
Source: IMS Connect
Column heading: CON Resp Time
- RESPIMS
- IMS response time. IMS transaction end-user response time. The elapsed time from
when the input transaction is enqueued by IMS
(01/35) to when the response is sent back to the originating LTERM (31 Communications). Only
transactions that respond back to their originating LTERM incur a response time. Responses may occur
prior to the completion of program execution time resulting in a response time less than the total
transaction time. Tip: To analyze all transactions from end-to-end, regardless of their response destination, use field TOTALTM.
Source: IMS
Column heading: IMS Resp Time
- RESPMODE
- Response mode indicator. Indicates whether a transaction is response mode or not. Reported
values are:
- R
- Response mode
- N
- Not response mode
- blank
- Not a message queue transaction
Source: IMS
Column heading: Resp Mode
- Resp time
- See RESPIMS
- RESUMETP
- Resume Tpipe indicator. Indicates whether IMS Connect uses a resume Tpipe to request asynchronous output data from IMS during a transaction. Reported values are:
- R
- Resume Tpipe is used
- N
- Resume Tpipe is not used
- blank
- Not an IMS Connect transaction
Source: IMS Connect
Column heading: Resum Tpipe
IMS Problem Investigator global field: ResumeTP
- Resume Tpipe Orig Msg Token
- See CONNOTOK
- Routing Code
- See FPRTCODE
- RXMLEXIT
- XML Adapter message Exit time. The elapsed time the input message from the XML Adapter spent
being processed by the READ Message Exit.
Source: IMS Connect
Column heading: RXMLExit Time
- R0TIME
- Internal Application Response time. The sum of the input queue time and processing
time.
Source: IMS
Column heading: ApplResp Time(R0)
- R1TIME
- Total Response time. The sum of the input queue time, processing time, and output queue
time.
Source: IMS
Column heading: Tot Resp Time(R1)
S
- SAF Call Time
- See SAFTIME
- SAFTIME
- SAF security call time. The accumulated elapsed time spent in all SAF calls for the
message.
Source: IMS Connect
Column heading: SAF Call Time
- SCHEDTM
- Schedule time. Schedule time is taken from the LINTMSCH field of the IMS Application Start (08)
record. If the (08) does not contain a valid LINTMSCH value then, for a Message Region, it is the
elapsed time from when the application program starts (08) to when the input message processing
starts (31 DLI).
Source: IMS, ATF
Column heading: Schedule Time
- SCHEDTYP
-
Description: Schedule type.
Reported values are:- REAL
-
Real schedule - first transaction only is counted.
- QUICK
-
Quick re-schedule - first transaction only is counted.
- FALSE
-
False schedule
- Blank
-
Unknown, or not the first transaction in schedule.
Note: For FALSE schedules to be reported, Form-based Transit option 'False schedules' must be set to 2 (YES).Source: IMS
- SCHEDWIC
- Wait time for Intent Conflict, taken from the LINTMINT field of the IMS Application Start (08) record.
Source: IMS
Column heading: Schedule WIC Time
- SCHEDWPS
- Wait time for Pool Space, taken from the LINTMPOL field of the IMS Application Start (08) record.
Source: IMS
Column heading: Schedule WPS Time
- SCOACKCT
- Sync Callout ACK count. The number of Sync callout ACK events attributed to the transaction.
See also
SCOACKTM.
Source: IMS
Column heading: SyncCout ACK Cnt
- SCOACKTM
- Sync Callout ACK time. The elapsed time from when the Sync Callout message is sent to when the
ACK is received (YOUT-YACK). If the transaction issued more than one ICAL call, then this field
contains the sum of all ACK times. The count of ACK times is available in SCOACKCT.
Source: IMS
Column heading: SyncCout ACK Time
- SCOCALCT
- Sync Callout Response count. The number of ICAL calls issued by the transaction that recorded a
response time. See also
SCOCALTM.
Source: IMS
Column heading: SyncCout Resp Cnt
- SCOCALTM
- Sync Callout Total time. The elapsed time from when the Sync Callout message is sent to when the
Response (YOUT-YRSP) or a NAK (YOUT-YNAK) is received back. If the transaction issued more than one
ICAL call, then this field contains the sum of all elapsed times. The count of Total Response times
is available in SCOCALCT.
Source: IMS
Column heading: SyncCout RespTime
- SCOEXTCT
- Sync Callout External Response count. The total number of Sync Callout external acknowledgments
or responses processed by the transaction. See also
SCOEXTTM.
Source: IMS
Column heading: SyncCout XRsp Cnt
- SCOEXTTM
- Sync Callout External Response time. The elapsed time from when the Sync Callout ACK is received
to when either the Response (YOUT-YRSP) or a NAK (YOUT-YNAK) is received. If the transaction issued
more than one ICAL call, then this field contains the sum of all elapsed times. The count of
External Response times is available in SCOEXTCT.
Source: IMS
Column heading: SyncCout XRspTime
- SCONAKCT
- Sync Callout NAK count. The number of Sync callout ACK events attributed to the transaction.
See also
SCONAKTM.
Source: IMS
Column heading: SyncCout NAK Cnt
- SCONAKTM
- Sync Callout NAK time. The elapsed time from when the Sync Callout message is sent to when the
NAK is received (YOUT-YNAK). If the transaction issued more than one ICAL call, then this field
contains the sum of all NAK times. The count of NAK times is available in SCONAKCT.
Source: IMS
Column heading: SyncCout NAK Time
- SCOTPIPE
- Sync Callout TPipe name. TPipe name derived from the IMS x'6701' YOUT Sync Callout
record.
Source: IMS
Column heading: Callout TPipe
- SDEP Buf Used
- See FPNRDBFU
- SECCHK
- Highest security check code returned from an ODBM command.
Source: IMS Connect
Column heading: Sec Code
- SEMHQ Input
- See FPSEMHQI
- SEMHQ Output
- See FPSEMHQO
- SMQ Glob OutQTime
- See OUTPUTG
- SMQ Locl OutQTime
- See OUTPUTL
- SOCKET
- Socket number.
Source: IMS Connect
Column heading: Sock Num
- SOCKTYPE
- Socket type.
- N
- Non-persistent socket
- P
- Persistent socket
- T
- Transaction socket
- blank
- Unknown
Source: IMS Connect
Column heading: Sock Type
- STARTCON
- Connect transaction start time. The time of day when the transaction input message enters IMS Connect (Read Prepare).
Source: IMS Connect
Column heading: CON Tran Start
- STARTDEP
- IMS transaction processing start. The time
of day when the IMS Full Function transaction
starts (31) or the time of day when the Fast Path transaction starts (5901+InputQ).
Source: IMS
Column heading: Process Start
- STARTIMS
- IMS transaction arrival time. The time of
day when the transaction input message is enqueued onto the IMS message queue with a type 01 (INPUT
MSG) or type 35 (MSG ENQ) record.
Source: IMS
Column heading: IMS Tran Start
- STARTLVL
- IMS transaction start level. Start level
is an attribute that IMS Performance Analyzer assigns to every transaction
reported in the IMS log. It is an indicator of
how far the transaction lifecycle has already progressed at the start of the IMS log. Together with Completion level (COMPLVL), Start
level is an indicator of the completeness of information collected about the reported transaction.
The reported values are:
- 1
- Transaction started with a type 01 (INPUT MSG) or type 35 (MSG ENQ) record generated when the transaction was added to the IMS Message Queue.
- 2
- Transaction started with a type 31 (DLI GU) record generated when the transaction was retrieved from the IMS Message Queue for processing.
- 3
- Transaction generated for a Non-message driven BMP or Thread process where the type 08 Application Start record is not available but dependent region processing has commenced.
Source: IMS
Column heading: Start Level
- STEPNAME
- Region Stepname. The stepname of the dependent region that processed the transaction.
Source: IMS, ATF
Column heading: Stepname
- SVRCOD
- Highest severity code returned from an ODBM command.
Source: IMS Connect
Column heading: Svr Code
- SWITTIME
- Program switch time.
A program switch occurs when one transaction calls another by inserting a message (destination is an IMS scheduler message block (SMB)) onto the message queue. Program switch time is the elapsed time from when the program switch message is eligible for processing to when it actually starts processing in a dependent message processing region. This time is attributed to the program switch transaction, not the originating transaction, and is analogous to input queue time for transactions coming into IMS from VTAM® or OTMA.
Program-to-program (P2P) transactions are discrete transactions with their own units of recovery. Their processing eligibility depends on the type of IO PCB used to insert the message:
- For EXPRESS=YES alternate IO PCB, the P2P transaction is immediately eligible for processing (asynchronously). SWITTIME is from the enqueue of the input message (35) to the start of processing (31 DLI).
- Otherwise for IO PCB, the P2P transaction cannot start until the parent completes syncpoint phase 1 processing. SWITTIME is from syncpoint phase 2 when the message is transferred from the temporary hold queue to its permanent destination (37) to the start of processing (31 DLI).
Source: IMS
Column heading: PgmSwtch Time
- SYNCELAP
- Syncpoint total elapsed time (phases 1 and 2). The time reported depends on the following:
- For all Fast Path transactions this is X'5936'.FLDQPRTS if available, otherwise X'5937'.SYNCPRTM.
- For all other transactions this is X'5610' to X'5612', except when X'5937'.SYNCOTHR > 0 then it is X'5610' to X'5937'.
Note: The required log records are not always available in the log. In this case, the time reported may be the value reported for Phase 1 or Phase 2 only.Source: IMS
Column heading: Syncpt Time
- SYNCFAIL
- Fast Path Syncpoint Failure code from the 5938 log record.
Source: IMS
Column heading: Sync Fail
- SYNCLEV
- OTMA synchronization level. Reported values are:
- NONE
- Synch Level=NONE. No acknowledgment is required from the client.
- CONFIRM
- Synch Level=CONFIRM. The client is required to acknowledge.
- SYNCH
- Sync Level=SYNCH. Two-phase commit processing is required.
- blank
- Not an OTMA transaction.
Source: IMS and IMS Connect
Column heading: Synch Level
- SYNCPH1E
- Syncpoint phase 1 elapsed time, measured as the time between the X'5610' and X'3730' log
records. Note: The required log records are not always available in which case the time will be reported as not available.
Source: IMS
Column heading: Sync PH1 Time
- SYNCPH2E
- Syncpoint phase 2 elapsed time.
- For all Fast Path transactions this is the value reported in log record field X'5936'.FLDQPRTS (if available), otherwise the value in X'5937'.SYNCPRTM is reported.
- For all other transactions this is the time between the X'3730' and X'5612' log records, except when the value in log record X'5937'.SYNCOTHR is greater than 0 in which case the time between log records X'3730' and X'5937' is used.
Note: The required log records are not always available in which case the time will be reported as not available.Source: IMS
Column heading: Sync PH2 Time
- SYNCPH2F
- Syncpoint phase 2 elapsed time for Fast Path only. For all non-IFP transactions that use Fast
Path this is the time between log records X'3730' and X'5937/38'. For all Fast Path transactions
this is the time reported in log record field X'5936.FLDQPRTS' (if available), otherwise the value
in log record field X'5937.SYNCPRTM' is used.Note: The required log records are not always available in which case the time will be reported as not available.
Source: IMS
Column heading: Sync PH2 FP Time
- SYNCTIME
- The time of day when the IMS Full Function
transaction or Fast Path transaction ends (5612).
Source: IMS
Column heading: Syncpoint Time
T
- TARGDS
- Target IMS data store. For OTMA workloads from IMS Connect, this is the name of the IMS data store that processed the request. See also
ORIGDS.
Source: IMS Connect
Column heading: Target datastor
- TERMINAL
- VTAM Node name or BTAM Line/PTERM number. When neither
VTAM or BTAM, TERMINAL may be reported as:
- For implicit APPC transactions, network ID (LUP_NETWORK_ID)
- For OTMA transactions, Tpipe name (TMAMCTNM)
- For MSC transactions, origin LTERM (MSGMSINM)
Source: IMS
Column heading: Terminal
IMS Problem Investigator global field: Terminal
- TESTDEQ
- The number of DL/I test dequeues.
Source: IMS
Column heading: Test Dequeues
- TESTENQ
- The number of DL/I test enqueues.
Source: IMS
Column heading: Test Enqueues
- TESTWAIT
- The number of DL/I waits on test enqueues.
Source: IMS
Column heading: Waits on Test Enq
- TIMEOUT
- Transaction timeout indicator. Indicates whether an IMS Connect transaction has timed-out. Reported values are:
- T
- Transaction timed-out
- blank
- Transaction did not time out
Source: IMS Connect
Column heading: Time Out
- TIMERV
- Transaction timer value. This value, set by the client in the IMS request message (IRM) header,
is the time IMS Connect will wait for a
response from OTMA before timing out. The time is reported in microseconds. Use the SECGROUP
operand to report values in seconds in the range 0 (no wait option) to 4200 (70 mins), or 9999
to wait forever. Tip: Use the TIMEOUT field to indicate whether the IMS Connect transaction did time out.
Source: IMS Connect
Column heading: Transact Timer
- TMEMBERD
- Destination OTMA Tmember name. IMS XCF queue which delivers the message to IMS Connect.
Source: IMS Connect
Column heading: Dest Tmember
- TMEMBERO
- Originating OTMA Tmember name. IMS Connect
XCF queue which will return the message to IMS.
Source: IMS
Column heading: Orig Tmember
- Total IMS Time
- See TOTALTM
- Total IO Count
- See DBIOCALL
- Total time
- See TOTALTM
- TOTALTM
- Total transaction elapsed time. The total elapsed time that the transaction incurs in message
queues and being processed by IMS. For
self-contained transactions, or the initial transaction in a program switch sequence, total time
consists of input queue, processing and output queue times. For subsequent transactions in a program
switch sequence, total time consists of switch time, processing time and output queue time.
Source: IMS
Column heading: Total IMS Time
- Tot Resp Time(R1)
- See R1TIME
- TOTRTIMS
- Resume Tpipe total time. The elapsed time from when the input message arrives (01/35) to when
the Resume Tpipe takes the output message and sends it to its final destination (RTPIPE 31 COMMS).
This time is useful for transactions that use SENDONLY RESUME-TPIPE protocol – it measures the
overall time in IMS that contributes to
end-user response time.
Source: IMS
Column heading: IMS RTp Tot Time
- TPIPE
- IMS Connect Tpipe name derived from IMS
Connect Extensions journal 41 record field CERE_41_TPIPE_NAME.
Source: IMS Connect
Column heading: Tpipe
- TRANCNT
- Transaction count. For Form-based summary reporting only, the number of transactions that were
accumulated in this key range.
When TRANCNT is used in combination with fields that report on database activity or external subsystems, additional report lines are produced that provide a count for each database or external subsystem affected by the transaction. If requested, a summary line is also produced that reports on the total number of transactions. As transactions can update more than one database, or more than one external subsystem, the total in the summary line will not necessarily be the sum of counts listed above.
In the following example, the total number of transactions ( A ) does not equal the sum of counts for each database as some transactions have accessed more than one database.Database Tran Trancode DBD Name Count IVTNO - 4 IVTNO IVPDB1 7 IVTNO IVPDB1I 6 IVTNO 11 A
Fields that report on database activity: DATABASE, DBACMETH, DBBLKDEL, DBBLKINS, DBBLKREP, DBBLKUPD, DBORGTYP, DBUPRATE, DEDBAREA, FPDDEPU, FPSDEPI
Fields that report on external subsystems: ESAFNAME, ESAFCALL, ESAFCCON, ESAFCOMT, ESAFPRE
See also ABENDCNT
Source: IMS and IMS Connect
Column heading: Tran Count
- TRANCODE
- Transaction code. For CICS-DBCTL only, the CICS transaction code is reported. Otherwise, the IMS
transaction code is reported.
Source: IMS and IMS Connect
Column heading: Trancode
IMS Problem Investigator global field: TranCode
- Transact Timer
- See TIMERV
U
- UORTIME
- Unit-of-recovery () time, or in other words, the elapsed time the transaction spends
processing in the dependent region. IMS Performance Analyzer
calculates the time as the difference between the IMS X’5612’ and X’5607’ log
records.Note: UOR time is similar to Processing Time, the difference for an MPP transaction is:
- UOR time starts when the IMS unit-of-recovery commences (5607).
- Processing time starts when the MPP transaction gets the input message from the message queue (31 DLI), usually after the commencement of the .
Source: IMS
Column heading: Time
- UOW Lock WAITS
- See FPUOWLWT
- UPDDEQ
- The number of DL/I update dequeues.
Source: IMS
Column heading: Update Dequeues
- UPDENQ
- The number of DL/I update enqueues.
Source: IMS
Column heading: Update Enqueues
- UPDWAIT
- The number of DL/I waits on update and enqueues.
Source: IMS
Column heading: Waits on Upd Enq
- USERID
- User ID. RACF® user ID, or substitute as used by IMS for security purposes.
Source: IMS, IMS Connect, and ATF
Column heading: Userid
IMS Problem Investigator global field: Userid
V
- VSAMREAD
- VSAM read IO count, approximation at completion level 5, accurate at completion level 6. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: VSAMRead Count
- VSAMWRIT
- VSAM write IO count, approximation at completion level 5, accurate at completion level 6. At completion level 5, resource
usage metrics are obtained from the type 07 application termination record and
apportioned equally among all transactions that executed under that schedule,
regardless of their respective processing times. At completion level 6, resource
usage metrics are obtained from the type 56FA transaction accounting
record.
Source: IMS
Column heading: VSAMWrit Count
- VSO Read DASD
- See FPVSREAD
- VSO Read Dataspce
- See FPVSORFD
- VSOWrite DASD
- See FPVSWRIT
W
- WFITIME
- WFI elapsed time. SUBQ6 time where the message region waited before the next WFI transaction
starts processing. Important: IMS only records SUBQ6 time to a precision of 0.1 seconds.
Source: IMS
Column heading: WFI Time
X
- XMITEXIT
- Transmit message Exit time. The elapsed time output messages (responses) spent being processed
by the XMIT Message Exit.
Source: IMS Connect
Column heading: XmitExit Time
- XMLADAPT
- XML Adapter name. The name of the XML Adapter passed by the SOAP Gateway.
Source: IMS Connect
Column heading: XML Adapter
- XQRYCOPY
- The number of XQuery COPY calls.
Source: IMS
Column heading: Xquery COPY Cnt
- XQRYRSTR
- The number of XQuery RSTR calls.
Source: IMS
Column heading: Xquery RSTR Cnt
- XQRYSAVE
- The number of XQuery SAVE calls.
Source: IMS
Column heading: Xquery SAVE Cnt