GH12-5238-02
The IBM Communication Oriented Message System (CORMES) program product is designed to build the central "paper-less" message exchange system in an organization, connecting terminal users and application programs of different functions. It provides communication links:
CORMES operates under the control of CICS/DOS/VS and DL/I DOS/VS or CICS/OS/VS and IMS/VS, respectively.
Beginning with Release 2, Modification Level 0 of CORMES, the TFG2000 Base Product (Program Number 5688-019) is a required prerequisite. It contains data bases, common code and installation aids.
CORMES is application-independent and can be used in most industries, for example; manufacturing, process, finance, distribution, and public sector. CORMES can be applied during the design of new interactive application programs, and it can be integrated into existing programs. CORMES interface programs help the user to incorporate CORMES functions into newly designed or existing online applications written in Assembler language, PL/I or COBOL.
CORMES is especially suited for TFG2000 applications as action messages are an integral part of TFG2000. These messages indicate the occurrence of an application exception, an application imbalance, or a normal condition requiring follow-up action. If CORMES is installed together with TFG2000 product(s), the CORMES files and tables are prepared for message interchange to TFG2000 needs.
Summary of Amendments
CORMES is a program to improve, simplify, and standardize the information exchange within an organization. It provides user services, application programmer services, and system services to enable information exchange:
Two major communication principles are supported by CORMES: the action file concept and the trigger concept.
Support of action messages
Action messages can be issued by application programs or terminal users on the occurrence of predefined events whenever human actions must be taken or decisions made.
Example: In a customer servicing application, an incoming order exceeds the customer's credit limit. The application automatically sends an action message to an authorized person requesting either a credit limit increase or an order rejection.
Action messages are inserted into action files associated with departments, functions, or individuals.
Action messages comprise formatted and unformatted data and can be manipulated and distributed via the CORMES functions. They can be routed from one terminal user to another, for instance, to represent a "case" that must be processed by several individuals.
The following functions are offered to a terminal user at the display unit:
Another group of similar functions can be included in application programs to communicate with external users:
CORMES provides interface programs to incorporate these functions into application programs written in Assembler, PL/I, or COBOL language.
An action file monitor checks due dates of action messages and message queue sizes. Whenever a message is found beyond the user-defined limits, a monitoring message is sent to a predefined address. In addition statistics are provided illustrating the user workload.
Support of Trigger Messages (Optional)
In CORMES, trigger messages initiate the asynchronous execution of application programs. They are issued by application programs and, besides simply triggering execution, can transfer data to the triggered program. The trigger messages are stored by CORMES in CICS facilities.
CORMES facilitates the following triggering functions:
Example: An application clears invoices for payment whenever they are received. The data for check printing is stored in the trigger file of a print program. Whenever a certain time of day has been reached, or a predefined amount of invoice data has been accumulated, the printing of the checks is initiated.
Utility Programs
The user of CORMES must define the action file, trigger files, and tables containing rules for message handling. Utilities are provided to set up and maintain the message tables and to initially load the action file.
Machine Requirements
Programming Requirements
These programs are written in Assembler. They require the Assembler Compiler for installation and error correction.
The programs are designed to operate with the following programs at the stated release level or their current, subsequent release:
These programs are written in Assembler. They require the Assembler Compiler for installation and error correction.
The programs are designed to operate with the following programs at the stated release level or their current, subsequent release:
Where release levels are given in this section, the above statements apply also to subsequent releases, if any, of the required programs unless otherwise stated.
Testing Period
Installation/Location License
Not applicable
A separate license is required for each machine on which the licensed program will be used.
Usage License
Not applicable
Type/duration of Program Services
Central Service
Until discontinued by IBM with a minimum of six months written notice.