START is used to start a new task. It is a interval control command. XCTL is used to pass control to a program within the same task. It is a program control command.
Minimum, Standard, FULL
To provide the control and services of the DB/DC system
In COBOL II start with CEBR, and get the offset/instruction.
Language interface and call parameters
Check EIBRESP after the call or use the HANDLE condition.
Yes, the called routine must be defined in PPT and the calling program must use CALL identifier...
EIBRESP, EIBCALEN, EIBRRCDE, EIBTASK, EIBDATE, EIBTIME
Used by STARTed tasks to get the parameters passed to them.
DB2/IDMS not up.
Any data exception problem SOC7, SOC4 etc.
Task control commands to make resources serially reusable.
Destination Control Table used define TDQs
MDT: Bit in the attribute byte indicating modification of field on screen. Happens on an input operation.
FSET: Sets MDT on to ensure field is transmitted. Happens on an output operation
FRSET: Reset MDT. Until this happens, field continues to be sent.
Defines the display/transmission of field. Most cases is an output field from the program.
The physical map is the load module and the symbolic map is the data structure.
SYMBOLIC MAP IS USED BY USER AND PHYSICAL MAP IS USED BY SYSTEM
Stop run will come out from the CICS region.
Pseudo-conversational transactions are almost always the preferred method. In these mode CICS releases resources between responses to user input, i.e. the task is ended awaiting the user response.
25. DB2 What is the difference between a package and a plan. How does one bind 2 versions of a CICS transaction with the same module name in two different CICS regions that share the same DB2 subsystem?
Package and plan are usually used synonymously, as in this site. Both contain optimized code for SQL statements - a package for a single program, module or subroutine contained in the database request module (DBRM) library. A plan may contain multiple packages and pointers to package that could be referenced in two different plans.
The ABEND command forces a task to end abnormally. It creates a transaction dump and invokes the dynamic transaction backout.
The LOAD command retrieves an object program from disk and loads it into main storage - it's primarily used for a constant table that will be available system-wide.
Task control refers to the CICS functions that manage the execution of tasks. Task control commands are SUSPEND, ENQ, and DEQ.
CICS interval control provides a variety of time-related features - common commands are ASKTIME, PORMATTIME, START, RETRIEVE, and CANCEL.
You can't at least not directly. Options, none of them good, inlude:
I. adding a logical-delete flag to the contents of each item;
II. moving item 4 to 3 and 5 to 4 and initializing item 5, all thru rewrites; this is a variant on 1;
III. Creating a new 'copy' TSQ that excludes the unwanted item, killing the old TSQ (deleteq ts). writing the new TSQ with the original name from the new TSQ, and then deleting the 'copy' TSQ. This way, you will get an accurate report from NUMITEMS.
Neither command is exclusively a transient data command. The ENQ command reserves any user defined resource for the specific task. For enqueued transient data no other task will be able to write records to it for as long as it is enqueued. DEQ removes the lock.
A logical message is a single unit of output created by SEND TEXT or SEND MAP commands
BMS collects the separate output from each command and treats them as one entity.
This technique may be used to build CICS reports.
CEBR lets you browse the contents of a specific temorary storage queue.
CEDF is the execute diagnostic facility that can be used for debugging CICS programs.
CECI is the command level interpreter transid that interactively executes CICS commands. It is a rudimentary CICS command debugger which does not require coding an entire program.
RDO is Resource Definition Online. Since release 1.6 RDO allows resources (terminals, programs, transactions and files) to be defined interactively while CICS is running.
A cursor is a pointer that identifies one row in a SQL results table as the current row.
MASSINSERT is a WRITE option that modifies normal VSAM split processing, leaving free space after the inserted record, so subsequent records can be inserted without splits. it is ended by an UNLOCK command
SYNCPOINT without the ROLLBACK option makes all updates to protected resources permanent, with the ROLLBACK option it reverses all updates.
Journal Recovery is recovery of changes made to a file during online processing. If a file has I/O problems it is restored from a backup taken before online processing began and the journalled changes are applied. Dynamic transaction backout is the removal of partial changes made by a failed transaction.
They are defined in the destination control table (DCT).
They are intrapartition, which can only be accessed from with CICS and extrapartition, which are typically used to collect data online, but process it in a batch environment.
Transient data provides CICS program with a simple method for sequential processing, often used to produce output for 3270 printers
Temporary storage is either main or auiliary storage that allows the program to save data between task invocations.
An ASRA is the CICS interrupt code, the equivalent of an MVS abend code.
It's controlled by the cursor option of the SEND MAP command using a direct (0 through 1919) or symbolic value.
EIBAID is a key field in the execute interface block; it indicates which attention key the user presse to initiate the task.
In COBOL storage was accessed via BLL cell using the SET option of ADDRESS commands. In COBOL II the special register. ADDRESS OF lets you reference the address of any Linkage Section field.
To fetch a program, table or map to the main storage.
Data files and data bases, Intrapartition TDQs, Auxiliary TSQs
To register all programs and maps
Terminal Control Program
Low level version of CICS macro level
In case of call, whenever you do changes to the called program you need to compile the calling program also. In case of link, it is not needed.
Both are used to save data among tasks. but
1. COMMAREA is private to that transaction only like every transaction has its own COMMAREA created by CICS as soon as the transaction is initiated. however TSQ, if queue id is known can be accessed by other transactions also
2. COMMAREA length is s9(4) comp i.e. 65k. but TSQ can have any length
3. COMMAREA is available only during the transaction is running. TSQ if created with auxiliary option resides in aux memory and available even if main memory crashes
4. normally COMMAREA is used to transfer data from one task to another while TSQ is used widely within the task as a scratch pad.
Communication Area is used to pass data between the program or between the task.
A). Alink was issued to a program whose name does not exist in the PPT (Program Processing Table
B) A program attempted to use a map that is not defined in the PCT ( Program Control Table).
C) A security violation has occurred. The operator is not defined with the proper authority in the SNT ( Sign on Table ) to use a particular file
D) A program interrupt (0C0 or 0C2 ot ...) has occurred in a CICS program
E) An I/O error has occurred when attempting to use a VSAM file from a CICS program
D) A program interrupt (0C0 or 0C2 ot ...) has occurred in a CICS program
U-for unconditional breakpoint, C-for conditional breakpoint, and A-for automatic breakpoint
There are six ways in initiating a transaction they are as follows.
1. embedding four character transid on the top left most corner of the screen.
2. making use of EXEC CICS START TRANSID()
3. making use of EXEC CICS RETURN TRANSID()
4. By defining the transid in DCT ( destination control table ) to enable ATI ( AUTOMATIC TASK INITIATION)
5. Making use of PLT ( program list table )
6. By associating four character transid in PCT ( program control table )
Intrapartition TDQ is read destructive. extra partition TDQ is not read destructive.
This is the error code for length, if length of the source data is more than the receiving field, This error will occur.
The default commarea size is 65k.
It occurs when program interruption takes place. e.g. when alphanumeric string moved to numeric data item OR when arithmetic calculations performed on nunnumeric data item OR when an attempt made to read an occurrence of a table beyond the defined occurrences.
This occurs when a programmer Issues a EXEC CICS Syncpoint command. this is called two phase because CICS will first commit changes to the resources under its control like VSAM files, and the DB2 changes are committed. Usually CICS signal DB2 to complete the next phase and release all the locks.
TDQ is read destructive, TSQ is not, TSQ can be created dynamically, TDQ cannot be created dynamically. TSQ is temporary in nature (i.e. it will be deleted when the program finishes execution, unless it is made permanent by making a entry in the Temporary Storage Table), TDQ is not.
You have to explicitly specify the word CURSOR between your EXEC CICS and END-EXEC in the program.
The EIB is the EXECUTIVE INTERFACE BLOCK. It is not the EXECUTE INTERFACE BLOCK. All TP monitors or transaction processor are know as EXECUTIVEs as they carry out process on behalf of a program module. CICS and DB2 are executives.
Max. of 12 exceptional conditions can be given in a HANDLE CONDITION.
By specifying the ITEM option
READQ TD, the read is destructive.
We can initiate CICS transaction
a) by giving transaction id
b) by giving CICS start command
c) automatic task initiation
The XCTL command passes control to another program, but the resources requested by the first program may still be allocated. A task does not end until a RETURN statement is executed. While in LINK command, program control resumes its instruction following the LINK parameter. The disadvantage of LINK is that it requires that both the calling program and the called program remain in main memory even though both are no longer needed.
PCT contains a list of valid transaction ID. Each transaction ID is paired with the name of the program, CICS will load and execute when the transaction is invoked. On the other hand, PPT indicates each program's location which pertains to a storage address if the program has already been loaded or a disk location if the program hasn't been loaded. PPT will also be used to detemine whether it will load a new copy of the program when the transaction is invoked.
The first way is to code a physical map and then code a matching symbolic map in your COBOL program. The second way to create a physical map along with a matching symbolic map is to code only the physical map using the and SYSPARM option, CICS will automatically create a member in a COPY library. And the third way is to use a map generator such as SDF ( Screen Definition Facility )
There are times when many users are concurrently using the same program, this is what we call MultiThreading, For example, 50 users are using program A, CICS will provide 50 Working storage for that program but one Procedure Dividion. And this technique is known as quasi-reentrancy
The physical mapset is a load module used to map the data to the screen at execution time. The symbolic map is the actual copybook member used in the program to reference the input and output fields on the screen.
COMMONAREA, TSQ and TDQ.
By issuing a REWRITE, DELETE, or UNLOCK command or by ending the task.
In RETURN with TRANSID the control goes to the CICS region and the user have to transfer the control to program B by pressing any of the AID KEYS. In XCTL the control is directly transfer to program B.
The length will be 0 (zero).
DFHEIBLK is Execute Interface Block. It is placed in the linkage section automatically by CICS translator program.
It must be the first entry in linkage section. CICS places values prior to giving control to the program and we can find almost any information about our transaction.
The LINK command anticipates return of control to the calling program, the XCTL command does not. RETURN to the calling program will be the result of the CICS RETURN command, specifying TRANSID (name of the calling program)
First issue a STARTBR (start browse), which will position the browse at the desired record. Retrieve records by using subsequent READNEXT commands. Indicate the end of sequential processing with the ENDBR command. If the generic key is specified in the STARTBR command position in the file will be before the first record satisfying the generic key. For reading in descending order use the READPREV instead of READNEXT.
pseudo-conversational will start a new task for each input. By coding a CICS RETURN command specifying TRANSID9ITSELF). Conversational will have an active task during the duration of the data entry.
An area used to transfer data between different programs or between subsequent executions of the same program. Needs to be defined in the LINKAGE Section.
The common work area is a storage area that can be accessed by any task in a CICS system.
Transid is a transaction identifier, a four character code used to invoke a CICS task. CEMT is the master terminal transaction that lets you display and change the status of resources - it is the primary CICS service transaction.
The modified data tag is the last bit in the attribute byte for each screen field. It indicates whether the corresponding field has been changed.
The execute interface block lets the program communicate with the execute interface program, which processes CICS commands. It contains terminal id, time of day and response codes.
The common systems area is the major CICS control block that contains system information, including pointers to most other CICS control blocks. The CSA points to all members of STATIC storage.
A program is considered reentrant if more than one task can execute the code without interfering with the other tasks' execution.
A CICS task exist from the time the operator presses the enter key until the application program returns control to CICS.
Terminal Control, File Control, Task Control, Storage Control, etc, Each CICS service program controls the usage and status for its resource (file, terminal, etc) within the CICS region.
PCT Program Control Table - defines each transaction containing a list of valid transaction identifiers (transid) where each transaction is paired with its matching program;
PPT Program Processing Table - contains a list of valid program names and maps and whether a current version is in the CICS region or needs to be brought in as a new copy;
FCT File Control Table - contains a list of files known to CICS, the dataset name and status (closed/open, enable/disabled;)
TCT Terminal Control Table - a list of the terminals known to CICS.
Link is temporary transfer of control. Xctl is permanent transfer of control
multitasking is the feature supported by the operating system to execute more than one task simultaneously. Multithreading is the system environment where the tasks are sharing the same programs load module under the multitasking environment. It is a subset of multitasking since it concerns task which use the same program.
PCT, FCT, TCT, DCT, PPT
MRO is the mechanism by which different CICS address spaces with in the same CPU can comunication and share resources.
Function request shipping is one of the CICS modes of intercommunication which allows an application program in a local CICS to access resources owned by a remote CICS.
By issuing an EXEC CICS ENQ against the resource. When processing is completed, a DEQ should be executed.
An EXEC CICS RETRIEVE command will access the common area.
You can also pass information in the following ways.
-By using a temporary storage queue.
-By using an intrapartion TDQ
-By using the Task Work Area
-By using TCTUA
-Through a file
By defining it on the PCT ( the Program Control Table)
You will be able to determine if the application was started by
(1) a transient data trigger level (QD),
(2) a START command (S,SD),
(3) user (U) or terminal input (TD), or
(4) Distributed Program Link (D, DS).
EXEC CICS ADDRESS with CWA option.
In the Program Control Table (PCT).
Deadlock (also known as a "deadly embrace") occurs when a task is waiting for a resource held by another task which, in turn, is waiting for a resources held by the first task.
If any one want to restrict Trans-ID to single user, enter trans-id with ENQ. It won't allow any one else to use the same trans-id.
Transaction routing is a CICS mode of intercommunication which allows a terminal connected to local CICS to execute another transaction owned by a remote CICS.
By issuing an EXEC CICS ENQ against the resource. When processing is completed, a DEQ should be executed.
When working in a pseudo-conversational mode, EIBCALEN can be checked if it is equal to zero. A programmer can use this condition as a way of determining first time usage (of the program).
The Transient Data Program (TDP).
The DFHMDF macro defines fields, literal, and characteristics of a field.
INTRA PARTITION TD QUEUEs. It is a goup of sequential records which are produced by the same and / or different transaction within a CICS region. These Qs are stored in only one physical file (VSAM) in a CICS region, which is prepared by the system programmer. Once a record is read from a queuue, the record will be logically removed from the queue; that is the record cannot be read again EXTRA PARTITION TD QUEUEs It is a group of sequential record which interface between the transaction s of the CICS region and the systems outside of CICS region. Each of there TDQs is a separate physical file, and it may be on the disk, tap, printer or plotter.
The ASKTIME command is used to request the current date and time. Whereas, the EIBTIME field have the value at the task initiation time.
Maps which can positioon themselves relative to the previous maps on the screen or page are known as the floating maps. For this you have to use special positional operands to LINE and COLUMN parameters of the BMS macro definition. They are SAME, NEXT. Actually this floating map concept is there only in Full BMS where as it is not available in Min. or Standard BMS macros. RECEIVE MAP is not recommended in the case of floating maps. Hence these maps are normally used to send information such as selected records from a database to screen but not for data entry. A mapset can contain more than one map in it, you may use all these maps to build a screen. In that case there are two ways to send these maps on to the screen.
i) Use separate SEND MAP commands one for each map involved. or
ii) Use ACCUM operand along with SEND MAP command and while sending really on to the screen use SEND PAGE to display them at one shot. The second one is called cumulative mapping scheme where you also can use foating maps.
Let's take a situation where you have to build a screen like this
HEADER MAP (no. of A gr. employs)
DETAIL MAP ( employee list)
When the length of the communication area (EIBCALEN) is equal to zeros, it means that no data was passed to the application.
The INTO option moves the information in the TIOA into the reserved specified area, while the SET option simple returns the address of the TIOA to the specified BLL cell or "address-of" a linkage-section.
When we use INTO option with the READ command the data content of the record will be moved into the specified field defined in the Working Storage Section of the program. When we use SET option with the READ command, CICS sets the address pointer to the address of the record in the file input / output area within 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. Therefore, the SET option provides a better performance than the INTO option.
MDT ( Modified Data Tag ) is one bit of the attribute character, If it is off (0), it indicates that this field has not been modified by the terminal operator. If it is on (1), It indicates that field has been modified by the operator. Only when MDT is on, will the data of the field be sent by the terminal hardware to the host computer (i.e. to the applcation progam in end). An effective use of MDT drastically reduces the amount of data traffic in the communication line, thereby improving performance significantly. Therefore, BMS maps and CICS application program should be devloped based on careful considerations for MDT.
The Modified Data Tag can be set on:
1. When the user enters data into the field.
2. When the application program moves DFHBMFSE to the attribute character.
3. By defining it in the BMS macro definition.
We dynamically position a cursor through an application program using a symbolic name of the symbolic map by placing -1 into the field length (i.e., fieldname + L) of the field where you wish to place the cursor. The SEND MAP command to be issued must have the CURSOR option (without value). Also, the mapset must be coded with MODE = INOUT in the DFHMSD macro. We get the cursor position when we receive a map by checking EIBCPOSN, which is a halfword ( S9(4) COMP) binary field in EIB, and contains offset position (relatively to zero) of the cursor on the screen.
I. Static positioning. Code the insert cursor (IC) in the DFHMDF BMS macro.
II. Relative positioning. Code the CURSOR option with a value relative to zero (position 1.1 is zero)
III. Symbolic positioning. Move high values or -1 the field length in the symbolic map (and code CURSOR on SEND command ).
A mapset is a collection of BMS maps link-edited together.
In order to avoid confusion and to maintain data security, a strict naming convention for QID will be required in the installation. Moreover, for a terminal-dependent task (e.g. pseudo-conversation task), the terminal id should be included in QID in order to ensure the uniqueness of TSQ to the task.
Temporary Storage Queue names are dynamically defined in the application program, while TDQs must first be defined in the DCT (Destination Control Table). When a TDQ contains certain amount of records (Trigger level), A CICS transaction can be started automatically. This does not happen when using a TSQ. TDQ (extra partition) may be used by batch application; TSQ cannot be accessed in batch. The Transient Data Queue is actually a QSAM file. You may update an existing item in a TSQ. A record in a TDQ cannot be updated. Records in TSQ can be read randomly. The TDQ can be read only sequentially. Records inTemporary Storage can be read more than once, while recordes stored in Temporary Data Queues cannot. With TDQs it is "one read" only.
CEDF:CICS-supplied Execution Diagnostic Facility transaction. It provides interactive program execution and debugging functions of a CICS programs.
CEMT: CICS-supplied Extended Master Terminal transaction. It displays or manipulates CICS control environment interactively.
CEBR: CICS-supplied Temporary Storage Browse transaction. It displays the content of Temporary Storage Queue (TSQ).
CECI: CICS-supplied Command Interpreter transaction. It verifies the syntax of a CICS command and executes the command.
To register all CICS terminals
INTRA-PARTITION Data queue.
When we send a map using SEND MAP command, Immediately we release the program by using EXEC CICS RETURN command. In this command we mention the TRANSACTION ID which is to be executed after receiving the map. In this command we also specify the data that should be stored in COMMUNICATION AREA for later use. When this command is executed the corresponding program is released from the memory. After receiving the response from the terminal the program is again loaded and this time the data which we stored in communication area will be copied into the working storage section. And the map will be received with RECEIVE MAP command. The variable EIBCALEN in EIB holds the length of communication area. In procedure division we checks the value of EIBCALEN if it is zero, we first send the map followed by RETURN command. Otherwise, that is if EIBCALEN is not zero, we know that this transaction is not running first time and we receive the map by using RECEIVE MAP command.
By coding an EXEC CICS START in the application program
1. By coding the trans id and a trigger level on the DCT table
2. By coding the trans id in the EXEC CICS RETURN command
3. By associating an attention key with the Program Control Table
4. By embedding the TRANSID in the first four positions of a screen to the terminal.
5. By using the Program List Table.
The XCTL command transfer control to another application (having the same Transaction ID), while the START command initiates a new transaction ID (therefore a new task number). The XCTL continues task on the same terminal. START can initiate a task on another terminal.
With an XCTL, the working storage and the procedure division of the program issuing the XCTL are released. The I/O areas, the GETMAIN areas, and the chained Linkage Section areas (Commarea from a higher level) remain. All existing locks and queues also remain in effect. With a LINK, however, program storage is also saved, since the transaction expects to return and use it again.
A program pr map loaded into the CICS nucleus so that is kept permanently in main storage and not deleted when CICS goes " Short on Storage."
I. The cursor position in the map
II. Transaction ID
III. Terminal ID
IV. Task Number
V. Length of communication area
VI. Current date and time
VII. Attention identifier
The next time the end user presses an attention key, CICS will start the transaction specified in the TRANSID option.
To specify the paragrph or program label to which control is to be passed if the "handle conditin" occurs.
HANDLE CONDTION command creates a "go-to" environment. An IGNORE command does not create a go-to environment: instead. it gives control back to the next sequential instruction following the command causing the condition. They are opposites.
By coding an EXEC CICS POP HANDLE command
The following commands are available for the Program Control services:
1. LINK: To pass control to another program at the lower level, expectiong to be returned.
2. XCTL: To pass control to another program at the same level, not expecting to be returned.
3. RETURN: To return to the next higher-level program or CICS.
4. LOAD: to load a program
5. RELEASE: To release a program.
Data can be passed between CICS programs in three ways- COMMAREA, TRANSIENT DATA QUEUE $ TEMPORARY STORAGE QUEUE.
Data can be passed to a called program using the COMMAREA option of the LINK or XCTL command in a calling program. The called program may alter the data content of COMMAREA and the changes will be available to the calling program after the RETURN command is issued in the called program. This implies that the called program does not have to specify the COMMAREA option in the RETURN command.
If the COMMAREA is used in the calling program, the area must be defined in the Working Storage Section of the program (calling), whereas, in the called program, the area must be defined as the first area in the Linkage Section . using reserved name DFHCOMMAREA.
It allows the establishing of an exit so cleanup processing can be done in the event of abnormal task termination.
No action is going to be taken for any exceptional conditional occurring during the execution of this command. the abnormal condition that occurred will be ignored even if an EXEC CICS HANDLE condition exist. It has the same effect as the EXEC CICS IGNORE condition except that it will not cancel the previous HANDLE CONDTION for any other command.
Reentrant program is a program which does not modify itself so that it can reenter to itself and continue processing after an interruption by the operating system which, during the interruption, executes other OS task including OS tasks of the same program. It is also called a "reenterable" program or "serially reusable" program
A quasi-reentrant program is a reentrant program under the CICS enviroment. That is, the quasi-reentrant program is a CICS program which does not modify itself. That way it can reenter to itself and continue processing after an interruption by CICS which, during the interruption executes other tasks inluding CICS tasks of the same program. In order to maintain the quasi- reentrancy, a CICS application program must follow the follow convention:
Constants in Working Storage: The quasi-reentrant program defines only constants in its ordinary data area (e.g. working Storage Section). These constants will never be modified and shared by the tasks
Variable in Dynamic Working Storage: The quasi reentrant program acquires a unique storage area ( called Dynamic Working Storage - DWS) dynamically for each task by issuing the CICS macro equivalent GETMAIN. All variables will be placed in this DWS for each task. All counter would have to be initialized after the DWS has been acquired.
The Base Locator for Linkage (BLL) is an addressing convention used to address storage outside the Working Storage Section of an application program. If BLL is used for the input commands (e.g.: READ, RECEIVE), it will improve the performance, since the program would be accessing directly the input buffer outside of the program. In order to work as intended, the program must construct BLL based on the following convention:
1. The parameter list must be defined by means of a 01 level data definition in the Linkage Section as the first area definition to the Linkage Section, unless a communication area is being passed to the program, in which case DFHCOMMAREA must be defined first. The parameter list consists of a group of the address pointers, each of which is defined as the full word binary field ( S9(8) COMP). This is called the BLL cells.
2. The parameter list is following by a group of 01 level data definitions, which would be the actual data areas. The first address pointer of the parameter list is set up by CICS for addressing the parameter list itself. From the second address pointer onward, there is a one-to-one correspondence between the address pointer of the parameter list and 01 level data definitions.
3. VS COBOL II provides CICS application programs with a significant improvements in the area of addressability through the specifial ADDRESS register. Therefore, if an application program is written in VS COBOL II, the program is no longer requires building the B
The XCTL command transfer control to an application program at the same logical level ( do not expect to control back), while the lINK command passes control to an application program at the next logical level and expects controal back.
You must code EXEC CICS ASSIGN with the OPENID option.
CICS automatically provides some system-related information to each task in a form of EXEC interface BLOCK (EIB), which is unique to the CICS command level. We can use all the fields of EIB in our application programs right away.
The EIBRCODE tells the application program if the last CICS command was executed successfully and, if not, why not.
An abnormal situation during execution of a CICS command is called an exceptional condition:
1. Handle Condition Command: It is used to transfer control to the procedure label specified if the exceptional condition specified occurs.
2. Ignore Condition Command: It causes no action to be taken if the condition specified occurs in the program. That is control will be returned to the next instruction following the command which encountered the exceptional condition.
3. No Handle Option: This option can be specified in any CICS command and it will cause no action to be taken for any exceptional condition occurring during execution of this command.
4. RESP Option: This option can be specified in any CICS command. If the RESP option is specified in a command, CICS places a response code at a completion of the command. The application program can check this code, then proceed to the next processing.
No more than 16 in a single handle condition. If you need more, then you must code another HANDLE CONDITION command.
This is the area of main storage designed to let programs or task communicate with one another. used in programs via RETURN, XCTL and LINK commands.
(Name the constituents of the Queue ID).
TWASIZE=300 in PCT table.
166. Code the related portions of CICS/COBOL-I programs to gain addressability to TWA area assigned to a particular task. Assme that the size of TWA area is 300 bytes. What are the advantages if COBOL-II is used in the place of COBOL?
Code the above requirement in COBOL-II.
AN: LINKAGE SECTION.
02 FILLER PIC S9(8) COMP.
02 TWA-PTR S(98) COMP.
02 DATA-AREA PIC x(300)
EXEC CICS ADDRESS
SERVISE RELOAD TWA-DATA-LAYOUT.
05 DATA-AREA PIC X(300).
EXEC CICS ADDRESS
TWA(ADDRESS OF TWA-DATA-LAYOUT)
The programming technique in which the task will not wait for the end-user replies on the terminal. Terminating the task every time the application needs a response from the user and specifying the next transaction to be started when the end user press any attention key ( (Enter, PF1 trough PF24, PF24, PA1, PA2 and clear) is pseudo-conversational processing.
The CICS translator convert the EXEC CICS commands into call statements for a specific programming language. There are CICS translator for Assembler, COBOL, and PL/1.
The Program List Table records the set of application programs that will be executed automatically at CICS start-up time
. Data Value - EX (Literal 8 or 77 KEYLEN PIC S9(4) COMP VALUE8.)
. Data Area - EX (01 RECORD-AREA. 05 FIELD PIC X(5).)
. Pointer-REF -EX (05 POINTER-I PIC S9(8( COMP.) . Name -EX (05 FIELD-NAME PIC X(5) VALUE 'FILEA'.)
. Label - Cobol paragraph name
. HHMMSS - EX (77 TIMEVAL PIC S9(7) COMP3. )
EIBDATE and EIBTIME.
RESP( S9(8) COM. )
EXEC CICS DELAY EXEC CICS DELAY
EIBCALEN - To check if COMMAREA has been passed in terurn command.
EXEC CICS RETURN
DFHDCT TYPE = INTRA,
DESTIN = MSGS,
TRANSID = MSW1,
TRIGLEV = 1000
EXEC CICS WRITEQ TD
TCP places data in TIOA and corresponding entry into TCT.
KCP acquires the transaction identifier from TIOA and verifies if it is present in PCT.
SCP acquires Storage in Task Control Area (TCA), in which KCP prepares control data for the task.
KCP then loads the application programs mentioned in PCT by looking for it in PPT.
If resident - real storage memory location is not present in the PPT the control is passed to PCP that loads the application program from the physical storage location address given in PPT. The control is then passed to the application program (LOAD module).
EXEC CICS UNLOCK END-EXEC.
EXEC CICS READ
MOVE-1 to FIELD + L field. Mention CURSOR option in the SEND command.
Mention FSET option in DFHMDF or set it dynamically in the program using FIELD+A sttribute field.
EXEC CICS ASSIGN
EXEC CICS STARTBR ---- END-EXEC.
SET(ADDRESS OF LINKAGE-AREA).
EXEC CICS CANCEL
The transaction initiated should be in a position to retrieve information pertaining to which transaction has initiated it and from which terminal. (Code the required CICS commands)
EXEC CICS START
EXEC CICS RETRIEVE
FIELD+L - Return the length of text entered (or for dymanic cursor positioning)
FIELD+F - Return X(80) if data entered but erased.
FIELD+A - Used for attributes reading and setting
FIELD+I - Used for reading the text entered while receiving the map.
FIELD+O - Used for sending information on to the MAP.
What are the commands used to gain
exclusive control over a resource
(for Ex a Temporary storage queue.)?
EXEC CICS ENQ EXEC CICS DEQ
List the sequence of steps used to achieve "Modiication in Skip Sequential Mode".
I. READNEXT command
II. Issue the ENDBR command
II. Issue the READ command with UDATE option.
IV. Manipulate the record ( DELETE or REWRITE command)
V. Issue START command
VI. Isusue two READNEXT commands (One for dummy skip)
VII. Go to step two.
Any BLL Cell -S9(8) COMP
Data type of length Option field - S9(4) COMP
HHMMSS type of data fields - S9(7) COMP 3
CICS (Customer Information Control System) is a transaction server that runs primarily on IBM mainframe systems under z/OS and z/VSE.
CICS is a transaction manager designed for rapid, high-volume online processing. This processing is mostly interactive (screen-oriented), but background transactions are possible.
While CICS has its highest profile among financial institutions such as banks and insurance companies, over 90 percent of Fortune 500 companies are reported to rely on CICS (running on z/OS) for their core business functions, beside many governments. CICS is used in bank-teller applications, ATM systems, industrial production control systems, insurance applications and many other types of interactive application.
Recent CICS Transaction Server enhancements include support for Web services and Enterprise Java Beans (EJBs). IBM began shipping the latest release, CICS Transaction Server - Version 3.2, in June of 2007.