Download Suite - TPF Software Featuring zTPFGI for z/TPF

zTPFGI Facilities
Suite
www.tpfsoftware.com
Focus
Three of zTPFGI’s facilities:
 zAutomation
 zTREX
 Logger
Suite
www.tpfsoftware.com
zAutomation
Facility to Bring Up VPARS Remotely
Suite
www.tpfsoftware.com
Introduction
• Part of zTPFGI suite of
products and it is VM
based.
• Efficient and Effective
management of the
process of bringing up
the VPARS.
Resource
User
• VPARS classification
 On Demand
 Shared
System
Automation
Suite
www.tpfsoftware.com
Overview
Client A
Client B
Client A requests VPARS from pool
Worker A starts another worker
A
 which brings VPARS to norm
state, then disconnects
B
V2
VPARS Pool
V1 V2 V3
V4
V5 V6
Worker A starts another worker
V3
V3
V4
Legend
Private
Worker
Not Logged
on
NORM State
(product is not activated)
 which gets another VPARS
ready for dispatch, then
disconnects
Client B requests VPARS from pool
Worker B starts another worker
 which finds a VPARS that is
ready for dispatch in the pool,
so uses it
Worker B starts another worker
 which gets another VPARS
ready for dispatch, then
disconnects
Ready for dispatch
Suite
www.tpfsoftware.com
Role of zAutomation
• Assigns worker machines to bring up VPARS,
 Based on the configured status chosen by the user.
• Constantly checks VPARS status in the POOL file and takes relevant
actions
 Bringing up stand by VPARS or ERROR handling.
• If the user chooses a Shared VPARS which is not available

zAuto will bring up the Shared VPARS – for all users to sign-on.
• Based on the configuration option
 always brings up more stand-by VPARS.
 When the new USER signs-on, the stand-by VPARS is immediately allocated
(thus reducing wait time for the end user – in starting a VPARS)
• Puts all the stand by VPARS in “CP TR EXT” mode
 so that VPARS are not using CPU cycles.
Suite
www.tpfsoftware.com
Role of zAutomation
• zTPFGI with zAutomation
 Multiple VPARS can be grouped as POOL
–
–
With a logical name for the POOL
and can be shared by a group of users.
 When user signs-on using zTPFGI
–
An available VPARS from the pool is allocated with the clean database.
 For On Demand
–
–
User is guaranteed a VPARS with clean database all the time,
but can be different VPARS, every time he signs-on.
• zRTF with zAutomation
 Two VPARS available from the pool is fetched and allocated for zRTF RUN.
–
Phase 1 and Phase 2
 During zRTF process termination, VPARS are returned to the POOL.
 With zAutomation and pool VPARS
–
Suite
no need of reserving TWO VPARS for zRTF run all the time.
www.tpfsoftware.com
On Demand VPARS
• One or more VPARS are grouped together as pool

a logical resource pool name is assigned.
• When user action requires a VPARS, zAuto
Client A
Client B
V1
V2
VPARS Pool
V1
V2
V3
V4
Not Logged on
In Use
Suite
Stand By


fetches an available VPARS from the pool and
assigns it to the user.
• The pool VPARS is allocated to the user only when
user action demands the VPARS,

hence referred as “On Demand” VPARS.
• During the termination of the user action

VPARS is returned to the pool
• Configuration files are used to define the POOL of
VPARS.
• Using the configuration file, VPARS can be added or
deleted.
• In case of pool VPARS, only one user can use the
VPARS.
• Every time a pool VPARS is allocated to a specific user

VPARS with a clean database is allocated.
www.tpfsoftware.com
Shared VPARS
Client A
Client B
• Some VPARS can be configured as
Shared VPAR
Client C

Implying the VPARS is shared by
multiple users.
• Shared VPARS can also be
configured

Client D
• Resource Manager brings up the
shared VPARS

V1
Not Logged on /
Disconnected
In Use
Suite
to be monitored by Resource
Manager
to the usable status only if the
VPARS are down.
• In case of shared VPARS

multiple users can log on to the
same VPARS at the same time and
can use TPF Software products
(zTPFGI, zDFX, zRTF).
www.tpfsoftware.com
Server / User Configuration
• Server Information
• Pool or On-Demand
• VPARS name
• Names of other VPARS
• If type is POOL
Server
• User Information
• Display summary
messages to Console
• Display detail messages to
Console
• Used by Administrator
• For Debugging
Suite
www.tpfsoftware.com
Automation Configuration
• Resource Configuration




OSA information
PMR information
Tape information
Etc.
• Command Section
Automation
Suite
 Command to execute
 Action to take – for good rc
 Action to take – for bad rc
www.tpfsoftware.com
User Exits
• Send error message to
Administrator team for the
following cases
 Problem in updating the VPARS
POOL file
 Problem in bringing up the system
User Exits
• Get the password for the
VPARS
• Extract the value from the
previous command and set it in
the next coming commands
Suite
www.tpfsoftware.com
zTREX
Transaction Recording and Examination
Facility
Suite
www.tpfsoftware.com
Overview
• Reasons for zTREX
• Capabilities of zTREX
• Types of collection in zTREX
• zTREX Viewer Details
Suite
www.tpfsoftware.com
Why zTREX?
Problem:
 zTPF Applications that use
too many resources
degrade system
performance
 But it’s difficult to see the
problem
Solution:
 zTREX – Allows
programmers to identify
which App is using what
resources
 You can see just how big a
problem you have!
Suite
How much resource usage
lies below the surface of
this zTPF application?
•
•
•
•
•
CPU cycles
Pool gets and releases
Files and Finds
Tape resources
Etc?
www.tpfsoftware.com
Capabilities
zTREX Analyzes Performance at Several Levels
• Transaction level


All the resources used by the transaction
Identifies all the ECBs
• ECB level


All resources used at ECB level
Identify programs and functions
• Individual program/function level

All resources used at the program/function level
– Counts of MACRO/SVC used
Suite
www.tpfsoftware.com
Types of Data Collected
• Summary of data collection
 Resource usage is collected by each ECB
 Data is collated on the transaction level for presentation
• Program level data collection
 This is the detail level of data collection for each program
called by ECB
 The data is collated at the ECB level for presentation
• File usage data collection
 This records information on every file used by an ECB
Suite
www.tpfsoftware.com
Viewer Details
1. CPU Usage
 zTREX collects CPU usage at ECB level
2. Memory Usage
 Application-level memory
 Core blocks, heap space, system work blocks
3. I/O Usage, Pool Records
 Find and Files
 GETFC/ RELFC
4. Program Usage
 What programs/ functions the application calls
5. Macro Counts
 Overall count as well as individual count for each macro
 TPFDF macro count
Suite
www.tpfsoftware.com
Logger
Logging Facility
Suite
www.tpfsoftware.com
Logger
• Test System Management
 Helps operators to analyze the events happened in a test system
 Gives information on the changes to the VPARS
–
–
–
–
–
System commands executed
System wide program load
Private program load
Core altered
File altered
• Tool Management
 Helps Tools Administrator to analyze the usage of the products
• Debug problems in Products
 Collect debugging information on Global Level
 Helps us to narrow down to the problem
Suite
www.tpfsoftware.com
Components of Logger
Data
Worker
Log Server
• Save Log
Data to Log
Server
Worker
Admin
VPARS
Suite
• Collect Log
Data from:
• VPARS
• Worker
VPARS
• View Log
Data in zTPFGI
www.tpfsoftware.com
Components of Logger
• Data Collection



Software component is responsible for
data collection and sending it to the server
to save the data in a common place in VM.
• Log Server / Data Repository




The collected data are stored in the common Data repository.
Log Server is a VM machine always listening for Log data from either the VPARS or the
Worker Machine for the log data.
The server refers to configuration files to determine the location of each type of log data and
The Server also does the house keeping activities for each log type.
• Report Generation





Utility provided in zTPFGI
To generate report on the log data
Based on the filters provided by the administrator
There are no separate steps to install this component.
The utility comes as a part of zTPFGI.
Suite
www.tpfsoftware.com
Demo
Suite
www.tpfsoftware.com