IBM DataStage and Cognos Fundamentals

Report Studio authors access the runtime version of a Framework Manager model through packages. The runtime version contains published metadata from Framework Manager optimized for report authoring. Authors cannot access development models or externalized files directly.

When importing numeric columns that are not indexed, Framework Manager sets the Usage property to Fact by default. Facts are typically numeric values that can be aggregated (summed, averaged, etc.) in reports. Attributes are descriptive text, identifiers are unique keys, and Unknown is the initial state before analysis.

Cognos Report Studio supports multiple output formats including Excel, HTML, and PDF - these are the three core export formats available. Word format is not natively supported as a standard export option in Report Studio. Option E 'All the above' is incorrect because Word is not a valid output format.

A Text Box Prompt is designed for free-text input where users know the exact value they want to enter, such as searching by name, account number, or ID. Value prompts present a predefined list to select from, Date prompts specifically handle calendar selection, and Generate Prompt is not a standard prompt type - it's likely a distractor.

The Insertable Objects pane in IBM Cognos Report Studio has three main tabs: Source, Data Item, and Toolbox. The Source tab provides access to available data sources, the Data Item tab contains data items that can be added to reports, and the Toolbox tab contains tools and objects for report design. The Properties tab is not part of the Insertable Objects pane - it's a separate panel.

In Cognos prompt interfaces, a star (*) indicates that a prompt is mandatory, and an arrow (>) indicates that no selection has been made yet. When both adornments appear together, it means the prompt requires a response but the user hasn't made any selection. Option A incorrectly combines mandatory status with single-selection constraint, while Option B omits the mandatory requirement.

When a user's authentication session expires, the browser may retain stale authentication cookies or data in its cache. Clearing the cache removes these stale credentials. Similarly, clearing browser history can remove stored session data that might be causing the 'User Already Authenticated' error. Renewing credentials or refreshing certificates are not the correct solutions for a session timeout issue.

In DataStage, passive stages are those that don't perform any active data processing or transformation - they simply read from or write to data sources. The Sequential File stage is passive because it only reads from or writes to files without manipulating the data. In contrast, Transformer, Aggregator, and Sort are active stages that perform data transformations.

The Link Collector stage in IBM InfoSphere DataStage can accept a maximum of 64 input links. This is a hard limit in DataStage architecture. Link Collectors are used to merge data from multiple sources, and understanding this limit is important for job design. Options 8, 32, and 128 are all incorrect - the actual limit is 64.

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.

The Execute Command activity in workflow and ETL tools is specifically designed to run operating system commands or scripts. Job Activity manages job control, Nested Condition handles conditional logic, and Routine Activity executes predefined routines or functions. Only Execute Command can invoke OS-level commands directly, making option D correct.

In DataStage, description annotations can be copied and pasted between different jobs. The statement claims they cannot be transferred between jobs, which is incorrect.

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.

The InterProcess stage in DataStage is an active stage that manages inter-process communication between jobs. The statement claims it's passive, 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.

Stage Variables in DataStage are intermediate variables that hold values during row processing but don't automatically pass values to target columns. Derivations, Constants, and Functions don't match this description.

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.

DataStage uses 256 MB as the default cache size for lookup operations and other in-memory processing. This default balances performance with typical memory constraints.