Computer File Systems

In COBOL, BLOCK CONTAINS 0 with SEQUENTIAL organization indicates a Fixed Block record format. This configuration tells the system that records are fixed-length and blocked. Option B (Fixed Unblock) would omit the BLOCK CONTAINS clause or specify BLOCK CONTAINS 1.

QTP uses XML format for exporting and importing object repositories, making them human-readable and editable. MTS, TSR, and XLS are not used for object repository operations - TSR is a file extension, not the format itself.

QuickTest Professional (QTP) supports multiple file extensions for function libraries, including .qfl, .vbs, or even files with no extension at all. .bat files are batch execution files and are not supported as QTP function libraries.

TSR is the file extension for shared object repository files in QTP. MTR and MTS are not QTP file extensions, and QFL is for function libraries, not object repositories.

ESDS (Entry Sequenced Data Set) files do not allow record deletion - records can only be added sequentially. This is a fundamental characteristic of ESDS organization in VSAM. Normal delete processes won't work, and you cannot delete even with random reads.

To open a file for writing in COBOL, you can use OUTPUT mode (creates new or truncates existing) or EXTEND mode (adds to end of existing file). INPUT (A) is for reading only. I-O (B) is for reading AND writing existing records, not pure writing. Option C incorrectly includes I-O.

The /etc/shadow file contains encrypted passwords. In modern Unix systems, password information is split: /etc/passwd contains public user information (username, UID, GID, home directory, shell) and is world-readable, while /etc/shadow contains sensitive data including encrypted passwords and is readable only by root. The 'one character' mentioned in the question likely refers to the 'x' placeholder in /etc/passwd which indicates the password is stored in /etc/shadow. The .rch extensions are not standard Unix files.

The tar (tape archive) command is used to archive files in Unix/Linux. It combines multiple files into a single archive file without compression by default. The compress and gzip commands are used for compression of individual files, not for creating archives. The -z flag with tar (tar -czf) creates compressed archives using gzip. There is no standard 'archive' command in Unix. The word 'commad' in the question is a typo for 'command'.

In LoadRunner Controller, scenario groups use .usr files which contain the Vuser script and configuration. .lrr is for scenario results, .lra is for analysis files, and .lrs is for scenario files. The .usr file is the correct choice for defining Vuser groups in scenarios.

User controls in ASP.NET use the .ascx file extension, which distinguishes them from web forms (.aspx) and web services (.asmx). The 'ascx' stands for 'ASP.NET User Control'.

Web forms in ASP.NET are stored with the .aspx file extension, which is the standard for ASP.NET web pages. The 'aspx' extension indicates an ASP.NET page that can contain server controls and code.

iso9660 is the CD-ROM file system, proc is the process information filesystem, and FFS is the Unix Fast File System. MFS typically refers to the Macintosh File System, which is not native to Unix, though some Unix systems have a Memory File System with the same abbreviation.

The /opt directory is the standard location for optional software packages in Unix/Linux systems. It's designed to hold add-on applications that are not part of the base system installation.

/etc/mtab contains information about currently mounted filesystems on Linux systems, dynamically updated by the mount command. /etc/fstab contains static configuration for filesystems to mount at boot, while /etc/inittab is for init system configuration. /etc/filesystems defines filesystem types but not mount status.

RMAN BACKUP command cannot back up online redo log files. RMAN supports backing up datafiles, control files, parameter files (spfile), archivelog files, and even backup sets themselves, but online redo logs are explicitly excluded. This is by design - redo logs are managed through the log switch/archive mechanism, not RMAN backups. Attempting to back them up with RMAN will fail.