Question 1

What does Dimensions for z/OS do?

Accepted Answer

Dimensions for z/OS is a change management system that helps organizations manage and control changes to their software and configurations on the z/OS platform. It provides features for version control, release management, and audit trails, ensuring that changes are properly tracked and implemented.

Question 2

Is this a system, application, or tool?

Accepted Answer

Dimensions for z/OS is a system. It provides a comprehensive set of features for managing changes across the software development lifecycle. It is not simply a tool or application, but a complete system for change and configuration management.

Question 3

What types of organizations use this?

Accepted Answer

Organizations that develop and maintain software on the z/OS platform, particularly those in regulated industries such as banking, finance, and government, commonly use Dimensions for z/OS. These organizations require robust change management processes to ensure compliance and minimize risks associated with software changes.

Question 4

When should we consider Dimensions for z/OS?

Accepted Answer

A company should consider Dimensions for z/OS when they need to improve their change management processes on the z/OS platform. This includes situations where they are experiencing frequent errors due to uncontrolled changes, struggling to meet compliance requirements, or need better visibility into their software development lifecycle.

Question 5

What are the alternatives to Dimensions for z/OS?

Accepted Answer

Alternatives to Dimensions for z/OS include CA Endevor, Compuware Topaz, and IBM Rational Team Concert. These products offer similar change management capabilities for the z/OS platform, but may differ in terms of features, integration capabilities, and ease of use.

Question 6

For mainframe products: Does this run in an LPAR?

Accepted Answer

Dimensions for z/OS runs on the z/OS platform and requires specific subsystems to be present, such as DB2 for storing metadata and control information. It typically runs in an LPAR and is dependent on the z/OS operating system.

Question 7

What infrastructure is required?

Accepted Answer

Dimensions for z/OS requires a z/OS environment, including the operating system and necessary subsystems. It also requires a database, such as DB2, to store metadata and configuration information. Network connectivity is needed for communication between components.

Question 8

What is the architecture of Dimensions for z/OS?

Accepted Answer

Dimensions for z/OS uses a client-server architecture. The client component provides the user interface for interacting with the system, while the server component manages the repository and enforces change management policies. Communication between the client and server occurs over a network using TCP/IP.

Question 9

What are some common commands in Dimensions for z/OS?

Accepted Answer

Common commands include creating and modifying items, checking items in and out of the repository, creating baselines, and promoting changes through the development lifecycle. Specific commands include 'CREATE ITEM', 'MODIFY ITEM', 'CHECKOUT', 'CHECKIN', 'BASELINE CREATE', and 'PROMOTE'.

Question 10

What is the business value of Dimensions for z/OS?

Accepted Answer

Dimensions for z/OS helps organizations reduce the risks associated with software changes, improve compliance with regulatory requirements, and increase the efficiency of their software development processes. By providing a controlled and auditable environment for managing changes, it minimizes errors and ensures that changes are properly implemented.

Question 11

What happens if an organization does not use Dimensions for z/OS?

Accepted Answer

Without Dimensions for z/OS, organizations may experience uncontrolled software changes, increased errors, difficulty meeting compliance requirements, and reduced visibility into their software development lifecycle. This can lead to increased costs, delays, and reputational damage.

Question 12

How does Dimensions for z/OS integrate with other systems?

Accepted Answer

Dimensions for z/OS integrates with other enterprise systems, such as build automation tools, testing frameworks, and deployment pipelines. This allows organizations to automate their software development processes and ensure that changes are properly integrated and tested before being deployed to production.

Question 13

What security features does Dimensions for z/OS provide?

Accepted Answer

Dimensions for z/OS supports authentication methods such as RACF, ACF2, and Top Secret. It uses an access control model based on roles and permissions, allowing administrators to define granular access controls for different users and groups. Encryption is used to protect sensitive data, such as passwords and configuration information.

Question 14

What audit and logging capabilities exist?

Accepted Answer

Dimensions for z/OS provides audit logging capabilities that track all changes made to the system, including who made the changes, when they were made, and what was changed. This allows organizations to monitor activity and identify potential security breaches.

Question 15

What access control model is used?

Accepted Answer

Dimensions for z/OS uses role-based access control (RBAC) to manage user permissions. Administrators assign users to roles, and each role has specific permissions that define what actions the user can perform within the system. This allows for granular control over access to sensitive data and functionality.

Question 16

How is Dimensions for z/OS typically deployed?

Accepted Answer

Dimensions for z/OS is typically deployed on-premise, within the organization's z/OS environment. Implementation requires technical expertise in z/OS, change management, and database administration. Ongoing operational requirements include monitoring system performance, maintaining the database, and managing user access.

Question 17

What are common implementation challenges?

Accepted Answer

Implementing Dimensions for z/OS can be challenging due to the complexity of the z/OS environment and the need to integrate with other systems. Common challenges include configuring the system to meet specific business requirements, migrating existing data, and training users on the new system.

Question 18

What administrative interfaces are available?

Accepted Answer

Administrative interfaces include a command-line interface (CLI) and a graphical user interface (GUI). The CLI is used for performing administrative tasks, such as configuring the system and managing users. The GUI provides a user-friendly interface for monitoring system performance and managing change requests.

Share Your Product Experience

Dimensions for z/OS

Product Overview

Frequently Asked Questions

What does Dimensions for z/OS do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider Dimensions for z/OS?

What are the alternatives to Dimensions for z/OS?

For mainframe products: Does this run in an LPAR?

What infrastructure is required?

What is the architecture of Dimensions for z/OS?

What are some common commands in Dimensions for z/OS?

What is the business value of Dimensions for z/OS?

What happens if an organization does not use Dimensions for z/OS?

How does Dimensions for z/OS integrate with other systems?

What security features does Dimensions for z/OS provide?

What audit and logging capabilities exist?

What access control model is used?

How is Dimensions for z/OS typically deployed?

What are common implementation challenges?

What administrative interfaces are available?

Related Products

More from OpenText Corporation

Expedite Base

Expedite Base/CICS

Similar Products

ASG-TMON Change Manager for CICS

Breeze for SCLM

CA Alchemist

CA Harvest Software Change Manager

CA Netman

CA PanAPT

Help Improve This Directory

Share Your Product Experience