Www.tpfsoftware.com Suite zTPFGI Facilities. Suite Focus Three of zTPFGI’s facilities: zAutomation zTREX Logger

www.tpfsoftware.comSuite

zTPFGI FacilitieszTPFGI Facilities


FocusFocus

Three of zTPFGI’s facilities: zAutomation zTREX Logger


zAutomationzAutomation

Facility to Bring Up VPARS Remotely


IntroductionIntroduction

•Part of zTPFGI suite of products and it is VM based.

•Efficient and Effective management of the process of bringing up the VPARS.

•VPARS classification On Demand SharedSystem

UserResource

Automation


On Demand VPARSOn Demand VPARS

VPARS Pool

V1 V2

V3 V4

Client A Client B

Not Logged on

In Use Stand By

V1 V2

V2

V3

• One or more VPARS are grouped together as pool a logical resource pool name is assigned.

• When user action requires a VPARS, zAuto 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.


Shared VPARSShared VPARS

• Some VPARS can be configured as Shared VPARS

Implying the VPARS is shared by multiple users.

• Shared VPARS can also be configured

To be monitored and Actioned by zAutomation

• zAutomation brings up the Shared VPARS

to the usable status only if the VPARS is 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).

Client A

Client BClient C

Client D

Not Logged on / Disconnected

In Use

V1 V1


Role of zAutomationRole 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” (SLEEP) mode so that VPARS are not using CPU cycles.


Role of zAutomationRole 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

– no need of reserving TWO VPARS for zRTF run all the time.


Server / User ConfigurationServer / User Configuration

• Server Information• Shared or On-Demand• VPARS name• Names of other VPARS

• If type is POOL

• User Information• Display summary

messages to Console• Display detail

messages to Console• Used by Administrator

• For Debugging

Server


Automation ConfigurationAutomation Configuration

• Resource Configuration OSA information PMR information Tape information Etc.

• Command Section Command to execute Action to take – for good

rc Action to take – for bad rc

Automation


User ExitsUser Exits

• Send error message to Administrator team for the following cases

Problem in updating the VPARS POOL file

Problem in bringing up the system

• Get the password for the VPARS

• Extract the value from the previous command and set it in the next coming commands

User Exits


zTREXzTREX

Transaction Recording and ExaminationFacility


OverviewOverview

•Reasons for zTREX

•Capabilities of zTREX

•Types of collection in zTREX

•zTREX Viewer Details


Why zTREX?

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!

How much resource usage lies below the surface of this zTPF application?

•CPU cycles•Pool gets and releases•Files and Finds•Tape resources•Etc?


CapabilitiesCapabilities

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


Types of Data CollectedTypes 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


Viewer DetailsViewer 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


LoggerLogger

Logging Facility


LoggerLogger

•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


Components of LoggerComponents of Logger

• Collect Log Data from:

• VPARS• Worker

• Save Log Data to Log Server

• View Log Data in zTPFGI

Admin

Worker

Worker

VPARS VPARS

Log Server

Data


Components of LoggerComponents 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.


DemoDemo

Documents

Www.tpfsoftware.com Suite zTPFGI Facilities. Suite Focus Three of zTPFGI’s facilities: zAutomation zTREX Logger