Presentation is loading. Please wait.

Presentation is loading. Please wait.

Suite www.tpfsoftware.com. Suite Part of zTPFGI suite of products and it is VM based. Efficient and Effective management of the process of bringing up.

Similar presentations


Presentation on theme: "Suite www.tpfsoftware.com. Suite Part of zTPFGI suite of products and it is VM based. Efficient and Effective management of the process of bringing up."— Presentation transcript:

1 Suite

2 Suite Part of zTPFGI suite of products and it is VM based. Efficient and Effective management of the process of bringing up the VPARS. Uses configuration files, which can be configured by the customer to suit their requirements. 2 System User Resource Automation

3 Suite SHARED VPARS – VPARS shared by multiple users  If the VPARS is not ACTIVE, zAutomation can bring up the VPARS. ON-DEMAND VPARS – Pool of VPARS from which a VPARS is brought up for individual usage.  The VPARS is CLEARED, Resource attached, IPL’d and brought up for usage by a developer PRIVATE VPARS – VPARS specifically defined for a user  If not active, zAutomation can bring up the VPARS  If active – will be restarted (woken up from sleep) for user 3

4 Suite Multiple VPARS can be grouped as POOL VPARS, and can be shared by a group of users. When user signs-on using zTPFGI, available VPARS from the pool is allocated with the clean database. User is guaranteed a VPARS with clean database all the time, but can be different VPARS, every time he signs-on. 4

5 Suite Client A requests VPARs from pool Worker A starts another worker  which brings VPARs to norm state, then disconnects Worker A starts another worker  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 5 VPARs Pool V2 V4 V2 V5 V6 V3 V1 V2 V3 V4 Private Not Logged on NORM State (product is not activated) Ready for dispatch V2 Legend Client A Worker V3V4 V3 Client B A B

6 Suite zAutomation can be configured to Monitor both SHARED and POOL VPARS. zAutomation assigns worker machines to bring up VPARS, up to the configured status chosen by the user. zAutomation updates and controls POOL status file zAutomation constantly checks VPARS status in the POOL file and takes relevant action like, Bringing up stand by VPARS or ERROR handling. In case of SHARED VPARS, If the user chooses to sign-on to the VPARS using zTPFGI debugger, and if VPARS is down or not available, zAutomation will assign worker machine to bring up the VPAR and indicates debugger to continue the SIGN-ON. 6

7 Suite zAutomation, based on the user chosen configuration option, always brings up more stand by VPARS. When the new USER signs-on using zTPFGI debugger, the stand by VPAR is immediately allocated so that the user does not have to wait for VPARS to come up all the time. In other terms, zAutomation takes care of time management of resources. zAutomation puts all the stand by VPARS in “CP TR EXT” mode, so that VPARS are not using CPU cycles.  Thus saving VM CPU cycles 7

8 Suite zTPFGI with zAutomation  Multiple VPARS can be grouped as POOL VPARS, and can be shared by a group of users.  When user signs-on using zTPFGI, available VPARS from the pool is allocated with the clean database.  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.  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. 8

9 Suite One or more VPARS are grouped together as pool and a logical resource pool name is assigned. When user action requires a VPAR, zAutomation fetches the available VPAR from the pool and assigns it to the user. The pool VPAR is allocated to the user only when user action demands the VPAR, 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 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 the user, VPARs with a clean database is allocated. 9

10 Suite Some VPARS can be configured as shared VPARS and can be shared by multiple users. Shared VPARS can also be configured to be monitored by zAutomation zAutomation brings up the shared VPARS to the usable status only if the VPARS are down. In case of shared VPARS, multiple users can log on to the same VPAR at the same time and can use TPF Software products (zTPFGI, zDFX, zRTF). In case of shared VPARS, multiple users use the same database. 10

11 Suite Server User Resource Command Centralized configuration in zVM  User Configurations (Existing)  Server Configuration (Existing)  Automation Configurations  Resource Definitions  Command Definitions Automation

12 Suite 12 Parameter to display the VPARS Console messages to command tab

13 Suite New parameters to define a VPARS as either a SHARED one or part of a POOL (On- Demand) Server 13

14 Suite Information about the resource required by the VPARS – RESOURCE Section Commands to bring up the system – COMMAND Section for Shared and Pool VPARS. Automation 14

15 Suite Information about all the resources that is required to bring up the system. Composed of various sections for resources and each section has the information about that resource type. Resource 15

16 Suite Commands to perform some functionality. For each function, a section has to be defined in this file, with the list of commands to perform the function. Command 16

17 Suite CMS file that will have the list of all pool VPARS along with information like pool state, VPARS state and time stamp. Created by the first user requesting a VPARS from the pool after installing this product. The name and location of this file should be coded as PoolFile and PoolPath under Pool section in PDWSRVR.CONFIG file 17

18 Suite 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 18

19 Suite AVAILABLE -Available for use. Yet to bring up the system READY-Ready for dispatch (system is in NORM State) PROGRESS-VPARS is assigned and the worker is bringing up the vpars IN_USE-In use by the user ERROR-Error in bringing up the system RECHECK-To check in the next clean up (when VPARS is logged on) SUSPEND-Suspended temporarily for some maintenance work CLEANUP-Marked for cleanup 19

20 Suite For more information, contact: Thiru Thirupuvanam TPF Software, Inc


Download ppt "Suite www.tpfsoftware.com. Suite Part of zTPFGI suite of products and it is VM based. Efficient and Effective management of the process of bringing up."

Similar presentations


Ads by Google