Mainframe DB2 SQL and JCL Fundamentals

Dataset concatenation in JCL combines multiple datasets for input processing. Option A is correct because concatenation merges multiple sequential datasets for input. Option C is correct because a DUMMY dataset can be placed in concatenation to mark end-of-input. Option B is incorrect because concatenation is input-only. Option D is incorrect because datasets on different device types can be concatenated for input.

When calling JCL procedures, you have extensive modification capabilities. Option B is most complete because procedures allow overriding, nullifying, or adding parameters on all statement types (JOB, EXEC, DD), plus adding new DD and OUTPUT statements. Options A, C, and D are incomplete because they don't capture the full range of modification capabilities available when calling procedures.

SQL predicates support all standard inequality comparison operators, including less than (<), greater than (>), and less than or equal to (<=). Thus, any of these operators can be used.

In SQL LIKE predicates, the percent sign (%) wildcard matches any string of zero or more characters. The underscore (_) wildcard matches exactly one character, while the asterisk (*) is not standard for LIKE pattern matching in SQL.

DISTINCT removes duplicate rows from result sets, returning only unique rows. It does not select all rows, affect ordering, or perform filtering - it purely eliminates duplicates based on selected columns.

UNION can be used with outer joins because UNION combines result sets from multiple queries, and outer joins return matched plus unmatched rows. UNION ALL preserves duplicates while UNION eliminates them, but both are compatible with join operations.

DB2 Alias can represent remote tables and views, can be used by anyone (public synonym), and does not require DB2 authority because it inherits permissions from the underlying object rather than granting new access.

Views serve two key purposes: they can restrict data access by showing only selected columns or rows (security/control), and they can simplify complex queries by presenting pre-joined or calculated data (usability). Both functions are standard use cases.

DB2 provides three main DML (Data Manipulation Language) statements for modifying data: INSERT adds new rows, UPDATE modifies existing rows, and DELETE removes rows. All three operations change the database content.

In SQL, a subquery (nested query) can be placed in several clauses, including the WHERE clause to filter rows and the HAVING clause to filter groups. Since both options are valid, 'Either of the above' is correct.

Static SQL statements are hard-coded or embedded directly within the source code of an application program before compile time. They are bound and prepared prior to execution, unlike dynamic SQL which is constructed and prepared during the application's execution.

When SQL retrieves data, the output is called a result table - a temporary set of rows matching the query criteria. A view is a stored query definition, a synonym is an alternate name for an object, and an alias is an alternate name for a table - none of these are the retrieved data itself.

WHERE is a SQL clause that introduces conditions, not a comparison operator itself. AND is a logical operator that combines conditions, IS NULL checks for null values, and BETWEEN tests range conditions - these are all valid operators or predicates used within WHERE clauses.

Column functions (also called aggregate functions) operate on sets of values. SUM calculates the total of numeric values, AVG computes the average. Both are standard column functions in SQL.

INFO-PROGRAM-ID is the specific INFO variable that stores the first six characters of the program name in CICS demand processing. INFO-FUNCTION-KEY stores function key numbers, INFO-CONVERSATION indicates conversational mode status, and INFO-PASSOFF handles passoff-related information.

INFO-FUNCTION-KEY is specifically designed to store the function key number when a function key is received in CICS. The other variables serve different purposes: INFO-PROGRAM-ID for program name, INFO-CONVERSATION for mode status, and INFO-PREVIOUS-PROGRAM-ID for tracking the prior program.

INFO-CONVERSATION is set to 'Y' when the terminal is in conversational mode and 'N' otherwise in CICS environments. This variable specifically tracks the conversational state of the terminal session, unlike INFO-PROGRAM-ID, INFO-USERID, or INFO-PASSOFF which serve different purposes.

In APS (Application Development System) COBOL generators, the INFO-PASSOFF variable is set to 'Y' when the program is invoked using a PASSOFF statement, whereas the other options store different context metadata.