Operating Systems

In JCL (Job Control Language for IBM mainframes), parameters can be positional or keyword. Positional parameters MUST be coded first and are interpreted based on their order in the statement. Keyword parameters (NAME=value) can come after positional ones and are self-identifying. This ordering rule is mandatory - you cannot place keyword parameters before positional ones.

JCL comment lines begin with //* in the first two columns. The //* sequence indicates that the rest of the line is a comment. Option A // is used for JCL statements (not comments). Option B /* is C-style comment syntax (not JCL). Option C ** is not JCL comment syntax. Only Option D //* correctly identifies the JCL comment format.

POSITIONAL parameters in JCL are interpreted by the operating system based strictly on their order - the first positional parameter maps to the first expected parameter, the second to the second, etc. Their meaning depends entirely on position. KEYWORD parameters (NAME=value) are self-identifying and order-independent. The question specifically asks which type is 'interpreted based on the order', which describes positional parameters.

The identifier (or name) field is the first field in a JCL statement, beginning with //. This field identifies the statement and gives it a name that can be referenced by other statements. It appears before the operation, parameter, and comment fields in the standard JCL statement structure.

WebKit, Media Framework, and Surface Manager are all C/C++ native libraries running directly above the Linux Kernel. In contrast, the Notification Manager (596959) belongs to the higher-level Java Application Framework layer, meaning it is not part of the native libraries layer.

The Zygote process is responsible for starting Dalvik VM instances in Android. When a new application needs to run, the Zygote forks itself to create a new Dalvik VM instance, which is more efficient than starting from scratch.

Android is officially defined as a comprehensive software stack for mobile devices, comprising a Linux-based operating system, middleware, and core applications along with APIs (597020). The other options represent only individual components of this multi-layered stack rather than the entire package.

Dalvik VM was specifically designed to allow multiple VM instances to run efficiently on a single device. This architecture enables Android to run multiple applications simultaneously, each in its own VM instance, with optimized memory usage and resource management.

Database connection parameters in MII are configured under Data Services -> Data Servers tab. This is where you define connection strings, drivers, and authentication details for SQL databases. The other tabs serve different purposes (buffer entries, security, SAP server configuration).

PermView.exe is a .NET SDK utility that displays the permission requests (minimal, optional, refused) declared in an assembly's metadata. Options B through E describe unrelated functionality - PermView has nothing to do with Dataset views, heap management, or dynamic assemblies. It's specifically a security diagnostic tool for examining CAS (Code Access Security) permission requests.

An APK contains compiled .dex files (Dalvik bytecode), the AndroidManifest.xml, all application resources, and native .so libraries for JNI. All three components listed are present in a standard APK structure.

The dx tool is part of the Android SDK that converts .class bytecode to .dex format. Running dx --version verifies the dx tool is installed and functional, confirming the Android SDK setup. dex and aapt are different tools.

In the Android SDK command line tools, the command to view available targets is android list targets (plural). Option C correctly specifies this command.

The 'android list' command in Android SDK displays both available Android targets (different platform versions and API levels) and Android Virtual Devices (AVDs) that have been created. Option C correctly identifies that this single command shows both types of information.