Executive Summary
This paper discusses the details of the migration of CICS (Customer Information Control System) applications to ASP.NET and NetCOBOL for Microsoft .NET. (8 Printed Pages)

CICS applications operate in much the same way pseudo-conversational programs do. Each time a new screen is shown, the program ends and the connection between the application and the terminal is severed. By disconnecting and not waiting for the user's response, CICS applications are able to serve a large number of users concurrently. This is one of the largest benefits of CICS and one of the primary reasons for its widespread use today.

This disconnected application model is very similar to the web application environment. When a user loads a screen in a Web application, the Web server processes the request and sends the corresponding screen. After that screen has been sent, the connection between the server and the client is broken. When the user enters the necessary information and submits the screen, a new request is generated and sent to the Web server. At that point, the Web server determines the necessary action based upon the user's request and then sends the results to the user.

Request a Copy
If you would like to receive a copy of Intensity Software's white paper " CICS Migration to ASP.NET and Fujitsu's NetCOBOL for Microsoft .NET" (August 2002), please fill out the form below. Fields marked with a red asterisk (*) are mandatory.

Please be sure to enter your email address correctly. A PDF version of the white paper will only be emailed to the address you specify.