Rational EM – RDz/RTC with CA Endevor

Scenario Overview

Keith AllenEM Solution ArchitectIBM Rational

2

JVM

RSE Daemon

JVM

Server processconnect via socket

(running as daemon)

Server Threads

Miner Threads

Authenticate client

communicate via socketpair

start as a thread

start as a thread

TSO Server(running as daemon)

start as a process

• A single RSE Daemon is running and provides daemon socket for each client• Multiple Server processes are running as a daemon and accommodate clients until its heap usage ratio will reach some threshold.

RDz Host startup flow

3

Z - USS

RTC JTS - WI

Locate WI

MVS Rexx Check STATUS

Update Comment with Endevor Action

Authenticate RTC WI client

communicate via USS Curl

• A MVS based Rexx that passes Endevor parms to USS Rex• Sign into RTC (JTS) and locate WI• Check WI Statue / Update required WI Fields• Return 0 is OK else Error 2256

RTC to CA Endevor flow

Validate RTC WI

Update RTC WIUpdate WI

Status with next RTC WI Flow

Endevor CCID

Endevor CCID = RTC WI #

Current situation

Keith AllenEM Solution ArchitectIBM Rational

RDz 3270 EmulationEndevor RP View

Views – Carma – RTC – Zos …

Potential Running

Use of RTC and Endevor and Non Endevor

Keith AllenEM Solution ArchitectIBM Rational