1 / 15

T PF to T PF F unction S erver ( zTTFS ) Overview

T PF to T PF F unction S erver ( zTTFS ) Overview. The Problem. z/TPF transactions aren ’ t simple They involve multiple systems and networks And the transactions need to access data from remote resources for successful completion Example:

iniko
Download Presentation

T PF to T PF F unction S erver ( zTTFS ) Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TPF to TPF Function Server (zTTFS)Overview

  2. The Problem • z/TPF transactions aren’t simple • They involve multiple systems and networks • And the transactions need to access data from remote resources for successful completion • Example: • Middle of the reservation transaction – we need Credit card authorization • Need to send data (credit card number, name, expiry date etc.) • Need to receive data (authorization code)

  3. The Solution • Allows Client VPARS to communicate with Server VPARS – which has access to the network • Without special scheduling • Without changing test systems TPF to TPF Function Server T S F T S T F T

  4. Benefits of zTTFS • End-users don’t have to compete for systems that have connectivity • z/TPF installations with zTTFS can provide N number of client VPARS with unlimited external connectivity without any physical network attached • zTTFS provides ability to share critical network resources across multiple VPARS

  5. z/TPF System request response Current Transaction Flow External System Reservation transaction – which requires Credit Card authorization in the middle Complete Reservation Initial Reservation Credit Card Authorization

  6. Client 1 Server zVM Repository High Level Overview External System • Configuration tables from repository copied to client and server • Transaction initiated • Check Intercept table for condition • If condition is satisfied send the request to Server • Server processes the request • Response is sent to client & transaction completes • Response to user

  7. Developer VPARS Server zVM VPARS Client 1 Repository High Level Overview: Request-Reverse Context Table External System

  8. Specifications • Client VPARS connects to Server VPARS • Server VPARS connects to all external networks • zTTFScode executes on the client VPARS and the Server VPARS • User exits provided for customization

  9. Configuration Tables • Configuration tables are required to control the Message traffic flow between client and server VPARS. • Using configuration tables customer can specify certain rules to control message traffic at different layer of message traffic

  10. Configuration Tables • Intercept Name Table • Name of the intercept • Scripts to be invoked • Owner VPARS • Destination VPARS • Conditions to be satisfied • Example: R9 + 100 + 300 + 500 = C’BA’ • Resides in centralized repository (zVM) Intercept Table 1 Intercept Table n

  11. Configuration Tables • Script Name Table • Name of the script • Segment to be invoked in z/TPF • Resides in centralized repository (zVM) Script Table

  12. Scripts • Once the message traffic is intercepted in client, Scripts are required to exchange relevant data between client and server, before we continue to run the transaction in server or VISA VERSA • Scripts are unique and can be coded to cater for specific message traffic • Scripts are to be coded at the customer place • Scripts have the capability to exchange: • Data block • Data in ECB memory • Data from heap memory • File and file chain • User exits (extensions) provided at the time of send and receive part of the script

  13. Script Structure VPARS Server Send Data Level Set Data Level VPARS Client Send Heap Set Heap Set File Chain Send File Chain

  14. Client Requirement • Subject Matter Expertise • Knowledge of current intercepts • What needs to be sent across • What needs to be received • Etc. • List of Intercepts • Program / Macro to intercept • Data to send the other side • Conditions to trap the intercept

More Related