Computer File Systems

IConv (Input Conversion) converts external string representations to internal storage formats, like converting a date string to internal date format. OConv (Output Conversion) does the reverse - converts from internal to external display format. Both are DataStage BASIC functions for data conversion.

DataStage supports exporting metadata including field definitions for sequential files through table definitions. You can export, import, and reuse metadata across jobs using the Repository or by exporting to .ds files. The statement claiming we can't export metadata is false - metadata management is a core DataStage capability.

The Sequential File stage is primarily used for reading (extract) and writing (load) sequential files. It does not perform transformations - that's the role of stages like Transformer. The stage is bidirectional but focused on data transfer, not manipulation.

All listed options (file path, file format, column definitions) ARE components of the Sequential File stage configuration. The question asks what is NOT a component, making 'None of the above' the correct answer because all options A, B, and C are valid components.

A DataStage configuration file for parallel jobs specifies all execution environment parameters: number of processes/nodes for parallel processing, disk storage locations for data, and the 'fastname' (node identifier). All three components are essential for proper parallel job configuration.

Sequential files are typically read by a single node. To enable parallel reading where multiple nodes each read parts of the file, you must select the "Read From Multiple Nodes" option. This allows the file to be partitioned across nodes for parallel processing. Number of Readers Per Node controls reader count per node, not multi-node access.

Hashed files in DataStage provide optimized storage and retrieval for reference data. They are ideal for lookups due to their key-based structure, excel at storing relatively static reference data like country codes or exchange rates, and offer very fast lookup performance using hash-based access rather than full table scans.

In Ab Initio, .xfr files contain Transform function code (business logic for data transformation), and .dml files contain Data Manipulation Language specifications (record formats and metadata). These are both package file extensions used in Ab Initio development. .mp files are metadata files and .cfg files are configuration files, but they're not typically classified as package extensions in the same context.

In SYNON, file-to-file relations include defined as, owned by, and extended by. known by is a file-to-field relation, and refers is not a valid relation name, making both correct answers.

ICONV is a DataStage BASIC function that converts string representations to internal storage format. For example, ICONV('2024-01-15','D') converts a date string to internal date integer. Option B correctly describes this conversion to internal format. Options A and C reverse the direction (OCONV does internal-to-string).

Indexed and Relative file organizations both support sequential and random access methods. Indexed files allow access via sequential reads or through a key lookup, while Relative files support sequential processing or direct access by relative record number. Sequential files only support sequential access, making option B the correct choice.

The DELETE statement cannot remove records from SEQUENTIAL files in COBOL. Sequential files must be processed with rewrite operations to effectively delete records, whereas RELATIVE and INDEXED files support direct record deletion via DELETE. This limitation exists because sequential files don't have individual record addressing required for deletion.

In TANDEM COBOL85, as with standard COBOL practice, files should be explicitly closed using the CLOSE statement before executing STOP RUN. This ensures proper file buffer flushing, record updates, and resource cleanup. Relying on implicit closure can lead to data loss or corruption.

The REWRITE verb in COBOL requires the file to be opened in I-O (Input-Output) mode. This is because REWRITE reads an existing record and then writes it back in the same position - it needs both read and write access. INPUT mode only allows reading, OUTPUT mode only allows writing new records, and EXTEND mode only adds records at the end.

To write new records into a file, the file must be opened in OUTPUT (to write new records), I-O (to insert/modify), or EXTEND (to append records). Therefore, both options a and b are valid. The distractor claiming none of these is wrong because these modes directly support write operations.