Computer File Systems

On Windows systems, NetBackup temporary files are stored in C:\Program Files\VERITAS\NetBackup\Temp. This is the default installation location for NetBackup on Windows. The other options (Windows folder, VERITAS root, My Documents) are not the correct locations for NetBackup temporary files.

The control file in SQL Loader specifies: how to interpret the data format (field delimiters, data types), location and format of the source data file, and paths for bad/discard files. Database connection parameters are passed on the command line (userid=), not defined in the control file.

In QTP (QuickTest Professional), files with the .tsr extension represent shared object repositories. Other options like .vbs are action/script files, and data is typically stored in Excel .xls or .xlsx files.

In COBOL, the OUTPUT mode opens a new or empty file for writing, replacing any existing content. The EXTEND mode opens a file to write records starting at the end of the existing file (appending). INPUT is read-only, and APPEND is not a valid COBOL OPEN keyword.

In COBOL, USAGE IS COMP (Computational) specifies binary format storage for numeric variables, which is highly efficient for arithmetic. USAGE IS COMP-3 defines packed decimal format, where each digit is packed into a half-byte (nibble) with the sign in the last nibble.

The REDEFINES clause in COBOL can only be used in the WORKING-STORAGE SECTION and LINKAGE SECTION, not in the FILE SECTION. In FILE SECTION, you must use separate record definitions instead.

In COBOL file handling, file status code 10 indicates end-of-file condition when reading a sequential file. This is a standard status code returned when a READ statement attempts to read beyond the last record in the file.

ISPF option 3.3 provides the Move/Copy Utility that allows copying data from one dataset to another. This option supports both sequential and PDS datasets and is commonly used for dataset operations.

In InfoSphere DataStage, a Sequential File stage can be configured to either read data from or write data to a flat file in a given instance. It cannot perform both read and write operations concurrently on the same link path in a single execution.

File Sets in DataStage have three key characteristics: they are partitioned across multiple files for parallel processing (A), they are readable by external applications because they use a standard format (D), and they consist of a header file describing the structure plus separate data files (E). Option B is false (file sets are partitioned), and Option C is false (they are multiple files, not a single file).

Dalvik VM (the virtual machine in Android's runtime) executes files in .dex (Dalvik Executable) format. Java bytecode is converted to .dex format during the Android build process. The .dex format is optimized for memory-constrained devices and uses a different instruction set than standard Java bytecode. .txt, .dtx, and .dx are not executable formats for Dalvik VM.

The BFILE data type stores a locator pointer to a binary file residing on the external operating system server filesystem. BLOB and CLOB store binary and character data internally inside the database tablespaces, while LONG RAW is a deprecated internal data type.

SilkTest projects use .t for test scripts, .pln for test plans, .ini for configuration settings, and .opt for options files. .vbs and .qfl files are standard in HP/Micro Focus UFT (QTP) rather than SilkTest.

An Entry Sequenced Data Set (ESDS) is a VSAM file structure where records are stored sequentially in the exact physical order in which they are written. KSDS uses keys, RRDS uses relative record numbers, and LDS is a byte-stream dataset.

The Assets folder in an Android project contains files that ARE packaged with the application. Unlike resources which are compiled and accessed through R.java, assets are included in the APK as-is and accessed via AssetManager. The statement claims they are 'not packaged' which is incorrect.