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

4. 3. 6. special recovery/restart proc. 6. 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. 5. 2. 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. Usually in seconds 4 . 3. 5. ONLINE SYSTEM Data is entered as needed not in sequence (terminal) Since processing sequence is unpredictable. 2. 4.Batch & Online : Differences 1. 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.

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 .

An entity which initiates execution of a task. 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 :. transaction is identified by the transaction identifier (Trans-id) 8 .

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

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 .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 significant amount of resource will be wasted just waiting • Pseudo-Conversational.

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

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

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. Eg. Task Control Area contains information about the task 13 .CICS Components • Control Programs (or Management Modules) Programs that interface between OS and app.

Control Table PPT FCT TCT PCT TST DCT 14 . Storage Table Destin.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.

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

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

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

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

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 .

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

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

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

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

Map and Mapset (Contd.g.. For e. MAPSET2 MAPNUM1 MAPNUM2 28 . For e.g. MAPSET1 MAPNUM1 Case 2: A mapset consists of several maps.) 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 FILLER PIC X(12). 02 FILLER PIC X(03). 02 EMPNAF PIC X. 30 . 02 EMPNAL PIC S9(4) COMP.Example – Symbolic Map 01 EMPRECI. 02 EMPNAO PIC X(21). 01 EMPRECO REDEFINES EMPRECI. 03 EMPNAA PIC X. 02 FILLER REDEFINES EMPNAF. 02 EMPNAI PIC X(21). 02 FILLER PIC X(12).

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

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

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

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

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

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

) 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. 39 .DFHMSD Macro (Contd..

Required for the CICS command level..DFHMSD Macro (Contd. 40 .) 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.

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 .

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

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

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. FSET Field set. In case. NORM Normal display. 47 .Attribute character (Contd.) BRT Bright display of a field (highlight). IC is specified more than once. The cursor will be positioned in this field. the cursor is placed in the last field. Insert cursor.. DRK IC Dark display.

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

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

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

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

this is required by the BMS under the CICS command level. 52 . • 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. • Next is the definition of FILLER PIC X(12). which is the TIOA prefix created by the TIOAPFX=YES of the DFHMSD macro. 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.

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

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

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

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

. fieldname + L) for the field where the cursor is to be placed.) • Dynamic/Symbolic Positioning. Also. 57 .e.Cursor Positioning Techniques (Contd. The SEND MAP command must be issued with the CURSOR option (without value). 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. The cursor is placed dynamically through an application program by moving -1 to the symbolic map field-length field (i. the mapset should be coded with MODE=INOUT in the DFHMSD macro.

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

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

.) 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. overriding the static cursor position defined at the map definition time.Cursor Positioning Techniques (Contd. 60 . the map will be displayed with the cursor placed at the specified position. At the completion of the SEND MAP command.

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

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

.) Flow of Information from 3270 Terminal and the Application Program.Interfacing with a Terminal using a Map (Contd. 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.) 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 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. At the completion of the command. : The Flag Byte which is normally X‟00‟. which contains the actual number of characters. : The actual input data field. Field name + F Field name + I 65 . typed in the screen field. X‟00‟ will be placed if no data is entered. It will be X‟80‟ if the field has been modified but cleared.Receive Map Command RECEIVE MAP Command is used to receive input from a terminal.

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

MAPSET specified the name of the MAPSET defined thru DFHMSD command which includes the MAP. 67 .) 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.Receive Map Command (Contd. INTO is used to specify the area in the working storage section to which the data from the terminal is to be placed.. which describes the screen details.

MAPFAIL MAPFAIL is set when the data being mapped has a length of zero. 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.) RESP will be used by CICS to place a response code at a completion of the command. 68 . INVREQR ..Receive Map Command (Contd. Conditions : INVMPSZ . NOHANDLE will cause no action to be taken for any exceptional condition occurring during execution of the CICS command. LENGERR.

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

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

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

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

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

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

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

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

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

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

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

1 80 .Exercise .

CICS File Processing Techniques 81 .

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

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

key) END-EXEC.CICS COBOL V/S COBOL BATCH COBOL CICS COBOL EXEC CICS READ DATASET (‘FILE IDENTIFIER) INTO (RECORD NAME) RID-FLD (record-key) END-EXEC. 84 . 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.

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

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

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

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

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

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

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

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 .

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

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

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

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

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

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

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

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

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

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

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

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

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

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

CICS Error Handling Procedures 108 .

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

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

LENGERR will be handled by system 111 ... • Syntax : EXEC CICS HANDLE CONDITION ERROR(ERRHANDL) LENGERR(LENGRTN) END-EXEC This example handles DUPREC condition separately. 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. 'condition' specifies the name of the condition.Error Handling methods (Contd. all the other Errors together..) • HANDLE CONDITION condition[(label)].

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.. it can be tested by means of DFHRESP as follows.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 contains a return code. or If xxx=DFHRESP(NORMAL) . 113 . If xxx=DFHRESP(NOSPACE) . On return from the command.

. • „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 ..IGNORE Condition • IGNORE CONDITION condition .

COBOL code with proper handling of errors Procedure Division. EXEC CICS HANDLE CONDITION NOT-FND(REC-NOT-FOUND) END EXEC. : 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.

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

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

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

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 .

PROGRAM=TEST. DFHPPT TYPE=ENTRY.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 .

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

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 .

XCTL Syntax EXEC CICS XCTL PROGRAM(name) [COMMAREA(data-area) [LENGTH(data-value)]] END-EXEC. LENGERR 127 . Conditions : PGMIDERR. 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.RETURN Syntax EXEC CICS RETURN [TRANSID(name) [COMMAREA(data-area) [LENGTH(data-value)]]] END-EXEC. LENGERR 129 .

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 .

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 . Condition : NOTAUTH.

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

COMMAREA • Data passed to called program using COMMAREA in LINK and XCTL • Calling program .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 .

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

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. • The RCT must be link-edited into a library that is accessible to MVS 137 .

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

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

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

QZERO. IOERR.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. NOTOPEN. ISCINVREQ. INVREQ.Data record not available in the queue after the read. QIDERR. LENGERR. NOTAUTH. QBUSY. SYSIDERR 144 . Conditions : DISABLED.

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

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.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.

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. the transaction MSW1 will be initiated automatically • Applications Message switching & Report printing 147 .

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 .No CICS table entry required if recovery not required .1 to 8 bytes .Created and deleted dynamically .Typically a combination of termid/tranid/operid • Each record in TSQ identified by relative position.Identified by Queue id . called the item number 148 .

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

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

Conditions : ITEMERR. SYSIDERR. IOERR.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. NOTAUTH. LENGERR. INVREQ. QIDERR. ISCINVREQ 151 . NOSPACE.

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. Conditions : ITEMERR. NOTAUTH. QIDERR. INVREQ. LENGERR. IOERR. SYSIDERR. ISCINVREQ 152 .

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

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)]... [TIME(data-area) [TIMESEP[(data-value)]]] END-EXEC. Condition: INVREQ 156 .FORMATTIME • Syntax : EXEC CICS FORMATTIME ABSTIME(data-ref) [YYDDD(data-area)] [YYMMDD(data-area)].. etc..

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. INVREQ 157 .

TERMIDERR. TRANSIDERR 158 . 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.

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

Recovery & Restart 160 .

eliminate the damage done to the online system. • Recovery/Restart facilities are required to minimize or if possible. in case of the above failures to maintain the system & data integrity. 161 .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.

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 .

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 .the work between the two consecutive SYNC points • When an ABEND occurs. in dynamic log (Set DTB=YES in PCT) 165 . CICS automatically recovers all recoverable resources using the info.

• Intermediate SYNC pt.LUW • The end of a logical unit of work is indicated to CICS by a synchronization point (sync pt).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.......... 167 .......|....LUWs & SYNC pts |...| Task B|---------------->--------------->--------------| SOT SP SP EOT-SP When the failure occurs. changes made within the abending LUW will be backed out.| Task A|---------------------------------------------| SOT EOT-SP |..LUW ....|.LUW.-LUW....

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 .

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

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

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

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

Compiling or Linking • As the CICS Commands have been translated. the compilation of the CICS program is the same as language program. the compiler options can be specified as required. • Hence. 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 .

the previous operator will be signed off 177 .LANGUAGE=l] • Userid & password values can be from 1-8 chars.NEWPS=newpassword][.CESN/CESF Transactions • To sign on to CICS system • CESN [USERID=userid] [.PS=password] [. • 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. • In RACF.

• CECI gives the complete command syntax of the specified command.sysid.CECI .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. • Before using the maps in programs.. terminal id. • CECI READQ TD QUEUE(TESTL001) will read the current record of the given TDQ 178 . 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 .

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 .To test/monitor a transaction attached across an MRO/ISC session • Sysid .OFF] • Termid .ON/.

CEDF (Contd. after EIB has been initialized and before the app. 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 ..) The points at which EDF interrupts execution of the program and sends a display to the terminal • At transaction initialization.. • EIB values can be changed.

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 .

2 183 .Exercise .

Thank You 184 .

Sign up to vote on this title
UsefulNot useful