Content Inside :
* We need an easy way to Web-enable our legacy 3270 CICS applications
* Development tools like CSP, Natural, and HPS have their own ways of doing it
* But what about BMS or 3270 Data Stream applications written in languages like COBOL, PL/I and Assembler?
* 10 years ago the then CICS GUIDE Nordic Group made a “Screen Manager” report to IBM, which turned out to be way ahead of its time
* The 3270 Bridge addresses this requirement, but there is still plenty of room for improvement
* Loaded with expectations, a team of fearless CICS Systems Programmers embarked on an exploration journey under the 3270 Bridge. They wanted to componentise screen-oriented applications in order to run unchanged applications with a new interface, even when the source code had been lost or was otherwise unavailable. They even had been promised ”Minimum Coding”, and who can resist that?
* They supported a Mainframe Web Enablement project that needed a distributed password administration. This could be achieved by front-ending a vendor CICS application.
* They also hoped for an easy and clean interface to be called from anywhere: CWS, CTG, APPC, EXCI, etc. etc. But they had to penetrate a jungle of ADS Descriptors and vectors, to modify samples, and to find, design, and build new tools just to get anywhere near where they wanted.
* This presentation aims at giving a little inspiration and a little help on methods, tools, and design.
* What is that Bridge, anyway?
* 3270 Data stream + Bridge + DFHWBTTA
* Reassembled BMS + Bridge + DFHWBTTA
* Performing a Real Transformation
* Control Blocks and Data Areas
* The CSC Denmark Internal Bridge Project
* Tools
* When to bridge and when to componentise
* What do we need next from IBM?
What is that Bridge, anyway?
* A virtual terminal, implemented by hooking into a few CICS functions, with a handful of samples
* Runs 3270 Data Stream applications and BMS applications – under certain restrictions
* “Bridge Mechanism”, “Bridge Facility”, “Bridge Environment”
* An alternative to HLLAPI, Host On-Demand, EPI, FEPI, and native 3270 Data Stream programming, not a Screen Scraper
* The 3270 bridge provides an interface so that you can run 3270-based CICS transactions without a 3270 terminal. Commands for the 3270 terminal are intercepted by CICS and replaced by a messaging mechanism that provides a bridge between the end-user and the CICS transaction.
* The bridge mechanism is the CICS function that allows a user transaction to be run without a VTAM 3270 terminal. Terminal input/output commands are intercepted by a bridge exit that emulates the terminal by passing the commands, packaged as messages to the end-user or client application.
* The bridge environment is established by CICS so that the user transaction can be executed and certain commands intercepted. A bridge exit and a bridge facility are essential components of the bridge environment.
* The bridge facility is a virtual terminal, replacing a real 3270, which is visible only to the user transaction and does not appear in response to CEMT I TERM or CEMT I TASK.
* It has a dynamically created TERMID that can be used, for example, as the basis of a unique name for a TD or TS queue.
My be you need full description for PPT : Swimming Upstream under the 3270 Bridge, you can download this PPT : Swimming Upstream under the 3270 Bridge or online view this PPT : Swimming Upstream under the 3270 Bridge document. This PPT : Swimming Upstream under the 3270 Bridge powerpoint presentation available from category Swimming. Download Seminar Paper Powerpoint Presentation PPT : Swimming Upstream under the 3270 Bridge PPT slide and get information about PPT : Swimming Upstream under the 3270 Bridge.
Category : Swimming