It looks like you want to define a COBOL program to CICS using the standard CICS CEDA transaction. How you logon to CICS depends on your organisation. If you have a TN3270 session with z/OS (using an emulator like PCOM), then you’d normally have some kind of ‘hello’ screen. Resource definition in cics. Definitions are stored in assembled tables in a program library, and installed during CICS initialization. The method you use depends on the resources you want to define. Method Description. Because CEDA operates on an active CICS system, care should be taken if it is used in a production system. Transaction definition; CEDA define transaction; 1 The 'indoubt' Attributes; CEDA Define Profile. Defining Programs, Mapsets and Libraries. CEDA Define Program; Mapset definition; Program Autoinstall; SIT parameters for Program Autoinstall; User-replaceable module COMMAREA; Program Autoinstall Models; Program Autoinstall Summary; Define Library. – PCT is checked to see the associated program. – PPT checks whether the program is in main storage or on disk. If it is on DISK, it loads the program on to main storage. How to define a new transaction in CICS: CEDA transaction is used for defining a transaction in CICS. Installing a program. If the CICS region uses Program Autoinstall you should be able to run the transaction. If the REGION does not use program autoinstall, define the program using 'CEDA Define Program(YYYYYY) G(ZZZZZ)' Then do a 'CEDA INSTALL G(ZZZZZ)' Run the transaction and enjoy. In CICS TS 3.2, If you try to define a new URIMAP (via CEDA) when you set the. CEDA command is mainly use for defining the entries with group name. If there is no group present previously than CICS will define a group.for example: CEDA define Trans(TXN1) gr(G1);if the group G1 is not present then CICS will define G1 by itself and put Transaction TXN1 into it.
Transaction in CICS has a great importance which is the unit of work performed and is represented by a 4 char TRANS ID. It is linked to one or more programs and once a transaction is initiated, programs that are defined gets executed. At the time of transction definition, these programs needs to be given/linked.
In simple words Transaction is a Unique code to execute any program under CICS. Program can not be invoked directly by the user. Either transaction is required or it should be invoked by an other program.
When a Transaction is invoked, program associated with that is loaded in to storage and a task gets started.
– PCT is checked to see the associated program.
– PPT checks whether the program is in main storage or on disk. If it is on DISK, it loads the program on to main storage.
How to define a new transaction in CICS:
CEDA transaction is used for defining a transaction in CICS. It has many options in the definition screen, most of these options are default and can be set based on any other existing transaction in the same group/application.
Below is the Sample definition:
CECI is used to check the syntax of the command. It executes the command, only if the syntax is correct.
Type the CECI option on the empty CICS screen after having logged in. It gives you the list of options available.
Example
Following example shows how to send mapped output data to terminal. We will be discussing about MAPS in the upcoming modules.
CEDF
CEDF is known as CICS Execute Debug Facility. It is used for debugging the program step by step, which helps in finding the errors.
Type CEDF and press enter in the CICS region. The terminal is in EDF mode message will be displayed. Now type the transaction id and press the enter key. After initiation, with each enter key, a line is executed. Before executing any CICS command, it shows the screen in which we can modify the values before proceeding further.
CMAC
CMAC is known as CICS Messages for Abend Codes. It is used to find the explanation and reasons for CICS Abend Codes.
Example
Following example shows how to check details for an Abend code −
Cics Cemt Set Program
CESF
CESF is known as CICS Execute Sign Off. It is used to Sign Off from the CICS region.
Example
Following example shows how to log off from the CICS region −
CEBR
CEBR is known as CICS Execute Temporary storage Browse. It is used to display contents of a temporary storage queue or TSQ.
CEBR is used while debugging to check if the items of the queue are being written and retrieved properly. We will discuss more about TSQ in the upcoming modules.
Define Program Logic Formulation
Example
Following example shows how to invoke the CEBR command −
CICS Concepts
Each command could be achieved by executing a series of CICS macros. We will discuss some basic features which will help us understand the concepts better −
Multitasking
This feature of operating system allows more than one task to be executed concurrently. The task may be sharing the same program or using different programs. The CICS schedules the task in its own region.
Multi-threading
This feature of the operating system allows more than one task to be executed concurrently sharing the same program. For multi-threading to be possible, an application program should be a re-entrant program under the operating system or a quasi-reentrant under the CICS.
Re-entrancy
A re-entrant program is one which does not modify itself and can re-enter in itself and continue processing after an interruption by the operating system.
Quasi-reentrancy
A quasi-reentrant program is a re-entrant program under CICS environment. CICS ensures re-entrancy by acquiring a unique storage area for each task. Between CICS commands, the CICS has the exclusive right to use the CPU resources and it can execute other CICS commands of other tasks.
There are times when many users are concurrently using the same program; this is what we call multi-threading. For example, let’s suppose 50 users are using a program A. Here the CICS will provide 50 working storage for that program but one Procedure Division. And this technique is known as quasi-reentrancy.