Generation of standalone CICS business application accessed by the 3270 Interface and by MQSeries & Securing CICS with RACF

Busse, Tobias
This master thesis deals with the design, programming, implementation and presentation of on-line business applications for IBM's On-Line Transaction Processing (OLTP) system called Customer Information Control System (CICS). According to the book "Designing and Programming CICS Applications” ([HOR00]) published by John Horswill we explain two out of many feasible procedures to present the functionality of CICS resp. CICS business applications. As the main result, we create for each of both procedures a business application representing a little clip of a bank customer account program. These applications access a database-like file stored on an Operating System/390 (OS/390) server to create, read, update, and delete customer accounts. Both use CICS not only as a transaction processing system but also as an application server that manages business applications 24 hours a day for 7 days a week. The difference between the two business applications are the data transfer and information display methods. The first procedure describes how to create a business application that uses the legacy 3270 Interface to inquire a customer record stored on the OS/390-server and how to display the information on a 3270 terminal screen (also called as the green screen). In contrast, the second business application uses Message Queuing (MQ) provided by IBM's Message Oriented Middleware (MOM) product MQSeries to transfer the request data to and the response data from the customer account file between CICS and the Java Virtual Machine (JVM). This JVM runs on a WINDOWS2000 client, whereas MQSeries has to run on both – the OS/390-server and the WINDOWS2000 client. For this procedure, the so-called MQSeries CICS Bridge – an interface between CICS and MQSeries on the OS/390-server – is installed and activated. It is also described how to use the Message Queue Interface (MQI) that connects MQSeries and JAVA on the client computer system. Hence, the business logic component is used by both sample applications, but they differ in the presentation logic components. The programs of the business logic component, written in the Common Business-Oriented Language (COBOL), are responsible for the data transfer to and from the customer account file to update or read it, for the business calculations, and for the error handling. The presentation logic component of the first business application – the CICS application NACT – is also written in the COBOL and use the Basic Mapping Support (BMS) to set up the 3270 Interface. In the second business application called the MQSeries CICS application MQNACT the programs of the presentation logic component are written in JAVA. Additionally, this master thesis describes the security management of CICS using IBM's External Security Manager (ESM) Resource Access Control Facility (RACF). The main part of this procedure is to allow only authorised terminal users an access to an existing CICS address space, including some CICS default user identifiers (userids), as for example the CICS Region Userid (CRU), and the Default CICS Userid (DCU). Furthermore, an authorised user should/may use only those CICS resources for which a permission exists. Securing CICS resources is explained on the examples of the CICS Transactions Security mechanism and the CICS Command Security mechanism.
Pubdate / Erscheinungsdatum: 
Pages / Seitenanzahl: 
Notes / Bemerkungen: 
An accompanied CD-ROM is also available; it includes most of all listings and some additional stuff. Pls use the printed version provided by the library of the university of Leipzig to list the content of the CD-ROM.
2004-13.pdf6.2 MB