Mainframe CICS and BMS Programming

A Mapset is a collection of one or more maps. In CICS BMS, maps are grouped together into mapsets for efficient management and loading. Individual maps are defined within a mapset. BMS is the overall system, while Physical Map and Symbolic Map refer to specific components, not collections.

To answer this question, the user needs to have knowledge of field protection attributes in computer programming.

Option A: NORM/BRT/DRK are not field protection attributes. They are used in graphics and represent different brightness levels.

Option B: PROT/UNPROT/ASKIP are field protection attributes. PROT stands for "Protected", which means that the field is protected against updates. UNPROT stands for "Unprotected", meaning the field can be updated. ASKIP stands for "Ask before skipping", which means a message will be displayed to the user asking if they want to skip the field.

Option C: FSET stands for "Field Set", which is a group of fields that share common properties.

Option D: NUM/IC are not field protection attributes. NUM stands for "Numeric", meaning the field can only accept numeric values. IC stands for "Input Capable", meaning that the field can be updated by the user.

Therefore, the correct answer is:

The Answer is: B. PROT / UNPROT / ASKIP

A field's Modified Data Tag (MDT) can be turned on by defining FSET in the physical map, setting the attribute byte to FSET programmatically in the symbolic map, or when the user types data into the field. Therefore, all listed options are valid methods.

A Mapset definition is ended with DFHMSD TYPE=FINAL END. This marks the final entry in the mapset definition sequence. DFHMDI ends individual maps, DFHMDF ends field definitions, and plain END is not sufficient for proper mapset termination in BMS.

In a CICS BMS symbolic map, multiple variable levels are generated for each field: suffix L for length, A for attribute, F for flag/modified data, and I/O for input/output data. Since all these components are generated, 'All of the above' is the correct answer.

DFHBMSCA is the copybook used to modify attribute bytes in the symbolic map. This allows programs to override physical map attributes like field intensity, protection status, and color at runtime. DFHEIBLK is for CICS interface block, DFHAID contains attention identifiers, and DFHCOPY is generic.

The FRSET (Force Reset) option in CICS BMS resets the Modified Data Tag (MDT) to zero for all fields on the screen before the map is written. This ensures only newly modified fields are sent back on subsequent reads, preventing unwanted data transmission.

The DATAONLY option tells BMS to use only the data and attributes from the symbolic map (including cursor positioning) when constructing the 3270 data stream. It bypasses the physical map's template, taking field contents and their associated attributes directly from the symbolic map structure in the program.

In CICS BMS, cursor positioning techniques include Initial (default position), Direct (absolute row/column), and Symbolic (using field name in symbolic map). There is no 'Physical cursor positioning' technique - cursor positioning is always done logically through symbolic references or absolute coordinates, not through physical map constructs.

EIBCPOSN in the CICS Execution Interface Block (EIB) specifically stores the screen cursor position. EIBCALEN contains the length of the communication area (COMMAREA), EIBAID holds the attention identifier (which key or function key the user pressed), and EIBCURS is not a standard CICS EIB field.

During a BMS RECEIVE operation, CICS populates EIBCPOSN with the cursor position relative to the appropriate field on the screen. EIBAID would contain the attention identifier (key pressed), not on RECEIVE. The COMMAREA length (EIBCALEN) is not determined during RECEIVE.

DFHAID is the CICS copybook that defines constants for attention identifier (AID) keys like PF1, ENTER, CLEAR, etc. DFHEIBLK defines the EIB structure itself. DFHBMSCA contains basic mapping support constants, and DFHKEYS is not a standard CICS copybook.

During a CICS RECEIVE MAP command, data entered by the user is mapped into the input fields of the symbolic structure, represented by variables ending with the suffix 'I'. Suffixes 'O', 'L', and 'A' represent output data, field length, and attributes respectively.

BMS commands include SEND MAP, SEND CONTROL, and RECEIVE MAP. There is no 'Send Mapset' command in CICS BMS - you send individual maps from a mapset, not the entire mapset. 'Receive Mapset' is also not a valid BMS command.

Field attributes in BMS control field protection, highlighting (for errors), cursor positioning, and color. Highlighting fields in error (Option A) is a primary use case. While protecting fields and positioning cursors are also field attribute functions, the question asks 'why' with a primary focus, and error highlighting is a critical application requirement.

In COBOL, the OCCURS clause cannot be specified at the 01 level because 01 level represents the highest level in the data hierarchy and defines record structures. OCCURS clauses must be defined at lower levels (02-49) to create table elements within a record.

In COBOL, the STOP RUN statement terminates the entire run unit, not just the current program. When Program B (called program) executes STOP RUN, it immediately ends program execution and control does NOT return to Program A (the calling program). This is different from GOBACK or EXIT PROGRAM which would return control to the caller.

S322 is the system abend code in IBM mainframe JCL that indicates a timeout condition - specifically when a job step exceeds the CPU time limit specified in the TIME parameter of the JOB card. Other options are: SB37 (out of space on DASD), SOC7 (data exception/numeric error), and 345 is not a standard abend code.