Developing applications
You can develop applications in Java™, COBOL, C, C++, PL/I, and Assembler languages. CICS® provides application programming interfaces (APIs) so that applications can access CICS services and data in other products, such as VSAM and DB2®.
For a list of the CICS application programming interface commands, see CICS command summary.
- Creating business services from CICS applications
Applications that are business services can participate in a service-oriented architecture (SOA). A business service is a service that is aligned with business processes and models rather than a technical implementation. You can expose existing and new CICS applications as part of a business service using the support provided in CICS. - Programming languages and Language Environment
Language Environment®, supplied as an element of z/OS®, provides a common set of runtime libraries. Language Environment allows you to use only one runtime environment for your applications, regardless of the programming language or system resource needs, because most system dependencies have been removed. - Translation and compilation
Some older compilers (and assemblers) cannot process CICS commands directly. An additional step is needed to convert your program into executable code. This step is called translation , and consists of converting CICS commands into the language in which the rest of the program is coded, so that the compiler (or assembler) can understand them. - Developing for recovery
When you are planning aspects of recovery, you must consider your applications, system definitions, internal documentation, and test plans.
Developing for asynchronous requests
When you develop applications for use with the CICS asynchronous API, you will need to consider the flow of the asynchronous API commands and the available options for each command. Channel handling must also be considered if you want to pass input or receive responses as part of an asynchronous request.- Developing with the BTS API
This section provides a detailed description of the BTS application components, and explains how you can use them. - Developing with the FEPI API
Application developers can use CICS API commands to develop FEPI applications. This information describes how to develop FEPI applications, including the interfaces that are available and how to handle conversations and errors. - Developing COBOL applications
Use this information to help you code, translate, and compile COBOL programs that you want to use as CICS application programs. - Developing C and C++ applications
Use this information to help you code, translate, and compile C and C++ programs that you want to use as CICS application programs. - Developing PL/I applications
Use this information to help you code, translate, and compile PL/I programs that you want to use as CICS application programs. - Developing Assembler language applications
Use this information to help you code assembler language programs that you want to use as CICS application programs. - Developing Java applications
You can write Java application programs that use CICS services and run under CICS control. Using the CICS Explorer® SDK, you can develop applications that use the JCICS class library to access CICS resources and interact with programs that are written in other languages. You can also connect to your Java programs by using various protocols and technologies, such as web services or CICS Transaction Gateway. - Developing REXX applications
- Developing distributed applications
You can develop an application that runs across multiple CICS regions and access resources in multiple regions. CICS provides a number of facilities for applications, including function shipping, distributed transaction processing, and transaction routing. - Developing for external interfaces
CICS allows you to develop applications to communicate with external data and resources, such as DB2, WebSphere® MQ, IMS™ DBCTL, data tables, client programs running in an Open Systems Distributed Computing Environment (DCE), and ONC RPC applications. - Developing for access to data tables
You access a data table with the same EXEC CICS file control commands that you use with any normal CICS file. These commands can be used fully with a CICS-maintained data table and, with some restrictions, a user-maintained data table. - Developing for access to data sources
- Developing applications to use the CICS-WebSphere MQ bridge
A non- CICS application can communicate with a CICS program or transaction by sending and receiving WebSphere MQ messages over the CICS-WebSphere MQ bridge. The data required by the CICS application is included in request messages, and the CICS-WebSphere MQ bridge uses reply messages to return the data provided by the CICS application. - Developing applications to use the CICS-WebSphere MQ adapter
The CICS-WebSphere MQ adapter implements the WebSphere MQ Message Queue Interface (MQI) for use by CICS application programs. The adapter also supports a CICS-WebSphere MQ API-crossing exit. You can use this exit to intercept MQI calls as they are being run, for monitoring, testing, maintenance, or security purposes. - Developing Java EE applications
You can develop an application that uses the CICS API to interact with clients or a server over HTTP. CICS also provides a business logic interface to link to an application instead of calling it through the CICS HTTP listener. - Developing web services
- Developing SAML applications
You can develop applications to use the SAML facilities provided in CICS.
developing.html |
Last updated: Monday, 5 June 2017