M204 Programming Language Quiz

The code defines a found set A with 10 records but contains no PRINT statement - only END. Without an explicit print command, M204 will not output anything even though records are found. Options A and B are incorrect because nothing is printed.

DELETE is the M204 statement that removes fields from a record. DELETE RECORD would remove the entire record, not just fields. DELETE FIELD and REMOVE are not valid M204 syntax for field removal.

TABLE B is the largest section in M204 file tables. M204 files are organized with Table A containing hash codes, Table B containing the actual record data (largest), Table C for overflow chains, and Table D for statistics. The record data stored in B makes it the largest section.

TABLE B contains all retrievable data fields for records in the file. Table A only has hash codes for lookup, Table C handles overflow, and Table D has statistics. All actual field data that queries access lives in Table B.

FPC (Find and Print Count) is the M204 command that counts and displays the number of records satisfying a condition. WOL is for ordered retrieval, FCOUNT is not a valid M204 command, and FRC is not a standard command.

PRINT STOR.CODE AND CTRY.CODE prints the two fields with a space between them in M204. The AND keyword inserts a space separator. WITH has different semantics (conditional), and commas produce comma-separated output without a space.

FREB204 (File Execution Batch 204) is the M204 utility that executes batch procedures. BATCH204, ADDR204, and EXEC204 are not standard M204 utility names for batch execution.

Variable names in M204 procedures are prefixed with % (percent sign). Options B, C, and D use $, ?, and # which are not valid M204 variable prefixes. The % prefix distinguishes variables from field names and commands.

In Model 204, the $SUBSYS function is used to determine the status or retrieve information about a specific subsystem.

FOR 3 RECORDS IN A is the correct statement to limit printing to the first 3 records of found set A. This syntax explicitly specifies the number of records to process. 'FR A' would process all records, 'FOR THREE RECORDS' uses a word instead of number, and 'FOR K RECORDS' uses an undefined variable K.

In Model 204, when K is negative in 'FOR K VALUES OF FIELDNAME', the statement loops through ALL occurrences of the field, not just a limited number. This is a special case where a negative value acts as a flag to process the entire set. Option B correctly describes this behavior. Options A and D are incorrect because the loop is neither skipped nor executed just once. Option C is incorrect because the loop terminates after processing all values.

The NOTE statement in Model 204 specifically marks only the FIRST occurrence within a multiply occurring field. This is useful when you need to identify the primary or initial value in a repeated field. Option C correctly states this behavior. Option B is incorrect because NOTE doesn't track login dates. Options A and D are incorrect because NOTE doesn't work on procedures and doesn't mark the last occurrence.

The FOR EACH RECORD IN ORDER BY statement both retrieves and loops through only the FIRST occurrence of a field in each record, not all occurrences. This is important when you want to process unique records without duplicate field values. Option A correctly describes this behavior. Options B, C, and D are incorrect because the statement doesn't just loop without retrieval, doesn't process all occurrences, and isn't limited to the last occurrence.

The COUNT IN clause refers specifically to the count value generated by the COUNT OCCURRENCES statement, not to counting 'IN' keywords or database files. This allows you to use the occurrence count in subsequent operations. Option A correctly identifies this relationship. Options B and D are incorrect because COUNT IN doesn't count keywords or use a generic Count statement. Option C is incorrect because it doesn't count database files.

The CLEARGO command in Model 204 clears all global images, screens, menus, found sets, lists, and both temporary and permanent positions from GTBL, but it specifically does NOT clear global variables. This selective clearing is important for preserving variable state while resetting other global elements. Option A correctly states this behavior. Option B is incorrect because it includes global variables. Options C and D are incorrect because CLEARGO doesn't target garbage variables or only global variables.

In Model 204, TTBL (terminal table), GTBL (global table), and STBL (screen table) are valid user language working areas. FSBC is NOT a valid working area in the Model 204 system. Option A correctly identifies FSBC as invalid. Options B, C, and D are incorrect because they list valid working areas (TTBL, GTBL, STBL).

The VALUE IN statement can be used with ADD, CHANGE, and STORE RECORD statements in Model 204, making it versatile for field manipulation. It allows you to reference specific values within these operations. Option D correctly states that VALUE IN works with all three statement types. Options A, B, and C are incorrect because VALUE IN isn't limited to just one of these statements - it works with all of them.

The statement 'CHANGE FULLNAME TO' with no value specified is equivalent to 'DELETE FULLNAME' - it removes the field from the record. This is a shorthand way to delete a field without explicitly using the DELETE command. Option D correctly identifies this equivalence. Options A, B, and C are incorrect because they attempt to assign specific values (NULL as keyword, string, or number) when the actual operation is deletion.

In Model 204 pattern matching, the '/' character is a REPEAT character that specifies how many times the preceding pattern element should repeat. This is different from wildcards, alphabetic characters, or OR operators. Option D correctly identifies '/' as a repeat character. Options A, B, and C are incorrect because '/' isn't a wildcard, doesn't represent alphabetic characters, and isn't an OR operator.