PL/SQL and JCL Programming Quiz

DISP=(,CATLG) uses abbreviated syntax where the first parameter is omitted and defaults to NEW. The full form is DISP=NEW,CATLG,CATLG meaning: create new dataset, catalog on normal completion, and catalog on abnormal completion. OLD applies only to existing datasets, and DELETE would remove rather than catalog the dataset.

MXIG requests allocation of the largest available contiguous space on a volume, useful for optimizing space utilization. CONTIG requires contiguous space but doesn't maximize size. ROUND allocates in specific cylinder units. RLSE releases unused space back to the system after dataset closing.

JOBLIB is a job-level statement that defines a private library for the entire job and cannot appear within a PROC. PROCs can contain EXEC statements (for steps), DD statements (like SYSPRINT for output, SYSABEND forabend dumps), and other step-level elements. JOBLIB must precede the first EXEC statement in a job.

A single job step can have a maximum of 255 DD (Data Definition) statements. This limit is imposed by the JES to prevent excessive resource consumption and ensure job manageability. Complex jobs requiring more datasets must be split into multiple steps.

TYPRUN=SCAN performs syntax checking without executing the job, useful for validating JCL before production submission. COMPILE compiles and executes the program. HOLD holds the job in the input queue without execution. ERRFREE is not a valid TYPRUN parameter value.

IEHPROGM is the IBM mainframe utility specifically designed for dataset management operations including renaming, cataloging, and uncataloging datasets. IEBCOPY is for copying PDS datasets, IEBGENER is for sequential dataset copying, and IEBCOMPR is for comparing datasets.

When the DISP parameter is omitted in a DD statement for a new dataset, the default is DISP=NEW,DELETE,DELETE. This means the dataset is treated as new (NEW), will be deleted if the step abends (first DELETE), and will be deleted after successful step completion (second DELETE).

SYSMDUMP produces an unformatted dump of the abended job's storage, written directly to disk without processing. SYSUDUMP creates a formatted dump, SYSABEND is forabend-related sysout output, and SYSOUT is general output class specification.

STEP1 executes and returns a condition code of 4. STEP2 executes next because it has COND=EVEN (runs even if previous steps abended), and it abends. STEP3 has COND=((8,LE,STEP1),ONLY). ONLY means run only if a prior step abended. Since STEP2 abended, and the condition 8 LE 4 is false (meaning STEP1's code 4 is not greater than or equal to 8, so we do not bypass), STEP3 executes. Thus, all three steps execute.

PARM is the JCL parameter used to pass input values to a COBOL (or other) program at execution time. INPUT is not a JCL parameter, SYSOUT defines output class, and COND specifies step conditional execution.

There are 12 types of triggers in PL/SQL: BEFORE UPDATE, AFTER UPDATE, BEFORE INSERT, AFTER INSERT, BEFORE DELETE, AFTER DELETE (6 row-level), and their 6 statement-level counterparts, totaling 12.

%ROWCOUNT is a cursor attribute that returns the number of rows fetched by the cursor so far. It is a numeric value that increments with each successful fetch operation.

PL/SQL has two types of cursors: implicit cursors (automatically created by Oracle for SQL statements) and explicit cursors (explicitly declared and managed by the programmer).

The correct structure of an explicit cursor is: OPEN cursor, FETCH cursor INTO variables, process the data, then CLOSE cursor. Option B correctly shows this complete lifecycle with FETCH statement included.

The %FOUND cursor attribute returns a BOOLEAN value (TRUE if a row was fetched, FALSE if not). It does not return NUMBER, CHARACTER, or STRING types.

NUMBER and PLS_INTEGER differ primarily in storage. NUMBER is a variable-length decimal type stored with mantissa and exponent, while PLS_INTEGER is a fixed-length binary integer stored in native machine format, making it more efficient for calculations.

Database stored procedures, triggers, and views are typically stored in the database dictionary as both the original source code (for viewing/editing) and in a compiled/p-code form (for execution efficiency).

The default parameter mode for procedures is IN. IN parameters pass values into the procedure but cannot be modified within the procedure.

Procedures accept three parameter modes: IN (read-only input), OUT (write-only output), and INOUT (read and write). These modes control how data flows between the procedure and calling environment.

In Oracle PL/SQL, a package can consist of a specification only if it defines types, constants, or variables without any procedural logic that requires a body. Thus, a package specification can legally exist without a corresponding package body.