Using the Code Debug CICS I/O Area
Related Topics
The Code Debug CICS I/O area holds data across screens in the File Utility during a session. This area is maintained within CICS shared storage. Because data is held in the Code Debug CICS I/O area, you can read data from one file resource, then write or rewrite the record to another resource. For example, you can read data from a data set, then write the record to a temporary storage queue.
Use the following commands to manipulate the size of this area while in the File Utility:
- INSERT: Creates an entirely new record, if none exists, or enlarges the size of the current I/O area.
- REMOVE: Decreases the size of the current I/O area.
Data in the I/O area can be displayed in up to four modes. Each mode supports different scrolling commands. The following table shows the modes and corresponding scrolling commands available on various screens:
File Utility Scrolling Commands
Command | Display Mode | Scroll Commands | Applicable Screens |
|---|---|---|---|
HEX OFF | Display data in character format | LEFT, RIGHT | 5.1.2, 5.1.3, 5.2.2, 5.2.3, 5.3.2, 5.4.4, 5.5.5, 5.5.6, 5.6.2, 5.6.3 |
HEX or HEX ON | Display data in vertical hex format | LEFT, RIGHT | 5.1.2, 5.1.3, 5.2.2, 5.2.3, 5.3.2, 5.4.4, 5.5.5, 5.5.6, 5.6.2, 5.6.3 |
HEX DUMP | Display data in dump format | UP, DOWN, TOP, BOT | 5.1.3, 5.2.3, 5.3.2, 5.4.4, 5.5.6, 5.6.2, 5.6.3 |
USING | Display data using COBOL or PL/I | UP, DOWN, TOP, BOT, | 5.1.3, 5.2.3, 5.3.2, 5.4.4, 5.5.6, 5.6.2, 5.6.3 |
Code Debug CICS accesses file resources using a separate transaction, which it starts. If this transaction does a CICS call, and CICS does not complete the call in 14 seconds, Code Debug CICS instructs the transaction to cancel once control returns to it. A message is displayed that the request could not be completed. The wait interval of 14 seconds can be changed in the SECONDS_TO_WAIT_FOR_DBFL_TO_COMPLETE parameter of the Code Debug CICS global parameters.