Computer File Systems

WAV (Waveform Audio File Format) is a Microsoft/IBM standard audio format for storing sound bitstreams on PCs. It contains uncompressed raw audio data and is specifically designed for sound files, not images, video, or documents.

Sequential file stages in DataStage are typically used as source or target stages for reading from or writing to flat files. They are not designed to be intermediate stages for data passing between other stages within a job. Use Dataset stages or in-memory buffers for intermediate storage.

The extended stored procedure xp_fileexist checks whether a specified file exists on the server's file system and returns output parameters indicating file existence. It returns 1 in the 'File Exists' parameter if the file is found. Note: Extended stored procedures are deprecated in modern SQL Server versions in favor of FILESTREAM and other methods.

I-O mode in COBOL allows both reading and updating records in a file, which is required when you need to modify existing records. Input mode only permits reading, Output mode creates new files, and Extended is not a standard file open mode in COBOL.

In the SELECT statement, the filename immediately following SELECT (FILE-1) is the logical filename used inside the COBOL program, and the name assigned (INFILE) corresponds to the external physical file or JCL DD name.

In DPS, the REP function replaces a saved form in its existing storage location, updating the copy that was previously saved. SAV saves to new storage, MOD modifies form data, and OLD retrieves previous versions.

In COBOL, DYNAMIC access mode allows a program to switch between sequential and random access of records on the same file. SEQUENTIAL only permits serial reading, and RANDOM only permits direct reading by key, making DYNAMIC the correct choice.

In COBOL, INDEXED, RELATIVE, and SEQUENTIAL file organizations can all be opened in INPUT, I-O, OUTPUT, and EXTEND modes. Each file type supports these four access modes for different operations.

The UNSTRING verb in COBOL is used to split a single string into multiple fields, not to transfer data from several sources to one receiving file. STRING is used for combining multiple fields into one.

In the Sequential File Stage, the 'Output' Reject Mode writes rejected records to a reject link for later handling. 'Fail' stops the job entirely on rejection, 'Drop' silently discards rejected records, and 'Continue' processes remaining records but doesn't write rejects anywhere.

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.

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.

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.