Mainframe JCL, REXX, and CICS Programming

Intra Partition Transient Data Queues (TDQ) support Automatic Transaction Initiation (ATI) in CICS, allowing a transaction to be automatically started when data is written to the queue. Extra Partition TDQ and TSQ do not support ATI, making option B the correct answer.

CEDA is the CICS transaction used for Resource Definition Online (RDO), allowing online definition and modification of CICS resources. CEMT is for master terminal functions, CECI is the command interpreter, and CEDF is for debugging - none of these define resources.

RENT is a mandatory compiler parameter for CICS programs because CICS programs must be re-entrant (multiple users can execute the same code simultaneously). SSRANGE and FLAGSAA are optional, and RES is not a standard COBOL compiler option.

CEBR (Browse) is the CICS transaction used to browse and display the contents of both Temporary Storage Queues (TSQ) and Transient Data Queues (TDQ). CEDA defines resources, CECI interprets commands, and CEMT handles master terminal functions - none browse queues.

The RCT (Resource Control Table) in CICS is used to register application plans. Other options like PCT (Program Control Table), DCT (Destination Control Table), and TCT (Terminal Control Table) serve different purposes in CICS resource management.

CICS supports both static calls (compile-time binding) and dynamic calls (runtime binding) for program invocation. This flexibility allows developers to choose between performance optimization (static) and runtime flexibility (dynamic) when designing CICS applications.

CECI (CICS Execute Interpreter) allows testing BMS maps interactively without writing a full COBOL program. CEDF is for debugging, CEMT for master terminal commands, and CEDA for resource definition - none of these specifically test BMS maps.

CICS does NOT support QSAM datasets - it only supports VSAM for file management. This is a key architectural limitation of CICS, which was designed specifically for VSAM's random access capabilities rather than QSAM's sequential access.

Both EXEC CICS LINK and COBOL CALL statements transfer control to another program and allow parameter passing. While CICS LINK is specific to the CICS environment, functionally they serve the same purpose of program invocation with similar control flow behavior.

CICS RETURN doesn't always return to the calling program - it can return to CICS itself depending on context. When used in a pseudo-conversation, RETURN TRANSID passes control to another transaction, not necessarily the caller. The statement is oversimplified and therefore false.

CEDF (CICS Execution Diagnostic Facility) does NOT allow interruptions at arbitrary COBOL statements. Interruptions are only permitted at specific CICS-level breakpoints or transaction boundaries. This is a fundamental constraint of the CICS debugging environment.

In CICS, the CANCEL command is used to cancel or suspend a task that was previously initiated with a START command. The CANCEL command terminates the specified task and prevents it from running. UNLOCK is used to release resources, IGNORE suppresses error messages, and RETRIEVE retrieves data from temporary storage - none of these suspend STARTed tasks.

wordindex() returns the position of a specified word within a string. This is a database-specific function (appears in some older systems). The question has grammatical issues ('which' should be capitalized) and the function name may not be standard across SQL dialects.

Strip() removes leading and trailing characters (typically spaces) from a string. This is similar to TRIM in standard SQL. The question has grammatical errors ('which' should be capitalized, 'infact' should be 'in fact').

In JCL (Job Control Language), the fundamental unit of work is a 'Job'. A job consists of one or more steps (EXEC statements) that execute programs, and each step may reference data definitions (DD statements). Jobs are identified by JOB statements and are the primary organizing unit in mainframe batch processing.

JCL statements must appear in a specific hierarchical order: JOB (identifies the job and sets parameters), then EXEC (defines execution steps/programs), then DD (defines data sets used by each step). This nesting structure reflects that jobs contain steps, and steps use data resources.

The JOB card (JOB statement) serves two key purposes: it identifies the job with a unique name, and it tells the MVS (Multiple Virtual Storage) operating system about the job's characteristics including type, priority, accounting info, and resource requirements. It's not just for identification - it conveys execution parameters to the system.