home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
cicspa2.zip
/
5764-091.INF
(
.txt
)
next >
Wrap
OS/2 Help File
|
1995-09-28
|
190KB
|
3,999 lines
ΓòÉΓòÉΓòÉ 1. CICS for OS/2 Performance Analyser User's Guide ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 2. Version Notice ΓòÉΓòÉΓòÉ
Sixth Edition, September 1995
This edition applies to Version 1.2.1 of CICS for OS/2 Performance Analyser,
program number 5764-091 and to all subsequent releases and modifications until
otherwise indicated in new editions.
A form for reader's comments is provided at the back of this publication. If
the form has been removed, address your comments to:
IBM United Kingdom Laboratories
Transaction Systems Marketing Support (MP207)
Hursley Park
Hursley
Hampshire, SO21 2JN, England
When you send information to IBM, you grant IBM a non-exclusive right to use or
distribute the information in any way it believes appropriate without incurring
any obligation to you. You may continue to use the information that you
supply. Copyright International Business Machines Corporation 1995. All rights
reserved.
Note to U.S. Government Users - Documentation related to restricted rights -
Use, duplication or disclosure is subject to restrictions set forth in GSA ADP
Schedule Contract with IBM Corporation.
ΓòÉΓòÉΓòÉ 3. Notices. ΓòÉΓòÉΓòÉ
The following paragraph does not apply in any country where such provisions are
inconsistent with local law.
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore this statement may not apply to you.
References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates.
Any reference to an IBM licensed program or other IBM product in this
publication is not intended to state or imply that only IBM's program or other
product may be used. Any functionally equivalent program that does not
infringe any of the intellectual property rights may be used instead of the IBM
product. Evaluation and verification of operation in conjunction with other
products, except those expressly designated by IBM, is the user's
responsibility.
IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license
to these patents. You can send license inquiries, in writing, to the IBM
Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New
York 10594, USA.
The information contained in this document has not be submitted to any formal
IBM test and is distributed AS IS. The use of the information or the
implementation of any of these techniques is a customer responsibility and
depends on the customer's ability to evaluate and integrate them into the
customer's operational environment. While each item has been reviewed by IBM
for accuracy in a specific situation, there is no guarantee that the same or
similar results will be obtained elsewhere. Customers attempting to adapt
these techniques to their own environments do so at their own risk.
The following terms are trademarks of the International Business Machines
Corporation in the United States and/or other countries:
CICS
CICS for OS/2
IBM
Operating System/2
OS/2
Personal System/2
PS/2
DB2/2
The following terms are trademarks of other companies:
BTRIEVE
BTRIEVE Technologies
INTEL,Pentium
Intel Corporation
ΓòÉΓòÉΓòÉ 4. Preface ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 4.1. What is CICS for OS/2 Performance Analyser? ΓòÉΓòÉΓòÉ
CICS for OS/2 Performance Analyser (5764-091) is a statistics and monitoring
package for CICS for OS/2. It has been built to provide information on how CICS
transactions and resources are being used in a CICS for OS/2 Version 2.0
system.
It has six primary uses:
1. To provide routine performance management information in order to track the
number and response times of transactions over some standard interval of
time.
2. To provide information that will assist in the resolution of CICS for OS/2
performance problems.
3. To provide information for capacity planning purposes.
4. To provide application and transaction level trace so that the impact of
the application design can be understood at the CICS Application
Programming Interface(API) level.
5. To provide user clocks that enable the implementation of high level
application timing probes, and buckets to accumulate the individual
durations. By inserting the calls to this function around the code to be
measured, the impact of calls to CICS or non-CICS for OS/2 resources to be
understood.
6. To allow other remote CICS systems to interrogate the transaction
statistics and user clock data held on a CICS for OS/2 Server.
For a wider system view, the reader is encouraged to purchase the Systems
Performance Monitor/2 (SPM/2) product which provides more complete system wide
information on storage usage, paging, swap file size etc. For an introduction
to its function in a CICS for OS/2 environment, see CICS OS/2 V2.0 Sizing and
Performance IBM Corp. GG24-4190-00.
ΓòÉΓòÉΓòÉ 4.2. Pre-requisites ΓòÉΓòÉΓòÉ
CICS OS/2 Performance Analyser requires Service Level 04, or later, of CICS
OS/2 Version 2.0.1 (Single or Multi-user).
To check the level of your system, look at the first message provided by CICS
for OS/2 while it is coming up. For Service Level 04 it should say:
For the Multi-user version
FAA0000I CICS OS/2 Version 2.0.1
FAA0000I Service Level 00 UN00000 .Released 27-Jan-95
FAA0003I Multi-user system initialization starting
For the Single-user version will be similar, except it will refer to the
Single-user system instead.
If CICS for OS/2 is not running you can look at old start-ups recorded in
CICSMSG.LOG which normally resides in the CICS200\BIN directory or enter
SYSLEVEL on the command line and look for the CICS for OS/2 entry. (In this
case, be careful not to be misled by a possible CICSOS2.$BK entry which will be
displayed as well if you have a back-up of an old CICS OS/2 level).
ΓòÉΓòÉΓòÉ 4.3. How this Document is Organised ΓòÉΓòÉΓòÉ
The document is organised as follows:
Performance monitoring
Provides a background to the various factors which can
effect the performance of CICS in any transaction system.
CICS for OS/2 Version 2 and OS/2
Describes the various factors which can effect the
performance of CICS for OS/2 (both at the OS/2 and CICS for
OS/2 level)
Performance Analyser Installation
Provides the instructions on how to install Performance
Analyser
How to use Performance Analyser
Describes how to use Performance Analyser
Getting CICS for OS/2 statistics from another CICS system
Describes how Performance Analyser can be used in a local
and/or distributed CICSplex to request statistics and
monitoring data from a central or distributed location
using Distributed Program Link.
Transaction Level Trace
Describes the transaction level trace function provided
with Performance Analyser.
Application Level Trace
Describes the application level trace function provided
with Performance Analyser.
User Clocks
Describes how to use the User Clock function provided with
Performance Analyser to measure execution times of
application code.
Using the supplied sample program (PA2BR14)
Describes how to use the the supplied sample echo program
(PA2BR14) to return data dependent on its invocation. This
can be used in a number of different ways to exercise a
CICS for OS/2 system.
Trap information
Describes how to use the information passed in PA2STAS.DAT
after a trap
Performance Analyser statistics file
Describes the format and content of the Performance
Analyser statistics file
Usage Examples
Examples of the usage of Performance Analyser with sample
output
If you are familiar with OS/2 and CICS for OS/2 performance parameters and just
wish to get Performance Analyser installed and into productive use, you can
skip over the first two chapters and go straight to the installation
instructions. Otherwise it is suggested you read them in order to gain an
appreciation of the parameters you can use to tune a CICS for OS/2 system
before attempting to use Performance Analyser.
ΓòÉΓòÉΓòÉ 5. Bibliography ΓòÉΓòÉΓòÉ
o OS/2 2.11 Unleashed! D.Moskowitz and D.Kerr, et al. SAMS Publishing ISBN
0-672-30445-7
o The Design of OS/2 H.M.Deitel,M.S.Kogan Addison Wesley ISBN 0-201-54889-5
o OS/2 Features, Functions and Applications J.I.Krantz, A.M.Mizell,
R.L.Williams Wiley ISBN 0-471-60709-6
o BTRIEVE Programmer's Manual BTRIEVE Technologies Part No 100-003056-001
o BTRIEVE for OS/2 Installation and Operation BTRIEVE Technolologies Part No
100-003055-001
o CICS OS/2 V2.0 Sizing and Performance IBM Corp. GG24-4190-00
o CICS OS/2 V2.0 Performance Report IBM Corp. Available from MKTOOLS
o CICS for OS/2 Version 2.0.1 Installation IBM Corp. SC33-0879
o CICS for OS/2 Version 2.0.1 Intercommunication IBM Corp. SC33-0826
o CICS for OS/2 Version 2.0.1 Customization IBM Corp. SC33-0880
o CICS for OS/2 Version 2.0.1 Operation IBM Corp. SC33-0881
o CICS for OS/2 Version 2.0.1 Problem Determination IBM Corp. SC33-1005
o CICS for OS/2 Version 2.0.1 Application Programming IBM Corp. SC33-0883
o CICS for OS/2 Version 2.0.1 Intercommunication IBM Corp. SC33-0826
o CICS Family: Interproduct Communication IBM Corp. SC33-0824
o CICS Family: Client\Server Programming IBM Corp. SC33-1435
o CICS Clients Version 1 Administration IBM Corp. SC33-1436
ΓòÉΓòÉΓòÉ 6. Performance monitoring ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 6.1. Performance Overview ΓòÉΓòÉΓòÉ
The basic constraints on a CICS for OS/2 system are the same as any other
system; available memory, engine(processor) speed, disk access time, network
speed and capacity, and, in a distributed system, the response time of the
partner system. Other items can impact performance, the primary one being bad
application design (for example, holding database locks across user "think"
time).
If you over stress any resource, the result is a performance problem! OS/2 is a
paging operating system which means that if memory is over-committed, a page
will be written to the swap file before a requested page can be loaded.
Normally, while paging is in progress, not much else other than device
interrupts, is doing useful work in the system. This leads to the first
performance rule: "There is no substitute for memory."
The resource that normally does not run out is engine power. For some reason,
people who purchase machines will always try and buy the fastest engine
available and minimise the cost by cutting down on memory! Unfortunately, this
leads to a clash with the second law of performance: "All machines wait at the
same speed."
The first law can be generalised to: "There is no substitute for resources"
This, however, flies in the face of providing an economic solution to whatever
business problem has to be solved and maximising performance therefore comes
down to balancing the relative availability of resources (for example, the
priority of a transaction). The salient point to remember, however, is that in
any constrained situation, what is given to one request is removed from some
other request.
The OS/2 operating system does its part in trying to allocate resources to
maximise the usefulness of the machine. It has various parameters, explained
later, that allow the designer of a CICS for OS/2 transaction system to
influence the allocation of the engine to the various concurrent pieces of work
running in the system.
CICS for OS/2 itself has set of resource related parameters which govern the
throughput of the transaction system (task classes, maximum active tasks,
priorities, and program residency options). Each of these allow the giving or
throttling of resources to a specific action within the system.
System File Manager, the keyed file access system, used by CICS for OS/2, also
has the same sort of parameters, the most important of these being the size of
the System File Manager cache. This major parameter allows you to trade disk
access time for memory. This then relates directly to end user response time,
because if a record is in memory the access time is almost instantaneous,
compared with having to access the index and the related data pages on a disk.
ΓòÉΓòÉΓòÉ 7. CICS for OS/2 Version 2 and OS/2 ΓòÉΓòÉΓòÉ
CICS for OS/2 Version 2 has been designed and built to exploit the features of
both OS/2 Version 2 operating system and the underlying INTEL 386/486 hardware
architectures. This has allowed the designers the ability to create a system
which can run multiple CICS transactions concurrently whilst also having
hardware storage protection between them.
ΓòÉΓòÉΓòÉ 7.1. OS/2 Version 2 architecture ΓòÉΓòÉΓòÉ
OS/2's model for its multi-tasking architecture is made up of a hierarchy of
objects called sessions, processes and threads. Sessions are the highest and
threads the lowest. The session is the unit of user I/O device sharing.
Processes run programs and are the unit of sharing of memory, files, threads
and so on. Threads are the basic unit of execution and a single process can
have multiple threads that execute concurrently within it.
Each session contains a logical mouse, keyboard and video buffer and may have
one or more processes attached to the session. CICS for OS/2 uses sessions to
implement Full Screen terminals, for the attachment of ASCII devices, for
example, a 3151 through COM1,2,..9. Each CICS for OS/2 transaction runs on a
separate OS/2 process using the hardware/software protection level provided by
the INTEL architecture. Beneath the processes are the threads, the number
varying by what function the process is performing. A table showing how many
threads belong to which processes can be found in CICS for OS/2 thread
requirements.
ΓòÉΓòÉΓòÉ 7.2. OS/2 Priorities ΓòÉΓòÉΓòÉ
OS/2 is built with four performance classes of execution for a thread or
process. They are (in ascending order of priority):
o Idle-time (lowest)
o Regular
o Foreground Server
o Time-critical (highest)
The mapping of these performance classes into numeric values is a little odd.
In ascending order of execution, they are 1, 2, 4 and 3 respectively. Within
each of these classes, there are 31 levels, ascending from 1 to 31. You will
find when you look at the process data provided by Performance Analyser values
such as 3.1. The first number (3) is the OS/2 performance class and the second
(1) is the level. Thus, 3.1 means Time-critical, level 1. Foreground Server
has also been known as Server Level and Fixed High; it was conceived for the
purpose of running server work at a higher priority than local work.
ΓòÉΓòÉΓòÉ 7.3. CICS and Priority ΓòÉΓòÉΓòÉ
CICS, no matter which software and hardware platform, has always had a built-in
priority scheme. Each transaction is run with a CICS priority in the range 0
through 255, 0 for the lowest through 255 for the highest. Various resources
may be defined with a priority, also ranging between 0 and 255, for example:
o An end-user terminal
o A network system entry
o A transaction
and (in some implementations)
o An end user
The transaction priority is the sum of the relevant priorities from the list
above (if the total is greater than 255, 255 is used).
ΓòÉΓòÉΓòÉ 7.4. Major CICS for OS/2 Version 2 Parameters ΓòÉΓòÉΓòÉ
CICS for OS/2 can be started either by a CICSRUN command or by invoking the
start up executable, FAAOMPSI.EXE, with the various start up options.
FAAOMPSI.EXE checks the start up options and transfers control to the CICS for
OS/2 main line program FAAOMPML. FAAOMPML is known as the Global Process
because it is involved with the serialisation of resources across the whole of
CICS for OS/2. FAAOMPSI then exits from its invoking window.
FAAOMPML starts the number of processes, FAAOTPTK.EXE, that you requested in
the CICS for OS/2 System Initialisation Table (SIT). The two relevant
parameters are:
1. Maximum number of tasks
2. Minimum free tasks
Maximum number of tasks is exactly what it says; it is the maximum number of
processes that MAY be started in this CICS for OS/2 invocation. (Each CICS task
needs a process to run on).
To explain the other parameter, consider the following example.
Assume a CICS for OS/2 system is setup with the defaults as distributed from
Manufacturing, Maximum number of tasks of six, Minimum free tasks of two and
that the two video terminals (namely V123 and V124) have Autoconnect=Y and
Autoconnect=N, respectively.
When CICS for OS/2 starts up, the messages shown in CICS for OS/2 Start Up will
appear on the console window.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé FAA1670I Non-Facility task, task ID = @02@ Γöé
Γöé FAA1670I Non-Facility task, task ID = @03@ Γöé
Γöé FAA1670I Terminal task, task ID = V123 Γöé
Γöé . . . . . . . . . . . . . . Γöé
Γöé FAA5661I Process 74 initialisation complete Γöé
Γöé FAA5661I Process 75 initialisation complete Γöé
Γöé FAA5661I Process 73 initialisation complete Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
CICS for OS/2 Start Up
This says that CICS has brought up three processes which OS/2 has numbered
internally as 73, 74 and 75. Process 73 is dedicated to the video terminal
V123, and processes 74 and 75 are available as non-facility processes to run
transactions that are not specifically tied to a named video terminal, for
example, a transaction invoked by the External Call Interface (ECI) or one
which is invoked via an inbound APPC request.
Note that there are two non-facility tasks, named @02@ and @03@. This is the
value you specified in Minimum Number of Free Tasks. This means that if more
requests for transaction initiations enter the system than can be handled by
@02@ and @03@, CICS for OS/2 will start up to three more processes giving a
maximum of six (that is, the value specified for Maximum Number of Tasks).
Currently, the stimuli which will activate this are:-
o the connection of a new terminal via the Program Network Architecture (PNA)
interface
o the invocation of the External Transaction Interface (ETI).
o the acquiring of a terminal which is defined and is in a non-acquired state.
This mapping between the names and the process numbers can be more easily seen
by changing to the Time Stamp View on CICSMSG.LOG which is shown in CICS for
OS/2 Start Up (Time Stamp View).
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé 8-04-94 4:06:38p @02@ @02@ FAA1670I Non-Facility task, task ID = @02@ Γöé
Γöé 8-04-94 4:06:38p @03@ @03@ FAA1670I Non-Facility task, task ID = @03@ Γöé
Γöé 8-04-94 4:06:38p @01@ V123 FAA1670I Terminal task, task ID = V123 Γöé
Γöé . . . . . . . . . . . . . . . Γöé
Γöé 8-04-94 4:06:49p @02@ @02@ FAA5661I Process 74 initialization complete Γöé
Γöé 8-04-94 4:06:49p @03@ @03@ FAA5661I Process 75 initialization complete Γöé
Γöé 8-04-94 4:06:49p @01@ V123 FAA5661I Process 73 initialization complete Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
CICS for OS/2 Start Up (Time Stamp View)
Another background process is the Trace process (FAAOMPTR) which is always
present though it will not be doing anything unless trace is activated by the
/t start up option or by invoking the CETR transaction. Details of these three
processes (FAAOMPSI, FAAOMPML and FAAOMPTR) can be seen by running the OS/2
utility, PSTAT, from an OS/2 command prompt. (See OS/2 tools for more
information).
ΓòÉΓòÉΓòÉ 7.5. CICS for OS/2 and Priority ΓòÉΓòÉΓòÉ
The global process (FAAOMPML) controls the total CICS for OS/2 system. It runs
in the Time Critical class with a priority of 3.1. You are unable to change
this value.
CICS for OS/2 allows you to specify a CICS priority (0 through 255) on the
following resources:
o A transaction entry in the Program Control Table (PCT)
o An end user terminal entry in Terminal Control Table (Terminal Entry) (TCT)
o A connection entry in the Terminal Control Table (System Entry) (TCS).
o A non-facility process by way of the Default Process priority entry in the
Systems Initialisation Table (SIT),
o The CICS System priority entry in the SIT.
The calculation to work out the task priority begins with the addition of the
priority of the transaction to be run and the facility that is used to initiate
the transaction: break.
A task running on a terminal or an inbound EPI Transaction priority + terminal
priority
A task serving an inbound communications request: Transaction priority +
connection priority
A task serving an inbound ECI or ETI request (with no terminal specified)
Transaction priority + default process priority
This is subject to a maximum priority of 255. Thus
Actual task priority = minimum(Task priority,255)
Finally the task priority is scaled against the CICS System priority entry in
the SIT. This allows the base priority at which all transactions run in CICS
for OS/2 to be varied so giving some control over balancing CICS for OS/2
against other sub-systems in the machine.
The complete algorithm is thus:
Task priority = CICS System priority + Actual task priority
- (CICS System priority * Actual task priority / 255)
This last step makes sure that there is scaling between the CICS System
priority and 255.
The final result is then mapped onto the OS/2 performance classes as shown in
Performance classes.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Task Priority Γöé Performance Class Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 0 through 85 Γöé Idle-time Γöé
Γöé 86 through 170 Γöé Regular Γöé
Γöé 171 through 255 Γöé Fixed-high Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Performance classes
Note. The Idle-time class should be avoided except for real background
transactions which only need to run when spare cycles are available. CICS for
OS/2 resource definition defaults terminal and connection priorities to 86 so
that even if a transaction has priority 0 (the default) it will run in OS/2's
Regular class.
ΓòÉΓòÉΓòÉ 7.6. CICS for OS/2 and Task Classes ΓòÉΓòÉΓòÉ
CICS for OS/2 gives the systems programmer the ability to throttle certain
transactions by assigning them to one of eleven Task Classes. The number of
concurrent transactions that will be allowed to run in a Task Class is defined
in the Systems Initialisation Table (SIT). Therefore, if the system has a
transaction that uses a large amount of resources, it could be placed in a
Transaction Class that has an upper limit of 1, so only one of these
transactions would be allowed to run at once. The task class for the
transaction is defined on the Program Control Table (PCT) entry with a value of
1 to 10. The eleventh is the default which is no Task class.
ΓòÉΓòÉΓòÉ 7.7. System File Manager and priority ΓòÉΓòÉΓòÉ
System File Manager currently runs at an OS/2 priority class of 4 and level 0;
that is at the bottom of Foreground server. This, using the table in the
previous section, translates into a CICS priority of 171. Experience with
mainframe CICS systems has almost always shown that the priority of a data
owning entity should be run at a higher priority than the application. This
means that until System File Manager allows you to alter its priority,
applications should be run at a CICS priority between 86 and 170.
ΓòÉΓòÉΓòÉ 7.8. Threads ΓòÉΓòÉΓòÉ
CICS for OS/2 uses more than one thread for each of the processes defined
earlier. CICS for OS/2 thread requirements provides a guide of how many
additional threads will be required to run a CICS for OS/2 system.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé Γöé Γöé
Γöé Process Γöé Function Γöé Number of threads required Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé Γöé Γöé
Γöé FAAOMPML Γöé Mainline Γöé 2 Standard Γöé
Γöé Γöé Γöé 1 Message log Γöé
Γöé Γöé Γöé 1 External Call Interface(ECI) Γöé
Γöé Γöé Γöé 1 ICE manager Γöé
Γöé Γöé Γöé 1 Scheduler Γöé
Γöé Γöé Γöé 3 PNA (if enabled) Γöé
Γöé Γöé Γöé 1+2*NetBios adapters (if enabled) Γöé
Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé FAAOMPTR Γöé Trace Γöé 2 Standard Γöé
Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé FAAOTPTK Γöé Application Γöé 3 for each (if Terminal Facility) Γöé
Γöé Γöé Γöé Γöé
Γöé Γöé Γöé 2 for each (if Non-Facility) Γöé
Γöé Γöé Γöé +1 if ever used as a PNA Terminal Γöé
Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé BTRIEVE/ Γöé Keyed file Γöé 3 Standard Γöé
Γöé System Γöé engine Γöé n Worker (as specified) Γöé
Γöé File Γöé Γöé m I/O (as specified) Γöé
Γöé Manager Γöé Γöé 1 Archive and/or Durability(if enabled) Γöé
Γöé Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
CICS for OS/2 thread requirements
OS/2 Version 2 has a default CONFIG.SYS entry for THREADS which is equal to
256. After looking at your system, using PSTAT or SPM/2, you may wish to
increase this default value to a higher value using the information detailed
above.
ΓòÉΓòÉΓòÉ 7.9. OS/2 parameters ΓòÉΓòÉΓòÉ
MAXWAIT CONFIG.SYS value which sets the amount of time, in
seconds, a process waits before the system assigns it a
higher priority. When a regular class thread is denied
the processor for this number of seconds, it receives a
temporary increase in priority for a minimum time slice.
(Default is 3 seconds)
MinSlice This is the first parameter of the TIMESLICE CONFIG.SYS
value and is the minimum amount of time in milliseconds a
thread can process before yielding the processor to
another thread of the same priority level. (Default is 32
milliseconds)
MaxSlice This is the second parameter of the TIMESLICE CONFIG.SYS
value and is the maximum amount of time in milliseconds a
thread can process before yielding the processor to
another thread of the same priority level. (Default is 32
milliseconds)
PRIORITY_DISK_IO When PRIORITY_DISK_IO=YES is specified in CONFIG.SYS, an
application running with the focus will receive disk I/O
priority over applications running in the background.
This means foreground applications should have a better
response time than those running in the background. For
a CICS for OS/2 Application server, it is recommended
this parameter should be set to NO, and set to YES for a
developer's machine. (Default is YES)
SWAPPATH SWAPPATH has three parameters, the first is the location
of the swap file. The normal recommendation is to place
it in the root directory of the most frequently partition
on least frequently used drive. If you only have one
drive, the same advice holds true, place it in the root
directory of the most frequently used partition. The
second parameter sets a warning threshold level in
kilobytes. This value should be at least 5120. The
third value is little known, because it is not set in the
default CONFIG.SYS, and specifies the initial size (in
kilobytes) of the swap file at boot time. If you are
using FAT on the volume where your swap file is,
fragmentation caused by the growth and reduction of the
swap file can cause between 10 and 15 percent
degradation.
THREADS The THREADS parameter gives the maximum number of threads
that can concurrently run on the system. If you do not
have enough, the system will normally hang! This number
will have to service the total of OS/2, Communications
Manager/2, NetBIOS, TCP/IP, BTRIEVE, DB2/2. The maximum
is 4096 with a default entry at OS/2 installation of 256.
If there is no entry in CONFIG.SYS, then the number of
threads defaults to 64.
RESTARTOBJECTS When CICS for OS/2 is running as a server, it is probably
unattended, so when you restart you will not want objects
to be restarted, so specify SET
RESTARTOBJECTS=STARTUPFOLDERSONLY.
ΓòÉΓòÉΓòÉ 7.10. OS/2 tools ΓòÉΓòÉΓòÉ
OS/2 Version 2 comes with some tools to help you view what is happening on your
system. The simplest of these is Pulse which you will find in the Productivity
folder in the OS/2 System folder on your desktop. It gives a small graphical
display of how busy the engine is in your machine. The second has been
mentioned already, PSTAT. An extract from the help information is reproduced
here but the full write up should be viewed on your machine by entering
help pstat
on a command line.
PSTAT displays information about:
o Current processes and threads
o System semaphores
o Shared memory for each process
o Dynamic-link libraries
PSTAT helps you find out which threads are running in the system, along with
their current status and current priorities. With it you can find out the
process ID that has been assigned to each process. This can be used as input
to the OS/2 TRACE utility program if you need to dive more deeply into the
system. The binary trace output is then formatted using the OS/2 TRACEFMT
command.
There are also quite a few Bulletin Board utilities for swap file activity,
NetBIOS usage etc. One starting point for finding these bulletin boards is a
list at the back of "OS/2 2.11 Unleashed" by David Moskowitz and David Kerr, et
al.
Every location should have at least one copy of the IBM System Performance
Monitor/2.
ΓòÉΓòÉΓòÉ 8. Performance Analyser Installation ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 8.1. Installation of the code ΓòÉΓòÉΓòÉ
The following procedure assumes you have CICS for OS/2 Version 2 installed in
the default CICS200 directory on drive cicsdrv, and the PATH and LIBPATH
statements in CONFIG.SYS were automatically updated by the CICS for OS/2
Version 2 installation. If you install Performance Analyser elsewhere you will
have to point CICSWRK or LIBPATH to the directory where you put the DLLs, and
PATH to where you put the EXEs.
1. Check your CICS for OS/2 Version 2 is at the right level.
2. Create a temporary directory on the target machine; this is referred to
later as tmpdrv:\tmpdir.
3. Copy the file CICSPA2.ZIP to this directory.
4. At a command prompt in this directory, unzip CICSPA2.ZIP.
5. The following files will be created.
FAAPLTPI.DLL Performs an EXEC CICS START to the Performance
Analyser initialisation transaction PA21.
FAAPLTPI.CCS Sample source to illustrate the EXEC CICS START
command needed to invoke the internal
initialisation transactionPA21.
PA2PLTPI.DLL Performance Analyser program that does an
asynchronous search of CICS for OS/2 resources
invoked from transaction PA21.
FAAPLTSD.DLL Executes an EXEC CICS LINK to program PA2PLTSD, the
Performance Analyser monitoring and statistics
output program PA2PLTSD.DLL.
FAAPLTSD.CCS Sample source to illustrate the above.
PA2PLTSD.DLL Performance Analyser program which creates the
monitoring and statistics output file PA2STATS.DAT.
FAAEXP17.DLL CICS for OS/2 exit to capture ABEND information and
statistics. If you are already using this exit, do
NOT copy the one supplied with this package into
your system
FAADKSIN.DLL CICS for OS/2 exit to capture application level
trace, timings and statistics. This is supplied
only as a DLL. The optional binary trace file
created is named PA2STATS.TRC, and may be formatted
whilst CICS for OS/2 is running by invoking
PA2DKSIN.EXE.
PA2BTRST.EXE Used to obtain information and statistics on keyed
files held in the System File Manager at start up.
PA2BTREN.EXE Used to obtain information and statistics on keyed
files held in the System File Manager using
transaction PA2B and at shutdown time when PA2PLTSD
is run.
FAAAEFIE.BTR CICS for OS/2 import file containing the
Performance Analyser run-time BMS maps and
transaction definitions in group PA2GROUP.
Installation Verification Program (IVP) definitions
are in group PA2EXMPL
PA2CLOCK.DLL Updates user clock data
PA2CLOCK.H C header file for use with user clocks
PA2CLOCK.LIB Library file for use with user clocks
PA2ABEND.DLL Installation Verification program
PA2ABEND.CCS Source for the above
PA2BR14.DLL Echo test program that provides a CICS superset of
the mainframe IEFBR14 program. It is simple echo
program that can be invoked in various ways (PA22)
PA2BR14.CCS Source for the above
PA2KCBIN.DLL A program that enables a remote CICS system to
request statistics from a CICS for OS/2 system
using Distributed Program Link. See Getting CICS
for OS/2 statistics from another CICS system.
PA2XXBIN.H C language header file showing the record layout of
the COMMAREA passed to and returned from
PA2KCBIN.DLL.
PA2ALLEN.H C language header file containing the #defines for
the above.
5764-091.INF VIEWable on-line documentation.
In addition, the following 3270 BMS transaction
programs are supplied. They are the Performance
Analyser applications that can be used to display
the various statistics captured by the exits. The
transaction IDs for each program is shown in
parenthesis.
PA2MMDSP.DLL Performance Analyser main menu (PA2)
PA2BTDSP.DLL Btrieve statistics (PA2B)
PA2BUDSP.DLL Bucket statistics (PA2E)
PA2FCDSP.DLL File Control statistics(PA2F)
PA2GCDSP.DLL File Control statistics (cont'd) (PA2G)
PA2ICDSP.DLL Interval Control statistics (PA2I)
PA2KCDSP.DLL Task Control statistics (PA2K)
PA2LGDSP.DLL CICS for OS/2 log display (PA2L)
PA2PCDSP.DLL Program Control statistics (PA2P)
PA2RCDSP.DLL Transaction rate display (PA2R)
PA2TDDSP.DLL Transient Data statistics (PA2D)
PA2TSDSP.DLL Temporary Storage statistics (PA2Q)
PA2XCDSP.DLL OS/2 Process Control statistics (PA2X)
The following are also 3270 BMS transaction
programs providing Performance Analyser Trace and
Statistics control functions.
PA2OCDSP.DLL Application level trace control (PA2O)
PA2OTDSP.DLL Transaction level trace control (PA2Y)
PA2MCDSP.DLL Drives output of PA2PLTSD.DLL to create
PA2STATS.DAT (PA2M)
The choice of 3270 BMS transactions is deliberate.
It allows the interrogation of a CICS for OS/2
server from any CICS system that supports
transaction routing.
A separate capability to the the online monitoring
and statistics function are the stand alone
Application and Transaction level trace formatters
with timings.
PA2DKSIN.EXE Input file is PA2STATS.TRC, and the readable output
file is named PA2STATS.RPT. If the output file
already exists, then new output is appended at the
end of it.
PA2TRSIN.EXE Input file is PA2STATS.TRN, and the readable output
file is also PA2STATS.RPT. If the output file
already exists, then new output is appended at the
end of it.
6. CICSPA2.ZIP may now be deleted.
7. If you do NOT have programs which do real PLTPI and/or PLTSD processing,
then go to step 6 Otherwise, you must add the following EXEC CICS
statements into your source and recompile.
a. An EXEC CICS START to transaction PA21 in FAAPLTPI
b. An EXEC CICS LINK for program PA2PLTSD in program FAAPLTSD. See the two
sample .CCS source modules (FAAPLTPI.CCS and FAAPLTSD.CCS) for examples of
these additions.
Go to step 7.
8. Rename the files FAAPLTPI.DLL and FAAPLTSD.DLL in the cicsdrv:\CICS200\BIN
subdirectory. For example,
ren FAAPLT*.DLL *.BAK
Copy the Performance Analyser versions of these 2 files to
cicsdrv:\CICS200\BIN subdirectory.
9. Rename the file FAADKSIN.DLL (if present) in the cicsdrv:\CICS200\BIN
subdirectory. For example,
ren FAADKSIN.DLL *.BAK
Copy the Performance Analyser versions of this file to cicsdrv:\CICS200\BIN
subdirectory.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé WARNING!!!! Γöé
Γöé Γöé
Γöé When installing a CSD on a CICS for OS/2 system which has Performance Γöé
Γöé Analyser installed the following modules may be overwritten by the CSD Γöé
Γöé installation: Γöé
Γöé Γöé
Γöé FAADKSIN.DLL Γöé
Γöé FAAPLTPI.DLL Γöé
Γöé FAAPLTSD.DLL Γöé
Γöé Γöé
Γöé MAKE SURE YOU TAKE BACKUP COPIES OF THESE FILES BEFORE INSTALLING A CSD Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
10. Copy the PA2*.EXE and PA2*.DLL files into the cicsdrv:\CICS200\BIN
subdirectory.
11. Copy FAAEXP17.DLL into the cicsdrv:\CICS200\BIN subdirectory, if you do NOT
have one already specified in your system.
12. If you are going to use buckets, copy PA2CLOCK.H to
cicsdrv:\CICS200\INCLUDE and PA2CLOCK.LIB to cicsdrv:\CICS200\LIB.
13. Copy 5764-091.INF to an appropriate directory and, optionally, set up a
desktop object using VIEW.EXE as the file name and path\5764-091.INF as the
optional parameter (where path points to the directory where you placed the
INF file.
You must now add the appropriate BMS maps and PCT entries for Performance
Analyser. You have two options; use the supplied CICS for OS/2 import file
(in which case go to step 12) or create them yourself (in which case go to
step 19).
14. Back-up your current import file (FAAAEFIE.BTR) in the
cicsdrv:\CICS200\BIN\DATA directory, if necessary, by renaming it or by
using the Backup Existing Data option on the Application Import Screen of
the import transaction CAIM.
15. Copy the supplied import file (FAAAEFIE.BTR) to cicsdrv:\CICS200\BIN\DATA
16. Bring up CICS for OS/2.
17. If you have a pre-release version of Performance Analyser (that is, prior
to V1.0) you should delete all Performance Analyser PCT/PPT references
using CEDA. Also, delete all Performance Analyser map items from the
map-file using CSCA.
18. Enter the CAIM transaction and fill in:
o PA2GROUP as the GROUP NAME
o N for Include conversion templates
o N for Include SNT
o Y for Data files
o N for Input from Backup
o Y or N for Backup existing data, depending what you want on the
Application Import Screen.
This will import the necessary screen maps and PCT entries for Performance
Analyser
19. If you wish to import the supplied samples, enter the CAIM transaction
again and fill in PA2EXMPL as the GROUP NAME on the screen with the same
parameters as described in the previous step.
20. Go to step 23.
21. Perform any customisation on the supplied BMS mapset and then translate by
entering the following command from an OS/2 command line:
cicsmap tmpdrv:\tmpdir\PA2KC
(where tmpdrv:\tmpdir is the path to the temporary directory created in
step 2).
22. Bring up CICS for OS/2.
23. Create a PPT entry for the map (PA2KC).
24. Create PCT entries for each of the PA2x transactions (ie PA2, PA2B, PA2F
etc).
It is recommended you use a GROUPNAME of PA2GROUP for future compatibility.
25. Shutdown CICS.
26. If you are using CICSRGRP environment variable, which is normally set in
CICSENV.CMD, to control the loading of specific groups then add PA2GROUP
and PA2EXMPL to your current list.
27. This completes the installation of Performance Analyser.
The next section provides details on how to verify that it is functioning
correctly.
ΓòÉΓòÉΓòÉ 8.2. Installation Verification Procedure ΓòÉΓòÉΓòÉ
1. Bring up CICS for OS/2.
2. Check CICSMSG.LOG or the CICS for OS/2 Version 2.0 window that message
FAA5706I was output during start-up.
FAA5706I Internal trace function enabled
If it was not, you have not placed FAADKSIN.DLL in a directory which is on
the CICSWRK path or on LIBPATH.
3. Check CICSMSG.LOG or the CICS for OS/2 Version 2.0 window that message
FAA5627I was output during start-up.
FAA5627I User exit 17(transaction abend/system error) loaded
If it was not, you have not placed FAAEXP17.DLL in a directory which is on
the CICSWRK path or on LIBPATH.
4. Check CICSMSG.LOG or the CICS for OS/2 Version 2.0 window that a FAAuser
message was output during start-up saying "PLTPI processing complete". If
it was not, you have not placed FAAPLTPI.DLL in a directory which is on the
CICSWRK path or on LIBPATH, or your version has removed this EXEC CICS
WRITE OPERATOR command.
5. Check CICSMSG.LOG or the CICS for OS/2 Version 2.0 window that a FAAuser
message was output during start-up saying "Performance Analyser/2 started".
If it was not, you have not placed PA2PLTPI.DLL in a directory which is on
the CICSWRK path or on LIBPATH, or you have no PCT entry for PA21 pointing
at program PA2PLTPI, or you have not inserted the EXEC CICS START
TRANSID("PA21") in your customised FAAPLTPI.
6. Enter transaction code PA2K on the 3270 terminal. You should receive
information similar to that shown in PA2K output example.
PA2K output example
If you do not, and receive message "FAA5405E Transaction identification
PA2K not valid - please resubmit" you have no PCT entry for PA2K. If you
receive message "FAA5407E Program PA2KCDSP is not available, RC = 0034",
you have not placed PA2KCDSP.DLL in a directory which is on the CICSWRK
path or on LIBPATH.
7. Shutdown CICS down using CQIT (NOT CQIT I).
8. Use an editor or file browser to look at statistics in
cicsdrv:\CICS200\BIN\PA2STATS.DAT. If this file does not exist, you have
not updated your FAAPLTSD.DLL with a LINK to program PA2PLTSD or FAAPLTSD
and/or PA2PLTSD are not present in a directory which is on the CICSWRK path
or on LIBPATH, or you did a CQIT I which bypasses CICS Program Load Table
(PLTSD) shutdown processing.
ΓòÉΓòÉΓòÉ 9. How to use Performance Analyser ΓòÉΓòÉΓòÉ
There are seven primary functions that are available with Performance Analyser:
1. Real-time display of CICS for OS/2 server statistics via terminal input
using a subset of the supplied transactions. Real-time statistics display
describes their use.
2. Generation of a formatted statistics file for off-line analysis. Generation
of a formatted statistics file describes the various ways this file can be
created.
3. Provision of statistical data for a particular CICS for OS/2 server to a
another remote CICS system. Getting CICS for OS/2 statistics from another
CICS system explains how this function is achieved using Distributed
Program Link.
4. Tracing the execution of CICS transactions providing both "time-of-day"
stamps and elapsed time measurements for them. Application Level Trace
explains how to control this function.
5. Tracing the execution of a CICS application and to provide both
"time-of-day" stamps and elapsed time measurements for the EXEC CICS calls
and internal CICS for OS/2 functions. Application Level Trace explains how
to control this function.
6. Insertion of "User Clocks" in application programs. This allows for the
measurement of code execution times and counting of the number of times a
particular section of code is run. User Clocks provides details on how to
implement this function.
7. Running of a sample CICS echo program (PA2BR14) to return data independent
of its method of invocation. This can be used in a number of different ways
to exercise a CICS for OS/2 system. Its use is is explained in Using the
supplied sample program (PA2BR14).
Performance Analyser has a set of "built-in" transactions which can be invoked
from any CICS 3270 terminal attached to a CICS OS/2 server with Performance
Analyser enabled. These transactions, which are shown together with their
equivalent program names in Performance Analyser transactions supplied in
PA2GROUP group and Performance Analyser transactions supplied in PA2EXMPL
group, provide access to many of the functions described above.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé Γöé Γöé
Γöé TRANID Γöé Program Name Γöé Function Γöé
Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé PA2 Γöé PA2MMDSP.DLL Γöé Performance Analyser main menu Γöé
Γöé Γöé Γöé Γöé
Γöé PA2B Γöé PA2BTDSP.DLL Γöé Display System File Manager statistics Γöé
Γöé PA2D Γöé PA2TDDSP.DLL Γöé Display Transient Data statistics Γöé
Γöé PA2E Γöé PA2BUDSP.DLL Γöé Display Buckets data Γöé
Γöé PA2F Γöé PA2FCDSP.DLL Γöé Display File Control statistics Γöé
Γöé PA2G Γöé PA2GCDSP.DLL Γöé Display Browse portion of File Control statistics Γöé
Γöé PA2I Γöé PA2ICDSP.DLL Γöé Display Interval Control statistics Γöé
Γöé PA2K Γöé PA2KCDSP.DLL Γöé Display Task Control statistics Γöé
Γöé PA2L Γöé PA2LGDSP.DLL Γöé Display CICS OS/2 Log File Γöé
Γöé PA2P Γöé PA2PCDSP.DLL Γöé Display Program Control statistics Γöé
Γöé PA2Q Γöé PA2TSDSP.DLL Γöé Display Temporary Storage Queues statistics Γöé
Γöé PA2R Γöé PA2RCDSP.DLL Γöé Display Transaction rate over last hour Γöé
Γöé PA2X Γöé PA2XCDSP.DLL Γöé Display OS/2 Process statistics Γöé
Γöé PA2M Γöé PA2MCDSP.DLL Γöé Generate statistics file dynamically Γöé
Γöé PA2O Γöé PA2OCDSP.DLL Γöé Performance Analyser application trace control Γöé
Γöé PA2Y Γöé PA2OTDSP.DLL Γöé Performance Analyser transaction trace control Γöé
Γöé PA21 Γöé PA2PLTPI.DLL Γöé Performance Analyser asynchronous initialisation Γöé
Γöé Γöé Γöé (for internal use by Performance Analyser) Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Performance Analyser transactions supplied in PA2GROUP group
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Γöé Γöé Γöé
Γöé TRANID Γöé Program Name Γöé Function Γöé
Γöé Γöé Γöé Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Γöé Γöé Γöé
Γöé PA22 Γöé PA2BR14.DLL Γöé Invoke Performance Analyser sample echo program Γöé
Γöé Γöé Γöé (Performance Analyser equivalent of IEFBR14) Γöé
Γöé Γöé Γöé Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Performance Analyser transactions supplied in PA2EXMPL group
Transaction PA2 displays the Performance Analyser main menu (see Performance
Analyser main menu). This can be used to invoke the majority of the other
transactions or, alternatively, all transactions can be run directly.
Performance Analyser main menu
ΓòÉΓòÉΓòÉ 9.1. Real-time statistics display ΓòÉΓòÉΓòÉ
Real-time display of CICS for OS/2 server statistics is achieved by issuing any
of the "DISPLAY" transactions listed in Performance Analyser transactions
supplied in PA2GROUP group (either directly or via the main menu as shown in
Performance Analyser main menu ) from an active terminal.
This will result in a pre-formatted screen being displayed containing
statistical data relating to a particular functional area of the CICS for OS/2
server. Explanation of PA2STATS.DAT file entries in Performance Analyser
statistics file provides an explanation of the data displayed.
PA2R output example is an example of PA2R issued on a local terminal. It shows
the transaction activity on the Server over the last hour.
This figure also shows the "boiler-plate" items of the Performance Analyser
display, namely:-
o In the top left-hand corner, the time of day.
o In the top right-hand corner, the elapsed time since CICS for OS/2 was
started.
o In the top centre, the title and subject of the output
o In the bottom right, there are two fields; the first marked MCT which is the
value of the Maximum Con-current Tasks that have executed on the system since
this run started and ServerId is the APPLID by which the system is known.
(ie as defined in the Systems Initialisation Table(SIT)).
PA2Routputexample
PA2P output example is an example of PA2P. It provides statistics on invoked
programs.
PA2P output example
PA2B output example is an example of PA2B. It provides statistics on System
File Manager usage.
PA2B output example
PA2R output example is another example of PA2K. This time the transaction was
issued on a remote terminal. Notice the different characters used to indicate
the transaction activity on the Server. The reason for the difference between
the two is that transaction routing flows all data in EBCDIC and there is no
equivalent character in EBCDIC to the ASCII full-box and half-box so these have
been replace by ":" and "." respectively.
PA2R output example
ΓòÉΓòÉΓòÉ 9.2. Generation of a formatted statistics file ΓòÉΓòÉΓòÉ
The same statistics data that is displayed in real-time with the supplied
transactions, can also be saved in a file for later, off-line analysis. The
file is called PA2STATS.DAT. It is an ASCII file that can be viewed with a
standard PC editor/browser or printed on a line printer. It is used as an
"append" file (that is, each time new data is collected it is added to the end
of the file). The file will thus continue to grow until specific action is
taken to delete it. The file is closed after use so that it may be accessed by
other processes in the system.
The file itself can be added to in one of three ways:
1. By selecting PA/2 Statistics Report from the Performance Analyser main
menu. An optional reason string can be passed in the field supplied.
2. By executing the supplied 3270 transaction PA2M. An optional reason string
can concatenated after the transaction code.
3. By LINKing to the program PA2PLTSD. An optional reason string can be passed
in the COMMAREA.
An example of a PA2STATS.DAT file generated by Performance Analyser is shown in
An example of a PA2STATS.DAT file in Performance Analyser statistics file
whilst Explanation of PA2STATS.DAT file entries also in Performance Analyser
statistics file provides an explanation of the various entries within the file.
ΓòÉΓòÉΓòÉ 10. Getting CICS for OS/2 statistics from another CICS system ΓòÉΓòÉΓòÉ
A requirement that is often needed in a distributed CICSplex is the ability to
request statistical data from a central or distributed location. Performance
Analyser provides this function with a DLL (PA2KCBIN) that can be linked to
using a CICS Distributed Program Link (DPL) from a remote CICS system and which
will then return the requested Performance Analyser statistics to the calling
system. This data is currently limited to statistics on tasks, processes and
bucket data.
ΓòÉΓòÉΓòÉ 10.1. PA2KCBIN ΓòÉΓòÉΓòÉ
This DLL can be linked from any CICS system using
EXEC CICS LINK
PROGRAM('PA2KCBIN')
COMMAREA(Commarea)
LENGTH(CommareaLen)
SYSID(Remotesysid)
SYNCONRETURN (See Note)
Note: SYNCONRETURN can be optionally used on those systems that can send it.
Its use will halve the network flows thus considerably improving the
performance of the command.
The only input parameter required is the ASCII letter in the field
CommPtr->entry_type. Three #defines are provided in PA2ALLEN.H:
PCT_TYPE_RECORD for task control statistics
PID_TYPE_RECORD for OS/2 process statistics
BUK_TYPE_RECORD for user clock statistics
There is no default and a PA2Q abend will occur if neither of these two are
provided.
The COMMAREA you pass needs to be large enough for all the statistics
available. The field CommPtr->end will contain an N if it is not, otherwise it
will contain a Y.
There are three abend codes associated with PA2KCBIN namely:
PA2L meaning the COMMAREA passed is not long enough even to return
the header
PA2Q meaning the input parameter is not recognised
PA2S meaning addressability to the Performance Analyser control
blocks has been lost.
A C language include file, PA2XXBIN.H, is included in the package and defines
the structure of the returned COMMAREA. Note, if there is no conversion,
integers are in INTEL format, backwards as compared with an IBM mainframe
format. For example, a time of 1.75 seconds (ie 1750 milli-seconds) will be
returned as a four byte entry of D6 06 00 00. This is interpreted as the
hexadecimal number '000006D6' which equates to 1750 decimal.
ΓòÉΓòÉΓòÉ 11. Transaction Level Trace ΓòÉΓòÉΓòÉ
Performance Analyser includes a transaction level trace facility. This enables
the tracing of the execution of a CICS transaction and provides "time-of-day"
stamps and elapsed time measurements for the start and end of all transactions.
The function is controlled using the supplied transaction PA2Y. It can be
entered directly (either on its own or with the parameters ON or OFF) or via
the Performance Analyser main menu in which case an input field is provided to
enter the ON or OFF parameters if required. (See Performance Analyser main
menu).
PA2Y Gives the status of the transaction level trace
PA2Y ON Starts the transaction level trace if it is not already
running
PA2Y OFF Stops the transaction level trace if it is not already
stopped
PA2TRSIN can then be run to format the binary trace file PA2TRSIN.TRC into the
readable form PA2STATS.RPT. PA2TRSIN must be run in the cicsdrv:\CICS200\BIN
sub-directory.
Running the Transaction Level Trace in this fashion provides system
programmers with an insight as to the way the system is behaving, for example
how much multi-tasking is going on.
The fields within the trace are as follows:
Time Time of day printed as Hours:Minutes:Seconds.Hundredths
PID The OS/2 process id. If it is blank, the process id is the
same as the line above
Type Entry or Exit with the transaction name printed further to
the right
Component time Time difference (in seconds and hundredths) between the
Entry and Exit record.
ΓòÉΓòÉΓòÉ 12. Application Level Trace ΓòÉΓòÉΓòÉ
Performance Analyser includes an application level trace facility. This
enables the tracing of the execution of a CICS application and provides both
"time-of-day" stamps and elapsed time measurements for the EXEC CICS calls and
internal CICS for OS/2 functions.
The function is controlled using the supplied transaction PA2O. It can be
entered directly (either on its own or with the parameters ON or OFF) or via
the Performance Analyser main menu in which case an input field is provided to
enter the ON or OFF parameters if required. (See Performance Analyser main
menu).
PA2O Gives the status of the application level trace
PA2O ON Starts the application level trace if it is not already
running
PA2O OFF Stops the application level trace if it is not already
stopped
PA2DKSIN can then be run to format the binary trace file PA2STATS.TRC into the
readable form PA2STATS.RPT. PA2DKSIN must be run in the cicsdrv:\CICS200\BIN
sub-directory.
Running the Application Level Trace in this fashion provides application
programmers with an insight as to the way their code is behaving in the system.
An actual trace output file is shown in An example of a PA2STATS.RPT file.
Comments have been added so that you can understand what information is
available and what can be inferred from the entries.
The fields within the trace are as follows:
Time Time of day printed as Hours:Minutes:Seconds.Hundredths
PID The OS/2 process id. If it is blank, the process id is the
same as the line above
Type Entry or Exit or blank. If it is blank the resource and
transaction name will be printed further to the right
Description Explanation of the atomic unit of the task being performed
Component time Time difference (in seconds.hundredths) between an Entry
and an Exit record for an atomic unit. On a resource line
this field is the resource name
EXEC time Time difference (in seconds.hundredths) between an Entry
and an Exit record for an EXEC CICS call. On a resource
line this field is the transaction name
In order that a systems programmer can see what is happening at initialisation,
trace can be initialised by creating a text file PA2STATS.INI and inserting /tr
in it. This should then be saved in the cicsdrv:\CICS200\BIN sub-directory;
Performance Analyser will read the file and act upon the setting at start-up.
Similarly, inserting /xn will start the transaction level trace.
Other options are for internal debugging purposes. Any data that is seen by
using them is liable to change without warning. They are:
o /du to dump working areas
o /de to list in CICSMSG.LOG, the resources and its corresponding group that
are being installed.
AnexampleofaPA2STATS . RPTfile
Performance Analyser for
CICS for OS/2 Version 2
5764-091
High level timing trace
All elapsed times in millisecs
Time PID Type Description Component EXEC
time time
15:27:10.38 62 Entry GLBL NetBios/PNA request
62 is global process
15:27:12.57 Exit GLBL NetBios/PNA request 2188
Still on the global process since the PID is blank
Entry GLBL NetBios/PNA request
Time is still 15:27:12.57 since the Time field is blank
15:27:12.75 Exit GLBL NetBios/PNA request 187
Component time is 187 milliseconds being the difference of 15:27:12.75 and
15:27:12.57
Entry GLBL NetBios/PNA request
15:27:12.82 Exit GLBL NetBios/PNA request 63
Start up 3 threads for NetBios (See thread information, CICS for OS/2 thread
requirements).
15:27:43.32 Entry GLBL GIVEMAIN request
15:27:43.38 Exit GLBL GIVEMAIN request 62
Entry GLBL GIVEMAIN request
Exit GLBL GIVEMAIN request 0
Entry GLBL GIVEMAIN request
15:27:43.41 Exit GLBL GIVEMAIN request 32
15:27:44.41 Entry GLBL GETMAIN request
Exit GLBL GETMAIN request 0
First process switch from the global process, 62, to an application process, 67
15:27:44.88 67 Entry Initialise
Exit Initialise 0
15:27:44.91 66 Entry Initialise
Switch to application process 66
Exit Initialise 0
15:27:45.41 62 Entry GLBL GETMAIN request
Exit GLBL GETMAIN request 0
Entry GLBL TASK initialisation
Exit GLBL TASK initialisation 0
15:27:45.44 Entry GLBL TASK initialisation
Exit GLBL TASK initialisation 0
15:27:45.63 65 Entry Initialise
Switch to application process 65
Exit Initialise 0
15:27:48.44 62 Entry GLBL TASK initialisation
Exit GLBL TASK initialisation 0
15:27:48.50 65 Entry Load Program
15:27:48.54 66 Entry Load Program
FAAOISII INIT
15:27:48.60 67 Entry Load Program
FAAOISII INIT
65 FAAOISII INIT
15:27:49.29 66 Exit Load Program 94
67 Exit Load Program 32
15:27:49.41 65 Exit Load Program 251
Loading program FAAOISII under internal transaction INIT on all three processes
65, 66, and 67
15:27:49.47 66 Entry Init prog COBOL call
15:27:49.75 67 Entry Init prog COBOL call
15:27:50.19 66 Exit Init COBOL prog call 719
Setting up COBOL environment
Entry EXEC CICS ADDRESS
15:27:50.22 Exit EXEC CICS ADDRESS 31
EXEC time is 31 milliseconds being the difference of 15:27:50.22 and
15:27:50.19
Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
15:27:50.29 Entry POP ALL
Exit POP ALL 0
Entry Delete program
15:27:50.35 67 Exit Init COBOL prog call 594
Setting up COBOL environment for FAAOISII
Entry EXEC CICS ADDRESS
Exit EXEC CICS ADDRESS 0
Entry EXEC CICS RETURN
15:27:50.38 Exit EXEC CICS RETURN 31
Entry POP ALL
Clear all CICS handles
Exit POP ALL 0
15:27:50.41 66 Exit Delete program 125
Entry Load Program
FAAPLTPI INIT
15:27:50.66 65 Entry Init prog COBOL call
15:27:50.69 Exit Init COBOL prog call 31
15:27:50.72 66 Exit Load Program 312
65 Entry EXEC CICS ADDRESS
15:27:50.75 Exit EXEC CICS ADDRESS 31
Entry EXEC CICS READ
FAACTFTB INIT
15:27:50.85 Entry FM GET EQUAL
15:27:50.88 66 Entry Init prog C call
Setting up C environment
15:27:50.97 Exit Init prog C call 94
Entry EXEC CICS ADDRESS
15:27:51.00 Exit EXEC CICS ADDRESS 31
Entry EXEC CICS START
PA21 INIT
START transaction PA21 from transaction INIT
15:27:51.32 65 Exit FM GET EQUAL 187
Exit EXEC CICS READ 281
Entry EXEC CICS HANDLE
15:27:51.35 Exit EXEC CICS HANDLE 31
15:27:51.38 Entry EXEC CICS START
CLOG INIT
START transaction CLOG from transaction INIT
15:27:51.47 66 Exit EXEC CICS START 187
Entry EXEC CICS WRITE OPERATOR
15:27:51.50 Exit EXEC CICS WRITE OPERATOR 31
Entry EXEC CICS XCTL
15:27:51.57 65 Exit EXEC CICS START 188
Entry Load Program
FAAMGSON INIT
15:27:52.07 66 Exit EXEC CICS XCTL 532
15:27:52.10 Entry POP ALL
Exit POP ALL 0
Entry Delete program
Deleting program so was not marked resident
15:27:52.13 Exit Delete program 31
15:27:52.16 65 Exit Load Program 563
15:27:52.19 Entry Init prog COBOL call
Exit Init COBOL prog call 0
15:27:52.22 Entry EXEC CICS READ
FAAMGFMG INIT
Entry FM GET EQUAL
15:27:52.25 62 Entry GLBL File Manager request
15:27:52.29 66 Entry Load Program
FAAOIS04 INIT
Program FAAOISS04 will run on each application process as the second part of
PLT processing
15:27:52.32 Exit Load Program 0
15:27:52.35 Entry Init prog COBOL call
Exit Init COBOL prog call 0
Entry EXEC CICS RETURN
15:27:52.38 Exit EXEC CICS RETURN 31
Entry POP ALL
Exit POP ALL 0
15:27:52.41 Entry GET message
Entry FM GET EQUAL
67 Entry Delete program
15:27:52.44 Exit Delete program 31
15:27:52.47 Entry Load Program
FAAOIS04 INIT
Second load of program FAAOISS04
15:27:52.57 Exit Load Program 94
Entry Init prog COBOL call
15:27:52.60 Exit Init COBOL prog call 31
Entry EXEC CICS RETURN
15:27:52.63 Exit EXEC CICS RETURN 31
Entry POP ALL
Exit POP ALL 0
15:27:52.66 Entry GET message
Entry FM GET EQUAL
15:27:52.72 62 Exit GLBL File Manager request 438
Entry GLBL File Manager request
65 Exit FM GET EQUAL 469
15:27:52.75 Exit EXEC CICS READ 500
Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
Entry POP P tab
15:27:52.82 Exit POP P tab 63
15:27:52.88 Entry EXEC CICS LINK
Exit EXEC CICS LINK 0
15:27:52.91 Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
Entry POP ALL
15:27:52.94 Exit POP ALL 31
Entry Delete program
15:27:53.19 Exit Delete program 250
Entry Load Program
FAAOIS04 INIT
Third load of program FAAOISS04
15:27:53.32 Exit Load Program 125
Entry Init prog COBOL call
15:27:53.35 Exit Init COBOL prog call 31
Entry EXEC CICS RETURN
15:27:53.38 Exit EXEC CICS RETURN 31
Entry POP ALL
Exit POP ALL 0
15:27:53.41 Entry GET message
Entry FM GET EQUAL
15:27:53.47 62 Exit GLBL File Manager request 750
Entry GLBL File Manager request
66 Exit FM GET EQUAL 1062
Exit GET MESSAGE 1062
15:27:53.54 62 Exit GLBL File Manager request 63
Entry GLBL File Manager request
67 Exit FM GET EQUAL 875
Exit GET MESSAGE 875
15:27:54.07 Entry EXEC CICS ASKTIME
15:27:54.10 Exit EXEC CICS ASKTIME 31
Entry Task Initiation PA21
PA21 now starting
Entry Delete program
15:27:54.13 Exit Delete program 31
15:27:54.16 62 Exit GLBL File Manager request 625
65 Exit FM GET EQUAL 750
15:27:54.19 Exit GET MESSAGE 781
15:27:54.25 Entry EXEC CICS ASKTIME
15:27:54.29 67 Entry Load Program
PA2PLTPI PA21
15:27:54.72 66 Entry EXEC CICS ASKTIME
Exit EXEC CICS ASKTIME 0
15:27:54.75 Entry Task Initiation CRSR
CRSR now starting on process 66
Entry Delete program
65 Exit EXEC CICS ASKTIME 500
15:27:54.79 Entry Task Initiation CLOG
CLOG now starting on process 65
15:27:54.82 Entry Delete program
15:27:54.88 Exit Delete program 62
Entry Load Program
FAALSPDL CLOG
15:27:55.16 Exit Load Program 282
15:27:55.22 Entry Init prog COBOL call
Exit Init COBOL prog call 0
15:27:55.25 66 Exit Delete program 500
Entry Load Program
FAAOIPTD CRSR
15:27:55.29 65 Entry EXEC CICS ASSIGN
Exit EXEC CICS ASSIGN 0
Entry EXEC CICS ASSIGN
Exit EXEC CICS ASSIGN 0
15:27:55.32 Entry EXEC CICS SEND
Entry FM GET EQUAL
15:27:55.35 62 Entry GLBL File Manager request
File Manager call in middle of a EXEC CICS SEND, must be a SEND MAP
15:27:55.50 67 Exit Load Program 1218
15:27:55.54 Entry Init prog C call
15:27:55.57 66 Exit Load Program 313
15:27:55.69 Entry Init prog COBOL call
15:27:55.72 67 Exit Init prog C call 187
Entry EXEC CICS ADDRESS
15:27:55.75 Exit EXEC CICS ADDRESS 31
Entry EXEC CICS CHANGE TASK
Exit EXEC CICS CHANGE TASK 0
Entry EXEC CICS WRITE OPERATOR
15:27:55.85 66 Exit Init COBOL prog call 156
Entry EXEC CICS ADDRESS
Exit EXEC CICS ADDRESS 0
15:27:55.88 67 Exit EXEC CICS WRITE OPERATOR 125
15:27:55.91 Entry EXEC CICS STARTBR
FAACTFTB PA21
Performance Analyser START BROWSE of resource data
Entry FM GET EQUAL KEY
66 Entry EXEC CICS ASSIGN
15:27:55.94 Exit EXEC CICS ASSIGN 31
Entry EXEC CICS STARTBR
FAACTFTB CRSR
CRSR browsing resource data at same time
15:27:56.29 Entry FM GET EQUAL KEY
15:27:56.32 67 Exit FM GET EQUAL KEY 62
Entry FM GET GTEQ KEY
Exit FM GET GTEQ KEY 0
EXEC CICS STARTBR caused 2 calls to the File Manager, a GET EQUAL and a GET
GTEQ
Exit EXEC CICS STARTBR 62
15:27:56.35 Entry EXEC CICS READNEXT
FAACTFTB PA21
Entry FM GET GTEQ
15:27:56.38 66 Exit FM GET EQUAL KEY 93
Entry FM GET GTEQ KEY
15:27:56.41 Exit FM GET GTEQ KEY 32
Exit EXEC CICS STARTBR 125
15:27:56.44 Entry EXEC CICS ENDBR
END BROWSE follows START BROWSE immediately, probably checking for a a record
and when not there exiting
FAACTFTB CRSR
15:27:56.47 62 Exit GLBL File Manager request 781
66 Exit EXEC CICS ENDBR 31
Entry EXEC CICS RETURN
15:27:56.50 Exit EXEC CICS RETURN 31
Entry POP ALL
Exit POP ALL 0
15:27:56.54 65 Exit FM GET EQUAL 875
66 Entry clear POST
Exit Internal clear POST 0
Entry EXEC CICS SYNCPOINT
15:27:57.00 65 Exit EXEC CICS SEND 1343
Entry EXEC CICS RETURN
15:27:57.04 Exit EXEC CICS RETURN 32
Implicit SYNCPOINT at end of transaction, no CICS recoverable resources
involved
66 Exit EXEC CICS SYNCPOINT 500
Exit Task Termination 1938
15:27:57.07 65 Entry POP ALL
Exit POP ALL 0
Entry clear POST
15:27:57.10 Exit Internal clear POST 31
Entry EXEC CICS SYNCPOINT
Implicit SYNCPOINT at end of transaction, no CICS recoverable resources
involved
Exit EXEC CICS SYNCPOINT 0
15:27:57.13 Exit Task Termination 1999
15:27:57.19 67 Exit FM GET GTEQ 844
15:27:57.22 Exit EXEC CICS READNEXT 875
Entry EXEC CICS WRITE OPERATOR
15:27:57.25 Exit EXEC CICS WRITE OPERATOR 31
Entry EXEC CICS READNEXT
FAACTFTB PA21
Entry FM GET NEXT
15:27:57.29 Exit FM GET NEXT 32
Exit EXEC CICS READNEXT 32
.. .. .. .. .. ..
.. .. .. .. .. ..
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:00.29 Entry FM GET NEXT
65 Entry EXEC CICS ASKTIME
Exit EXEC CICS ASKTIME 0
15:28:00.32 Entry Task Initiation CLOG
CLOG now starting on process 65
Entry Load Program
FAALSPDL CLOG
15:28:00.35 Exit Load Program 31
Entry Init prog COBOL call
15:28:00.38 Exit Init COBOL prog call 31
Entry EXEC CICS RECEIVE
Exit EXEC CICS RECEIVE 0
15:28:00.41 Entry EXEC CICS XCTL
15:28:00.63 Exit EXEC CICS XCTL 218
Entry POP ALL
Exit POP ALL 0
15:28:00.66 67 Exit FM GET NEXT 375
Exit EXEC CICS READNEXT 375
Entry EXEC CICS WRITE OPERATOR
15:28:00.88 Exit EXEC CICS WRITE OPERATOR 218
15:28:00.91 Entry EXEC CICS READNEXT
FAACTFTB PA21
Entry FM GET NEXT
65 Entry Delete program
15:28:01.29 Exit Delete program 375
15:28:01.32 Entry Load Program
FAALSPSN CLOG
Exit Load Program 0
15:28:01.35 Entry Init prog COBOL call
Exit Init COBOL prog call 0
15:28:01.38 Entry EXEC CICS SIGNOFF
Exit EXEC CICS SIGNOFF 0
Entry EXEC CICS SEND
15:28:01.41 Entry FM GET EQUAL
File Manager call in middle of a EXEC CICS SEND, must be a SEND MAP
62 Entry GLBL File Manager request
15:28:01.47 67 Exit FM GET NEXT 562
Exit EXEC CICS READNEXT 562
.. .. .. .. .. ..
.. .. .. .. .. ..
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:02.38 Entry FM GET NEXT
62 Exit GLBL File Manager request 937
15:28:02.41 65 Exit FM GET EQUAL 969
15:28:03.16 67 Exit FM GET NEXT 782
Exit EXEC CICS READNEXT 782
Entry EXEC CICS WRITE OPERATOR
15:28:03.19 Exit EXEC CICS WRITE OPERATOR 31
15:28:03.22 Entry EXEC CICS READNEXT
FAACTFTB PA21
Entry FM GET NEXT
15:28:03.25 65 Exit EXEC CICS SEND 1844
15:28:03.57 Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
Entry POP ALL
15:28:03.60 Exit POP ALL 31
Entry clear POST
15:28:03.63 Exit Internal clear POST 31
Entry EXEC CICS SYNCPOINT
Implicit SYNCPOINT at end of transaction, no CICS recoverable resources
involved
Exit EXEC CICS SYNCPOINT 0
Exit Task Termination 3281
15:28:03.69 67 Exit FM GET NEXT 469
Exit EXEC CICS READNEXT 469
Entry EXEC CICS WRITE OPERATOR
15:28:03.72 Exit EXEC CICS WRITE OPERATOR 31
Entry EXEC CICS READNEXT
FAACTFTB PA21
.. .. .. .. .. ..
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:17.69 Entry FM GET NEXT
65 Entry EXEC CICS ASKTIME
15:28:18.16 Exit EXEC CICS ASKTIME 469
Entry Task Initiation CLOG
15:28:18.19 Entry Delete program
15:28:18.25 Exit Delete program 62
Entry Load Program
FAALSPDL CLOG
15:28:18.38 Exit Load Program 125
15:28:18.41 Entry Init prog COBOL call
15:28:18.44 Exit Init COBOL prog call 31
Entry EXEC CICS XCTL
15:28:18.50 67 Exit FM GET NEXT 812
Exit EXEC CICS READNEXT 843
Entry EXEC CICS WRITE OPERATOR
15:28:18.54 Exit EXEC CICS WRITE OPERATOR 32
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:18.57 Entry FM GET NEXT
15:28:19.10 65 Exit EXEC CICS XCTL 656
15:28:19.13 Entry POP ALL
Exit POP ALL 0
Entry Delete program
15:28:19.19 Exit Delete program 63
15:28:19.22 Entry Load Program
FAALSPSN CLOG
Exit Load Program 0
15:28:19.25 Entry Init prog COBOL call
Exit Init COBOL prog call 0
15:28:19.32 Entry EXEC CICS HANDLE
Exit EXEC CICS HANDLE 0
Entry EXEC CICS HANDLE
Exit EXEC CICS HANDLE 0
15:28:19.35 67 Exit FM GET NEXT 781
Exit EXEC CICS READNEXT 812
Entry EXEC CICS WRITE OPERATOR
15:28:19.38 Exit EXEC CICS WRITE OPERATOR 31
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:19.41 Entry FM GET NEXT
65 Entry EXEC CICS RECEIVE
15:28:19.44 Exit EXEC CICS RECEIVE 31
Entry EXEC CICS SIGNON
Entry FM GET EQUAL
File Manager call in middle of a EXEC CICS SIGNON
15:28:19.79 67 Exit FM GET NEXT 375
Exit EXEC CICS READNEXT 407
Entry EXEC CICS WRITE OPERATOR
15:28:19.82 Exit EXEC CICS WRITE OPERATOR 31
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:19.85 Entry FM GET NEXT
15:28:20.16 65 Exit FM GET EQUAL 688
15:28:20.19 67 Exit FM GET NEXT 344
15:28:20.22 Exit EXEC CICS READNEXT 375
Entry EXEC CICS WRITE OPERATOR
15:28:20.25 65 Exit EXEC CICS SIGNON 781
Entry EXEC CICS ASKTIME
67 Exit EXEC CICS WRITE OPERATOR 31
15:28:20.29 Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:20.60 Entry FM GET NEXT
15:28:20.63 65 Exit EXEC CICS ASKTIME 375
Entry EXEC CICS WRITEQ TS/TD
CSCS CLOG
15:28:20.66 Entry FM GET GLEQ MLOCK
62 Entry GLBL File Manager request
File Manager call switched to Global Task, must be non-recoverable
15:28:20.69 Exit GLBL File Manager request 31
65 Exit FM GET GLEQ MLOCK 31
Entry FM INSERT
15:28:20.72 62 Entry GLBL File Manager request
15:28:21.04 Exit GLBL File Manager request 313
65 Exit FM INSERT 344
Exit EXEC CICS WRITEQ TS/TD 375
15:28:21.07 Entry Load Program
FAAMGSON CLOG
15:28:21.10 67 Exit FM GET NEXT 468
Exit EXEC CICS READNEXT 780
Entry EXEC CICS WRITE OPERATOR
15:28:21.16 Exit EXEC CICS WRITE OPERATOR 63
15:28:21.19 Entry EXEC CICS READNEXT
FAACTFTB PA21
Entry FM GET NEXT
15:28:21.66 65 Exit Load Program 594
15:28:21.75 67 Exit FM GET NEXT 562
Exit EXEC CICS READNEXT 562
Entry EXEC CICS WRITE OPERATOR
15:28:21.79 65 Entry Init prog COBOL call
15:28:21.82 Exit Init COBOL prog call 31
Entry EXEC CICS READ
FAAMGFMG CLOG
CICS for OS/2 getting message text
15:28:21.85 67 Exit EXEC CICS WRITE OPERATOR 94
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:21.91 Entry FM GET NEXT
65 Entry FM GET EQUAL
15:28:21.94 62 Entry GLBL File Manager request
15:28:22.25 67 Exit FM GET NEXT 343
15:28:22.29 Exit EXEC CICS READNEXT 407
.. .. .. .. .. ..
.. .. .. .. .. ..
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:23.22 Entry FM GET NEXT
15:28:23.25 62 Exit GLBL File Manager request 1281
15:28:23.60 65 Exit FM GET EQUAL 1656
Exit EXEC CICS READ 1719
Entry EXEC CICS RETURN
15:28:23.63 Exit EXEC CICS RETURN 31
15:28:23.94 Entry POP P tab
15:28:23.97 Exit POP P tab 31
15:28:24.00 Entry EXEC CICS LINK
Exit EXEC CICS LINK 0
Entry EXEC CICS SEND
15:28:24.35 Exit EXEC CICS SEND 344
Entry EXEC CICS RETURN
15:28:24.38 Exit EXEC CICS RETURN 31
Entry POP ALL
Exit POP ALL 0
Entry clear POST
15:28:24.41 67 Exit FM GET NEXT 1188
Exit EXEC CICS READNEXT 1188
Entry EXEC CICS WRITE OPERATOR
15:28:24.44 Exit EXEC CICS WRITE OPERATOR 31
Entry EXEC CICS READNEXT
FAACTFTB PA21
15:28:24.47 Entry FM GET NEXT
65 Exit Internal clear POST 94
Entry EXEC CICS SYNCPOINT
Implicit SYNCPOINT at end of transaction, no CICS recoverable resources
involved
15:28:24.82 Exit EXEC CICS SYNCPOINT 344
Exit Task Termination 6531
15:28:24.88 67 Exit FM GET NEXT 406
Exit EXEC CICS READNEXT 437
.. .. .. .. .. ..
.. .. .. .. .. ..
Entry EXEC CICS ENDBR
FAACTFTB PA21
15:28:29.63 Exit EXEC CICS ENDBR 0
15:28:30.07 Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
Entry POP ALL
15:28:30.10 Exit POP ALL 31
Entry clear POST
Exit Internal clear POST 0
Entry EXEC CICS SYNCPOINT
Implicit SYNCPOINT at end of transaction, no CICS recoverable resources
involved
15:28:30.13 Exit EXEC CICS SYNCPOINT 31
Exit Task Termination 32190
15:28:41.38 65 Entry EXEC CICS ASKTIME
15:28:41.41 Exit EXEC CICS ASKTIME 32
Entry Task Initiation CECI
Entry Delete program
15:28:41.47 Exit Delete program 62
Entry Load Program
FAAATPCI CECI
15:28:41.79 Exit Load Program 313
15:28:42.22 Entry Init prog COBOL call
15:28:42.25 Exit Init COBOL prog call 31
Entry EXEC CICS HANDLE
Exit EXEC CICS HANDLE 0
15:28:42.29 Entry EXEC CICS ASSIGN
Exit EXEC CICS ASSIGN 0
Entry EXEC CICS ASSIGN
15:28:42.32 Exit EXEC CICS ASSIGN 31
Entry EXEC CICS HANDLE
Exit EXEC CICS HANDLE 0
15:28:42.38 Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
Entry EXEC CICS GETMAIN
15:28:42.41 Exit EXEC CICS GETMAIN 32
Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
15:28:42.44 Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
Entry EXEC CICS GETMAIN
15:28:42.47 Exit EXEC CICS GETMAIN 31
Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
Entry EXEC CICS GETMAIN
15:28:42.50 Exit EXEC CICS GETMAIN 31
Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
Eight GETMAINs taking 94 milliseconds on this machine
15:28:42.54 Entry EXEC CICS RECEIVE
Exit EXEC CICS RECEIVE 0
15:28:42.57 Entry EXEC CICS SEND
Entry FM GET EQUAL
15:28:42.60 62 Entry GLBL File Manager request
15:28:42.72 Exit GLBL File Manager request 125
65 Exit FM GET EQUAL 156
15:28:43.41 Exit EXEC CICS SEND 844
Entry EXEC CICS RECEIVE
15:28:43.60 Exit EXEC CICS RECEIVE 187
15:28:43.66 Entry EXEC CICS SEND
15:28:43.94 Exit EXEC CICS SEND 281
15:28:43.97 Entry Load Program
PA2ABEND CECI
15:28:44.57 Exit Load Program 594
15:28:44.69 Entry Init prog C call
15:28:44.72 Exit Init prog C call 31
15:28:44.97 Entry EXEC CICS WRITE OPERATOR
15:28:45.00 Exit EXEC CICS WRITE OPERATOR 31
15:28:45.07 Entry EXEC CICS ABEND
Entry FM GET EQUAL
15:28:45.10 62 Entry GLBL File Manager request
15:28:45.13 Exit GLBL File Manager request 31
65 Exit FM GET EQUAL 62
CSMT CECI
Entry FM GET GLEQ MLOCK
15:28:45.16 62 Entry GLBL File Manager request
Message to CSMT queue, unrecoverable queue since switch to Global Task
Exit GLBL File Manager request 0
15:28:45.19 65 Exit FM GET GLEQ MLOCK 63
Entry FM INSERT
15:28:45.22 62 Entry GLBL File Manager request
Exit GLBL File Manager request 0
15:28:45.25 65 Exit FM INSERT 62
15:28:46.10 Exit EXEC CICS ABEND 1031
Entry POP P tab
Exit POP P tab 0
15:28:46.13 Entry EXEC CICS ASSIGN
Exit EXEC CICS ASSIGN 0
Entry EXEC CICS RECEIVE
15:28:46.19 Exit EXEC CICS RECEIVE 63
Entry EXEC CICS GETMAIN
15:28:46.22 Exit EXEC CICS GETMAIN 31
Entry EXEC CICS LINK
Exit EXEC CICS LINK 0
15:28:46.25 Entry EXEC CICS SEND
15:28:46.94 Exit EXEC CICS SEND 688
Entry EXEC CICS RECEIVE
15:28:47.91 Exit EXEC CICS RECEIVE 969
15:28:48.00 Entry EXEC CICS SEND
15:28:48.69 Exit EXEC CICS SEND 688
Entry EXEC CICS RECEIVE
15:28:49.16 Exit EXEC CICS RECEIVE 469
15:28:49.22 Entry EXEC CICS SEND
15:28:49.63 Exit EXEC CICS SEND 406
Conversational program, 3 RECEIVE/SEND pairs
Entry Load Program
PA2ABEND CECI
15:28:49.75 Exit Load Program 125
15:28:49.79 Entry Init prog C call
Exit Init prog C call 0
15:28:50.04 Entry EXEC CICS WRITE OPERATOR
15:28:50.07 Exit EXEC CICS WRITE OPERATOR 31
15:28:50.13 Entry EXEC CICS ABEND
Entry FM GET EQUAL
15:28:50.16 62 Entry GLBL File Manager request
Exit GLBL File Manager request 0
15:28:50.50 65 Exit FM GET EQUAL 375
CSMT CECI
Entry FM GET GLEQ MLOCK
Message to CSMT queue, unrecoverable queue since switch to Global Task
15:28:50.54 62 Entry GLBL File Manager request
Exit GLBL File Manager request 0
65 Exit FM GET GLEQ MLOCK 32
Entry FM INSERT
15:28:50.57 62 Entry GLBL File Manager request
15:28:50.66 Exit GLBL File Manager request 94
15:28:50.69 65 Exit FM INSERT 156
15:28:50.91 Exit EXEC CICS ABEND 782
Entry POP P tab
15:28:50.94 Exit POP P tab 31
Entry EXEC CICS ASSIGN
Exit EXEC CICS ASSIGN 0
15:28:51.00 Entry EXEC CICS FREEMAIN
Exit EXEC CICS FREEMAIN 0
Entry EXEC CICS RECEIVE
15:28:51.07 Exit EXEC CICS RECEIVE 63
Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
15:28:51.10 Entry EXEC CICS LINK
Exit EXEC CICS LINK 0
15:28:51.13 Entry EXEC CICS SEND
15:28:51.82 Exit EXEC CICS SEND 688
Entry EXEC CICS RECEIVE
15:28:52.60 Exit EXEC CICS RECEIVE 781
Entry EXEC CICS SEND
15:28:52.91 Exit EXEC CICS SEND 313
Still a conversational program, 2 RECEIVE/SEND pairs
Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
15:28:52.94 Entry POP ALL
Exit POP ALL 0
Entry clear POST
Exit Internal clear POST 0
15:28:52.97 Entry EXEC CICS SYNCPOINT
Implicit SYNCPOINT at end of transaction, no CICS recoverable resources
involved
Exit EXEC CICS SYNCPOINT 0
15:28:53.00 Exit Task Termination 11593
15:29:25.04 Entry EXEC CICS ASKTIME
Exit EXEC CICS ASKTIME 0
15:29:25.07 Entry Task Initiation PA2M
Entry Delete program
15:29:25.13 Exit Delete program 62
Entry Load Program
PA2MCDSP PA2M
15:29:25.47 Exit Load Program 344
Entry Init prog C call
15:29:25.54 Exit Init prog C call 63
Entry EXEC CICS ADDRESS
Exit EXEC CICS ADDRESS 0
15:29:25.57 Entry EXEC CICS RECEIVE
Exit EXEC CICS RECEIVE 0
Entry Load Program
PA2PLTSD PA2M
15:29:25.94 Exit Load Program 375
Actually LINKing to PA2PLTSD from PA2MCDSP
Entry Init prog C call
15:29:25.97 Exit Init prog C call 31
15:29:26.25 Entry EXEC CICS ENQ
62 Entry GLBL EXTRA ENQ request
Make sure only one printout at a time
15:29:26.34 Exit GLBL EXTRA ENQ request 86
15:29:26.36 65 Exit EXEC CICS ENQ 110
15:29:26.37 Entry EXEC CICS DUMP
Dump taken because of /du option on Performance Analyser. See page Application
Level Trace.
15:29:27.69 Exit EXEC CICS DUMP 1321
Entry EXEC CICS WRITE OPERATOR
15:29:27.72 Exit EXEC CICS WRITE OPERATOR 31
15:29:28.04 Entry EXEC CICS ADDRESS
15:29:28.07 Exit EXEC CICS ADDRESS 31
Entry EXEC CICS ADDRESS
Exit EXEC CICS ADDRESS 0
Entry EXEC CICS WRITE OPERATOR
Start message
15:29:28.10 Exit EXEC CICS WRITE OPERATOR 31
15:29:30.19 Entry EXEC CICS WRITE OPERATOR
End message
15:29:30.22 Exit EXEC CICS WRITE OPERATOR 31
Entry EXEC CICS DEQ
15:29:30.25 62 Entry GLBL EXTRA ENQ request
Exit GLBL EXTRA ENQ request 0
65 Exit EXEC CICS DEQ 31
Entry EXEC CICS RETURN
15:29:30.29 Exit EXEC CICS RETURN 32
15:29:30.32 Entry POP P tab
15:29:30.35 Exit POP P tab 31
Entry EXEC CICS LINK
15:29:30.38 Exit EXEC CICS LINK 31
Entry EXEC CICS SEND
Entry FM GET EQUAL
15:29:30.41 62 Entry GLBL File Manager request
15:29:30.94 Exit GLBL File Manager request 531
15:29:30.97 65 Exit FM GET EQUAL 594
15:29:31.41 Exit EXEC CICS SEND 1032
SEND MAP because call to System File Manager in middle of SEND
15:29:31.44 Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
Entry POP ALL
Exit POP ALL 0
Entry clear POST
15:29:31.47 Exit Internal clear POST 31
Entry EXEC CICS SYNCPOINT
Implicit SYNCPOINT at end of transaction, no CICS recoverable resources
involved
Exit EXEC CICS SYNCPOINT 0
Exit Task Termination 6406
15:29:33.82 Entry EXEC CICS ASKTIME
Exit EXEC CICS ASKTIME 0
15:29:33.85 Entry Task Initiation PA2M
Entry Load Program
PA2MCDSP PA2M
Exit Load Program 0
15:29:33.88 Entry Init prog C call
Exit Init prog C call 0
15:29:33.91 Entry EXEC CICS ADDRESS
Exit EXEC CICS ADDRESS 0
Entry EXEC CICS SEND
15:29:34.19 Exit EXEC CICS SEND 281
Entry EXEC CICS RETURN
15:29:34.25 Exit EXEC CICS RETURN 62
Entry POP ALL
Exit POP ALL 0
15:29:34.29 Entry clear POST
Exit Internal clear POST 0
Entry EXEC CICS SYNCPOINT
Implicit SYNCPOINT at end of transaction, no CICS recoverable resources
involved
Exit EXEC CICS SYNCPOINT 0
15:29:34.32 Exit Task Termination 469
15:29:37.85 Entry EXEC CICS ASKTIME
15:29:37.88 Exit EXEC CICS ASKTIME 31
Entry Task Initiation CQIT
Entry Delete program
15:29:37.91 Exit Delete program 32
Entry Load Program
FAAOISQT CQIT
15:29:38.13 Exit Load Program 218
Entry Init prog COBOL call
15:29:38.16 Exit Init COBOL prog call 32
Entry EXEC CICS ADDRESS
15:29:38.19 Exit EXEC CICS ADDRESS 31
Entry EXEC CICS ASSIGN
15:29:38.22 Exit EXEC CICS ASSIGN 31
Entry EXEC CICS RECEIVE
Exit EXEC CICS RECEIVE 0
Entry EXEC CICS PERFORM SHUTDOWN
I CQIT
Transaction CQIT doing a SHUTDOWN IMMEDIATE
15:29:38.35 Exit EXEC CICS PERFORM SHUTDOWN 125
Entry EXEC CICS ABEND
Entry FM GET EQUAL
15:29:40.32 62 Entry GLBL TASK termination
15:29:40.35 Exit GLBL TASK termination 31
Entry GLBL TASK termination
(C) Copyright IBM Corp. 1994. All rights reserved.
ΓòÉΓòÉΓòÉ 13. User Clocks ΓòÉΓòÉΓòÉ
A function that is often required when gathering and monitoring system
statistics is the ability to measure the time taken to execute a section of
application code and the number of times the code was run. This requirement is
satisfied in Performance Analyser by a function called User Clocks. Up to four
clocks can be defined in any transaction, numbered, fairly obviously, 1 through
4.
Included with Performance Analyser is the source file, PA2ABEND.CCS, (some of
which is reproduced in Part of sample user clocks code (PA2ABEND.CCS)) and its
compiled version PA2ABEND.DLL. It demonstrates how to implement user clocks
and also shows what happens if a a mistake is made in the starting and stopping
of the clocks. When CICS is running, issue
CECI LINK PROGRAM(PA2ABEND)
in a 3270 window and press the Enter key (normally the Right Ctrl key) to get
it to execute.
PA2CLOCK(PA2BEGIN,1); /* start clock 1 */
PA2CLOCK(PA2BEGIN,2); /* start clock 2 */
PA2CLOCK(PA2BEGIN,3); /* start clock 3 */
PA2CLOCK(PA2END,4); /* stop clock 4, before started */
/* get stop before start message in FAASTATS.ERR */
PA2CLOCK('X',2); /* pass non valid function value */
/* get non valid function message in FAASTATS.ERR */
PA2CLOCK(PA2BEGIN,7); /* start clock 7, out of range 1-4 */
/* get out of range message in FAASTATS.ERR */
/* Perform a CICS statement to put some time on clocks 1,2,and 3 */
EXEC CICS WRITE OPERATOR
TEXT(Message)
TEXTLENGTH((long)strlen(Message));
PA2CLOCK(PA2END,2); /* end clock 2, to get some real data */
PA2CLOCK(PA2BEGIN,3); /* start clock 3, without having stopped it first */
/* get not stopped and not reset clock message in */
/* FAASTATS.ERR */
. . . . . . . .
. . . . . . . .
EXEC CICS ABEND ABCODE("PA2X");
/* get not stopped clock 1 and 3 before end of */
/* transaction message in FAASTATS.ERR */
Part of sample user clocks code (PA2ABEND.CCS)
Clocks 1 and 3 will be stopped at the end of the transaction automatically even
if they are not stopped explicitly (although an error message will be generated
in FAASTATS.ERR)
The FAASTATS.ERR file will also be included in the statistics and monitoring
data produced by the transaction PA2M in the file PA2STATS.DAT. The sample code
above produces the bucket statistics shown in Bucket statistics produced by
PA2ABEND.
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Bucket Γöé Xactn Γöé Times Γöé Times Γöé Total Γöé Average Γöé
Γöé number Γöé name Γöéstarted Γöé stopped Γöé (secs) Γöé (secs) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé Clock(1)Γöé CECI Γöé 1 Γöé 0 Γöé 9.91 Γöé 9.906 Γöé
Γöé Clock(2)Γöé CECI Γöé 1 Γöé 1 Γöé 0.03 Γöé 0.031 Γöé
Γöé Clock(3)Γöé CECI Γöé 2 Γöé 0 Γöé 9.94 Γöé 4.969 Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
Bucket statistics produced by PA2ABEND
From this it can be seen that the EXEC CICS WRITE OPERATOR took between 1 and 2
timer units from the result of the Clock(2) value. Clock(1) and Clock(3) totals
are almost the same (ie approximately 9.91 secs). They look long, and imply
that the time between the clock being started and then stopped automatically at
the end of the transaction is due to user "think time" and that the task is
therefore conversational. Also, the effect of starting Clock(3) twice can be
seen; the times started value is 2 and therefore affects the average (ie it is
half that of Clock(1)).
In order to resolve the PA2CLOCKinvocations, you will have to add PA2CLOCK.LIB
to your link edit library list.
ΓòÉΓòÉΓòÉ 14. Using the supplied sample program (PA2BR14) ΓòÉΓòÉΓòÉ
IEFBR14 is a well known mainframe program which just returns to the caller when
invoked. PA2BR14 supplies this function which can be invoked in several ways.
1. By an EXEC CICS LINK (either locally or remote). The supplied COMMAREA is
returned.
2. By an EXEC CICS LINK SYNCONRETURN. A syncpoint is taken and the supplied
COMMAREA is returned to the remote invoker.
3. By an EXEC CICS SEND or CONVERSE over an LU6.2 link. Either Distributed
Transaction Processing (APPC) or Transaction Routing from a remote 3270
terminal or a CICS for OS/2 terminal/client can be used.
The supplied transaction (PA22) in PA2EXMPL group can be invoked from a
3270 terminal.
4. By an EXEC CICS WRITEQ. This will read the queue and return. If a trigger
level is set up in the DCT then another transaction may be invoked.
5. By an EXEC CICS START with data. This will return the data and start
another transaction, the ID of which is the same as the first four
characters of the returned data. PA22 can be used with CECI to test this
out.
6. By an EXEC CICS START with no data. This will start itself again and thus
go into a loop. This can be useful for assessing the maximum throughput of
a system.
ΓòÉΓòÉΓòÉ 15. Trap information ΓòÉΓòÉΓòÉ
Following a trap and if the application trace is running, Performance Analyser
will output the last 64 calls made to the server in the PA2STATS.DAT file. If
the trace is not running, only the trap call will be output.
Figure Function callswill be of use in interpreting the last 64 calls.
Function calls
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Function Γöé Meaning Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 10 Γöé EXEC CICS SET TRANSACTION Γöé
Γöé 11 Γöé EXEC CICS INQUIRE TRANSACTION Γöé
Γöé 20 Γöé Transaction routing Γöé
Γöé 22 Γöé Delete shipped terminal Γöé
Γöé 28 Γöé EXEC CICS SET CONNECTION Γöé
Γöé 29 Γöé EXEC CICS INQUIRE CONNECTION Γöé
Γöé 30 Γöé EXEC CICS SET FILE Γöé
Γöé 31 Γöé EXEC CICS INQUIRE FILE Γöé
Γöé 40 Γöé EXEC CICS READ Γöé
Γöé 41 Γöé EXEC CICS WRITE Γöé
Γöé 42 Γöé EXEC CICS REWRITE Γöé
Γöé 43 Γöé EXEC CICS DELETE Γöé
Γöé 44 Γöé EXEC CICS UNLOCK Γöé
Γöé 45 Γöé EXEC CICS STARTBR Γöé
Γöé 46 Γöé EXEC CICS READNEXT Γöé
Γöé 47 Γöé EXEC CICS READPREV Γöé
Γöé 48 Γöé EXEC CICS RESETBR Γöé
Γöé 49 Γöé EXEC CICS ENDBR Γöé
Γöé 51 Γöé EXEC CICS CONVERSE Γöé
Γöé 52 Γöé EXEC CICS ISSUE Γöé
Γöé 53 Γöé EXEC CICS SEND Γöé
Γöé 54 Γöé EXEC CICS RECEIVE Γöé
Γöé 55 Γöé Task control WRITE Γöé
Γöé 56 Γöé Task control READ Γöé
Γöé 57 Γöé Task control ERASE Γöé
Γöé 58 Γöé Terminal WSU initialise Γöé
Γöé 60 Γöé EXEC CICS SET EXEC CICS TASK Γöé
Γöé 61 Γöé EXEC CICS INQUIRE TASK Γöé
Γöé 62 Γöé EXEC CICS CHANGE TASK Γöé
Γöé 63 Γöé EXEC CICS SET PROGRAM Γöé
Γöé 64 Γöé EXEC CICS INQUIRE PROGRAM Γöé
Γöé 70 Γöé EXEC CICS GETMAIN Γöé
Γöé 71 Γöé EXEC CICS SET TRACEDEST Γöé
Γöé 72 Γöé EXEC CICS ENTER Γöé
Γöé 73 Γöé EXEC CICS INQUIRE TRACEDEST Γöé
Γöé 74 Γöé EXEC CICS FREEMAIN Γöé
Γöé 76 Γöé ENQ internal Γöé
Γöé 77 Γöé DEQ internal Γöé
Γöé 79 Γöé EXEC CICS DUMP Γöé
Γöé 80 Γöé EXEC CICS SET TERMINAL Γöé
Γöé 81 Γöé EXEC CICS INQUIRE TERMINAL Γöé
Γöé 82 Γöé EXEC CICS WRITE OPERATOR Γöé
Γöé 83 Γöé EXEC CICS INQUIRE SYSTEM Γöé
Γöé 90 Γöé EXEC CICS ASKTIME Γöé
Γöé 91 Γöé Pop all Γöé
Γöé 92 Γöé Start transaction Γöé
Γöé 93 Γöé End transaction Γöé
Γöé 94 Γöé EXEC CICS ABEND Γöé
Γöé 96 Γöé Get message Γöé
Γöé 97 Γöé Initial COBOL program call Γöé
Γöé 98 Γöé EXEC CICS SYNCPOINT Γöé
Γöé 99 Γöé Initialise Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Function Γöé Meaning Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 100 Γöé EXEC CICS LINK Γöé
Γöé 101 Γöé EXEC CICS XCTL Γöé
Γöé 102 Γöé EXEC CICS ASSIGN Γöé
Γöé 103 Γöé EXEC CICS HANDLE Γöé
Γöé 105 Γöé EXEC CICS ADDRESS Γöé
Γöé 110 Γöé EXEC CICS RETURN Γöé
Γöé 111 Γöé EXEC CICS PUSH Γöé
Γöé 112 Γöé EXEC CICS POP Γöé
Γöé 113 Γöé Pop P table Γöé
Γöé 114 Γöé Link/Xctl Γöé
Γöé 115 Γöé Delete program Γöé
Γöé 116 Γöé EXEC CICS LOAD Γöé
Γöé 120 Γöé EXEC CICS TS/TD WRITEQ Γöé
Γöé 121 Γöé EXEC CICS TS/TD READQ Γöé
Γöé 122 Γöé EXEC CICS TS/TD DELETEQ Γöé
Γöé 123 Γöé EXEC CICS START Γöé
Γöé 124 Γöé EXEC CICS RETRIEVE Γöé
Γöé 125 Γöé EXEC CICS CANCEL Γöé
Γöé 130 Γöé EXEC CICS SET TDQUEUE Γöé
Γöé 131 Γöé EXEC CICS INQUIRE TDQUEUE Γöé
Γöé 160 Γöé EXEC CICS SIGNON Γöé
Γöé 161 Γöé EXEC CICS SIGNOFF Γöé
Γöé 170 Γöé Clear post Γöé
Γöé 171 Γöé EXEC CICS POST Γöé
Γöé 172 Γöé EXEC CICS WAIT Γöé
Γöé 173 Γöé EXEC CICS DELAY Γöé
Γöé 174 Γöé EXEC CICS FORMATTIME Γöé
Γöé 180 Γöé EXEC CICS ENQ Γöé
Γöé 181 Γöé EXEC CICS DEQ Γöé
Γöé 182 Γöé EXEC CICS SUSPEND Γöé
Γöé 197 Γöé Initialise C program call Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 200 Γöé EDF closing Γöé
Γöé 297 Γöé Initialise EBCDIC program call Γöé
Γöé 397 Γöé Initialise PLI program call Γöé
Γöé 201 Γöé EXEC CICS ALLOCATE Γöé
Γöé 202 Γöé EXEC CICS EXTRACT Γöé
Γöé 203 Γöé EXEC CICS CONNECT Γöé
Γöé 204 Γöé EXEC CICS FREE Γöé
Γöé 206 Γöé EXEC CICS PERFORM SHUTDOWN Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Function Γöé Meaning Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 512 Γöé File Manager OPEN Γöé
Γöé 513 Γöé File Manager CLOSE Γöé
Γöé 514 Γöé File Manager INSERT Γöé
Γöé 515 Γöé File Manager UPDATE Γöé
Γöé 516 Γöé File Manager DELETE Γöé
Γöé 517 Γöé File Manager GET EQUAL Γöé
Γöé 518 Γöé File Manager GET NEXT Γöé
Γöé 519 Γöé File Manager GET PREV Γöé
Γöé 520 Γöé File Manager GET GT Γöé
Γöé 521 Γöé File Manager GET GTEQ Γöé
Γöé 522 Γöé File Manager GET GL Γöé
Γöé 523 Γöé File Manager GET GLEQ Γöé
Γöé 524 Γöé File Manager GET FIRST Γöé
Γöé 525 Γöé File Manager GET LAST Γöé
Γöé 526 Γöé File Manager CREATE Γöé
Γöé 531 Γöé File Manager BEGIN TRANSACTION Γöé
Γöé 532 Γöé File Manager END TRANSACTION Γöé
Γöé 533 Γöé File Manager ABORT TRANSACTION Γöé
Γöé 534 Γöé File Manager GET POSITION Γöé
Γöé 535 Γöé File Manager GET DIRECT Γöé
Γöé 536 Γöé File Manager STEP NEXT Γöé
Γöé 539 Γöé File Manager UNLOCK Γöé
Γöé 567 Γöé File Manager GET EQUAL KEY Γöé
Γöé 568 Γöé File Manager GET NEXT KEY Γöé
Γöé 569 Γöé File Manager GET PREV KEY Γöé
Γöé 570 Γöé File Manager GET GT KEY Γöé
Γöé 571 Γöé File Manager GET GTEQ KEY Γöé
Γöé 572 Γöé File Manager GET GL KEY Γöé
Γöé 573 Γöé File Manager GET GLEQ KEY Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 617 Γöé File Manager GET EQUAL LOCK Γöé
Γöé 618 Γöé File Manager GET NEXT LOCK Γöé
Γöé 619 Γöé File Manager GET PREV LOCK Γöé
Γöé 620 Γöé File Manager GET GT LOCK Γöé
Γöé 621 Γöé File Manager GET GTEQ LOCK Γöé
Γöé 622 Γöé File Manager GET GL LOCK Γöé
Γöé 623 Γöé File Manager GET GLEQ LOCK Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 817 Γöé File Manager GET EQUAL MLOCK Γöé
Γöé 818 Γöé File Manager GET NEXT MLOCK Γöé
Γöé 819 Γöé File Manager GET PREV MLOCK Γöé
Γöé 820 Γöé File Manager GET GT MLOCK Γöé
Γöé 821 Γöé File Manager GET GTEQ MLOCK Γöé
Γöé 822 Γöé File Manager GET GL MLOCK Γöé
Γöé 823 Γöé File Manager GET GLEQ MLOCK Γöé
Γöé 825 Γöé File Manager MBEGIN TRANSACTION Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé Function Γöé Meaning Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 1024 Γöé Task initialise terminal Γöé
Γöé 1281 Γöé Global log message Γöé
Γöé 1282 Γöé Global BTRIEVE request Γöé
Γöé 1284 Γöé Global extra-partition TD request Γöé
Γöé 1285 Γöé Global extra-partition ENQ request Γöé
Γöé 1286 Γöé Global task purge request Γöé
Γöé 1290 Γöé Global task initialisation Γöé
Γöé 1291 Γöé Global task termination Γöé
Γöé 1292 Γöé Global terminal attach Γöé
Γöé 1293 Γöé Global terminal detach Γöé
Γöé 1294 Γöé Global log thread error Γöé
Γöé 1295 Γöé Global ETI request Γöé
Γöé 1296 Γöé Global ETI result Γöé
Γöé 1301 Γöé Global getmain request Γöé
Γöé 1302 Γöé Global freemain request Γöé
Γöé 1303 Γöé Global program load Γöé
Γöé 1304 Γöé Global start task Γöé
Γöé 1305 Γöé Global PNA request Γöé
Γöé 1306 Γöé Global givemain request Γöé
Γöé 1307 Γöé Global querymain request Γöé
Γöé 1308 Γöé Global performance request Γöé
Γöé 1309 Γöé Open task global queue semaphore Γöé
Γöé 1310 Γöé Internal request Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé 4096 Γöé TRAP Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ 16. Performance Analyser statistics file ΓòÉΓòÉΓòÉ
This appendix provides details on the content of the Performance Analyser
statistics file, PA2STATS.DAT.
PA2STATS.DAT is an ASCII file that can be viewed with a standard PC
editor/browser or printed on a line printer. It is used as an "append" file
(that is, each time new data is collected it is added to the end of the file).
The file will thus continue to grow until specific action is taken to delete
it. The file is closed after use so that it may be accessed by other processes
in the system.
An example of a PA2STATS.DAT file generated by Performance Analyser is shown in
An example of a PA2STATS.DAT file whilst Explanation of PA2STATS.DAT file
entries provides a full description of the file content.
ΓòÉΓòÉΓòÉ 16.1. Sample PA2STATS.DAT file ΓòÉΓòÉΓòÉ
An example of a PA2STATS.DAT file
Performance Analyser for
CICS for OS/2 Version 2
5764-091
Statistics
Run started Mon May 09 15:27:09 1994
Statistics taken at Mon May 09 15:29:27 1994
Length of Run so far 0:02:18 (hh:mm:ss)
Hardware
IBM PS/2 Model 80
Engine Rated Bus types
speed
(Mhz)
386 20 PS/2 32-bit
Operating System Software
OS/2 Version 2.0 Revision 0
Operating System parameters
Maxwait MinSlice MaxSlice
(secs) (msecs) (msecs)
3 32 32
System File Manager
Version 6.15
CICS Run-time Environment variables
BMSMAP=D:\CICS200\BIN
BTRINTF=/H:D:\CICS200\BIN
CICSRD=D:\CICS200\BIN\DATA\FAACTFTB.BTR
CICSRGRP=FAASYS,PA2GROUP,PA2EXMPL
CICSTEXT=D:\CICS200\BIN\DATA
CICSTRACE=D:\CICS200\UTIL\FAATAFEN.TRC
CICSWRK=D:\CICS200\BIN;
Reason for monitoring and statistics
SAMPLE OUTPUT
CICS values
APPLID Local Default File
SYSID SYSID Manager
ANDYKOS2 ANDY
Max Min System Process
Task Free Priority Priority
6 2 0 86
Task Class Limits
Class Class Class Class Class Class Class Class Class Class
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
1 1 1 1 1 1 1 1 1 1
Transactions run
Transaction Times Percent Average Shortest Longest Standard
name Run total (secs) (secs) (secs) Deviation
CECI 1 14.29 11.59 11.59 11.59 0.00
CLOG 3 42.86 4.10 2.34 6.66 1.07
CRSR 1 14.29 2.28 2.28 2.28 0.00
PA21 1 14.29 36.03 36.03 36.03 0.00
PA2M 1 14.29 0.00 0.00 0.00 0.00
Totals 7
Transaction Times Times Syncpoint Syncpoint Syncpoint
name Run abended (secs) File Mngr
operations
CECI 1 2 1 0.00 0
CLOG 3 0 3 0.34 0
CRSR 1 0 1 0.50 0
PA21 1 0 1 0.03 0
PA2M 1 0 0 0.00 0
Totals 7 2 6 0
Transaction attributes
Transaction Priority Program Task Group Sysid
name Class
CECI 0 FAAATPCI 0 FAASYS
CLOG 0 FAALSPDL 0 FAASYS
CRSR 0 FAAOIPTD 0 FAASYS
PA21 0 PA2PLTPI 3 PA2GROUP
PA2M 0 PA2MCDSP 0 PA2GROUP
Communications
Xactn Times Times Send Times Receive ..
name Run Send (secs) Receive (secs) ..
CECI 1 7 3.91 7 2.59 ..
CLOG 3 3 3.91 2 0.03 ..
PA2M 1 0 0.00 1 0.00 ..
.. Times Converse Times Issue
.. Converse (secs) Issue (secs)
.. 0 0.00 0 0.00
.. 0 0.00 0 0.00
.. 0 0.00 0 0.00
User Buckets
Bucket Xactn Times Times Total Average
number name started stopped (secs) (secs)
Clock(1) CECI 2 0 8.31 4.157
Clock(2) CECI 2 2 0.47 0.235
Clock(3) CECI 4 0 8.34 2.086
File Control
File Xactn Read Write Rewrite Delete Unlock
name name
FAACTFTB CRSR 0 0 0 0 0
FAACTFTB INIT 1 0 0 0 0
FAACTFTB PA21 0 0 0 0 0
FAAMGFMG CLOG 1 0 0 0 0
FAAMGFMG INIT 1 0 0 0 0
Totals 3 0 0 0 0
Equivalent File Manager operations
File Xactn Read Write Rewrite Delete Unlock
name name
FAACTFTB CRSR 0 0 0 0 0
FAACTFTB INIT 1 0 0 0 0
FAACTFTB PA21 0 0 0 0 0
FAAMGFMG CLOG 1 0 0 0 0
FAAMGFMG INIT 1 0 0 0 0
Totals 3 0 0 0 0
File Xactn Start Read Read Reset End
name name Browse Next Previous Browse Browse
FAACTFTB CRSR 1 0 0 0 1
FAACTFTB INIT 0 0 0 0 0
FAACTFTB PA21 1 73 0 3 1
FAAMGFMG CLOG 0 0 0 0 0
FAAMGFMG INIT 0 0 0 0 0
Totals 2 73 0 3 2
Equivalent File Manager operations
File Xactn Start Read Read Reset End
name name Browse Next Previous Browse Browse
FAACTFTB CRSR 2 0 0 0 0
FAACTFTB INIT 0 0 0 0 0
FAACTFTB PA21 2 73 0 6 0
FAAMGFMG CLOG 0 0 0 0 0
FAAMGFMG INIT 0 0 0 0 0
Totals 4 73 0 6 0
Transient data
Queue Xactn Readq Writeq Deleteq
name name
CSCS CLOG 0 1 0
Totals 0 1 0
Equivalent File Manager operations
Queue Xactn Readq Writeq Deleteq
name name
CSCS CLOG 0 2 0
Totals 0 2 0
Interval control
Started Xactn Start Retrieve Cancel
Xactn name
name
CLOG INIT 1 0 0
PA21 INIT 1 0 0
Totals 2 0 0
Program control
Program Xactn Times Load Link Load Xctl
name name loaded time
FAAATPCI CECI 1 0.3 2 0 0
FAALSPDL CLOG 3 0.4 0 0 2
FAALSPSN CLOG 2 0.0 1 0 0
FAAMGSON CLOG 1 0.9 0 0 0
FAAMGSON INIT 1 0.5 0 0 0
FAAOIPTD CRSR 1 0.4 0 0 0
FAAOIS04 INIT 3 0.2 0 0 0
FAAOISII INIT 3 1.7 1 0 0
FAAPLTPI INIT 1 0.3 0 0 1
PA2ABEND CECI 2 0.7 0 0 0
PA2MCDSP PA2M 1 0.3 0 0 0
PA2PLTPI PA21 1 1.2 0 0 0
PA2PLTSD PA2M 1 0.3 0 0 0
Totals 21 4 0 3
Abend control
Program Xactn Abend Number
name name code
PA2ABEND CECI PA2X 2
Totals 2
Process control
Process number Trans Priority Priority Percent Percent Type
Run Class Level busy split
62 0 3 1 0.00 26.71 Global
65 5 2 0 17.32 41.77
66 1 2 0 1.65 2.45
67 1 4 31 26.11 29.71
Totals 7
Global Process statistics
Process number File Mngr Extra TD ETI Terminal TerminalNetBiosPNA
requests requests requests attaches detaches requests
62 16 0 0 0 0 3
System File Manager
File name File Pagesize Start Start End End
flags Number Unused Number Unused
Records Pre-Alloc Records Pre-Alloc
Pages Pages
FAAAEFBU 1....... 512 88 0 88 0
FAAAEFIE 1....... 512 20 0 20 0
FAACTFTB 1....... 512 84 0 84 0
FAAHLFT1 1....... 512 88 0 88 0
FAAHLFT2 1....... 512 1481 0 1481 0
FAAHLFT3 1....... 512 105 0 105 0
FAAMGFMG 11...... 512 1415 0 1415 0
FAAMSFSC 1....... 512 5 0 5 0
FAAMSFSY 1....... 512 76 0 76 0
FAATSFP1 1....... 512 0 0 0 0
FAATSFU1 1....... 512 4 0 6 0
File name Location
FAAAEFBU .\DATA\FAAAEFBU.BTR
FAAAEFIE .\DATA\FAAAEFIE.BTR
FAACTFTB .\DATA\FAACTFTB.BTR
FAAHLFT1 .\DATA\FAAHLFT1.BTR
FAAHLFT2 .\DATA\FAAHLFT2.BTR
FAAHLFT3 .\DATA\FAAHLFT3.BTR
FAAMGFMG .\DATA\FAAMGFMG.BTR
FAAMSFSC .\DATA\FAAMSFSC.BTR
FAAMSFSY .\DATA\FAAMSFSY.BTR
FAATSFP1 .\DATA\FAATSFP1.BTR
FAATSFU1 F:\FAATSFU1.BTR
Performance control
Bucket size Bucket Percent
used used
65535 13876 21.17
Bucket error messages
PA2CLOCK Clock number 4 not started before a stop, ignored, in transaction CECI
PA2CLOCK Non valid action X passed to clock number 2, ignored, in transaction CECI
PA2CLOCK Clock number 7 out of range 1-4 in transaction CECI
PA2CLOCK Clock number 3 not stopped before a start, not reset, in transaction CECI
PA2CLOCK Clock number 1 not stopped before a start, not reset, in transaction CECI
PA2CLOCK Clock number 3 not stopped before a start, not reset, in transaction CECI
PA2CLOCK Clock number 4 not started before a stop, ignored, in transaction CECI
PA2CLOCK Non valid action X passed to clock number 2, ignored, in transaction CECI
PA2CLOCK Clock number 7 out of range 1-4 in transaction CECI
PA2CLOCK Clock number 3 not stopped before a start, not reset, in transaction CECI
FAADKSIN Clock number 1 not stopped before end of transaction CECI, added
FAADKSIN Clock number 3 not stopped before end of transaction CECI, added
(C) Copyright IBM Corp. 1994. All rights reserved.
ΓòÉΓòÉΓòÉ 16.2. Explanation of PA2STATS.DAT file entries ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 16.2.1. Times ΓòÉΓòÉΓòÉ
Run started Date and time when this CICS for OS/2 run started
Statistics taken at Date and time when requested
Length of Run so far Difference of the above
ΓòÉΓòÉΓòÉ 16.2.2. Hardware ΓòÉΓòÉΓòÉ
Type Description (eg IBM PS/2 Model 80)
Engine INTEL or equivalent (eg 386)
Rated speed (Mhz) Processor speed (eg 20Mhz)
Bus types Processor bus type (eg PS/2 32-bit)
ΓòÉΓòÉΓòÉ 16.2.3. Operating System Software Level ΓòÉΓòÉΓòÉ
Operating System Software Level Description (eg OS/2 Version 2.0 Revision 0)
ΓòÉΓòÉΓòÉ 16.2.4. Operating System parameters ΓòÉΓòÉΓòÉ
Maxwait(secs) CONFIG.SYS value which sets the amount of time a
process waits before the system assigns it a
higher priority. When a regular class thread is
denied the processor for this number of seconds
it receives a temporary increase in priority for
a minimum time slice. (Default is 3 seconds)
MinSlice(msecs) First parameter of the TIMESLICE CONFIG.SYS value
and is the minimum amount of time a thread can be
processed before yielding the processor to a
thread of the same priority level. (Default is 32
milliseconds)
MaxSlice(msecs) Second parameter of the TIMESLICE CONFIG.SYS
value and is the maximum amount of time a thread
can be processed before yielding the processor to
a thread of the same priority level. (Default is
32 milliseconds)
ΓòÉΓòÉΓòÉ 16.2.5. System File Manager Level ΓòÉΓòÉΓòÉ
System File Manager Level Description (eg Version 6.15)
ΓòÉΓòÉΓòÉ 16.2.6. CICS Run-time Environment variables ΓòÉΓòÉΓòÉ
Performance Analyser reports on the seven CICS for OS/2 specific environment
variables BMSMAP, BTRINTF, CICSRD, CICSRGRP, CICSTEXT, CICSTRACE and CICSWRK.
If they are not specified, (null) will be output to be compatible with OS/2.
BMSMAP= Points to the directory where user generated BMS maps are
held in in the file FAAMSFSC.BTR. The default value built
in by CICSENV is cicsdrv:\CICS200\BIN\DATA.
BTRINTF= Points to System File Manager home directory
CICSRD= Points to a specific CICS resource definition file, the
default value built by CICSENV is
cicsdrv:\CICS200\BIN\DATA\FAACTFTB.BTR.
CICSRGRP= Is the list of resource groups to be loaded for this run of
CICS for OS/2. The CICS for OS/2 system, as shipped, is
contained in the group FAASYS. For example, if
CICSRGRP=FAASYS,MYGROUPB,MYGROUPA all the resource entries
in group FAASYS will be loaded, then all the resources from
group MYGROUPA, and finally all the resources from
MYGROUPB. This means that if the same name appears for the
same resource type in multiple groups, the highest entry
found in the ASCII collating sequence will be used. If
CICSRGRP is not specified, all resources defined to the
system will be installed by group in ascending ASCII
collating sequence.
CICSTEXT= Names the directory that CICS for OS/2 will search for help
text. The default value built by CICSENV is
cicsdrv:\CICS200\BIN\DATA.
CICSTRACE= Names a specific file for the binary trace output when it
is invoked either via the CETR transaction or the /t
start-up option. The default value built by CICSENV is
cicsdrv:\CICS200\UTIL\FAATAFEN.TRC.
CICSWRK= Names a set of directories where CICS for OS/2 will search
for .DLLs and .EXEs before trying the CONFIG.SYS values for
LIBPATH and PATH respectively. The default value built by
CICSENV is cicsdrv:\CICS200\BIN.
ΓòÉΓòÉΓòÉ 16.2.7. Reason for monitoring and statistics ΓòÉΓòÉΓòÉ
Reason for monitoring A string used as a means of labelling output for
future reference. The value may be set either by
the PA2M invocation or passed in a COMMAREA of a
LINK statement to PA2PLTSD (for example, "See if
System File Manager values have changed").
ΓòÉΓòÉΓòÉ 16.2.8. CICS values ΓòÉΓòÉΓòÉ
APPLID Eight character logical unit name, also used as
the server name for CICS for OS/2 clients to
connect to, where it is specified in FAARQ.SYS
Local SYSID Four character system identifier CICS uses to
distinguish remote resources from local ones
Default SYSID Four character system identifier used as the
remote target for unknown transaction identifiers
File Manager Eight character name of the .DLL to be used for
an alternative file manager instead of System
File Manager.
Max Task Maximum number of allowable tasks, see Major CICS
for OS/2 Version 2 Parameters.
Min Free Minimum number of free tasks, see Major CICS for
OS/2 Version 2 Parameters.
System Priority CICS base priority, see CICS for OS/2 and
Priority.
Process Priority CICS non-facility process priority, see CICS for
OS/2 and Priority.
Note. All of these values are set in the Systems Initialisation Table (SIT).
ΓòÉΓòÉΓòÉ 16.2.9. Task Class limits ΓòÉΓòÉΓòÉ
Class(1,2,3,...,10) Limit of the number of transactions defined in
that class that can run concurrently
Note. All of these values are set in the Systems Initialisation Table (SIT).
ΓòÉΓòÉΓòÉ 16.2.10. Transactions run ΓòÉΓòÉΓòÉ
First table
Transaction name Four character transaction name
Times Run Number of times the transaction was executed
Percent of total Number of times executed/Total number of
transactions run expressed as a percentage
Average(secs) Total time in system in seconds/Number of times
executed
Shortest(secs) Shortest time in system in seconds
Longest(secs) Longest time in system in seconds
Standard Deviation Standard deviation of the time in system
Note. Almost all of this information in this table is available via the on-line
transaction PA2K.
Second table
Transaction name Four character transaction name
Times Run Number of times executed
Times Abended Number of times transaction abended (see Abend
statistics below)
Syncpoint Number of times SYNCPOINT command executed either
explicitly or implicitly
Syncpoint(secs) Total time taken in SYNCPOINT for this
transaction
Syncpoint File Manager operations Number of calls to the File Manager within
SYNCPOINT
ΓòÉΓòÉΓòÉ 16.2.11. Transaction attributes ΓòÉΓòÉΓòÉ
First table
Transaction name Four character transaction name
Priority CICS transaction priority
Program Name of program that the PCT entry for this
transaction points to
Task Class Class defined for this transaction. 0 means none
defined
Group Groupname that was used to bring this transaction
resource into the system
Sysid System identifier if defined. If it is different
from that defined in the SYSID in the SIT the
transaction will be considered to be remote
Note. All of these values are set in the Program Control Table (PCT) for the
transaction.
ΓòÉΓòÉΓòÉ 16.2.12. User Buckets ΓòÉΓòÉΓòÉ
This table will only be output if data exists to be reported.
Transaction name Transaction name
Clock(number) Number of clock, ranges between 1 and 4
Times started Number of times user clock started within
transaction
Times stopped Number of times user clock stopped within
transaction
The analyser will do its best if you do not stop
a clock specifically. (See explanation of Bucket
error messages in User Clocks)
Total(secs) Total time in seconds attributed to clock
Average(secs) Total time in seconds attributed to clock divided
by the number of times the user clock was started
within the transaction
Note. The information in this table is available via the on-line transaction
PA2E
ΓòÉΓòÉΓòÉ 16.2.13. Communications ΓòÉΓòÉΓòÉ
First table
Transaction name Transaction name
Times Send Number of EXEC CICS SEND statements executed
Send(secs) Total time executing EXEC CICS SEND statements
Times Receive Number of EXEC CICS RECEIVE statements executed
Receive(secs) Total time executing EXEC CICS RECEIVE statements
Times Converse Number of EXEC CICS CONVERSE statements executed
Converse(secs) Total time executing EXEC CICS CONVERSE
statements
Times Issue Number of EXEC CICS ISSUE statements executed
Issue(secs) Total time executing EXEC CICS ISSUE statements
Second table. This table will only be printed if APPC has been used within the
transaction.
Xactn name Transaction name
Times Allocate Number of EXEC CICS ALLOCATE statements executed
Allocate(secs) Total time executing EXEC CICS ALLOCATE
statements
Times Extract Number of EXEC CICS EXTRACT statements executed
Extract(secs) Total time executing EXEC CICS EXTRACT statements
Times Connect Number of EXEC CICS CONNECT statements executed
Connect(secs) Total time executing EXEC CICS CONNECT statements
Times Free Number of EXEC CICS FREE statements executed
Free(secs) Total time executing EXEC CICS FREE statements
ΓòÉΓòÉΓòÉ 16.2.14. File control ΓòÉΓòÉΓòÉ
File name File name used for operation
Xactn name Transaction name that uses the file
Read Number of EXEC CICS READ statements executed, by
transaction
Write Number of EXEC CICS WRITE statements executed, by
transaction
Rewrite Number of EXEC CICS REWRITE statements executed,
by transaction
Delete Number of EXEC CICS DELETE statements executed,
by transaction
Unlock Number of EXEC CICS UNLOCK statements executed,
by transaction
Note. The information in this table is available via the on-line transaction
PA2F.
ΓòÉΓòÉΓòÉ 16.2.15. Equivalent File Manager Operations ΓòÉΓòÉΓòÉ
Each operation from the table above normally results in one or more calls to
the File Manager. By dividing the equivalent operations from this table by the
number of operations from the corresponding table above, a view can be taken
how much work is being generated to the file manager by each of the EXEC CICS
calls.
ΓòÉΓòÉΓòÉ 16.2.16. File control ΓòÉΓòÉΓòÉ
This table will only be printed if the browse API has been used within the
transaction.
Start Browse Number of EXEC CICS STARTBR statements executed,
by transaction
Read Next Number of EXEC CICS READNEXT statements executed,
by transaction
Read Previous Number of EXEC CICS READPREV statements executed,
by transaction
Reset Browse Number of EXEC CICS RESETBR statements executed,
by transaction
End Browse Number of EXEC CICS ENDBR statements executed, by
transaction
The information in this table is available via the on-line transaction PA2G
ΓòÉΓòÉΓòÉ 16.2.17. Equivalent File Manager Operations ΓòÉΓòÉΓòÉ
Each operation from the table above normally results in one or more calls to
the File Manager. By dividing the equivalent operations from this table by the
number of operations from the corresponding table above, a view can be taken
how much work is being generated to the file manager by each of the EXEC CICS
calls.
ΓòÉΓòÉΓòÉ 16.2.18. Temporary storage ΓòÉΓòÉΓòÉ
Queue name Eight character queue name
Xactn name Transaction name that used the queue
Readq Number of EXEC CICS READQ TS statements executed,
by transaction
Writeq Number of EXEC CICS WRITEQ TS statements
executed, by transaction
Deleteq Number of EXEC CICS DELETEQ TS statements
executed, by transaction
Note. The information in this table is available via the on-line transaction
PA2Q (Q for queue).
ΓòÉΓòÉΓòÉ 16.2.19. Equivalent File Manager Operations ΓòÉΓòÉΓòÉ
Each operation from the table above normally results in one or more calls to
the File Manager. By dividing the equivalent operations from this table by the
number of operations from the corresponding table above, a view can be taken
how much work is being generated to the file manager by each of the EXEC CICS
calls.
ΓòÉΓòÉΓòÉ 16.2.20. Transient data ΓòÉΓòÉΓòÉ
Queue name Four character queue name
Xactn name Transaction name that uses the queue
Readq Number of EXEC CICS READQ TD statements executed,
by transaction
Writeq Number of EXEC CICS WRITEQ TD statements
executed, by transaction
Deleteq Number of EXEC CICS DELETEQ TD statements
executed, by transaction
Note.The information in this table is available via the on-line transaction
PA2D (D for Destination Control Table (DCT)).
ΓòÉΓòÉΓòÉ 16.2.21. Equivalent File Manager Operations ΓòÉΓòÉΓòÉ
Each operation from the table above normally results in one or more calls to
the File Manager. By dividing the equivalent operations from this table by the
number of operations from the corresponding table above, a view can be taken
how much work is being generated to the file manager by each of the EXEC CICS
calls.
ΓòÉΓòÉΓòÉ 16.2.22. Interval control ΓòÉΓòÉΓòÉ
Transaction Transaction name that gets started, followed by
transaction that started it
Start Number of EXEC CICS START statements executed, by
transaction
Retrieve Number of EXEC CICS RETRIEVE statements executed,
by transaction
Cancel Number of EXEC CICS CANCEL statements executed,
by transaction
Note. The information in this table is available via the on-line transaction
PA2I.
ΓòÉΓòÉΓòÉ 16.2.23. Program control ΓòÉΓòÉΓòÉ
Program name Name of program that is doing a LINK,LOAD or XCTL
Xactn name Transaction name that this program is running
under
Times loaded Number of times ProgramName.DLL was loaded
Load time Total time in seconds to load ProgramName.DLL
Link Number of EXEC CICS LINK statements executed by
this program in this transaction
Load Number of EXEC CICS LOAD statements executed, by
this program in this transaction
Xctl Number of EXEC CICS XCTL statements executed, by
this program in this transaction
Note. The information in this table is available via the on-line transaction
PA2P.
ΓòÉΓòÉΓòÉ 16.2.24. Abend control ΓòÉΓòÉΓòÉ
Program name Name of program that abended
Xactn name Transaction name that abended
Abend code ABEND code issued
Number Number of times that program abended with that
ABEND code
ΓòÉΓòÉΓòÉ 16.2.25. Process usage ΓòÉΓòÉΓòÉ
Process number OS/2 process number
Trans Run Number of transactions run on this process.
(Note that no transactions will be run on the
Global Process).
Priority class OS/2 priority, of the form c.l where c (in
ascending priority) is 1,2,4,3 which are the OS/2
performance classes (Idle-time, Regular,
Foreground Server and Time-critical) and l is the
level within that class (ascending from 0 to 31)
Priority level OS/2 priority level, see above
Percent busy Total time that transactions were active on this
process divided by total length of the run
Percent split Total time that this process was active divided
by the total length of the run
Type Differentiates the Global Process from other CICS
application processes
Note. The information in this table is available via the on-line transaction
PA2X. Extra information is also displayed by PA2X
Depth Depth of program level nesting
Active Xactn Active transaction name running on this process
Task number CICS task number
Active Program Active program of the transaction running on this
process
ΓòÉΓòÉΓòÉ 16.2.26. Global Process statistics ΓòÉΓòÉΓòÉ
Process number OS/2 process number
System File Manager requests Number of System File Manager requests processed
by the Global Task for an unrecoverable resource
Extra TD requests Number of Extra-Partition Transient Data requests
ETI requests Number of External Transaction Initiation
requests
Terminal attaches Number of terminal attaches
Terminal detaches Number of terminal detaches
NetBIOS PNA requests Number of requests to initiate a NetBIOS or PNA
request.
ΓòÉΓòÉΓòÉ 16.2.27. System File Manager ΓòÉΓòÉΓòÉ
First table.
File name CICS file name
File flags Flags as defined by the System File Manager
1....... The file allows variable length records
.1...... System File Manager truncates trailing blanks in variable
length records
..1..... System File Manager pre-allocated pages for the file
...1.... System File Manager compresses the data in the file
....1... System File Manager created the file as a key-only file
......1. System File Manager maintains a 10% free space threshold
.......1 System File Manager maintains a 20% free space threshold
......11 System File Manager maintains a 30% free space threshold
Pagesize Length of a page as defined in the File Control
Table (FCT)
Start Number Records Number of records in file at start of the CICS
run
Start Unused Pre-Alloc Pages Number of unused pages in a file which was
pre-allocated, by invoking the BTRIEVE CREATE
command, at start of the CICS run
End Number Records Number of records in file when the statistics
were gathered
End Unused Pre-Alloc Pages Number of unused pages in a pre-allocated file
when the statistics were gathered
The information in this table is available via the on-line transaction PA2B.
Second table
File name CICS file name
Location Path to data. Either a fully qualified path
name, for example, d:\mydata\persons.btr or an
addition to the current directory.
ΓòÉΓòÉΓòÉ 16.2.28. Performance control ΓòÉΓòÉΓòÉ
Bucket size Size of control block allocated for storing the
monitoring and statistics data
Bucket used Length of statistics and monitoring data acquired
so far
Percent used Length of statistics and monitoring data acquired
so far divided by the Size of control block for
storing the monitoring and statistics data
ΓòÉΓòÉΓòÉ 16.2.29. Bucket and other error messages ΓòÉΓòÉΓòÉ
Bucket and other error messages Relate to the use of user probes and other
error situations whilst running Performance
Analyser
ΓòÉΓòÉΓòÉ 17. Usage Examples ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 17.1. Example 1 ΓòÉΓòÉΓòÉ
This example is based on a real problem generated during the writing of
Performance Analyser.
ΓòÉΓòÉΓòÉ 17.1.1. Scenario ΓòÉΓòÉΓòÉ
Statistics file for Example 1 - prior to modification shows part of the
statistics generated when Performance Analyser was being tested. The
transaction codes starting with the letters PA2 all belong to Performance
Analyser and it can be seen that the length of the PA21 transaction (8.66
seconds) seems too long. A re-run gave a time of 8.38 seconds and some sort of
problem was suspected.
Look at the statistics and see if you can spot what was wrong with the way PA21
was first written.
ΓòÉΓòÉΓòÉ 17.1.2. Statistics ΓòÉΓòÉΓòÉ
(Note: the lines of dots signify deleted lines where the information is
irrelevant to the problem).
Statistics file for Example 1 - prior to modification
Transactions run
Transaction Times Percent Average Shortest Longest Standard
name Run total (secs) (secs) (secs) Deviation
CLOG 5 62.50 1.96 1.16 3.06 0.30
CRSR 1 12.50 1.50 1.50 1.50 0.00
PA21 1 12.50 8.66 8.66 8.66 0.00
PA2M 1 12.50 0.00 0.00 0.00 0.00
Totals 8
Transaction Times Times Syncpoint Syncpoint Syncpoint
name Run abended (secs) File Mngr
operations
CLOG 5 0 5 0.06 0
CRSR 1 0 1 0.00 0
PA21 1 0 1 0.03 0
PA2M 1 0 0 0.00 0
Totals 8 0 7 0
Communications
Xactn Times Times Send Times Receive....
name Run Send (secs) Receive (secs)....
....
CLOG 5 5 3.13 4 0.09....
PA2M 1 0 0.00 1 0.00....
.... Times Converse Times Issue
....Converse (secs) Issue (secs)
....
.... 0 0.00 0 0.00
.... 0 0.00 0 0.00
File Control
File Xactn Read Write Rewrite Delete Unlock
name name
FAACTFTB CRSR 0 0 0 0 0
FAACTFTB INIT 1 0 0 0 0
FAACTFTB PA21 0 0 0 0 0
FAAMGFMG CLOG 3 0 0 0 0
FAAMGFMG INIT 1 0 0 0 0
Totals 5 0 0 0 0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Xactn Start Read Read Reset End
name name Browse Next Previous Browse Browse
FAACTFTB CRSR 1 0 0 0 1
FAACTFTB INIT 0 0 0 0 0
FAACTFTB PA21 11 22 0 0 11
FAAMGFMG CLOG 0 0 0 0 0
FAAMGFMG INIT 0 0 0 0 0
Totals 12 22 0 0 12
Equivalent File Manager operations
File Xactn Start Read Read Reset End
name name Browse Next Previous Browse Browse
FAACTFTB CRSR 2 0 0 0 0
FAACTFTB INIT 0 0 0 0 0
FAACTFTB PA21 22 22 0 0 0
FAAMGFMG CLOG 0 0 0 0 0
FAAMGFMG INIT 0 0 0 0 0
Totals 24 22 0 0 0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interval control
Started Xactn Start Retrieve Cancel
Xactn name
name
CLOG INIT 1 0 0
PA21 INIT 1 0 0
Totals 2 0 0
Program control
Program Xactn Times Load Link Load Xctl
name name loaded time
FAALSPDL CLOG 5 0.81 0 0 4
FAALSPSN CLOG 4 0.03 3 0 0
FAAMGSON CLOG 3 0.50 0 0 0
FAAMGSON INIT 1 0.28 0 0 0
FAAOIPTD CRSR 1 0.25 0 0 0
FAAOIS04 INIT 3 0.22 0 0 0
FAAOISII INIT 3 1.34 1 0 0
FAAPLTPI INIT 1 0.19 0 0 1
PA2MCDSP PA2M 1 0.31 0 0 0
PA2PLTPI PA21 1 0.31 0 0 0
PA2PLTSD PA2M 1 0.44 0 0 0
Totals 24 4 0 5
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ΓòÉΓòÉΓòÉ 17.1.3. Deductions ΓòÉΓòÉΓòÉ
On scanning this data you should be able to see that:
1. From the Transaction Run section:
o PA21 ran once
o It did not abend, because there is no Abend data, so we did not spend time
taking a default dump.
o Syncpoint was one timer blip of 0.03 seconds so did not spend a large
amount of time committing large amounts of data to disk.
2. PA21 does not appear in the Communications section so PA21 it cannot be a
conversational transaction (even if it did, it still might not be).
3. From the Interval Control section:
o PA21 was STARTed once from INIT.
o There is no Temporary Storage (TS) activity (Retrieves = 0), so the START
did not have data and hence it is not a TS problem.
4. From the Program Control section, the load time was 0.31 seconds and this
is not dissimilar to most of the other programs listed.
5. The first File Control table shows no activity in PA21.
6. The second shows 11 Start Browse, 22 Read Next, and 11 End Browse!
This last observation seemed a bit odd and on examining the code it was found
that the browsing code was inside another loop! The code was slightly
restructured and the statistics shown in Statistics file for Example 1 after
modification to code were obtained from the same machine.
Transaction Times Percent Average Shortest Longest Standard
name Run total (secs) (secs) (secs) Deviation
PA21 1 14.29 4.03 4.03 4.03 0.00
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
File Xactn Start Read Read Reset End
name name Browse Next Previous Browse Browse
FAACTFTB PA21 1 12 0 0 1
Equivalent File Manager operations
File Xactn Start Read Read Reset End
name name Browse Next Previous Browse Browse
FAACTFTB PA21 2 12 0 0 0
Statistics file for Example 1 after modification to code
As can be seen, the number of calls to CICS was cut by two thirds with a
similar reduction in the number of calls to System File Manager and the
occupancy time was halved!
ΓòÉΓòÉΓòÉ 17.2. Example 2 ΓòÉΓòÉΓòÉ
This example came from running a test on Performance Analyser to check for
storage leakage when running ECI calls to a CICS for OS/2 Server.
ΓòÉΓòÉΓòÉ 17.2.1. Scenario ΓòÉΓòÉΓòÉ
A client machine was used to invoke a CICS for OS/2 server to execute a program
ECHO. When the request was received by CICS for OS/2 the CICS mirror (FAAMIR)
was invoked using transaction code CPMI. The LINK was executed and the program
ECHO was LOADED and run. Use of the supplied transaction PA2P provided the
screen shown in PA2P output for Example 2.
ΓòÉΓòÉΓòÉ 17.2.2. Statistics ΓòÉΓòÉΓòÉ
PA2P output for Example 2
ΓòÉΓòÉΓòÉ 17.2.3. Deductions ΓòÉΓòÉΓòÉ
The mirror was invoked 1,939 times during the run.
o ECHO was linked to 1,938 times (only 1,936 are shown since the application
was active and 2 invocations were in process at the time of the screen
capture)
o FAATCPIN was linked to 1 time
which adds up to 1,939.
ECHO took an average load time of 2.38 seconds.
ΓòÉΓòÉΓòÉ 17.3. Example 3 ΓòÉΓòÉΓòÉ
This example came from running an overnight test on Performance Analyser to
check performance when running Distributed Program Links to a mainframe.
ΓòÉΓòÉΓòÉ 17.3.1. Scenario ΓòÉΓòÉΓòÉ
A client machine was used to invoke a CICS for OS/2 server to execute a program
ECHOHOST. When the request was received by the CICS for OS/2 server, CICS
mirror (FAAMIR) was invoked using transaction code CPMI. The LINK was executed
but in this case ECHOHOST was marked remote, so the request was packaged up and
forwarded to the remote host where it was executed. Use of the supplied
transaction PA2K and PA2P provided the screens shown in PA2K output for Example
3 and PA2P output for Example 3.
ΓòÉΓòÉΓòÉ 17.3.2. Statistics ΓòÉΓòÉΓòÉ
PA2K output for Example 3
PA2P output for Example 3
ΓòÉΓòÉΓòÉ 17.3.3. Deductions ΓòÉΓòÉΓòÉ
The mirror was invoked 37,741 times during the run.
o ECHO was linked to 854 times
o ECHOHOST was linked to 36,885 times
ECHOHOST had an average response time of 1.64 seconds across the link. From
the Task Control (PA2K) output this was the majority of the total internal
transaction time of 1.98 seconds.
ΓòÉΓòÉΓòÉ 17.3.4. Trace output ΓòÉΓòÉΓòÉ
Example 3 Statistics file shows part of a trace taken on the CICS for OS/2
server machine using the PA2O transaction. It shows the sequence of events in
the execution of ECHOHOST along with timings (in milliseconds).
Example 3 Statistics file
08:34:49.57 86 Entry EXEC CICS ASKTIME
Exit EXEC CICS ASKTIME 0
08:34:49.60 Entry Task Initiation CPMI
Entry Load Program
FAAMIR CPMI
Exit Load Program 0
Entry Init prog COBOL call
Exit Init COBOL prog call 0
Entry EXEC CICS HANDLE
08:34:49.63 Exit EXEC CICS HANDLE 31
Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
Entry Load Program
ECHOHOST CPMI
08:34:49.94 Exit Load Program 313
Entry EXEC CICS LINK
Exit EXEC CICS LINK 0
Entry EXEC CICS SYNCPOINT
Exit EXEC CICS SYNCPOINT 0
08:34:49.97 Entry EXEC CICS HANDLE
Exit EXEC CICS HANDLE 0
Entry EXEC CICS FREEMAIN
Exit EXEC CICS FREEMAIN 0
08:34:50.00 Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
Entry POP ALL
Exit POP ALL 0
Entry clear POST
08:34:50.04 Exit Internal clear POST 32
Entry EXEC CICS SYNCPOINT
Exit EXEC CICS SYNCPOINT 0
Exit Task Termination 438
08:34:50.35 Entry EXEC CICS ASKTIME
Exit EXEC CICS ASKTIME 0
Entry Task Initiation CPMI
Entry Load Program
FAAMIR CPMI
Exit Load Program 0
Entry Init prog COBOL call
08:34:50.38 Exit Init COBOL prog call 31
Entry EXEC CICS HANDLE
Exit EXEC CICS HANDLE 0
Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
Entry Load Program
ECHOHOST CPMI
08:34:50.50 88 Entry EXEC CICS ASKTIME
Exit EXEC CICS ASKTIME 0
Entry Task Initiation CPMI
Entry Load Program
FAAMIR CPMI
Exit Load Program 0
Entry Init prog COBOL call
08:34:50.54 Exit Init COBOL prog call 32
08:34:50.57 Entry EXEC CICS HANDLE
Exit EXEC CICS HANDLE 0
Entry EXEC CICS GETMAIN
Exit EXEC CICS GETMAIN 0
Entry Load Program
ECHOHOST CPMI
08:34:50.72 86 Exit Load Program 313
Entry EXEC CICS LINK
Exit EXEC CICS LINK 0
Entry EXEC CICS SYNCPOINT
Exit EXEC CICS SYNCPOINT 0
Entry EXEC CICS HANDLE
08:34:50.75 Exit EXEC CICS HANDLE 31
Entry EXEC CICS FREEMAIN
Exit EXEC CICS FREEMAIN 0
08:34:50.79 Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
Entry POP ALL
Exit POP ALL 0
08:34:50.82 Entry clear POST
Exit Internal clear POST 0
Entry EXEC CICS SYNCPOINT
Exit EXEC CICS SYNCPOINT 0
Exit Task Termination 438
08:34:51.44 88 Exit Load Program 844
Entry EXEC CICS LINK
08:34:51.47 Exit EXEC CICS LINK 31
Entry EXEC CICS SYNCPOINT
Exit EXEC CICS SYNCPOINT 0
Entry EXEC CICS HANDLE
Exit EXEC CICS HANDLE 0
Entry EXEC CICS FREEMAIN
08:34:51.50 Exit EXEC CICS FREEMAIN 31
08:34:51.54 Entry EXEC CICS RETURN
Exit EXEC CICS RETURN 0
Entry POP ALL
08:34:51.57 Exit POP ALL 31
Entry clear POST
Exit Internal clear POST 0
Entry EXEC CICS SYNCPOINT
Exit EXEC CICS SYNCPOINT 0
Exit Task Termination 1032
08:34:53.00 86 Entry EXEC CICS ASKTIME
ΓòÉΓòÉΓòÉ 18. Known Errors ΓòÉΓòÉΓòÉ
The following are known errors in Version 1.0.1 of Performance Analyser.
1. PA2L transaction added to view CICSMSG.LOG from a CICS 3270 display
Note. Left and right scrolling may lose itself due to an error in the OS/2
toolkit being used. This will be fixed in a later release. Viewing from top
or bottom will reset the viewing display.
ΓòÉΓòÉΓòÉ 19. Additions since original shipment ΓòÉΓòÉΓòÉ
The following additions to Performance Analyser have been made since its first
Shipment in September 1994.
1. Maximum con-current tasks is displayed on all the Performance Analyser
screens.
2. ServerId available on transaction routed CICS 3270 displays as well as
local CICS 3270 displays.
3. Transaction level trace added.
4. PA2L transaction added to view CICSMSG.LOG from a CICS 3270 display.
5. Elapsed times in the application trace are printed in seconds.hundredths
rather than milliseconds to improve readability.
6. Highlighted start and end transaction events in the application trace.
7. Transaction name added to end transaction events in the application trace.
8. EXEC CICS RESP values added to Exit EXEC CICS events in the application
trace.
9. Eyecatchers added to end of line proportional to the elapsed time between
this CICS for OS/2 event and the next. Each '*' represents 5 timer units
(.15 seconds) up to a maximum of 1.5 seconds, in the application trace.