CICS

(Customer Information Control System)
1

Table of Contents
• • • • • • • • • • • Introduction to CICS Basic Mapping Support Program Control File Processing Error Handling Queues Interval and Task Control Recovery and Restart Program preparation CICS Supplied Transactions Case Study
2

Introduction to CICS
• Customer Information Control System -CICS developed in late 1960s as a DB/DC control system • CICS provides an interface between the Operating System and application programs • Macro Level CICS - initial version Assembler macro to request CICS services • Command Level CICS - high level lang.version - commands to request CICS services - Single command can replace series of macros

3

Usually in seconds 4 . ONLINE SYSTEM Data is entered as needed not in sequence (terminal) Since processing sequence is unpredictable. 3. 6. 5. special recovery/restart proc. BATCH SYSTEM Input data is prepared and given in sequence (file) Processing sequence is predictable and hence restarting the process in case of failure is easy. is required in case of failure Programs and files can be shared Transaction can be run at any time O/p displayed on Terminal updated files Response Time: Could be in minutes or second. 6. 3.Batch & Online : Differences 1. 2. 4. 4. Programs and files can‟t be shared Programs are scheduled through jobs O/P printed on paper or in sequential of VSAM or Indexed files Response time: Could be scheduled to be Hours or days 1. 2. 5.

Files & Database 5 .CICS & Operating System Operating System CICS Enter Code : User’s App.

and Application Programs 6 .DB/DC System Terminals Data Base Central System CICS System Environment & API routines.

CICS System Services • Data-Communication Functions • Data-Handling Functions • Application Program Services • System Services • Monitoring Functions 7 .

In CICS.A basic unit of work which is scheduled by the operating system or CICS Ex -Read from and write to the terminal • Transaction :.Task & Transaction • Task :.An entity which initiates execution of a task. transaction is identified by the transaction identifier (Trans-id) 8 .

Application Programming Concepts • Pseudo-Conversational • Multitasking • Multithreading • Quasi-Reentrancy 9 .

a significant amount of resource will be wasted just waiting • Pseudo-Conversational.Terminal Conversation • Conversational : A mode of dialogue between program and terminal based on a combination of sending message and receiving message within the same task – Since human response is slower than the CPU speed. A mode of dialogue between program and terminal which appears to the operator as a continuous conversation but which is actually carried by a series of tasks 10 .

. EXEC CICS RECEIVE ---.. : process EXEC CICS SEND ----.12345 END-EXEC..SECOND PROCESS..<= TSK1.. : FIRST-PROCESS. : process 11 ..Program Waits For Response .<= EMP(12345) Details END-EXEC...<= User Enters Data END-EXEC. EXEC CICS RECEIVE ----. * .Terminal Conversation Example PROCEDURE DIVISION.

EXEC CICS RETURN TRANSID („TSK2‟) END-EXEC. : EXEC CICS SEND END-EXEC. 12 . : EXEC CICS SEND END-EXEC.Pseudo-Conversation Example Transaction TSK1 Program PROG1 PROCEDURE DIVISION. : EXEC CICS RECEIVE END-EXEC. : EXEC CICS RECEIVE END-EXEC. EXEC CICS RETURN END-EXEC. Transaction TSK2 Program PROG2 PROCEDURE DIVISION.

CICS Components • Control Programs (or Management Modules) Programs that interface between OS and app. Eg. pgm Handle the general functions that are crucial to operation of CICS • Control Tables Define the CICS environment Functionally associated with the management module • Control Blocks (or Areas) Contain system type information. Task Control Area contains information about the task 13 .

Mangement Pgms & Ctrl Tables • Programs Program Control File control Terminal Control Task Control Temporary Storage Transient Data Storage Control Interval Control Journal Control • Tables PCP FCP TCP KCP TSP TDP SCP ICP JCP Processing Program Table File Control Table Terminal Control Table Program Control Table Temp. Storage Table Destin. Control Table PPT FCT TCT PCT TST DCT 14 .

CICS Program Considerations Considerations: • Must eventually return control to CICS • Can‟t modify procedure division instructions because CICS programs may be shared by many tasks • Can modify working storage since a unique copy of working storage is created for each task 15 .

DISPLAY. • FILE SECTION. I/O SECTION to be specified in the ENVIRONMENT DIVISION. GOBACK are avoided. EXHIBIT. and non-CICS READ & WRITE statements are not permitted because file management is handled by CICS. OPEN. SECTION. CLOSE. (STOP RUN & GOBACK are sometimes included in order to eliminate compiler diagnostic but never executed) 16 . STOP RUN. TRACE.CICS Program Restrictions Restrictions: • No CONFIG. • COBOL commands such as ACCEPT.

01 WS-INPUT. SAMPLE. DATA DIVISION. 17 . 05 WS-TRANSID PIC X(4). 05 FILLER PIC X(1). 05 WS-IN-EMP-CD PIC X(4) VALUE ALL „X‟. ENVIRONMENT DIVISION.Sample CICS Program IDENTIFICATION DIVISION. PROGRAM-ID. WORKING-STORAGE SECTION.

.) 01 WS-OUTPUT. 01 WS-LENGTH PIC S9(4) COMP. CAN Include DFHCOMMAREA if data needs to be communicated between two transactions or multiple iterations of the same transaction. PERFORM 200-SEND-OUTPUT. PROCEDURE DIVISION. 05 FILLER PIC X(16) VALUE „EMP CODE : „. EXEC CICS RETURN END-EXEC.Sample Program (Contd. PERFORM 100-RECV-INPUT. 05 WS-OUT-EMP-CD PIC X(4). 000-MAINLINE. LINKAGE SECTION. 18 .

Sample Program (Contd. EXEC CICS SEND FROM (WS-OUTPUT) LENGTH (20) ERASE END-EXEC.. MOVE 9 TO WS-LENGTH.) 100-RECV-INPUT. MOVE WS-IN-EMP-CODE TO WS-OUT-EMP-CODE 200-SEND-OUTPUT. 19 . EXEC CICS RECEIVE INTO (WS-INPUT) LENGTH (WS-LENGTH) END-EXEC.

CICS Translator The CICS translator converts CICS commands into the COBOL code so that it could be compiled by a Standard Cobol compiler CICS program with CICS Commands COBOL Statements CICS Translator 20 .

Translator • When you compile a CICS/VS program the translator will automatically add many lines of code to your program. which can be seen in the compiled listing 21 .

Basic Mapping Support 22 .

Topics in BMS • Introduction to BMS • Map and Mapset • Physical and Symbolic Map • Map Definition Macros • Screen Manipulation/Handling • Screen Design Considerations • Interfacing with Terminal using a Map 23 .

Introduction to BMS Introductory concepts In online systems. a terminal (e. 24 . In order to display formatted screen. re-coding is required whenever there is change in the terminal device or screen format.g. To remove this device and format dependency from application program. this NMDS is a mixture of Buffer Control Characters (BCCs) and text data. CICS provides a facility called Basic Mapping Support (BMS). So if NMDS is used. NMDS is designed for a particular terminal and is thus both device dependent and format dependent. 3278) must receive a series of data stream called Native Mode Data Stream (NMDS) based on the hardware protocol. formatted screens are used.

25 . screen field positions. • Map is a program written in assembly language. and field characteristics. • BMS macros are available for Map coding. and Mapsets to define the screen attributes...) • Construct NMDS .Primary Functions of BMS • Removal of device dependent codes from Application Program • Removal of constant information from Application program (Headers.Native Mode Data Stream • Text handling • Terminal Paging & Message routing • Contents of the screen defined thru‟ BMS is called Map. Titles. The BMS Macros are coded in the form of Maps.

PROGRAM=name Or 26 .Map and Mapset • Representation of one screen format is called Map (screen panel). • Mapset must have a entry in PPT as given below: DFHPPT DFHPPT TYPE=ENTRY. link edited together. • One or more maps.MAPSET=name TYPE=ENTRY. makes up a Mapset (load module).

To identify the device type 27 . Program. – Generic name – Suffix • Multimap Panel • Dynamically constructing a screen panel with multiple maps at the execution time 1.7 chars. Used in App.) • Mapset name has two parts.. 1 char.Map and Mapset (Contd.

For e. MAPSET1 MAPNUM1 Case 2: A mapset consists of several maps. For e.Map and Mapset (Contd. MAPSET2 MAPNUM1 MAPNUM2 28 .g..g.) The concepts of map and mapset can be utilized in two type of cases as given below: Case 1: A mapset consist of a single map.

29 .Types of MAPS There are 2 types of MAPS • Physical Map Physical Map is a map used by CICS (CSECT) Ensure device independence in the application program BMS macro coding ==> Assembly==> Link edit ==> Load module ==> LOADLIB ===> To be used by CICS • Symbolic Map Ensure device and format independence in the application program Symbolic Map is a map used by Application Program (DSECT) BMS macro coding ==> Assembly ==> Symbolic map definition ==> COPYLIB ==> Copied (COPY) into CICS application program.

02 EMPNAI PIC X(21). 30 . 03 EMPNAA PIC X. 01 EMPRECO REDEFINES EMPRECI. 02 FILLER PIC X(12). 02 EMPNAF PIC X.Example – Symbolic Map 01 EMPRECI. 02 FILLER REDEFINES EMPNAF. 02 FILLER PIC X(12). 02 FILLER PIC X(03). 02 EMPNAL PIC S9(4) COMP. 02 EMPNAO PIC X(21).

Logic Flow BMS source Assembler Physical MAP Symbolic MAP Linkage editor Load module (MVS) 31 .Physical & Symbolic Map .

field characteristics and the default data for each field and allows BMS to construct an output NMDS. In case of input operations.Physical Map • Physical Map. In case of output operations. At the program execution time the physical map is being used by CICS to load the screen image. 32 • • . length. the physical map defines the starting position. The mapset like any other CICS program is stored in CICS runtime library the PPT(Program Processing Table). The BMS macros are assembled and link-edited into CICS load library to create the physical map. the physical map defines the maximum length. the starting position for each field to be read and allows BMS to interpret an input NMDS.

assembled separately and catalogued into a copy library. . • The symbolic map can be used by the CICS application programs to dynamically to alter the field attributes. protect . and is used by the application program to send and receive information from the terminal. and highlight . unprotect specific fields on the 33 screen.Symbolic Map • The symbolic map is coded using the BMS macro. The program issues a COBOL COPY statement to include it in the program. modify screen cursor position. • The symbolic maps represents the actual data structure of the fields defined in the physical map. in the CICS SEND-MAP & RECEIVE MAP commands. The symbolic map serves as a DSECT for referencing the Terminal Input/Output Area (TIOA).

TIOAPFX=YES X X X X * * ANY COMMENTS 34 . LANG=COBOL.Map definition Macros General Format Column Number 1 setname operation Example EMPMAP DFHMSD 16 operands 72 contd. MODE=INOUT. STORAGE=AUTO. TYPE=MAP.

Macro identifier. It is the load module name. Optional key words (parameters) separated by comma. OPERATION OPERANDS CONTD : : : Comments : 35 . Current line can be continued by leaving this column non-blank (usually X) and the next line have to be started in 16th column.) Explanations: SETNAME : Name of the mapset. ‘*’ in column 1 makes the line comment.Map definition Macros (Contd. Mapset/Map/Field definition.. Used in CICS command to read or write one of the maps in the mapset.

.) INITIAL VALUES Escape Chars : : Always surround initial values by single quote marks ‘ and & 36 .Map definition Macros (Contd.

Order of Macros DFHMSD TYPE=DSECT DFHMDI DFHMDF DFHMDF : DFHMDI DFHMDF DFHMDF : DFHMSD TYPE=FINAL END Mapset Map A field A field Map A field A field Mapset 37 .

PRINT) 38 . Only one mapset is allowed in one assembly run.DFHMSD Macro The DFHMSD macro is used to define a mapset (TYPE=MAP) and its characteristics or to end a mapset definition (TYPE=FINAL). TIOAPFX=YES. X X CNTL=(FREEKB. MODE=INOUT.FRSET. and they're loaded together at execution time. LANG=COBOL. X X STORAGE=AUTO. All the maps in a map set get assembled together. Example: TSTMSET X DFHMSD TYPE=&SYSPARM.

) Options TYPE= DSECT MAP &SYSPARM FINAL MODE= IN OUT INOUT To define the map type For symbolic map For physical map For special assembly procedure To indicate the end of a mapset coding To indicate input/output operations For an input map only For an output map only For maps involving both input and output.DFHMSD Macro (Contd.. 39 .

DFHMSD Macro (Contd.. Required for the CICS command level.) STORAGE = AUTO To acquire a separate symbolic map area for each mapset BASE To have the same storage base for the symbolic maps of from more than one mapset TIOAPFX= YES To reserve the prefix space (12 bytes) for BMS commands to access TIOA properly. 40 .

DFHMSD Macro (Contd..)
CNTL=
FREEKB FRSET ALARM PRINT

To define the device control requests To unlock the keyboard To reset MDT to zero status To set an alarm at screen display time To indicate the mapset to be sent to the printer
This ensures device independence, required if other than 3270 terminal is being used To specify the user provided suffix number. This must correspond to the TCT parameter.

TERM=type

SUFFIX=nn

41

DFHMDI Macro
Defines a map and its characteristics Example EMPMAP DFHMDI SIZE=(ll,cc), X LINE=nn, X COLUMN=mm, X JUSTIFY=LEFT/RIGHT Options SIZE=(ll,cc) To define the size of the map by the line size (ll) and the column size (cc). Useful when the screen contains. LINE Indicates the starting line number of the map. COLUMN Indicates the starting column number of the map. JUSTIFY To specify the entire map (map fields) is to be left or right justified.
42

DFHMDF Macro
The DFHMDF macro is used to define a field in a map and its characteristics. This is the position on the screen where the field should appear. It's the position relative to the beginning of the map. Field starts with its attribute byte, so if POS=(1,1) is coded, then the attribute byte for that field is on line 1 in column 1, and the actual data starts in column 2. The length of the field (not counting the attribute byte) is specified. Literals can be specified within quotes; these character data is for an output field. It is used to define labels and titles for the screen and keep them independent of the program.

43

Sample Screen layout The above defines the screen layout as given below: ITEM NUMBER :&nnnnnnnn Where „&‟ Is the Attribute character „n‟ Is unprotected numeric „_„ Is Cursor 44 .

IC). LENGTH=8 X X X X X X X X 45 .NUM. ATTRB=(UNPROT.DFHMDF Macro For The Above Layout Define a field and its characteristics Example DFHMDF POS(ll.FSET. PICIN=„9(8)‟. PICOUT=„9(8)‟. INITIAL=„Customer No.cc). LENGTH=14 CUSTNO DFHMDF POS=(ll. :‟.cc). ATTRB=ASKIP. JUSTIFY=RIGHT.

The cursor skips to the next field. UNPROT Unprotected field. Only numbers (0 to 9) and special characters (“. NUM Numeric field. Data cannot be entered into this field.” and “-“) are allowed. ASKIP Autoskip. Data cannot be entered in this field. PROT Protected field. If data is entered. which precedes a screen field and determines the characteristics of a field. Data can be entered and this is used for all input fields. 46 .Attribute character Function: The attribute character is an invisible 1-byte character. it will cause the input-inhibit status.

.Attribute character (Contd. The cursor will be positioned in this field.) BRT Bright display of a field (highlight). 47 . the cursor is placed in the last field. DRK IC Dark display. IC is specified more than once. Insert cursor. MDT is set on so that the field data is to be sent from the terminal to the host computer regardless of whether the field is actually modified by the user. NORM Normal display. FSET Field set. In case.

If it is on (1). the data of the field will be sent by the terminal hardware to the host computer. it is automatically set to “1” (on) by the terminal hardware. Only when MDT is on. An effective use of MDT drastically reduces the amount of data traffic in the communication line and thus improves performance. Three ways of setting and resetting the MDT.Modified Data Tag Function: Modified Data Tag (MDT) is a one bit of the attribute character. it indicates that the terminal operator has not modified the field. 1. Terminal user modifies a field on the screen. 48 . it indicates that the operator has modified this field. If it is off (0).

when the map is sent to the terminal..Modified Data Tag (Contd. MDT will be reset to “0” (off) i. not modified for all the fields of the mapset or the map. 49 . If CNTL=FRSET is specified in the DFHMSD or DFHMDI macro. when the mapset or the map is sent to the terminal.e. (on i.) 2. MDT will be set to “1”.e. If FSET is specified in the ATTRB parameter of the DFHMDF macro for a field. 3. modified) for the field regardless of whether the field has been modified by the terminal user.

• Screen Layout : &xxxxx&$ &xx where $ Skipper field & Attribute byte X Unprotected field 50 .cc).ATTRB=ASKIP.Skipper Technique • Unlabelled 1-byte field with the autoskip attribute • DFHMDF POS(ll.LENGTH=1 • To skip the cursor to the next unprotected field after one unprotected field.

• Screen Layout : &xxxxx&$#&$ where # Stopper field 51 .cc).ATTRB=PROT.Stopper Technique • Unlabelled 1-byte field with the protect attribute • DFHMDF POS(ll.LENGTH=1 • To stop the cursor in order to prevent erroneous field overflow by terminal user.

the COBOL COPY statement can be used to include it in the application program.Format Of the Symbolic Map Format of Symbolic Map • Once the symbolic map is assembled and is placed in the COPY library. which is the TIOA prefix created by the TIOAPFX=YES of the DFHMSD macro. • Next is the definition of FILLER PIC X(12). this is required by the BMS under the CICS command level. • The symbolic map starts with the 01 level definition of the map name specified in the DFHMDI macro with the suffix ‘I’ for the input map and the suffix ‘O’ for the output map. 52 .

) For each field name (1 to 7 characters) specified in the DFHMDF macro. For the input field. the actual number of characters typed in the field will be placed by the BMS when the map is received. For the output field.Format Of the Symbolic Map (Contd. The meaning of these fields are given below: • Name + L: The half-word binary (PIC S9(4) COMP) field. 53 .. this is used for the dynamic cursor positioning. by placing one character suffix to the original field name. BMS creates three fields for inputs and three fields for outputs.

it will be X’80’ if the field has been modified but no data is sent (i. The Attribute byte for both input and output • Name + I: The input data field. For the input field. X’00’ will be placed if no data is entered.Format Of the Symbolic Map (Contd.. Note that space X’40’ is data. Otherwise this field is X’00’.e. • Name + A: fields. the field has been cleared).) • Name + F: Flag Byte. 54 . • Name + O: The output data field. The application program should differentiate X’00’ from space (X’40’).

01 EMPRECO REDEFINES EMPRECI. 02 EMPNAI PIC X(21). 02 FILLER PIC X(12). 55 .Example Of Symbolic Map 01 EMPRECI. 02 EMPNAL PIC S9(4) COMP. 02 FILLER PIC X(12). 02 EMPNAF PIC X. 02 FILLER PIC X(03). 02 FILLER REDEFINES EMPNAF. 03 EMPNAA PIC X. 02 EMPNAO PIC X(21).

IC).Cursor Positioning Techniques CICS provides multiple ways of to specify where to position the cursor on the screen.ATTRB=(UNPROT. Example : DFHMDF POS=(5. or to point to an error which has occurred during editing the user entries. • Static positioning (Achieved thru Map definition ATTRIB=IC).FSET. The cursor positioning is important to prompt an user of an entry he has to make.8).LENGTH=10 56 .

the mapset should be coded with MODE=INOUT in the DFHMSD macro. The cursor is placed dynamically through an application program by moving -1 to the symbolic map field-length field (i.Cursor Positioning Techniques (Contd.. 57 .) • Dynamic/Symbolic Positioning. The SEND MAP command must be issued with the CURSOR option (without value). fieldname + L) for the field where the cursor is to be placed. This approach is very useful when the cursor is to be placed at the field where data entry error has been detected by the data edit routine.e. Also.

: COPY MAPSET1 01 MAPSET1I 05 FILLER PIC X(6). 05 FIELD1I PIC X. 58 . 05 FIELD1F PIC X. WORKING-STORAGE SECTION.Cursor Positioning Techniques (Contd.) Example Of Dynamic Cursor Positioning. 05 FIELD1L PIC X(5)..

Cursor Positioning Techniques (Contd.) PROCEDURE DIVISION. 59 . : MOVE –1 TO FIELDL. The cursor will be placed at FIELD1 field of the map during execution. EXEC CICS SEND MAP(‘MAP1’) MAPSET(‘MAPSET1’) CURSOR ERASE END-EXEC..

) Dynamic/Relative Positioning (application program) The cursor is placed dynamically through an application program using the CURSOR(data-value) option in the SEND MAP command with the value of the relative position (starting from zero) of the terminal. 60 . overriding the static cursor position defined at the map definition time. At the completion of the SEND MAP command.Cursor Positioning Techniques (Contd.. the map will be displayed with the cursor placed at the specified position.

) Example EXEC CICS SEND MAP(„MAP1‟) MAPSET(„MAPSET1‟) CURSOR(100) ERASE END-EXEC.Cursor Positioning Techniques (Contd. The cursor will be placed at FIELD1 field of the map MAP1 during execution.. 61 .

The following are the three basic functions performed by CICS commands: Map Sending function – using the data in the symbolic map. BMS prepares the output NMDS. 3. Map Receiving Function – using the input NDMS from the terminal. and sends to the terminal. BMS prepares data in the symbolic map through the corresponding physical map. the corresponding physical map.Interfacing with a Terminal using a Map The BMS maps are used in the application programs for the actual terminal input/output operation. These operations are performed by a set of CICS commands for BMS. . 62 1. 2. Text Handling Function – BMS prepares text without using a map and sends to the terminal.

Application Program Send Map Command Symbolic Map BMS Output NDMS Terminal Physical Map Data Entry Application Program Receive Map Command Symbolic Map BMS Input NDMS Terminal 63 ..Interfacing with a Terminal using a Map (Contd.) Flow of Information from 3270 Terminal and the Application Program.

.Interfacing with a Terminal using a Map (Contd.) The following are the available commands: • RECEIVE MAP • SEND MAP • SEND CONTROL • SEND TEXT • SEND PAGE : : : : : To receive a map To send a map To send a control function to the terminal To send a text To send the accumulated text or maps as a logical message 64 .

: The Flag Byte which is normally X‟00‟.Receive Map Command RECEIVE MAP Command is used to receive input from a terminal. the symbolic map will contain valid data from the terminal in the following three fields as per each field defined by the DFHMDF macro: Field name + L : The length field. It will be X‟80‟ if the field has been modified but cleared. which contains the actual number of characters. X‟00‟ will be placed if no data is entered. : The actual input data field. typed in the screen field. At the completion of the command. Field name + F Field name + I 65 .

) Syntax: EXEC CICS RECEIVE MAP (MAPNAME) MAPSET(MAPSETNAME) [ SET(POINTER)| INTO(DATANAME) ] [ LENGTH(MSG-LEN)] [ HANDLE | NOHANDLE ] [ RESP() ] END-EXEC. • Conditions: INVREQ. MAPFAIL 66 ..Receive Map Command (Contd.

) MAP specified the name of the MAP defined thru DFHMDI command . SET is used when the address pointer is to be set to the address of the symbolic map (by CICS) so that the application program can directly refer to the record without moving the record content into the working storage area defined in the program. which describes the screen details.. INTO is used to specify the area in the working storage section to which the data from the terminal is to be placed. MAPSET specified the name of the MAPSET defined thru DFHMSD command which includes the MAP. 67 .Receive Map Command (Contd.

LENGERR.Receive Map Command (Contd.) RESP will be used by CICS to place a response code at a completion of the command.. NOHANDLE will cause no action to be taken for any exceptional condition occurring during execution of the CICS command. INVREQR . 68 . It occurs when the following keys are pressed in response to the RECEIVE MAP command: CLEAR or Attention Keys & ENTER or PF keys without entering data. HANDLE is used to transfer control to the procedure label specified if the exceptional condition specified occurs. MAPFAIL MAPFAIL is set when the data being mapped has a length of zero. Conditions : INVMPSZ .

which has the following three fields per each field defined by the DFHMDF macro: Name + L: The length field. 69 . where the application program places the data. Name + A: The Attribute byte for output fields. the application program must prepare the data in the symbolic map of the map to be sent. for which the application program need not prepare except when used for the dynamic cursor positioning.SEND MAP Command The SEND MAP command is used to send formatted output to a terminal. Before issuing this command. Name + O: The actual output data field. Application program will use it for dynamic cursor positioning.

. [DATAONLY] | MAPONLY]. [ CURSOR(VALUE) ].LENGERR 70 .SEND MAP Command (Contd.) EXEC CICS SEND MAP(MAP1) MAPSET(MAPSET1) ] [FROM(DATANAME) ]. [ FREEKB ] . [ RESP (DATANAME) ] END-EXEC. • Conditions : INVREQ. [ FRSET ] . [ HANDLE | NOHANDLE ] . [ ERASE ] .

MAPONLY is used when no data from your program is to be merged into the map. 71 . MAPSET specified the name of the MAPSET defined thru DFHMSD command which includes the MAP. DATAONLY is used when only the data from the program is to be sent to the screen. The constants in the map are not sent.) MAP specified the name of the MAP defined thru DFHMDI command . which describes the screen details..SEND MAP Command (Contd.

.SEND MAP Command (Contd. 72 .) FROM is used to specify the area in the working storage section from which the data is to be sent to the terminal.

Once the screen appears. CICS application program needs to trap the attention identifier keys and process various functions related to the AID keys.AID KEYS First time when a transaction is initiated the application program throws the screen image on the terminal thru SEND MAP command. ENTER & CLEAR key • EIBAID in the CICS Executive Interface Block contains. the AID (Attention Identifier ) Keys are being used to send the information back from the terminal to CICS to application program. recently used AID key. 73 . Salient Points • PF keys. PA keys.

Flow : User hits AID key – Control goes to CICS – To Application program. Syntax : EXEC CICS HANDLE AID Option (label) END-EXEC Conditions : INVREQ 74 .) • DFHAID – CICS System copybook which stores the values of the EIBAID field for the various AID keys. Program compares EIBAID to the DFHAID field and performs processing logic as per the AID key pressed.AID KEYS (Contd. • HANDLE AID establish the routines that are to be invoked when the aid is detected by a RECEIVE MAP command. EIBAID contains information about the last AID key pressed..

This helps at problem determination time. 75 . • Screen title and field descriptions should be self-explanatory. • Screen id should be placed at the top right corner of a screen. Instructions should be concise.Screen Design Considerations Functional Screen Design • Screen layout should be similar to source where terminal users enter data.

g. E.) • Large fields can be broken into a number of small fields. email ids and postal address.. sequence numbers helps. the field contact information can be split into contact numbers. 76 . • Error messages should be provided.Screen Design Considerations (Contd. Preferably the last few lines can be used for the error messages. • In case of repeated fields or group of fields.

in case the user forgets to enter a field data. • Highlight the error field. defaults values are assigned according to the field. 77 .Screen Design Considerations User-Friendly Screen Design • Screens should be simple and friendly. • The cursors should be placed in the appropriate fields. • Default values in fields helps in reducing keystrokes by the users. This enables users to identify the erroneous field easily. Using a different colour or blinking the error field can achieve this. • Calculations should be done by program and not by users. Also.

The help message should be instructive and kind and should not be rude. • Provide suitable help messages for erroneous entries. 78 . • Provide help on fields and their meanings.Screen Design Considerations (Contd.) • Alarm sound can be used for error entries. and lines makes a screen look good.. • Proper use of indentations. makes a screen user-friendly. spaces. which has details on each field. Using an attention key for a help menu. Artistic Screen Design • A simple screen layout is always preferred.

however the colour used should be in accordance with the norms and standards followed. • Related fields can be grouped together. 79 . This reduces manual skipping and is preferred.Screen Design Considerations (Contd..) • Colour can help in improving the screen design. • Protected fields should be skipped automatically. • Skipper/Stopper techniques can be used at appropriate places. Considerations for Human Errors • Important and useful fields can be placed at the top part of the screen.

Exercise .1 80 .

CICS File Processing Techniques 81 .

File Specific functions to be performed are the following. It is essential to know the various file handling commands for application programming. Defining a specific file to the CICS system. Handle any errors that occur during file processing • • • • • • • 82 . Reading and Updating a record Deleting a Record. Reading a file sequentially Reading a Key Sequenced file randomly Reading a file sequentially starting from a specific point.CICS VS FILE PROCESSING File handling in CICS is achieved thru a set of file handling commands.

CICS has a list of all the files it is allowed To access. Files do not need to exclusively defined in Application programs. Application programs do not need The FD Section. The files do not need to opened and closed in a CICS application program . When CICS/VS is closed down it closes all the files. Application program directly Refer to filenames in EXEC CICS Command. before being used in the program. This list is called the FILE CONTROL TABLE (FCT) and is maintained by the systems programmers When CICS/VS is started up.CICS VS FILE PROCESSING Instead. and the Input – Output Section. 83 . It goes through the FCT and makes all the files available.

CICS COBOL V/S COBOL BATCH COBOL CICS COBOL EXEC CICS READ DATASET (‘FILE IDENTIFIER) INTO (RECORD NAME) RID-FLD (record-key) END-EXEC.key) END-EXEC. READ DATAFILE INTO REC-AREA AT END MOVE ‘Y’ TO EOF-FLAG Replaced by WRITE RECORD-NAME FROM RECORD-AREA Replaced by EXEC CICS WRITE DATASET (‘File identifier’) FROM (Record-Name) RID-FLD (Record. 84 .

VSAM Different types of VSAM Datasets used in CICS are : • ESDS • KSDS • RRDS Entry Sequenced Dataset Key Sequenced Dataset Relative Record Dataset 85 .

Services Provided By CICS • Basic Operations required for a file are Adding a Record. Modifying an Existing Record. Deleting an Existing Record. • In Addition. Journaling. 86 . CICS Provides Exclusive Control. Opening and closing Files. Browsing One or Selected or All Records. (Record Level Locking). Data Independence.

) • Defining files can be done either by CEDA Transaction or DFHFCT Macro. etc. • FCT will contain all the Information about a file (like dataset name. access methods. permissible file service request. 88 .Defining A File in CICS • Files should be defined in FCT (File Control Table).

FILSTAT=(ENABLED.Syntax of DFHFCT Macro DFHFCT TYPE=FILE. DATASETNAME=NAME.READ.DELETE.OPENED) 89 . SERVRQ=(ADD.BROWSE.UPDATE).ACCMETH=VSAM.

• Records can be written in any order. 90 . A number of records can be added at a time. • Program should not open or close a File.File Handling in Programs • Files should not be defined in the Program. • Records can be inserted. updated or deleted.

91 . • LENGTH :. • RESP :.Important Key-Words • Dataset/File :.Working-Storage Area defined in the program where the CICS Puts/Gets the Data.Length of the Record to be Retrieved or Written.Contains the return code of the executed command.Contains the Record Key.Name in the FCT. • Into/From (WS-Rec) :. • RIDFLD :.

92 . IOERR. NOTFND. Condition: DISABLED. DUPKEY. NOTOPEN. LENGERR.Random READ EXEC CICS READ File(filename) [SET() | Into()] RIdfld(Rec-Key) END-EXEC.

Example for Random Read EXEC CICS READ File( 'INVMAS ') Into(WS-INVMAS-REC) Length(WS-INVMAS-LEN) RIdfld('7135950602') | RIdfld(WS-INVMAS-KEY) END-EXEC. 93 .

• During Browse Operation.Sequential Read • Sequential Read is done by Browse Oper. 94 . • Browse can be re-positioned. • End the Browse Operation at last. Records cannot be Updated. • Next and Previous Records can be Read as required Using ReadNext and ReadPrev. • Establish the pointer to the First Record to be Read Using StartBr.

95 .Syntax for STARTBR EXEC CICS STARTBR FILE(filename) RIDFLD(data-area) END-EXEC. NOTOPEN. IOERR. Condition : DISABLED. NOTFND.

96 .Reading the Record after STARTBR • Sequentially the Next or Previous Record can be read by a READNEXT or READPREV. • The first READNEXT or READPREV will read the Record where the STARTBR has positioned the File Pointer.

NOTFND.Syntax of READNext/READPrev EXEC CICS READNext | READPrev FILE(name) INTO(data-area)|SET(ptr-ref) RIDFLD(data-area) END-EXEC. IOERR. 97 . ENDFILE. LENGERR. Condition : DUPKEY.

Condition: INVREQ 98 .ENDBRowse • ENDBRowse terminates a Previously issued STARTBR. • SYNTAX : EXEC CICS ENDBR FILE(filename) END-EXEC.

• Syntax : EXEC CICS RESETBR FILE(filename) RIDFLD(data-area) END-EXEC.RESETBR • Its effect is the same as ENDBR and then giving another STARTBR. NOTFND. Condition: IOERR. 99 .

The record will be written depending on the Key. • For ESDS. RBA value is returned and Record will be written at the end of the File. 100 . RIDFLD should be the Record Key.WRITE Command • Adds a new record into the File. • For KSDS. • MASSINSERTion must be done in ascending order of the Key. RIDFLD is not used but after write execution.

IOERR. NOTOPEN. 101 . DUPREC. Condition: DISABLED.Syntax for WRITE EXEC CICS WRITE FILE(filename) FROM(data-area) RIDFLD(data-area) END-EXEC. NOSPACE. LENGERR.

• REWRITE automatically UNLOCKs the Record after execution. 102 .REWRITE Command • Updates a Record which is Previously Read with UPDATE Option.

103 . NOSPACE. IOERR. Condition: DUPREC. LENGERR.Syntax for REWRITE EXEC CICS REWRITE FILE(filename) FROM(data-area) END-EXEC.

1. The record read with READ with UPDATE will be deleted.DELETE Command • Deletes a Record from a dataset. • Record can be deleted in two ways. 104 . • Multiple Records Delete is possible using Generic Option. RIDFLD with the full key in it 2.

NOTOPEN. NOTFND. IOERR. 105 .Syntax of DELETE EXEC CICS DELETE FILE(filename) RIDFLD(data-area) END-EXEC. DUPKEY. Optional Condition: DISABLED.

NOTOPEN. 106 . IOERR. • Syntax : EXEC CICS UNLOCK FILE(filename) : [other options] END-EXEC.UNLOCK • To Release the Record which has been locked by READ with UPDATE Command. Condition: DISABLED.

SYSIDERR. FILENOTFOUND. NOTAUTH.General Exceptions • The following exceptions usually will occur for ALL CICS file handling commands. INVREQ 107 .

CICS Error Handling Procedures 108 .

• Conditions caused by user errors and input data errors. 109 .Error Handling in CICS Possible Errors: • Conditions that aren't normal from CICS's point of view but that are expected in the program. generation parameters and JCL • Errors related to hardware or other system conditions beyond the control of an application program. • Errors caused by mismatches between applications and CICS tables. • Conditions caused by omissions or errors in the application code.

Control goes to a label in the program defined earlier by a HANDLE CONDITION command.Control returns to the next inst.System will terminate or suspend the task depends on the exceptional condition occurred 110 . the program can do any of the following • Take no action & let the program continue . • Rely on the system default action . following the command that has failed to execute.Error Handling methods When the error (exceptional conditions) occur. A return code is set in EIBRESP and EIBRCODE. This state occurs „cause of NO HANDLE /RESP/IGNORE conditions • Pass control to a specified label .

Error Handling methods (Contd. LENGERR will be handled by system 111 . 'condition' specifies the name of the condition. and 'label' specifies the location within the program to be branched • Remains active while the program is executing or until it encounters IGNORE/another HANDLE condition..) • HANDLE CONDITION condition[(label)]. all the other Errors together.. • Syntax : EXEC CICS HANDLE CONDITION ERROR(ERRHANDL) LENGERR(LENGRTN) END-EXEC This example handles DUPREC condition separately..

112 .FOUND paragraph in the program. The error handling logic can be coded in the REC-NOT-FND paragraph.HANDLE Condition Example of Handle condition: EXEC CICS HANDLE CONDITION NOTFND(RECORD-NOT-FOUND) END-EXEC This condition catches the NOTFND condition and transfers control to the REC-NOT.

Later.. If xxx=DFHRESP(NOSPACE) . 113 .. or If xxx=DFHRESP(NORMAL) ..Alternative to Handle condition • NOHANDLE to specify “no action to be taken for any condition or attention identifier (AID) “ • RESP(xxx) "xxx" is a user-defined full word binary data area. it can be tested by means of DFHRESP as follows.. On return from the command. it contains a return code.

.IGNORE Condition • IGNORE CONDITION condition . • „condition‟ specifies the name of the condition that is to be ignored( no action will be taken) • Syntax : EXEC CICS IGNORE CONDITION ITEMERR LENGERR END-EXEC • This command will not take any actions if the given two error occurs and will pass the control to the next instruction 114 ..

: EXEC CICS READ DATASET(SAMPLE) RIDFLD(EMP-NO) INTO (EMP-REC) END-EXEC : GO TO LAST-PART 115 .Sample program to use Handle condition Here is an example of the CICS.COBOL code with proper handling of errors Procedure Division. EXEC CICS HANDLE CONDITION NOT-FND(REC-NOT-FOUND) END EXEC.

.) REC-NOT-FOUND MOVE „NOT-ON-FILE‟ TO NAMEO ( SYMBOLIC MAP PARAMETER) LAST-PART. EXEC CICS SEND MAP („TC0BM31‟) MAPSET(„TC0BM30‟) FROM („TC0BM310‟) DATA-ONLY END-EXEC 116 .Sample program to use Handle condition (Contd.

117 . HANDLE AID and HANDLE ABEND commands. while calling sub-pgms (CALL). a sub-program can suspend Handle commands of the called program using PUSH HANDLE. IGNORE CONDITION. it can restore the Handle command using POP HANDLE. • Used for eg.PUSH & POP • To suspend all current HANDLE CONDITION. • While returning the control. • While receiving the control.

• Syntax of Pop : EXEC CICS Pop Handle END-EXEC. 118 .Syntax of Push & Pop • Syntax of Push : EXEC CICS Push Handle END-EXEC.

EXEC Interface Block (EIB) • CICS provides some system-related information to each task as EXEC Interface Block (EIB) • Unique to the CICS command level EIBAID Attention.Id (1 Byte) EIBCALEN Length of DFHCOMMAREA (S9(4) comp) EIBDATE Date when this task started (S9(7) comp-3) EIBFN Function Code of the last command ( 2 Bytes) EIBRCODE Response Code of the last command (6 Bytes) EIBTASKN Task number of this task (S9(7) comp-3) EIBTIME Time when this task started (S9(7) comp-3) EIBTRMID Terminal-Id (1 to 4 chars) EIBTRNID Transaction-Id (1 to 4 chars) 119 .

DFHPPT TYPE=ENTRY.PROGRAM=TEST.PPT DFHPPT TYPE=ENTRY PROGRAM |MAPSET= name [PGMLANG= ASM|COBOL|PLI] [RES= NO|FIX|YES] : : other options : Eg.Processing Program Table . PGMLANG=COBOL 120 .

PCT Entry
DFHPCT TYPE=ENTRY TRANSID= name PROGRAM=name TASKREQ=pf6 RESTART=yes/no ( TRANSEC = 1 to 64) RSLKEY= 1 to 24 resource level key SCTYKEY= 1 to 64 security key : : other options

121

PROGRAM CONTROL
122

Program Control Commands
• LINK • XCTL • RETURN • LOAD • RELEASE

123

LINK • Used to pass control from one application program to another • The calling program expects control to be returned to it • Data can be passed to the called program using COMMAREA • If the called program is not already in main storage it is loaded 124 .

NOTAUTH. LENGERR 125 .LINK Syntax EXEC CICS LINK PROGRAM(name) [COMMAREA(data-area) [LENGTH(data-value)]] END-EXEC. Conditions : PGMIDERR.

XCTL • To transfer control from one application program to another in the same logical level • The program from which control is transferred is released • Data can be passed to the called program using COMMAREA • If the called program is not already in main storage it is loaded 126 .

LENGERR 127 . Conditions : PGMIDERR.XCTL Syntax EXEC CICS XCTL PROGRAM(name) [COMMAREA(data-area) [LENGTH(data-value)]] END-EXEC. NOTAUTH.

RETURN • To return control from one application program to another at a higher logical level or to CICS • Data can be passed using COMMAREA when returning to CICS to the next task 128 .

Conditions : INVREQ. LENGERR 129 .RETURN Syntax EXEC CICS RETURN [TRANSID(name) [COMMAREA(data-area) [LENGTH(data-value)]]] END-EXEC.

CICS PROG A LINK RETURN PROG C LINK RETURN Level 0 Level 1 PROG B XCTL Level 2 Level 3 Application Program Logic Levels PROG D XCTL PROG E RETURN 130 .

Condition : NOTAUTH.LOAD • To load program/table/map from the CICS DFHRPL concatenation library into the main storage • Using load reduces system overhead • Syntax : EXEC CICS Load Program(name) [SET (pointer-ref)] [LENGTH (data-area)] END-EXEC. PGMIDER 131 .

INVREQ 132 . NOTAUTH.RELEASE • To RELEASE a loaded program/table/map • Syntax : EXEC CICS RELEASE PROGRAM(name) END-EXEC. Conditions : PGMIDERR.

Linkage section definition under DFHCOMMAREA • Called program can alter data and this will automatically available in calling program after the RETURN command ( need not use COMMAREA option in the return for this purpose ) • EIBCALEN is set when COMMAREA is passed 133 .Working Storage definition • Called program .COMMAREA • Data passed to called program using COMMAREA in LINK and XCTL • Calling program .

Communication With Databases
134

CICS - DB2
• CICS provides interface to DB2. • DB2 requires “CICS Attachment Facility” to connect itself to CICS • CICS programs can issue commands for SQL services in order to access the DB2 database.
EXEC SQL function [options] END-EXEC

135

Operating system

CICS REGION

DB2

REGION

App. Pgm. EXEC SQL..

CICS Attachment Facility

DB2 Database

DB2 Database access by CICS
136

• The RCT must be link-edited into a library that is accessible to MVS 137 .RCT Entry • The CICS-to-DB2 connection is defined by creating and assembling the resource control table (RCT) • The information in RCT is used to control the interactions between CICS & DB2 resources • DB2 attachment facility provides a macro (DSNCRCT) to generate the RCT.

DB2 - Precompiler
Source Program (EXEC SQL...
| EXEC CICS...) DB2 Precompiler | CICS command translator | Compile By COBOL | Linkedit by Linkage editor | Load Module
138

QUEUES
139

Transient data Control
• Provides application programmer with a queuing facility • Data can be stored/queued for subsequent internal or external processing • Stored data can be routed to symbolic destinations • TDQs require a DCT entry • Identified by Destination id - 1 to 4 bytes

140

statistics.Tape.association external to the CICS subsystem. Printer etc Typical uses are .Create files for subsequent processing by Non-CICS / Batch programs.Message switching .Broadcasting etc • Extra-partitioned .ATI (Automatic Task Initiation) associated with trigger level . transaction error messages .Logging data. Can associate with any sequential device .association within the same CICS subsystem Typical uses are .TDQs • Intra-partitioned . DASD. 141 .

142 .TDQs • Operations Write data to a transient data queue (WRITEQ TD) Read data from a transient data queue (READQ TD) Delete an intra partition transient data queue (DELETEQ TD).

SYSIDERR 143 . LENGERR. NOTOPEN. Conditions: DISABLED. IOERR. QIDERR. NOSPACE. NOTAUTH. INVREQ. ISCINVREQ.WRITEQ TD • Syntax : EXEC CICS WRITEQ TD QUEUE(name) FROM(data-area) [LENGTH(data-value)] [SYSID(systemname)] END-EXEC.

LENGERR.READQ TD • Reads the queue destructively . • Syntax : EXEC CICS READQ TD QUEUE(name) {INTO(data-area) | SET(ptr-ref) } [LENGTH(data-value)] [NOSUSPEND] END-EXEC.Data record not available in the queue after the read. NOTOPEN. IOERR. INVREQ. Conditions : DISABLED. QBUSY. NOTAUTH. SYSIDERR 144 . QZERO. ISCINVREQ. QIDERR.

SYSIDERR 145 .DELETEQ TD • Deletes all entries in the queue • Syntax : EXEC CICS DELETEQ TD QUEUE(name) END-EXEC. QIDERR. NOTAUTH. Conditions: INVREQ. ISCINVREQ.

Destination Control Table • DCT is to register the information of all TDQs • Destination Control Program (DCP) uses DCT to identify all TDQs and perform all I/O operations. 146 . • DFHDCT is a macro to define intra & extra partition TDQs TYPE=INTRA/EXTRA • REUSE option specified along with intra partition TDQ tells whether the space used by TDQ record will be removed & reused after it has been read.

the transaction MSW1 will be initiated automatically • Applications Message switching & Report printing 147 .Automatic Task Initiation • Facility through which a CICS transaction can be initiated automatically DFHDCT TYPE=INTRA DESTID=MSGS TRANSID=MSW1 TRIGLEV=500 When the number of TDQ records reaches 500.

called the item number 148 .No CICS table entry required if recovery not required .Typically a combination of termid/tranid/operid • Each record in TSQ identified by relative position.Created and deleted dynamically .Temporary Storage Control • Provides application programmer the ability to store and retrieve data in a TSQ • Application can use the TSQ like a scratch pad • TSQs are .Identified by Queue id .1 to 8 bytes .

VSAM file DFHTEMP 149 .Recoverable – TST entry required.TSQs • Operations – Write and Update data – Read data .Non-recoverable – Auxiliary .Sequential and random – Delete the queue • Access – Across transactions – Across terminals • Storage – Main .

TSQs .Typical uses • Data passing among transactions • Terminal Paging • Report printing 150 .

SYSIDERR. Conditions : ITEMERR. INVREQ. NOTAUTH. ISCINVREQ 151 . IOERR. NOSPACE. QIDERR. LENGERR.WRITEQ TS • Syntax : EXEC CICS WRITEQ TS QUEUE(name) FROM(data-area) [LENGTH(data-value)] [NUMITEMS(data-area) | ITEM(data-area) [REWRITE] ] [MAIN|AUXILIARY] [NOSUSPEND] END-EXEC.

Conditions : ITEMERR. SYSIDERR. NOTAUTH. ISCINVREQ 152 . LENGERR. INVREQ. QIDERR.READQ TS • Syntax : EXEC CICS READQ TS QUEUE(name) {INTO(data-area) | SET(ptr-ref) } LENGTH(data-value) [NUMITEMS(data-area)] [ITEM(data-area) | NEXT ] END-EXEC. IOERR.

Conditions: INVREQ. QIDERR.DELETEQ TS • Deletes all entries in the queue • Syntax : EXEC CICS DELETEQ TS QUEUE(name) END-EXEC. ISCINVREQ. NOTAUTH. SYSIDERR 153 .

INTERVAL & TASK CONTROL 154 .

ASKTIME • Used to obtain current date and time • Syntax : EXEC CICS ASKTIME[ABSTIME(data-area)] END-EXEC. • EIBDATE and EIBTIME updated with current date and time • ABSTIME returns value of time in packed decimal format 155 .

... [DATE(data-area) [DATEFORM[(data-area)]]] [DATESEP[(data-value)]] [DAYOFMONTH(data-area)] [MONTHOFYEAR(data-area)] [YEAR(data-area)]. Condition: INVREQ 156 ... etc..FORMATTIME • Syntax : EXEC CICS FORMATTIME ABSTIME(data-ref) [YYDDD(data-area)] [YYMMDD(data-area)]. [TIME(data-area) [TIMESEP[(data-value)]]] END-EXEC.

INVREQ 157 .DELAY • Used to DELAY the processing of a task • The issuing task is suspended for a specified interval or Until the specified time • Syntax : EXEC CICS DELAY INTERVAL(hhmmss) | TIME(hhmmss) END-EXEC Conditions: EXPIRED.

TRANSIDERR 158 .TERMIDERR. LENGERR.START • Used to start a transaction at the specified terminal and at the specified time or interval • Data can be passed to the new transaction • Syntax : EXEC CICS START TRANSID(transid) [TERMID(termid) TIME(hhmmss) | INTERVAL(hhmmss) ] END-EXEC Conditions : INVREQ.

Used to retrieve the data passed by the START • CANCEL -Used to cancel the Interval Control requests. eg. • RETRIEVE .to wait for an event to occur.to request notification when the specified time has expired.to free the exclusive control from the resource gained by ENQ 159 . DELAY.Used to suspend a task • ENQ .to gain exclusive control over a resource • DNQ .Other Interval Control Commands • POST . • WAIT EVENT . • SUSPEND .POST and START identified by REQID.

Recovery & Restart 160 .

The Need for Recovery/Restart • The possible failures that can occur outside the CICS system are Communication failures (in online systems) Data set or database failures Application or system program failures Processor failures & Power supply failures. eliminate the damage done to the online system. 161 . • Recovery/Restart facilities are required to minimize or if possible. in case of the above failures to maintain the system & data integrity.

RECOVERY • An attempt to come back to where the CICS system or the transaction was when the failure occurred • Recoverable Resources VSAM files Intrapartition TDQ TSQ in the auxiliary storage DATA tables Resource definitions & System definition files 162 .

RESTART • To resume the operation of the CICS system or the transaction when the recovery is completed 163 .

Facilities for Recovery/Restart Facilities for CICS Recovery/Restart • • • • • • Dynamic Transaction Backout Automatic Transaction Restart Resource Recovery Using System Log Resource Recovery Using Journal System Restart Extended Recovery Facility (XRF) 164 .

CICS automatically recovers all recoverable resources using the info.Dynamic Transaction Backout (DTB) • When the transaction fails. backing out the changes made by the transaction while the rest of the CICS system continues normally is called DTB • CICS automatically writes the „before image‟ information of the record into the dynamic log for the duration of one LUW . in dynamic log (Set DTB=YES in PCT) 165 .the work between the two consecutive SYNC points • When an ABEND occurs.

LUW & SYNC point • The period between the start of a particular set of changes and the point at which they are complete is called a logical unit of work . can be done by • Syntax : EXEC CICS SYNCPOINT [ROLLBACK] END-EXEC 166 .LUW • The end of a logical unit of work is indicated to CICS by a synchronization point (sync pt). • Intermediate SYNC pt.

.|....LUW.......| Task B|---------------->--------------->--------------| SOT SP SP EOT-SP When the failure occurs. 167 .LUW .. changes made within the abending LUW will be backed out...LUW..| Task A|---------------------------------------------| SOT EOT-SP |...-LUW.LUWs & SYNC pts |............|.

set RESTART=YES in PCT • Care should be taken in order to restart the task at the point where DTB completes in the case of intermediate SYNC point 168 .Automatic Transaction Restart • CICS capability to automatically restart a transaction after all resources are recovered through DTB • If the transaction requires automatic restart facility.

Program Preparation 169 .

• Executing the Program. • Defining the Program in the CICS Region. 170 .Introduction • Preparing a Program to run in CICS Environment.

Program preparation IF DB2 : SOURCE DB2 PRECOMPILER CICS COMPILER COBOL COMPILER LOAD MODULE LINK EDIT 171 .

• Assemble or Compile the Translator Output. 172 .Preparing a Program CICS requires the following steps to prepare a program • Translating the Program. & • Link the Program.

• The SYSPUNCH is given as the input to the Program Compiler. • If any Copy Books are used in the Program. • The Translator gives two outputs. a Program Listing as SYSPRINT and a Translated Source in SYSPUNCH.Translation • Translates the „EXEC CICS‟ Statements into the Statements your Language (COBOL) Compiler can Understand. 173 . there should not be any CICS Statements in the Copy Book.

the compiler options can be specified as required. • Hence.Compiling or Linking • As the CICS Commands have been translated. the compilation of the CICS program is the same as language program. 174 .

175 . • This can be done either by using CEDA trans or DFHPPT.Defining the Program • The Application should be defined and installed into the PPT.

CICS Supplied Transactions 176 .

CESN/CESF Transactions • To sign on to CICS system • CESN [USERID=userid] [. • In RACF. the previous operator will be signed off 177 .LANGUAGE=l] • Userid & password values can be from 1-8 chars. • NEWPS to change the password and LANGUAGE to choose national language • Sign off by CESF which breaks the connection between the user and CICS • If the Sign on is done twice for the same userid at the terminal. the Userid given in CESN is verified.NEWPS=newpassword][.PS=password] [.

terminal id. • CECI READQ TD QUEUE(TESTL001) will read the current record of the given TDQ 178 .Command Level Interpreter • To build and test the effect of EXEC CICS commands • CECI ASSIGN is used to get the current userid. application id etc. • CECI gives the complete command syntax of the specified command.CECI .sysid.. • Before using the maps in programs. it can be tested using CECI to check how it appears on the screen.

CEMT-Master Terminal Transaction CEMT provides the following services • • • • Displays the status of CICS & system resources Alter the status of CICS & system resources Remove the installed resource definitions Perform few functions that are not related to resources 179 .

To test/monitor a transaction attached across an MRO/ISC session • Sysid .ON/.the identifier of the terminal on which the transaction to be tested is being run • Sessionid .CEDF-Execution Diagnostic Facility • To test command level application programs interactively • CEDF [termid/sysid/sessionid] [.To test a transaction across an APPC session 180 .OFF] • Termid .

• EIB values can be changed.) The points at which EDF interrupts execution of the program and sends a display to the terminal • At transaction initialization. pgm given control • Start of execution of each CICS command (auguement values can be changed at this point) • End of execution of each CICS command and before the Handle condition mechanism is invoked (response code values can be changed) • At program termination & at normal task termination • When an ABEND occurs & at abnormal task termination.& CEBR can be invoked 181 .CEDF (Contd. after EIB has been initialized and before the app...

CEBR-Temporary Storage Browse • To browse the contents of CICS temporary storage queues (TSQ) • CEBR by default will show the queue associated with the current terminal „CEBRL001‟ which can be overridden to view any other queue • TERM to browse TSQ for another terminal • QUEUE to make the named queue. current • PUT to copy the current queue contents into TDQ • GET to fetch TDQ for browsing • PURGE erases the contents of the current queue 182 .

Exercise .2 183 .

Thank You 184 .

Sign up to vote on this title
UsefulNot useful