COBOL and JCL Programming Quiz

Historically, IBM mainframe operating systems limited PDS (Partitioned Data Set) concatenations to a maximum of 16 datasets. Although modern z/OS environments support up to 255 extents and datasets in a concatenation, 16 remains the standard correct answer in legacy exams and textbooks.

In IBM MVS JCL, there is a system-defined architectural limit on the number of job steps. A maximum of 255 EXEC statements (which define individual job steps) can be coded and executed within a single Job Control Language (JCL) stream.

Files with KEEP disposition require the volume serial number for access because the system needs to locate the specific volume where the retained file resides. This is standard MVS dataset management.

When creating GDG(+2) when current generation is G0001V00, the new generation becomes G0003V00. GDG increments by 2 from 0001 to 0003. This follows standard GDG numbering where (+2) means increment generation number by 2.

Instream data cannot be coded directly in a PROC. PROCs are for defining JCL structures, while instream data requires DD statements like SYSIN with * or DATA. The actual data is supplied when the PROC is executed in a job step.

In JCL, the TIME parameter specifies the maximum CPU time a job step can consume. Coding TIME=1440 (which equals 24 hours) has a special meaning in z/OS, telling the system that no CPU time limit is to be applied to the step, allowing it to run indefinitely.

The JOB statement identifies the job name and provides accounting information. It's the first statement in JCL and names the job for system tracking and resource allocation.

This job step needs 3 DD statements: one for input (previous job step output), one for output (new data set creation), and one for copying to another storage device. Each data access requires its own DD statement.

In JCL, missing DISP parameters default based on status. For DISP=(,,KEEP), status defaults to NEW, and normal disposition defaults to DELETE, matching (NEW,DELETE,KEEP). For DISP=(OLD,,), normal and abnormal dispositions default to KEEP (since status is OLD), matching (OLD,KEEP,KEEP).

In COBOL, file status code 41 indicates that an OPEN operation was attempted on a file that was already opened. This is a specific file I/O error condition. Code 6, 16, and 42 represent different file errors.

All three error types are possible within a COBOL IF statement: infinite loops (if logic never terminates), logical errors (incorrect condition logic), and runtime errors (invalid data access during condition evaluation). Therefore 'All of the above' is correct.

When storing YYYYMMDD as 8 bytes in COBOL, you use PIC X(8) because it's stored as alphanumeric character data, not as a numeric or date type. The DATE format verb doesn't exist in this syntax, and Y/M/D format is not valid for PICTURE clauses.

VARIABLE is NOT a reserved word in COBOL - it's a valid user-defined name. RECORD, INDEX, and FILE are all COBOL reserved words with specific meanings in the language syntax.

ASSIGN is NOT used for calculations in COBOL - it's used to assign file names to file descriptors or assign data items. DIVIDE, MULTIPLY, and ADD are all arithmetic verbs used for mathematical calculations.

Scope terminators (like END-PERFORM, END-EVALUATE) are mandatory for in-line PERFORMs and EVALUATE statements to clearly delimit the statement block. They are optional (not mandatory) for IF statements, though recommended for clarity. 'all' is incorrect.

In programming languages like COBOL, files can be opened in exactly four modes: INPUT, OUTPUT, I-O, and EXTEND. Similarly, Python defines four basic file open modes: read ('r'), write ('w'), append ('a'), and exclusive creation ('x'). Therefore, four is the standard correct answer.

In an EVALUATE statement (COBOL's equivalent of a CASE/SWITCH structure), WHEN clauses are evaluated sequentially from top to bottom. The first clause whose condition evaluates to true is executed, so the order is significant when conditions overlap or when using WHEN OTHER (which must come last).

In COBOL, the WRITE operation requires the file to be opened in OUTPUT mode (for creating new records in a new file) or INPUT-OUTPUT mode (for updating existing records in indexed or relative files). INPUT mode is only for reading, and EXTEND is for adding records to the end of an existing file.

In COBOL, GO BACK is equivalent to STOP RUN in a stand-alone program because GO BACK returns control to the calling program, and when there is no caller (stand-alone), it terminates the program. FINISH, STOP, and EXIT are not valid COBOL verbs for program termination in this context. EXIT PROGRAM exists but is for called programs, not stand-alone programs.