Explore topic-wise InterviewSolutions in .

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.

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.

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.

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.

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.

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.

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.

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.

INTRA-PARTITION DATA QUEUE.

INTRA-PARTITION Data queue.

CEDA

CEDA

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.

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.

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.

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.

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.

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.

1.  Static positioning. Code the insert cursor (IC) in the DFHMDF BMS macro.
2. . Relative positioning. Code the CURSOR option with a VALUE relative to zero (POSITION 1.1 is zero).
3.  Symbolic positioning. Move high values or -1 the field LENGTH in the symbolic map (and code CURSOR on SEND command ).

    

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.

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.

No

No

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.

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.

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.

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.

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.

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.

When the length of the COMMUNICATION AREA (EIBCALEN) is equal to ZEROS, it MEANS that no data was passed to the application.

When the length of the communication area (EIBCALEN) is equal to zeros, it means that no data was passed to the application.

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)
TRAILER MAP

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)
TRAILER MAP

The ASKTIME command is USED to request the current date and TIME. Whereas, the EIBTIME field have the value at the task INITIATION time.

The ASKTIME command is used to request the current date and time. Whereas, the EIBTIME field have the value at the task initiation time.

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.

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 TRANSIENT DATA PROGRAM (TDP).

The Transient Data Program (TDP).

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

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

By issuing an EXEC CICS ENQ against the RESOURCE. When PROCESSING is completed, a DEQ should be executed.

By issuing an EXEC CICS ENQ against the resource. When processing is completed, a DEQ should be executed.

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.

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.

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.

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.

In the PROGRAM CONTROL Table (PCT).

In the Program Control Table (PCT).

EXEC CICS ADDRESS with CWA OPTION.

EXEC CICS ADDRESS with CWA option.

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

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

By DEFINING it on the PCT ( the PROGRAM CONTROL Table)

By defining it on the PCT ( the Program Control Table)

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.

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.

An EXEC CICS RETRIEVE command will access the common AREA.

An EXEC CICS RETRIEVE command will access the common area.

By issuing an EXEC CICS ENQ against the RESOURCE. When processing is completed, a DEQ should be EXECUTED.

By issuing an EXEC CICS ENQ against the resource. When processing is completed, a DEQ should be executed.

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.

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.

MRO is the mechanism by which DIFFERENT CICS address SPACES with in the same CPU can COMUNICATION and SHARE resources.

MRO is the mechanism by which different CICS address spaces with in the same CPU can comunication and share resources.

PCT, FCT, TCT, DCT, PPT

PCT, FCT, TCT, DCT, PPT

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.

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.

LINK is TEMPORARY transfer of CONTROL. XCTL is PERMANENT transfer of control.

Link is temporary transfer of control. Xctl is permanent transfer of control.

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.

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.

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.

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.

A CICS task EXIST from the time the operator presses the enter KEY until the application PROGRAM returns CONTROL to CICS.

A CICS task exist from the time the operator presses the enter key until the application program returns control to CICS.

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.

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.

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 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 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 modified data tag is the last bit in the attribute byte for each screen field. It indicates whether the corresponding field has been changed.

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.

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 COMMON WORK area is a storage area that can be accessed by any TASK in a CICS SYSTEM.

The common work area is a storage area that can be accessed by any task in a CICS system.

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.

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.

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.

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.

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.

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.

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)

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)

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.

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 LENGTH will be 0 (ZERO).

The length will be 0 (zero).