Computer File Systems

The MERGE stage in DataStage is specifically designed to join exactly TWO files or datasets. It cannot merge more than two inputs. For joining multiple data sources (more than two), you would need to use JOIN stages or use multiple MERGE stages in sequence. Therefore, the statement that more than two files can be joined using MERGE stage is false.

Hashed files in DataStage are used primarily as lookup/reference sources, not as primary data sources. The statement claims they can be used as primary sources, which is incorrect.

LinkCollector, Link Partitioner, and Aggregator are all active stages that process or transform data. Hashed File is a passive stage that stores data for lookup operations without actively processing the data flow.

The correct command for analyzing hashed files in DataStage is 'HASH.FILE' or commands through DataStage Administrator. 'FILE.STAT' is not a valid DataStage command, so the statement correctly identifies it as not the right command.

Hashed files use a hashing algorithm on key columns, which naturally eliminates duplicate records because identical keys produce the same hash value and overwrite previous entries. This automatic deduplication is a fundamental property of hash-based storage. The other options describe different DataStage operations not inherent to hashed files.

The cat command prints the entire contents of a file directly to the standard output, making it the primary tool to visualize files. While more is a pager and view is a read-only editor, type is used to identify command types, making cat the best option.

A folder map in Documentum Web Publisher is an XML file containing rules that place content files in specific locations in Web Cabinets based on file properties. The system evaluates folder maps whenever objects are created or properties change. When paths reference secondary folder maps, those secondary maps are evaluated before returning to the primary. The rules define the relationship between property values and repository paths.

In Content Management Systems, the Folder Map defines the directory structure and determines where each content file is stored within the web cabinet. It maps content types to specific folder locations. Rules Files define processing logic, while Presentation Files control display formatting.

A Site Publishing Configuration (SPC) in Documentum Site Caching Services (SCS) specifies various settings for the publishing process. This includes the source directory, target directory, file formats/filters to include or exclude, and the logging/trace levels for troubleshooting.

MP4, AVI, and QT are all legitimate video file extensions for different video formats. JPG is a standard image compression format for photographs and graphics, not a video format. Video formats contain sequential frames and audio tracks, while JPG stores single static images.

EPS (Encapsulated PostScript) is a vector graphics format that uses mathematical equations to define images, not pixel grids. Vector formats like EPS maintain quality at any scale. Bitmap images (BMP, PNG, JPG) store individual pixels and become pixelated when enlarged.

The /res/raw directory is specifically designed for files that should NOT be compiled into binary format. Files placed here are copied to the device as-is. In contrast, /res/xml files are parsed and compiled into a binary XML format, and /res/layout files are also compiled into binary format during the build process.

In SQLite3 and Android best practices, large files like bitmaps or audio files are typically NOT stored directly within database tables as BLOBs. Instead, they're stored in the file system, and only the file path or URI is stored in the database. This approach is more efficient, avoids database bloating, and is easier to manage.

Environment.getExternalStorageDirectory() returns the path to the primary shared/external storage directory. This is the standard Android API for accessing SD card storage. Context does not have a getStorageDirectory() method, and Environment.getStorageDirectory() does not exist.

EasyTrieve does NOT have a FILE SECTION - that is specific to COBOL. EasyTrieve has ENVIRONMENT SECTION for system configuration, LIBRARY SECTION for defining fields and variables, and ACTIVITY SECTION for procedural logic. File handling in EasyTrieve is done differently than in COBOL.